53-1002150-02 03 June 2011 Fabric OS Troubleshooting and Diagnostics Guide Supporting Fabric OS v7.0.
Copyright © 2008-2011 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron, SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and Brocade Network Advisor (formerly Data Center Fabric Manager or DCFM), Extraordinary Networks, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
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-1002150-02
Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . xvi What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Frame Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Switch message logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Switch boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Rolling Reboot Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4 Configuration In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Configuration upload and download issues . . . . . . . . . . . . . . . . . . . 45 Gathering additional information . . . . . . . . . . . . . . . . . . . . . . . . 48 Brocade configuration form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Chapter 5 Firmware Download Errors In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 8 ISL Trunking In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Link issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Buffer credit issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Getting out of buffer-limited mode . . . . . . . . . . . . . . . . . . . . . . . 74 Chapter 9 Zoning In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Checking the temperature, fan, and power supply . . . . . . . . . . 98 Checking the status of the fans . . . . . . . . . . . . . . . . . . . . . . . . . 99 Checking the status of a power supply. . . . . . . . . . . . . . . . . . . . 99 Checking temperature status . . . . . . . . . . . . . . . . . . . . . . . . . .100 System message log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x Fabric OS Troubleshooting and Diagnostics Guide 53-1002150-02
Figures Figure 1 Superping and fcPing paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Figure 2 Simple port initialization process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Figure 3 Example of a D_Port configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xii Converged Enhanced Ethernet Administrator’s Guide 53-1002163-01
Tables Table 1 Common troubleshooting problems and tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Table 2 Common symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Table 3 Environmental changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Table 4 SwitchShow output and suggested action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Table 5 Loopback modes . . .
xiv Converged Enhanced Ethernet Administrator’s Guide 53-1002163-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii • 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.0.0, documenting all possible configurations and scenarios is beyond the scope of this document.
Document conventions This section describes text formatting conventions and important notice formats used in this document.
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. NOTE A note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information. ATTENTION An Attention statement indicates potential damage to hardware or data.
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. Other industry resources For additional resource information, visit the Technical Committee T11 website.
• Brocade 300, 5100, and 5300 — On the switch ID pull-out tab located on the bottom of the port side of the switch. • Brocade 6510 — On the switch ID pull-out tab located inside the chassis on the port side on the left. • • • • Brocade 7800 and 8000 — On the bottom of the chassis. Brocade DCX Backbone — On the bottom right on the port side of the chassis. Brocade DCX-4S 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” 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” Configupload or download fails FTP or SCP server or USB availability Chapter 4, “Configuration” E_Port failed to come online Corr
1 Questions for common symptoms TABLE 2 Common symptoms (Continued) Symptom Areas to check Chapter or Document License issues Licensing Chapter 2, “General” LSAN is slow or times-out LSAN tagging Chapter 2, “General” 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 Administrator’s Guide No connectivity betwe
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 2. Type the appropriate supportSave command based on your needs: • If you are saving to an FTP or SCP server, use the following syntax: supportSave When invoked without operands, this command goes into interactive mode. The following operands are optional: -n Does not prompt for confirmation. This operand is optional; if omitted, you are prompted for confirmation. -c Uses the FTP parameters saved by the supportFtp command.
Building a case for your switch support provider 1 3. Set the utility to capture output from the screen. Some utilities require this step to be performed prior to opening up a session. Check with your utility vendor for instructions. 4. Type the command or start the process to capture the required data on the console. Capturing command output 1. Connect to the switch through a Telnet or SSH utility. 2. Log in using an account with admin permissions. 3.
1 Building a case for your switch support provider • • • • • • • Do you have IPsec installed on the switch’s Ethernet interface? Yes or no. Use the ipsecConfig --show command to determine the answer. Do you have Inband Management installed on the switches GigE ports? Yes or no. User the portShow iproute geX command to determine the answer. Are you using NPIV? Yes or no. Use the switchShow command to determine the answer.
Building a case for your switch support provider 1 • Host information: - OS version and patch level - HBA type - HBA firmware version - HBA driver version - Configuration settings • Storage information: - Disk/tape type - Disk/tape firmware level - Controller type - Controller firmware level - Configuration settings - Storage software (such as EMC Control Center, Veritas SPC, etc.) • If this is a Brocade DCX, DCX 8510 family, and DCX-4S enterprise-class platforms, are the CPs in-sync? Yes or no.
1 10 Building a case for your switch support provider Fabric OS Troubleshooting and Diagnostics Guide 53-1002150-02
Chapter 2 General 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 which flows contained the dropped frames, which in turn 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.) This also assists in the debug process.
Switch boot Symptom 2 MQ errors are appearing in the switch log. Probable cause and recommended action An MQ error is a message queue error. Identify an MQ error message by looking for the two letters MQ followed by a number in the error message: 2004/08/24-10:04:42, [MQ-1004], 218,, ERROR, ras007, mqRead, queue = raslog-test- string0123456-raslog, queue I D = 1, type = 2 MQ errors can result in devices dropping from the switch’s Name Server or can prevent a switch from joining the fabric.
2 Switch boot Rolling Reboot Detection A rolling reboot occurs when a switch or enterprise-class platform has continuously experienced unexpected reboots. This behavior is continuous until the rolling reboot is detected by the system. Once the Rolling Reboot Detection (RRD) occurs, the switch is put into a stable state so that a minimal supportSave can be collected and sent to your service support provider for analysis. Not every reboot activates the Rolling Reboot Detection feature.
Switch boot 2 This is an HA bootup-related issue and happens when switch is unable to recover to a stable state. HASM log contains more detail and specific information on this type of failure, such as one of the following: - Failover recovery failed: This occurs when failover recovery failed and has to reboot the CP. - Failover when LS trans incomplete: Takes place when a logical switch transaction is incomplete.
2 FC-FC routing connectivity * Fabric OS has detected frequent switch reboot condition. * * Following actions can be taken to recover the switch: * * - take off or replace the bad blades. * * - use supportsave to collect supportsave data. * * * * ************************************************************** Please change passwords for switch default accounts now. Use Control-C to exit or press 'Enter' key to proceed.
FC-FC routing connectivity 2 received reply from 0x60f00: 12 bytes time:430 usec received reply from 0x60f00: 12 bytes time:462 usec 5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout Round-trip min/avg/max = 430/467/506 usec Pinging 0x5f001 with 12 bytes of data: received reply from 0x5f001: 12 bytes time:2803 usec received reply from 0x5f001: 12 bytes time:2701 usec received reply from 0x5f001: 12 bytes time:3193 usec received reply from 0x5f001: 12 bytes time:2738 usec received reply
2 FC-FC routing connectivity Superping Superping refers to the fcPing --allpaths command which is a diagnostic tool used to test all least cost ISLs between a source and destination switch. When you run the command you are provided with a list of all available least cost paths from a source domain to a destination device. Superping isolates links with potential failures so that you can investigate these ISLs to determine the exact links.
FC-FC routing connectivity 2 In the following example, superping is invoked using the fcPing --allpaths command to destination domain 165. The following example displays each hop as (Domain1/Index1-> Domain2/Index2) format. To reach destination domain 165 from source domain 3 there are 2 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 Restrictions • Fabric reconfiguration cannot occur while using the superping tool. It is assumed that the fabric is stable before the fcPing --allpaths command is executed. • The control path for interswitch communication should be available, even if the data path for device to device communication may have resource starvation. • When executed in a fabric with trunk ports, only the trunk master index is output to the user i.e.
FC-FC routing connectivity 2 Target port is Embedded Hop In Port Domain ID (Name) Out Port BW Cost --------------------------------------------------------0 E 9 (web226) 2 1G 1000 1 3 10 (web229) 8 1G 1000 2 8 8 (web228) 9 1G 1000 3 6 91 (web225) E - To display basic and extended statistics in interactive mode: switch:admin> pathinfo Max hops: (1..127) [25] Fabric Id: (1..128) [-1] Domain|Wwn|Name: [] 8 Source port: (0..15) [-1] Destination port: (0..
2 FC-FC routing connectivity For details about the pathInfo command, refer to the Fabric OS Command Reference. Performance issues Symptom General slow-down in FCR performance and scalability. Probable cause and recommended action As LSAN zone databases get bigger, it takes more switch resources to process them. Use the enforce tag feature to prevent a backbone switch from accepting unwanted LSAN zone databases into its local database. Symptom Host application times out.
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 LEDs purpose and explains the current behavior as well as provides 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_, L_, E_, EX_, VE_, VEX_, or N_Port. • A device that is not logically connected to the switch is registered as a G_ or U_Port, if NPIV is not on the switch. 3.
Connection problems *N NL 3 021a00; 2,3;20:00:00:e0:69:f0:07:c6;10:00:00:e0:69:f0:07:c6; 895 Fabric Port Name: 20:0a:00:60:69:10:8d:fd 051edc; 3;21:00:00:20:37:d9:77:96;20:00:00:20:37:d9:77:96; na FC4s: FCP [SEAGATE ST318304FC 0005] NL Fabric Port Name: 20:0e:00:60:69:10:9b:5b 051ee0; 3;21:00:00:20:37:d9:73:0f;20:00:00:20:37:d9:73:0f; na FC4s: FCP [SEAGATE ST318304FC 0005] NL Fabric Port Name: 20:0e:00:60:69:10:9b:5b 051ee1; 3;21:00:00:20:37:d9:76:b3;20:00:00:20:37:d9:76:b3; na FC4s: FCP [SEAGATE ST3
3 Link failures Link failures A link failure occurs when a server, storage, or switch device is connected to a switch, but the link between the devices does not come up. This prevents the devices from communicating to or through the switch. If the switchShow command or LEDs indicate that the link has not come up properly, use one or more of the following procedures. The port negotiates the link speed with the opposite side.
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 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. Correcting a port that has come up in the wrong mode 1. Enter the switchShow command. 2.
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 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 into the switch. To correct this type of problem, remove the Lock L_Port configuration using the portCfgDefault command.
Media-related issues 3 ------------------------------------------------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.066 PORT scn 8 5 00000000,00000000,00000002 16:52:39.066 PORT scn 8 1 00010004,4302000f,00000002 16:52:39.066 PORT scn 8 1 00010004,4302000f,02000000 16:52:39.071 PORT ioctl 88010004 1,0 * 4 16:52:42.
3 Segmented fabrics Testing a port’s external transmit and receive path 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 a switch’s internal components 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.
Segmented fabrics • • • • • • • 3 Incompatible zoning configuration (see Chapter 9, “Zoning”). Domain ID conflict (see “Reconciling fabric parameters individually” on page 37). Fabric ID conflict (see Chapter 7, “Virtual Fabrics”). Incompatible security policies. Incorrect fabric mode. Incorrect policy distribution. Incompatible software features. There are a number of settings that control the overall behavior and operation of the fabric.
3 Segmented fabrics Downloading a correct configuration You can restore a segmented fabric by downloading a previously saved correct backup configuration to the switch. Downloading in this manner reconciles any discrepancy in the fabric parameters and allows the segmented switch to rejoin the main fabric. For details on uploading and downloading configurations, refer to the Fabric OS Administrator’s Guide.
Port mirroring 3 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..1) [0] Suppress Class F Traffic: (0..1) [0] Per-frame Route Priority: (0..1) [0] Long Distance Fabric: (0..1) [0] BB credit: (1..
3 Port mirroring Port mirroring captures traffic between two devices. It mirrors only the frames containing the SID/DID to the mirror port. Because of the way it handles mirroring, a single mirror port can mirror multiple mirror connections. This also means that the port cannot exceed the maximum bandwidth of the mirror port.
Port mirroring 3 • If you have NPIV or 10-bit address mode enabled on a Brocade 300, 5300, 5410, 5450, 5460, 5470, 5480, 7800, and the M5424 platforms, all devices from the same NPIV port or 10-bit addressing mode hit the same mirror connection, regardless of different AL_PAs, since the validation is done only for the first 16-bits of the SID/DID. • Port mirroring is not supported for the shared area ports of 48-port blades in the default switch.
3 Port mirroring Maximum mirror connections Table 9 shows the maximum number of mirror connections you can add to a mirror port.
Port mirroring 3 The configuration database keeps information about the number of port mirror connections configured on a switch, the number of chunks of port mirroring data that are stored, and the chunk number. When removing a mirror connection, always use this method to ensure that the data is cleared. Deleting a connection removes the information from the database. Deleting a port mirror connection 1. Connect to the switch and log in using an account with admin permissions. 2.
3 44 Port mirroring Fabric OS Troubleshooting and Diagnostics Guide 53-1002150-02
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.163.163.50 Pinging 192.163.163.50 with 32 bytes of data: Reply from 192.163.163.50: bytes=32 time=5ms TTL=61 Ping statistics for 192.163.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 Probable cause and recommended action Verify that the switch was rebooted by checking the system log. If you are doing this on a enterprise-class platform, verify that both CPs rebooted by checking the system log. If any error occurs during the download, such as an error about a particular key, it is important to issue the configDefault command and attempt to repeat the configDownload command.
Brocade configuration form TABLE 10 4 Brocade configuration and connection (Continued) Brocade configuration settings Value 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-1002150-02 49
4 50 Brocade configuration form Fabric OS Troubleshooting and Diagnostics Guide 53-1002150-02
Chapter 5 Firmware Download Errors In this chapter • Blade troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Firmware download issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Troubleshooting the firmwareDownload command . . . . . . . . . . . . . . . . . . . • USB error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Considerations for downgrading firmware . . . .
5 Firmware download issues 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. Symptom The AP blade is stuck in the “LOADING” state (issue slotShow to confirm).
Firmware download issues Symptom 5 Firmware download times out. Probable cause and recommended action This can be caused by an excessively slow network. If it takes more than 30 minutes to download firmware on a switch, or on each CP in a director, the firmware download process times out. If a timeout occurs on a switch, the firmware download process synchronizes the two partitions on the switch by starting a firmware commit operation.
5 Firmware download issues Password: Server IP: 192.126.168.115, Protocol IPv4 Checking system settings for firmwaredownload... Firmware access timeout. The server is inaccessible or firmware path is invalid. Please make sure the server name or IP address, the user/password and the firmware path are valid. Symptom Cannot download the requested firmware. Probable cause and recommended action The firmware you are trying to download on the switch is incompatible.
Troubleshooting the firmwareDownload command 5 Troubleshooting the firmwareDownload command A network diagnostic script and preinstallation check is a part of the firmwareDownload 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 see, “Considerations for downgrading firmware” on page 56.
5 Considerations for downgrading firmware TABLE 11 USB error handling Scenario under which download fails Error handling Action An access error occurs during firmwaredownload because the removal of the USB device, or USB device hardware failure, etc. Firmwaredownload times out and commit isisstarted to repair the partitions of the CPUs that are affected. See previous table for details. None. USB device is not enabled.
Considerations for downgrading firmware 5 File Name: /home/userfoo/v6.3.0 Network Protocol (1-auto-select, 2-FTP, 3-SCP) [1]: Password: Checking System Settings... Version compatibility check passed. Checking version compatibility... Version compatibility check passed.. The following items must be addressed before downloading the specified firmware: Downgrade is not allowed because there are more than 2 FX8-24 blades plugged in to the chassis. The limit after downgrade is 2.
5 Considerations for downgrading firmware IPSec on FCIP tunnels requires version v6.3.1 or higher for 7800, and v7.0.0 or higher for FX8-24. Please use "portcfg fciptunnel" to disable IPSec for all FCIP tunnels and try again. Downgrade is not allowed because Persistent PID is enabled. Please use "ag --persistentpidenable 0" to disable the feature before downgrading. Downgrade is not allowed because one or more ports are locked as E-port.Please use "portcfgeport" CLI to remove the lock.
Considerations for downgrading firmware Message 5 The FS8-18 (type 43) 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 downgrade a system to Fabric OS v6.1.1_enc or earlier with one or more Brocade FC8-18 AP blades (blade ID 43) in the system. Brocade Encryption Blade FC8-18 AP blades are not supported on firmware v6.1.
5 Considerations for downgrading 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. Probable cause and recommended action You cannot downgrade because Virtual Fabrics are enabled. Delete the logical switches, delete the base switch, and disable Virtual Fabrics prior to downgrading the firmware.
Chapter 6 Security In this chapter • Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Device authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Protocol and certificate management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FIPS. . . . . . . . . . . . .
6 Device authentication Symptom Unable to log into the boot PROM. Probable cause and recommended action To recover a lost boot PROM password, contact your switch service provider. You must have previously set a recovery string to recover the boot PROM password. This does not work on lost or forgotten passwords in the account database. Password recovery options Table 12 describes the options available when one or more types of passwords are lost.
Protocol and certificate management Symptom 6 Switch is unable to form an F_Port. Probable cause and recommended action Regardless of the device authentication policy mode on the switch, the F_Port is disabled if the DH-CHAP protocol fails to authenticate. If the HBA sets the FC-SP bit during FLOGI and the switch sends a FLOGI accept with FC-SP bit set, then the switch expects the HBA to start the AUTH_NEGOTIATE.
6 SNMP • If you think it may be related to E_Port authentication then collect a supportSave -n from both switches of the affected E_Port. • If you think this is a policy-related issue, FCS switch or other security server-related issue then use supportSave -n to collect data from the Primary FCS switch and all affected switches.
FIPS 6 The results of all self-tests, for both power-up and conditional, are recorded in the system log or are output to the local console. This includes logging both passing and failing results. If the tests fail on your switch it constantly reboots. Because boot PROM access is disabled you are not able to exit out of the reboot. You must send the switch back to your switch service provider for repair.
6 66 FIPS Fabric OS Troubleshooting and Diagnostics Guide 53-1002150-02
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 • VE_Ports cannot exist in a logical switch that has XISL use turned on. Although VE_Ports are allowed in a base switch, Fabric OS v6.2.0 and later do not support the use of VE_Ports to carry traffic for logical fabrics using XISLs. They can be used to carry FCR traffic through EX_ and VEX_Ports. You should make sure your configuration does not result in the use of VE_Ports in a base switch for logical fabric traffic.
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 using XISLs is running an incompatible firmware version and must be upgraded to Fabric OS v6.2.0. 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. Reissue the command with the appropriate slot number.
Switch configuration blade compatibility Symptom 7 Unable to remove ports from their current switch. Probable cause and recommended action When moving ports to a switch, they are first removed from the switch in which they reside. This error message is displayed if this step fails. Symptom 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.
7 Gathering additional information Gathering additional information For Virtual Fabrics-related issues, use the following guidelines to gather additional data for your switch support provider: • Perform the supportSave command. • If not sure about the problem area, perform the supportSave command on all chassis and logical switches in the fabric. • If you think it may be related to E_Port authentication, then perform the supportSave -n command on both switches or logical switches of the affected E_Port.
Chapter 8 ISL Trunking In this chapter • Link issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 • Buffer credit issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 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 it to. 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. zone --show [name] where: name 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 are 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 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 Changing the default zone access A switch is not allowed to merge with another switch that has an active effective configuration if the default zone is set to “no access”. Before the switch can join, the default zone setting has to be set to "all access". When the default zone no access option is enabled and the active configuration is disabled by using the cfgDisable command, a special hidden configuration with no members is activated.
9 Zone conflicts Checking for Fibre Channel connectivity problems Enter the fcPing command (refer to the Fabric OS Command Reference for more information on this command), which checks the zoning configuration for the two ports specified by: • Generates an Extended Link Service (ELS) frame 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.
Zone conflicts 9 received reply from 0x020800: 12 bytes time:1006 usec received reply from 0x020800: 12 bytes time:1008 usec received reply from 0x020800: 12 bytes time:1038 usec received reply from 0x020800: 12 bytes time:1010 usec 5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout Round-trip min/avg/max = 1006/1044/1159 usec Pinging 22:00:00:04:cf:75:63:85 [0x217d9] with 12 bytes of data: Request timed out Request timed out Request timed out Request timed out Request timed out 5 frame
9 Gathering additional information Gathering additional information Collect the data from a supportSave -n command. Then collect the data from the cfgTransShow command. For the port having the problem, collect the data from the filterPortShow command.
Chapter Diagnostic Features 10 In this chapter • About Fabric OS diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 • Diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 • Power-on self test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 • Switch status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10 Power-on self test Most information can be captured using the supportSave command and downloaded by FTP off the switch, but when you are collecting information from specialized commands, such as supportShow, this information has to be captured using a Telnet client. To save a set of files that customer support technicians can use to further diagnose the switch condition, enter the supportSave command.
Power-on self test 10 modprobe: modprobe: Can't open dependencies file /lib/modules/2.4.19/modules.dep (No such file or directory) 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.
10 Switch status Disabling POST A reboot is not required for this command to take effect. 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 this command to take effect. 1. Connect to the switch and log in with a user account that has admin privileges with the chassis-role permission. 2.
Switch status Faulty ports monitor Missing SFPs monitor 10 HEALTHY HEALTHY All ports are healthy For more information on how the overall switch status is determined, refer to the switchStatusPolicySet command in the Fabric OS Command Reference.
10 Switch status The switchShow command also displays the following information for ports on the specified switch: TABLE 17 switchShow command output Variable Definition Index Index follows Area up to 255. Then it continues to the maximum port of the platform. Index identifies the port number relative to the switch. Index column is only displayed on enterprise-class platforms. Slot Slot number 1-4 and 7-10. Port Port number 0-15, 0-31 or 0-47. Address The 24-bit Address Identifier.
Using the SpinFab and portTest commands 10 Using the SpinFab and portTest commands The spinFab command is an online diagnostics command to verify the ISL links between switches at the maximum speed. It is done by setting up the routing functionality in the hardware such that the test frames received by E_Port are retransmitted on the same E_Port. Several frames are then sent to the port attached to each active E_Port specified.
10 Using the SpinFab and portTest commands Link errors Once the frame is sent out of the port, the spinFab command monitors the link errors in the ASIC. If any of the error counters are non-zero, spinFab reports ERROR and the test fails on the port.
Using the SpinFab and portTest commands 10 Tx/Rx errors Following errors are seen when the port fails to transmit or receive the frames. ERROR: DIAG PORTSTOPPED spinfab:spinfab, 0 nMegs, Pt7/2(2) Ch0/2 No Longer Transmitting, FTX Counter Stuck at 116295726, ERROR: DIAG TIMEOUT spinfab:spinfab, pass 2, Pt0/17(7) Ch0/7 Receive Error/Timeout The following are debugging procedures: • Check whether the same port is reporting Link Errors as discussed in “Link errors” on page 90.
10 Diagnostic Port • To disable a port that is persistently enabled, enter the command portCfgPersistentDisable portnumber or portCfgPersistentDisable slotnumber/portnumber. Diagnostic Port Fabric OS v7.0.0 allows you to convert a fibre channel port, including ISLs and loopback ports, into a Diagnostic Port (D_Port). This port lets you isolate the inter-switch link (ISL) to diagnose link level faults.
Diagnostic Port 10 For complete information on the portdporttest and portcfgdport commands, refer to the Fabric OS Command Reference. NOTE These tests can be run on EX_Ports by using the portcfgexport command to enable and disable the EX_Ports. For detailed information on the portcfgexport command, refer to the Fabric OS Command Reference. To configure a D_Port diagnostics session, perform the following steps. 1. Disable Port 1 on Switch A, shown in Figure 3, using the portdisable 1 command.
10 Diagnostic Port Remote WWNN: 10:00:00:05:33:13:2f:b5 Remote port: 2 Mode: Automatic Start time: Wed Feb 2 01:41:43 2011 End time: Wed Feb 2 01:43:23 2011 Status: RESPONDER ============================================================================= Test Start time Result EST(secs) Comments ============================================================================= Electrical loopback 01:42:08 PASS ----------Optical loopback 01:42:16 RESPONDER -See remote port results Link traffic test 01:43:15 RESPO
Port information 10 D_Port limitations The D_Port state and test data is not synchronized between the ports. If one of the switches has a failover, the D_Port link goes though re-initialization. If the remote switch is in final state after reboot or failover, the D_Port tries to automatically start the test. However, the test cannot proceed as the other port is already in the final state. When the remote port is in stable state, the test terminates with the error "Remote port is not ready".
10 Port information 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 Delim_err: 0 Address_err: 0 Lr_in: 3 Lr_out: 0 Ols_in: 0 Ols_out: 3 Frjt: Fbsy: 0 0 Port part of other ADs: No Refer to the Fabric OS Command Reference for additional portShow comman
10 Port information er_c3_dest_unreach unreachable er_other_discard er_type1_miss er_type2_miss er_type6_miss er_zone_miss er_lun_zone_miss er_crc_good_eof er_inv_arb open transfer opened starve_stop fl_tenancy nl_tenancy zero_tenancy 0 Class 3 frames discarded due to destination 0 0 0 0 0 0 0 0 810 0 409856 0 1715 331135 4 Other discards frames with FTB type 1 miss frames with FTB type 2 miss frames with FTB type 6 miss frames with hard zoning miss frames with LUN zoning miss Crc error with good eof
10 Equipment status 28: 0 0 0 29: 0 0 0 30: 664k 6.7k 0 31: 12 4 0 (output truncated) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 3 0 0 0 0 0 0 0 0 0 0 1 1 1 1 2 2 0 0 0 0 0 0 0 0 The portErrShow command output provides one output line per port. See Table 19 for a description of the error types.
Equipment status 10 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. If any power supplies show a status other than OK, consider replacing the power supply as soon as possible. Checking the status of the fans 1. Connect to the switch and log in as admin. 2.
10 System message log If any of the power supplies show a status other than OK, consider replacing the power supply as soon as possible. For certain switch models, the OEM serial ID data displays after each power supply status line. Checking temperature status 1. Connect to the switch and log in as admin. 2.
Port log 10 The FID can be a number from 0 to 128, and the identifier CHASSIS depends on the instance that generates the message and that it was generated by a chassis instance. The identifier FID 128 means the message was generated by the default switch instance. 2008/08/01-00:19:44, [LOG-1003], 1, SLOT 6 | CHASSIS, INFO, Silkworm12000, The log has been cleared. 2008/09/08-06:52:50, [FW-1424], 187, SLOT 6 | FID 128, WARNING, Switch10, Switch status changed from HEALTHY to DOWN.
10 Port log 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.783 FCPH seq 64 28 22380000,02e201bf,00000c1e,0000001c,00000000 16:48:46.
Syslogd configuration 20:29:20.804 20:29:20.805 20:29:20.805 20:29:20.805 20:29:20.805 20:29:20.806 20:29:20.806 20:29:20.806 20:29:32.638 20:29:32.638 20:29:32.638 20:29:32.638 PORT PORT FCPH FCPH PORT PORT FCPH FCPH FCPH FCPH PORT FCPH 20:29:32.638 FCPH 20:29:32.
10 Syslogd configuration local7.info local7.debug /var/adm/swinfo /var/adm/debug7 If you prefer to map Fabric OS severities to a different UNIX local7 facility level, see “Setting the facility level” on page 104. Configuring the switch Configuring the switch involves specifying syslogd hosts and, optionally, setting the facility level. You can also remove a host from the list of syslogd hosts. Specifying syslogd hosts 1. Connect to the switch and log in as admin. 2.
Automatic trace dump transfers 10 3. Verify the IP address was deleted using the syslogdIpShow command. Automatic trace dump transfers You can set up a switch so that diagnostic information is transferred automatically to a remote server. If a problem occurs, you can then provide your customer support representative with the most detailed information possible. To ensure the best service, you should set up for automatic transfer as part of standard switch configuration, before a problem occurs.
10 Automatic trace dump transfers Saving comprehensive diagnostic files to the server 1. Connect to the switch and log in as admin. 2. Enter the supportSave -c command and respond to the prompts. switch:admin> supportsave -c This command will collect RASLOG, TRACE, supportShow, core file, FFDC data and other support information and then transfer them to a FTP/SCP server or a USB device. This operation can take several minutes.
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, you can use this chart 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 switchType to B-Series model converter (Continued) B-Series switch model ASIC Base switch speed 67 Brocade Encryption Switch Condor2 8 Gb 16-port encryption switch 69 5410 GoldenEye2 8 Gb 12-port embedded switch 71 300 GoldenEye2 8 Gb 16-port switch 72 5480 GoldenEye2 8 Gb 24-port embedded switch 75 M5424 GoldenEye2 8 Gb 24-port embedded switch 76 8000 Condor2 8 Gb 16-FC port, 10 GbE 8-Ethernet port switch 77 Brocade DCX-4S Condo
Appendix B Hexadecimal Hexadecimal overview Hexadecimal, also known as hex, is a numeral system with a base of 16, usually written using unique 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 Hexadecimal overview TABLE 24 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 28 Decimal 41 42 43 44 45 46 47 48 49 50 Hex 29 2a 2b 2c 2d 2e 2f 30 31 32 Decimal
Hexadecimal overview TABLE 24 B Decimal to Hex conversion table (Continued) Hex b5 b6 b7 b8 b9 ba bb bc bd be Decimal 191 192 193 194 195 196 197 198 199 200 bf c0 c1 c2 c3 c4 c5 c6 c7 c8 201 202 203 204 205 206 207 208 209 210 c9 ca cb cc cd ce cf d0 d1 d2 Decimal 211 212 213 214 215 216 217 218 219 220 Hex d3 d4 d5 d6 d7 d8 d9 da db dc 221 222 223 224 225 226 227 228 229 230 dd de df e0 e1 e2 e3 e4 e5 e6 231
B 112 Hexadecimal overview Fabric OS Troubleshooting and Diagnostics Guide 53-1002150-02
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, 71 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
EX_Ports, 3, 23 F F_Port, 23, 30 fabric issues, 2 merge fails, 3 parameters, 37 parameters, reconcile, 37 segments, 3 fabric merge problem, 75 fabric segmentation configuration mismatch, 77 content mismatch, 77 default zone access, 79 fcPing, 80 Fibre Channel connectivity, 80 type mismatch, 77 zone configuration members, 79 zone conflict, 77 zoning problems, 81 fans, status of, 99 FCIP tunnel bounces, 3 tunnel does not come online, 3 tunnel does not form, 3 tunnel is sluggish, 3 FCR is slowing down, 3 feat
L P L_Port, 30 LEDs flashing, 3 no light, 4 steady, 3 License issues, 4 licensing issues, 11 link intermittent connectivty, 3 marginal, 4 no port LED light, 25 port LEDs flashing, 25 port LEDs steady, 25 logical connection, 26 loop initialization failure, 29 LSAN is slow or times-out, 4 passwords, recovering forgotten, 61 pathInfo, 20 performance problems, 4 PLOGI, 24 POD enabling ports, 91 point-to-point initialization failure, 29 port, 91 bypassed, 30 disabled, 30 enabling, 91 in wrong mode, 30 initial
resolving zone conflicts, 77 Rolling Reboot Detection, 14 S SCSI retry errors, 4 timeout errors, 4 security, gathering additional information, 63 segmentation, 3 segmented fabrics, 36, 76 setting up automatic trace dump transfers, 105 slow-down in FCR performance, 22 SNMP gathering additional information, 64 management server unable to receive traps, 64 SSL, 63 storage devices, 2 management applications, 2 structural tests, 35 superping tool, 18 supportSave, 5 supportSave timeout value, 6 switch configurat
Z zone configuration, 2 configuration mismatch, 5 content mismatch, 5 resolving conflicts, 77 troubleshooting, 77 type mismatch, 5 Fabric OS Troubleshooting and Diagnostics Guide 53-1002150-02 117
118 Fabric OS Troubleshooting and Diagnostics Guide 53-1002150-02