Configuring EVPN Routing Instances on EX9200 Switches

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 this statement, see the statement summary for this statement.

The route distinguisher is a 6-byte value that you can specify in one 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 Internet service provider’s (ISP’s) own or the customer’s own AS number.

• 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.

• Configure interface encapsulation for the CE facing interfaces at the [edit interfaces interface-name encapsulation] hierarchy level. . Supported encapsulations for EX9200 switches are: (extended-vlan-bridge | flexible-ethernet-services | vlan-bridge).

• Configure vlan-bridge encapsulation on the logical interface at the [edit interfaces interface-name flexible-vlan-tagging encapsulation flexible-ethernet-services unit 0 encapsulation] hierarchy level.

• (Optional) 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 by including the ignore-encapsulation-mismatch 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 this 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 once the configured MAC address limit is reached.

You can optionally configure the packet-action drop option to specify that packets for new source MAC addresses be dropped once the MAC address limit is reached. If you do not configure this option, packets for new source MAC addresses are forwarded.