•
If you are using VTP in a Token Ring environment, you must use version 2.
•
When a switch is configured in VTP client or server mode, VLANs 1002 to1005 are reserved VLANs.
•
VTPv3 pruning is supported from Cisco NX-OS Release 7.2(0)N1(1) onwards.
•
You must enter the
copy running-config startup-config
command followed by a reload after changing
a reserved VLAN range. For example:
switch(config)# system vlan 2000 reserve
This will delete all configs on vlans 2000-2081. Continue anyway? (y/n) [no] y
After the switch reload, VLANs 2000 to 2081 are reserved for internal use, which requires that you enter
the
copy running-config startup-config
command before the switch reload. Creating VLANs within
this range is not allowed.
•
Ensure VLAN 1 is not STP blocked for VTP interfaces in VTP transparent mode.
•
In SNMP, the vlanTrunkPortVtpEnabled object indicates whether the VTP feature is enabled or not.
About VLAN Translation
In a data center there are often instances when you want to merge separate Layer 2 domains. For example,
you might have two data centers that are connected via some form of Data Center Interconnect (DCI) such
as Overlay Transport Virtualization (OTV). Both data centers might have an engineering group that has its
own VLAN in each data center. Due to differences such as different administrators, the VLAN number might
be different in each data center. Once the two data centers are connected via DCI, it makes sense that all
engineering traffic should be visible in both data centers. In complex installations reconfiguration is not worth
the collateral damage reconfiguration can cause. This is a scenario where VLAN translation would be useful
to merge the two Layer 2 domains without actually changing their VLAN number.
Cisco Nexus 6000 Series NX-OS Layer 2 Switching Configuration Guide, Release 7.x
11
Configuring VLANs
About VLAN Translation