Cisco Nexus 9000 Series Configuration Manual page 33

Configuring VXLAN
• PV switching and PV routing are not supported on FEX ports.
• On Cisco Nexus 9300 Series switches, PV routing is not supported on 40G ports.
• PV routing supports configuring an SVI on the translated VLAN for flood and learn and BGP EVPN
mode for VXLAN.
• VLAN translation (mapping) is supported on Cisco Nexus 9000 Series switches with a Network
Forwarding Engine (NFE).
• When changing a property on a translated VLAN, the port that has mapping a configuration with that
VLAN as the translated VLAN, should be flapped to ensure correct behavior.
For example:
Int eth 1/1
switchport vlan mapping 101 10
.
.
.
/***Deleting vn-segment from vlan 10.***/
/***Adding vn-segment back.***/
/***Flap Eth 1/1 to ensure correct behavior.***/
• When adding a member to an existing port channel using the force command, the "mapping enable"
configuration must be consistent.
For example:
Int po 101
switchport vlan mapping enable
switchport vlan mapping 101 10
switchport trunk allowed vlan 10
int eth 1/8
/***No configuration***/
Now int po 101 has the "switchport vlan mapping enable" configuration, while eth 1/8 does not. If you
want to add eth 1/8 to port channel 101, you first need to apply the "switchport vlan mapping enable"
configuration on eth 1/8, and then use the force command.
int eth 1/8
switchport vlan mapping enable
channel-group 101 force
• Port VLAN mapping is not supported on Cisco Nexus 9200 Series switches.
Beginning with Cisco NX-OS Release 7.0(3)I6(1), port VLAN switching is supported on Cisco Nexus
9500 and 9300 platform switches. However, PV routing is not supported on Cisco Nexus 9500 and 9300
platform switches.
• VLAN mapping helps with VLAN localization to a port, scoping the VLANs per port. A typical use
case is in the service provider environment where the service provider leaf switch has different customers
with overlapping VLANs that come in on different ports. For example, customer A has VLAN 10 coming
in on Eth 1/1 and customer B has VLAN 10 coming in on Eth 2/2.
In this scenario, you can map the customer VLAN to a provider VLAN and map that to an L2 VNI.
There is an operational benefit of terminating different customer VLANs and mapping them to the
fabric-managed-VLANs, L2 VNIs.
Configuring Port VLAN Mapping on a Trunk Port
Cisco Nexus 9000 Series NX-OS VXLAN Configuration Guide, Release 7.x
21