Cisco N5K-C5010P-BF Troubleshooting Guide - Page 100

Interface is isolated because of FC Domain ID overlap, show logging, Possible Cause, 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 100 highlights

FC Services Chapter 5 Troubleshooting SAN Switching Issues Send document comments to [email protected]. Interface is isolated because of FC Domain ID overlap The Fibre Channel or SAN port channel interface of a Cisco Nexus 5000 switch (in fabric mode) that is connected to an FC switch with the xE port type is isolated because of a domain overlap. The following example shows possible logging messages in the show logging command log: Example: PORT-5-IF_DOWN_DOMAIN_OVERLAP_ISOLATION: Interface fc is down (Isolation due to domain overlap). %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN %$ Isolation of interface san-port-channel (reason: domain ID assignment failure) %FCDOMAIN-2-EPORT_ISOLATED: %$VSAN %$ Isolation of interface san-port-channel (reason: other side Eport indicates isolation) Possible Cause Two switch fabrics might not merge. If two fabrics with two or more switches are connected, have at least one assigned domain ID in common, and the auto-reconfigure option is disabled (this option is disabled by default), then the E ports that are used to connect the two fabrics will be isolated due to domain ID overlap. In a Fibre Channel network, the principal switch assigns domain IDs when a new switch is added to an existing fabric. However, when two fabrics merge, the principal switch selection process determines which one of the preexisting switches becomes the principal switch for the merged fabric. The election of the new principal switch is characterized by the following rules: • A switch with a populated domain ID list takes priority over a switch that has an empty domain ID list. The principal switch becomes the one in the fabric with the populated domain ID list. • If both fabrics have a domain ID list, the priority between the two principal switches is determined by the configured switch priority. This is a parameter that can be set by the user. The lower the value of the parameter, the higher the priority. • If the principal switch cannot be determined by the two previous criteria, the principal switch is then determined by the WWNs of the two switches. The lower the value of the WWN, the higher the switch priority. Solution To resolve an FC domain ID overlap, you can change the overlapping static domain ID by manually configuring a new static domain ID for the isolated switch, or disable the static domain assignment and allow the switch to request a new domain ID after a fabric reconfiguration. To assign a static domain ID using the NX-OS CLI All devices attached to the switch in the VSAN get a new FC ID when a new domain ID is assigned. Some hosts or storage devices may not function as expected if the FC ID of the host or storage device changes. To verify FC domain ID overlap and reassign a new domain ID using the CLI, perform the following steps: Step 1 Enter the show interface fc command to view the isolation error message for the E port. Example: switch(config)# show int fc 2/2 fc2/2 is down (Isolation due to domain other side eport isolated) Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN) Port WWN is 20:42:00:0d:ec:d5:fe:00 5-28 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-28
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
FC Services
Interface is isolated because of FC Domain ID overlap
The Fibre Channel or SAN port channel interface of a Cisco Nexus 5000 switch (in fabric mode) that is
connected to an FC switch with the xE
port type is isolated because of a domain overlap. The following
example shows possible logging messages in the
show logging
command log:
Example:
PORT-5-IF_DOWN_DOMAIN_OVERLAP_ISOLATION: Interface fc <slot/port> is down (Isolation due
to domain overlap).
%FCDOMAIN-2-EPORT_ISOLATED: %$VSAN <vsan-id>%$ Isolation of interface san-port-channel
<channel-id> (reason: domain ID assignment failure)
%FCDOMAIN-2-EPORT_ISOLATED: %$VSAN <vsan-id>%$ Isolation of interface san-port-channel
<channel-id> (reason: other side Eport indicates isolation)
Possible Cause
Two switch fabrics might not merge. If two fabrics with two or more switches are connected, have at
least one assigned domain ID in common, and the auto-reconfigure option is disabled (this option is
disabled by default), then the E ports that are used to connect the two fabrics will be isolated due to
domain ID overlap.
In a Fibre Channel network, the principal switch assigns domain IDs when a new switch is added to an
existing fabric. However, when two fabrics merge, the principal switch selection process determines
which one of the preexisting switches becomes the principal switch for the merged fabric.
The election of the new principal switch is characterized by the following rules:
•
A switch with a populated domain ID list takes priority over a switch that has an empty domain ID
list. The principal switch becomes the one in the fabric with the populated domain ID list.
•
If both fabrics have a domain ID list, the priority between the two principal switches is determined
by the configured switch priority. This is a parameter that can be set by the user. The lower the value
of the parameter, the higher the priority.
•
If the principal switch cannot be determined by the two previous criteria, the principal switch is then
determined by the WWNs of the two switches. The lower the value of the WWN, the higher the
switch priority.
Solution
To resolve an FC domain ID overlap, you can change the overlapping static domain ID by manually
configuring a new static domain ID for the isolated switch, or disable the static domain assignment and
allow the switch to request a new domain ID after a fabric reconfiguration.
To assign a static domain ID using the NX-OS CLI
All devices attached to the switch in the VSAN get a new FC ID when a new domain ID is assigned.
Some hosts or storage devices may not function as expected if the FC ID of the host or storage device
changes.
To verify FC domain ID overlap and reassign a new domain ID using the CLI, perform the following
steps:
Step 1
Enter the
show interface fc
<slot/port>
command to view the isolation error message for the E port.
Example:
switch(config)# show int fc 2/2
fc2/2 is down (Isolation due to domain other side eport isolated)
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:42:00:0d:ec:d5:fe:00