53-1000853-01 12 March 2008 Fabric OS Troubleshooting and Diagnostics Guide Supporting Fabric OS v6.1.
Copyright © 2008 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, Fabric OS, File Lifecycle Manager, MyView, and StorageX are registered trademarks and the Brocade B-wing symbol, DCX, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners.
Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . x What’s new in this document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switch Message Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Checking fan components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Checking the switch temperature. . . . . . . . . . . . . . . . . . . . . . . . 13 Checking the power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Checking the temperature, fan, and power supply . . . . . . . . . . 13 Fibre Channel Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting firmwareDownload . . . . . . . . . . . . . . . . . . . . . . . . . 41 Gathering additional information . . . . . . . . . . . . . . . . . . . . . . . . 41 Brocade DCX error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 USB error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Considerations for downgrading firmware . . . . . . . . . . . . . . . . . . . . 44 Preinstallation messages . . . . . . . . . . . . . . . . . . . .
Chapter 9 FCIP Issues In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 FCIP tunnel issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 FCIP links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Gathering additional information . . . . . . . . . . . . . . . . . . . . . . . . 72 Port mirroring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Port information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Viewing the status of a port . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Displaying the port statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Displaying a summary of port errors for a switch . . . . . . . . . . . 98 Equipment status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Displaying the status of the fans . . . . . . . . . . . . .
viii Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi • Additional information. . . . . . . . . . .
• Chapter 11, “iSCSI Issues,” provides information and procedures specific to Brocade 48000 and Brocade DCX models. Because these models have CP blades that support the iSCSI feature. • Chapter 12, “Working With Diagnostic Features,” provides procedures for use of the Brocade Adaptive Networking suite of tools, including Traffic Isolation, QoS Ingress Rate Limiting, and QoS SID/DID Traffic Prioritization. • The appendices provide special information to guide you in understanding switch output.
Document conventions This section describes text formatting conventions and important notice formats used in this document.
Key terms For definitions specific to Brocade and Fibre Channel, see the Brocade Glossary. For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary at: http://www.snia.org/education/dictionary Additional information This section lists additional Brocade and industry-specific documentation that you might find helpful. Brocade resources To get up-to-the-minute information, join Brocade Connect. It’s free! Go to http://www.brocade.
Getting technical help Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available: 1.
For the Brocade 4016, 4018, 4020, and 4024 embedded switches: Provide the license ID. Use the licenseIdShow command to display the WWN. Document feedback Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Forward your feedback to: documentation@brocade.
Chapter 1 Introduction to Troubleshooting This chapter provides information on troubleshooting and the most common procedures to use to diagnose and recover from problems. This book is a companion guide to be used in conjunction with the Fabric OS Administrator’s Guide. Although it provides a lot of common troubleshooting tips and techniques it does not teach troubleshooting methodology. In this chapter • About troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 BadRootDev errors Firmware versions on switch Chapter 5, “FirmwareDownload Errors” Blade is faulty Firmware or application download Hardware Chapter 2, “General Issues” Chapter 5, “FirmwareDownload Errors” Blade is stuck in the “LOADING” state Firmware or application download Chapter 5, “FirmwareDownload Errors” Configupload or download fails FTP or SCP server or USB availability Chapter 4, “Configuratio
1 TABLE 2 Questions for common symptoms Common symptoms Symptom Areas to check Chapter SCSI retry errors Buffer credits FCIP tunnel bandwidth Chapter 9, “FCIP Issues” SCSI timeout errors Links HBA Buffer credits FCIP tunnel bandwidth Chapter 3, “Connections Issues” Chapter 7, “ISL Trunking Issues” Chapter 9, “FCIP Issues” Switch constantly reboots FIPS Chapter 6, “Security Issues” Switch is unable to join fabric Security policies Zoning Fabric parameters Chapter 3, “Connections Issues” Swi
Gathering information for your switch support provider 1 Gathering information for your switch support provider If you are troubleshooting a production system, you must gather data quickly. As soon as a problem is observed, perform the following tasks (if using a dual CP system, run the commands on both CPs). For more information about these commands and their operands, refer to the Fabric OS Command Reference. 1.
1 Gathering information for your switch support provider Capturing a supportSave 1. Connect to the switch and log in using an account assigned to the admin role. 2. Type the supportSave command. 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 Building a case for your switch support provider The following form should be filled out in its entirety and presented to your switch support provider when you are ready to contact them. Having this information immediately available will expedite the information gathering process that is necessary to begin determining the problem and finding a solution. Basic switch information 1.
1 Building a case for your switch support provider • • • • • • What happened prior to the problem? Is the problem reproducible? If so, what are the steps to produce 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.
Building a case for your switch support provider 1 Gathering additional information Below are 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 specified for the commands whose data you need to capture. • • • • • • Configurations, see Chapter 3, “Connections Issues”. Firmwaredownload, see Chapter 5, “FirmwareDownload Errors”.
1 10 Building a case for your switch support provider Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01
Chapter 2 General Issues This chapter provides information on troubleshooting and the most common procedures to use to recover from licensing and common switch log errors. In this chapter • Licensing issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Switch Message Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Fibre Channel Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Switch Message Logs Symptom Inaccurate information in the system message log Probable cause and recommended action In rare instances, events gathered by the track change feature can report inaccurate information to the system message log. For example, a user enters a correct user name and password, but the login was rejected because the maximum number of users had been reached. However, when looking at the system message log, the login was reported as successful.
Fibre Channel Routing 2 3. Check the fan status and speed output. If any of the fan speeds display abnormal RPMs, replace the fan. You may first consider re-seating the fan (unplug it and plug it back in). Checking the switch temperature 1. Log in to the switch as user. 2. Enter the tempShow command. 3. Check the temperature output. Look for indications of high or low temperatures. Checking the power supply 1. Log in to the switch as user. 2. Enter the psShow command. 3. Check the power supply status.
2 Fibre Channel Routing Checking for Fibre Channel connectivity problems 1. 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 (extended link service) ECHO request to the source port specified and validates the response.
Third party applications 2 Third party applications Symptom Replication application works for a while and then breaks. Probable cause and recommended action Some third party applications will work when they are first set up and then cease to work due to an incorrect parameter setting. Check each of the following parameters and your application vendor documentation to determine if these are set correctly: • Port-base routing Use the aptPolicy command to set this feature.
2 16 Third party applications Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01
Chapter 3 Connections Issues This chapter provides information on troubleshooting basic connectivity issues and the most common procedures to use to diagnose and recover from basic connection problems. In this chapter • Port initialization and FCP auto discovery process . . . . . . . . . . . . . . . . . . . . • Link issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Connection problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Port initialization and FCP auto discovery process Figure 1 shows the process behind port initialization. Understanding this process can help you determine where a problem resides. For example, if your switch cannot form an E_Port, you understand that the process never got to that point or does not recognize the switch as an E_Port. Possible solutions would be to look at licensing and port configuration.
Link issues 3 Link issues Symptom LEDs are flashing. Probable cause and recommended action Depending on the rate of the flash and the color of the 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 LEDs are steady.
3 Connection problems • A device that is not logically connected to the switch will be registered as a G_ or U_Port. If NPIV is not on the switch, the N_Port is another possible port type. 3. If the missing device is logically connected, proceed to the next troubleshooting procedure (“Checking the name server (NS)” on page 20). 4. If the missing device is not logically connected, check the device and everything on that side of the data path. Also see “Link failures” on page 21 for additional information.
Link failures NL NL 3 051ee2; 3;21:00:00:20:37:d9:77:5a;20:00:00:20:37:d9:77:5a; na FC4s: FCP [SEAGATE ST318304FC 0005] Fabric Port Name: 20:0e:00:60:69:10:9b:5b 051ee4; 3;21:00:00:20:37:d9:74:d7;20:00:00:20:37:d9:74:d7; na FC4s: FCP [SEAGATE ST318304FC 0005] Fabric Port Name: 20:0e:00:60:69:10:9b:5b 051ee8; 3;21:00:00:20:37:d9:6f:eb;20:00:00:20:37:d9:6f:eb; na FC4s: FCP [SEAGATE ST318304FC 0005] Fabric Port Name: 20:0e:00:60:69:10:9b:5b NL 051eef; 3;21:00:00:20:37:d9:77:45;20:00:00:20:37:d9:77:45; na
3 Link failures NOTE Skip this procedure if the port speed is set to a static speed through the portCfgSpeed command. Determining a successful negotiation 1. Enter the portCfgShow command to display the port speed settings of all the ports. 2. Enter the switchShow command to determine if the port has module light. 3. Determine whether or not the port completes speed negotiation by entering the portCfgSpeed command.
Link failures 11:40:02.078 PORT Received LISA frame Rx3 23 20 3 22000000,00000000,ffffffff,11050100 The LISA frame indicates that the loop initialization is complete. 3. Skip point-to-point initialization by using the portCfgLport Command. The switch changes to point-to-point initialization after the LISA phase of the loop initialization. This behavior sometimes causes trouble with old HBAs. Checking for a point-to-point initialization failure 1.
3 Marginal links TABLE 4 SwitchShow output and suggested action (Continued) Output Suggested action G_Port The port has not come up as an E_Port or F_Port. Check the output from portLogShow or PortLogDump commands and identify the link initialization stage where the initialization procedure went wrong. L_Port If the opposite side is not a loop device, the link has come up in a wrong mode.
Device login issues 3 • If the loopback test did not fail, the SFP was bad. 7. Perform the following steps to rule out cabling issues: a. Insert a new cable in the suspected marginal port. b. Enter the portErrShow command to determine if a problem still exists. • If the portErrShow output displays a normal number of generated errors, the issue is solved.
3 Device login issues 22 22 -N8 No_Module 23 23 -N8 No_Module 24 24 -N8 No_Module 25 25 -N8 No_Module 26 26 -N8 No_Module 27 27 -N8 No_Module 28 28 -N8 No_Module 29 29 -N8 No_Module 30 30 -N8 No_Module 31 31 -N8 No_Module 32 32 -N8 No_Module 33 33 -N8 No_Module 34 34 -N8 No_Module 35 35 -N8 No_Module 36 36 -N8 No_Module 37 37 -N8 No_Module 38 38 -N8 No_Module 39 39 -N8 No_Module 40 40 -N8 No_Module 41 41 -N8 No_Module 42 42 -N8 No_Module 43 43 -N8 No_Module 44 44 -N8 No_Module 45 45 -N8 No_Module 46 46 -N
Device login issues 79 79 id (Trunk master) N2 Online E-Port 3 10:00:00:05:1e:34:d0:05 "1_d1" Pinpointing problems with device logins 1. Log in to the switch as admin. 2. Enter the switchShow command; then, check for correct logins. 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.
3 Device login issues switch:admin> porterrshow 0: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: frames enc crc too too bad enc disc link loss loss frjt fbsy tx rx in err shrt long eof out c3 fail sync sig ===================================================================== 39m 95m 0 0 0 0 0 364k 10 13 6.1k 8 0 0 2.6g 4.1g 0 0 0 0 0 150k 46 0 0 1 0 0 3.7g 2.0g 0 0 0 0 0 18 134 0 0 0 0 0 2.2g 2.9g 0 0 0 0 0 19 127 0 0 0 0 0 20m 19m 0 0 0 0 0 241k 10 10 4.3k 5 0 0 113m 2.
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> portlogdump 13 time task event port cmd args ------------------------------------------------Tue Apr 24 19:45:58 2007 19:45:58.728 PORT Tx3 0 12 22000000,00000000,ffffffff,11010000 19:45:58.778 SPEE sn 0 WS 000000f0,00000000,00000000 19:45:58.787 SPEE sn 0 WS 00000001,00000000,00000000 19:45:59.
3 Media-related issues 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 Segmented fabrics Fabric segmentation is generally caused by one of the following conditions: • • • • • • • Incompatible fabric parameters (see “Reconciling fabric parameters individually,” next). Incorrect PID setting (see Fabric OS Administrator’s Guide). Incompatible zoning configuration (see Chapter 8, “Zone Issues”). Domain ID conflict (see “Reconciling fabric parameters individually” on page 31). Incompatible security policies. Incorrect fabric mode.
3 Segmented fabrics See the Fabric OS Command Reference for more detailed information. 9. Enable the switch by entering the switchEnable command. Alternatively, you can reconcile fabric parameters by entering the configUpload command for each switch. Downloading a correct configuration You can restore a segmented fabric by downloading a previously saved correct backup configuration to the switch.
Chapter Configuration Issues 4 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. As part of standard configuration maintenance procedures, it is recommended that you back up all important configuration data for every switch on a host computer server for emergency reference. NOTE For information about AD-enabled switches using Fabric OS v5.2.
4 Configupload and download issues 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.
Configupload and download issues Symptom 4 The configuration download fails. Probable cause and recommended action Check the following: • The FTP or SCP server’s host name is known to the switch. Verify with your network administrator that the switch has access to the FTP server. • The USB path is correct. If your platform supports a USB memory device, verify that it is connected and running. Verify that the path name is correct.
4 Brocade configuration form • • • • configUpload completed successfully … (RASLog) configDownload not permitted … (Audit log) configUpload not permitted … (RASLog) (Warning) Downloading configuration without disabling the switch was unsuccessful. (Audit log) Brocade configuration form Use this form as a hard copy reference for your configuration information. In the hardware reference manuals for the Brocade 48000 and DCX modular switches there is a guide for FC port setting tables.
Chapter 5 FirmwareDownload Errors This chapter contains procedures to troubleshoot and fix common firmware download issues relating to a switch or an enterprise-class switch. In this chapter • Blade troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Firmware download issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Troubleshooting firmwareDownload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 Firmware download issues Brocade 48000 with FA4-18 or a FC10-6 blades: If you are running Fabric OS v5.3.0, then you cannot downgrade to earlier versions without removing the blades. Brocade 48000 with FC8-16 blades: If you are running Fabric OS v6.0, then you cannot downgrade to earlier versions without removing the blade. Brocade DCX Director with FC8-16/32/48 blades: If you are running Fabric v6.1.0, then you cannot downgrade to pre-Fabric OS v6.0.
Firmware download issues 5 Available space on usbstorage 74% Example of error message Stealth200E:admin> firmwaredownload Server Name or IP Address: 192.126.168.115 User Name: jdoe File Name: /users/home/jdoe/firmware/v6.1.0 Network Protocol(1-auto-select, 2-FTP, 3-SCP) [1]: 2 Password: Checking system settings for firmwaredownload... Protocol selected: FTP Trying address-->AF_INET IP: 192.126.168.115, flags : 2 Firmware access timeout. The server is inaccessible or firmware path is invalid.
5 Firmware download issues Symptom You receive a BadRootDev error message. Probable cause and recommended action You perform a firmwaredownload on a 3900 or 4100 (a single-bladed/4.x switch). During the firmwaredownload process the boot environment variables are incorrectly set and causes a BadRootDev error message to appear. You can find the information contained in the examples below in the output from the supportShow command.
Troubleshooting firmwareDownload 5 Troubleshooting firmwareDownload 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, see the Fabric OS Message Reference for details about error messages. Also see, “Considerations for downgrading firmware” on page 44.
5 Brocade DCX error handling TABLE 9 Scenario No. When Scenario Error handling Required Action 1 During step 1 During downloading to the main CPU of the standby CP, if an error occurs and the main CPU reboots. 1. When the main CPU boots up, firmwareDownload is aborted. 2. The firmwareCommit command will be initiated on the main CPU and the original firmware is restored on that CPU. Restart firmwareDownload after the repair is done. 3. Both CPUs on both CPs will have the original firmware.
Brocade DCX error handling TABLE 9 5 Brocade DCX CP Error Handling Scenario No. When Scenario Error handling Required Action 7 During step 7 When downloading to the co CPU of the standby CP, if an error occurs and the co CPU reboots. 1. When the co-CPU on the standby CP boots up, firmwareDownload is aborted. 2. The firmwareCommit command will be initiated on both CPUs on both CPs. Restart firmwareDownload after the repair is done. 3.
5 USB error handling USB error handling The following table outlines how the USB device handles errors under specific scenarios and details what actions you should take after the error occurs. TABLE 10 USB error handling Scenario under which download fails Error handling Action An access error occurs during firmwaredownload due to the removal of the USB device, or USB device hardware failure, etc.
Considerations for downgrading firmware 5 This example shows hardware-related messages for the same downgrade example: director:admin> firmwaredownload Type of Firmware (FOS, SAS, or any application) [FOS]: Server Name or IP Address: 192.168.32.10 Network Protocol (1-auto-select, 2-FTP, 3-SCP) [1]: User Name: userfoo File Name: /home/userfoo/dist/v5.3.0 Password: Verifying the input parameters ... Checking system settings for firmwaredownload...
5 Considerations for downgrading firmware Message AP Blade type 33 is inserted. Please use slotshow to find out which slot it is in and remove it. Cannot downgrade due to the presence of AP BLADE type 33. Remove or power off these blades before proceeding. Probable cause and recommended action The firmware download operation was attempting to download Fabric OS v5.0.0 with one or more Brocade FR4-18 port blades (blade ID 33) in the system. Brocade FR4-18 port blades are not supported on firmware v5.0.
Considerations for downgrading firmware Message 5 SW Blade type 51 is inserted. Please use slotshow to find out which slot it is in and remove it. Probable cause and recommended action The firmware download operation was attempting to downgrade a system to Fabric OS v5.3.0 or earlier with one or more Brocade FC8-48 port blades (blade ID 51) in the system. Brocade FC8-48 port blades are not supported on firmware v5.3.0 or earlier, so the firmware download operation failed.
5 Considerations for downgrading firmware Upgrade your switch to Fabric OS version v5.1.0 or v5.2.0 before upgrading to v5.3.0 Message Firmwaredownload of blade application firmware failed. Reissue firmwareDownload to recover. Probable cause and recommended action The firmware download operation was attempting to upgrade the SAS image while the blade was operational. Retry the firmwaredownload command again.
Considerations for downgrading firmware 5 Platform These messages are switch features or fabric-wide settings that need to be removed or disabled before downgrading the firmware. Message Only platform option 5 is supported by version 6.1.0. Use chassisconfig to reset the option before downloading the firmware. Probable cause and recommended action The firmware download operation was attempting to upgrade a system to Fabric OS v6.1.0.
5 Considerations for downgrading firmware Message The active security DB size is greater than 256 KB, you will not be allowed to downgrade to below v6.0.0. Probable cause and recommended action You cannot downgrade because the active security database size is greater than 256 KB. Reduce the size before downgrading. Message Cannot downgrade to v5.3.0 or earlier because FIPS mode is enabled. Probable cause and recommended action You cannot downgrade because FIPS mode is enabled.
Considerations for downgrading firmware 5 Port settings These messages refer to port settings that need to be fixed before downgrading the switch’s firmware. Message Cannot downgrade to v5.2.0 or lower due to GE port(s) has MTU size configured between 1261 to 1499 bytes. Please use portcfg command to reconfigure the MTU size and try again. Probable cause and recommended action If a GE port has its MTU size configured between 1261 to 1499 bytes, you will not be allowed to downgrade to v5.2.0 or earlier.
5 Considerations for downgrading firmware Message The command failed due to presence of long-distance ports in L0.5 mode. Please remove these settings before proceeding. Probable cause and recommended action The firmware download operation was attempting to upgrade a system to Fabric OS v6.0.0 with long-distance ports in L0.5, L1, or L2 modes. Long-distance ports in these modes are not supported in firmware v6.0.0 or later, so the firmware upgrade operation failed.
Considerations for downgrading firmware LE LD LS Message 5 Specify LE mode is used for E_Ports for distances beyond 5 Km and up to 10 Km. A total of 5, 10, or 20 full-size frame buffers are reserved for port speeds of 1 Gbps, 2 Gbps, or 4 Gbps, respectively. LE does not require an Extended Fabrics license. Specify LD for automatic long-distance configuration. The buffer credits for the given E_Port are automatically configured, based on the actual link distance.
5 Considerations for downgrading firmware Use the portDisable command to disable these ports before proceeding. Routing These error messages refer to routing policies. Message Cannot downgrade to v5.1.0 because Device Based routing policy is not supported by v5.1.0. Use aptPolicy to change the routing policy before proceeding. Probable cause and recommended action The firmware download operation was attempting to upgrade a system to Fabric OS v5.1.0 with device-based routing policy selected.
Considerations for downgrading firmware Message 5 Cannot downgrade due to the presence of broadcast zone(s). Remove or disable them before proceeding. Probable cause and recommended action If the switch is running v5.3.0 or later, and a “broadcast zone” is configured, you cannot downgrade the switch to v5.2.0 or earlier, as a broadcast zone gets a special meaning in v5.3.0, but it will be treated as regular zone in v5.2.0 or earlier.
5 56 Considerations for downgrading firmware Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01
Chapter 6 Security Issues This chapter provides troubleshooting information and procedures on security for the switch management channel. In this chapter • Password issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Protocol and certificate management issues . . . . . . . . . . . . . . . . . . . . . . . . • SNMP issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FIPS issues. . . . . . . . . . .
6 Protocol and certificate management issues 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 The following table describes the options available when one or more types of passwords are lost.
Protocol and certificate management issues Symptom 6 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 12 for recommended actions you can take to correct the problem. TABLE 12 SSL messages and actions Message Action The page cannot be displayed The SSL certificate is not installed correctly or HTTPS is not enabled correctly.
6 SNMP issues SNMP issues 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 will need to verify the following: • There are no port filters in the firewalls between the fabric and the SNMP management station.
Chapter 7 ISL Trunking Issues This chapter describes symptoms and solutions to trunking problems as well as recommended actions to take to correct trunking problems. In this chapter • Link issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 • Buffer credit issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 Buffer credit issues • • • • 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 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. • The ports are not set to the same long distance mode.
Chapter 8 Zone Issues This chapter describes troubleshooting techniques and recommended actions for common zoning problems. In this chapter • Overview of corrective action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Segmented fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Zone conflicts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Gathering additional information .
8 Zone conflicts Symptom Zone conflict appears in logs and fabric is segmented. Probable cause and recommended action This issue is usually caused by an incompatible zoning configurations. Verify one of the following: • The effective cfg (zone set) on each end of the segmented ISL must be identical. • Any zone object with the same name must have the same entries in the same sequence. Symptom Fabric segmentation is caused by an “incompatible zone database”.
Zone conflicts 8 ATTENTION Be careful using the cfgClear command because it deletes the defined configuration. Table 13 summarizes commands that are useful for debugging zoning issues. TABLE 13 Commands for debugging zoning Command Function aliCreate Use to create a zone alias. aliDelete Use to delete a zone alias. cfgCreate Use to create a zone configuration. cfgShow Displays zoning configuration.
8 Zone conflicts ATTENTION The cfgClear command clears the zoning database on the switch where the command is run. 5. Enter the switchEnable command on each switch once the zoning configuration has been cleared. This forces the zones to merge and populates the switches with the correct zoning database. The fabrics will then merge. Editing zone configuration members 1. Log in to one of the switches in a segmented fabric as admin. 2. Enter the cfgShow command and print the output. 3.
Zone conflicts 8 • Generating an ELS ECHO request to the destination port specified and validates the response. Regardless of the device’s zoning, the fcPing command sends the ELS frame to the destination port. A device can take any of the following actions: • Send an ELS Accept to the ELS request. • Send an ELS Reject to the ELS request. • Ignore the ELS request. There are some devices that do not support the ELS ECHO request.
8 Gathering additional information Request timed out Request timed out Request timed out Request timed out Request timed out 5 frames sent, 0 frames received, 0 frames rejected, 5 frames timeout Round-trip min/avg/max = 0/0/0 usec switch:admin> For details about the fcPing command, see the Fabric OS Command Reference. Checking for zoning problems 1. Enter the cfgActvShow command to determine if zoning is enabled.
Chapter 9 FCIP Issues This chapter describes the FCIP concepts, configuration procedures, and tools and procedures for monitoring network performance. Commands described in this chapter require Admin or root user access. See the Fabric OS Command Reference for detailed information on command syntax. In this chapter • FCIP tunnel issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCIP links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9 FCIP tunnel issues Reply Reply Reply Reply from from from from 11.1.1.2: 11.1.1.2: 11.1.1.2: 11.1.1.2: bytes=64 bytes=64 bytes=64 bytes=64 rtt=0ms rtt=0ms rtt=0ms rtt=0ms ttl=64 ttl=64 ttl=64 ttl=64 Ping Statistics for 11.1.1.2: Packets: Sent = 4, Received = 4, Loss = 0 ( 0 percent loss) Min RTT = 0ms, Max RTT = 0ms Average = 0ms If you are able to ping, then you have IP connectivity and your tunnel should come up. If not continue to the next step. 4.
FCIP links • • • • • • 9 To much data tries to be sent over the link. Management data gets lost, queued too long, and timeouts expire. Data exceeds timeouts multiple times. Verify what link bandwidth is available. Confirm the IP path is being used exclusively for FCIP traffic. Confirm that traffic shaping is configured to limit the bandwidth to available (portshow fciptunnel). 1. If committing a rate, generally recommend setting a little below available to allow for bursting 2.
9 Port mirroring • When configuring routing over an FCIP link for a fabric, the edge fabric will use VE_Ports and the backbone fabric will use VEX_Ports for a single tunnel. • If an FCIP tunnel fails with the “Disabled (Fabric ID Oversubscribed)” message, the solution is to reconfigure the VEX_Port to the same Fabric ID as all of the other ports connecting to the edge fabric.
Port mirroring 9 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. Attempts to mirror more traffic than available bandwidth result in the port mirror throttling the SID/DID traffic so that traffic does not exceed the maximum available bandwidth.
9 Port mirroring The FC4-48 implements port pairing, meaning that two ports share the same area. Port pairing uses a single area to map to two physical ports. A frame destined to the secondary port is routed to the primary port. The primary port's filtering zone engine is used to redirect the frame to the secondary port. Port mirroring uses the port filter zone engine to redirect the frames to the mirror port. If two F_Ports share the same area, both ports cannot be part of a mirror connection.
Port mirroring 9 The bandwidth of the mirror port is unidirectional. The host (SID) talks to multiple storage devices (DIDs) and does not send full line rate to a single target. A mirror port configured at 2GB can only support up to 2GB of traffic. A normal 2G F_Port is bidirectional and can support up to 4GB of traffic (two to transmit and two to receive).
9 FTRACE concepts Displaying port mirror connections 1. Log in to the switch as admin. 2.
FTRACE concepts 9 After information is captured, you can use the portshow command to display FTRACE information on a GE port for a tunnel. You can save trace events can for future analysis. Displaying the trace for a tunnel 1. Log on to the switch as admin. 2. Enter the portShow -ftrace command with the following options: portshow -ftrace ge0 -stats This displays the trace stats for the GE port 0 for tunnel 1. NOTE The configuration file includes key FCIP FTRACE configuration values.
9 FTRACE concepts The following example configures FTRACE with ACO disabled, and FTRACE enabled with a trigger mask value of 00000003, and a trace mask value of ffffffff. portcfg ftrace ge0 3 cfg -a 0 -e 1 -p 5 -s 00000003 -t ffffffff Configuring FTRACE for a tunnel Use the following syntax to configure a trace: portcfg -ftrace [slot-number] ge port number [tunnel -id] cfg|del] Enabling a trace 1. Log on to the switch as admin. 2.
Chapter FICON Fabric Issues 10 This chapter discusses FICON issues, recommended actions, and additional information you should gather to fix your issue. Any information you need to verify that FICON has been set up correctly can be found in the Fabric OS Administrator’s Guide. In this chapter • FICON issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 • Troubleshooting FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10 Troubleshooting FICON Symptom Packets are being dropped between two FICON units. Probable cause and recommended action When planning cable the following criteria must be considered. • Distance considerations • Fibre Optics Sub Assembly (FOSA) type (SW or LW) • Cable specifications (SM or MM) • Patch Panel Connections between FOSA ports (link loss .
Troubleshooting FICON 10 • Supportshow data is only valid if run within about 30 minutes of the failure in order for the data to be valid. • Provide the IOCDS mainframe file. This will define how all mainframe ports are configured. • Type of mainframe involved. Need make, model, and driver levels in use. • Type of actual Storage array installed. Many arrays will emulate a certain type of IBM array and we need to know the exact make, model, and firmware of the array in use.
10 Troubleshooting FICON Single-switch topology checklist This checklist is something you should verify that you have done in your FICON environment to ensure proper functionality of the feature: • • • • Brocade switch Fabric OS v4.1.2 or later release. Management tool - Suggested: Brocade Fabric Manager (FM) v4.1.0 or later. No license is required to enable FICON support. There is no special mode setting for FICON. NOTE There is no requirement to have a secure fabric in a single switch topology.
Troubleshooting FICON CUP 10 • Is this a single-switch or cascaded environment? • If this is a cascaded FICON installation, you must have security policies enabled. • Is IDID (insistent Domain) set? This parameter must be set for cascaded (multiple switch) FICON configurations. It is a best practice to set this parameter in all FICON configurations. • Is the FICON group enabled for supportshow? Check at the top of the supportshow.
10 Troubleshooting FICON CUP Symptom Mainframe RMF utility fails to capture performance data Probable cause and recommended action On Fabric OS v6.0.0, Brocade SilkWorm switches do not fully implement all of CUP commands needed to collect all of performance data on switch. Upgrade your switch to Fabric OS v6.1.0, where the performance data is captured. Symptom Switch panic when a firmware upgrade from v5.0.1d to v5.1.0c occurred.
Troubleshooting FICON NPIV Symptom 10 Upgraded firmware from v5.0.x to v5.2.1a. The Brocade 24000 crashed when new firmware went active. Probable cause and recommended action RNID processing enhancement in firmware.
10 86 Troubleshooting FICON NPIV Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01
Chapter 11 iSCSI Issues If you are having problems with the iSCSI FC4-16IP blade connectivity, use the following chapter to troubleshoot before calling your support provider. NOTE The iSCSI blade FC4-16IP is not supported in the Brocade DCX Backbone. In this chapter • Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 • Zoning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 Connectivity Symptom Multiple sessions are established with the same target. Probable cause and recommended action All available ports are reported by SendTargets processing, and sessions are established for each port to the same target and LUNs.
Zoning 11 Zoning The following issues address zoning problems that can occur in iSCSI. Symptom No DDSet or zoning configuration enabled and iSCSI host cannot discover any targets. Probable cause and recommended action Default zoning is set to no access. Check default zoning using: defZone --show Either create a zoning configuration or set default zoning to All Access using the defZone command. Symptom No DDSet or zoning configuration enabled and iSCSI host cannot discover any targets.
11 Authentication Symptom Changes made to the iSCSI database do not appear on iSCSI hosts. Probable cause and recommended action The DDSet has not been enabled or the database has not been committed. Check the currently enabled DD Set using: iscsiCfg - -show ddset Make sure it is reported as enabled and committed.
Chapter Working With Diagnostic Features 12 This chapter provides information on diagnostics and how to display or save system, port, and specific hardware information. It also describes how to set up system logging mapping (syslogd) and how to set up the offloading of error messages (supportSave). In this chapter This chapter contains the following topics: • About Fabric OS diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 • Diagnostic information . . . . . . .
12 Diagnostic information Diagnostic information On the switch you can enter the supportShow command to dump important diagnostic and status information to the session screen, where you can review it or capture its data.
Power-on self test 12 : : : Checking system RAM - press any key to stop test Checking memory address: 00100000 System RAM test using Default POST RAM Test succeeded. Press escape within 4 seconds to enter boot interface. Booting "Fabric Operating System" image. Linux/PPC load: BootROM command line: quiet Uncompressing Linux...done. Now booting the kernel Attempting to find a root file system on hda2... modprobe: modprobe: Can't open dependencies file /lib/modules/2.4.19/modules.
12 Switch status 2005/03/31-20:13:13, [BL-1001], 222,, INFO, Paulsa45, Port Initialization Completed 2005/03/31-20:13:13, [EM-5012], 0,, INFO, SW4100_P45, EM: sent dumpready to ME., em.c, line: 2152 2005/03/31-20:13:13, [DGD-5002], 0,, INFO, SW4100_P45, Slot 0 has passed the POST tests., main.c, line: 936 If you choose to bypass POST2, or after POST2 completes, various system services are started and the boot process displays additional console status and progress messages.
Switch status 12 Displaying switch information 1. Connect to the switch and log in as admin. 2. Enter the switchShow command, which displays the following information for a switch: Switch summary information includes the following: • • • • • • • • • • • switchName - Switch name. switchType - Switch model and revision numbers. switchState - Switch state: Online, Offline, Testing, or Faulty. switchMode - Switch operation mode: Native, Interop, or Access Gateway.
12 Port information Port information Use the following commands to view information about ports. Viewing the status of a port 1. Connect to the switch and log in as admin. 2. Enter the portShow command, specifying the number that corresponds to the port you are troubleshooting.
Port information 12 Displaying the port statistics 1. Connect to the switch and log in as admin. 2. At the command line, enter the portStatsShow command. Port statistics include information such as the number of frames received, number of frames sent, number of encoding errors received, and number of class 2 and class 3 frames received. See the Fabric OS Command Reference for additional portStatsShow command information, such as the syntax for slot or port numbering.
12 Port information Displaying a summary of port errors for a switch 1. Connect to the switch and log in as admin. 2. Enter the portErrShow command. See the Fabric OS Command Reference for additional portErrShow command information. brcd300:admin> porterrshow frames enc crc too too bad enc disc link loss loss frjt fbsy tx rx in err shrt long eof out c3 fail sync sig ===================================================================== 0: 5.4k 1.9k 0 0 0 0 0 841k 0 0 2 4 0 0 1: 4.
Equipment status TABLE 17 12 Error summary description (Continued) Error type Description loss sig Loss of signal frjt Frames rejected with F_RJT fbsy Frames busied with F_BSY Equipment status You can display status for fans, power supply, and temperature. NOTE The number of fans, power supplies, and temperature sensors depends on the switch type. For detailed specifications on these components, refer to the switch hardware reference manual.
12 System message log • • • • 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). Displaying temperature status 1. Connect to the switch and log in as admin. 2.
Port log 12 Clearing the system message log 1. Connect to the switch and log in as admin. 2. Enter the errClear command. All switch and chassis events are removed. Port log The Fabric OS maintains an internal log of all port activity. The port log stores entries for each port as a circular buffer. The range of lines is 32768 to 65536 for the Brocade 48000 and the Brocade 7500 switch. For all other switches, the number of lines range from 8192 to 16384.
12 Syslogd configuration TABLE 18 Commands for port log management (Continued) Command Description portLogDump Display port logs for all or particular ports, without page breaks. portLogEnable Enable port logs for all or particular ports. portLogShow Display port logs for all or particular ports, with page breaks. The portLogDump command output (trace) is a powerful tool that is used to troubleshoot fabric issues.
Syslogd configuration 12 Fabric OS can be configured to use a UNIX-style syslogd process to forward system events and error messages to log files on a remote host system. The host system can be running UNIX, Linux, or any other operating system that supports the standard syslogd functionality. Fabric OS supports UNIX local7 facilities (the default facility level is 7). Configuring for syslogd involves configuring the host, enabling syslogd on the switch, and, optionally, setting the facility level.
12 Automatic trace dump transfers switch:admin> syslogdipadd 10.1.2.4 switch:admin> syslogdipadd 10.1.2.5 switch:admin> syslogdipadd 10.1.2.6 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.
Automatic trace dump transfers 12 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. Enter the following command: switch:admin> supportftp -s The command is interactive. 4. Respond to the prompts as follows: Host Name User name Password Remote directory Enter the name or IPv4 or IPv6 address of the server where the file is to be stored; for example, 1080::8:800:200C:417A for a server configured for IPv6.
12 Diagnostic tests not supported by M-EOS 9.6.2 and FOS 6.0 The command is interactive. 3. Respond to the prompts as follows: User name Password Remote directory Enter the user name of your account on the server; for example, “JohnDoe”. Enter your account password for the server. Specify a path name for the remote directory. Absolute path names can be specified by starting the path name with a forward slash (/).
Appendix A Switch Type 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:FinanceSwitch switchType:34.0 <=== convert this number using Table 20.
A Switch Type TABLE 20 Switch Type 108 Switch type to B-Series model converter B-Series switch model ASIC 62 Brocade DCX Condor2 64 5300 GoldenEye2 66 5100 Condor2 71 300 GoldenEye2 Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01
Appendix B Hexidecimal Hexidecimal, or simply 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 and represent in a format easier for humans to read. It acts as a form of shorthand, in which one hexidecimal digit stands in place of four binary bits. For example, the decimal numeral 79, whose binary representation is 01001111, is 4F (or 4f) in hexidecimal (4 = 0100, F = 1111).
B Hexidecimal TABLE 21 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 51 52 53 54 55 56 57 58 59 60 Hex 33 34 35 36 37 38 39 3a 3b 3c Decimal 61 62 63 64
Hexidecimal TABLE 21 Hex Decimal Hex Decimal Hex Decimal Hex Decimal Hex Decimal Hex Decimal Hex B Decimal to Hex conversion table 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 211 212 213 214 215 216 217 218 219 220 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 232 233 234 235 236 237 238 239 240 e7 e8 e9 ea eb
B 112 Hexidecimal Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01
Index A account management lost password recovery options, 58 recovering forgotten passwords, 57 unable to modify switch settings, 58 user forgot password, 4 user unable to change switch settings, 4 B BadRootDev, 3, 40 blade errors AP blade type 24 is inserted, 45 AP blade type 31 is inserted, 45 AP blade type 33 is inserted, 46 faulty, 3, 38 stuck in the ’LOADING’ state, 3, 38 SW blade type 36 is inserted, 46 SW blade type 37 is inserted, 46 SW blade type 39 is inserted, 46 SW blade type 51 is inserted,
disc_c3 errors, 27 E E_Port, 17, 23 failed to come online, 3 failed to form, 3 enc_out errors, 27 equipment status, viewing, 99 EX_Port, 17 does not form, 3, 19 FICON errors configured, 53 FICON NPIV troubleshooting, 85 FIPS downgrading firmware, 50 switch boots continuously, 60 F F_Port, 17, 23 fabric issues, 2 merge fails, 3 parameters, 31 parameters, reconcile, 31 segments, 3 fans, status of, 99 FCIP gathering additional information, 72 tunnel bounces, 3, 70 tunnel does not come online, 3, 69 tunnel d
firmwareDownload errors, 41 Access Gateway policies, 50 active security DB size is greater than 256 KB, 50 AP blade type 24 is inserted, 45 AP blade type 31 is inserted, 45 AP blade type 33 is inserted, 46 BadRootDev, 40 blade application firmware failed, 48 blade is faulty, 38 blade is stuck in the ‘LOADING’ state, 38 broadcast zone(s), 55 Brocade DCX error handling, 41 cannot download the requested firmware, 39 cannot upgrade directly to v5.3.0, 47 cannot upgrade directly to v6.
L L_Port, 24 LEDs flashing, 3 no light, 3 steady, 3 link intermittent connectivty, 3 LEDs flashing, 19 LEDs steady, 19 marginal, 3 no LED light, 19 logical connection, 19 loop initialization failure, 22 LUN, 88 M marginal link, 3 marginal links, 2 message logs, 1 missing devices, 2 N Name Server, (See also NS), 20 network time protocol, (See also NTP), 1 no connectivity between host and storage, 3 no connectivity between switches, 3 no light on LEDs, 3 NS, 20 nsShow, 88, 90 NTP, 1 O output from a console
R T RAID device, 88 recovering forgotten passwords, 57 resolving zone conflicts, 64 routing errors device-based routing, 54 tag field, interpreting, 81 target LUNs on, 88 targets, 2 temperature, status of, 100 test a port, 30 a switch, 30 troubleshooting, 81 certificates, 59 corrupt certificate, 59 invalid certificate, 59 trunk bounces, 4 failed to form, 4 tunnel goes on- and offline, 70 S SCSI retry errors, 4 timeout errors, 4 security gathering additional information, 59 segmentation, 3, 31 segmented
Z zone configuration, 2 configuration mismatch, 4 content mismatch, 4 resolving conflicts, 64 troubleshooting, 64 type mismatch, 4 zone errors broadcast zone exists, 55 broadcast zone(s), 55 LSAN count, 55 LSAN zone enabled, 55 zoning, 90 118 Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01
