Cisco Nexus 9000 Series Configuration Manual page 29

Nx-os vxlan
Hide thumbs Also See for Nexus 9000 Series:
Table of Contents

Advertisement

Configuring VXLAN
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
• When the NVE or loopback is shut in VPC configurations:
As a best practice, you should keep both the NVE and loopback up on both the primary and secondary
VPC switches.
• Redundant anycast RPs configured in the network for multicast load-balancing and RP redundancy are
supported on VPC VTEP topologies.
• Enabling vpc peer-gateway configuration is mandatory. For peer-gateway functionality, at least one
backup routing SVI is required to be enabled across peer-link and also configured with PIM. This
provides a backup routing path in the case when VTEP loses complete connectivity to the spine. Remote
peer reachability is re-routed over peer-link in his case. In BUD node topologies, the backup SVI needs
to be added as a static OIF for each underlay multicast group.
The following is an example of backup SVI with PIM enabled:
swithch# sh ru int vlan 2
interface Vlan2
route-map match-mcast-groups permit 1
Note
Note
peer-switch
peer-keepalive destination 172.29.206.65 source 172.29.206.64
peer-gateway
ipv6 nd synchronize
ip arp synchronize
◦ 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.
description backupl_svi_over_peer-link
no shutdown
ip address 30.2.1.1/30
ip router ospf 1 area 0.0.0.0
ip pim sparse-mode
ip igmp static-oif route-map match-mcast-groups
match ip multicast group 225.1.1.1/32
In BUD node topologies, the backup SVI needs to be added as a static OIF for each
underlay multicast group.
The SVI must be configured on both VPC peers and requires PIM to be enabled.
Cisco Nexus 9000 Series NX-OS VXLAN Configuration Guide, Release 7.x
Guidelines and Limitations for VXLAN
17

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents