Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual page 228

VSAN Issues
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
Use the show interface fc slot/port trunk vsan vsan-id command to verify the reason for VSAN
Step 2
isolation.
switch# show interface fc2/14 trunk vsan 1
fc2/15 is trunking
Vsan 1 is down (Isolation due to zone merge failure)
This output shows that VSAN 1 is isolated because of a zone merge error.
Use the show port internal info interface fc slot/port command to determine the root cause of the
Step 3
VSAN isolation.
To issue commands with the internal keyword, you must have an account that is a member of the
Note
network-admin group.
switch# show port internal info interface fc2/14
fc2/14 - if_index: 0x0109C000, phy_port_index: 0x3c
Admin Config - state(up), mode(TE), speed(auto), trunk(on)
beacon(off), snmp trap(on), tem(false)
rx bb_credit(default), rx bb_credit multiplier(default)
rxbufsize(2112), encap(default), user_cfg_flag(0x3)
description()
Hw Capabilities: 0xb
trunk vsans (up) (7)
.
.
.
trunk vsans (isolated) (1,8)
TE port per vsan information
fc2/29, Vsan 1 - state(down), state reason(Isolation due to domain other side eport
isolated), fcid(0x000000)
port init flag(0x10000), current state [TE_FSM_ST_ISOLATED_DM_ZS]
fc2/29, Vsan 7 - state(up), state reason(None), fcid(0x690202)
port init flag(0x38000), current state [TE_FSM_ST_E_PORT_UP]
fc2/29, Vsan 8 - state(down), state reason(Isolation due to vsan not configured on
peer), fcid(0x000000)
port init flag(0x0), current state [TE_FSM_ST_ISOLATED_VSAN_MISMATCH]
The last few lines of the command output provide a description of the reason for VSAN isolation for
every isolated VSAN.
In this example, VSAN 7 is up, while two VSANs are isolated. VSAN 1 is isolated because of domain
ID misconfiguration, and VSAN 8 is isolated because of VSAN misconfiguration.
Step 4 Correct the root cause. See the
domain misconfiguration problems. Use the vsan vsan-id interface command to correct the VSAN
misconfiguration problems.
Repeat this procedure for all isolated VSANs on this TE port.
Step 5
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
11-8
Chapter 11
"DPVM Config Database Not Activating" section on page 11-14
Troubleshooting VSANs, Domains, and FSPF
OL-9285-05
for