Cisco N5K-C5010P-BF Troubleshooting Guide - Page 76

Server on downstream NPV edge switch does not login to the fabric, Solution, Possible Cause

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

Chapter 5 Troubleshooting SAN Switching Issues NPV Send document comments to [email protected]. This may be normal and a direct result of the default SID/DID load balancing that is done before the Nexus 5000 4.2(1)N1 release. Solution If the upstream switch is an MDS switch that is running 4.1(3) code or above, and it is a NPV F_Port Trunking capable switch, the preferred configuration would be to run the F_Port Trunking Port Channeling feature. Example (NPIV core): pod3-9222i(config)# feature npiv pod3-9222i(config)# feature fport-channel-trunk pod3-9222i(config)# interface port-channel 1 pod3-9222i(config-if)# switchport mode f pod3-9222i(config-if)# switchport trunk mode on pod3-9222i(config-if)# channel mode active pod3-9222i(config-if)# interface fc2/13, fc2/19 pod3-9222i(config-if)# switchport mode f pod3-9222i(config-if)# switchport rate-mode dedicated pod3-9222i(config-if)# switchport trunk mode on pod3-9222i(config-if)# channel-group 1 force In this example, fc2/13 and fc2/19 are added to port channel 100 and are disabled. Do the same operation on the switch at the other end of the port channel, then do no shutdown at both ends to bring them up. Example: pod3-9222i(config-if)# no shut Example (NPV Edge): pod7-5020-51(config)# interface san-port-channel 1 pod7-5020-51(config-if)# switchport mode np pod7-5020-51(config-if)# switchport trunk mode on pod7-5020-51(config-if)# interface fc2/1-2 pod7-5020-51(config-if)# switchport mode np pod7-5020-51(config-if)# switchport trunk mode on pod7-5020-51(config-if)# channel-group 1 In this example, fc2/1 and fc2/2 are added to port channel 1 and are disabled. Do the same operation on the switch at the other end of the port channel, then do no shutdown at both ends to bring them up Example: pod7-5020-51(config-if)# no shut Server on downstream NPV edge switch does not login to the fabric The server connected to the downstream NPV edge switch does not log in to the fabric. Possible Cause The server on the downstream NPV edge switch does not log in to the fabric, and/or you see a "waiting for FLOGI" message. Example: switch# show npv status npiv is enabled Cisco Nexus 5000 Series Troubleshooting Guide 5-4 OL-25300-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
  • 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-4
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
NPV
This may be normal and a direct result of the default SID/DID load balancing that is done before the
Nexus 5000 4.2(1)N1 release.
Solution
If the upstream switch is an MDS switch that is running 4.1(3) code or above, and it is a NPV F_Port
Trunking capable switch, the preferred configuration would be to run the F_Port Trunking Port
Channeling feature.
Example (NPIV core):
pod3-9222i(config)#
feature npiv
pod3-9222i(config)#
feature fport-channel-trunk
pod3-9222i(config)#
interface port-channel 1
pod3-9222i(config-if)#
switchport mode f
pod3-9222i(config-if)#
switchport trunk mode on
pod3-9222i(config-if)#
channel mode active
pod3-9222i(config-if)#
interface fc2/13, fc2/19
pod3-9222i(config-if)#
switchport mode f
pod3-9222i(config-if)#
switchport rate-mode dedicated
pod3-9222i(config-if)#
switchport trunk mode on
pod3-9222i(config-if)#
channel-group 1 force
In this example, fc2/13 and fc2/19 are added to port channel 100 and are disabled. Do the same operation
on the switch at the other end of the port channel, then do no shutdown at both ends to bring them up.
Example:
pod3-9222i(config-if)# no shut
Example (NPV Edge):
pod7-5020-51(config)# interface san-port-channel 1
pod7-5020-51(config-if)# switchport mode np
pod7-5020-51(config-if)# switchport trunk mode on
pod7-5020-51(config-if)# interface fc2/1-2
pod7-5020-51(config-if)# switchport mode np
pod7-5020-51(config-if)# switchport trunk mode on
pod7-5020-51(config-if)# channel-group 1
In this example, fc2/1 and fc2/2 are added to port channel 1 and are disabled. Do the same operation on
the switch at the other end of the port channel, then do no shutdown at both ends to bring them up
Example:
pod7-5020-51(config-if)#
no shut
Server on downstream NPV edge switch does not login to the fabric
The server connected to the downstream NPV edge switch does not log in to the fabric.
Possible Cause
The server on the downstream NPV edge switch does not log in to the fabric, and/or you see a “waiting
for FLOGI” message.
Example:
switch# show npv status
npiv is enabled