1. Manuals
  2. Brands
  3. Brocade Communications Systems Manuals
  4. Switch
  5. A7533A - Brocade 4Gb SAN Switch Base
  6. Troubleshooting manual

Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Troubleshooting Manual

Brocade fabric os troubleshooting and diagnostics guide v6.2.0 (53-1001187-01, april 2009)
Hide thumbs Also See for A7533A - Brocade 4Gb SAN Switch Base:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Administrator's Manual, Reference Manual
53-1001187-01
24 November 2008
Fabric OS
Troubleshooting and Diagnostics Guide
Supporting Fabric OS v6.2.0

Advertisement

Table of Contents
loading

Related Manuals for Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base

Summary of Contents for Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base

  • Page 1 53-1001187-01 24 November 2008 Fabric OS Troubleshooting and Diagnostics Guide Supporting Fabric OS v6.2.0...
  • Page 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.

  • 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 Chapter 5 FirmwareDownload Errors In this chapter ......... . . 43 Blade troubleshooting tips .
  • Page 6 Buffer credit issues ........66 Chapter 9 Zone Issues In this chapter .
  • Page 7 Connectivity ..........95 Zoning .
  • Page 8 Appendix A Switch Type Appendix B Hexadecimal Index viii Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01...

  • Page 9: About This Document

    About This Document In this chapter • How this document is organized ........ix •...

  • Page 10: Supported Hardware And Software

    • 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. 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...

  • Page 11: Document Conventions

    • 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 •...

  • Page 12: Notes, Cautions, And Warnings

    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.

  • 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, 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.com...

  • Page 14: Document Feedback

    • 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.
  • Page 15 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. Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01...
  • Page 16 Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01...

  • Page 17: Introduction To Troubleshooting

    Chapter Introduction to Troubleshooting In this chapter • Troubleshooting overview ......... 1 •...

  • Page 18: 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 19 Questions for common symptoms TABLE 2 Common symptoms Symptom Areas to check Chapter 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 20 Questions for common symptoms TABLE 2 Common symptoms Symptom Areas to check Chapter No connectivity between host and storage Cables Chapter 3, “Connections Issues” SCSI timeout errors Chapter 8, “ISL Trunking Issues” SCSI retry errors Chapter 9, “Zone Issues” Zoning Chapter 10, “FCIP Issues”...

  • Page 21: Gathering Information For Your Switch Support Provider

    Gathering information for your switch support provider 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).

  • Page 22: Capturing A Supportsave

    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.

  • Page 23: Capturing Command Output

    Building a case for your switch support provider 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.

  • Page 24: Detailed Problem Information

    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...

  • Page 25: Gathering Additional Information

    Building a case for your switch support provider • 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.
  • Page 26 Building a case for your switch support provider Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01...

  • Page 27: General Issues

    Chapter General Issues In this chapter • Licensing issues ..........11 •...

  • Page 28: 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 29: Checking Fan Components

    Switch message logs 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 30: Checking The Power Supply

    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. Power supply functioning correctly.

  • Page 31: Fibre Channel Router Connectivity

    Fibre Channel Router connectivity 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.
  • Page 32 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. •...

  • Page 33: Route And Statistical Information

    Fibre Channel Router connectivity 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>...
  • Page 34 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.

  • Page 35: Performance Issues

    Fibre Channel Router connectivity B/s (1s) B/s (64s) Txcrdz (1s) Txcrdz (64s) F/s (1s) F/s (64s) 2743 Words 2752748 2822763 Frames 219849 50881 Errors Hop In Port Domain ID (Name) Out Port BW Cost --------------------------------------------------------- 1 3 10 (web229) 12 1G 1000 Port ----------------------------------------------- B/s (1s)

  • Page 36: Third Party Applications

    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.

  • Page 37: Connections Issues

    Chapter Connections Issues In this chapter • Port initialization and FCP auto discovery process ....21 • Link issues ........... . 23 •...
  • Page 38 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 39: 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 40: Checking The Name Server (Ns)

    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: •...

  • Page 41: Link Failures

    Link failures FC4s: FCP [SEAGATE ST318304FC 0005] Fabric Port Name: 20:0e:00:60:69:10:9b:5b 051ee8; 3;21:00:00:20:37:d9:6f:eb;20:00:00:20:37:d9:6f:eb; na FC4s: FCP [SEAGATE ST318304FC 0005] Fabric Port Name: 20:0e:00:60:69:10:9b:5b 051eef; 3;21:00:00:20:37:d9:77:45;20:00:00:20:37:d9:77:45; na FC4s: FCP [SEAGATE ST318304FC 0005] 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:69:10:9b:5b...

  • Page 42: Determining A Successful Negotiation

    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.

  • Page 43: Checking For A Point-To-Point Initialization Failure

    Link failures 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.

  • Page 44: Marginal Links

    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.

  • Page 45: Device Login Issues

    Device login issues 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.
  • Page 46 Device login issues No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module...

  • Page 47: Pinpointing Problems With Device Logins

    Device login issues No_Module No_Module No_Module No_Module Online E-Port 10:00:00:05:1e:34:d0:05 "1_d1" (upstream)(Trunk master) Online F-Port 10:00:00:06:2b:0f:6c:1f No_Module Online E-Port 10:00:00:05:1e:34:d0:05 "1_d1" (Trunk master) Pinpointing problems with device logins 1. Log in to the switch as admin. 2. Enter the switchShow command; then, check for correct logins. 3.
  • Page 48 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.
  • Page 49 Device login issues 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.

  • Page 50: Media-Related Issues

    Media-related issues 16:52:42.572 PORT 22000000,00000000,ffffffff,11020000 16:52:42.572 PORT 22000000,00000000,ffffffff,11020000 16:52:42.572 PORT 22000000,00000000,ffffffff,11030000 16:52:42.572 PORT 22000000,00000000,ffffffff,11030000 NOTE “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.

  • Page 51: Testing Components To And From The Hba

    Segmented fabrics [-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.

  • Page 52: Reconciling Fabric Parameters Individually

    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”.)

  • Page 53: Reconciling A Domain Id Conflict

    Segmented fabrics 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.
  • Page 54 Segmented fabrics Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01...

  • Page 55: Configuration Issues

    Chapter Configuration Issues In this chapter • Configupload and download issues ....... . 39 •...
  • Page 56 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...

  • Page 57: 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 58: 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 59: In This Chapter

    Chapter FirmwareDownload Errors In this chapter • Blade troubleshooting tips ........43 •...

  • Page 60: 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 61 Firmware download issues 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.

  • Page 62: Troubleshooting Firmwaredownload

    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.

  • Page 63: Considerations For Downgrading Firmware

    Considerations for downgrading firmware TABLE 9 USB error handling Scenario under which download fails Error handling Action An access error occurs during Firmwaredownload will timeout None. firmwaredownload because the and commit will be started to removal of the USB device, or USB repair the partitions of the CPUs device hardware failure, etc.

  • Page 64: Blade Types

    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.

  • Page 65: Ip Settings

    Considerations for downgrading firmware Message 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”...
  • Page 66 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.

  • Page 67: Port Settings

    Considerations for downgrading firmware Message Downgrade is not allowed because VF is enabled. Please run "lscfg --config" and "lscfg --delete" commands to remove the non-default LS first, then run "fosconfig --disable vf" to disable VF before proceeding. Probable cause and recommended action You cannot downgrade because Virtual Fabrics are enabled.

  • Page 68: 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 69: Security Issues

    Chapter Security Issues In this chapter • Password issues ..........53 •...

  • Page 70: 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 71: 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 72: 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 73 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 74 FIPS issues Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01...

  • Page 75: Virtual Fabrics

    Chapter Virtual Fabrics In this chapter • General Virtual Fabric troubleshooting ......59 •...

  • Page 76: 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 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.

  • Page 77: 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 78: 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 79: 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 80: 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 81: Isl Trunking Issues

    Chapter ISL Trunking Issues In this chapter • Link issues ........... . 65 •...

  • Page 82: 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 83: Zone Issues

    Chapter Zone Issues In this chapter • Overview of corrective action ........67 •...

  • Page 84: 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 85: 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 86: Correcting A Fabric Merge Problem Quickly

    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.

  • Page 87: Changing The Default Zone Access

    Zone conflicts 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.

  • Page 88: Reordering The Zone Member List

    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.

  • Page 89: Checking For Zoning Problems

    Zone conflicts 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...

  • Page 90: Gathering Additional Information

    Gathering additional information switch:admin> defzone show Default Zone Access Mode committed - No Access transaction - No Transaction “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.

  • Page 91: Fcip Issues

    Chapter FCIP Issues In this chapter • FCIP tunnel issues ..........75 •...
  • Page 92 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) 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.

  • Page 93: Fcip Links

    FCIP links Symptom 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).

  • Page 94: Gathering Additional Information

    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.

  • Page 95: Port Mirroring

    Port mirroring • 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...

  • Page 96: Port Mirroring Considerations

    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.

  • Page 97: Port Mirroring Management

    Port mirroring 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.

  • Page 98: Ftrace Concepts

    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.
  • Page 99 FTRACE concepts 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.
  • Page 100 FTRACE concepts 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).
  • Page 101 FTRACE concepts 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.
  • Page 102 FTRACE concepts Buffer 0 will be saved 16000320 bytes will be saved for buffer 0. Write Progress: 491840 of 16000320 bytes sent Write Progress: 1311040 of 16000320 bytes sent Write Progress: 2146624 of 16000320 bytes sent Write Progress: 2965824 of 16000320 bytes sent Write Progress: 3801408 of 16000320 bytes sent Write Progress: 4030784 of 16000320 bytes sent Write Progress: 4309312 of 16000320 bytes sent...
  • Page 103 FTRACE concepts |Trace Header| Wrap | In | Out Switch Switch Id | State Size Address Count | OXID | OXID | Date Time +-----+-------------+--------+------------+------------+------+------+-------------+----------+ unused | 200000 | 0x10010000 | 0 | FFFF | FFFF | Current | 200000 | 0x10010100 | 0 | FFFF | FFFF | unused | 200000 | 0x10010200 | 0 | FFFF | FFFF |...
  • Page 104 FTRACE concepts Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01...

  • Page 105: Ficon Fabric Issues

    Chapter FICON Fabric Issues In this chapter • FICON issues ..........89 •...

  • Page 106: Troubleshooting Ficon

    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) •...

  • Page 107: Identifying Ports

    Troubleshooting FICON • 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. •...

  • Page 108: Single-Switch Topology Checklist

    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. •...

  • Page 109: Troubleshooting Ficon Cup

    Troubleshooting FICON CUP 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. •...

  • Page 110: Troubleshooting Ficon Npiv

    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.

  • Page 111: Connectivity

    Chapter iSCSI Issues In this chapter • Connectivity ........... 95 •...
  • Page 112 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 113: 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 114: 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 115: Working With Diagnostic Features

    Chapter Working With Diagnostic Features In this chapter • About Fabric OS diagnostics ........99 •...

  • Page 116: Power-On Self Test

    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.
  • Page 117 Power-on self test 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;...

  • Page 118: 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 119: 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 120: Displaying The Uptime For A Switch

    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.

  • Page 121: Spinfab And Porttest

    Port information • 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.

  • Page 122: Displaying The Port Statistics

    Port information 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 123: Displaying A Summary Of Port Errors For A Switch

    Port information 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 nl_tenancy 331135 number of times NL has the tenancy zero_tenancy zero tenancy Displaying a summary of port errors for a switch 1.

  • Page 124: Equipment Status

    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...

  • Page 125: Displaying The Status Of A Power Supply

    Equipment status • 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. Enter the psShow command: brcd5300:admin>...

  • Page 126: System Message Log

    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.

  • Page 127: Port Log

    Port log 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.

  • Page 128: Syslogd Configuration

    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.

  • Page 129: Configuring The Host

    Syslogd configuration 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 TABLE 17 Fabric OS to UNIX message severities...

  • Page 130: Automatic Trace Dump Transfers

    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. It is necessary to set the facility level only if you specified a facility other than local7 in the host /etc/syslog.conf file.

  • Page 131: Specifying A Remote Server

    Automatic trace dump transfers 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.

  • Page 132: Diagnostic Tests Not Supported By M-Eos 9.6.2 And Fos 6.0

    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.
  • Page 133 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 134 Switch Type TABLE 18 Switch type to B-Series model converter Switch Type B-Series switch model ASIC Base switch speed 5300 GoldenEye2 8 Gbit 64-port switch 5100 Condor2 8 Gbit 32-port switch Brocade Encryption Switch Condor2 8 Gbit 16-port encryption switch Brocade Encryption Blade Condor2 8 Gbit 16-port encryption blade...
  • Page 135 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 136 Hexadecimal TABLE 19 Decimal to Hex conversion table Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Decimal Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01...
  • Page 137 Hexadecimal TABLE 19 Decimal to Hex conversion table Decimal Decimal Decimal Decimal Decimal Decimal Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01...
  • Page 138 Hexadecimal Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01...
  • Page 139 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 140 FICON cascade mode topology checklist E_Port gathering additional information failed to come online identifying ports from the tag field failed to form enc_out errors packets being dropped equipment status, viewing single-switch topology checklist EX_Ports switch does not talk to hosts troubleshooting troubleshooting NPIV FICON CUP...
  • Page 141 FTRACE iscsiCfg configuring commit displaying for a tunnel show FICON issues ISL trunk failed functional tests L_Port G_Port LEDs gathering flashing basic switch information no light detailed information steady FCIP information licensing issues FICON information link information for technical support intermittent connectivty marginal no port LED light...
  • Page 142 portShow ipif iproute output from a console POST power supply PRLI passwords, recovering forgotten pathInfo performance problems RAS logs PLOGI recovering forgotten passwords point-to-point initialization failure replication application breaks port resolving zone conflicts bypassed disabled in wrong mode initialization loopback port information, viewing SCSI port mirroring...
  • Page 143 switch status, viewing viewing switch temperature and saving diagnostic information equipment status switchType fan status symptoms port information synchronize switches port log syslog messages port status power supply status power-on self test switch status temperature status tag field, interpreting the system message log targets Virtual Fabrics temperature, fan, and power supply...
  • Page 144 Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-01...

This manual is also suitable for:

Brocade 8/12cBrocade 8/24c

Table of Contents