Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring IRB Interfaces in an EVPN-VXLAN Environment to Provide Layer 3 Connectivity for Hosts in a Data Center

 

Starting with Junos OS Release 15.1X53-D30, you can use integrated routing and bridging (IRB) interfaces to route data packets between Virtual Extensible LANs (VXLANs) that are implemented in an Ethernet VPN (EVPN)-VXLAN environment. In this example, the IRB interfaces provide Layer 3 connectivity for physical servers, on which applications directly run, in the same data center.

Requirements

This example uses the following hardware and software components:

  • Two QFX10002 switches (Spine 1 and Spine 2) running Junos OS Release 15.1X53-D30 software.

  • Four QFX5100 switches (Leaf 1 through Leaf 4) running Junos OS Release 14.1X53-D30 software.

  • Leaf 1 and Leaf 2 that are connected to one physical server (Server A), and Leaf 3 and Leaf 4 that are connected to another physical server (Server B).

Overview

In this example, physical servers that support two groups in a customer’s organization must exchange large volumes of data. To meet this need, the following protocols are implemented:

  • EVPN is used to establish a Layer 2 virtual bridge to connect the two physical servers.

  • Within the EVPN topology, BGP is used to exchange route information.

  • VXLAN is used to tunnel the data packets through the underlying Layer 3 fabric. The use of VXLAN encapsulation preserves the Layer 3 fabric for use by routing protocols.

  • IRB interfaces are used to route data packets between the VXLANs.

In this example, IRB interfaces are configured on the spine devices only. With this configuration, the spine devices function as Layer 3 gateways for the physical servers that are connected through their respective leaf devices. When the physical servers in the two customer sites exchange data, the spine devices route the data packets to their respective destinations.

Topology

The simple IP Clos topology shown in Figure 1 includes two spine switches, four leaf switches, and two physical servers. Each leaf switch has a connection to each of the spine switches for redundancy. Table 1 maps the interfaces shown in Figure 1 with their assigned IP addresses.

Physical server A supports group 1, and physical server B supports group 2 in the same customer organization. The customer network is segmented into four VXLANs. VXLANs v0001 and v0002 support group 1, and VXLANs v0005 and v0006 support group 2. Table 2 shows key entities, including IRB interfaces, that are configured for customer groups 1 and 2. Each VXLAN is supported by an IRB interface, over which data packets from the other VXLANs are routed.

Figure 1: EVPN-VXLAN Topology
EVPN-VXLAN Topology

Table 1: Mapping of Interfaces with IP Addresses

Interface Names

IP Addresses

Devices with Which Interfaces Connect

Spine 1

et-1/0/0.0

10.1.24.10/24

Leaf 1

et-1/0/1.0

10.1.25.10/24

Leaf 2

et-1/0/4.0

10.1.28.10/24

Leaf 3

et-1/0/5.0

10.1.29.10/24

Leaf 4

Spine 2

et-0/0/0.0

10.1.12.9/24

Leaf 1

et-0/0/2.0

10.1.13.9/24

Leaf 2

et-0/0/8.0

10.1.4.9/24

Leaf 3

et-0/0/11.0

10.1.41.9/24

Leaf 4

Leaf 1

et-0/0/49.0

10.1.12.3/24

Spine 2

et-0/0/50.0

10.1.24.3/24

Spine 1

Leaf 2

et-0/0/49.0

10.1.13.4/24

Spine 2

et-0/0/50.0

10.1.25.4/24

Spine 1

Leaf 3

et-0/0/48.0

10.1.4.7/24

Spine 2

et-0/0/50.0

10.1.28.7/24

Spine 1

Leaf 4

et-0/0/50.0

10.1.29.8/24

Spine 1

et-0/0/52.0

10.1.41.8/24

Spine 2

Table 2: Key Entities Configured for Customer Groups 1 and 2

Entity

Entity for Customer Group 1

Entity for Customer Group 2

VXLAN

v0001

v0005

v0002

v0006

VNI

1

5

2

6

VLAN ID

1

5

2

6

IRB interface

irb.1

irb.5

irb.2

irb.6

When configuring the entities in Table 2, keep the following in mind:

  • Each VXLAN must be assigned an IP address with a different IP subnet than the other VXLANs.

  • Each VXLAN must be assigned a unique VXLAN network identifier (VNI).

  • Each IRB interface must be specified as part of a Layer 3 virtual routing fowarding (VRF) instance.

  • The configuration of each IRB interface must include a default gateway address, which you can specify by including the virtual-gateway-address configuration statement at the [interfaces irb unit logical-unit-number family inet address ip-address] hierarchy level. Configuring the default gateway sets up a redundant default gateway for each IRB interface.

  • Policies must be set up to enable the exchange of data packets between the four VXLANs.

Note

When setting up a routing instance for EVPN-VXLAN, you must include a loopback interface. You must also specify an IP address for the interface using the set interfaces lo0 unit logical-unit-number family inet address ip-address/prefix. If you inadvertently omit the loopback interface and associated IP address, EVPN control packets cannot be processed.

Spine 1: Underlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Spine 1: Configure the Underlay Network

Step-by-Step Procedure

To configure the underlay network on Spine 1:

  1. Configure the Layer 3 interfaces.

  2. Specify an IP address for the loopback interface. This IP address serves as the source IP address in the outer header of any VXLAN-encapsulated packets.

  3. Set the routing options.

  4. Configure a BGP group that includes peers that handle underlay functions.

    Note

    In this configuration, the EBGP peers are in the same subnet. However, if your configuration includes EBGP peers in different subnets, you must include the set protocols bgp group underlay accept-remote-nexthop command so that the BGP routes appear in the routing table as direct routes. VXLAN requires direct next hops for equal-cost multipath (ECMP) load balancing.

  5. Configure a per-packet load-balancing policy.

  6. Configure a policy that enables BGP to advertise direct interfaces such as loopback interface lo0.

Spine 1: Overlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Overlay Network on Spine 1

Step-by-Step Procedure

To configure the overlay network on Spine 1:

  1. Configure an internal BGP (iBGP) group for the EVPN-VXLAN overlay.

  2. Configure VXLAN encapsulation for the data packets exchanged between the EVPN neighbors.

  3. Specify a tunnel type used for passing multicast traffic between Juniper Networks switches in an EVPN-VXLAN environment.

  4. Set up a policy to handle Layer 2 EVPN traffic.

  5. Configure options for the default routing instance (virtual switch type).

Spine 1: Customer Profile Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Note

When setting up a routing instance for EVPN-VXLAN, you must include a loopback interface. You must also specify an IP address for the interface using the set interfaces lo0 unit logical-unit-number family inet address ip-address/prefix. If you inadvertently omit the loopback interface and associated IP address, EVPN control packets cannot be processed.

Step-by-Step Procedure

To configure profiles for the two customer groups:

  1. Configure the IRB interfaces that enable communication among VXLANs 1, 2, 5, and 6.

  2. Configure a loopback interface for each customer group.

  3. Specify which VNIs are included in the EVPN-VXLAN domains.

  4. Configure a route target for each VNI.

    Note

    In this configuration, the spine devices run Junos OS Release 15.1X53-D30, and the leaf devices run 14.1X53-D30. In these software releases, when you include the vrf-target configuration statement in the [edit protocols evpn vni-options vni] hierarchy level, you must also include the export option as shown in this step. Note that later Junos OS releases might not require this option. However, if you include the export option in a software release in which it is not required, the system still commits the configuration.

  5. Configure policies that accept and import overlay routes.

  6. Set up communities for the customer groups and VXLANs. .

  7. Set up a routing instance for customer group 1.

    Note

    When setting up a routing instance for EVPN-VXLAN, you must include a loopback interface. You must also specify an IP address for the interface using the set interfaces lo0 unit logical-unit-number family inet address ip-address/prefix. If you inadvertently omit the loopback interface and associated IP address, EVPN control packets cannot be processed.

  8. Set up a routing instance for customer group 2.

    Note

    When setting up a routing instance for EVPN-VXLAN, you must include a loopback interface. You must also specify an IP address for the interface using the set interfaces lo0 unit logical-unit-number family inet address ip-address/prefix. If you inadvertently omit the loopback interface and associated IP address, EVPN control packets cannot be processed.

  9. Configure VXLANs v0001, v0002, v0005, and v0006, and associate the corresponding VNIs and IRB interfaces with each VXLAN.

  10. Configure the importing of routes from one customer VRF instance into the other.

Spine 2: Underlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Underlay Network on Spine 2

Step-by-Step Procedure

To configure the underlay network on Spine 2:

  1. Configure the Layer 3 interfaces.

  2. Specify an IP address for the loopback interface. This IP address serves as the source IP address in the outer header of any VXLAN-encapsulated packets.

  3. Set the routing options.

  4. Configure a BGP group that includes peers that handle underlay functions.

    Note

    In this configuration, the EBGP peers are in the same subnet. However, if your configuration includes EBGP peers in different subnets, you must include the set protocols bgp group underlay accept-remote-nexthop command so that the BGP routes appear in the routing table as direct routes. VXLAN requires direct next hops for equal-cost multipath (ECMP) load balancing.

  5. Configure a policy that spreads traffic across multiple paths between the Juniper Networks switches.

  6. Configure a policy that enables BGP to advertise direct interfaces such as loopback interface lo0.

Spine 2: Overlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Overlay Network on Spine 2

Step-by-Step Procedure

To configure the overlay network on Spine 2:

  1. Configure an IBGP group for the EVPN-VXLAN overlay.

  2. Configure VXLAN encapsulation for the data packets exchanged between the EVPN neighbors.

  3. Specify a tunnel type used for passing multicast traffic between Juniper Networks switches in an EVPN-VXLAN environment.

  4. Set up a policy to handle Layer 2 EVPN traffic.

  5. Configure options for the default routing instance (virtual switch type).

Spine 2: Customer Profile Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Note

When setting up a routing instance for EVPN-VXLAN, you must include a loopback interface. You must also specify an IP address for the interface using the set interfaces lo0 unit logical-unit-number family inet address ip-address/prefix. If you inadvertently omit the loopback interface and associated IP address, EVPN control packets cannot be processed.

Step-by-Step Procedure

To configure profiles for the two customer groups:

  1. Configure the IRB interfaces that enable communication among VXLANs v0001, v0002, v0005, and v0006.

  2. Configure a loopback interface for each customer group.

  3. Specify which VNIs are included in the EVPN-VXLAN domains.

  4. Configure a route target for each VNI.

    Note

    In this configuration, the spine devices run Junos OS Release 15.1X53-D30, and the leaf devices run 14.1X53-D30. In these software releases, when you include the vrf-target configuration statement in the [edit protocols evpn vni-options vni] hierarchy level, you must also include the export option as shown in this step. Note that later Junos OS releases might not require this option. However, if you include the export option in a software release in which it is not required, the system still commits the configuration.

  5. Configure policies that accept and import overlay routes.

  6. Set up communities for the customer groups and VXLANs.

  7. Set up a routing instance for customer 1.

    Note

    When setting up a routing instance for EVPN-VXLAN, you must include a loopback interface. You must also specify an IP address for the interface using the set interfaces lo0 unit logical-unit-number family inet address ip-address/prefix. If you inadvertently omit the loopback interface and associated IP address, EVPN control packets cannot be processed.

  8. Set up a routing instance for customer 2.

    Note

    When setting up a routing instance for EVPN-VXLAN, you must include a loopback interface. You must also specify an IP address for the interface using the set interfaces lo0 unit logical-unit-number family inet address ip-address/prefix. If you inadvertently omit the loopback interface and associated IP address, EVPN control packets cannot be processed.

  9. Configure VXLANs v0001, v0002, v0005, and v0006, and associate the corresponding VNIs and IRB interfaces with each VXLAN.

  10. Configure the importing of routes from one customer VRF instance into the other.

Step-by-Step Procedure

Leaf 1: Underlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Underlay Network for Leaf 1

Step-by-Step Procedure

To configure the underlay network for Leaf 1:

  1. Configure the Layer 3 interfaces.

  2. Specify an IP address for the loopback interface. This IP address serves as the source IP address in the outer header of any VXLAN-encapsulated packets.

  3. Set the routing options.

  4. Configure a BGP group that includes peers that handle underlay functions.

    Note

    In this configuration, the EBGP peers are in the same subnet. However, if your configuration includes EBGP peers in different subnets, you must include the set protocols bgp group underlay accept-remote-nexthop command so that the BGP routes appear in the routing table as direct routes. VXLAN requires direct next hops for equal-cost multipath (ECMP) load balancing.

  5. Configure a policy that spreads traffic across multiple paths between the Juniper Networks switches.

  6. Configure a policy that enables BGP to advertise direct interfaces such as loopback interface lo0.

Leaf 1: Overlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Overlay Network for Leaf 1

Step-by-Step Procedure

To configure the overlay network for Leaf 1:

  1. Configure an IBGP group for the EVPN-VXLAN overlay network.

  2. Configure VXLAN encapsulation for the data packets exchanged between the EVPN neighbors.

  3. Specify a tunnel type used for passing multicast traffic between Juniper Networks switches in an EVPN-VXLAN environment.

  4. Set up a policy to handle Layer 2 EVPN traffic.

  5. Configure options for the default routing instance (virtual switch type).

Leaf 1: Customer Profile Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Customer Profiles for Leaf 1

Step-by-Step Procedure

To configure the customer profiles for the two customer groups:

  1. Configure a Layer 2 Ethernet interface for the connection with the physical server. This interface is associated with VXLANs v0001, v0002, v0005, and v0006.

  2. Configure a route target for each VNI.

    Note

    In this configuration, the spine devices run Junos OS Release 15.1X53-D30, and the leaf devices run 14.1X53-D30. In these software releases, when you include the vrf-target configuration statement in the [edit protocols evpn vni-options vni] hierarchy level, you must also include the export option as shown in this step. Note that later Junos OS releases might not require this option. However, if you include the export option in a software release in which it is not required, the system still commits the configuration.

  3. Specify which VNIs are included in the EVPN-VXLAN domains.

  4. Configure policies that accept and import overlay routes.

  5. Set up communities for the customer groups and VXLANs.

  6. Configure VXLANs v0001, v0002, v0005, and v0006.

Leaf 2: Underlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Underlay Network for Leaf 2

Step-by-Step Procedure

To configure the underlay network for Leaf 2:

  1. Configure the Layer 3 interfaces.

  2. Specify an IP address for the loopback interface. This IP address serves as the source IP address in the outer header of any VXLAN-encapsulated packets.

  3. Set the routing options.

  4. Configure a BGP group that includes peers that handle underlay functions.

    Note

    In this configuration, the EBGP peers are in the same subnet. However, if your configuration includes EBGP peers in different subnets, you must include the set protocols bgp group underlay accept-remote-nexthop command so that the BGP routes appear in the routing table as direct routes. VXLAN requires direct next hops for equal-cost multipath (ECMP) load balancing.

  5. Configure a policy that spreads traffic across multiple paths between the Juniper Networks switches.

  6. Configure a policy that enables BGP to advertise direct interfaces such as loopback interface lo0.

Leaf 2: Overlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Overlay Network for Leaf 2

Step-by-Step Procedure

To configure the overlay network for Leaf 2:

  1. Configure an IBGP group for the EVPN-VXLAN overlay network.

  2. Configure VXLAN encapsulation for the data packets exchanged between the EVPN neighbors.

  3. Specify a tunnel type used for passing multicast traffic between Juniper Networks switches in an EVPN-VXLAN environment.

  4. Set up a policy to handle Layer 2 EVPN traffic.

  5. Configure options for the default routing instance (virtual switch type).

Leaf 2: Customer Profile Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Customer Profiles for Leaf 2

Step-by-Step Procedure

To configure profiles for the two customer groups:

  1. Configure a Layer 2 Ethernet interface for the connection with the physical server. This interface is associated with VXLANs v0001, v0002, v0005, and v0006.

  2. Configure a route target for each VNI.

    Note

    In this configuration, the spine devices run Junos OS Release 15.1X53-D30, and the leaf devices run 14.1X53-D30. In these software releases, when you include the vrf-target configuration statement in the [edit protocols evpn vni-options vni] hierarchy level, you must also include the export option as shown in this step. Note that later Junos OS releases might not require this option. However, if you include the export option in a software release in which it is not required, the system still commits the configuration.

  3. Specify which VNIs are included in the EVPN-VXLAN domains.

  4. Configure policies that accept and import overlay routes.

  5. Set up the communities.

  6. Configure VXLANs v0001, v0002, v0005, and v0006.

Leaf 3: Underlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Underlay Network for Leaf 3

Step-by-Step Procedure

To configure the underlay network for Leaf 3:

  1. Configure the Layer 3 interfaces.

  2. Specify an IP address for the loopback interface. This IP address serves as the source IP address in the outer header of any VXLAN-encapsulated packets.

  3. Set the routing options.

  4. Configure a BGP group that includes peers that handle underlay functions.

    Note

    In this configuration, the EBGP peers are in the same subnet. However, if your configuration includes EBGP peers in different subnets, you must include the set protocols bgp group underlay accept-remote-nexthop command so that the BGP routes appear in the routing table as direct routes. VXLAN requires direct next hops for equal-cost multipath (ECMP) load balancing.

  5. Configure a policy that spreads traffic across multiple paths between the Juniper Networks switches.

  6. Configure a policy that enables BGP to advertise direct interfaces such as loopback interface lo0.

Leaf 3: Overlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Overlay Network for Leaf 3

Step-by-Step Procedure

To configure the overlay network for Leaf 3:

  1. Configure an IBGP group for the EVPN-VXLAN overlay network.

  2. Configure VXLAN encapsulation for the data packets exchanged between the EVPN neighbors.

  3. Specify a tunnel type used for passing multicast traffic between Juniper Networks switches in an EVPN-VXLAN environment.

  4. Set up a policy to handle Layer 2 EVPN traffic.

  5. Configure options for the default routing instance (virtual switch type).

Leaf 3: Customer Profile Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

To configure profiles for the two customer groups:

  1. Configure a Layer 2 Ethernet interface for the connection with the physical server. This interface is associated with VXLANs v0001, v0002, v0005, and v0006.

  2. Configure a route target for each VNI.

    Note

    In this configuration, the spine devices run Junos OS Release 15.1X53-D30, and the leaf devices run 14.1X53-D30. In these software releases, when you include the vrf-target configuration statement in the [edit protocols evpn vni-options vni] hierarchy level, you must also include the export option as shown in this step. Note that later Junos OS releases might not require this option. However, if you include the export option in a software release in which it is not required, the system still commits the configuration.

  3. Specify which VNIs are included in the EVPN-VXLAN domains.

  4. Configure policies that accept and import overlay routes.

  5. Set up communities for the customer groups and VXLANs.

  6. Configure VXLANs v0001, v0002, v0005, and v0006.

Leaf 4: Underlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Underlay Network for Leaf 4

Step-by-Step Procedure

To configure the underlay network for Leaf 4:

  1. Configure the Layer 3 interfaces.

  2. Specify an IP address for the loopback interface. This IP address serves as the source IP address in the outer header of any VXLAN-encapsulated packets.

  3. Set the routing options.

  4. Configure a BGP group that includes peers that handle underlay functions.

    Note

    In this configuration, the EBGP peers are in the same subnet. However, if your configuration includes EBGP peers in different subnets, you must include the set protocols bgp group underlay accept-remote-nexthop command so that the BGP routes appear in the routing table as direct routes. VXLAN requires direct next hops for equal-cost multipath (ECMP) load balancing.

  5. Configure a policy that spreads traffic across multiple paths between the Juniper Networks switches.

  6. Configure a policy that enables BGP to advertise direct interfaces such as loopback interface lo0.

Leaf 4: Overlay Network Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring the Overlay Network for Leaf 4

Step-by-Step Procedure

To configure the overlay network for Leaf 4:

  1. Configure an IBGP group for the EVPN-VXLAN overlay.

  2. Configure VXLAN encapsulation for the data packets exchanged between the EVPN neighbors.

  3. Specify a tunnel type used for passing multicast traffic between Juniper Networks switches in an EVPN-VXLAN environment.

  4. Set up a policy to handle Layer 2 EVPN traffic.

  5. Configure options for the default routing instance (virtual switch type).

Leaf 4: Customer Profile Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

To configure profiles for the two customer groups:

  1. Configure a Layer 2 Ethernet interface for the connection with the physical server. This interface is associated with VXLANs v0001, v0002, v0005, and v0006.

  2. Configure a route target for each VNI.

    Note

    In this configuration, the spine devices run Junos OS Release 15.1X53-D30, and the leaf devices run 14.1X53-D30. In these software releases, when you include the vrf-target configuration statement in the [edit protocols evpn vni-options vni] hierarchy level, you must also include the export option as shown in this step. Note that later Junos OS releases might not require this option. However, if you include the export option in a software release in which it is not required, the system still commits the configuration.

  3. Specify which VNIs are included in the EVPN-VXLAN domains.

  4. Configure policies that accept and import overlay routes.

  5. Set up communities for the customer groups and VXLANs.

  6. Configure VXLANs v0001, v0002, v0005, and v0006.

Verification

Confirm that the IRB interfaces are working properly:

Verifying the Configuration of the IRB Interfaces

Purpose

Verify the configuration of the IRB interfaces on Spine 1 and Spine 2.

Action

From operational mode, enter the show interfaces irb command.

user@switch> show interfaces irb

Meaning

The sample output from Spine 2 verifies the following:

  • IRB interfaces irb.1, irb.2, irb.5, and irb.6 are configured.

  • The physical interface upon which the IRB interfaces are configured is up and running.

  • Each IRB interface is properly mapped to its respective VXLAN.

  • The configuration of each IRB interface properly reflects the IP address and destination (virtual gateway address) assigned to it.

Verifying the Configuration of the Routing Instances

Purpose

Verify that the routing instances for customer groups 1 and 2 are properly configured on Spine 1 and Spine 2.

Action

From operational mode, enter the show route instance routing-instance-name extensive command for customer groups 1 and 2.

user@switch> show route instance cust0001 extensive
user@switch> show route instance cust0002 extensive

Meaning

In the sample output from Spine 2, the routing instances for customer groups 1 and 2 shows the loopback interface and IRB interfaces that are associated with each group. The output also shows the actual route distinguisher and import and export policy configurations.

Verifying that Dynamic MAC Addresses Are Installed

Purpose

Verify that for VXLANs v0001, v0002, v0003, and v0004, a dynamic MAC address is installed in the Ethernet switching tables on Leaf 1, Leaf 2, Leaf 3, and Leaf 4.

Action

From operational mode, enter the show ethernet-switching table command.

user@switch> show ethernet-switching table

Meaning

The sample output from Leaf 1 indicates that it has learned the MAC address 00:00:5e:00:01:01 for a virtual gateway, which is the next-hop of the ESI. The output also indicates that Leaf 1 learned the IRB MAC addresses for Spine 1 and Spine 2, which function as virtual tunnel endpoints (VTEPs).

Release History Table
Release
Description
Starting with Junos OS Release 15.1X53-D30, you can use integrated routing and bridging (IRB) interfaces to route data packets between Virtual Extensible LANs (VXLANs) that are implemented in an Ethernet VPN (EVPN)-VXLAN environment.