Filter
Top Products
5-10
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-29284-01, Release 6.x
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
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
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.
Isolated
Switch 1 Switch 2
E port
VSAN 2
E port
VSAN 3
VSAN mismatch
85471
Switch 1 Switch 3Switch 2
Third-party switches
VSAN 2
E port
VSAN 3
E port
85472