5-8
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-29284-01, Release 6.x
Chapter 5 Configuring Trunking
Guidelines and Limitations
• No FC-SP authentication is supported by the NPV switch on the server F ports.
• MDS does not enforce the uniqueness of logical pWWNs across VSANs.
• DPVM is not supported on trunked F port logins.
• The DPVM feature is limited to the control of the port VSAN, since the EVFP protocol does not
allow changing the VSAN on which a logical pWWN has done FLOGI.
• The port security configuration will be applied to both the first physical FLOGI and the per VSAN
FLOGIs.
• Trunking is not supported on F ports that have FlexAttach enabled.
• On MDS 91x4 core switches, hard zoning can be done only on F ports that are doing either NPIV
or trunking. However, in NPV mode, this restriction does not apply since zoning is enforced on the
core F port.
Note Fibre Channel Security Protocol (FC-SP) is not supported for 6.2(1) release on MDS 9710, but targeted
for a future release.
Upgrade and Downgrade Limitations
The trunking and channeling feature includes the following upgrade and downgrade limitations:
• When F port trunking or channeling is configured on a link, the switch cannot be downgraded to
Cisco MDS SAN-OS Release 3.x and NX-OS Release 4.1(1b), or earlier.
• If you are upgrading from a SAN-OS Release 3.x to NX-OS Release 5.0(1), and you have not created
VSAN 4079, the NX-OS software will automatically create VSAN 4079 and reserve it for EVFP
use.
If VSAN 4079 is reserved for EVFP use, the switchport trunk allowed vsan command will filter
out VSAN 4079 from the allowed list, as shown in the following example:
switch(config-if)# switchport trunk allowed vsan 1-4080
1-4078,4080
switch(config-if)#
–
If you have created VSAN 4079, the upgrade to NX-OS Release 5.0(1) will have no affect on
VSAN 4079.
–
If you downgrade after NX-OS Release 5.0(1), the VSAN will no longer be reserved for EVFP
use.
Difference Between TE Ports and TF-TNP Ports
In case of TE ports, the VSAN will in be initializing state when VSAN is coming up on that interface
and when peers are in negotiating phase. Once the handshake is done, VSAN will be moved to up state
in the successful case, and isolated state in the case of failure. Device Manager will show the port status
as amber during initializing state and it will be green once VSANs are up.
This example shows the trunk VSAN states of a TE port:
Switch# show interface fc2/15
fc2/15 is trunking
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
