Page 1 53-1001340-01 ® 28 July 2009 Fabric OS Troubleshooting and Diagnostics Guide Supporting Fabric OS v6.3.0...
Page 2 Copyright © 2008-2009 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 DCFM, Extraordinary Networks, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
Page 3: Table Of Contents
Contents About This Document In this chapter ..........ix How this document is organized .
Page 4 Time issues ..........11 Switch message logs.
Page 5 Blade troubleshooting tips ....... . . 41 Firmware download issues ....... . . 42 Troubleshooting firmwareDownload .
Page 6 Overview of corrective action ....... 63 Verifying a fabric merge problem ......63 Verifying a TI zone problem .
Page 7 Port log..........87 Viewing the port log .
Page 8 viii Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-01...
Page 9: About This Document
About This Document In this chapter • How this document is organized ........ix •...
Page 10: Supported Hardware And Software
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 exactly which switches are supported and which are not. Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc.
Page 11: Document Conventions
• Information that was deleted: All obsolete information. This information was obsoleted because it was no longer supported in the current version of firmware. FCIP chapter has been moved to the Fibre Channel over IP Administrator’s Guide. FICON chapter has been moved to the FICON Administrator’s Guide. For further information about documentation updates for this release, refer to the release notes.
Page 12: Command Examples
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. Example: show mode egress | ingress Command examples This book describes how to perform configuration tasks using the Fabric OS command line interface, but does not describe the commands in detail.
Page 13: Additional Information
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, go to http://my.brocade.com and 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.com White papers, online demos, and data sheets are available through the Brocade Web site at:...
Page 14: Document Feedback
• 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.: *FT00X0054E9* FT00X0054E9...
Page 15: In This Chapter
Chapter Introduction to Troubleshooting In this chapter • Troubleshooting overview ......... 1 •...
Page 16: Most Common Problem Areas
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. TABLE 1 Common troubleshooting problems and tools Problem area Investigate Tools • •...
Page 17 Questions for common symptoms TABLE 2 Common symptoms Symptom Areas to check Chapter or Document Blade is faulty Firmware or application download Chapter 2, “General Issues” Hardware connections Chapter 5, “FirmwareDownload Errors” Chapter 7, “Virtual Fabrics” Blade is stuck in the “LOADING” state Firmware or application download Chapter 5, “FirmwareDownload Errors”...
Page 18 Questions for common symptoms TABLE 2 Common symptoms Symptom Areas to check Chapter or Document LEDs are steady Links Chapter 3, “Connectivity Issues” License issues Licensing Chapter 2, “General Issues” LSAN is slow or times-out LSAN tagging Chapter 2, “General Issues” Marginal link Links Chapter 3, “Connectivity Issues”...
Page 19: Gathering Information For Your Switch Support Provider
Gathering information for your switch support provider TABLE 2 Common symptoms Symptom Areas to check Chapter or Document User is unable to change switch settings RBAC settings Chapter 6, “Security Issues” Account settings Virtual Fabric does not form FIDs Chapter 7, “Virtual Fabrics” Zone configuration mismatch Effective configuration Chapter 9, “Zone Issues”...
Page 20: Capturing Output From A Console
Building a case for your switch support provider -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. This operand is optional; if omitted, specify the FTP parameters through command line options or interactively.
Page 21: Basic Information
Building a case for your switch support provider Basic information 1. What is the switch’s current Fabric OS level? To determine the switch’s Fabric OS level, type the firmwareShow command and write the information. 2. What is the switch model? To determine the switch model, type the switchshow command and write down the value in the switchType field.
Page 22: Detailed Problem Information
Building a case for your switch support provider Detailed problem information Obtain as much of the following informational items as possible prior to contacting the SAN technical support vendor. Document the sequence of events by answering the following questions: • When did problem occur? •...
Page 23: Gathering Additional Information
Building a case for your switch support provider TABLE 3 Environmental changes Type of Change Date when change occurred Gathering additional information Below are features that require you to gather additional information. The additional information is necessary in order for your switch support provider to effectively and efficiently troubleshoot your issue.
Page 24 Building a case for your switch support provider Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-01...
Page 25: Licensing Issues
Chapter General Issues In this chapter • Licensing issues ..........11 •...
Page 26: Switch Message Logs
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.
Page 27: Switch Boot Issues
Switch boot issues Symptom I2C bus errors are appearing in the switch log. Probable cause and recommended action C 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.
Page 28 FC-FC Routing connectivity The fcPing command sends a Fibre Channel ELS ECHO request to a pair of ports. It performs a zone check between the source and destination. In addition, two Fibre Channel Extended Link Service (ELS) requests will be generated. The first ELS request is from the domain controller to the source port identifier.
Page 29: Route And Statistical Information
FC-FC Routing connectivity Example of one device that accepts the request and another device that rejects the request: switch:admin> fcping 10:00:00:00:c9:29:0e:c4 21:00:00:20:37:25:ad:05 Source: 10:00:00:00:c9:29:0e:c4 Destination: 21:00:00:20:37:25:ad:05 Zone Check: Not Zoned Pinging 10:00:00:00:c9:29:0e:c4 [0x20800] with 12 bytes of data: received reply from 10:00:00:00:c9:29:0e:c4: 12 bytes time:1162 usec received reply from 10:00:00:00:c9:29:0e:c4: 12 bytes time:1013 usec received reply from 10:00:00:00:c9:29:0e:c4: 12 bytes time:1442 usec received reply from 10:00:00:00:c9:29:0e:c4: 12 bytes time:1052 usec...
Page 30 FC-FC Routing connectivity To use pathInfo across remote fabrics, you must specify both the fabric ID (FID) and the domain ID of the remote switch. You cannot use the command to obtain source port information across remote FCR fabrics. When obtaining path info across remote fabrics, the destination switch must be identified by its domain ID.
Page 31: Performance Issues
F/s (64s) Words 240434036 2294316 2119951 2121767 Frames 20025929 54999 162338 56710 Errors Hop In Port Domain ID (Name) Out Port BW Cost --------------------------------------------------------- (web228) (output truncated) For details about the pathInfo command, see the Fabric OS Command Reference. Performance issues Symptom General slow-down in FCR performance and scalability.
Page 32 Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-01...
Page 33: Port Initialization And Fcp Auto Discovery Process
Chapter Connectivity Issues In this chapter • Port initialization and FCP auto discovery process ....19 • Link issues ........... . 21 •...
Page 34 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.
Page 35: Link Issues
Link issues 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.
Page 36: Checking The Logical Connection
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 into the switch. • A device that is logically connected to the switch is registered as an F_, L_, E_, EX_, VE_, VEX_, or N_Port.
Page 37 Connection problems Type Pid PortName NodeName TTL(sec) 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] 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] 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 ST318304FC 0005] Fabric Port Name: 20:0e:00:60:69:10:9b:5b...
Page 38: Link Failures
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.
Page 39: Checking For A Loop Initialization Failure
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.
Page 40: Correcting A Port That Has Come Up In The Wrong Mode
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 the portCfgGPort to force the port to try to come up as point-to-point only.
Page 41: Troubleshooting A Marginal Link
Marginal links 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 the portLoopbackTest to test a marginal link.
Page 42 Marginal links switch:admin> porterrshow frames enc disc link loss loss frjt fbsy err g_eof shrt long eof out c3 fail sync sig ============================================================================ 665k 7.0k 665k 7.4k (output truncated) 3. If you suspect a marginal link, isolate the areas by moving the suspected marginal port cable to a different port on the switch.
Page 43: Device Login Issues
Device login issues Device login issues A correct login is when the port type matches the device type that is plugged in. In the example below, 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.
Page 44 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.
Page 45: Media-Related Issues
Media-related issues 14 Online In_Sync PRESENT ACTIVE F_PORT G_PORT U_PORT LOGICAL_ONLINE LOGIN NOELP LED ACCEPT 15 Online In_Sync PRESENT ACTIVE E_PORT G_PORT U_PORT SEGMENTED LOGIN 6. Enter the portLogDumpPort portid command where the port ID is the port number; then, view the device-to-switch communication.
Page 46: Testing A Port's External Transmit And Receive Path
Media-related issues TABLE 6 Component test descriptions Test name Operands Checks portTest [-ports itemlist] [-iteration count] Used to isolate problems to a single [-userdelay time] [-timeout time] replaceable element and isolate [-pattern pattern] [-patsize size] problems to near-end terminal [-seed seed] [-listtype porttype] equipment, far-end terminal equipment, or transmission line.
Page 47: Segmented Fabrics
Segmented fabrics TABLE 7 Switch component tests Test Function portLoopbackTest Performs a functional test of port N to N path. Verifies the functional components of the switch. turboRamTest Verifies that the on chip SRAM located in the 4 and 8 Gbps ASIC is using the Turbo-Ram BIST circuitry.
Page 48: Downloading A Correct Configuration
Segmented fabrics 4. Enter the configShow -pattern “fabric.ops” command. 5. Compare the two switch configurations line by line and look for differences. Do this by comparing the two Telnet windows or by printing the configShow -pattern “fabric.ops” output. Also, verify that the fabric parameter settings (see the above list) are the same for both switches.
Page 49 Segmented fabrics 9. Press enter on all prompts to accept their default settings. 10. Enter the switchEnable command. This will enable the joining switch to obtain a new domain ID as part of the process of coming online. The fabric principal switch will allocate the next available domain ID to the new switch during this process.
Page 50 Segmented fabrics Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-01...
Page 51: Configupload And Download Issues
Chapter Configuration Issues In this chapter • Configupload and download issues ....... . 37 •...
Page 52 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:\>...
Page 53: Gathering Additional Information
Configupload and download issues • 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.
Page 54: Brocade Configuration Form
Brocade configuration form Messages captured in the logs Configuration download generates both RASLog and Audit log messages resulting from execution of the configDownload command. The following messages are written to the logs: • configDownload completed successfully … (RASLog and Audit log) •...
Page 55: Blade Troubleshooting Tips
Chapter FirmwareDownload Errors In this chapter • Blade troubleshooting tips ........41 •...
Page 56: Firmware Download Issues
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.
Page 57 Firmware download issues Verify the path to the FTP or SCP server is accessible from the switch. For more information on checking your FTP or SCP server, see Chapter 4, “Configuration Issues”. • The USB path is not correct. If your platform supports a USB memory device, verify that it is connected and running. Verify that the path name is correct by using the usbStorage -l command.
Page 58: Troubleshooting Firmwaredownload
Troubleshooting firmwareDownload Perform a firmwareDownload -o command. The operand bypasses the checking of Coordinated HotCode Load (HCL). On single CP systems in interop fabrics, the HCL protocol is used to ensure data traffic is not disrupted during firmware upgrades. This option will allow a firmware download to continue even if HCL is not supported in the fabric or the protocol fails.
Page 59: Usb Error Handling
USB error handling Gathering additional information You should follow these best practices for firmware download before you start the procedure: • Keep all session logs. • Enter the supportSave or the supportShow command before and after entering the firmwareDownload command. •...
Page 60: Blade Types
Considerations for downgrading firmware Upgrade is not allowed because one of the Zones or configs defined on this switch is using a reserved naming prefix "msfr_zn" or "msfr_cfg" please rename them before upgrading. Upgrade is not allowed because Secondary KV is registered. Please deregister the secondary KV and then try again.
Page 61: Firmware Versions
Considerations for downgrading firmware Use the slotShow command to display which slots the Brocade FC8-18 AP blades occupy. Physically remove the blades from the chassis, or use the micro-switch to turn the blade off. Retry the firmware download operation. Firmware versions These messages refer to differences between the current firmware and the firmware you are applying to the switch.
Page 62: Routing
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"...
Page 63: Password Issues
Chapter Security Issues In this chapter • Password issues ..........49 •...
Page 64: Password Recovery Options
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.
Page 65: Protocol And Certificate Management Issues
Protocol and certificate management issues Symptom 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.
Page 66: Snmp Issues
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. •...
Page 67 FIPS issues 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.
Page 68 FIPS issues Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-01...
Page 69: General Virtual Fabric Troubleshooting
Chapter Virtual Fabrics In this chapter • General Virtual Fabric troubleshooting ......55 •...
Page 70: Fabric Identification Issues
Fabric identification issues • VE_Ports cannot exist in a logical switch that has XISL use turned on. Although VE_Ports are allowed in a base switch, Fabric OS v6.2.0 and later do not support the use of VE_Ports to carry traffic for logical fabrics using XISLs. They can be used to carry FCR traffic through EX_ and VEX_Ports.
Page 71: Base Switch Issues
Base switch issues Symptom The switch with domain <domain> with firmware version <fw version> has joined the FID <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.
Page 72: Logical Switch Issues
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.
Page 73: Switch Configuration Blade Compatibility
Switch configuration blade compatibility Symptom 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.
Page 74: Gathering Additional Information
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.
Page 75: In This Chapter
Chapter ISL Trunking Issues In this chapter • Link issues ........... . 61 •...
Page 76: Buffer Credit Issues
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.
Page 77: Overview Of Corrective Action
Chapter Zone Issues In this chapter • Overview of corrective action ........63 •...
Page 78: Segmented Fabrics
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.
Page 79: Zone Conflicts
Zone conflicts Symptom 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. •...
Page 80: Correcting A Fabric Merge Problem Quickly
Zone conflicts TABLE 12 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 defZone...
Page 81: Changing The Default Zone Access
Zone conflicts 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".
Page 82: Checking For Fibre Channel Connectivity Problems
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 ELS (Extended Link Service frame) ECHO request to the source port specified and validates the response.
Page 83: Checking For Zoning Problems
Zone conflicts 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...
Page 84: Gathering Additional Information
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 <port> command. Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-01...
Page 85: Connectivity
Chapter iSCSI Issues In this chapter • Connectivity ........... 71 •...
Page 86 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. This can be controlled by configuring the iSCSI host initiator and the GbE port on the FC4-16IP blade to allow only one connection per session by using the following command: switch:admin>...
Page 87: Zoning
Zoning 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.
Page 88: Authentication
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.
Page 89: About Fabric Os Diagnostics
Chapter Working With Diagnostic Features In this chapter • About Fabric OS diagnostics ........75 •...
Page 90: Power-On Self Test
Power-on self test To save a set of files that customer support technicians can use to further diagnose the switch condition, enter the supportSave command. The command prompts for an FTP server, packages the following files, and sends them to the specified server: •...
Page 91 Power-on self test eth0: Link status change: Link Up. 100 Mbps Full duplex Auto (autonegotiation complete). INITCP: CPLD Vers: 0x95 Image ID: 0x19 uptime: 2008; sysc_qid: 0 Fabric OS (Paulsa45) Paulsa45 console login: 2005/03/31-20:12:42, [TRCE-5000], 0,, INFO, ?, trace:, trace_buffer.c, line: 1170 2005/03/31-20:12:42, [LOG-5000], 0,, INFO, SW4100_P45, Previous message repeat 1 time(s), trace_ulib.c, line: 540 2005/03/31-20:12:43, [HAM-1004], 219,, INFO, SW4100_P45, Processor rebooted -...
Page 92: Disabling Post
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.
Page 93: Displaying Switch Information
Switch status Faulty ports monitor HEALTHY Missing SFPs monitor 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.
Page 94: Displaying The Uptime For A Switch
SpinFab and portTest 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.
Page 95: Port Information
Port information The spinFab command supports the following: • F_Ports and loopback ports • Shared area ports • Logical and base switch ports ATTENTION The diagnostic tests portTest and spinFab are not supported between an M-EOS v9.6.2 and Fabric OS v6.0.0. These tests are designed to work between two Brocade-attached switches. These diagnostics will fail if the B-series switch is linked to an M-series switch.
Page 96: Displaying The Port Statistics
Port information Proc_rqrd: Protocol_err: 0 Timed_out: Invalid_word: 563851 Rx_flushed: Invalid_crc: Tx_unavail: Delim_err: Free_buffer: Address_err: Overrun: Lr_in: Suspended: Lr_out: Parity_err: Ols_in: 2_parity_err: Ols_out: CMI_bus_err: 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.
Page 97: Displaying A Summary Of Port Errors For A Switch
Port information er_type6_miss frames with FTB type 6 miss er_zone_miss frames with hard zoning miss er_lun_zone_miss frames with LUN zoning miss er_crc_good_eof Crc error with good eof er_inv_arb Invalid ARB open loop_open transfer loop_transfer opened 409856 FL_Port opened starve_stop tenancies stopped due to starvation fl_tenancy 1715 number of times FL has the tenancy...
Page 98: Equipment Status
Equipment status The portErrShow command output provides one output line per port. See Table 13 for a description of the error types. TABLE 13 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...
Page 99: Checking The Status Of The Fans
Equipment status 5. Check the power supply status. If any power supplies show a status other than OK, consider replacing the power supply as soon as possible. Checking the status of the fans 1. Connect to the switch and log in as admin. 2.
Page 100: Checking Temperature Status
System message log Checking temperature status 1. Connect to the switch and log in as admin. 2. Enter the tempShow command: switch:admin> tempshow Sensor State Centigrade Fahrenheit ================================================= Information displays for each temperature sensor in the switch. The possible temperature status values are: •...
Page 101: Port Log
Port log Displaying the system message log, with no page breaks 1. Connect to the switch and log in as admin. 2. Enter the errDump command. Displaying the system message log one message at a time 1. Connect to the switch and log in as admin. 2.
Page 102 Port log 16:48:47.263 PORT 02fffffd,00fffffd,02e4ffff,14000000 16:48:47.263 PORT c0fffffd,00fffffd,02e401c2,00000001 16:48:47.263 FCPH read 02fffffd,00fffffd,c0000000,00000000,02e401c2 16:48:47.263 FCPH 22380000,02e401c2,00000c1e,0000001c,00000000 <output truncated> Use the commands summarized in Table 14 to view and manage port logs. See the Fabric OS Command Reference for additional information about these commands. TABLE 14 Commands for port log management Command...
Page 103: Syslogd Configuration
Syslogd configuration 20:29:32.638 FCPH 00300000,00000000,000005f4,00020182,00000000 20:29:32.639 PORT 02fffffd,00fffffd,09aaffff,14000000 <output truncated> Syslogd configuration The system logging daemon (syslogd) is an IP-based service for logging system messages made available by default on Unix and Linux operating systems. It is available as a third-party application for Windows operating systems.
Page 104: Automatic Trace Dump Transfers
Automatic trace dump transfers Specifying syslogd hosts 1. Connect to the switch and log in as admin. 2. Enter the syslogdIpAdd command and specify an IP address. 3. Verify that the IP address was entered correctly, using the syslogdIpShow command. The syslogdIpadd command accepts IPv4 and IPv6 addresses.
Page 105: Specifying A Remote Server
Automatic trace dump transfers Setting up for automatic transfer of diagnostic files involves the following tasks: • Specifying a remote server to store the files. • Enabling the automatic transfer of trace dumps to the server. (Trace dumps overwrite each other by default;...
Page 106 Automatic trace dump transfers Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-01...
Page 107 Appendix 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.
Page 108 Switch Type TABLE 16 switchType to B-Series model converter switchType B-Series switch model ASIC Base switch speed 5000 Condor 4 Gb 32-port switch 4424 GoldenEye 2 Gb 24-port embedded switch Brocade DCX Condor2 8 Gb 798-port core fabric backbone 5300 GoldenEye2 8 Gb 64-port switch 5100...
Page 109 Appendix 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.
Page 110 Hexadecimal TABLE 17 Decimal to Hex conversion table Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-01...
Page 111 Hexadecimal TABLE 17 Decimal to Hex conversion table Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-01...
Page 112 Hexadecimal Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-01...
Page 113 Index configuration download fails save to a host account management switch reboots during the download lost password recovery options upload fails recovering forgotten passwords connectivity unable to modify switch settings no connectivity between host and storage user forgot password no connectivity between switches user unable to change switch settings contacting your switch support provider core file warning messages...
Page 114 firmwareDownload errors AP blade type 24 is inserted blade application firmware failed E_Port blade application firrmware failed failed to come online blade errors failed to form blade is faulty enc_out errors blade is stuck in the ‘LOADING’ state equipment status, viewing cannot download the requested firmware EX_Ports cannot download with interop mode turned on...
Page 115 iSCSI CHAP mutual database Name Server, (See also NS) Easy create cannot find any LUNs on the target network time protocol, (See also NTP) GE_Ports cannot go to Online state no connectivity between host and storage host cannot discover any targets no connectivity between switches host cannot mount any disks no light on LEDs...
Page 116 portErrShow switch message logs crc_err counter errors switch panic crc_g_eof counter errors switch reboots during the configuration download disc_c3 errors switch status, viewing enc_out errors switchType frames tx and rx errors symptoms portFlagsShow synchronize switches portLogDumpPort syslog messages portloopbacktest portShow ipif iproute POST...
Page 117 viewing and saving diagnostic information equipment status fan status port information port log port status power supply status power-on self test switch status temperature status the system message log Virtual Fabrics E_Ports directly connecting two logical switches does not form firmwaredownload errors general troubleshooting Virutal Fabrics...
Page 118 Fabric OS Troubleshoot and Diagnostics Guide 53-1001340-01...

This manual is also suitable for:

Am866a - storageworks 8/8 base san switch 8/24 8/40 8/8 8/80

Brocade Communications Systems 1606 Troubleshooting Manual

Table of Contents

Chapter 1 Introduction to Troubleshooting

Chapter 2 General Issues

Connectivity Issues

Chapter 3 Connectivity Issues

Chapter 4 Configuration Issues

Chapter 9 Zone Issues

Chapter 11 Working with Diagnostic Features

Chapter 6 Security Issues

Chapter 7 Virtual Fabrics

Chapter 8 ISL Trunking Issues

Chapter 10 Iscsi Issues

11 In this Chapter

Quick Links

Chapters

Troubleshooting

Related Manuals for Brocade Communications Systems 1606

Summary of Contents for Brocade Communications Systems 1606

This manual is also suitable for:

Table of Contents