53-1001187-01 24 November 2008 Fabric OS Troubleshooting and Diagnostics Guide Supporting Fabric OS v6.2.
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Time issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Switch message logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Checking fan components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Checking the switch temperature. . . . . . . . . . . . . . . . . . . . . . . . 13 Checking the power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Checking the temperature, fan, and power supply . . .
Chapter 5 FirmwareDownload Errors In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Blade troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Firmware download issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Troubleshooting firmwareDownload . . . . . . . . . . . . . . . . . . . . . . . . . 46 Gathering additional information . . . . . . . . . . . . . . . . . . . . . . . .
Buffer credit issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Chapter 9 Zone Issues In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Overview of corrective action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Verifying a fabric merge problem . . . . . . . . . . . . . . . . . . . . . . . . 67 Verifying a TI zone problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Chapter 13 Working With Diagnostic Features In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 About Fabric OS diagnostics. . . . . . . .
Appendix A Switch Type Appendix B Hexadecimal Index viii Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-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 13, “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.
• Support for gathering additional information - FCIP troubleshooting support • Provided additional information on FTRACE - Brocade HBA feature support • FC Ping between devices (GUI and CLI support) - Miscellaneous • • • • FC Ping to switch WWN Path information similar to traceroute CLI output RAS enhancements – system-wide RAS LOG support TI zone troubleshooting information • Information that was changed: - All commands have been updated. • Information that was deleted: - All obsolete information.
command Commands are printed in bold. --option, option Command options are printed in bold. -argument, arg Arguments. [] Optional element. variable Variables are printed in italics. In the help pages, values are underlined or enclosed in angled brackets < >. ... Repeat the previous element, for example “member[;member...]” value Fixed values following arguments are printed in plain font. For example, --show WWN | Boolean. Elements are exclusive.
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.com and click Brocade Connect to register at no cost for a user ID and password. For practical discussions about SAN design, implementation, and maintenance, you can obtain Building SANs with Brocade Fabric Switches through: http://www.amazon.
• Detailed description of the problem, including the switch or fabric behavior immediately following the problem, and specific questions • Description of any troubleshooting steps already performed and the results • Serial console and Telnet session logs • syslog message logs 2. Switch Serial Number The switch serial number and corresponding bar code are provided on the serial number label, as illustrated below.
Provide the title and version number of the document and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.
xvi Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01
Chapter 1 Introduction to Troubleshooting In this chapter • Troubleshooting overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Most common problem areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Questions for common symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Gathering information for your switch support provider . . . . . . . . . . . . . . . . .
1 Most common problem areas Most common problem areas Table 1 identifies the most common problem areas that arise within SANs and identifies tools to use to resolve them.
Questions for common symptoms TABLE 2 1 Common symptoms Symptom Areas to check Chapter Blade is faulty Firmware or application download Hardware connections Chapter 2, “General Issues” Chapter 5, “FirmwareDownload Errors” Chapter 7, “Virtual Fabrics” 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, “Configuration Issues” E_Port failed to come online Corr
1 TABLE 2 Questions for common symptoms Common symptoms Symptom Areas to check Chapter No connectivity between host and storage Cables SCSI timeout errors SCSI retry errors Zoning Chapter 3, “Connections Issues” Chapter 8, “ISL Trunking Issues” Chapter 9, “Zone Issues” Chapter 10, “FCIP Issues” No connectivity between switches Licensing Fabric parameters Segmentation Virtual Fabrics Zoning, if applicable Chapter 2, “General Issues” Chapter 3, “Connections Issues” No light on LEDs Links Chapter
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 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.
Building a case for your switch support provider 1 Capturing command output 1. Connect to the switch through a Telnet or SSH utility. 2. Log in using an account assigned to the admin role. 3. Set the Telnet or SSH utility to capture output from the screen. Some Telnet or SSH utilities require this step to be performed prior to opening up a session. Check with your Telnet or SSH utility vendor for instructions. 4. Type the command or start the process to capture the required data on the console.
1 Building a case for your switch support provider Use the switchShow command to determine the answer. • Are there security policies turned on in the fabric? If so, what are they? (Gather the output from the following commands: secPolicyShow fddCfg --showall ipFilter --show authUtil --show secAuthSecret --show fipsCfg --showall Is the fabric redundant? If yes, what is the MPIO software? (List vendor and version.) • 5. If you have a redundant fabric, did a failover occur? 6.
Building a case for your switch support provider 1 • 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.) 8. If this is a Brocade 48000, Brocade DCX or DCX-4S enterprise-class platform, are the CPs in-sync? Yes or no. Use the haShow command to determine the answer. 9.
1 10 Building a case for your switch support provider Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01
Chapter 2 General Issues In this chapter • Licensing issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Time issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Switch message logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Switch boot issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Switch message logs Switch message logs Switch message logs (RAS logs) contain information on events that happen on the switch or in the fabric. This is an effective tool in understanding what is going on in your fabric or on your switch. Weekly review of the RAS logs is necessary to prevent minor problems from becoming larger issues, or in catching problems at an early stage. Below are some common problems that can occur with or in your system message log.
Switch message logs Symptom 2 I2C bus errors are appearing in the switch log. Probable cause and recommended action I2C bus errors generally indicate defective hardware or poorly seated devices or blades; the specific item is listed in the error message. See the Fabric OS Message Reference for information specific to the error that was received. Some Chip-Port (CPT) and Environmental Monitor (EM) messages contain I2C-related information.
2 Switch boot issues Checking the power supply 1. Log in to the switch as user. 2. Enter the psShow command. 3. Check the power supply status. Refer to the appropriate hardware reference manual for details regarding the power supply status. OK Power supply functioning correctly. absent Power supply not present. unknown Power supply unit installed. predicting failure Power supply is present but predicting failure.
Fibre Channel Router connectivity 2 Fibre Channel Router connectivity This section describes tools you can use to troubleshoot Fibre Channel routing connectivity and performance. Generate and route an ECHO The FC-FC Routing Service enables you to route the ECHO generated when an fcPing command is issued on a switch, providing fcPing capability between two devices in different fabrics across the FC router. The fcPing command sends a Fibre Channel ELS ECHO request to a pair of ports.
2 Fibre Channel Router connectivity 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.
Fibre Channel Router connectivity 2 Round-trip min/avg/max = 1012/1136/1442 usec Pinging 21:00:00:20:37:25:ad:05 [0x211e8] with 12 bytes of data: Request rejected Request rejected Request rejected Request rejected Request rejected 5 frames sent, 0 frames received, 5 frames rejected, 0 frames timeout Round-trip min/avg/max = 0/0/0 usec Example To use fcPing with a single destination (in this example, the destination is a device node WWN): switch:admin> fcping 20:00:00:00:c9:3f:7c:b8 Destination: 20:00:00:
2 Fibre Channel Router connectivity Where: destination_switch Specifies the destination switch. The destination switch can be identified by its Domain ID, by the switch WWN, or by the switch name. This operand is optional; if omitted, the command runs interactively. source_port Specifies the port whose path to the destination domain is traced. For bladed systems and ports above 256, the destination is specified as the port index; otherwise, it is the port area. The embedded port (-1) is the default.
Fibre Channel Router connectivity 2 B/s (1s) 0 0 B/s (64s) 1 1 Txcrdz (1s) 0 Txcrdz (64s) 0 F/s (1s) 0 0 F/s (64s) 2743 0 Words 2752748 2822763 Frames 219849 50881 Errors 0 Hop In Port Domain ID (Name) Out Port BW Cost --------------------------------------------------------1 3 10 (web229) 12 1G 1000 Port 3 12 Tx Rx Tx Rx ----------------------------------------------B/s (1s) 36 76 0 0 B/s (64s) 5 5 5 5 Txcrdz (1s) 0 0 Txcrdz (64s) 0 0 F/s (1s) 1 1 0 0 F/s (64s) 0 0 0 0 Words 240434036 2294316 2119951 2
2 Third party applications Third party applications Symptom Replication application works for a while and then an error or malfunction is reported. Probable cause and recommended action Some third party applications will work when they are first set up and then cease to work because of 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.
Chapter 3 Connections Issues 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 1 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 • 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 25 for additional information. Checking the path includes the following for the Host. Verify the following: • • • • • • • • • All aspects of the Host OS. The third-party vendor multi-pathing input/output (MPIO) software if it is being used. The driver settings and binaries are up to date.
Link failures FC4s: FCP [SEAGATE ST318304FC 3 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 FC4s: FCP [SEAGATE ST318304FC 0005] NL N Fabric Port Name: 20:0e:00:60:69:10:9b:5b 051f00; 2,3;50:06:04:82:bc:01:9a:0c;50:06:04:82:bc:01:9a:0c; na FC4s: FCP [EMC SYMMETRIX 5267] Fabric Port Name: 20:0f:00:60
3 Link failures 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. Then change the port speed to 1, 2, 4 or 8Gbps, depending on what speed can be used by both devices. This should correct the negotiation by setting to one speed. 4.
Link failures 3 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. Enter the switchShow command to confirm that the port is active and has a module that is synchronized. If a fabric device or another switch is connected to the switch, the switch port must be online. 2.
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 5. Run the portLoopbackTest on the marginal port. You will need an adapter to run the loopback test for the SFP. Otherwise, run the test on the marginal port using the loopback mode lb=5. Use the different modes shown in Table 5 to test the port. See the Fabric OS Command Reference for additional information on this command. 6. Check the results of the loopback test and proceed as follows: • If the loopback test failed, the port is bad. Replace the port blade or switch.
3 Device login issues 13 13 -14 14 -15 15 -16 16 -17 17 -18 18 -19 19 -20 20 -21 21 -22 22 -23 23 -24 24 -25 25 -26 26 -27 27 -28 28 -29 29 -30 30 -31 31 -32 32 -33 33 -34 34 -35 35 -36 36 -37 37 -38 38 -39 39 -40 40 -41 41 -42 42 -43 43 -44 44 -45 45 -46 46 -47 47 -48 48 -49 49 -50 50 -51 51 -52 52 -53 53 -54 54 -55 55 -56 56 -57 57 -58 58 -59 59 -60 60 -61 61 -62 62 -63 63 -64 64 id (Trunk master) 65 65 -66 66 -67 67 id 68 68 id 69 69 -70 70 -71 71 id 30 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8 N8
Device login issues 72 72 -N8 No_Module 73 73 -N8 No_Module 74 74 -N8 No_Module 75 75 -N8 No_Module 76 76 id N2 Online (upstream)(Trunk master) 77 77 id N4 Online 78 78 -N8 No_Module 79 79 id N2 Online (Trunk master) E-Port F-Port E-Port 3 10:00:00:05:1e:34:d0:05 "1_d1" 10:00:00:06:2b:0f:6c:1f 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.
3 Device login issues • The enc_out are errors that occur outside the frame and usually indicating a bad primitive. To determine if you are having a cable problem, take snapshots of the port errors by using the portErrShow command in increments of 5 to 10 minutes. If you notice the crc_err counter go up, you have a bad or damaged cable, or a bad or damaged device in the path.
Device login issues 3 NOTE When two shared ports on an FC4-48 blade are receiving traffic and the primary port goes offline, all the frames that are out for delivery for the primary port are dropped, but the counters show them as dropped on the secondary port that shares the same area. Error counters increment unexpectedly for the secondary port, but the secondary port is operating properly.
3 Media-related issues 16:52:42.572 16:52:42.572 16:52:42.572 16:52:42.572 PORT PORT PORT PORT Tx3 Rx3 Tx3 Rx3 8 8 8 8 20 20 20 20 22000000,00000000,ffffffff,11020000 22000000,00000000,ffffffff,11020000 22000000,00000000,ffffffff,11030000 22000000,00000000,ffffffff,11030000 NOTE See “Port log” on page 111 for overview information about portLogDump. Media-related issues This section provides procedures that help pinpoint any media-related issues, such as bad cables and SFPs, in the fabric.
Segmented fabrics 3 [-nframes count]—Specify the number of frames to send. [-lb_mode mode]—Select the loopback point for the test. [-spd_mode mode]—Select the speed mode for the test. [-ports itemlist]—Specify a list of user ports to test. Testing components to and from the HBA 1. Connect to the switch and log in as admin. 2. Enter the portTest command (see the Fabric OS Command Reference for information on the command options).
3 Segmented fabrics • • • • • • • • R_A_TOV E_D_TOV Data field size Sequence level switching Disable device probing Suppress class F traffic Per-frame route priority Long distance fabric (not necessary on Bloom-based, Condor, GoldenEye, Condor2, or GoldenEye2 fabrics. For more information regarding these ASIC types, refer to Appendix A, “Switch Type”.) • BB credit • PID format Reconciling fabric parameters individually 1. Log in to one of the segmented switches as admin. 2.
Segmented fabrics 3 Reconciling a domain ID conflict If a domain ID conflict appears, the conflict is only reported at the point where the two fabrics are physically connected. However, there may be several conflicting domain IDs, which appear as soon as the initial conflict is resolved. Typically, the fabric automatically resolves domain conflicts during fabric merges or builds unless Insistent Domain ID (IDID) is configured.
3 38 Segmented fabrics Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01
Chapter Configuration Issues 4 In this chapter • Configupload and download issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 • Brocade configuration form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Configupload 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 Configupload and download issues • The FTP or SCP server’s IP address cannot be contacted. Verify that you can connect to the FTP server. Use your local PC to connect to the FTP server or ping the FTP server. Example of a successful ping C:\>ping 192.163.163.50 Pinging 192.163.163.50 with 32 bytes of data: Reply from 192.163.163.50: bytes=32 time=5ms TTL=61 Ping statistics for 192.163.163.
Configupload and download issues 4 • On a Virtual Fabric-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 will be able to determine what works and what does not work. Knowing which change corrected the problems will help you to avoid this problem in future endeavors. Symptom The configuration download fails.
4 Brocade configuration form Messages captured in the logs Configuration download generates both RASLog and Audit log messages resulting from execution of the configDownload command.
Chapter 5 FirmwareDownload Errors In this chapter • Blade troubleshooting tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Firmware download issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Troubleshooting firmwareDownload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • USB error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 5 The server is inaccessible or firmware path is invalid. Please make sure the server name or IP address, the user/password and the firmware path are valid. Symptom Cannot download the requested firmware. Probable cause and recommended action The firmware you are trying to download on the switch is incompatible. Check the firmware version against the switch type. If the firmware is incompatible, retrieve the correct firmware version and try again.
5 Troubleshooting firmwareDownload 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 47.
Considerations for downgrading firmware TABLE 9 5 USB error handling Scenario under which download fails Error handling Action An access error occurs during firmwaredownload because the removal of the USB device, or USB device hardware failure, etc. Firmwaredownload will timeout and commit will be started to repair the partitions of the CPUs that are affected. See previous table for details. None. USB device is not enabled.
5 Considerations for downgrading firmware 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/v6.1.0 Password: Verifying the input parameters ... Checking system settings for firmwaredownload... The following items need to be addressed before downloading the specified firmware: AP BLADE type 43 is inserted. Please use slotshow to find out which slot it is in and remove it. Firmwaredownload command failed.
Considerations for downgrading firmware Message 5 Cannot upgrade directly to v6.0. Upgrade your switch to v5.2.1_NI1 or v5.3.0 first before upgrading to the requested version. Probable cause and recommended action If the switch is running v5.2.1 or earlier, you will not be allowed to upgrade directly to v6.0 because of the “two-version” rule. Upgrade your switch to Fabric OS version v5.2.1_NI1 or v5.3.0 before upgrading to v6.
5 Considerations for downgrading 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. The chassisConfig option was set to 1, 2, 3 or 4, which are not supported in v6.1.0, so the firmware download operation was aborted.
Considerations for downgrading firmware Message 5 Downgrade is not allowed because VF is enabled. Please run "lscfg --config" and "lscfg --delete" commands to remove the non-default LS first, then run "fosconfig --disable vf" to disable VF before proceeding. Probable cause and recommended action You cannot downgrade because Virtual Fabrics are enabled. Delete the logical switches, delete the base switch, and disable Virtual Fabrics prior to downgrading the firmware.
5 Considerations for downgrading firmware Routing This message refers to any route settings that need to be changed prior to downgrading the switch’s firmware. Message Downgrade is not allowed because IOD Delay value is configured for one or more domains. Please use \"ioddelayshow and ioddelayreset\" to disable them before downgrading. Probable cause and recommended action If the switch is running v6.2.
Chapter 6 Security Issues In this chapter • Password issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Device authentication issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Protocol and certificate management issues . . . . . . . . . . . . . . . . . . . . . . . . • SNMP issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FIPS issues. . . . . . . . . . . . . . .
6 Device authentication 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 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 issues • If not sure about the problem area, collect a supportSave -n from all switches in the fabric. • If you think it may be related to E_Port authentication then collect a supportSave -n from both switches of the affected E_Port. • If you think this is a policy-related issue, FCS switch or other security server-related issue then use supportSave -n to collect data from the Primary FCS switch and all affected switches.
FIPS issues 6 The results of all self-tests, for both power-up and conditional, are recorded in the system log or are output to the local console. This includes logging both passing and failing results. If the tests fail on your switch it will constantly reboot. Because boot PROM access is disabled you will not be able to exit out of the reboot. You will need to send the switch back to your switch service provider for repair.
6 58 FIPS issues Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01
Chapter 7 Virtual Fabrics In this chapter • General Virtual Fabric 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 does not support the use of VE_Ports to carry traffic for logical fabrics using XISLs. They can be used to carry FCR traffic through EX_ and VEX_Ports. You should make sure your configuration does not result in the use of VE_Ports in a base switch for logical fabric traffic. • Admin Domains are mutually exclusive with Virtual Fabrics.
Base switch issues Symptom 7 The switch with domain with firmware version has joined the FID fabric and may not be compatible with XISL use. Probable cause and recommended action This message indicates the specified switch in the logical fabric using XISLs is running an incompatible firmware version and must be upgraded to Fabric OS v6.2.0. Base switch issues All logical switches in a fabric should have the same base switch attribute.
7 Logical switch issues Logical switch issues CAUTION When a logical switch is created, all configuration for the logical switch is set to factory defaults. When a logical switch is deleted, all configuration for the logical switch is deleted permanently and is not recoverable. Symptom The indicated slot is empty. Probable cause and recommended action You used the lsCfg command and an empty slot was specified. Reissue the command with the appropriate slot number.
Switch configuration blade compatibility Symptom 7 Unable to remove ports from their current switch. Probable cause and recommended action When moving ports to a switch, they are first removed from the switch in which they reside. This error message is displayed if this step fails. Symptom A non-GE blade is within the slot range. Probable cause and recommended action You are attempting to configure a GE port on a slot that does not contain GE ports.
7 Switch configuration blade compatibility Gathering additional information For Virtual Fabric-related issues, use the following guidelines to gather additional data for your switch support provider: • Perform the supportSave command. • If not sure about the problem area, perform the supportSave command on all chassis and logical switches in the fabric.
Chapter 8 ISL Trunking Issues In this chapter • Link issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 • Buffer credit issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 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 • • • • 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. • The ports are not set to the same long distance mode.
Chapter 9 Zone Issues 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 an “incompatible zone database”.
9 Zone conflicts ATTENTION Be careful using the cfgClear command because it deletes the defined configuration. Table 12 summarizes commands that are useful for debugging zoning issues. TABLE 12 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.
Zone conflicts 9 ATTENTION The cfgClear command clears the zoning database on the switch where the command is run. 6. 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. 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”.
9 Zone conflicts Reordering the zone member list 1. Obtain the output from the cfgShow command for both switches. 2. Compare the order in which the zone members are listed. Members must be listed in the same order. 3. Rearrange zone members so the configuration for both switches is the same. Arrange zone members in alphabetical order, if possible.
Zone conflicts 9 Following is sample output from the fcPing command in which one device accepts the request and another device does not respond to the request: switch:admin> fcping 0x020800 22:00:00:04:cf:75:63:85 Source: 0x20800 Destination: 22:00:00:04:cf:75:63:85 Zone Check: Zoned Pinging 0x020800 with 12 bytes of data: received reply from 0x020800: 12 bytes time:1159 usec received reply from 0x020800: 12 bytes time:1006 usec received reply from 0x020800: 12 bytes time:1008 usec received reply from 0x0
9 Gathering additional information switch:admin> defzone --show Default Zone Access Mode committed - No Access transaction - No Transaction See “Zone conflicts” on page 69 for 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 10 FCIP Issues In this chapter • FCIP tunnel issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCIP links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Port mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FTRACE concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10 FCIP tunnel issues Reply from 11.1.1.2: bytes=64 rtt=0ms 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. Enter the portCmd --traceroute command to the remote tunnel endpoint from both endpoints. portcmd --traceroute ge1 -s 11.1.1.1 -d 11.1.1.2 Traceroute to 11.1.1.2 from IP interface 11.1.
FCIP links Symptom 10 FCIP tunnel goes online and offline. Probable cause and recommended action A bouncing tunnel is one of the most common problems. This issue is usually because of an over commitment of available bandwidth (trying to push 1 Gbps through a pipe that can only sustain 0.5 Gbps). • • • • • • Too much data tries to go over the link. Management data gets lost, queued too long, and timeouts expire. Data exceeds timeouts multiple times. Verify what link bandwidth is available.
10 FCIP links • IP addresses are retained by slot in the system. If FR4-18i blades are moved to different slots without first deleting configurations, errors can be seen when trying to reuse these IP addresses. • The portCmd --ping command only verifies physical connectivity. This command does not verify that you have configured the ports correctly for FCIP tunnels. • One port can be included in multiple tunnels, but each tunnel must have at least one port that is unique to that tunnel.
Port mirroring 10 • Ping and traceroute utility • Performance to determine path characteristics between FCIP endpoints And finally gather the data from the supportSave -n command. See Fabric OS Administrator’s Guide or Fabric OS Command Reference for complete details on these commands 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.
10 Port mirroring • • • • • • • • FC4-16 16-port blade FC4-48 48-port blade FC8-16 16-port blade FC8-32 32-port blade FC8-48 48-port blade FA4-18 application blade FR4-18i routing and FCIP blade FC4-16IP iSCSI blade on Fibre Channel ports only The FC4- and FC8-48 implement 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.
Port mirroring 10 For example, in a three-domain fabric containing switches 4100A, 4100B, and 4100C, a mirror connection that is created between 4100A and 4100B only allows 4100A to add mirror connections for those ports on 4100B. To mirror traffic between 4100A and 4100C, add a mirror connection on 4100C. The first connection defines the restriction on the domain, which can be either the local domain or a remote domain.
10 FTRACE concepts 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 assigned to the admin role. 2.
FTRACE concepts 10 Tracing every FICON event affects performance. To avoid this, the default trace mask is set to 0x80000C7b. The mask is a filter where a bit specifies which frames and events will be captured and displayed. For troubleshooting, you should set the trace mask to 0-0xFFFFFFFF. The following table describes the configurable FTRACE parameters.
10 FTRACE concepts cfg Creates an FTRACE configuration. -a 1|0 Enables or disables ACO. -b value Number of buffers (range 0 to 8). -e 1|0 Enable or disable FTRACE. -i value Display mask value (range 0 to FFFFFFFF). Default is FFFFFFFF. -p value Post trigger percentage value (range 0-100). Default is 5. -r value Number of records (range 0 through 1,677,721). Default us 200000. -s value Trigger mask value (range 00000000 to FFFFFFFF). Default is 00000003.
FTRACE concepts 10 Deleting a configuration for a tunnel 1. Log on to the switch as admin. 2. Enter the portCfg ftrace [slot/]Ge_Port tunnel_Id del command. switch:admin> portcfg ftrace ge1 1 del This deletes the FTRACE configuration for GigE 1, tunnel 1. Displaying FTRACE for a tunnel The portShow command uses the ftrace option to display a trace for a tunnel.
10 FTRACE concepts Buffer 0 will be saved 16000320 bytes will be saved for buffer 0.
FTRACE concepts 10 | | | |Trace Header| Wrap | In | Out | Switch | Switch | | Id | State | Size | Address | Count | OXID | OXID | Date | Time | +-----+-------------+--------+------------+------------+------+------+-------------+----------+ | 0 | unused | 200000 | 0x10010000 | 0 | FFFF | FFFF | | | | 1 | Current | 200000 | 0x10010100 | 0 | FFFF | FFFF | | | | 2 | unused | 200000 | 0x10010200 | 0 | FFFF | FFFF | | | | 3 | unused | 200000 | 0x10010300 | 0 | FFFF | FFFF | | | +-----+-------------+--------+---
10 88 FTRACE concepts Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01
Chapter 11 FICON Fabric Issues In this chapter • FICON issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Troubleshooting FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Troubleshooting FICON CUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Troubleshooting FICON NPIV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 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 11 • 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.
11 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 11 Also refer to Fabric OS Administrator’s Guide and the most recent version of the Fabric OS Release Notes for notes on FICON setup and configuration. • 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.
11 Troubleshooting FICON NPIV Symptom Mainframe RMF utility fails to capture performance data Probable cause and recommended action In Fabric OS v6.0.0, Brocade SilkWorm switches do not fully implement all CUP commands needed to collect all performance data on a switch. Upgrade your switch to Fabric OS v6.1.0, where the performance data is captured.
Chapter 12 iSCSI Issues In this chapter • Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 • Zoning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 • Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Connectivity The following issues deal with the iSCSI FC4-16IP blade connectivity between devices.
12 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 12 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 the defZone --show command. 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.
12 Authentication Enable an appropriate DDSet using the iscsiCfg - -enable ddset command. Check for open transactions using the iscsiCfg - -show transaction command. Commit any open transactions using the iscsicfg - -commit all -f command. Authentication Symptom Cannot set up mutual CHAP. Probable cause and recommended action A CHAP name that matches the IQN of an iSCSI initiator is treated differently in the CHAP database.
Chapter Working With Diagnostic Features 13 In this chapter • About Fabric OS diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 • Diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 • Power-on self test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 • Switch status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13 Power-on self test Most information can be captured using the supportShow or supportSave commands and FTP’d off the switch, but when you are collecting information from commands, 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 13 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.
13 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 13 HEALTHY HEALTHY All ports are healthy For more information on how the overall switch status is determined, see the switchStatusPolicySet command in the Fabric OS Command Reference. Displaying switch information 1. Connect to the switch and log in as admin. 2.
13 Chassis-level diagnostics The switchShow command also displays the following information for ports on the specified switch: Area Part of the 24-bit port ID, which consists of domain, port area number, and optional AL_PA. Area column is only displayed on non-modular platforms. 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.
Port information 13 • chassisEnable — enables all the ports in the chassis • bladeDisable — disables all the ports in the blade • bladeEnable — enables all the ports in the blade Spinfab and porttest If Virtual Fabrics-mode is enabled, the commands spinFab and portTest are online diagnostics that are available only on the default switch. These tests are not supported in the logical switch context. If Virtual Fabrics-mode is not enabled, then these commands are available to the switch.
13 Port information Free_buffer: Overrun: Suspended: Parity_err: 2_parity_err: CMI_bus_err: 0 0 0 0 0 0 Address_err: Lr_in: Lr_out: Ols_in: Ols_out: 0 3 0 0 3 Port part of other ADs: No See the Fabric OS Command Reference for additional portShow command information, such as the syntax for slot or port numbering, displaying IP interfaces on a GbE port, or displaying FCIP tunnel connection or configuration information. Displaying the port statistics 1. Connect to the switch and log in as admin. 2.
13 Port information er_inv_arb open transfer opened starve_stop fl_tenancy nl_tenancy zero_tenancy 0 810 0 409856 0 1715 331135 4 Invalid ARB loop_open loop_transfer FL_Port opened tenancies stopped due to starvation number of times FL has the tenancy number of times NL has the tenancy zero tenancy Displaying a summary of port errors for a switch 1. Connect to the switch and log in as admin. 2. Enter the portErrShow command.
13 Equipment status The portErrShow command output provides one output line per port. See Table 15 for a description of the error types. TABLE 15 Error summary description Error type Description frames tx Frames transmitted frames rx Frames received enc in Encoding errors inside frames crc err Frames with CRC errors crc g_eof CRC errors that occur on frames with good end-of-frame delimiters.
Equipment status 13 • Above minimum—Fan is rotating too quickly. • Unknown—Unknown fan unit installed. • FAULTY—Fan has exceeded hardware tolerance. Displaying the status of a power supply 1. Connect to the switch and log in as admin. 2.
13 System message log System message log The system message, or RAS, log feature enables messages to be saved across power cycles and reboots. The Brocade 48000 director and the Brocade DCX and DCX-4S enterprise-class platforms maintain the same RASlog for each of the two CP blades. Since all RASlog messages will be routed to the Active CP, the message CPU ID is added as part of the RASlog message attribute. RASlog message attribute SLOT is defined to identify the CPU that generated the message.
Port log 13 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. These ranges are for all ports on the switch, not just for one port. When the log is full, the newest log entries overwrite the oldest log entries.
13 Syslogd configuration The portLogDump command output (trace) is a powerful tool that is used to troubleshoot fabric issues. The portLogDump output provides detailed information about the actions and communications within a fabric. By understanding the processes that are taking place in the fabric, issues can be identified and located. The portLogDump command displays the port log, showing a portion of the Fibre Channel payload and header (FC-PH).
Syslogd configuration 13 Configuring the host Fabric OS supports a subset of UNIX-style message severities that default to the UNIX local7 facility. To configure the host, edit the /etc/syslog.conf file to map Fabric OS message severities to UNIX severities, as shown in Table 17.
13 Automatic trace dump transfers switch:admin> syslogdipshow syslog.IP.address.1080::8:800:200C:417A syslog.IP.address.1081::8:800:200C:417A syslog.IP.address.1082::8:800:200C:417A syslog.IP.address.4 10.1.2.4 syslog.IP.address.5 10.1.2.5 syslog.IP.address.6 10.1.2.6 Setting the facility level 1. Connect to the switch and log in as admin. 2. Enter the following command: switch:admin> syslogdfacility -l n n is a number from 0 through 7, indicating a UNIX local7 facility. The default is 7.
Automatic trace dump transfers 13 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.
13 Diagnostic tests not supported by M-EOS 9.6.2 and FOS 6.0 The command only prompts you to continue. 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. NOTE: supportSave will transfer existing trace dump file first, then automatically generate and transfer latest one.
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 18.
A Switch Type TABLE 18 Switch Type 118 Switch type to B-Series model converter B-Series switch model ASIC Base switch speed 64 5300 GoldenEye2 8 Gbit 64-port switch 66 5100 Condor2 8 Gbit 32-port switch 67 Brocade Encryption Switch Condor2 8 Gbit 16-port encryption switch 68 Brocade Encryption Blade Condor2 8 Gbit 16-port encryption blade 69 5410 GoldenEye2 8 Gbit 12-port embedded switch 71 300 GoldenEye2 8 Gbit 16-port switch 72 5480 GoldenEye2 8 Gbit 24-port embedded swit
Appendix B Hexadecimal Hexadecimal, 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 hexadecimal digit stands in place of four binary bits. For example, the decimal numeral 79, whose binary representation is 01001111, is 4F (or 4f) in hexadecimal (4 = 0100, F = 1111).
B Hexadecimal TABLE 19 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
Hexadecimal TABLE 19 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 Decimal 211 212 213 214 215 216 217 218 219 220 Hex d3 d4 d5 d6 d7 d8 d9 da db dc 221 222 223 224 225 226 227 228 229 230 dd de df e0 e1 e2 e3 e4 e5 e6 231 232 233 234 235 236 237 238 239 240 Hex e7 e8 e9 ea eb ec ed ef ee f0 Decimal 241 242 243 244 24
B 122 Hexadecimal Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01
Index A account management lost password recovery options, 54 recovering forgotten passwords, 53 unable to modify switch settings, 54 user forgot password, 4 user unable to change switch settings, 4 B blade errors AP blade type 24 is inserted, 63 faulty, 3, 44 stuck in the ’LOADING’ state, 3, 44 browser troubleshooting certificates, 55 C certificates corrupt, 55 invalid, 55 not installed, 55 troubleshooting, 55 cfgShow, 98 command cfgShow, 98 defZone, 97 fcLunQuery, 96 iscsiCfg, 97 nsShow, 96, 98 portCfg
E E_Port, 21, 27 failed to come online, 3 failed to form, 3 enc_out errors, 32 equipment status, viewing, 108 EX_Ports, 3, 21 F F_Port, 21, 27 fabric issues, 2 merge fails, 3 parameters, 35 parameters, reconcile, 36 segments, 3 fabric merge problem, 67 fabric segmentation configuration mismatch, 69 content mismatch, 69 default zone access, 71 fcPing, 72 Fibre Channel connectivity, 72 incompatible zone database, 69 type mismatch, 69 zone configuration members, 71 zone conflict, 69 zoning problems, 73 fan co
FTRACE configuring, 83 displaying for a tunnel, 85 FICON issues, 83 functional tests, 34 G G_Port, 21, 28 gathering basic switch information, 7 detailed information, 8 FCIP information, 78 FICON information, 90 information for technical support, 5 H host connection failure, 95 iSCSI log out, 98 host application times out, 19 hosts, 2 HTTPS, 55 I I2C bus errors, 13 identifying media-related issues, 34 inaccurate information in the system message log, 12, 20 intermittent connectivity, 3 iSCSI CHAP mutual,
O output from a console, 6 P passwords, recovering forgotten, 53 pathInfo, 17 performance problems, 4 PLOGI, 22 point-to-point initialization failure, 27 port bypassed, 27 disabled, 27 in wrong mode, 27 initialization, 21 loopback, 27 port information, viewing, 105 port mirroring, 21 adding port connections, 81 considerations, 80 deleting port connections, 82 FICON, 80 IOD is enabled, 80 multiple locations, 80 supported hardware, 79 port type E_Port, 21, 27 EX_Port, 21 F_Port, 21, 27 FL_Port, 21 G_Port, 21
switch status, viewing, 102 switch temperature, 13 switchType, 117 symptoms, 2 synchronize switches, 1 syslog messages, 4 T tag field, interpreting, 91 targets, 2 temperature, fan, and power supply, 14 temperature, status of, 109 test a port, 34 a switch, 34 TI zone problem, 67 time is not in-sync, 11 troubleshooting certificates, 55 corrupt certificate, 55 invalid certificate, 55 trunk bounces, 4 failed to form, 4 trunk goes offline and online (bounces), 66 tunnel goes on- and offline, 77 U U_Port, 21 us
128 Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01
