Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Static VXLAN Tunnels with Q-in-Q

For small MC-LAG networks, you can use static VXLAN to reduce the control plane complexity in your network. Configuring VTEPs on a static VXLAN is straightforward. Use this example to configure static VXLAN tunnels with Q-in-Q tagging (VLAN translation) between data centers. In this example, we focus on the following features:

Figure 1 shows a portion of a spine-leaf data center (POD). Within the POD, the TOR devices (TOR1 and TOR2) collect VLANs from the servers below and also manages the VLAN translations (Q-in-Q tunnels). The aggregators collect VLANs from different TOR devices and function as the gateway for the POD. We use a static VXLAN tunnel as a gateway between two PODs. We configure MC-LAG between the peer TOR devices and the peer aggregators. In our reference test environment, we tested a configuration with 64 pods. For this example, we describe how to configure the aggregators and TOR devices in a single pod.

Figure 1: Data Center POD with Q-in-Q and Static VXLAN Tunnels Data Center POD with Q-in-Q and Static VXLAN Tunnels

This example is configured on top of an existing IP Fabric. See IP Fabric Underlay Network Design and Implementation.

Configuring the Aggregators

The following section describes how to configure the aggregators.

  1. Configure the aggregators to support aggregated Ethernet and MC-LAG.
    • Set the maximum number of aggregated Ethernet interfaces.

    • Set the service identifier (SID) for the LAG.

    • Configure a loopback address.

    • Configure a management port. We use the management interface as an "always up" port to support the keepalive communication between ICCP peers.

    AGG1 and AGG2

    AGG1

    AGG2

  2. Assign the aggregated Ethernet interfaces.
    • ae0 and ae1 forms the ICL and ICCP links between the aggregators.

    • ae3 connects the aggregator to the spine devices.

    • ae4 connects the aggregators to the TOR devices.

    AGG1 and AGG2

  3. Enable LACP on the aggregated Ethernet interfaces. Enable LACP with the fast periodic interval to send a packet every second.

    AGG1 and AGG2

  4. Configure the MC-LAG interfaces from the aggregators to the TOR devices and set it to active-active mode. Set a unique chassis ID for each peer.

    AGG1 and AGG2

    AGG1

    AGG2

  5. Configure the ICCP peers (AGG1 and AGG2) across the ICL. We use the IP address of the management link when we configure backup-liveness-detection to exchange keepalive messages.

    AGG1

    AGG2

  6. Configure the interfaces to support VLANs.

    AGG1 and AGG2

  7. Configure the interface to the Spine devices.

    AGG1

    AGG2

  8. Enable static VXLAN by configuring the local and remote VTEP interfaces.

    AGG1 and AGG2

  9. Map the VLANs to the remote VTEP.

    AGG1 and AGG2

Configuring the TOR Devices

The following section describes how to configure the TOR devices.

  1. Configure the TOR device to support aggregated Ethernet and MC-LAG.
    • Set the maximum number of aggregated Ethernet interfaces.

    • Set the SID for the LAG.

    • Configure a loopback address.

    • Configure a management port. We use the management interface as an "always up" port to support the keepalive communication between ICCP peers.

    TOR1 and TOR2

    TOR1

    TOR2

  2. Assign the aggregated Ethernet interfaces.
    • ae0 and ae1 form the ICL and ICCP link between the TOR devices.

    • ae4 connects the TOR devices to the aggregators.

    • ae7 and ae8 connect the TOR devices to the servers.

    TOR1 and TOR2

  3. Enable LACP on the aggregated Ethernet interfaces. Enable LACP with a fast periodic interval to send a packet every second.

    TOR1 and TOR2

  4. Configure the interfaces to support VLANs and Q-in-Q translation.
    Note:

    When you configure Q-in-Q mapping, the device selects the lowest value in the VLAN ID range as the outer tag. For example, with a range of 3000-3001 in our vlan-id-list, our device uses the VLAN 3000 as the outer tag. When the device receives an outgoing packet with a VLAN in the 3000 to 3001 range, the device pushes an outer tag of with a VLAN ID of 3000. Conversely, the device strips the outer tag for incoming packets with a VLAN ID of 3000 in its outer tag.

    TOR1 and TOR2

  5. Configure the MC-LAG interfaces from the TOR devices to the aggregators and servers and set it to active-active mode. Set a unique chassis ID for each peer.

    TOR1 and TOR2

    TOR1

    TOR2

  6. Configure ICCP across the ICL between the two TOR peers (TOR1 and TOR2). We use the IP address of the management link when we configure backup-liveness-detection to exchange keepalive messages.

    TOR1

    TOR2

Verify the Static VXLAN Tunnels with Q-in-Q on Aggregators

This section shows how to verify the operation of the aggregators as it manages VLANs through the static VXLAN tunnels. All commands are issued on AGG1.

  1. Display the VLAN information.
  2. Verify the operational status of the multichassis aggregated Ethernet link.
  3. Verify the MC-LAG status between AGG1 and AGG2.
  4. Verify the LACP status on the aggregated Ethernet interface.
  5. Verify the local and remote VTEP interfaces for the Static VXLAN is operational.

Verify Q-in-Q Tunnels on the TOR Devices

This section shows how you verify the operation of VLANs on one of the TOR Device. All commands are issued on TOR1

  1. Display the VLAN information.
  2. Verify the operational status of the multichassis aggregated Ethernet link.
  3. Verify the LACP status on the aggregated Ethernet interface.
  4. Verify the MC-LAG status between TOR1 and TOR2.