53-1002751-01 14 December 2012 Fabric OS Troubleshooting and Diagnostics Guide Supporting Fabric OS v7.1.
Copyright © 2008-2012 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-1002751-01
Contents About This Document How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . xii What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switch boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Rolling Reboot Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 FC-FC routing connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Generating and routing an ECHO . . . . . . . . . . . . . . . . . . . . . . . . 16 Superping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Route and statistical information . . .
Brocade configuration form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Chapter 5 Firmware Download Errors Blade troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Firmware download issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Troubleshooting with the firmwareDownload command . . . . . . . . . 54 Gathering additional information . . . . . . . . . . . . . . . . . . . . . . . . 55 USB error handling . . . . . . . . .
Chapter 9 Zoning Overview of corrective action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Verifying a fabric merge problem . . . . . . . . . . . . . . . . . . . . . . . . 73 Verifying a TI zone problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Segmented fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Zone conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System message log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 Displaying the system message log, with no page breaks . . .110 Displaying the system message log one message at a time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Clearing the system message log . . . . . . . . . . . . . . . . . . . . . . .111 Port log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Viewing the port log . . . . . . . . . . .
x Fabric OS Troubleshooting and Diagnostics Guide 53-1002751-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii • Additional information . . . . . . . . . . .
Supported hardware and software In those instances in which procedures or parts of procedures documented here apply to some switches but not to others, this guide identifies which switches are supported and which are not. Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. for Fabric OS v7.1.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 6505, 6510, and 6520— 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.
1 Questions for common symptoms TABLE 2 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 Corre
1 TABLE 2 Questions for common symptoms 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 between
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, “Zoning
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-1002751-01
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 can help you determine which applications might be impacted. Using Frame Viewer, you can see exactly what time the frames were dropped. (Timestamps are accurate to within one second.) Additionally, this assists in the debug process.
Switch 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 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 Regardless of the device’s zoning configuration, the fcPing command sends the ELS frame to the destination port. A destination device can take any one of the following actions: • Send an ELS Accept to the ELS request. • Send an ELS Reject to the ELS request. • Ignore the ELS request.
2 FC-FC routing connectivity ATTENTION There are some devices that do not support the ELS ECHO request. In these cases, the device either does not respond to the request or send an ELS reject. When a device does not respond to the ELS request, further debugging is required; however, do not assume that the device is not connected. It works by sending ECHO frames to a destination device and outputs the status of each ISL it traverses whether or not the response from the destination device is received.
2 FC-FC routing connectivity 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.
2 FC-FC routing connectivity switch:admin> pathinfo 5 Hop In Port Domain ID (Name) Out Port BW Cost ----------------------------------------------------------------------------0 2 1 (sw0) 6 4G 500 1 23 2 (sw0) 8 4G 500 2 4 3 (sw0) 3 4G 500 3 12 4 (sw0) 18 4G 10000 4 4 7 (switch_3) 0 4G 500 5 26 5 (switch_3) 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..
2 FC-FC routing connectivity Symptom Host application times out. Probable cause and recommended action The FCR tends to take a long time, more than 5 seconds, to present and setup paths for the proxy devices. Certain hosts are able to do discovery much faster as a result they end up timing out. Use the speed tag feature to always present target proxy to the host and import them faster. This helps sensitive hosts to do a quick discovery without timing out or cause an application failure.
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.
3 Link failures 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.
3 Media-related issues ------------------------------------------------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 Alternatively, you can reconcile fabric parameters by entering the configUpload command for each switch and upload a known-good configuration file. If you do this option, the two switches must be the same model. Downloading a correct configuration You can restore a segmented fabric by downloading a previously saved correct backup configuration to the switch.
Segmented fabrics 3 Fabric parameters (yes, y, no, n): [no] y Domain: (1..239) [1] 89 WWN Based persistent PID (yes, y, no, n): [no] Allow XISL Use (yes, y, no, n): [yes] R_A_TOV: (4000..120000) [10000] E_D_TOV: (1000..5000) [2000] WAN_TOV: (0..30000) [0] MAX_HOPS: (7..19) [7] Data field size: (256..2112) [2112] Sequence Level Switching: (0..1) [0] Disable Device Probing: (0..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 With port mirroring, you can configure a switch port to mirror the traffic between a specific source and destination port. This is only supported between F_Ports. This is a useful way to troubleshoot a problem port without bringing down the host and destination links to insert an inline analyzer. Port mirroring captures traffic between two devices. It mirrors only the frames containing the SID/DID to the mirror port.
3 Port mirroring • Using the firmware download procedure to downgrade to previous Fabric OS releases that do not support port mirroring requires that you remove all the port mirroring connections. If you downgrade to a previous versions of Fabric OS, you cannot proceed until the mirroring connections are removed. • Port mirroring is supported with Virtual Fabrics with the limitation that you cannot have FCR enabled within the same 8-port group.
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-1002751-01
Chapter Configuration 4 In this chapter • Configuration upload and download issues . . . . . . . . . . . . . . . . . . . . . . . . . 45 • Brocade configuration form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Configuration upload and download issues It is important to maintain consistent configuration settings on all switches in the same fabric because inconsistent parameters (such as inconsistent PID formats) can cause fabric segmentation.
4 Configuration upload and download issues • The FTP or SCP server’s IP address cannot be contacted. Verify that you can connect to the FTP server. Use your local PC to connect to the FTP server or ping the FTP server. Example of a successful ping C:\> ping 192.168.163.50 Pinging 192.168.163.50 with 32 bytes of data: Reply from 192.168.163.50: bytes=32 time=5ms TTL=61 Ping statistics for 192.168.163.
Configuration upload and download issues 4 • On a Virtual Fabrics-enabled switch, you do not have the chassis role permission set on your user account. Implement one change at a time, then issue the command again. By implementing one change at a time, you are able to determine what works and what does not work. Knowing which change corrected the problems help you to avoid this problem in future endeavors. Symptom The configuration download fails.
4 Brocade configuration form Symptom Configuration did not seem to change after the configuration download process finished. 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.
Brocade configuration form TABLE 10 4 Brocade configuration and connection (Continued) Brocade configuration settings Value Domain ID Switch name Ethernet IP address Ethernet subnet mask Total number of local devices (nsShow) Total number of devices in fabric (nsAllShow) Total number of switches in the fabric (fabricShow) Fabric OS Troubleshooting and Diagnostics Guide 53-1002751-01 49
4 50 Brocade configuration form Fabric OS Troubleshooting and Diagnostics Guide 53-1002751-01
Chapter 5 Firmware Download Errors In this chapter • Blade troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Firmware download issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Troubleshooting with the firmwareDownload command . . . . . . . . . . . . . . . • USB error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Considerations for downgrading firmware . . . . . .
5 Firmware download issues 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 Cannot upgrade directly to v6.3.0. Probable cause and recommended action If the switch is running Fabric OS v6.1.0 or earlier, you are not allowed to upgrade directly to v6.3.0 because of the “one-version” rule. Upgrade your switch to Fabric OS version v6.2.0 before upgrading to v6.3.0. The “one-version” rule also applies to downgrading. Symptom Server is inaccessible or firmware path is invalid.
5 Troubleshooting with the firmwareDownload command Network Protocol(1-auto-select, 2-FTP, 3-SCP) [1]: 2 Password: Server IP: 192.168.168.115, Protocol IPv4 Checking system settings for firmwaredownload... Cannot download the requested firmware because the firmware doesn't support this platform. Please enter another firmware path. Symptom Cannot download on a switch with Interop mode turned on.
5 USB error handling If the firmware download fails in a director or enterprise-class platform, the CPs may end up with different versions of firmware and are unable to achieve HA synchronization. In such cases, issue the firmwareDownload -s command on the standby CP; the single mode (-s) option allows you to upgrade the firmware on the standby CP to match the firmware version running on the active CP. Then reissue the firmwareDownload command to download the desired firmware version to both CPs.
5 Considerations for downgrading firmware Considerations for downgrading firmware The pre-installation check of the firmwareDownload command detects all of the blocking conditions that can prevent a successful downgrade, and warns you about all these conditions. The error messages displayed by the firmwareDownload command states the blocking conditions and the corresponding commands to correct them. You must address all of these blocking conditions before proceeding.
Considerations for downgrading firmware 5 Checking version compatibility... Version compatibility check passed.. The following items must be addressed before downloading the specified firmware: FC8-32E and FC8-48E are not supported by the targeted firmware. Please use slotshow to determine which of these are installed and remove them before continuing. The messages in this section are displayed if an exception case is encountered during firmware downgrade.
5 Considerations for downgrading firmware Downgrade is not allowed because R-RDY flow control ports are configured as D-Ports. Please use "portdporttest --show all" to view the port list and "portcfgdport --disable" to disable before downgrading. Downgrade is not allowed because D-Port is configured with DWDM mode. Please use "portcfgshow" to view the port list and "portcfgdport --enable" to reset DWDM mode before downgrading. Downgrade is not allowed because ICL ports are configured as D-Ports.
Considerations for downgrading firmware Message 5 Cannot upgrade directly to v6.3.0. Upgrade your switch to v6.2.0 first before upgrading to the requested version. Probable cause and recommended action If the switch is running v6.1.0 or earlier, you are not allowed to upgrade directly to v6.3.0 because of the “two-version” rule. Upgrade your switch to Fabric OS version v6.2.0 before upgrading to v6.3.0 Message Non-disruptive firmwaredownload is not supported when downgrading to 6.1.
5 60 Considerations for downgrading firmware Fabric OS Troubleshooting and Diagnostics Guide 53-1002751-01
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 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.
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_Ports 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 that is using XISLs is running an incompatible firmware version and must be upgraded to Fabric OS v6.2.0 or later. Base switch issues All logical switches in a fabric should have the same base switch attribute.
7 Logical switch issues Logical switch issues CAUTION When a logical switch is created, all configuration for the logical switch is set to factory defaults. When a logical switch is deleted, all configuration for the logical switch is deleted permanently and is not recoverable. Symptom The indicated slot is empty. Probable cause and recommended action You used the lsCfg command and an empty slot was specified. Reissue the command with the appropriate slot number.
Switch configuration blade compatibility Symptom 7 A non-GE blade is within the slot range. Probable cause and recommended action You are attempting to configure a GE port on a slot that does not contain GE ports. Symptom A port or ports is already in the current switch. Probable cause and recommended action You may not move a port to the same switch. Symptom The maximum number of switches for this platform has been reached.
7 Gathering additional information 2 3 4 5 6 7 8 9 10 11 12 SW BLADE SW BLADE SW BLADE CORE BLADE CP BLADE CP BLADE CORE BLADE SW BLADE SW BLADE AP BLADE SW BLADE 97 96 96 98 50 50 98 55 96 75 97 FC16-32 FC16-48 FC16-48 CR16-8 CP8 CP8 CR16-8 FC8-32 FC16-48 FX8-24 FC16-32 ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED Gathering additional information For Virtual Fabrics-related issues, use the following guidelines to gather additional data for your switch suppor
Chapter 8 ISL Trunking In this chapter • Link issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 • Buffer credit issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Link issues This section describes trunking link issues that can come up and recommended actions to take to correct the problems. Symptom A link that is part of an ISL trunk failed.
8 Buffer credit issues • • • • • Trunking is not supported in switch interoperability mode. Port trunking is disabled. The port is not an E_Port. The port is not 2 Gbps, 4 Gbps, or 8 Gbps. The port connects to a switch other than the one you want 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 • Diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 • Power-on self test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 • 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.
10 Using the SpinFab and portTest commands 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 Debugging spinFab errors Link errors and tx/rx errors are seen when the spinFab test fails. 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 • Further isolation can be done by running the portLoopbackTest command (Offline test) on the failing port in-order to check whether the blade internal ports are having some problems. - The -lb_mode 1 operand verifies that the SFP is working within normal operating parameters. The use of this operand requires that loopback cables are connected. - The -lb_mode 2 verifies that the ASIC port is working within normal operating parameters.
10 Diagnostic Port (D_Port) Disabling a port 1. Connect to the switch and log in using an account with admin permissions. 2. Enter the appropriate command based on the current state of the port and on whether it is necessary to specify a slot number:. • To disable a port that is enabled, enter the command portDisable portnumber or portDisable slotnumber/portnumber.
Diagnostic Port (D_Port) 10 Understanding D_Port The D_Port does not carry any user traffic, and is designed to run only specific diagnostics tests on it for identifying link-level faults or failures. Basically, in order to bring up a port in D_Port mode, you must configure both ends of the link between a given pair of switches (or switches configured as Access Gateways), and you must disable the existing port before you can configure it as a D_Port.
10 Diagnostic Port (D_Port) • • • • • • Size of test frames Duration of test User-defined test payload Predefined pattern for use in test payload Testing with forward error correction (FEC) on or off (default is off) Testing with credit recovery (CR) on or off (default is off) D_Port test initiation modes and test start behavior Table 20 summarizes D_Port test initiation modes and test start behavior.
Diagnostic Port (D_Port) 10 Supported topologies The following supported topologies illustrate at a high level how D_Port functionality can be used: • • • • “Topology 1: ISLs” on page 93 “Topology 2: ICLs” on page 93 “Topology 3: Access Gateways” on page 94 “Topology 4: HBA to switch” on page 95 NOTE In all of these topologies, both automatic and manual D_Port configuration and test modes are supported. HBAs also support dynamic D_Port mode.
10 Diagnostic Port (D_Port) FIGURE 5 ICLs connecting chassis blades For configuration details see “Using D_Port without HBAs” on page 95. Topology 3: Access Gateways Figure 6 illustrates a switch configured as a single Access Gateway connected to a fabric switch. N and F represent, respectively, an N_Port and an F_Port to be configured as D_Ports. (See note below.
Diagnostic Port (D_Port) 10 Topology 4: HBA to switch Figure 8 illustrates connectivity between an HBA and a switch. F represents an F_Port to be configured as a D_Port. This topology supports dynamic D_Port mode. In dynamic mode, the HBA port does not need to be configured explicitly as a D_Port. It comes up in D_Port mode if the corresponding switch port has been configured as a D_Port.
10 Diagnostic Port (D_Port) 1. Disable Port 1 on Switch A, by using the portDisable [slot/]port command. switchA:admin> portdisable 1 2. Configure Port 1 on Switch A as a D_Port, by using portCfgDport - -enable [slot/]port. switchA:admin> portcfgdport --enable 1 3. Repeat steps 1 and 2 for the corresponding port (in this example Port 2) on Switch B. switchB:admin> portdisable 2 switchB:admin> portcfgdport --enable 2 4. Enable Port 1 on Switch A by using the portEnable [slot/]port command.
Diagnostic Port (D_Port) 7. 10 To display a summary of the D_Port, use the portDportTest [slot/]port command with the - -show all operand. switch:admin> portdporttest --show all Port State SFP Capabilities Test Result ============================================= 24 ONLINE E,O PASSED 26 ONLINE E,O RESPONDER 33 OFFLINE --- RESPONDER 8. Optional: If one of the switches reboots, or if the test does not complete on one of the switches, restart the test on both switches.
10 Diagnostic Port (D_Port) HBAs also support testing in dynamic mode, described as follows. If D_Port is enabled on the switch only, it forces the connected adapter port into D_Port mode. The switch initiates and stops tests on the adapter port as specified by the switch configuration. Testing is started by means of BCU commands or HCM options. In dynamic mode you can disable the physical port by using the bcu port --disable command to exit D_Port mode.
Diagnostic Port (D_Port) 10 BCU D_Port commands The following are BCU commands that you can use for D_Port configuration and control: • bcu diag --dportenable — Enables D_Port on a specific port, sets the test pattern, and sets the frame count for testing. • bcu diag --dportdisable — Disables D_Port on a specific port and sets the port back to an N_Port or NL_Port. • bcu diag --dportshow — Displays test results for a test in progress on a specific port.
10 Diagnostic Port (D_Port) Controlling testing You can stop and start D_Port testing on a port by using the following respective commands: • portdporttest - -stop [slot/]port • portdporttest - -start [slot/]port Available suboptions to the - --start option are as follows: • • • • • • • -nframes — Number of frames (in millions) -framesize — Size of frame (from 36 to 2112 bytes) -time — Test duration (in HH:MM format) -pattern — A predefined pattern -payload — A user-defined payload -fec — Forward error
Diagnostic Port (D_Port) 10 4. Install an SFP and attempt to enable the D_Port. switch:admin> bcu diag --dportenable 1/0 ERROR: Switch port is not D_Port capable or D_Port is disabled 5. Connect to the HBA without the SFP and disable the native port. switch:admin> bcu port --disable 1/0 port disabled 6. Attempt to enable the D_Port. switch:admin> bcu diag --dportenable 1/0 ERROR: SFP is not present. D-port will be enabled but it will be operational only after inserting a valid SFP.
10 Diagnostic Port (D_Port) The default value is 1 for 1 million frames. - Specifies the size of test frames that are generated to run the test. The Range is minimum 36 bytes and maximum 2112 bytes The size of the frames should be given in multiples of 4 otherwise the nearest higher multiple of 4 value will be taken as frame size. Default value is taken as 1024 bytes -time - Specified in HH:MM format. Either this option or the nframes can be provided.
Diagnostic Port (D_Port) 10 Example The following example shows the results of a portdporttest - -show output where the electrical and optical tests pass but the link test fails. switch:admin> portdporttest --show 10/39 D-Port Information: =================== Slot: 10 Port: 39 Remote WWNN: 10:00:00:05:33:7e:69:c4 Remote port: 24 Mode: Manual No.
10 Diagnostic Port (D_Port) Example Use the switchShow command to see D_Port information as in the following example. switch:admin> switchshow switchName: switch_10 switchType: 109.
10 Port information Port information Use the following instructions to view information about ports and to help diagnose if your switch is experiencing port problems. Viewing the status of a port 1. Connect to the switch and log in as admin. 2. Enter the portShow [slot/] port command, specifying the number that corresponds to the port you are troubleshooting.
10 Port information 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. Refer to the Fabric OS Command Reference for additional portStatsShow command information, such as the syntax for slot or port numbering.
10 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. Refer to the Fabric OS Command Reference for additional portErrShow command information. switch:admin> porterrshow frames enc crc crc too too bad enc disc link loss loss frjt fbsy tx rx in err g_eof shrt long eof out c3 fail sync sig ============================================================================ 0: 665k 7.
10 Equipment status TABLE 21 Error summary description (Continued) Error type Description too shrt Frames shorter than minimum too long Frames longer than maximum bad eof Frames with bad end-of-frame delimiters enc out Encoding error outside of frames disc c3 Class 3 frames discarded link fail Link failures (LF1 or LF2 states) loss sync Loss of synchronization loss sig Loss of signal frjt Frames rejected with F_RJT fbsy Frames busied with F_BSY Equipment status You can display statu
Equipment status 10 Fan 1 is Absent Fan 2 is Ok, speed is 6553 RPM Fan 3 is Ok, speed is 6367 RPM The possible status values are: • • • • • • OK—Fan is functioning correctly. Absent—Fan is not present. Below minimum—Fan is present but rotating too slowly or stopped. Above minimum—Fan is rotating too quickly. Unknown—Unknown fan unit installed. FAULTY—Fan has exceeded hardware tolerance. The output from this command varies depending on switch type and number of fans present.
10 System message log 3 Ok 18 64 Information displays for each temperature sensor in the switch. The possible temperature status values are: • OK—Temperature is within acceptable range. • FAIL—Temperature is outside of acceptable range. Damage might occur. Refer to the hardware reference manual for your switch to determine the normal temperature range. System message log The system message log, or RASLog, feature enables messages to be saved across power cycles and reboots.
Port log 10 Displaying the system message log one message at a time 1. Connect to the switch and log in as admin. 2. Enter the errShow command. Clearing the system message log 1. Connect to the switch and log in as admin. 2. Enter the errClear command. 3. Repeat step 2 on the standby CP for a complete erasure of the message log. All switch and chassis events are removed from both CPs. Port log The Fabric OS maintains an internal log of all port activity.
10 Port log 16:48:47.263 PORT Rx 79 40 02fffffd,00fffffd,02e4ffff,14000000 16:48:47.263 PORT Tx 79 0 c0fffffd,00fffffd,02e401c2,00000001 16:48:47.263 FCPH read 79 40 02fffffd,00fffffd,c0000000,00000000,02e401c2 16:48:47.263 FCPH seq 79 28 22380000,02e401c2,00000c1e,0000001c,00000000
Syslogd configuration 10 20:29:20.806 FCPH read 3 40 02fffffd,00fffffd,d2000000,00000000,02ee09a8 20:29:20.806 FCPH seq 3 28 22380000,02ee09a8,00000608,0000001c,00000000 20:29:32.638 FCPH write 3 40 00fffffd,00fffffd,00000000,00000000,00000000 20:29:32.638 FCPH seq 3 28 00300000,00000000,000005f4,00020182,00000000 20:29:32.638 PORT Tx 3 40 02fffffd,00fffffd,09a9ffff,14000000 20:29:32.638 FCPH write 9 40 00fffffd,00fffffd,00000000,00000000, 00000000 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 114. 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 24 switchType switchType to B-Series model converter (Continued) B-Series switch model Base switch speed 67 Brocade Encryption Switch 8 Gb 16-port encryption switch 70 5410 8 Gb 12-port embedded switch 71 300 8 Gb 16-port switch 72 5480 8 Gb 24-port embedded switch 73 5470 8 Gb 20-port embedded switch 75 M5424 8 Gb 24-port embedded switch 76 8000 8 Gb 16-FC port, 10 GbE 8-Ethernet port switch 77 Brocade DCX-4S 8 Gb 192-port core fabric backbone 83
Switch Type and Blade ID TABLE 25 Blade ID A B-series blade model descriptions (Continued) B-series blade model Description 74 FCOE10-24 24-FC ports on an application blade that provides Converged Enhanced Ethernet to bridge a Fibre Channel and Ethernet SAN.
A 120 Switch Type and Blade ID Fabric OS Troubleshooting and Diagnostics Guide 53-1002751-01
Appendix Hexadecimal Conversion B Hexadecimal overview Hexadecimal, also known as hex, is a numeral system with a base of 16, usually written by means of symbols 0–9 and A–F (or a–f). Its primary purpose is to represent the binary code that computers interpret in a format easier for humans to remember. It acts as a form of shorthand, in which one hexadecimal digit takes the place of four binary bits.
B Hexadecimal Conversion Decimal-to-hexadecimal conversion table TABLE 26 122 Decimal-to-hexadecimal conversion table Decimal 01 02 03 04 05 06 07 08 09 10 Hex 01 02 03 04 05 06 07 08 09 0a Decimal 11 12 13 14 15 16 17 18 19 20 Hex 0b 0c 0d 0e 0f 10 11 12 13 14 Decimal 21 22 23 24 25 26 27 28 29 30 Hex 15 16 17 18 19 1a 1b 1c 1d 1e Decimal 31 32 33 34 35 36 37 38 39 40 Hex 1f 20 21 22 23 24 25 26 27 28 Decimal 41
B Hexadecimal Conversion TABLE 26 Decimal-to-hexadecimal conversion table (Continued) Hex ab ac ad ae af b0 b1 b2 b3 b4 Decimal 181 182 183 184 185 186 187 188 189 190 Hex b5 b6 b7 b8 b9 ba bb bc bd be Decimal 191 192 193 194 195 196 197 198 199 200 Hex bf c0 c1 c2 c3 c4 c5 c6 c7 c8 Decimal 201 202 203 204 205 206 207 208 209 210 Hex c9 ca cb cc cd ce cf d0 d1 d2 Decimal 211 212 213 214 215 216 217 218 219 220 Hex d3
B 124 Hexadecimal Conversion Fabric OS Troubleshooting and Diagnostics Guide 53-1002751-01
Index A account management lost password recovery options, 62 recovering forgotten passwords, 61 unable to modify switch settings, 62 user forgot password, 4 user unable to change switch settings, 5 B blade errors AP blade type 24 is inserted, 69 faulty, 3, 52 stuck in the ’LOADING’ state, 3, 52 browser troubleshooting certificates, 63 C certificates corrupt, 63 invalid, 63 not installed, 63 troubleshooting, 63 command output, 7 common problem areas, 2 symptoms, 2 configdownload fails, 3 configupload fai
enabling port, 89 enc_out errors, 31 equipment status, viewing, 108 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, 73 fabric segmentation configuration mismatch, 75 content mismatch, 75 default zone access, 77 fcPing, 78 Fibre Channel connectivity, 78 type mismatch, 75 zone configuration members, 77 zone conflict, 75 zoning problems, 79 fans, status of, 108 FCIP tunnel bounces, 3 tunnel does not come online, 3 tunn
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, 89 point-to-point initialization failure, 29 port, 90 bypassed, 30 disabled, 30 enabling, 89 in wrong mode, 30 initial
resolving zone conflicts, 75 Rolling Reboot Detection, 14 S SCSI retry errors, 4 timeout errors, 4 security, gathering additional information, 63 segmentation, 3 segmented fabrics, 36, 74 setting up automatic trace dump transfers, 115 slow-down in FCR performance, 21 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, 17 supportSave, 5 supportSave timeout value, 6 switch configurat
Z zone configuration, 2 configuration mismatch, 5 content mismatch, 5 resolving conflicts, 75 troubleshooting, 75 type mismatch, 5 Fabric OS Troubleshooting and Diagnostics Guide 53-1002751-01 129
130 Fabric OS Troubleshooting and Diagnostics Guide 53-1002751-01
