Cisco N5K-C5010P-BF Troubleshooting Guide - Page 86

Newly added Fibre Channel interface does not come online in a SAN Port Channel

Page 86 highlights

SAN Port Channels Chapter 5 Troubleshooting SAN Switching Issues Send document comments to [email protected]. Newly added Fibre Channel interface does not come online in a SAN Port Channel When a new Fibre Channel interface is added, it does not come online in a SAN port channel. The following error message during the configuration operation may appear. Command failed: port not compatible [reason] Possible Cause Port channel mode is configured as on. If you use the default ON mode to avoid inconsistent states across switches and to maintain consistency across switches, then the ports shut down. Solution Explicitly enable the ports again using the no shutdown command. Possible Cause Interface parameters are not compatible with the existing SAN port channel. Solution Use the force option to force the physical interface to take on the parameters of the SAN port channel. In the interface sub-configuration mode, use the channel-group force command. Cannot configure trunking Trunking cannot be configured under the interface configuration mode. The following error message may appear in the CLI output: error:invalid switchport config Possible Cause Trunking protocol is disabled. Solution Enable trunking by using the trunk protocol enable CLI command. VSAN traffic does not traverse trunk The VSAN traffic is not able to traverse the trunk. A host cannot gain access to a target that is on the same VSAN and connected to two different switches using TE ports. The VSAN traffic is not able to traverse the trunk. Depending on the path from host to target, you may observe a performance degradation or you may not be able to access any disks. Possible Cause VSAN is not listed in the allowed-active VSAN list. Solution 5-14 Cisco Nexus 5000 Series Troubleshooting Guide 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-14
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
SAN Port Channels
Newly added Fibre Channel interface does not come online in a SAN Port
Channel
When a new Fibre Channel interface is added, it does not come online in a SAN port channel.
The following error message during the configuration operation may appear.
Command failed: port not compatible [reason]
Possible Cause
Port channel mode is configured as on.
If you use the default ON mode to avoid inconsistent states across switches and to maintain consistency
across switches, then the ports shut down.
Solution
Explicitly enable the ports again using the
no shutdown
command.
Possible Cause
Interface parameters are not compatible with the existing SAN port channel.
Solution
Use the force option to force the physical interface to take on the parameters of the SAN port channel.
In the interface sub-configuration mode, use the
channel-group
<channel-group number>
force
command.
Cannot configure trunking
Trunking cannot be configured under the interface configuration mode.
The following error message may appear in the CLI output:
error:invalid switchport config
Possible Cause
Trunking protocol is disabled.
Solution
Enable trunking by using the
trunk protocol enable CLI
command.
VSAN traffic does not traverse trunk
The VSAN traffic is not able to traverse the trunk.
A host cannot gain access to a target that is on the same VSAN and connected to two different switches
using TE ports. The VSAN traffic is not able to traverse the trunk. Depending on the path from host to
target, you may observe a performance degradation or you may not be able to access any disks.
Possible Cause
VSAN is not listed in the allowed-active VSAN list.
Solution