Resolving vPC Type-1 Inconsistency in VXLAN EVPN Setup

AD.

In a VXLAN E VPN setup with vPC Type-1 configuration, vPC peers use a single control plane and present a single logical device to the network. In this scenario, a vPC Type-1 inconsistency occurs when the vPC peers have different configurations that impact the forwarding behavior of traffic. To resolve the issue, the following two actions can be attempted:

A. Configure the NVE interfaces to be Up on both switches: NVE (Network Virtualization Edge) is a protocol used for encapsulating VXLAN traffic across an IP network. If NVE interfaces are not configured properly or are down on one of the switches, it can cause a vPC Type-1 inconsistency. Therefore, the first action that needs to be attempted is to check the NVE interfaces and ensure that they are Up on both switches. If they are down, they should be brought up to restore proper connectivity.

E. Set a different primary IP addresses on NVE source-interface: The primary IP address on the NVE source-interface is used for control plane communication between the vPC peers. If both vPC peers have the same primary IP address, it can cause a vPC Type-1 inconsistency. Therefore, the second action that needs to be attempted is to check the primary IP address on the NVE source-interface and ensure that they are different on both switches. If they are the same, one of them should be changed to a different address.

The other options are not directly related to the vPC Type-1 inconsistency and may not help in resolving the issue. For example, setting a different distributed gateway virtual MAC address (option B) or setting a different secondary IP addresses on NVE source-interface (option C) are not relevant to the vPC Type-1 inconsistency. Similarly, configuring the same VNI to multicast group mapping (option D) may not help in resolving the issue as it is related to the VXLAN configuration and not the vPC configuration.