Information About VSAN Trunking
VSAN trunking enable interconnected ports to transmit and receive frames in more than one VSAN. Trunking is supported on E ports and F ports.
The VSAN trunking feature includes the following restrictions:
-
Trunking configurations are applicable only to E ports. If trunk mode is enabled in an E port and that port becomes operational as a trunking E port, it is referred to as a TE port.
-
The trunk-allowed VSANs configured for TE ports are used by the trunking protocol to determine the allowed-active VSANs in which frames can be received or transmitted.
-
If a trunking-enabled E port is connected to a third-party switch, the trunking protocol ensures seamless operation as an E port.
VSAN Trunking Mismatches
If you misconfigure VSAN configurations across E ports, issues can occur such as the merging of traffic in two VSANs (causing both VSANs to mismatch). The VSAN trunking protocol validates the VSAN interfaces at both ends of an ISL to avoid merging VSANs (see the following figure).
In this example, the trunking protocol detects potential VSAN merging and isolates the ports involved.
The trunking protocol cannot detect merging of VSANs when a third-party switch is placed in between two Cisco SAN switches (see the following figure).
VSAN 2 and VSAN 3 are effectively merged with overlapping entries in the name server and the zone applications. helps detect such topologies.
VSAN Trunking Protocol
The trunking protocol is important for E-port and TE-port operations. It supports the following capabilities:
-
Dynamic negotiation of operational trunk mode.
-
Selection of a common set of trunk-allowed VSANs.
-
Detection of a VSAN mismatch across an ISL.
By default, the VSAN trunking protocol is enabled. If the trunking protocol is disabled on a switch, no port on that switch can apply new trunk configurations. Existing trunk configurations are not affected: the TE port continues to function in trunk mode but only supports traffic in VSANs that it negotiated with previously (when the trunking protocol was enabled). Other switches that are directly connected to this switch are similarly affected on the connected interfaces. If you need to merge traffic from different port VSANs across a nontrunking ISL, disable the trunking protocol.