Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring EVPN with VLAN-Aware Bundle Service

    VLAN-aware bundle services supports the mapping of one or more routing instances of type Virtual Switch to many VLAN IDs (VIDs) and multiple bridge tables, with each bridge table corresponding to a different VLAN. To enable VLAN-aware bundle service, configure a Virtual Switch routing instance. For service provider-related applications, where the VLAN ID is local to the Layer 2 logic interface, enable the flexible-vlan-tagging statement in your configuration. For enterprise-related applications (discussed in this topic), where the VLAN ID has global significance, enable the family ethernet-switching statement in your configuration.

    This configuration task explains how to configure Layer 2 switching and Layer 3 routing with two Virtual Switch routing instances and four VLANs on a provider edge device.

    1. Configure the xe-0/0/8 interface to be a trunk interface.

      For example:

      [edit]
      user@switch# set interfaces xe-0/0/8 unit 0 family ethernet-switching interface-mode trunk
    2. Configure the xe-0/0/8 interface to be included in VLANs v100 and v200.

      For example:

      [edit]
      user@switch# set interfaces xe-0/0/8 unit 0 family ethernet-switching vlan members v100
      user@switch# set interfaces xe-0/0/8 unit 0 family ethernet-switching vlan members v200
    3. Configure the xe-0/0/9 interface to be a trunk interface.

      For example:

      [edit]
      user@switch# set interfaces xe-0/0/9 unit 0 family ethernet-switching interface-mode trunk
    4. Configure the xe-0/0/9 interface to be included in VLANs v300 and v400.

      For example:

      [edit]
      user@switch# set interfaces xe-0/0/8 unit 0 family ethernet-switching vlan members v300
      user@switch# set interfaces xe-0/0/8 unit 0 family ethernet-switching vlan members v400
    5. Configure four IRB interfaces, each with unique IP addresses but with the same MAC address.

      For example:

      [edit]
      user@switch# set interfaces irb unit 100 family inet address 192.168.0.1/24
      user@switch# set interfaces irb unit 100 mac 00:00:ba:ba:00:01
      user@switch# set interfaces irb unit 200 family inet address 192.168.1.1/24
      user@switch# set interfaces irb unit 200 mac 00:00:ba:ba:00:01
      user@switch# set interfaces irb unit 300 family inet address 192.168.3.1/24
      user@switch# set interfaces irb unit 300 mac 00:00:ba:ba:00:01
      user@switch# set interfaces irb unit 400 family inet address 192.168.4.1/24
      user@switch# set interfaces irb unit 400 mac 00:00:ba:ba:00:01
    6. Configure the first of two routing instance of type virtual-switch.

      For example:

      [edit]
      user@switch# set routing-instances vs1 instance-type virtual-switch
    7. Configure the loopback address as the virtual tunnel endpoint source interface for the vs1 virtual switch routing instance.

      For example:

      [edit]
      user@switch# set routing-instances vs1 vtep-source-interface lo0.0
    8. Configure the access interface on the provider edge device (PE) for handling EVPN traffic.

      For example:

      [edit]
      user@switch# set routing-instances vs1 interface xe-0/0/8.0
    9. Configure a VLAN identifier for VLAN v100.

      For example:

      [edit]
      user@switch# set routing-instances vs1 vlans v100 vlan-id 100
    10. Configure a Layer 3 integrated and routing (IRB) interface for VLAN v100.

      For example:

      [edit]
      user@switch# set routing-instances vs1 vlans v100 l3-interface irb.100
    11. Configure a unique VXLAN Network Identifier for VLAN v100.

      For example:

      [edit]
      user@switch# set routing-instances vs1 vlans v100 vxlan vni 111
    12. Configure a VLAN identifier for VLAN v200.

      For example:

      [edit]
      user@switch# set routing-instances vs1 vlans v200 vlan-id 200
    13. Configure a Layer 3 integrated and routing (IRB) interface for VLAN v200.

      For example:

      [edit]
      user@switch# set routing-instances vs1 vlans v200 l3-interface irb.200
    14. Configure a unique VXLAN Network Identifier for VLAN v200.

      For example:

      [edit]
      user@switch# set routing-instances vs1 vlans v200 vxlan vni 222
    15. Configure a unique route distinguisher for the vs1 routing instance to identify from which EVPN the route belongs.

      For example:

      [edit]
      user@switch# routing-instances vs1 route-distinguisher 1.2.3.11:1
    16. Configure the VPN routing and forwarding (VRF) target community for the vs1 routing instance.

      For example:

      [edit]
      user@switch# set routing-instances vs1 vrf-target target:65001:1
    17. Configure the encapsulation type for the vs1 routing instance.

      For example:

      [edit]
      user@switch# set routing-instances vs1 protocols evpn encapsulation vxlan
    18. Specify that all VXLAN Network Identifiers (VNIs) for the vs1 routing instance are advertised.

      For example:

      [edit]
      user@switch# set routing-instances vs1 protocols evpn extended-vni-list all
    19. Disable advertisement of IRB interface MAC addresses in the EVPN control plane.

      Because you already specified in step 5 that each IRB interface is configured with the same MAC address, you do not need to advertise MAC addresses.

      For example:

      [edit]
      user@switch# set routing-instances vs1 protocols evpn default-gateway do-not-advertise
    20. Configure the second of two routing instance of type virtual-switch.

      For example:

      [edit]
      user@switch# set routing-instances vs2 instance-type virtual-switch
    21. Configure the loopback address as the virtual tunnel endpoint source interface for the vs2 virtual switch routing instance.

      For example:

      [edit]
      user@switch# set routing-instances vs2 vtep-source-interface lo0.0
    22. Configure the access interface on the provider edge device (PE) for handling EVPN traffic.

      For example:

      [edit]
      user@switch# set routing-instances vs2 interface xe-0/0/9.0
    23. Configure a VLAN identifier for VLAN v300.

      For example:

      [edit]
      user@switch# set routing-instances vs2 vlans v300 vlan-id 300
    24. Configure a Layer 3 integrated and routing (IRB) interface for VLAN v300.

      For example:

      [edit]
      user@switch# set routing-instances vs2 vlans v300 l3-interface irb.300
    25. Configure a unique VXLAN Network Identifier for VLAN v300.

      For example:

      [edit]
      user@switch# set routing-instances vs2 vlans v300 vxlan vni 333
    26. Configure a VLAN identifier for VLAN v400.

      For example:

      [edit]
      user@switch# set routing-instances vs2 vlans v400 vlan-id 400
    27. Configure a Layer 3 integrated and routing (IRB) interface for VLAN v400.

      For example:

      [edit]
      user@switch# set routing-instances vs2 vlans v400 l3-interface irb.400
    28. Configure a unique VXLAN Network Identifier for VLAN v400.

      For example:

      [edit]
      user@switch# set routing-instances vs2 vlans v400 vxlan vni 444
    29. Configure a unique route distinguisher for the vs2 routing instance to identify from which EVPN the route belongs.

      For example:

      [edit]
      user@switch# routing-instances vs2 route-distinguisher 1.2.3.11:2
    30. Configure the VPN routing and forwarding (VRF) target community for the vs2 routing instance.

      For example:

      [edit]
      user@switch# set routing-instances vs2 vrf-target target:65001:2
    31. Configure the encapsulation type for the vs2 routing instance.

      For example:

      [edit]
      user@switch# set routing-instances vs2 protocols evpn encapsulation vxlan
    32. Specify which VXLAN Network Identifier (VNI) lists are part of the vs2 routing instance.

      For example:

      [edit]
      user@switch# set routing-instances vs2 protocols evpn extended-vni-list 333
      user@switch# set routing-instances vs2 protocols evpn extended-vni-list 444
    33. Disable advertisement of IRB interface MAC addresses in the EVPN control plane.

      Because you already specified in step 5 that each IRB interface is configured with the same MAC address, you do not need to advertise MAC addresses.

      For example:

      [edit]
      user@switch# set routing-instances vs2 protocols evpn default-gateway do-not-advertise

    Modified: 2018-03-06