Cisco N5K-C5010P-BF Troubleshooting Guide - Page 117

Possible Cause, show interface brief, show vsan membership, Solution

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 117 highlights

Chapter 5 Troubleshooting SAN Switching Issues VSANs Send document comments to [email protected]. The storage and hosts are in the correct VSAN. Example: switch(config-vsan-db)# show flogi database vsan 100 INTERFACE VSAN FCID PORT NAME NODE NAME fc2/2 100 0x5a0000 50:0a:09:81:86:78:39:66 50:0a:09:80:86:78:39:66 [Storage] switch(config-if)# show flogi database vsan 100 INTERFACE VSAN FCID PORT NAME NODE NAME fc4/2 100 0x640114 20:00:00:25:b5:00:20:0e 20:00:00:25:b5:02:02:09 [Host] Possible Cause The error is displayed by the show interface brief command and the show vsan membership command. They show that the E port on one switch is in the wrong VSAN. The non-trunking E port on one switch is in the wrong VSAN. (VSAN 100 is the correct VSAN.) Example: switch(config-if)# show interface brief Interface Vsan Admin Admin Status SFP Oper Oper Port Mode Trunk Mode Speed Channel Mode (Gbps) fc1fc1/2 100 E off up swl E 2 -- Solution Move the non-trunking E-port into VSAN 100. Example: switch(config-vsan-db)# vsan 100 interface fc 2/4 Traffic on fc2/4 may be impacted. Do you want to continue? (y/n) [n] y The zone set is now active and the FC topology is correct. Example: switch(config-if)# show zoneset active vsan 100 zoneset name ZoneSet_Host_Storage vsan 100 zone name Zone_Host_Storage vsan 100 * fcid 0x640114 [pwwn 20:00:00:25:b5:00:20:0e] [Host] * fcid 0x5a0000 [pwwn 50:0a:09:81:86:78:39:66] [Storage] switch(config-if)# show topology FC Topology for VSAN 100 : Interface Peer Domain Peer Interface Peer IP Address fc1/2 0x5a(90) fc2/4 172.25.183.124 OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 5-45

  • 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-45
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
VSANs
The storage and hosts are in the correct VSAN.
Example:
switch(config-vsan-db)# show flogi database vsan 100
--------------------------------------------------------------------------------
INTERFACE
VSAN
FCID
PORT NAME
NODE NAME
--------------------------------------------------------------------------------
fc2/2
100
0x5a0000
50:0a:09:81:86:78:39:66 50:0a:09:80:86:78:39:66
[Storage]
switch(config-if)# show flogi database vsan 100
--------------------------------------------------------------------------------
INTERFACE
VSAN
FCID
PORT NAME
NODE NAME
--------------------------------------------------------------------------------
fc4/2
100
0x640114
20:00:00:25:b5:00:20:0e 20:00:00:25:b5:02:02:09
[Host]
Possible Cause
The error is displayed by the
show interface brief
command and the
show vsan membership
command.
They show that the E port on one switch is in the wrong VSAN.
The non-trunking E port on one switch is in the wrong VSAN. (VSAN 100 is the correct VSAN.)
Example:
switch(config-if)# show interface brief
-------------------------------------------------------------------------------
Interface
Vsan
Admin
Admin
Status
SFP
Oper
Oper
Port
Mode
Trunk
Mode
Speed
Channel
Mode
(Gbps)
-------------------------------------------------------------------------------
fc1fc1/2
100
E
off
up
swl
E
2
--
Solution
Move the non-trunking E-port into VSAN 100.
Example:
switch(config-vsan-db)# vsan 100 interface fc 2/4
Traffic on fc2/4 may be impacted. Do you want to continue? (y/n) [n] y
The zone set is now active and the FC topology is correct.
Example:
switch(config-if)# show zoneset active vsan 100
zoneset name ZoneSet_Host_Storage vsan 100
zone name Zone_Host_Storage vsan 100
* fcid 0x640114 [pwwn 20:00:00:25:b5:00:20:0e] [Host]
* fcid 0x5a0000 [pwwn 50:0a:09:81:86:78:39:66] [Storage]
switch(config-if)# show topology
FC Topology for VSAN 100 :
--------------------------------------------------------------------------------
Interface
Peer Domain Peer Interface
Peer IP Address
--------------------------------------------------------------------------------
fc1/2
0x5a(90)
fc2/4
172.25.183.124