HP AM866A Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1000853-01, - Page 21

Building a case for your switch support provider, Basic switch information

Page 21 highlights

Building a case for your switch support provider 1 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: Fabric OS Troubleshooting and Diagnostics Guide 7 53-1000853-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132

Fabric OS Troubleshooting and Diagnostics Guide
7
53-1000853-01
Building a case for your switch support provider
1
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: