53-1002930-01 26 July 2013 Fabric OS Troubleshooting and Diagnostics Guide Supporting Fabric OS v7.2.
Copyright © 2008-2013 Brocade Communications Systems, Inc. All Rights Reserved. ADX, AnyIO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX, MLX, MyBrocade, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and HyperEdge, The Effortless Network, and The On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners.
Document History Title Publication number Summary of changes Date Fabric OS Troubleshooting and Diagnostics Guide 53-0000853-01 First released edition. March 2008 Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01 Added support for Virtual Fabrics, fcPing, pathInfo, and additional troubleshooting tips.
iv Fabric OS Troubleshooting and Diagnostics Guide 53-1002930-01
Contents About This Document How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . xii What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switch boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Rolling Reboot Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 FC-FC routing connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Generating and routing an ECHO . . . . . . . . . . . . . . . . . . . . . . . . 16 Superping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Routing and statistical information . .
Brocade configuration form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Chapter 5 Firmware Download Errors Blade troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Firmware download issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Troubleshooting with the firmwareDownload command . . . . . . . . . 55 Gathering additional information . . . . . . . . . . . . . . . . . . . . . . . . 55 USB error handling . . . . . . . . .
Chapter 9 Zoning Overview of corrective action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Verifying a fabric merge problem . . . . . . . . . . . . . . . . . . . . . . . . 73 Verifying a TI zone problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Segmented fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Zone conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syslogd configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Configuring the host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Configuring the switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Automatic trace dump transfers . . . . . . . . . . . . . . . . . . . . . . . . . . .100 Specifying a remote server . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Enabling the automatic transfer of trace dumps. . . . .
x Fabric OS Troubleshooting and Diagnostics Guide 53-1002930-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii • Additional information . . . . . . . . . . .
Supported hardware and software In those instances in which procedures or parts of procedures documented here apply to some switches but not to others, this guide identifies which switches are supported and which are not. Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. for Fabric OS v7.2.0, documenting all possible configurations and scenarios is beyond the scope of this document.
• In Chapter 10, “Diagnostic Features,” deleted the information about Diagnostic Ports (D_Ports) and moved this information to the Fabric OS Administrator’s Guide. • In Table 22 on page 103, added entries for the Brocade 5431, M6505, and 6547. For further information about documentation updates for this release, refer to the release notes. Document conventions This section describes text formatting conventions and important notice formats used in this document.
Command examples This book describes how to perform configuration tasks using the Fabric OS command line interface, but does not describe the commands in detail. For complete descriptions of all Fabric OS commands, including syntax, operand descriptions, and sample output, refer to the Fabric OS Command Reference. Notes, cautions, and warnings The following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards.
Brocade resources To get up-to-the-minute information, go to http://my.brocade.com and register at no cost for a user ID and password. White papers, online demonstrations, and data sheets are available through the Brocade website at: http://www.brocade.com/products-solutions/products/index.page For additional Brocade documentation, visit the Brocade website: http://www.brocade.com Release notes are available on the MyBrocade website and are also bundled with the Fabric OS firmware.
' "! &' FT00X0054E9 The serial number label is located as follows: • Brocade 5424 — On the bottom of the switch module. • Brocade 300, 5100, and 5300 — On the switch ID pull-out tab located on the bottom of the port side of the switch. • Brocade 6505, 6510, and 6520— On the switch ID pull-out tab located inside the chassis on the port side on the left. • • • • Brocade 7800 — On the bottom of the chassis. Brocade DCX Backbone — On the bottom right on the port side of the chassis.
Chapter 1 Introduction In this chapter • Troubleshooting overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Most common problem areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Questions for common symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Gathering information for your switch support provider . . . . . . . . . . . . . . . . . • Building a case for your switch support provider . . . . . . . .
1 Most common problem areas Most common problem areas Table 1 identifies the most common problem areas that arise within SANs and identifies tools to use to resolve them.
Questions for common symptoms TABLE 2 1 Common symptoms Symptom Areas to check Chapter or Document Blade is faulty Firmware or application download Hardware connections Chapter 2, “General Troubleshooting” Chapter 5, “Firmware Download Errors” Chapter 7, “Virtual Fabrics” Blade is stuck in the “LOADING” state Firmware or application download Chapter 5, “Firmware Download Errors” Configuration upload or download fails FTP or SCP server or USB availability Chapter 4, “Configuration” E_Port fai
1 Questions for common symptoms TABLE 2 Common symptoms (Continued) Symptom Areas to check Chapter or Document License issues Licensing Chapter 2, “General Troubleshooting” LSAN is slow or times-out LSAN tagging Chapter 2, “General Troubleshooting” Marginal link Links Chapter 3, “Connectivity” No connectivity between host and storage Cables SCSI timeout errors SCSI retry errors Zoning Chapter 3, “Connectivity” Chapter 8, “ISL Trunking” Chapter 9, “Zoning” Fibre Channel over IP Administrato
Gathering information for your switch support provider TABLE 2 1 Common symptoms (Continued) Symptom Areas to check Chapter or Document User is unable to change switch settings RBAC settings Account settings Chapter 6, “Security” Virtual Fabric does not form FIDs Chapter 7, “Virtual Fabrics” Zone configuration mismatch Effective configuration Chapter 9, “Zoning” Zone content mismatch Effective configuration Chapter 9, “Zoning” Zone type mismatch Effective configuration Chapter 9, “Zonin
1 Gathering information for your switch support provider 1. Connect to the switch and log in using an account with admin permissions. 2. Enter the appropriate supportSave command based on your needs: • If you are saving to an FTP or SCP server, use the following syntax: supportSave [-n] [-c] When invoked without operands, this command goes into interactive mode. The following operands are optional: -n—Does not prompt for confirmation.
Building a case for your switch support provider 1 Capturing output from a console Some information, such as boot information is only outputted directly to the console. To capture this information, you must connect directly to the switch through its management interface, either a serial cable or an RJ-45 connector that is specifically used for Ethernet connection to the management network. 1. Connect directly to the switch using hyperterminal. 2.
1 Building a case for your switch support provider • Are there VE, VEX, or EX ports connected to the chassis? Yes or no. Use the switchShow command to determine the answer. • How large is the fabric? Use the nsAllShow command to determine the answer. • Do you have encryption blades or switches installed in the fabric? Yes or no. • Do you have Virtual Fabrics enabled in the fabric? Yes or no. Use the switchShow command to determine the answer.
Building a case for your switch support provider 1 • Are specific devices affected? - If so, what are their World Wide Number Names? • What happened prior to the problem? • Is the problem reproducible? - If so, what are the steps to reproduce the problem? • What configuration was in place when the problem occurred? • A description of the problem with the switch or the fault with the fabric.
1 Building a case for your switch support provider Gathering additional information The following features that require you to gather additional information. The additional information is necessary in order for your switch support provider to effectively and efficiently troubleshoot your issue. Refer to the chapter or document specified for the commands used for the data you must capture: • • • • • • 10 Configurations, refer to Chapter 3, “Connectivity”.
Chapter 2 General Troubleshooting In this chapter • Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Frame Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Switch message logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Frame Viewer Frame Viewer When a frame is unable to reach its destination due to timeout, it is discarded. You can use Frame Viewer to find out the flows that contained the dropped frames, which can help you determine which applications might be impacted. Using Frame Viewer, you can see exactly what time the frames were dropped. (Timestamps are accurate to within one second.) Additionally, this assists in the debug process.
Switch message logs 2 However, in this limited example, the Track Change feature reports this event inaccurately to the system message log; it appears that the login was successful. This scenario only occurs when the maximum number of users has been reached; otherwise, the login information displayed in the system message log reflects reality. Refer to the Fabric OS Administrator’s Guide for information regarding enabling and disabling Track Changes (TC).
2 Switch boot Switch boot Symptom The enterprise-class platform model rebooted again after an initial bootup. Probable cause and recommended action This issue can occur during an enterprise-class platform bootup with two CPs. If any failure occurs on the active CP, before the standby CP is fully functional and has obtained HA sync, the standby CP may not be able to take on the active role to perform failover successfully. In this case, both CPs reboot to recover from the failure.
Switch boot 2 • Software Fault: Kernel Panic - If the system detects an internal fatal error from which it cannot safely recover, it outputs an error message to the console, dumps a stack trace for debugging, and then performs an automatic reboot. - After a kernel panic, the system may not have enough time to write the reboot reason, causing the reboot reason to be empty. This is treated as a reset case.
2 FC-FC routing connectivity 3. Enter the supportSave command to go into interactive mode. Alternatively, if using a USB device, enter usbstorage -e. 4. Respond to the prompts. 5. Once the supportSave command had completed, contact your service support provider to provide them with the data. The following message is an example of the screen on a Brocade DCX. Fabos Version 7.1.
FC-FC routing connectivity 2 On the edge Fabric OS switch, make sure that the source and destination devices are properly configured in the LSAN zone before entering the fcPing command. This command performs the following functions: • Checks the zoning configuration for the two ports specified. • Generates an ELS ECHO request to the source port specified and validates the response. • Generates an ELS ECHO request to the destination port specified and validates the response.
2 FC-FC routing connectivity Example using fcPing with a single destination (in this example, the destination is a device node WWN) switch:admin> fcping 20:00:00:00:c9:3f:7c:b8 Destination: 20:00:00:00:c9:3f:7c:b8 Pinging 20:00:00:00:c9:3f:7c:b8 [0x370501] with 12 bytes of data: received reply from 20:00:00:00:c9:3f:7c:b8: 12 bytes time:825 usec received reply from 20:00:00:00:c9:3f:7c:b8: 12 bytes time:713 usec received reply from 20:00:00:00:c9:3f:7c:b8: 12 bytes time:714 usec received reply from 20:00:
FC-FC routing connectivity FIGURE 1 2 Superping and fcPing paths In the following example, Superping is invoked using the fcPing --allpaths command to destination domain 165. The following example displays each hop in (Domain1/Index1-> Domain2/Index2) format. To reach destination domain 165 from source domain 3 there are two unique end-to-end paths. In the first path, the frame traverses from egress port index 205 on source domain 3 to ingress port index 25 on domain 207.
2 FC-FC routing connectivity Consider the following example in which a few errors are recorded on ISLs 3/205-->2/25, 3/204-->2/27, 2/42-->101/3, and 2/1-->101/8. The potential faulty link is internal port 0/284 on domain 2 with the maximum of 100 percent failure.
FC-FC routing connectivity 2 Routing and statistical information The pathInfo command displays routing and statistical information from a source port index on the local switch to a destination port index on another switch. This routing information describes the full path that a data stream travels between these ports, including all intermediate switches. ATTENTION Using the pathInfo command when exchange-based routing is turned on can provide different paths with each attempt.
2 FC-FC routing connectivity Target port is Embedded Hop In Port Domain ID (Name) Out Port BW Cost ----------------------------------------------------------------------------0 2 1 (sw0) 6 4G 500 1 23 2 (sw0) 8 4G 500 2 4 3 (sw0) 3 4G 500 3 2 4 (sw0) 24 4G 10000 4 3 7 (switch_3) 2 4G 500 5 27 5 (switch_3) 24 Reverse path 6 24 7 2 8 24 9 3 10 8 11 6 (output truncated) 5 7 4 3 2 1 (switch_3) (switch_3) (sw0) (sw0) (sw0) (sw0) 27 3 2 4 23 2 4G 4G 4G 4G 4G - 500 500 500 10000 500 - For details about the
Chapter 3 Connectivity In this chapter • Port initialization and FCP auto-discovery process . . . . . . . . . . . . . . . . . . . . • Link issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Connection problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Link failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Marginal links . . . . . . . .
3 Port initialization and FCP auto-discovery process • VEX_Port—A virtual EX_Port. It connects a Fibre Channel router to an edge fabric. From the point of view of a switch in an edge fabric, a VEX_Port appears as a normal VE_Port. It follows the same Fibre Channel protocol as other VE_Ports. However, the router terminates VEX_Ports rather than allowing different fabrics to merge as would happen on a switch with regular VE_Ports. Figure 2 shows the process behind port initialization.
Link issues 3 Link issues Symptom Port LEDs are flashing. Probable cause and recommended action Depending on the rate of the flash and the color of the port LED, this could mean several things. To determine what is happening on either your port status LED or power status LED, refer to that switch’s model hardware reference manual. There is a table that describes the purpose of the LEDs and explains the current behavior as well as suggested resolutions. Symptom Port LEDs are steady.
3 Connection problems Checking the logical connection 1. Enter the switchShow command. 2. Review the output from the command and determine if the device successfully logged in to the switch. • A device that is logically connected to the switch is registered as an F_Port, L_Port, E_Port, EX_Port, VE_Port, VEX_Port, or N_Port. • A device that is not logically connected to the switch is registered as a G_Port or U_Port, if NPIV is not on the switch. 3.
Connection problems 3 Checking the Name Server 1.
3 Link failures 4. Enter the fcpProbeShow command to display the FCP probing information for the devices attached to the specified F_Port or L_Port. This information includes the number of successful logins and SCSI INQUIRY commands sent over this port and a list of the attached devices. 5. Check the port log to determine whether or not the device sent the FLOGI frame to the switch, and the switch probed the device.
Link failures 3 Checking for a loop initialization failure 1. Verify the port is an L_Port. a. Enter the switchShow command. b. Check the last field of the output to verify that the switch port indicates an L_Port. If a loop device is connected to the switch, the switch port must be initialized as an L_Port. c. Check to ensure that the state is online; otherwise, check for link failures.
3 Marginal links 4. Skip over the loop initialization phase. After becoming an active port, the port becomes an F_Port or an E_Port depending on the device on the opposite side. If the opposite device is a host or target device, the port becomes an F_Port. If the opposite device is another switch, the port becomes an E_Port. If there is a problem with the host or target device, enter portCfgGPort to force the port to try to come up as point-to-point only.
Marginal links 3 Only one frame is transmitted and received at any given time. An external cable is not required to run this test. The port LEDs flicker green rapidly while the test is running. Table 5 shows the different loopback modes you can use when using portLoopbackTest to test a marginal link.
3 Marginal links switch:admin> porterrshow frames tx rx enc in crc crc too too bad enc disc link loss loss frjt fbsy err g_eof shrt long eof out c3 fail sync sig ============================================================================ 0: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 665k 7.0k 0 0 0 0 0 0 0 0 0 0 0 0 0 0 78 60 12 4 0 0 0 0 0 0 0 0 0 0 0 0 665k 7.
Device login issues 3 Device login issues A correct login is when the port type matches the device type that is plugged in. In the following example, it shows that the device connected to Port 1 is a fabric point-to-point device and it is correctly logged in an F_Port. switch:admin> switchshow switchName:brcd5300 switchType:64.
3 Device login issues 3. Enter the portCfgShow command to see if the port is configured correctly. In some cases, you may find that the port has been locked as an L_Port and the device attached is a fabric point-to-point device such as a host or switch. This would be an incorrect configuration for the device and therefore the device cannot log in to the switch. To correct this type of problem, remove the Lock L_Port configuration using the portCfgDefault command.
Media-related issues 3 6. Enter the portLogDumpPort portid command where the port ID is the port number; then, view the device-to-switch communication. switch:admin> portlogdumpport 8 | more time task event port cmd args ------------------------------------------------Thu Nov 6 16:52:39 2008 16:52:39.066 PORT scn 8 1 00010004,4302000f,02000000 16:52:39.066 PORT scn 8 2 ce3dfab0,d9672800,00000002 16:52:39.066 PORT scn 8 2 ce3dfab0,d9672800,00000080 16:52:39.
3 Media-related issues The following procedures are for checking switch-specific components. Testing the external transmit and receive path of a port 1. Connect to the switch and log in as admin. 2. Connect the port you want to test to any other switch port with the cable you want to test. 3. Enter the portLoopbackTest -lb_mode 2 command. Testing the internal components of a switch 1. Connect to the switch and log in as admin. 2.
Segmented fabrics 3 Segmented fabrics Fabric segmentation is generally caused by one of the following conditions: • Incompatible fabric parameters (refer to “Reconciling fabric parameters individually” on page 37) • • • • • • • Incompatible zoning configuration (refer to Chapter 9, “Zoning”) Domain ID conflict (refer to “Reconciling fabric parameters individually” on page 37) Fabric ID conflict (refer to Chapter 7, “Virtual Fabrics”) Incompatible security policies Incorrect fabric mode Incorrect policy
3 Segmented fabrics 8. Enter the configure command to edit the appropriate fabric parameters for the segmented switch. 9. Enable the switch by entering the switchEnable command. Alternatively, you can reconcile fabric parameters by entering the configUpload command for each switch and upload a known-good configuration file. If you do this option, the two switches must be the same model.
Segmented fabrics 3 Example of setting the domain ID switch_89:FID89:admin> switchdisable switch_89:FID89:admin> configure Configure... Fabric parameters (yes, y, no, n): [no] y Domain: (1..239) [1] 89 WWN Based persistent PID (yes, y, no, n): [no] Allow XISL Use (yes, y, no, n): [yes] R_A_TOV: (4000..120000) [10000] E_D_TOV: (1000..5000) [2000] WAN_TOV: (0..30000) [0] MAX_HOPS: (7..19) [7] Data field size: (256..2112) [2112] Sequence Level Switching: (0..1) [0] Disable Device Probing: (0..
3 Port mirroring Port mirroring With port mirroring, you can configure a switch port to mirror the traffic between a specific source and destination port. This is only supported between F_Ports. This is a useful way to troubleshoot a problem port without bringing down the host and destination links to insert an inline analyzer. Port mirroring captures traffic between two devices. It mirrors only the frames containing the SID/DID to the mirror port.
Port mirroring 3 • Deleting a port mirroring connection with IOD enabled causes frame drop between two endpoints. • Using the firmware download procedure to downgrade to previous Fabric OS releases that do not support port mirroring requires that you remove all the port mirroring connections. If you downgrade to a previous version of Fabric OS, you cannot proceed until the mirroring connections are removed.
3 Port mirroring TABLE 8 Port mirroring platform supportability (Continued) Brocade Model Fabric OS v6.1.1_enc Fabric OS v6.3.0 Fabric OS v6.4.0 Fabric OS v7.1.0 FX8-24 Port mirroring is supported only on the FC ports. It is not supported over GbE ports/FCIP VE tunnels. Port mirroring is supported over GbE ports/FCIP VE tunnels. Port mirroring is supported over GbE ports/FCIP VE tunnels. Brocade 7800 Port mirroring is supported only on the FC ports.
Port mirroring TABLE 9 3 Maximum number of mirror connections (Continued) Model Maximum number of mirror connections (chassis-wide) FS8-18 3 FX8-24 3 Configuring a port to be a mirror port 1. Connect to the switch and log in using an account with admin permissions. 2. Enter the portCfg mirrorport [slot number/] port number --enable command. NOTE The enable command enables the port as a mirror port. The disable command disables the mirror port configuration. Adding a port mirror connection 1.
3 Port mirroring Displaying port mirror connections 1. Connect to the switch and log in using an account with admin permissions. 2. Enter the portMirror --show command.
Chapter Configuration 4 In this chapter • Configuration upload and download issues . . . . . . . . . . . . . . . . . . . . . . . . . 45 • Brocade configuration form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Configuration upload and download issues It is important to maintain consistent configuration settings on all switches in the same fabric because inconsistent parameters (such as inconsistent PID formats) can cause fabric segmentation.
4 Configuration upload and download issues • The FTP or SCP server’s IP address cannot be contacted. Verify that you can connect to the FTP server. Use your local PC to connect to the FTP server or ping the FTP server. Example of a successful ping C:\> ping 192.168.163.50 Pinging 192.168.163.50 with 32 bytes of data: Reply from 192.168.163.50: bytes=32 time=5ms TTL=61 Ping statistics for 192.168.163.
Configuration upload and download issues 4 • On a Virtual Fabrics-enabled switch, you do not have the chassis role permission set on your user account. Implement one change at a time, then issue the command again. By implementing one change at a time, you are able to determine what works and what does not work. Knowing which change corrected the problems help you to avoid this problem in future endeavors. Symptom The configuration download fails.
4 Brocade configuration form • Enter the configDownload command, without the -vf operand, to download the regular configuration data. This step does not cause a reboot. However, the configDownload command issues a notice that "A switch reboot is required for the changes to take effect." There is no reliable mechanism to determine, which parameters may or may not require a reboot.
Brocade configuration form TABLE 10 4 Brocade configuration and connection (Continued) Brocade configuration settings Value Chassis configuration option Management connections Serial cable tag Ethernet cable tag Configuration information Domain ID Switch name Ethernet IP address Ethernet subnet mask Total number of local devices (nsShow) Total number of devices in fabric (nsAllShow) Total number of switches in the fabric (fabricShow) Fabric OS Troubleshooting and Diagnostics Guide 53-1002930-01 49
4 50 Brocade configuration form Fabric OS Troubleshooting and Diagnostics Guide 53-1002930-01
Chapter 5 Firmware Download Errors In this chapter • Blade troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Firmware download issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Troubleshooting with the firmwareDownload command . . . . . . . . . . . . . . . • USB error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Considerations for downgrading firmware . . . . . .
5 Firmware download issues NOTE This message only appears with Fabric OS v7.1.0 and earlier versions. Symptom The blade is faulty (issue slotShow to confirm). Probable cause and recommended action If the port or application blade is faulty, enter the slotPowerOff and slotPowerOn commands for the port or application blade. If the port or application blade still appears to be faulty, remove it and re-insert it into the chassis.
Firmware download issues 5 Wait at least 15 minutes for the commit operation to complete, then use the firmwareShow command to verify the partitions are synchronized. In some older versions of firmware, the firmware commit operation may not be started automatically on the switch (or on the standby CP in the director). In this case, you can enter the firmwareCommit command manually on the switch (or on the standby CP in the director) to synchronize the partitions.
5 Firmware download issues Symptom Cannot download the requested firmware. Probable cause and recommended action The firmware you are trying to download on the switch is incompatible. Check the firmware version against the switch type. If the firmware is incompatible, retrieve the correct firmware version and try again. Example of error message SW3900:admin> firmwaredownload Server Name or IP Address: 192.168.126.115 User Name: userFoo File Name: /users/home/userFoo/firmware/v7.1.
Troubleshooting with the firmwareDownload command 5 Troubleshooting with the firmwareDownload command A network diagnostic script and preinstallation check is a part of the firmware download procedure. The script and preinstallation check performs troubleshooting and automatically checks for any blocking conditions. If the firmware download fails, refer to the Fabric OS Message Reference for details about error messages. Also refer to, “Considerations for downgrading firmware” on page 56.
5 USB error handling USB error handling Table 11 outlines how the USB device handles errors under specific scenarios and details what actions you should take after the error occurs. TABLE 11 USB error handling Scenario under which download fails Error handling Action An access error occurs during firmware download because the removal of the USB device, or USB device hardware failure, and so on. Firmware download times out and commit is started to repair the partitions of the CPUs that are affected.
Considerations for downgrading firmware 5 Upgrade to 7.2 is not allowed since base switch has R_RDY enabled ports. Please disable the R_RDY enabled ports in base switch using portcfgislmode command. Firmware upgrade to Fabric OS 7.2.0 or higher is not allowed when there are more than 4 chassis connected through Inter-Chassis Links (ICLs) and the Enterprise ICL (EICL) license is not installed in the system. Note that even with an EICL license installed, only 9 chassis are allowed to connect through ICLs.
5 Considerations for downgrading firmware Downgrade is not allowed because there are few ports other than the first octet of the blade/switch configured for 10G/N10 speeds.Please change the octet speed combo of those ports to 1 using "portcfgoctetspeedcombo" CLI and change their speeds using "portcfgspeed" CLI. Downgrade is not allowed because Monitoring and Alerting Policy Suite (MAPS) is enabled. Please disable MAPS using "mapsconfig --disable" before proceeding. Downgrade to pre-7.
Considerations for downgrading firmware 5 Blade types Where blades are incompatible with a firmware download, they must be removed or powered off before a firmware download begins, as noted in the following message. Message The FC10-6 (type 39) blade is not supported by the target firmware. Please use slotshow to find out which slot it is in and remove it first. Probable cause and recommended action The firmware download operation was attempting to upgrade a system to Fabric OS v7.2.
5 Considerations for downgrading firmware Platform The following system message pertains to switch features or fabric-wide settings that must be removed or disabled before downgrading the firmware. Message Downgrade is not allowed because VF is enabled. Please run "lscfg - -config" and "lscfg - -delete" commands to remove the non-default LS first, then run "fosconfig - -disable vf" to disable VF before proceeding.
Chapter 6 Security In this chapter • Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Device authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Protocol and certificate management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FIPS. . . . . . . . . . . . .
6 Device authentication Password recovery options Table 12 describes the options available when one or more types of passwords are lost. TABLE 12 Symptom Password recovery options Topic Solution If all the passwords are forgotten, what is the password recovery mechanism? Are these procedures non-disruptive recovery procedures? Contact your switch service provider. A non-disruptive procedure is available.
Protocol and certificate management 6 Protocol and certificate management This section provides information and procedures for troubleshooting standard Fabric OS security features such as protocol and certificate management. Symptom Troubleshooting certificates. Probable cause and recommended action If you receive messages in the browser or in a pop-up window when logging in to the target switch using HTTPS, refer to Table 13 for recommended actions you can take to correct the problem.
6 SNMP SNMP This section describes symptoms with associated causes and recommended actions for SNMP-related issues. Symptom SNMP management station server is unable to receive traps from fabric. Probable cause and recommended action There are several causes related to this generic issue. You must verify the following: • There are no port filters in the firewalls between the fabric and the SNMP management station.
Chapter 7 Virtual Fabrics In this chapter • General Virtual Fabrics troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fabric identification issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Logical Fabric issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Base switch issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Logical switch issues. . . . . . .
7 Fabric identification issues • Admin Domains are mutually exclusive with Virtual Fabrics. When Virtual Fabrics is enabled, all access control is based on the Virtual Fabrics context. • Traffic Isolation zones with no failover option are not supported in logical fabrics. TI zones defined in the base fabric for logical fabric traffic must allow failover. NOTE The configure command has a “Disable FID check” fabric parameter option, which can be used to disable the FID check for FICON logical switches.
Base switch issues Symptom 7 The switch with domain with firmware version has joined the FID fabric and may not be compatible with XISL use. Probable cause and recommended action This message indicates the specified switch in the logical fabric that is using XISLs is running an incompatible firmware version and must be upgraded to Fabric OS v6.2.0 or later. Base switch issues All logical switches in a fabric should have the same base switch attribute.
7 Logical switch issues Logical switch issues CAUTION When a logical switch is created, all configuration for the logical switch is set to factory defaults. When a logical switch is deleted, all configuration for the logical switch is deleted permanently and is not recoverable. Symptom The indicated slot is empty. Probable cause and recommended action You used the lsCfg command and an empty slot was specified. Re-issue the command with the appropriate slot number.
Switch configuration blade compatibility Symptom 7 A non-GE blade is within the slot range. Probable cause and recommended action You are attempting to configure a GE port on a slot that does not contain GE ports. Symptom A port or ports is already in the current switch. Probable cause and recommended action You may not move a port to the same switch. Symptom The maximum number of switches for this platform has been reached.
7 Gathering additional information Use the lsCfg –restore_slot_to_default command to correct the problem. Once the configuration discrepancy has been fixed, you may use slotPowerOff followed by slotPowerOn to recover.
Chapter 8 ISL Trunking In this chapter • Link issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 • Buffer credit issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Link issues This section describes trunking link issues that can come up and recommended actions to take to correct the problems. Symptom A link that is part of an ISL trunk failed.
8 Buffer credit issues • • • • • Trunking is not supported in switch interoperability mode. Port trunking is disabled. The port is not an E_Port. The port is not 2 Gbps, 4 Gbps, or 8 Gbps. The port connects to a switch other than the one you want. To correct this issue, connect additional ISLs to the switch with which you want to communicate. • The ports are not the same speed or they are not set to an invalid speed. Manually set port speeds to a speed supported on both sides of the trunk.
Chapter 9 Zoning In this chapter • Overview of corrective action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Segmented fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Zone conflicts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Gathering additional information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9 Segmented fabrics If you enter the cfgShow command to display information about all zones, the TI zones appear in the defined zone configuration only and do not appear in the effective zone configuration. 1. Connect to the switch and log in as admin. 2. Enter the zone --show command where .name is the name of the zone to be displayed. If the name is omitted, the command displays information about all TI zones in the defined configuration.
Zone conflicts Symptom 9 Zone conflict appears in logs and fabric is segmented. Probable cause and recommended action This issue is usually caused by incompatible zoning configurations. Verify the following is true: • The effective cfg (zone set) on each end of the segmented ISL is identical. • Any zone object with the same name has the same entries in the same sequence. Symptom Fabric segmentation is caused by a “configuration mismatch”.
9 Zone conflicts TABLE 14 Commands for debugging zoning (Continued) Command Function cfgDisable Disables the active (effective) configuration cfgEnable Use to enable and activate (make effective) the specified configuration. cfgSave Use to save changes to the zone configuration database. cfgTransAbort Use to abort the current zoning transaction without committing it. cfgTransShow Use to display the ID of the current zoning transaction.
Zone conflicts 9 Correcting a fabric merge problem quickly 1. Determine which switches have the incorrect zoning configuration; then, log in to the switches as admin. 2. Enter the switchDisable command on all problem switches. 3. Enter the cfgDisable command on each switch. 4. Enter the cfgClear command on each switch. 5. Enter the cfgSave command on each switch to commit the change. ATTENTION The cfgClear command clears the zoning database on the switch where the command is run. 6.
9 Zone conflicts If the zoneset members between two switches are not listed in the same order in both configurations, the configurations are considered a mismatch; this results in the switches being segmented in the fabric. For example: [cfg1 = z1; z2]is different from [cfg1 = z2; z1], even though the members of the configuration are the same. One simple approach to making sure that the zoneset members are in the same order is to keep the members in alphabetical order. Reordering the zone member list 1.
Zone conflicts 9 Round-trip min/avg/max = 1012/1136/1442 usec Pinging 21:00:00:20:37:25:ad:05 [0x211e8] with 12 bytes of data: Request rejected Request rejected Request rejected Request rejected Request rejected 5 frames sent, 0 frames received, 5 frames rejected, 0 frames timeout Round-trip min/avg/max = 0/0/0 usec switch:admin> The following example is sample output from the fcPing command in which one device accepts the request and another device does not respond to the request: switch:admin> fcping 0
9 Gathering additional information • If they are in the same zone, perform the following tasks: Enter the portCamShow command on the host port to verify that the target is present. Enter the portCamShow command on the target. Enter the nsZoneMember command with the port ID for the zoned devices on the host and target to determine whether the name server is aware that these devices are zoned together. 3. Resolve zoning conflicts by putting the devices into the same zoning configuration. 4.
Chapter Diagnostic Features 10 In this chapter • Fabric OS diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 • Diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 • Power-on self-test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 • Switch status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10 Power-on self-test To save a set of files that customer support technicians can use to further diagnose the switch condition, enter the supportSave command. The command prompts for an FTP server, packages the following files, and sends them to the specified server: • • • • The output of the supportShow command. Any core files, panic dumps or FFDC files that may have been generated. System message (RAS) logs. Other special feature logs. Refer to“Automatic trace dump transfers” on page 100.
Power-on self-test 10 INIT: version 2.78 booting INIT: Entering runlevel: 3 eth0: Link status change: Link Up. 100 Mbps Full duplex Auto (autonegotiation complete). INITCP: CPLD Vers: 0x95 Image ID: 0x19 uptime: 2008; sysc_qid: 0 Fabric OS (Paulsa45) Paulsa45 console login: 2005/03/31-20:12:42, [TRCE-5000], 0,, INFO, ?, trace:, trace_buffer.c, line: 1170 2005/03/31-20:12:42, [LOG-5000], 0,, INFO, SW4100_P45, Previous message repeat 1 time(s), trace_ulib.
10 Switch status Disabling POST A reboot is not required for diagDisablePost to take effect. NOTE Disabling POST is not recommended and should only be done on the advice of your customer support technician. 1. Connect to the switch and log in with a user account that has admin privileges with the chassis-role permission. 2. Enter the diagDisablePost command. This disables POST1 and POST2. Enabling POST A reboot is not required for diagEnablePost to take effect. 1.
Switch status 10 Viewing the overall status of the switch 1. Connect to the switch and log in as admin. 2. Enter the switchStatusShow command. ecp:admin> switchstatusshow Switch Health Report Switch Name: brcdDCXbb IP address:192.168.234.
10 Switch status TABLE 15 Switch summary information (Continued) Variable Definition switchWwn Switch World Wide Name (WWN) switchBeacon Switch beaconing state: On or Off zoning When Access Gateway mode disabled, the name of the active zone displays in parentheses. FC Router FC Router’s state: On or Off FC Router BB Fabric ID The backbone fabric ID for FC routing Table 16 lists the following additional properties displayed in the switch summary for Virtual Fabrics-enabled switches.
Using the spinFab and portTest commands 10 Displaying the uptime for a switch 1. Connect to the switch and log in as admin. 2. Enter the uptime command. ecp:admin> uptime 10:50:19 up 11 days, 6:28, 1 user, load average: 0.49, 0.53, 0.54 The uptime command displays the length of time the system has been in operation, the total cumulative amount of uptime since the system was first powered on, and the load average over the past one minute.
10 Using the spinFab and portTest commands TABLE 18 Port type support Port type Supported in v6.3.0 Supported in v6.4.0 Supported in v7.2.0 F_Ports connected to Brocade HBAs No Yes1 Yes ICL ports No No Yes F_Ports connected to Access Gateway No No Yes EX_Ports No No No Ports in an Access Gateway switch No No No 1. If you use the spinFab command to test F_Ports connected to Brocade HBAs, it is required that the firmware version on the HBA is v2.1.1 or later.
Using the spinFab and portTest commands 10 • Verify that the cables and SFPs are inserted properly. Remove and insert them again on both ends. • Verify that the failing local port is working when connected to another remote port. Similarly, check whether the failing remote port is working when connected to another local port. • Once the fault is isolated on either the local port or the remote port, replace the cable and SFPs connected to the local port and the remote ports.
10 Port information Enabling a port 1. Connect to the switch and log in using an account with admin permissions. 2. Enter the appropriate command based on the current state of the port and whether it is necessary to specify a slot number: • To enable a port that is disabled, enter the command portEnable portnumber or portEnable slotnumber/portnumber. • To enable a port that is persistently disabled, enter the command portCfgPersistentEnable portnumber or portCfgPersistentEnable slotnumber/portnumber.
Port information 10 port generation number: 14 portId: 020a00 portIfId: 4302000b portWwn: 20:0a:00:05:1e:41:4a:a5 portWwn of device(s) connected: 21:00:00:e0:8b:05:e0:b1 Distance: normal portSpeed: N2Gbps LE domain: 0 FC Fastwrite: OFF Interrupts: 0 Unknown: 0 Lli: 18 Proc_rqrd: 161 Timed_out: 0 Rx_flushed: 0 Tx_unavail: 0 Free_buffer: 0 Overrun: 0 Suspended: 0 Parity_err: 0 2_parity_err: 0 CMI_bus_err: 0 Link_failure: 0 Loss_of_sync: 3 Loss_of_sig: 6 Protocol_err: 0 Invalid_word: 563851 Invalid_crc: 0 D
10 Port information time_txcrd_z_vc 12-15: 0 er_enc_in 0 er_crc 0 er_trunc 0 er_toolong 0 er_bad_eof 0 er_enc_out 0 er_bad_os 0 er_c3_timeout 0 er_c3_dest_unreach 0 unreachable er_other_discard 0 er_type1_miss 0 er_type2_miss 0 er_type6_miss 0 er_zone_miss 0 er_lun_zone_miss 0 er_crc_good_eof 0 er_inv_arb 0 open 810 transfer 0 opened 409856 starve_stop 0 fl_tenancy 1715 nl_tenancy 331135 zero_tenancy 4 0 0 0 Encoding errors inside of frames Frames with CRC errors Frames shorter than minimum Frames longer
10 Equipment status 20: 6.3k 6.6k 0 21: 0 0 0 22: 0 0 0 23: 0 0 0 24: 0 0 0 25: 0 0 0 26: 0 0 0 27: 0 0 0 28: 0 0 0 29: 0 0 0 30: 664k 6.
10 Equipment status Checking the temperature, fan, and power supply 1. Log in to the switch as admin. 2. Enter the sensorShow command. Refer to the Fabric OS Command Reference for details regarding the sensor numbers. 3. Check the temperature output. Look for indications of high or low temperatures. 4. Check the fan speed output. If any of the fan speeds display abnormal RPMs, replace the fan FRU. 5. Check the power supply status.
System message log 10 The possible status values are: • • • • • OK—Power supply functioning correctly. Absent—Power supply not present. Unknown—Unknown power supply unit installed. Predicting failure—Power supply is present but predicting failure. FAULTY—Power supply is present but faulty (no power cable, power switch turned off, fuse blown, or other internal error). If any of the power supplies show a status other than OK, consider replacing the power supply as soon as possible.
10 Port log In the following message the identifier SLOT 6/1 means the message was generated from the slot 6 blade co-CPU. 2001/01/07-04:03:00, [SEC-1203], 2, SLOT 6/1 , | FFDC | CHASSIS, INFO, C08_1, Login information: Login successful via TELNET/SSH/RSH. IP Addr: 192.168.38.2050 Because RASlog supports Virtual Fabrics and logical switches, the FID (Fabric ID) displays on every RASlog message to identify the source of the logical switch that generates the message.
Port log 10 Viewing the port log 1. Connect to the switch and log in as admin. 2. Enter the portLogShow command: switch:admin> portlogshow time task event port cmd args ------------------------------------------------Fri Feb 22 16:48:45 2008 16:48:45.208 SPEE sn 67 NM 00000009,00000000,00000000 16:48:46.783 PORT Rx 64 40 02fffffd,00fffffd,02e2ffff,14000000 16:48:46.783 PORT Tx 64 0 c0fffffd,00fffffd,02e201bf,00000001 16:48:46.783 FCPH read 64 40 02fffffd,00fffffd,be000000,00000000,02e201bf 16:48:46.
10 Syslogd configuration 20:29:12.638 FCPH write 3 40 00fffffd,00fffffd,00000000,00000000,00000000 20:29:12.638 FCPH seq 3 28 00300000,00000000,000005f4,00020182,0000000 20:29:12.638 PORT Tx 3 40 02fffffd,00fffffd,09a5ffff,14000000 20:29:12.638 FCPH write 9 40 00fffffd,00fffffd,00000000,00000000,00000000 20:29:12.638 FCPH seq 9 28 00300000,00000000,000005f4,00020182,00000000 20:29:12.639 PORT Tx 9 40 02fffffd,00fffffd,09a6ffff,14000000 20:29:12.639 PORT Rx 3 0 c0fffffd,00fffffd,09a50304,00000001 20:29:12.
Syslogd configuration 10 Configuring the host Fabric OS supports a subset of UNIX-style message severities that default to the UNIX local7 facility. To configure the host, edit the /etc/syslog.conf file to map Fabric OS message severities to UNIX severities, as shown in Table 21.
10 Automatic trace dump transfers switch:admin> syslogdipshow syslog.IP.address.1080::8:800:200C:417A syslog.IP.address.1081::8:800:200C:417A syslog.IP.address.1082::8:800:200C:417A syslog.IP.address.4 10.1.2.4 syslog.IP.address.5 10.1.2.5 syslog.IP.address.6 10.1.2.6 Setting the facility level 1. Connect to the switch and log in as admin. 2. Enter the following command: switch:admin> syslogdfacility -l n The n variable is a number from 0 through 7, indicating a UNIX local7 facility. The default is 7.
Automatic trace dump transfers 10 After the setup is complete, you can run the supportSave -c command to save RASlog, TRACE, supportShow, core file, FFDC data and other diagnostic support information to the server without specifying server details. The following procedures describe the tasks for setting up automatic transfer. Specifying a remote server 1. Verify that the FTP service is running on the remote server. 2. Connect to the switch and log in as admin. 3.
10 102 Automatic trace dump transfers Fabric OS Troubleshooting and Diagnostics Guide 53-1002930-01
Appendix A Switch Type and Blade ID The switchType is a displayed field listed when you run the switchShow command. When you are gathering information to give to your switch support provider, you may be asked the switch model. If you do not know the model, refer to Table 22 to convert the switchType to a B-Series model number. switch:admin> switchshow switchName:Sprint5100 switchType:66.
A Switch Type and Blade ID TABLE 22 switchType to B-Series model converter (Continued) switchType B-Series switch model Base switch speed 67 Brocade Encryption Switch 8 Gb 16-port encryption switch 70 5410 8 Gb 12-port embedded switch 71 300 8 Gb 16-port switch 72 5480 8 Gb 24-port embedded switch 73 5470 8 Gb 20-port embedded switch 75 M5424 8 Gb 24-port embedded switch 77 Brocade DCX-4S 8 Gb 192-port core fabric backbone 83 7800 8 Gb 16-FC ports, 6 GbE ports extension switch
Switch Type and Blade ID 8 9 10 11 12 TABLE 23 CORE BLADE AP BLADE SW BLADE SW BLADE AP BLADE 52 43 37 55 75 CORE8 FS8-18 FC8-16 FC8-32 FX8-24 A ENABLED ENABLED ENABLED ENABLED ENABLED B-series blade model descriptions Blade ID B-series blade model Description 37 FC8-16 8 Gb 16-FC ports blade 51 FC8-48 8 Gb 48-FC ports blade 55 FC8-32 8 Gb 32-FC ports blade 68 FS8-18 8 Gb 16-port encryption blade 74 FCOE10-24 24-FC ports on an application blade that provides DCB to bridge a Fibre Ch
A 106 Switch Type and Blade ID Fabric OS Troubleshooting and Diagnostics Guide 53-1002930-01
Appendix Hexadecimal Conversion B Hexadecimal overview Hexadecimal, also known as hex, is a numeral system with a base of 16, usually written by means of symbols 0–9 and A–F (or a–f). Its primary purpose is to represent the binary code that computers interpret in a format easier for humans to remember. It acts as a form of shorthand, in which one hexadecimal digit takes the place of four binary bits.
B Decimal-to-hexadecimal conversion table Decimal-to-hexadecimal conversion table TABLE 24 108 Decimal-to-hexadecimal conversion table Decimal 01 02 03 04 05 06 07 08 09 10 Hex 01 02 03 04 05 06 07 08 09 0a Decimal 11 12 13 14 15 16 17 18 19 20 Hex 0b 0c 0d 0e 0f 10 11 12 13 14 Decimal 21 22 23 24 25 26 27 28 29 30 Hex 15 16 17 18 19 1a 1b 1c 1d 1e Decimal 31 32 33 34 35 36 37 38 39 40 Hex 1f 20 21 22 23 24 25 26 27
B Decimal-to-hexadecimal conversion table TABLE 24 Decimal-to-hexadecimal conversion table (Continued) Decimal 171 172 173 174 175 176 177 178 179 180 Hex ab ac ad ae af b0 b1 b2 b3 b4 Decimal 181 182 183 184 185 186 187 188 189 190 Hex b5 b6 b7 b8 b9 ba bb bc bd be Decimal 191 192 193 194 195 196 197 198 199 200 Hex bf c0 c1 c2 c3 c4 c5 c6 c7 c8 Decimal 201 202 203 204 205 206 207 208 209 210 Hex c9 ca cb cc cd ce cf d
B 110 Decimal-to-hexadecimal conversion table Fabric OS Troubleshooting and Diagnostics Guide 53-1002930-01
Index A account management lost password recovery options, 62 recovering forgotten passwords, 61 unable to modify switch settings, 62 user forgot password, 4 user unable to change switch settings, 5 B blade errors AP blade type 24 is inserted, 69 faulty, 3, 52 stuck in the ’LOADING’ state, 3, 52 browser troubleshooting certificates, 63 C certificates corrupt, 63 invalid, 63 not installed, 63 troubleshooting, 63 command output, 7 common problem areas, 2 symptoms, 2 configdownload fails, 3 configupload fai
F F_Port, 23, 30 fabric issues, 2 merge fails, 3 parameters, 37 parameters, reconcile, 37 segments, 3 fabric merge problem, 73 fabric segmentation configuration mismatch, 75 content mismatch, 75 default zone access, 77 fcPing, 78 Fibre Channel connectivity, 78 type mismatch, 75 zone configuration members, 77 zone conflict, 75 zoning problems, 79 fans, status of, 94 FCIP tunnel bounces, 3 tunnel does not come online, 3 tunnel does not form, 3 tunnel is sluggish, 3 fcping, 16 FCR is slowing down, 3 feature is
M M_Port, 23 marginal links, 2, 4 media-related issues functional tests, 35 structural tests, 35 message logs, 1 missing devices, 2 N Name Server, 27 Network Time Protocol, See NTP, 1 no connectivity between host and storage, 4 no connectivity between switches, 4 no light on LEDs, 4 NS, 27 NTP, 1 O port type E_Port, 23, 30 EX_Port, 23 F_Port, 23, 30 FL_Port, 23 G_Port, 23, 30 L_Port, 30 M_Port, 23 U_Port, 23 VE_Port, 23 VEX_Port, 24 portErrShow, 34 crc_err counter errors, 31 crc_g_eof counter errors, 31
structural tests, 35 superping tool, 18 supportSave, 5 supportSave timeout value, 6 switch configuration, 2 constantly reboots, 4 disabling port, 90 panic, 4 reboots during configup/download, 4 system status, 84 unable to join fabric, 4 switch message logs, 12 switch panic, 64 switch reboots during the configuration download, 47 switch status, viewing, 84 switchType, 103 symptoms, 2 synchronize switches, 1 syslog messages, 4 T targets, 2 temperature, fan, and power supply, 94 temperature, status of, 95 tes
