Chapter 5 Configuring Trunking

Guidelines and Limitations

Receive B2B

Credit

is 32

 

Receive data field

Size is

2112

Beacon is turned off

 

Trunk vsans

(admin

allowed

and active) (1,100-101,1101,1163-1166,1216,2172,2

182-2183)

 

 

 

Trunk vsans

(up)

 

(1,2183)

Trunk vsans

(isolated)

()

Trunk vsans

(initializing)

(1101,1163-1166,1216,2172,2182)

Trunking Misconfiguration Examples

If you do not configure the VSANs correctly, issues with the connection may occur. For example, if you merge the traffic in two VSANs, both VSANs will be mismatched. The trunking protocol validates the VSAN interfaces at both ends of a link to avoid merging VSANs (see Figure 5-5).

Figure 5-5

VSAN Mismatch

Switch 1

Switch 2

 

Isolated

E port

E port

VSAN 2

VSAN 3

VSAN mismatch

85471

The trunking protocol detects potential VSAN merging and isolates the ports involved (see Figure 5-5).

The trunking protocol cannot detect merging of VSANs when a third-party switch is placed in between two Cisco MDS 9000 Family switches (see Figure 5-6).

Figure 5-6 Third-Party Switch VSAN Mismatch

 

 

 

Third-party switches

 

 

 

 

VSAN 2

 

 

 

VSAN 3

 

 

 

E port

 

 

 

E port

Switch 1

 

Switch 2

 

Switch 3

85472

VSAN 2 and VSAN 3 are effectively merged with overlapping entries in the name server and the zone applications. Cisco DCNM-SAN helps detect such topologies.

 

Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide

5-10

OL-29284-01, Release 6.x

Page 164
Image 164
Cisco Systems DSC9148D8G48PK9 manual Trunking Misconfiguration Examples, Vsan Mismatch