Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1000853-01, June 2008)

Fabric OS Troubleshooting and Diagnostics Guide 7

53-1000853-01

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.

Basic switch information

1. What is the switch’s current Fabric OS level?

To determine the switch’s Fabric OS level, type the firmwareShow command and write the

information.

2. What is the switch model?

To determine the switch model, type the switchshow command and write down the value in the

switchType field. Cross-reference this value with the chart located in Appendix A, “Switch

Type”.

3. Is the switch operational? Yes or No

4. Impact assessment and urgency:

• Is the switch down? Yes or no.

• Is it a standalone switch? Yes or no.

• Are there VE, VEX or EX ports connected to the chassis? Yes or no.

• How large is the fabric? nsallshow

• Is it a secure fabric?

• Are there security policies turned on in the fabric? If so, what are they? (Gather the output

from the following commands:

 secPolicyShow

 fddCfg --showall

 ipFilter --show

 authUtil --show

 secAuthSecret --show

 fipsCfg --showall

• Is the fabric redundant? If yes, what is the MPIO software? (List vendor and version.)

5. If you have a redundant fabric, did a failover occur?

6. Was POST enabled on the switch?

7. Which CP blade was active? (Only applicable to the Brocade 24000 and 48000 directors, and

the Brocade DCX Backbone.)

Detailed problem information

Obtain as much of the following informational items as possible prior to contacting the SAN

technical support vendor.

Document the sequence of events by answering the following questions: