Dell Brocade G620 Brocade 8.0.1 Fabric OS Troubleshooting and Diagnostics Guid - Page 71

Switch configuration blade compatibility, Gathering additional information

Page 71 highlights

Virtual Fabrics Symptom Probable cause and recommended action A port or ports cannot be moved to the requested switch because it would exceed the 256 area limit for this switch. The area limit would be exceeded if the lsCfg command were allowed. Symptom Probable cause and recommended action A port or ports cannot be moved to the requested switch because it may only exist in a base or default switch. You are attempting to move ports on a core blade into a non-default or non-base switch. Switch configuration blade compatibility Symptom Probable cause and recommended action A slot in the chassis displays a FAULTY(91) in the output of the slotShow command. When an enterprise-class platform is coming up or when a blade is inserted, the switch configuration is checked based on the blade type. If the configuration does not match with the blade type, the blade is faulted. This is displayed as FAULTY(91) in the output of the slotShow command. Use the lsCfg -restore_slot_to_default command to correct the problem. Once the configuration discrepancy has been fixed, you may use slotPowerOff followed by slotPowerOn to recover. For example, refer to the following CLI related to DCX 8510 platform: >lscfg -restore_slot_to_default 1 >slotpoweroff 1 >slotpoweron 1 Slot Blade Type ID Model Name Status 1 SW BLADE 77 FC8-64 ENABLED 2 SW BLADE 97 FC16-32 ENABLED 3 SW BLADE 96 FC16-48 ENABLED 4 SW BLADE 96 FC16-48 ENABLED 5 CORE BLADE 98 CR16-8 ENABLED 6 CP BLADE 50 CP8 ENABLED 7 CP BLADE 50 CP8 ENABLED 8 CORE BLADE 98 CR16-8 ENABLED 9 SW BLADE 55 FC8-32 ENABLED 10 SW BLADE 96 FC16-48 ENABLED 11 AP BLADE 75 FX8-24 ENABLED 12 SW BLADE 97 FC16-32 ENABLED Gathering additional information For Virtual Fabrics-related issues, use the following guidelines to gather additional data for your switch support provider: ∙ Use the supportSave command. ∙ If not sure about the problem area, use the supportSave command on all chassis and logical switches in the fabric. ∙ If you think it may be related to E_Port authentication, then use the supportSave -n command on both switches or logical switches of the affected E_Port. Brocade Fabric OS Troubleshooting and Diagnostics Guide 53-1004126-01 71

  • 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

Symptom
A port or ports cannot be moved to the requested switch because it would
exceed the 256 area limit for this switch.
Probable cause and recommended action
The area limit would be exceeded if the
lsCfg
command were allowed.
Symptom
A port or ports cannot be moved to the requested switch because it may
only exist in a base or default switch.
Probable cause and recommended action
You are attempting to move ports on a core blade into a non-default or
non-base switch.
Switch configuration blade compatibility
Symptom
A slot in the chassis displays a FAULTY(91) in the output of the slotShow command.
Probable cause and recommended action
When an enterprise-class platform is coming up or when a blade is inserted, the switch configuration is
checked based on the blade type. If the configuration does not match with the blade type, the blade is
faulted. This is displayed as FAULTY(91) in the output of the
slotShow
command.
Use the
lsCfg -restore_slot_to_default
command to correct the problem. Once the configuration
discrepancy has been fixed, you may use
slotPowerOff
followed by
slotPowerOn
to recover.
For example, refer to the following CLI related to DCX 8510 platform:
>lscfg -restore_slot_to_default 1
>slotpoweroff 1
>slotpoweron 1
Slot
Blade Type
ID
Model Name
Status
--------------------------------------------------
1
SW BLADE
77
FC8-64
ENABLED
2
SW BLADE
97
FC16-32
ENABLED
3
SW BLADE
96
FC16-48
ENABLED
4
SW BLADE
96
FC16-48
ENABLED
5
CORE BLADE
98
CR16-8
ENABLED
6
CP BLADE
50
CP8
ENABLED
7
CP BLADE
50
CP8
ENABLED
8
CORE BLADE
98
CR16-8
ENABLED
9
SW BLADE
55
FC8-32
ENABLED
10
SW BLADE
96
FC16-48
ENABLED
11
AP BLADE
75
FX8-24
ENABLED
12
SW BLADE
97
FC16-32
ENABLED
Gathering additional information
For Virtual Fabrics-related issues, use the following guidelines to gather additional data for your switch support provider:
Use the
supportSave
command.
If not sure about the problem area, use the
supportSave
command on all chassis and logical switches in the fabric.
If you think it may be related to E_Port authentication, then use the
supportSave -n
command on both switches or logical
switches of the affected E_Port.
Virtual Fabrics
Brocade Fabric OS Troubleshooting and Diagnostics Guide
53-1004126-01
71