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 troubleshooting and diagnostics guide v6.1.0 (53-1000853-01, june 2008)
Hide thumbs Also See for A7533A - Brocade 4Gb SAN Switch Base:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Administrator's Manual
53-1000853-01
12 March 2008
Fabric OS
Troubleshooting and Diagnostics Guide
Supporting Fabric OS v6.1.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-1000853-01 12 March 2008 Fabric OS Troubleshooting and Diagnostics Guide Supporting Fabric OS v6.1.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 Switch Message Logs ........11 Checking fan components.
  • Page 5 Troubleshooting firmwareDownload ......41 Gathering additional information ......41 Brocade DCX error handling .
  • Page 6 Chapter 9 FCIP Issues In this chapter ......... . . 69 FCIP tunnel issues.
  • Page 7 Port information ......... 96 Viewing the status of a port .
  • Page 8 viii Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-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 11, “iSCSI Issues,” provides information and procedures specific to Brocade 48000 and Brocade DCX models. Because these models have CP blades that support the iSCSI feature. • Chapter 12, “Working With Diagnostic Features,” provides procedures for use of the Brocade Adaptive Networking suite of tools, including Traffic Isolation, QoS Ingress Rate Limiting, and QoS SID/DID Traffic Prioritization.

  • Page 11: Document Conventions

    Document conventions This section describes text formatting conventions and important notice formats used in this document. Text formatting The narrative-text formatting conventions that are used are as follows: bold text Identifies command names Identifies the names of user-manipulated GUI elements Identifies keywords and operands Identifies text to enter at the GUI or CLI italic text...

  • Page 12: Key Terms

    Key terms For definitions specific to Brocade and Fibre Channel, see the Brocade Glossary. For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary http://www.snia.org/education/dictionary Additional information This section lists additional Brocade and industry-specific documentation that you might find helpful.

  • Page 13: Getting Technical Help

    Getting technical help Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. To expedite your call, have the following information available: 1. General Information • Switch model • Switch operating system version •...

  • Page 14: Document Feedback

    For the Brocade 4016, 4018, 4020, and 4024 embedded switches: Provide the license ID. Use the licenseIdShow command to display the WWN. Document feedback Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document.

  • Page 15: Introduction To Troubleshooting

    Chapter Introduction to Troubleshooting This chapter provides information on troubleshooting and the most common procedures to use to diagnose and recover from problems. This book is a companion guide to be used in conjunction with the Fabric OS Administrator’s Guide. Although it provides a lot of common troubleshooting tips and techniques it does not teach troubleshooting methodology.

  • 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 BadRootDev errors Firmware versions on switch Chapter 5, “FirmwareDownload Errors” Blade is faulty Firmware or application download Chapter 2, “General Issues” Hardware Chapter 5, “FirmwareDownload Errors” 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 SCSI retry errors Buffer credits Chapter 9, “FCIP Issues” FCIP tunnel bandwidth SCSI timeout errors Links Chapter 3, “Connections Issues” Chapter 7, “ISL Trunking Issues” Buffer credits Chapter 9, “FCIP Issues”...

  • Page 19: 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 20: 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 supportSave command. When invoked without operands, this command goes into interactive mode.The following operands are optional: -n Does not prompt for confirmation.

  • Page 21: Building A Case For Your Switch Support Provider

    Building a case for your switch support provider Building a case for your switch support provider The following form should be filled out in its entirety and presented to your switch support provider when you are ready to contact them. Having this information immediately available will expedite the information gathering process that is necessary to begin determining the problem and finding a solution.
  • Page 22 Building a case for your switch support provider • What happened prior to the problem? • Is the problem reproducible? • If so, what are the steps to produce the problem? • What configuration was in place when the problem occurred? •...

  • Page 23: Gathering Additional Information

    Building a case for your switch support provider Gathering additional information Below are features that require you to gather additional information. The additional information is necessary in order for your switch support provider to effectively and efficiently troubleshoot your issue. Refer to the chapter specified for the commands whose data you need to capture. •...
  • Page 24 Building a case for your switch support provider Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01...

  • Page 25: In This Chapter

    Chapter General Issues This chapter provides information on troubleshooting and the most common procedures to use to recover from licensing and common switch log errors. In this chapter • Licensing issues ..........11 •...

  • Page 26: Checking Fan Components

    Switch Message Logs Symptom Inaccurate information in the system message log Probable cause and recommended action In rare instances, events gathered by the track change feature can report inaccurate information to the system message log. For example, a user enters a correct user name and password, but the login was rejected because the maximum number of users had been reached.

  • Page 27: Checking The Switch Temperature

    Fibre Channel Routing 3. Check the fan status and speed output. If any of the fan speeds display abnormal RPMs, replace the fan. You may first consider re-seating the fan (unplug it and plug it back in). Checking the switch temperature 1.

  • Page 28: Checking For Fibre Channel Connectivity Problems

    Fibre Channel Routing Checking for Fibre Channel connectivity problems 1. On the edge Fabric OS switch, make sure that the source and destination devices are properly configured in the LSAN zone before entering the fcPing command. This command performs the following functions: •...

  • Page 29: Third Party Applications

    Third party applications Third party applications Symptom Replication application works for a while and then breaks. Probable cause and recommended action Some third party applications will work when they are first set up and then cease to work due to an incorrect parameter setting.
  • Page 30 Third party applications Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01...

  • Page 31: Connections Issues

    Chapter Connections Issues This chapter provides information on troubleshooting basic connectivity issues and the most common procedures to use to diagnose and recover from basic connection problems. In this chapter • Port initialization and FCP auto discovery process ....17 •...
  • Page 32 Port initialization and FCP auto discovery process Figure 1 shows the process behind port initialization. Understanding this process can help you determine where a problem resides. For example, if your switch cannot form an E_Port, you understand that the process never got to that point or does not recognize the switch as an E_Port. Possible solutions would be to look at licensing and port configuration.

  • Page 33: Link Issues

    Link issues Link issues Symptom LEDs are flashing. Probable cause and recommended action Depending on the rate of the flash and the color of the LED this could mean several things. To determine what is happening on either your port status LED or power status LED, refer to that switch’s model hardware reference manual.

  • Page 34: Checking The Name Server (Ns)

    Connection problems • A device that is not logically connected to the switch will be registered as a G_ or U_Port. If NPIV is not on the switch, the N_Port is another possible port type. 3. If the missing device is logically connected, proceed to the next troubleshooting procedure (“Checking the name server (NS)”...

  • Page 35: Link Failures

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

  • Page 36: Determining A Successful Negotiation

    Link failures NOTE Skip this procedure if the port speed is set to a static speed through the portCfgSpeed command. Determining a successful negotiation 1. Enter the portCfgShow command to display the port speed settings of all the ports. 2. Enter the switchShow command to determine if the port has module light. 3.

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

    Link failures 11:40:02.078 PORT 22000000,00000000,ffffffff,11050100 Received LISA frame The LISA frame indicates that the loop initialization is complete. 3. Skip point-to-point initialization by using the portCfgLport Command. The switch changes to point-to-point initialization after the LISA phase of the loop initialization. This behavior sometimes causes trouble with old HBAs.

  • Page 38: 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 39: Device Login Issues

    Device login issues • If the loopback test did not fail, the SFP was bad. 7. Perform the following steps to rule out cabling issues: a. Insert a new cable in the suspected marginal port. b. Enter the portErrShow command to determine if a problem still exists. •...
  • Page 40 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 41: Pinpointing Problems With Device Logins

    Device login issues 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. Enter the portCfgShow command to see if the port is configured correctly. In some cases, you may find that the port has been locked as an L_Port and the device attached is a fabric point-to-point device such as a host or switch.
  • Page 42 Device login issues switch:admin> porterrshow frames enc disc link loss loss frjt fbsy err shrt long c3 fail sync ===================================================================== 364k 6.1k 2.6g 4.1g 150k 3.7g 2.0g 2.2g 2.9g 241k 4.3k 113m 2.4g 331m 359m 249m 1.4k 2.3k 156m 171m 10m 1.4k 3.0g 1.1g 117k...

  • Page 43: Media-Related Issues

    Media-related issues 6. Enter the portLogDumpPort portid command where the port ID is the port number; then, view the device-to-switch communication. switch:admin> portlogdump 13 time task event port cmd args ------------------------------------------------- Tue Apr 24 19:45:58 2007 19:45:58.728 PORT 22000000,00000000,ffffffff,11010000 19:45:58.778 SPEE 000000f0,00000000,00000000 19:45:58.787...

  • Page 44: Testing A Port's External Transmit And Receive Path

    Media-related issues Testing a port’s external transmit and receive path 1. Connect to the switch and log in as admin. 2. Connect the port you want to test to any other switch port with the cable you want to test. 3.

  • Page 45: Segmented Fabrics

    Segmented fabrics Segmented fabrics Fabric segmentation is generally caused by one of the following conditions: • Incompatible fabric parameters (see “Reconciling fabric parameters individually,” next). • Incorrect PID setting (see Fabric OS Administrator’s Guide). • Incompatible zoning configuration (see Chapter 8, “Zone Issues”).

  • Page 46: Downloading A Correct Configuration

    Segmented fabrics See the Fabric OS Command Reference for more detailed information. 9. Enable the switch by entering the switchEnable command. Alternatively, you can reconcile fabric parameters by entering the configUpload command for each switch. Downloading a correct configuration You can restore a segmented fabric by downloading a previously saved correct backup configuration to the switch.

  • Page 47: Configuration Issues

    Chapter Configuration 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. As part of standard configuration maintenance procedures, it is recommended that you back up all important configuration data for every switch on a host computer server for emergency reference.
  • Page 48 Configupload and download issues Example of a successful ping C:\>ping 192.163.163.50 Pinging 192.163.163.50 with 32 bytes of data: Reply from 192.163.163.50: bytes=32 time=5ms TTL=61 Ping statistics for 192.163.163.50: Packets: Sent = 4, Received = 4, Lost = 0 (0%loss), Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 5ms, Average = 4ms If your ping is successful from your computer, but you cannot reach it from inside your data center, there could be a block on the firewall to not allow FTP connections from inside the data...

  • Page 49: Gathering Additional Information

    Configupload and download issues Symptom The configuration download fails. Probable cause and recommended action Check the following: • The FTP or SCP server’s host name is known to the switch. Verify with your network administrator that the switch has access to the FTP server. •...

  • Page 50: Brocade Configuration Form

    Brocade configuration form • configUpload completed successfully … (RASLog) • configDownload not permitted … (Audit log) • configUpload not permitted … (RASLog) • (Warning) Downloading configuration without disabling the switch was unsuccessful. (Audit log) Brocade configuration form Use this form as a hard copy reference for your configuration information. In the hardware reference manuals for the Brocade 48000 and DCX modular switches there is a guide for FC port setting tables.

  • Page 51: Firmwaredownload Errors

    Chapter FirmwareDownload Errors This chapter contains procedures to troubleshoot and fix common firmware download issues relating to a switch or an enterprise-class switch. In this chapter • Blade troubleshooting tips ........37 •...

  • Page 52: Firmware Download Issues

    Firmware download issues Brocade 48000 with FA4-18 or a FC10-6 blades: If you are running Fabric OS v5.3.0, then you cannot downgrade to earlier versions without removing the blades. Brocade 48000 with FC8-16 blades: If you are running Fabric OS v6.0, then you cannot downgrade to earlier versions without removing the blade.
  • Page 53 Firmware download issues Available space on usbstorage 74% Example of error message Stealth200E:admin> firmwaredownload Server Name or IP Address: 192.126.168.115 User Name: jdoe File Name: /users/home/jdoe/firmware/v6.1.0 Network Protocol(1-auto-select, 2-FTP, 3-SCP) [1]: 2 Password: Checking system settings for firmwaredownload... Protocol selected: FTP Trying address-->AF_INET IP: 192.126.168.115, flags : 2 Firmware access timeout.
  • Page 54 Firmware download issues Symptom You receive a BadRootDev error message. Probable cause and recommended action You perform a firmwaredownload on a 3900 or 4100 (a single-bladed/4.x switch). During the firmwaredownload process the boot environment variables are incorrectly set and causes a BadRootDev error message to appear.

  • Page 55: 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 56 Brocade DCX error handling TABLE 9 Brocade DCX CP Error Handling Scenario When Scenario Error handling Required Action During During downloading to When the main CPU boots up, Restart step 1 the main CPU of the firmwareDownload is aborted. firmwareDownload standby CP, if an error after the repair is The firmwareCommit command will...
  • Page 57 Brocade DCX error handling TABLE 9 Brocade DCX CP Error Handling Scenario When Scenario Error handling Required Action During When downloading to When the co-CPU on the standby CP Restart step 7 the co CPU of the boots up, firmwareDownload is firmwareDownload standby CP, if an error aborted.

  • Page 58: Usb Error Handling

    USB error handling USB error handling The following table outlines how the USB device handles errors under specific scenarios and details what actions you should take after the error occurs. TABLE 10 USB error handling Scenario under which download fails Error handling Action An access error occurs during...

  • Page 59: Blade Types

    Considerations for downgrading firmware This example shows hardware-related messages for the same downgrade example: director:admin> firmwaredownload Type of Firmware (FOS, SAS, or any application) [FOS]: Server Name or IP Address: 192.168.32.10 Network Protocol (1-auto-select, 2-FTP, 3-SCP) [1]: User Name: userfoo File Name: /home/userfoo/dist/v5.3.0 Password: Verifying the input parameters ...
  • Page 60 Considerations for downgrading firmware Message AP Blade type 33 is inserted. Please use slotshow to find out which slot it is in and remove it. Cannot downgrade due to the presence of AP BLADE type 33. Remove or power off these blades before proceeding.

  • Page 61: Firmware Versions

    Considerations for downgrading firmware Message SW Blade type 51 is inserted. Please use slotshow to find out which slot it is in and remove it. Probable cause and recommended action The firmware download operation was attempting to downgrade a system to Fabric OS v5.3.0 or earlier with one or more Brocade FC8-48 port blades (blade ID 51) in the system.

  • Page 62: Ip Settings

    Considerations for downgrading firmware Upgrade your switch to Fabric OS version v5.1.0 or v5.2.0 before upgrading to v5.3.0 Message Firmwaredownload of blade application firmware failed. Reissue firmwareDownload to recover. Probable cause and recommended action The firmware download operation was attempting to upgrade the SAS image while the blade was operational.

  • Page 63: Platform

    Considerations for downgrading firmware Platform These messages are switch features or fabric-wide settings that need to be removed or disabled before downgrading the firmware. Message Only platform option 5 is supported by version 6.1.0. Use chassisconfig to reset the option before downloading the firmware.
  • Page 64 Considerations for downgrading firmware Message The active security DB size is greater than 256 KB, you will not be allowed to downgrade to below v6.0.0. Probable cause and recommended action You cannot downgrade because the active security database size is greater than 256 KB. Reduce the size before downgrading.

  • Page 65: Port Settings

    Considerations for downgrading firmware Port settings These messages refer to port settings that need to be fixed before downgrading the switch’s firmware. Message Cannot downgrade to v5.2.0 or lower due to GE port(s) has MTU size configured between 1261 to 1499 bytes.
  • Page 66 Considerations for downgrading firmware Message The command failed due to presence of long-distance ports in L0.5 mode. Please remove these settings before proceeding. Probable cause and recommended action The firmware download operation was attempting to upgrade a system to Fabric OS v6.0.0 with long-distance ports in L0.5, L1, or L2 modes.
  • Page 67 Considerations for downgrading firmware Specify LE mode is used for E_Ports for distances beyond 5 Km and up to 10 Km. A total of 5, 10, or 20 full-size frame buffers are reserved for port speeds of 1 Gbps, 2 Gbps, or 4 Gbps, respectively.

  • Page 68: Routing

    Considerations for downgrading firmware Use the portDisable command to disable these ports before proceeding. Routing These error messages refer to routing policies. Message Cannot downgrade to v5.1.0 because Device Based routing policy is not supported by v5.1.0. Use aptPolicy to change the routing policy before proceeding. Probable cause and recommended action The firmware download operation was attempting to upgrade a system to Fabric OS v5.1.0 with device-based routing policy selected.
  • Page 69 Considerations for downgrading firmware Message Cannot downgrade due to the presence of broadcast zone(s). Remove or disable them before proceeding. Probable cause and recommended action If the switch is running v5.3.0 or later, and a “broadcast zone” is configured, you cannot downgrade the switch to v5.2.0 or earlier, as a broadcast zone gets a special meaning in v5.3.0, but it will be treated as regular zone in v5.2.0 or earlier.
  • Page 70 Considerations for downgrading firmware Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01...

  • Page 71: In This Chapter

    Chapter Security Issues This chapter provides troubleshooting information and procedures on security for the switch management channel. In this chapter • Password issues ..........57 •...

  • Page 72: Password Recovery Options

    Protocol and certificate management issues Symptom Unable to log into the boot PROM. Probable cause and recommended action To recover a lost boot PROM password, contact your switch service provider. You must have previously set a recovery string to recover the boot PROM password. This does not work on lost or forgotten passwords in the account database.

  • Page 73: Gathering Additional Information

    Protocol and certificate management issues Symptom Troubleshooting certificates Probable cause and recommended action If you receive messages in the browser or in a pop-up window when logging in to the target switch using HTTPS, refer to Table 12 for recommended actions you can take to correct the problem. TABLE 12 SSL messages and actions Message...

  • Page 74: Snmp Issues

    SNMP issues SNMP issues This section describes symptoms with associated causes and recommended actions for SNMP-related issues. Symptom SNMP management station server is unable to receive traps from fabric. Probable cause and recommended action There are several causes related to this generic issue. You will need to verify the following: •...

  • Page 75: In This Chapter

    Chapter ISL Trunking Issues This chapter describes symptoms and solutions to trunking problems as well as recommended actions to take to correct trunking problems. In this chapter • Link issues ........... . 61 •...

  • 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 you want to communicate.

  • Page 77: In This Chapter

    Chapter Zone Issues This chapter describes troubleshooting techniques and recommended actions for common zoning problems. In this chapter • Overview of corrective action ........63 •...

  • Page 78: 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 an incompatible zoning configurations. Verify one of the following: • The effective cfg (zone set) on each end of the segmented ISL must be identical. •...

  • Page 79: Correcting A Fabric Merge Problem Quickly

    Zone conflicts ATTENTION Be careful using the cfgClear command because it deletes the defined configuration. Table 13 summarizes commands that are useful for debugging zoning issues. TABLE 13 Commands for debugging zoning Command Function aliCreate Use to create a zone alias. aliDelete Use to delete a zone alias.

  • Page 80: Editing Zone Configuration Members

    Zone conflicts ATTENTION The cfgClear command clears the zoning database on the switch where the command is run. 5. Enter the switchEnable command on each switch once the zoning configuration has been cleared. This forces the zones to merge and populates the switches with the correct zoning database. The fabrics will then merge.
  • Page 81 Zone conflicts • Generating an ELS ECHO request to the destination port specified and validates the response. Regardless of the device’s zoning, the fcPing command sends the ELS frame to the destination port. A device can take any of the following actions: •...

  • Page 82: Checking For Zoning Problems

    Gathering additional information Request timed out Request timed out Request timed out Request timed out Request timed out 5 frames sent, 0 frames received, 0 frames rejected, 5 frames timeout Round-trip min/avg/max = 0/0/0 usec switch:admin> For details about the fcPing command, see the Fabric OS Command Reference. Checking for zoning problems 1.

  • Page 83: Fcip Tunnel Issues

    Chapter FCIP Issues This chapter describes the FCIP concepts, configuration procedures, and tools and procedures for monitoring network performance. Commands described in this chapter require Admin or root user access. See the Fabric OS Command Reference for detailed information on command syntax. In this chapter •...
  • Page 84 FCIP tunnel issues Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64 Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64 Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64 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.

  • Page 85: Fcip Links

    FCIP links • To much data tries to be sent over the link. • Management data gets lost, queued too long, and timeouts expire. • Data exceeds timeouts multiple times. • Verify what link bandwidth is available. • Confirm the IP path is being used exclusively for FCIP traffic. •...

  • Page 86: Port Mirroring

    Port mirroring • When configuring routing over an FCIP link for a fabric, the edge fabric will use VE_Ports and the backbone fabric will use VEX_Ports for a single tunnel. • If an FCIP tunnel fails with the “Disabled (Fabric ID Oversubscribed)” message, the solution is to reconfigure the VEX_Port to the same Fabric ID as all of the other ports connecting to the edge fabric.

  • Page 87: Supported Hardware

    Port mirroring Port mirroring captures traffic between two devices. It mirrors only the frames containing the SID/DID to the mirror port. Because of the way it handles mirroring, a single mirror port can mirror multiple mirror connections. This also means that the port cannot exceed the maximum bandwidth of the mirror port.

  • Page 88: Port Mirroring Considerations

    Port mirroring The FC4-48 implements port pairing, meaning that two ports share the same area. Port pairing uses a single area to map to two physical ports. A frame destined to the secondary port is routed to the primary port. The primary port's filtering zone engine is used to redirect the frame to the secondary port.

  • Page 89: Port Mirroring Management

    Port mirroring The bandwidth of the mirror port is unidirectional. The host (SID) talks to multiple storage devices (DIDs) and does not send full line rate to a single target. A mirror port configured at 2GB can only support up to 2GB of traffic. A normal 2G F_Port is bidirectional and can support up to 4GB of traffic (two to transmit and two to receive).

  • Page 90: Ftrace Concepts

    FTRACE concepts Displaying port mirror connections 1. Log in to the switch as admin. 2. Type portMirror show You should see output similar to the following: switch:admin> portmirror --show Number of mirror connection(s) configured: 4 Mirror_Port State ---------------------------------------- 0x070400 0x0718e2 Enabled 0x070400 0x0718e3...
  • Page 91 FTRACE concepts After information is captured, you can use the portshow command to display FTRACE information on a GE port for a tunnel. You can save trace events can for future analysis. Displaying the trace for a tunnel 1. Log on to the switch as admin. 2.
  • Page 92 FTRACE concepts The following example configures FTRACE with ACO disabled, and FTRACE enabled with a trigger mask value of 00000003, and a trace mask value of ffffffff. portcfg ftrace ge0 3 cfg -a 0 -e 1 -p 5 -s 00000003 -t ffffffff Configuring FTRACE for a tunnel Use the following syntax to configure a trace: portcfg -ftrace [slot-number] ge port number [tunnel -id] cfg|del] <opt args>...

  • Page 93: Ficon Issues

    Chapter FICON Fabric Issues This chapter discusses FICON issues, recommended actions, and additional information you should gather to fix your issue. Any information you need to verify that FICON has been set up correctly can be found in the Fabric OS Administrator’s Guide. In this chapter •...

  • Page 94: 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 95: 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 96: 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 97: Troubleshooting Ficon Cup

    Troubleshooting FICON CUP • 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.
  • Page 98 Troubleshooting FICON CUP Symptom Mainframe RMF utility fails to capture performance data Probable cause and recommended action On Fabric OS v6.0.0, Brocade SilkWorm switches do not fully implement all of CUP commands needed to collect all of performance data on switch. Upgrade your switch to Fabric OS v6.1.0, where the performance data is captured.

  • Page 99: Troubleshooting Ficon Npiv

    Troubleshooting FICON NPIV Symptom Upgraded firmware from v5.0.x to v5.2.1a. The Brocade 24000 crashed when new firmware went active. Probable cause and recommended action RNID processing enhancement in firmware. The following message will appear in the switches log: 2007/05/13-07:06:56, [KSWD-1003], 78412/24993, FFDC, WARNING, SilkWorm24000, kSWD: Detected unexpected termination of: ''[4]ficud:0'RfP=712,RgP=712,DfP=0,died=1,rt=87261,dt=36843,to=50000,aJc=35761,aJ p=19101,abiJc=1942030008,abiJp=1942013308,aSeq=3,kSeq=0,kJc=0,kJp=0,J=50418,rs=2'...
  • Page 100 Troubleshooting FICON NPIV Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01...

  • Page 101: Connectivity

    Chapter iSCSI Issues If you are having problems with the iSCSI FC4-16IP blade connectivity, use the following chapter to troubleshoot before calling your support provider. NOTE The iSCSI blade FC4-16IP is not supported in the Brocade DCX Backbone. In this chapter •...
  • Page 102 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 103: 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: defZone --show Either create a zoning configuration or set default zoning to All Access using the defZone command.

  • Page 104: Authentication

    Authentication Symptom Changes made to the iSCSI database do not appear on iSCSI hosts. Probable cause and recommended action The DDSet has not been enabled or the database has not been committed. Check the currently enabled DD Set using: iscsiCfg - -show ddset Make sure it is reported as enabled and committed.

  • Page 105: About Fabric Os Diagnostics

    Chapter Working With Diagnostic Features This chapter provides information on diagnostics and how to display or save system, port, and specific hardware information. It also describes how to set up system logging mapping (syslogd) and how to set up the offloading of error messages (supportSave). In this chapter This chapter contains the following topics: •...

  • Page 106: Diagnostic Information

    Diagnostic information Diagnostic information On the switch you can enter the supportShow command to dump important diagnostic and status information to the session screen, where you can review it or capture its data. If you are using a Telnet client, you may have to set the client up to capture the data prior to opening the session 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.
  • Page 107 Power-on self test Checking system RAM - press any key to stop test Checking memory address: 00100000 System RAM test using Default POST RAM Test succeeded. Press escape within 4 seconds to enter boot interface. Booting "Fabric Operating System" image. Linux/PPC load: BootROM command line: quiet Uncompressing Linux...done.

  • Page 108: Switch Status

    Switch status 2005/03/31-20:13:13, [BL-1001], 222,, INFO, Paulsa45, Port Initialization Completed 2005/03/31-20:13:13, [EM-5012], 0,, INFO, SW4100_P45, EM: sent dumpready to ME., em.c, line: 2152 2005/03/31-20:13:13, [DGD-5002], 0,, INFO, SW4100_P45, Slot 0 has passed the POST tests., main.c, line: 936 If you choose to bypass POST2, or after POST2 completes, various system services are started and the boot process displays additional console status and progress messages.

  • Page 109: Displaying Switch Information

    Switch status Displaying switch information 1. Connect to the switch and log in as admin. 2. Enter the switchShow command, which displays the following information for a switch: Switch summary information includes the following: • switchName - Switch name. • switchType - Switch model and revision numbers.

  • Page 110: Port Information

    Port information Port information Use the following commands to view information about ports. Viewing the status of a port 1. Connect to the switch and log in as admin. 2. Enter the portShow command, specifying the number that corresponds to the port you are troubleshooting.

  • Page 111: Displaying The Port Statistics

    Port information Displaying the port statistics 1. Connect to the switch and log in as admin. 2. At the command line, enter the portStatsShow command. Port statistics include information such as the number of frames received, number of frames sent, number of encoding errors received, and number of class 2 and class 3 frames received.

  • Page 112: Displaying A Summary Of Port Errors For A Switch

    Port information Displaying a summary of port errors for a switch 1. Connect to the switch and log in as admin. 2. Enter the portErrShow command. See the Fabric OS Command Reference for additional portErrShow command information. brcd300:admin> porterrshow frames enc disc link loss loss frjt fbsy err shrt long c3 fail sync...

  • Page 113: Equipment Status

    Equipment status TABLE 17 Error summary description (Continued) Error type Description loss sig Loss of signal frjt Frames rejected with F_RJT fbsy Frames busied with F_BSY Equipment status You can display status for fans, power supply, and temperature. NOTE The number of fans, power supplies, and temperature sensors depends on the switch type. For detailed specifications on these components, refer to the switch hardware reference manual.

  • Page 114: Displaying Temperature Status

    System message log • Absent—Power supply not present. • Unknown—Unknown power supply unit installed. • Predicting failure—Power supply is present but predicting failure. • FAULTY—Power supply is present but faulty (no power cable, power switch turned off, fuse blown, or other internal error). Displaying temperature status 1.

  • Page 115: Clearing The System Message Log

    Port log Clearing the system message log 1. Connect to the switch and log in as admin. 2. Enter the errClear command. All switch and chassis events are removed. Port log The Fabric OS maintains an internal log of all port activity. The port log stores entries for each port as a circular buffer.

  • Page 116: Syslogd Configuration

    Syslogd configuration TABLE 18 Commands for port log management (Continued) Command Description portLogDump Display port logs for all or particular ports, without page breaks. portLogEnable Enable port logs for all or particular ports. portLogShow Display port logs for all or particular ports, with page breaks. The portLogDump command output (trace) is a powerful tool that is used to troubleshoot fabric issues.

  • Page 117: Configuring The Host

    Syslogd configuration Fabric OS can be configured to use a UNIX-style syslogd process to forward system events and error messages to log files on a remote host system. The host system can be running UNIX, Linux, or any other operating system that supports the standard syslogd functionality. Fabric OS supports UNIX local7 facilities (the default facility level is 7).

  • Page 118: Automatic Trace Dump Transfers

    Automatic trace dump transfers switch:admin> syslogdipadd 10.1.2.4 switch:admin> syslogdipadd 10.1.2.5 switch:admin> syslogdipadd 10.1.2.6 switch:admin> syslogdipshow syslog.IP.address.1080::8:800:200C:417A syslog.IP.address.1081::8:800:200C:417A syslog.IP.address.1082::8:800:200C:417A syslog.IP.address.4 10.1.2.4 syslog.IP.address.5 10.1.2.5 syslog.IP.address.6 10.1.2.6 Setting the facility level 1. Connect to the switch and log in as admin. 2. Enter the following command: switch:admin>...

  • Page 119: 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 120: 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 is interactive. 3. Respond to the prompts as follows: User name Enter the user name of your account on the server; for example, “JohnDoe”. Password Enter your account password for the server. Remote Specify a path name for the remote directory.
  • Page 121 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 122 Switch Type TABLE 20 Switch type to B-Series model converter Switch Type B-Series switch model ASIC Brocade DCX Condor2 5300 GoldenEye2 5100 Condor2 GoldenEye2 Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01...
  • Page 123 Appendix Hexidecimal Hexidecimal, or simply hex, is a numeral system with a base of 16, usually written using unique symbols 0–9 and A–F, or a–f. Its primary purpose is to represent the binary code that computers interpret and represent in a format easier for humans to read. It acts as a form of shorthand, in which one hexidecimal digit stands in place of four binary bits.
  • Page 124 Hexidecimal TABLE 21 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-1000853-01...
  • Page 125 Hexidecimal TABLE 21 Decimal to Hex conversion table Decimal Decimal Decimal Decimal Decimal Decimal Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01...
  • Page 126 Hexidecimal Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01...
  • Page 127 Index command cfgShow defZone account management fcLunQuery lost password recovery options iscsiCfg recovering forgotten passwords nsShow unable to modify switch settings portCfg user forgot password portCmd user unable to change switch settings portShow command output common problem areas symptoms BadRootDev configdownload fails blade errors configupload fails...
  • Page 128 disc_c3 errors FICON errors configured FICON NPIV troubleshooting FIPS downgrading firmware E_Port switch boots continuously failed to come online failed to form enc_out errors equipment status, viewing EX_Port does not form F_Port fabric issues merge fails parameters parameters, reconcile segments fans, status of FCIP gathering additional information...
  • Page 129 firmwareDownload errors user created IP filter policies zone size is not supported Access Gateway policies FL_Port active security DB size is greater than 256 KB AP blade type 24 is inserted FLOGI AP blade type 31 is inserted frames tx and rx AP blade type 33 is inserted FTRACE BadRootDev...
  • Page 130 PLOGI point-to-point initialization failure port L_Port bypassed LEDs disabled flashing no light in wrong mode steady initialization link loopback intermittent connectivty port information, viewing LEDs flashing port mirroring LEDs steady adding port connections marginal considerations no LED light deleting port connections logical connection FICON loop initialization failure...
  • Page 131 RAID tag field, interpreting device target recovering forgotten passwords LUNs on resolving zone conflicts targets routing errors temperature, status of device-based routing test a port a switch troubleshooting certificates corrupt certificate SCSI invalid certificate retry errors trunk timeout errors bounces security failed to form gathering additional information...
  • Page 132 zone configuration configuration mismatch content mismatch resolving conflicts troubleshooting type mismatch zone errors broadcast zone exists broadcast zone(s) LSAN count LSAN zone enabled zoning Fabric OS Troubleshooting and Diagnostics Guide 53-1000853-01...

This manual is also suitable for:

Ae370a - brocade 4gb san switch 4/12Am866a - storageworks 8/8 base san switch8/248/408/88/80

Table of Contents