vPC Peers

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.

Diagram

Classes

topology (vxlan)

Name	Type	Constraint	Mandatory	Default Value
vpc_peers	List	`[vpc_peers]`	No

vpc_peers (vxlan.topology)

Name	Type	Constraint	Mandatory	Default Value
peer1	String		Yes
peer1_peerlink_interfaces	List	`[peer1_peerlink_interfaces]`	No
peer2	String		Yes
peer2_peerlink_interfaces	List	`[peer2_peerlink_interfaces]`	No
fabric_peering	Boolean	`true`, `false`	No
domain_id	Integer	min: `1`, max: `1000`	No	`1`
vtep_vip	IP		No
vpc_interfaces	List	`[vpc_interfaces]`	No

peer1_peerlink_interfaces (vxlan.topology.vpc_peers)

Name	Type	Constraint	Mandatory	Default Value
name	String	Regex: `^(?:e\|eth(?:ernet)?)\d(?:\/\d+){1,2}$`	Yes

peer2_peerlink_interfaces (vxlan.topology.vpc_peers)

Name	Type	Constraint	Mandatory	Default Value
name	String	Regex: `^(?:e\|eth(?:ernet)?)\d(?:\/\d+){1,2}$`	Yes

vpc_interfaces (vxlan.topology.vpc_peers)

Name	Type	Constraint	Mandatory	Default Value
vpc_id	Integer	min: `1`, max: `4096`	Yes

Example 1 - vPC Peering with Physical Links

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.

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.

vxlan:
  topology:
    vpc_peers:
      - peer1: dc1-leaf1
        peer2: dc1-leaf2
        fabric_peering: true

Example 3 - Customize your vPC Domain ID

By default, NDFC automatically manages the Domain ID by selecting an ID from the range defined in vxlan.global.vpc.domain_id_range. Starting with release 0.4.3, you also have the option to manually manage the Domain ID using the workflow. When managed manually, the Domain ID will be allocated between both switches before initiating the vPC pairing.

To do this, you must configure the Domain ID under vxlan.topology.vpc_peers.domain_id.

The VPC Domain ID must be unique for every switch pair.

---
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
        domain_id: 10
        fabric_peering: false

Example 4 - Configure Secondary VTEP Address between Leaf Switches in vPC.

Starting with release 0.4.3, you can manually manage your underlay IP address by setting the parameter vxlan.underlay.general.manual_underlay_allocation to True. When this option is enabled, you must configure the IP address and specify the secondary IP address using the key vtep_vip.

---
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
        vtep_vip: 30.1.0.1
        fabric_peering: false