Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

EVPN

  • Support for DHCP Option 82 over EVPN (ACX Series)—Starting in Junos OS Release 21.2R1, Option 82 flags are inserted in the DHCP packets to enhance security when the packet is sent to the server. The provider edge (PE) router that is part of the EVPN instance acts as the relay agent, and adds these flags to the DHCP packets.

    DHCPv4 packet relay and DHCPv6 packet relay use this process. With the introduction of EVPN IRB, the relay agent uses the IRB interface with EVPN for forwarding the requests, and for replies to and from the client or the server instead of using the default routing option. If one PE router fails, an appropriate DHCPv6-PD state is made available for the remaining PE routers participating in the DHCP-PD process for the VLAN. This is done using automatic synchronization of DHCPv6-PD states between multiple PE routers that are connected to the same Ethernet segment identifier (ESI) through EVPN BGP messages.

    [See Understanding DHCP Option 82

  • Support for DHCPv6-PD on EVPN IRB synchronization among multiple PE routers (ACX Series)—You can use DHCPv6 prefix delegation (DHCPv6-PD) to automate the delegation of IPv6 prefixes to a requesting router on EVPN IRB. DHCPv6 prefix delegation is configured on EVPN IRB, and provides IPv6 prefixes to the requesting clients instead of a unique address. The DHCPv6-PD server acts as a provider edge (PE) router that provides the delegates through the relay (PE router) operating in the EVPN instance.

    If one PE router fails, an appropriate DHCPv6-PD state is made available for the remaining PE routers participating in the DHCP-PD process for the VLAN. This is done using automatic synchronization of DHCPv6-PD states between multiple PE routers that are connected to the same Ethernet segment identifier (ESI) through EVPN BGP messages.

  • Port-based VLAN bundle services for EVPN (EX9200)—Starting in Junos OS Release 21.2R1, Junos OS supports port-based VLAN bundle services for EVPN on the EX9200 switch. The port-based VLAN bundle service maps the VLANs on a port to the same bundle service.

    [See VLAN Bundle Service for EVPN.]

  • EVPN Type 2 and Type 5 route coexistence (EX4650, QFX5110, QFX5120, and QFX10002)—Starting in Junos OS Release 21.2R1, we support the coexistence of EVPN Type 2 and Type 5 routes in EVPN-VXLAN edge-routed bridging overlay fabrics. This feature enables more efficient traffic flow and better usage of Packet Forwarding Engine resources. The switch applies a preference algorithm when you enable Type 5 routes. For any destinations for which the switch has no Type 5 route, the switch uses Type 2 routes by default. Otherwise, the switch gives preference to:

    • Type 2 routes for local ESI interfaces (locally learned routes)
    • Type 5 routes for all other destinations within the data center or across data centers

    You can refine these preferences by configuring routing policies in the EVPN routing instance to control the Type 5 routes that the switch imports and exports.

    [See EVPN Type 2 and Type 5 Route Coexistence with EVPN-VXLAN.]

  • Optimized inter-subnet multicast support with symmetric bridge domain configuration in an EVPN-VXLAN fabric (QFX5110, QFX5120, QFX10002-36Q, and QFX10002-72Q)—Starting in Junos OS Release 21.2R1, you can configure optimized inter-subnet multicast (OISM) on leaf devices and border leaf devices in an EVPN-VXLAN edge-routed bridging overlay fabric. This feature helps optimize the routing of multicast traffic across VLANs in an EVPN tenant domain. This feature uses a supplemental bridge domain (SBD) and a multicast VLAN (MVLAN) to route multicast traffic from or to devices outside of the fabric. This feature also works with existing IGMP snooping and selective multicast (SMET) forwarding optimizations to minimize replication in the EVPN core when bridging within tenant VLANs.

    With this implementation, you must enable OISM and IGMP snooping on all the leaf and border leaf devices in the EVPN-VXLAN fabric. You also must configure the SBD and all tenant VLANs symmetrically on all leaf and border leaf devices in the fabric.

    You can use OISM with:

    • EVPN on the default-switch instance with VLAN-aware bundle service model (Layer 2)
    • Routing instances of type vrf (Layer 3)
    • EVPN single-homing or multihoming (all-active mode)
    • IGMPv2
    • Multicast sources and receivers within the EVPN data center
    • Multicast sources and receivers outside the EVPN data center that are reachable through the border leaf devices

    [See Optimized Inter-Subnet Multicast in EVPN Networks.]

  • Overlapping VLAN support for edge-routed bridging in an EVPN-VXLAN fabric (QFX5110 and QFX5120)—Starting in Junos OS Release 21.2R1, you can map the host VLAN to the VLAN that is provisioned on the leaf device by using VLAN translation. The host VLAN is translated to the VLAN that is already configured on the leaf device before the packet is processed. Conversely, the packet egresses from the access port with the translated VLAN.

    [See vlan-rewrite.]
  • Enhancement in the number of supported VLANs and ports (EX4400-24P, EX4400-24T, EX4400-48F, EX4400-48P, and EX4400-48T switches)—Starting with Junos OS Release 21.2R1, we have increased the combined total number of VLANs and ports that can be supported on the EX4400 switches. The number of supported VLANs remains at 4093, but Junos OS no longer limits the total number of ports and VLANS that can be configured on EVPN-VXLAN. This enhancement applies only when you use the enterprise style of configuration when configuring the interfaces.

    [See Understanding EVPN with VXLAN Data Plane Encapsulation.]