Configuring EVPN VLAN Bundle Services

Each routing instance that you configure on a PE router must have a unique route distinguisher associated with it. VPN routing instances need a route distinguisher to help BGP to distinguish between potentially identical network layer reachability information (NLRI) messages received from different VPNs. If you configure different VPN routing instances with the same route distinguisher, the commit fails.

For a list of the hierarchy levels at which you can include the route-distinguisher statement, see route-distinguisher.

The route distinguisher is a 6-byte value that you can specify in either of the following formats:

• as-number:number, where as-number is an autonomous system (AS) number (a 2-byte value) and number is any 4-byte value. The AS number can be in the range 1 through 65,535. We recommend that you use an Internet Assigned Numbers Authority (IANA)-assigned, nonprivate AS number, preferably the ISP’s own or the customer’s own AS number.

  Note:

  The automatic derivation of the BGP route target (auto-RT) for advertised prefixes is supported on 2-byte AS numbers only.

• ip-address:number, where ip-address is an IP address (a 4-byte value) and number is any 2-byte value. The IP address can be any globally unique unicast address. We recommend that you use the address that you configure in the router-id statement, which is a nonprivate address in your assigned prefix range.

See Configuring Policies for the VRF Table on PE Routers in VPNs.

Note:

Adding a trunk port with dual tags to an EVPN and MPLS routing instance to an EVPN and VXLAN routing instance causes the CLI commit check configuration to fail and generate an error. To avoid configuration check errors, use sub-interface style interface configuration with dual tags for the routing instances.

• Configure each interface using the interface statement at the [edit routing-instances routing-instance-name protocols evpn] hierarchy level.

• Configure interface encapsulation for the CE-facing interfaces at the [edit interfaces interface-name encapsulation] hierarchy level. Supported encapsulations are ethernet-bridge, vlan-bridge, and extended-vlan-bridge.

  Note:

  If you are configuring the port-based VLAN bundle service, you will need to also configure the interface encapsulation ethernet-bridge unit to 0.

• (Optional) Include the ignore-encapsulation-mismatch statement at the [edit routing-instances routing-instance-name protocols evpn interface interface-name] hierarchy level to allow the EVPN to establish a connection to the CE device even if the CE device interface encapsulation and the EVPN interface encapsulations do not match.

• Specify a static MAC address for a logical interface in a bridge domain using the static-mac statement at the [edit routing-instances routing-instance-name protocols evpn interface interface-name] hierarchy level.

You can configure the same limit for all interfaces configured for a routing instance by including the interface-mac-limit statement at the [edit routing-instances routing-instance-name protocols evpn] hierarchy level. You can also configure a limit for a specific interface by including this statement at the [edit routing-instances routing-instance-name protocols evpn interface interface-name] hierarchy level.

By default, packets with new source MAC addresses are forwarded after the MAC address limit is reached. You can alter this behavior by including the packet-action drop statement at either the [edit routing-instances routing-instance-name protocols evpn interface-mac-limit] or the [edit routing-instances routing-instance-name protocols evpn interface interface-name] hierarchy level. If you configure this statement, packets from new source MAC addresses are dropped after the configured MAC address limit is reached.

If you configure this statement, one MPLS label is allocated for the specified EVPN routing instance.