The vpc_peers configuration allows to define the vpc pairs in the fabric. This includes defining the 2 switches that belong to a pair and the interfaces that the switches will use for the vpc peering.
The supported workflows are “Provision” and “Decommission” only. In other words, the configuration of any vpc pair cannot be edited after deployment, to scale up or down the peer interfaces or change the vpc pairs. The recommended method to perform changes to a already deployed vpc pair is, to delete the vpc pair completely and create them fresh.
This configuration defines the settings for creating a vPC domain between the dc1-leaf1/dc1-leaf2 pair and the dc1-leaf3/dc1-leaf4. The dc1-leaf1/dc1-leaf2 pair have interfaces Ethernet1/3 and Ethernet1/4 as member interfaces of the peer-link while the dc1-leaf3/dc1-leaf4 pair only contains interface Ethernet1/3 as member interface of the peer-link.
topology_vpc-peers.nac.yaml
vxlan:
topology:
vpc_peers:
- peer1: dc1-leaf1
peer2: dc1-leaf2
peer1_peerlink_interfaces:
- name: Ethernet1/3
- name: Ethernet1/4
peer2_peerlink_interfaces:
- name: Ethernet1/3
- name: Ethernet1/4
- peer1: dc1-leaf3
peer2: dc1-leaf4
peer1_peerlink_interfaces:
- name: Ethernet1/3
peer2_peerlink_interfaces:
- name: Ethernet1/3
Example 2 - vPC Peering using Fabric Peering
This configuration defines the settings for creating a vPC domain between the dc1-leaf1/dc1-leaf2 pair. In this example Fabric Peering is used so there are no interfaces.