This chapter contains the following sections:
Information About VXLAN
VXLAN has the following guidelines and limitations:
Bind NVE to a loopback address that is separate from other loopback addresses that are required by Layer 3 protocols. A best practice is to use a dedicated loopback address for VXLAN. This best practice should be applied not only for the VPC VXLAN deployment, but for all VXLAN deployments.
show commands with the internal keyword are not supported.
FEX ports do not support IGMP snooping on VXLAN VLANs.
Beginning with Cisco NX-OS Release 7.0(3)I4(2), VXLAN is supported for the Cisco Nexus 93108TC-EX and 93180YC-EX switches and for Cisco Nexus 9500 Series switches with the X9732C-EX line card.
DHCP snooping (Dynamic Host Configuration Protocol snooping) is not supported on VXLAN VLANs.
The device cannot be an IP transient device and a VXLAN terminating device for the same VXLAN or VXLANs that share the same transport multicast group.
SPAN TX for VXLAN encapsulated traffic is not supported for the Layer 3 uplink interface.
RACLs are not supported on Layer 3 uplinks for VXLAN traffic. Egress VACLs support is not available for de-capsulated packets in the network to access direction on the inner payload.
As a best practice, use PACLs/VACLs for the access to the network direction.
QoS classification is not supported for VXLAN traffic in the network to access direction on the Layer 3 uplink interface.
The QoS buffer-boost feature is not applicable for VXLAN traffic.
Only one NVE (Network Virtualization Edge) interface on a switch.
SNMP is not supported on the NVE interface.
VXLAN SVI uplinks are not supported over underlying Layer 2 VPC ports.
A VXLAN SVI uplink VLAN cannot be a member of the peer-link.
VTEP does not support Layer 3 subinterface uplinks. In addition, non-VXLAN subinterface VLANs cannot be shared with VXLAN VLANs.
For 6.1(2)I3(4) and earlier, VXLAN does not support consistency checks.
Point to multipoint Layer 3 and SVI uplinks are not supported. Since both uplink types can only be enabled point-to-point, they cannot span across more than two switches.
A FEX host interface port is not supported for a VLAN that is extended with VXLAN.
A loopback address is required when using the source-interface config command. The loopback address represents the local VTEP IP.
To establish IP multicast routing in the core, IP multicast configuration, PIM configuration, and RP configuration is required.
VTEP to VTEP unicast reachability can be configured through any IGP protocol.
When configuring BGP-EVPN on Cisco Nexus 9300-EX switches and Cisco Nexus 9500 switches with N9K-X9732C-EX line cards, use the system routing template-vxlan-scale command. Performing this step requires a reload of the switch. This command is not applicable on Cisco Nexus 9200 switches, Cisco Nexus 9300 switches, and Cisco Nexus 9500 switches with N9K-X9564PX, N9K-X9564TX, and N9K-X9536PQ line cards.
As a best practice when changing the IP address of a VTEP device, shut the NVE interface before changing the IP address.
Configuring an Rendezvous Point (RP) on a leaf node is not supported. As a best practice, the RP for the multicast group should be configured only on the spine layer. Use the anycast RP for RP load balancing and redundancy.
ip pim rp-address 1.1.1.10 group-list 224.0.0.0/4 ip pim anycast-rp 1.1.1.10 1.1.1.1 ip pim anycast-rp 1.1.1.10 1.1.1.2
![]() Note |
|
Bind NVE to a loopback address that is separate from other loopback addresses that are required by Layer 3 protocols. A best practice is to use a dedicated loopback address for VXLAN.
On VPC VXLAN, it is recommended to increase the delay restore interface-vlan timer under the VPC configuration, if the number of SVIs are scaled up. For example, if there are 1000 VNIs with 1000 SVIs, it is recommended to increase the delay restore interface-vlan timer to 45 Seconds.
The loopback address used by NVE needs to be configured to have a primary IP address and a secondary IP address.
The secondary IP address is used for all VxLAN traffic that includes multicast and unicast encapsulated traffic.
VPC peers must have identical configurations.
For multicast, the VPC node that receives the (S, G) join from the RP (rendezvous point) becomes the DF (designated forwarder). On the DF node, encap routes are installed for multicast.
Decap routes are installed based on the election of a decapper from between the VPC primary node and the VPC secondary node. The winner of the decap election is the node with the least cost to the RP. However, if the cost to the RP is the same for both nodes, the VPC primary node is elected.
The winner of the decap election has the decap mroute installed. The other node does not have a decap route installed.
On a VPC device, BUM traffic (broadcast, unknown-unicast, and multicast traffic) from hosts is replicated on the peer-link. A copy is made of every native packet and each native packet is sent across the peer-link to service orphan-ports connected to the peer VPC switch.
To prevent traffic loops in VXLAN networks, native packets ingressing the peer-link cannot be sent to an uplink. However, if the peer switch is the encapper, the copied packet traverses the peer-link and is sent to the uplink.
![]() Note | Each copied packet is sent on a special internal VLAN (VLAN 4041). |
When peer-link is shut, the loopback interface used by NVE on the VPC secondary is brought down and the status is Admin Shut. This is done so that the route to the loopback is withdrawn on the upstream and that the upstream can divert all traffic to the VPC primary.
![]() Note | Orphans connected to the VPC secondary will experience loss of traffic for the period that the peer-link is shut. This is similar to Layer 2 orphans in a VPC secondary of a traditional VPC setup. |
When peer-link is no-shut, the NVE loopback address is brought up again and the route is advertised upstream, attracting traffic.
For VPC, the loopback interface has 2 IP addresses: the primary IP address and the secondary IP address.
The primary IP address is unique and is used by Layer 3 protocols.
The secondary IP address on loopback is necessary because the interface NVE uses it for the VTEP IP address. The secondary IP address must be same on both vPC peers.
The VPC peer-gateway feature must be enabled on both peers.
As a best practice, use peer-switch, peer gateway, ip arp sync, ipv6 nd sync configurations for improved convergence in VPC topologies.
In addition, increase the STP hello timer to 4 seconds to avoid unnecessary TCN generations when VPC role changes occur.
The following is an example (best practice) of a VPC configuration:
switch# sh ru vpc version 6.1(2)I3(1) feature vpc vpc domain 2 peer-switch peer-keepalive destination 172.29.206.65 source 172.29.206.64 peer-gateway ipv6 nd synchronize ip arp synchronize
On a VPC pair, shutting down NVE or NVE loopback on one of the VPC nodes is not a supported configuration. This means that traffic failover on one-side NVE shut or one-side loopback shut is not supported.
When the NVE or loopback is shut in VPC configurations:
If the NVE or loopback is shut only on the primary VPC switch, the global VxLAN VPC consistency checker fails. Then the NVE, loopback, and VPCs are taken down on the secondary VPC switch.
If the NVE or loopback is shut only on the secondary VPC switch, the global VXLAN VPC consistency checker fails. Then the NVE, loopback, and secondary VPC are brought down on the secondary. Traffic continues to flow through the primary VPC switch.
As a best practice, you should keep both the NVE and loopback up on both the primary and secondary VPC switches.
Enabling vpc peer-gateway configuration is mandatory. For peer-gateway functionality, at least one SVI is required to be enabled across peer-link and also configured with PIM. This provides a backup path in the case when VTEP loses complete connectivity to the spine. Remote peer reachability is re-routed over peer-link in this case.
The following is an example of SVI with PIM enabled:
swithch# sh ru int vlan 2 interface Vlan2 description special_svi_over_peer-link no shutdown ip address 30.2.1.1/30 ip pim sparse-mode // example config for backup SVI: interface Vlan2000 description backup_svi_over_peer-link //change “special” into “backup” no shutdown no ip redirects ip address 20.20.20.1/24 no ipv6 redirects ip router ospf 1 area 0.0.0.0 ip pim sparse-mode ip igmp static-oif route-map match-mcast-groups route-map match-mcast-groups permit 1 match ip multicast group 225.1.1.1/32
![]() Note | In BUD node topologies, the backup SVI needs to be added as a static OIF for each underlay multicast group. |
![]() Note | The SVI must be configured on both VPC peers and requires PIM to be enabled. |
As a best practice when changing the secondary IP address of an anycast VPC VTEP, the NVE interfaces on both the VPC primary and the VPC secondary should be shut before the IP changes are made.
DHCP relay is supported when the DHCP server is reachable through a default VRF. However, DHCP relay is not supported when the DHCP client and DHCP server are in the same non-default VRF.
MTU Size in the Transport Network
Due to the MAC-to-UDP encapsulation, VXLAN introduces 50-byte overhead to the original frames. Therefore, the maximum transmission unit (MTU) in the transport network needs to be increased by 50 bytes. If the overlays use a 1500-byte MTU, the transport network needs to be configured to accommodate 1550-byte packets at a minimum. Jumbo-frame support in the transport network is required if the overlay applications tend to use larger frame sizes than 1500 bytes.
ECMP and LACP Hashing Algorithms in the Transport Network
As described in a previous section, Cisco Nexus 9000 Series Switches introduce a level of entropy in the source UDP port for ECMP and LACP hashing in the transport network. As a way to augment this implementation, the transport network uses an ECMP or LACP hashing algorithm that takes the UDP source port as an input for hashing, which achieves the best load-sharing results for VXLAN encapsulated traffic.
Multicast Group Scaling
The VXLAN implementation on Cisco Nexus 9000 Series Switches uses multicast tunnels for broadcast, unknown unicast, and multicast traffic forwarding. Ideally, one VXLAN segment mapping to one IP multicast group is the way to provide the optimal multicast forwarding. It is possible, however, to have multiple VXLAN segments share a single IP multicast group in the core network. VXLAN can support up to 16 million logical Layer 2 segments, using the 24-bit VNID field in the header. With one-to-one mapping between VXLAN segments and IP multicast groups, an increase in the number of VXLAN segments causes a parallel increase in the required multicast address space and the amount of forwarding states on the core network devices. At some point, multicast scalability in the transport network can become a concern. In this case, mapping multiple VXLAN segments to a single multicast group can help conserve multicast control plane resources on the core devices and achieve the desired VXLAN scalability. However, this mapping comes at the cost of suboptimal multicast forwarding. Packets forwarded to the multicast group for one tenant are now sent to the VTEPs of other tenants that are sharing the same multicast group. This causes inefficient utilization of multicast data plane resources. Therefore, this solution is a trade-off between control plane scalability and data plane efficiency.
Despite the suboptimal multicast replication and forwarding, having multiple-tenant VXLAN networks to share a multicast group does not bring any implications to the Layer 2 isolation between the tenant networks. After receiving an encapsulated packet from the multicast group, a VTEP checks and validates the VNID in the VXLAN header of the packet. The VTEP discards the packet if the VNID is unknown to it. Only when the VNID matches one of the VTEP’s local VXLAN VNIDs, does it forward the packet to that VXLAN segment. Other tenant networks will not receive the packet. Thus, the segregation between VXLAN segments is not compromised.
The following are considerations for the configuration of the transport network:
On the VTEP device:
Enable and configure IP multicast.
Create and configure a loopback interface with a /32 IP address.
(For vPC VTEPs, you must configure primary and secondary /32 IP addresses.)
Enable IP multicast on the loopback interface.
Advertise the loopback interface /32 addresses through the routing protocol (static route) that runs in the transport network.
Enable IP multicast on the uplink outgoing physical interface.
Throughout the transport network:
Configuring VXLAN
1.
configure terminal
2.
[no]
feature nv
overlay
3.
[no]
feature
vn-segment-vlan-based
4.
(Optional) copy running-config startup-config
1.
configure terminal
2.
vlan
vlan-id
3.
vn-segment
vnid
4.
exit
Command or Action | Purpose |
---|
An NVE interface is the overlay interface that terminates VXLAN tunnels.
You can create and configure an NVE (overlay) interface with the following:
1.
configure terminal
2.
interface nve
x
3.
source-interface
src-if
4.
member vni
vni
5.
mcast-group
start-address [end-address]
1.
configure terminal
2.
no
feature
vn-segment-vlan-based
3.
no
feature nv
overlay
4.
(Optional) copy running-config startup-config
Command or Action | Purpose | |
---|---|---|
Step 1 | configure terminal
|
Enters global configuration mode. |
Step 2 | no
feature
vn-segment-vlan-based
|
Disables the global mode for all VXLAN bridge domains |
Step 3 | no
feature nv
overlay
|
Disables the VXLAN feature. |
Step 4 | copy running-config startup-config
| (Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. |
To display the VXLAN configuration information, enter one of the following commands:
Command |
Purpose |
---|---|
show logging level nve |
Displays logging level. |
show tech-support nve |
Displays related NVE tech-support information. |
show run interface nve x |
Displays NVE overlay interface configuration. |
show nve interface |
Displays NVE overlay interface status. |
show nve peers |
Displays NVE peer status. |
show nve peers peer_IP_address interface interface_ID counters |
Displays per NVE peer statistics. |
clear nve peers peer_IP_address interface interface_ID counters |
Clears per NVE peer statistics. |
clear nve peer-ip peer-ip-address |
Clears stale NVE peers. Stale NVE peers are peers that do not have MAC addresses learnt behind them. |
show nve vni |
Displays VXLAN VNI status. |
show nve vni vni_number counters |
Displays per VNI statistics. |
clear nve vni vni_number counters |
Clears per VNI statistics. |
show nve vxlan-params |
Displays VXLAN parameters, such as VXLAN destination or UDP port. |
An example of a loopback interface configuration and routing protocol configuration:
Nexus 9000 VTEP-1 configuration:
switch-vtep-1(config)# feature ospf switch-vtep-1(config)# feature pim switch-vtep-1(config)# router ospf 1 switch-vtep-1(config-router)# router-id 100.100.100.1 switch-vtep-1(config)# ip pim rp-address 10.1.1.1 group-list 224.0.0.0/4 switch-vtep-1(config)# interface loopback0 switch-vtep-1(config-if)# ip address 100.100.100.1/32 switch-vtep-1(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-1(config-if)# ip pim sparse-mode switch-vtep-1(config)# interface e2/1 switch-vtep-1(config-if)# ip address 20.1.1.1/30 switch-vtep-1(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-1(config-if)# ip pim sparse-mode
switch-vtep-1(config)# feature nv overlay switch-vtep-1(config)# feature vn-segment-vlan-based switch-vtep-1(config)# interface e1/1 switch-vtep-1(config-if)# switchport switch-vtep-1(config-if)# switchport access vlan 10 switch-vtep-1(config-if)# no shutdown switch-vtep-1(config)# interface nve1 switch-vtep-1(config-if)# no shutdown switch-vtep-1(config-if)# source-interface loopback0 switch-vtep-1(config-if)# member vni 10000 mcast-group 230.1.1.1 switch-vtep-1(config)# vlan 10 switch-vtep-1(config-vlan)# vn-segment 10000 switch-vtep-1(config-vlan)# exit
Nexus 9000 VTEP-2 configuration:
switch-vtep-2(config)# feature ospf switch-vtep-2(config)# feature pim switch-vtep-2(config)# router ospf 1 switch-vtep-2(config-router)# router-id 100.100.100.2 switch-vtep-2(config)# ip pim rp-address 10.1.1.1 group-list 224.0.0.0/4 switch-vtep-2(config)# interface loopback0 switch-vtep-2(config-if)# ip address 100.100.100.2/32 switch-vtep-2(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-2(config-if)# ip pim sparse-mode switch-vtep-2(config)# interface e2/1 switch-vtep-2(config-if)# ip address 30.1.1.1/30 switch-vtep-2(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-2(config-if)# ip pim sparse-mode
switch-vtep-2(config)# feature nv overlay switch-vtep-2(config)# feature vn-segment-vlan-based switch-vtep-2(config)# interface e1/1 switch-vtep-2(config-if)# switchport switch-vtep-2(config-if)# switchport access vlan 10 switch-vtep-2(config-if)# no shutdown switch-vtep-2(config)# interface nve1 switch-vtep-2(config-if)# no shutdown switch-vtep-2(config-if)# source-interface loopback0 switch-vtep-2(config-if)# member vni 10000 mcast-group 230.1.1.1 switch-vtep-2(config)# vlan 10 switch-vtep-2(config-vlan)# vn-segment 10000 switch-vtep-2(config-vlan)# exit
An example of an ingress replication topology:
Nexus 9000 VTEP-1 configuration:
switch-vtep-1(config)# feature ospf switch-vtep-1(config)# router ospf 1 switch-vtep-1(config-router)# router-id 200.200.8.8 switch-vtep-1(config)# interface loopback0 switch-vtep-1(config-if)# ip address 200.200.8.8/32 switch-vtep-1(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-1(config)# interface e2/1 switch-vtep-1(config-if)# ip address 20.1.1.1/30 switch-vtep-1(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-1(config-if)# ip pim sparse-mode switch-vtep-1(config)# feature nv overlay switch-vtep-1(config)# feature vn-segment-vlan-based switch-vtep-1(config)# interface e1/1 switch-vtep-1(config-if)# switchport switch-vtep-1(config-if)# switch port mode trunk switch-vtep-1(config-if)# switch port allowed vlan 11-12 switch-vtep-1(config-if)# no shutdown switch-vtep-1(config)# vlan 11 switch-vtep-1(config-vlan)# vn-segment 10011 switch-vtep-1(config)# vlan 12 switch-vtep-1(config-vlan)# vn-segment 10012 switch-vtep-1(config)# interface nve1 switch-vtep-1(config-if)# no shutdown switch-vtep-1(config-if)# source-interface loopback0 switch-vtep-1(config-if)# member vni 10011 switch-vtep-1(config-if)# ingress-replication protocol static switch-vtep-1(config-if)# peer_ip 200.200.9.9 switch-vtep-1(config-if)# member vni 10012 switch-vtep-1(config-if)# ingress-replication protocol static switch-vtep-1(config-if)# peer_ip 200.200.9.9 switch-vtep-1(config-vlan)# exit
switch-vtep-1# show nve vni ingress-replication Interface VNI show nve vni ingress-replication Interface VNI Replication List Up Time --------- -------- ----------------- ------- nve1 10011 200.200.9.9 07:39:51 nve1 10012 200.200.9.9 07:39:40
Nexus 9000 VTEP-2 configuration:
switch-vtep-2(config)# feature ospf switch-vtep-2(config)# router ospf 1 switch-vtep-2(config-router)# router-id 200.200.9.9 switch-vtep-2(config)# interface loopback0 switch-vtep-2(config-if)# ip address 200.200.9.9/32 switch-vtep-2(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-2(config)# interface e2/1 switch-vtep-2(config-if)# ip address 30.1.1.1/30 switch-vtep-2(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-2(config-if)# ip pim sparse-mode switch-vtep-2(config)# feature nv overlay switch-vtep-2(config)# feature vn-segment-vlan-based switch-vtep-2(config)# interface e1/1 switch-vtep-2(config-if)# switchport switch-vtep-2(config-if)# switch port mode trunk switch-vtep-2(config-if)# switch port allowed vlan 11-12 switch-vtep-2(config-if)# no shutdown switch-vtep-2(config)# vlan 11 switch-vtep-2(config-vlan)# vn-segment 10011 switch-vtep-2(config)# vlan 12 switch-vtep-2(config-vlan)# vn-segment 10012 switch-vtep-2(config)# interface nve1 switch-vtep-2(config-if)# no shutdown switch-vtep-2(config-if)# source-interface loopback0 switch-vtep-2(config-if)# member vni 10011 switch-vtep-2(config-if)# ingress-replication protocol static switch-vtep-2(config-if)# peer_ip 200.200.8.8 switch-vtep-2(config-if)# member vni 10012 switch-vtep-2(config-if)# ingress-replication protocol static switch-vtep-2(config-if)# peer_ip 200.200.8.8 switch-vtep-2(config-vlan)# exit
switch-vtep-2# show nve vni ingress-replication Interface VNI Replication List Up Time --------- -------- ----------------- ------- nve1 10011 200.200.8.8 07:42:23 200.200.10.10 07:42:23 nve1 10012 200.200.8.8 07:42:23
For a vPC VTEP configuration, the loopback address requires a secondary IP.
An example of a vPC VTEP configuration:
Nexus 9000 VTEP-1 configuration:
switch-vtep-1(config)# feature nv overlay switch-vtep-1(config)# feature vn-segment-vlan-based
switch-vtep-1(config)# feature ospf switch-vtep-1(config)# feature pim switch-vtep-1(config)# router ospf 1 switch-vtep-1(config-router)# router-id 200.200.200.1 switch-vtep-1(config)# ip pim rp-address 10.1.1.1 group-list 224.0.0.0/4 switch-vtep-1(config)# interface loopback0 switch-vtep-1(config-if)# ip address 200.200.200.1/32 switch-vtep-1(config-if)# ip address 100.100.100.1/32 secondary switch-vtep-1(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-1(config-if)# ip pim sparse-mode switch-vtep-1(config)# interface e2/1 switch-vtep-1(config-if)# ip address 20.1.1.1/30 switch-vtep-1(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-1(config-if)# ip pim sparse-mode
switch-vtep-1(config)# interface port-channel 10 switch-vtep-1(config-if)# vpc 10 switch-vtep-1(config-if)# switchport switch-vtep-1(config-if)# switchport mode access switch-vtep-1(config-if)# switchport access vlan 10 switch-vtep-1(config-if)# no shutdown switch-vtep-1(config)# interface e1/1 switch-vtep-1(config-if)# channel-group 10 mode active switch-vtep-1(config-if)# no shutdown
switch-vtep-1(config)# interface nve1 switch-vtep-1(config-if)# no shutdown switch-vtep-1(config-if)# source-interface loopback0 switch-vtep-1(config-if)# member vni 10000 mcast-group 230.1.1.1 switch-vtep-1(config)# vlan 10 switch-vtep-1(config-vlan)# vn-segment 10000 switch-vtep-1(config-vlan)# exit
Nexus 9000 VTEP-2 configuration:
switch-vtep-2(config)# feature nv overlay switch-vtep-2(config)# feature vn-segment-vlan-based
switch-vtep-2(config)# feature ospf switch-vtep-2(config)# feature pim switch-vtep-2(config)# router ospf 1 switch-vtep-2(config-router)# router-id 200.200.200.2 switch-vtep-2(config)# ip pim rp-address 10.1.1.1 group-list 224.0.0.0/4 switch-vtep-2(config)# interface loopback0 switch-vtep-2(config-if)# ip address 200.200.200.2/32 switch-vtep-2(config-if)# ip address 100.100.100.1/32 secondary switch-vtep-2(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-2(config-if)# ip pim sparse-mode switch-vtep-2(config)# interface e2/1 switch-vtep-2(config-if)# ip address 20.1.1.5/30 switch-vtep-2(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-2(config-if)# ip pim sparse-mode
switch-vtep-2(config)# interface port-channel 10 switch-vtep-2(config-if)# vpc 10 switch-vtep-2(config-if)# switchport switch-vtep-2(config-if)# switchport mode access switch-vtep-2(config-if)# switchport access vlan 10 switch-vtep-2(config-if)# no shutdown switch-vtep-2(config)# interface e1/1 switch-vtep-2(config-if)# channel-group 10 mode active switch-vtep-2(config-if)# no shutdown
switch-vtep-2(config)# interface nve1 switch-vtep-2(config-if)# no shutdown switch-vtep-2(config-if)# source-interface loopback0 switch-vtep-2(config-if)# member vni 10000 mcast-group 230.1.1.1 switch-vtep-2(config)# vlan 10 switch-vtep-2(config-vlan)# vn-segment 10000 switch-vtep-2(config-vlan)# exit
Nexus 9000 VTEP-3 configuration:
switch-vtep-3(config)# feature nv overlay switch-vtep-3(config)# feature vn-segment-vlan-based
switch-vtep-3(config)# feature ospf switch-vtep-3(config)# feature pim switch-vtep-3(config)# router ospf 1 switch-vtep-3(config-router)# router-id 100.100.100.2 switch-vtep-3(config)# ip pim rp-address 10.1.1.1 group-list 224.0.0.0/4 switch-vtep-3(config)# interface loopback0 switch-vtep-3(config-if)# ip address 100.100.100.2/32 switch-vtep-3(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-3(config-if)# ip pim sparse-mode switch-vtep-3(config)# interface e2/1 switch-vtep-3(config-if)# ip address 30.1.1.1/30 switch-vtep-3(config-if)# ip router ospf 1 area 0.0.0.0 switch-vtep-3(config-if)# ip pim sparse-mode
switch-vtep-3(config)# interface e1/1 switch-vtep-3(config-if)# switchport switch-vtep-3(config-if)# switchport access vlan 10 switch-vtep-3(config-if)# no shutdown switch-vtep-3(config)# interface nve1 switch-vtep-3(config-if)# no shutdown switch-vtep-3(config-if)# source-interface loopback0 switch-vtep-3(config-if)# member vni 10000 mcast-group 230.1.1.1 switch-vtep-3(config)# vlan 10 switch-vtep-3(config-vlan)# vn-segment 10000 switch-vtep-3(config-vlan)# exit
![]() Note | The secondary IP is used by the emulated VTEP for VXLAN. |
![]() Note | Ensure that all configurations are identical between the VPC primary and VPC secondary. |