Scribd
Upload
129 views3 pages

Cisco Port Isolation

This document provides steps to resolve VSAN isolation on a trunking E port (TE port) using the CLI. Step 1 is to use the show interface command to verify one or more VSANs are isolated on the TE port. Step 2 is to use the show interface trunk vsan command to determine the reason for isolation of a specific VSAN. Step 3 is to use the show port internal info interface command, which provides the root cause of isolation for each isolated VSAN, such as domain or VSAN misconfiguration. Step 4 is to correct the root cause issue, such as domain ID or VSAN configuration problems. Step 5 is to repeat for all isolated VSANs on

Uploaded by

Shashi Kanth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
129 views3 pages

Cisco Port Isolation

This document provides steps to resolve VSAN isolation on a trunking E port (TE port) using the CLI. Step 1 is to use the show interface command to verify one or more VSANs are isolated on the TE port. Step 2 is to use the show interface trunk vsan command to determine the reason for isolation of a specific VSAN. Step 3 is to use the show port internal info interface command, which provides the root cause of isolation for each isolated VSAN, such as domain or VSAN misconfiguration. Step 4 is to correct the root cause issue, such as domain ID or VSAN configuration problems. Step 5 is to repeat for all isolated VSANs on

Uploaded by

Shashi Kanth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

Resolving an Isolated ISL Using the CLI

Trunking E ports (TE ports) are similar to E ports except that they carry traffic for multiple VSANs. E ports carry traffic
for a single VSAN. Because TE ports carry traffic for multiple VSANs, ISL isolation can affect one or more VSANs.
For this reason, on a TE port you must troubleshoot for ISL isolation on each VSAN.

To resolve VSAN isolation on a TE port using the CLI, follow these steps:

Step 1 Use the show interface command on the TE port to verify that you have an isolated VSAN.

switch# show interface fc2/14


fc2/14 is trunking
Hardware is Fibre Channel, WWN is 20:4e:00:05:30:00:63:9e
Port mode is TE
Speed is 2 Gbps
vsan is 2
Beacon is turned off
Trunk vsans (allowed active) (1-3,5)
Trunk vsans (operational) (1-3,5)
Trunk vsans (up) (2-3,5)
Trunk vsans (isolated) (1)
Trunk vsans (initializing) ()
475 frames input, 8982 bytes, 0 discards
0 runts, 0 jabber, 0 too long, 0 too short
0 input errors, 0 CRC, 3 invalid transmission words
0 address id, 0 delimiter
0 EOF abort, 0 fragmented, 0 unknown class
514 frames output, 7509 bytes, 16777216 discards
Received 30 OLS, 21 LRR, 18 NOS, 53 loop inits

The example shows the output of the show interface command with one or more isolated VSANs. Here, the TE port
has one VSAN isolated.

Step 2 Use the show interface fc slot/port trunk vsan vsan-id command to verify the reason for VSAN 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.

Step 3 Use the show port internal info interface fc slot/port command to determine the root cause of the VSAN
isolation.

Note To issue commands with the internal keyword, you must have an account that is a member of the 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 "DPVM Config Database Not Activating" section for domain misconfiguration
problems. Use the vsanvsan-id interface command to correct the VSAN misconfiguration problems.

Step 5 Repeat this procedure for all isolated VSANs on this TE port.

You might also like