Cisco N5K-C5010P-BF Troubleshooting Guide - Page 99

Solution, no fcid-allocation area company, show flogi database

Get Cisco N5K-C5010P-BF - Nexus 5010 Switch PDF manuals and user guides
UPC - 882658212208
View all Cisco N5K-C5010P-BF manuals
Add to My Manuals
Save this manual to your list of manuals

Page 99 highlights

Chapter 5 Troubleshooting SAN Switching Issues FC Services Send document comments to [email protected]. hard-addr :0x000000 permanent-port-wwn (vendor) :20:11:00:05:1e:06:da:ea Connected Interface :fc2/2 Switch Name (IP address) :N5K (10.200.220.13) Some legacy gateway switches might require that the area part of the FCID be the same for the switch and for all the blades logged in through that port. However, because of an old issue with Qlogic HBAs, the Cisco Nexus 5000 domain server assigns a separate area for each Qlogic HBA that matches a certain OUI by default. Therefore, a conflict between legacy gateway requirements and the Cisco domain allocation scheme exists. Cisco still implements this set up to support old existing Qlogic HBAs in the field. Solution Configure no fcid-allocation area company for all used Qlogic OUIs (ensuring flat FCID allocation in the future), force all affected blades to log out of the fabric, delete the already created persistent FCID entry from the Nexus 5000 switch configuration, and allow the blade to log in again. In the following show flogi database command output, all devices obtain a unique area id (x01, x08, x0c): Example: Fc2/1 2 Fc2/1 2 Fc2/1 2 0x620104 20:10:00:05:1e:5e:6a:85 10:00:00:05:1e:5e:6a:85 0x620800 21:01:00:1b:32:a3:c0:2e 20:01:00:1b:32:a3:c0:2e 0x620c00 21:01:00:1b:32:33:8b:8e 20:01:00:1b:32:33:8b:8e Because of the specific area ID requirement of the legacy switch, the last two blades must also have area x01. To force the Qlogic adapters to log in again and obtain FCID in 0x6201xx range, do the following steps: Step 1 Step 2 Configure (force) the future FCID allocation scheme to be flat for all WWNs matching the OUIs that are in this situation. switch(configure)# no fcid-allocation area company 0x001B32 Force the FCID under reconfiguration to log out of the fabric. Note If you shut down the Nexus 5000 interface that serves as the primary uplink for that server, it only will log in through another one. The appropriate method is to shut down the affected blade and ensure that the FLOGI for the WWN is gone. Step 3 Step 4 Delete the automatically created configuration entry for persistent FCID allocation as shown in the following example: Example: switch(config)# fcdomain fcid database switch(config-fcid-db)# no vsan 2 wwn 21:01:00:1b:32:a3:c0:2e fcid 0x620800 area dynamic Bring up the blade and ensure that it gets a proper fcid. Example: Fc2/1 2 Fc2/1 2 0x620104 20:10:00:05:1e:5e:6a:85 10:00:00:05:1e:5e:6a:85 0x620123 21:01:00:1b:32:a3:c0:2e 20:01:00:1b:32:a3:c0:2e OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 5-27

  • 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
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
Send document comments to [email protected].
5-27
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
FC Services
hard-addr
:0x000000
permanent-port-wwn (vendor) :20:11:00:05:1e:06:da:ea
Connected Interface
:fc2/2
Switch Name (IP address)
:N5K (10.200.220.13)
Some legacy gateway switches might require that the area part of the FCID be the same for the switch
and for all the blades logged in through that port.
However, because of an old issue with Qlogic HBAs, the Cisco Nexus 5000 domain server assigns a
separate area for each Qlogic HBA that matches a certain OUI by default. Therefore, a conflict between
legacy gateway requirements and the Cisco domain allocation scheme exists. Cisco still implements this
set up to support old existing Qlogic HBAs in the field.
Solution
Configure
no fcid-allocation area company
<oui>
for all used Qlogic OUIs (ensuring flat FCID
allocation in the future), force all affected blades to log out of the fabric, delete the already created
persistent FCID entry from the Nexus 5000 switch configuration, and allow the blade to log in again.
In the following
show flogi database
command output, all devices obtain a unique area id (x01, x08,
x0c):
Example:
Fc2/1
2
0x620104
20:10:00:05:1e:5e:6a:85 10:00:00:05:1e:5e:6a:85
Fc2/1
2
0x620800
21:01:00:1b:32:a3:c0:2e 20:01:00:1b:32:a3:c0:2e
Fc2/1
2
0x620c00
21:01:00:1b:32:33:8b:8e 20:01:00:1b:32:33:8b:8e
Because of the specific area ID requirement of the legacy switch, the last two blades must also have area
x01. To force the Qlogic adapters to log in again and obtain FCID in 0x6201xx range, do the following
steps:
Step 1
Configure (force) the future FCID allocation scheme to be flat for all WWNs matching the OUIs that are
in this situation.
switch(configure)# no fcid-allocation area company 0x001B32
Step 2
Force the FCID under reconfiguration to log out of the fabric.
Note
If you shut down the Nexus 5000 interface that serves as the primary uplink for that server, it only will
log in through another one. The appropriate method is to shut down the affected blade and ensure that
the FLOGI for the WWN is gone.
Step 3
Delete the automatically created configuration entry for persistent FCID allocation as shown in the
following example:
Example:
switch(config)# fcdomain fcid database
switch(config-fcid-db)# no vsan 2 wwn 21:01:00:1b:32:a3:c0:2e fcid 0x620800 area dynamic
Step 4
Bring up the blade and ensure that it gets a proper fcid.
Example:
Fc2/1
2
0x620104
20:10:00:05:1e:5e:6a:85 10:00:00:05:1e:5e:6a:85
Fc2/1
2
0x620123
21:01:00:1b:32:a3:c0:2e 20:01:00:1b:32:a3:c0:2e