53-1001193-02 December 5, 2008 EZSwitchSetup Administrator’s Guide Supporting Fabric OS v6.2.0 Supporting Brocade 200E, 300, 4100, 4900, 5000, 5100, 5300.This director-class SAN switch product guide provides the attributes of director switch products and a spec list for Brocade and Cisco Systems directors. Brocade’s Network Functions Virtualization (NFV) solutions help build fast, secure networks where the need for agility and automation is paramount. With the Brocade vRouter you get ease in scalability, breadth in capability, and peace of mind from rock solid reliability. Whenever you see a leap in a minor version there is a bucket-load of new functions and features in software and FOS 7.4.0 is no exception. Besides the usual bugfixes. PROPER USE OF HEALTH CONTENT. The Technology/Standard List identifies technologies and technical standards that have been assessed. Each project team must. Create zoning with Brocade SAN switch WEB tool - GUI Step by step create zone configuration 1. Brocade Network Advisor - Technical How-To - Using the BNA Dashboard - Duration: 7:25. Brocade Communications Systems, Inc. AWS OpsWorks is a configuration management service that makes it easy for DevOps engineers to operate and manage applications using Chef automation. To collect supportsave from BNA(Brocade Network Advisor) or DCFM, go to Monitor=>Technical Support =>SupportSave. You can also schdule supportsave. Scheduling - Open. Stack Configuration Reference. Compute uses the nova- scheduler service to determine how to. For example, the. VM should launch on. The term. host in the context of filters. You can. configure the scheduler through a variety of options. Compute is configured with the following default scheduler options in the. By default, the scheduler. In the default. configuration, this scheduler considers hosts that meet all. The scheduler caches its list of available hosts; you can. Instances are evacuated to the host explicitly. For information about instance evacuation. Evacuate. instances section of the Cloud Administrator Guide. The Filter Scheduler. It supports filtering and weighting to make. When the Filter Scheduler receives a request for a. Filters are binary: either a host is accepted by. Hosts that are accepted by. Weights section. Filtering. The scheduler. The default setting. Compute service: scheduler. For example, if you implemented your own custom. Python called. myfilter. My. Filter and you wanted to. The default filters. If the. per- aggregate value is not found, the value falls back. Aggregate. Image. Properties. Isolation. Matches properties defined in an image's metadata against those of aggregates to. If a host belongs to an aggregate and the aggregate defines one or. If a host does not belong to any aggregate, it can boot instances from. For example, the following aggregate my. Win. Agg has the. Windows operating system as metadata (named 'windows'): $ nova aggregate- details My. Win. Agg. +- -- -+- -- -- -- -- -+- -- -- -- -- -- -- -- -- -- +- -- -- -- -- -- -+- -- -- -- -- -- -- -- +. Aggregate. Instance. Extra. Specs. Filter. Matches properties defined in an instance type's. Works with specifications that are. Aggregate. Multi. Tenancy. Isolation. Isolates tenants to specific host aggregates. A host can be in different aggregates. If a. host does not belong to an aggregate with the metadata. Implements blueprint. If. per- aggregate value is not found, it falls back to the. This is a no- op filter, it does not eliminate any of. Filters hosts by availability zone. This filter must. Compute. Capabilities. Filter. Matches properties defined in an instance type's. If an extra specs key contains a colon . If a namespace is present and is not. Passes all hosts that are operational and. In general, this filter should always be enabled. If this filter is not. This filter can be configured to allow a fixed. CPU overcommitment by using the. The default setting. As. a result changes to the cpu. Changes to this configuration key are only taken. To take advantage of this filter, the. This filter is. the opposite of the Same. Host. Filter. For. For. example. The default setting. This might be desirable if you. The Group. Affinity. Filter ensures that an instance is. To. take advantage of this filter, the requester must pass. Using the. nova command- line tool, use the. For. example: $ nova boot - -image IMAGE. To take. advantage of this filter, the requester must pass a. Using the. nova command- line tool, use the. For. example: $ nova boot - -image IMAGE. It passes hosts that can support the. An image can be decorated. Examples. are i. 68. Examples are xen, kvm. The flag. restrict. For example. isolated. The. following operators are supported: The filter supports the following variables: $free. If this filter is not set. RAM. (for example, the RAM allocated by virtual machine. RAM). This filter can be configured to allow a fixed. RAM overcommitment by using the. The default setting. If the scheduler selects a. This filter is only useful if the. To take advantage of. This filter is. the opposite of the. Different. Host. Filter. Using the. nova command- line tool, use the. To. take advantage of this filter, the requester must create a. UUID as the value. Using the. nova command- line tool, use the. For. example: $ nova server- group- create - -policy affinity group- 1. IMAGE. To take advantage of this. UUID as the value. Using the. nova command- line tool, use the. For. example: $ nova server- group- create - -policy anti- affinity group- 1. IMAGE. For example. IP subnet. 1. 92. Each time the scheduler selects a host, it virtually consumes. This process is. useful when the customer asks for the same large amount of instances, because weight is. All weights are normalized before being summed up; the host with the largest weight is. Weighing hosts. If cells are used, cells are weighted by the scheduler in the same manner as hosts. Hosts and cells are weighed based on the following options in the. Table 2. 8. Host Weighting options. Section. Option. Description. Set the. ram. Use a. This property defines the subset size from which a host. A value of 1 chooses the first host returned by the weighing. This value must be at least 1. A value less than 1 is ignored, and. Use an integer value. Hosts are then weighed. Use a floating- point value. Use a comma- separated list of. Name=ratio. To avoid the raised exception, you should use the scheduler. Metric. Filter to filter out hosts. False—Treated as a negative factor in the weighing process (uses the. Cell weighting options. Section. Option. Description. Use a negative, floating- point value. Use a positive, floating- point value. Use a floating. point value. Set the. ram. Use a floating- point value. Cells are then weighed and sorted. For example. Each node can. This information can be used in the. The nova command- line tool supports. Hosts can be made available to. An error occurs if you cannot add a. Delete an aggregate with id. Show details of the aggregate with id. Add host with name. Remove the host with name. If. you try to use these commands and the user name and. Compute service do. ERROR: Policy doesn't allow compute. For. example, you may want to allow users to request compute. SSD drives if they need access to faster. I/O, or access to compute hosts that have GPU cards. GPU- accelerated code. To configure the scheduler to support host aggregates. You create a fast- io host. Then, you add the. In this case, that is the. Setting a. key- value pair on a flavor is done using the nova. In this example, these are. Xen. Server hypervisor pools to support live. When using the Xen. API- based hypervisor, the Compute. Xen. Server Resource. Local CP, remote CP and BPs' information will be saved,but support. Show information is available only on the Active CP. This operation can take several minutes. NOTE: support. Save will transfer existing trace dump file first, thenautomatically generate and transfer latest one. There will be two trace dumpfiles transferred after this command. OK to proceed? You can also schdule supportsave. What's in Support. Save Collection. Support. Save script will basically compress output before download from switch, below listed supportsave data collected from DCX director. DCX0. 1- S4bp- 2. BCMDRV. If the output came from a director Control Processor (CP) then the “S” number would be between 4 and 7 depending on the type of director. Use ha. Show command to find out the active Cp: SAN0. FID1. 28: admin> slotshow. Blade Type ID Status- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 1 SW BLADE 7. ENABLED 2 SW BLADE 7. ENABLED 3 UNKNOWN VACANT 4 AP BLADE 7. ENABLED 5 CORE BLADE 5. ENABLED 6 CP BLADE 5. ENABLED 7 CP BLADE 5. ENABLED 8 CORE BLADE 5. ENABLED 9 AP BLADE 7. ENABLED 1. 0 UNKNOWN VACANT 1. SW BLADE 7. 7 ENABLED 1. SW BLADE 7. 7 ENABLEDSAN0. FID1. 28: admin> In the example output below, we have DCX with below blades- 4 Port blades, FC8- 6. Blades- 2 AP Blades, FX8- 2. AP Blades- 2 CP Blades, CP8 CP blades. To find out the blade model, using ID to cross reference with blow list. ID1. 6 1. 7 1. 8 3. Type of Blade. CP2. FC4- 1. 6 port blade FC4- 3. FC4- 1. 6IP port blade FA4- 1. FC4- 4. 8 port blade FC8- 1. FS8- 1. 8 application processor blade CR4. S- 8 core blade CP8 control processor blade FC8- 4. Core. 8 core blade FC8- 3. FCo. E1. 0- 2. 4 application processor blade FX8- 2. FC8- 6. 4 switch blade FC1. FC1. 6- 3. 2 switch blade CR1. CR1. 6- 4 core blade FC8- 3. E switch blade FC8- 4. E switch blade. Support. Save Data Collection. Support. Save RAS Log. RAS stands for Reliability, Availability and Serviceability. The RAS log was designed to capature only abnormal, error- related messages, NOT high- frequency audit log events. With FOS 5. 2 and later, error messages go to the RAS log and all Audit events only go to Audit Console. Users enabling event auditing will also configure syslogd to stream data to a remote host running a syslog server. The syslog server files can be periodically checked for audit events. Please note the Audit messages is not included in the Support. Save data collection, you can collect the Audit message by auditdump - s from CLI. The RAS log or System message log is by default save to nonvolatile storage, When more than maximum entries, old entries are overwritten. It's always recommended to setup syslog to forward RAS log and Console log entries to syslog host. The Support. Save includes RAS logs. Error messages can be found in *. SSHOW. Please note only CP blades will report the SSHOW. Date and Time(UTC), 2). Message Module and Numeric instance. It indicate specific Area errors reported error. Please See Appendix A for the complete list of Message Modules, For updated list. Indicates that the error message is either captured from specified Fabric ID (FID) or from a specific SLOT . These are the available severity levels: Level 1 (CRITICAL), Level 2 (ERROR), Level 3 (WARNING), and Level 4 (INFO). FFDC (First Failure Data Capature)With First Failure Data Capture, Sufficient diagnostic information will be captured so problem source identification can occur without recreating the problem. The specific events that trigger an FFDC event are pre- selected by Brocade engineering, and cannot be changed by the user. When an FFDC defined event triggers a core dump then FFDC data is gathered along with panic data. FFDC file can be opened (using Word Pad or another application) the captured data includes the error log (errdump output) before and after the event that triggered the FFDC occurred. It also include console output (boot information) that occurred immediately after the panic. FFDC is enabled by default. To display the FFDC configuration: switch: admin> supportffdc - -show. First Failure Data Capture (FFDC) is disabled. To enable the FFDC events: switch: admin> supportffdc - -enable. First Failure Data Capture (FFDC) is enabled. Panic Dump and Core Dump. In the event of Fabric OS kernal issue, FFDC defined event triggers a core dump and the data capture will be included with FFDC information in compressed file *. CORE. For example, when FOS daemon non- responsive or terminates unexpectedly, a panic dump, core files and FFDC files will be created. You can also display panic dump by using command line, The pdshow command displays data in a panic dump file. The command has oneoptional argument: the name of a specific panic dump file. If no file is specified, output is displayed from the most recent panic dump file. Trace Dump. Trace functionality is a troubleshooting tool, It can be an important aid to debugging system crashes by provided an historical record of switch activity and behavior. A trace dump is generated when. Support. Save Output Use the supportshow command to display support information from groups of preselected Fabric OS and Linux commands and other support and debugging information. For pre- Fabric OS v. SUPPORTSHOW. gz. For Fabric OS v. Support. Save output, there are multiple zip files. SSHOW. BKSWMessages generated by the Blade Fabric OS kernel software watch dog module. BLBlade error messages are a result of faulty hardware, transient out- of- memory conditions, application specific integrated circuit (ASIC) errors, or inconsistencies in the software state between a blade and the EM (environment monitor) module. BLLBloom is the name of the application specific integrated circuit (ASIC) used as the building block for third- generation hardware platforms. BM Blade management error messages are a result of autoleveling firmware upgrades performed by the control processor (CP). EM controls the state of the FRUs during system startup, hot- plug sequences, and fault recovery. EM provides access to and monitors the sensor and status data from the FRUs and maintains the integrity of the system using the environmental and power policies. EM reflects system status by way of CLI commands, system light emitting diodes (LEDs), and status and alarm messages. EM also manages some component- related data. The FABRIC error messages come from the fabric daemon. The fabric daemon follows the FC- SW- 3 standard for the fabric initialization process, such as determining the E. Probing is a process the switch uses to find the devices attached to the loop ports and to update the Name Server with the information. Errors to this module are usually initiation errors or indications that FICON- CUP prerequisites have not been met, such as a license key, core process ID (PID), and secure mode on the fabric. These messages are about protocol errors. These facilities include version negotiation, state information transfer, and internal synchronization functions, enabling the transition from standby to active operation. FSS is defined both as a component and a service. A component is a module in the Fabric OS, implementing a related set of functionality. A service is a collection of components grouped together to achieve a modular software architecture. A component is a module in Fabric OS implementing a related set of functionality. A service is a collection of components grouped together to achieve a modular software architecture. This module monitors thresholds for many switch subsystems: for example, temperature, voltage, fan speed, and switch status. Any changes that cross a specified threshold are reported to the system message log. The HELLO protocol is used to establish connectivity with a neighbor switch, to establish the identity of the neighbor switch, and to exchange FSPF parameters and capabilities. It manages i. SCSI initiator access control, session authentication, and session/connection statistics. It manages i. SCSI configurations such as CHAP, VT/LUN, DD/DDSet and portal configurations, and statistics such as i. SCSI session/connection information. Moreover, ICPD distributes i. SCSI configurations not only switch wide, but also fabric wide. It keeps track i. SCSI VT status and updates VT status to BP. Its functions include: initialization, message delivery from i. SCSI protocol clients, system error monitoring, and fault recovery. This database is used to route frames. Fibre Connection control unit port (FICON- CUP) messages are displayed under the FICU module. Message queues allow many messages, each of variable length, to be queued. Any process or interrupt service routine (ISR) can write messages to a message queue. Any process can read messages from a message queue. MS The Management Service enables the user to obtain information about the Fibre Channel fabric topology and attributes by providing a single management access point. MS provides for both monitoring and control of the following areas: - Fabric Configuration Server. Provides for the configuration management of the fabric. Provides access to Name Server information that is not subject to zone constraints. Provides access to and control of zone information. Input to the FSM changes the local switch from one state to another, based on specific events. For example, when two switches are connected to each other using an ISL (interswitch link) cable, they are in the Init state. After both switches receive HELLO messages, they move to the Database Exchange state, and so on. These messages might display if there are any problems during the firmware. Download procedure. Most messages are informational only and are generated even during successful firmware download. For additional information, refer to the Fabric OS Administrator’s Guide. Additionally, if the SNMP trap option is enabled, an SNMP trap is also sent.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |