10.5. EVPN Command Reference

This command enables the context to configure the BGP-related parameters for a BGP Epipe or VPLS.

The no version of the command removes the BGP instance.

This command configures the route distinguisher (RD) component that is signaled in the MP-BGP NLRI for Layer 2 VPN and EVPN families. This value is used for the BGP Epipe NLRI and BGP VPLS NLRI when this command is configured.

Alternatively, for BGP-EVPN-enabled Epipe and VPLS services, the route-distinguisher value can be auto-derived from the evi evi value (config>service>epipe>bgp-evpn>evi or config>service>vpls>bgp-evpn>evi) if this command is not configured.

This command configures the route target (RT) component that is signaled in the related MP-BGP attribute that is used for the BGP Epipe, BGP VPLS, and EVPN when this command is configured in this Epipe or VPLS service.

If this command is not used, the RT is formed automatically using the Epipe or VPLS ID. The extended community can have the same two formats as the Epipe or VPLS ID, that is, a two-octet AS-specific extended community or an IPv4-specific extended community. The extended community can also have a four-octet AS-specific community format. For BGP-EVPN-enabled Epipe and VPLS services, the route target can also be auto-derived from the evi value (config>service>vpls>bgp-evpn>evi or config>service>epipe>bgp-evpn>evi) if this command is not configured.

This command specifies the name of the virtual switch instance (VSI) export policies to be used for BGP VPLS when this command is configured in this VPLS service. If multiple policy names are configured, the policies are evaluated in the order in which they are specified. The first policy that matches is applied.

The policy name list is handled by the SNMP agent as a single entity.

This command specifies the name of the virtual switch instance (VSI) import policies to be used for BGP VPLS when this command is configured in this VPLS service. If multiple policy names are configured, the policies are evaluated in the order in which they are specified. The first policy that matches is applied.

The policy name list is handled by the SNMP agent as a single entity.

This command enables the context to configure the BGP-EVPN parameters in the specified service.

This command enables the advertisement and withdrawal, as appropriate, of the IEEE MAC address associated with the MEP created on a SAP in an EVPN service.

The update occurs each time a MEP is added or deleted or an IEEE MAC address is changed for an MEP on a SAP within the service. The size of the update depends on the number of MEPs in the service affected by the modification.

Only enable this functionality for services that require a resident MAC address to properly forward unicast traffic and that do not perform Layer 2 MAC learning as part of the data plane.

Local MEP IEEE MAC addresses are not stored in the local FDB and therefore cannot be advertised through a control plane to a peer without this command.

The no version of the command disables the functionality and withdraws all previously advertised MEP IEEE MAC addresses.

This command specifies a 2-byte EVPN instance (EVI) that is unique in the system. It is used for the service-carving algorithm for multihoming and for auto-deriving route targets and route distinguishers.

If not specified, the evi value is 0 and there are no route distinguishers or route targets auto-derived from the value. If the evi value is specified and no other route distinguishers or route targets are configured in the service, the following rules apply:

If VSI import and VSI export policies are configured, the route target must be configured in the policies and the policy values take preference over the auto-derived route targets. The operational route target for a service is shown using the show>service>id>bgp command.

The no version of the command sets the evi value back to 0.

This command specifies that the IP address configured with the command is encoded in the originating-ip field of EVPN Inclusive Multicast Routes with tunnel type Ingress Replication (IR) (value 6).

The configured address does not need to be reachable in the base router or have an interface in the base router. The originating IP address is used solely for BGP route-key selection.

The no version of the command withdraws the affected Inclusive Multicast Routes and readvertises the routes with the default system IP address in the originating IP field.

This command enables the advertisement of the inclusive multicast Ethernet tag route with tunnel type ingress-replication in the PMSI tunnel attribute.

This command enables or disables the advertisement of IP prefixes in EVPN. When enabled, any active route in the r-VPLS VPRN route table will be advertised in EVPN using the VPLS BGP configuration. The interface host addresses are not advertised in EVPN unless the incl-host parameter is specified.

This command enables the context and specifies the attachment circuit name in which the local Ethernet tag value is configured.

This command configures the Ethernet tag value. When configured in the local-ac-name context, the system uses the value in the advertised AD per-EVI route sent for the attachment circuit. When configured in the remote-ac-name context, the system compares that value with the eth-tag tag-value of the imported AD per-EVI routes for the service. If there is a match, the system creates an EVPN-MPLS destination for the Epipe.

This command enables the advertisement in BGP of the learned MAC addresses on SAPs and SDP bindings. When the mac-advertisement command is disabled, the local MAC addresses are withdrawn in BGP.

This command enables the context to configure the BGP-EVPN MAC duplication parameters.

This command modifies the default behavior of the mac-duplication command. The mac-duplication feature is always enabled by default and monitors the number of moves of a MAC address for a period of time (window).

This command specifies the timer after which the MAC in hold-down state is automatically flushed and the MAC duplication process starts again. This value is expected to be equal to or greater than two times that of the window minutes.

The no form of the command implies that when MAC duplication is detected, MAC updates for that MAC will be held down until the user intervenes or a network event that flushes the MAC occurs.

This command enables the context to configure the BGP-EVPN MPLS parameters.

This command enables the context to configure automatic binding of a BGP-EVPN MPLS service to tunnels to MP-BGP peers.

This command enables ECMP for Layer 2 unicast traffic on Epipe or VPLS services for EVPN-MPLS destinations. The command allows the resolution of an EVPN-MPLS next hop to a group of ECMP tunnels of type RSVP-TE or SR-TE and determines the number of Traffic Engineering (TE) tunnels that the EVPN-MPLS next hop can be resolved to. For shortest path tunnels, such as LDP, SR-ISIS, and SR-OSPF, the number of tunnels in the ECMP group is determined by the config>router>ecmp command.

This command configures the resolution mode in the automatic binding of a BGP-EVPN MPLS service to tunnels to MP-BGP peers.

The user must configure the resolution command to enable auto-bind resolution to tunnels in the tunnel table manager (TTM). The following options are available:

The user must set the resolution command to filter in order to activate the list of tunnel types configured under the resolution-filter command.

This command enables the context that allows the configuration of the subset of tunnel types that can be used in the resolution of BGP-EVPN routes within the automatic binding of BGP-EVPN MPLS service to tunnels to MP-BGP peers.

The user must set the resolution command to filter in order to activate the list of tunnel types configured under the resolution-filter command.

The following tunnel types are supported in a BGP-EVPN MPLS context in order of preference: RSVP, SR-TE, LDP, SR-ISIS, SR-OSPF, and BGP.

This command selects the BGP tunnel type.

The bgp command instructs BGP-EVPN to search for a BGP LSP to the address of the BGP next hop. If the user does not enable the BGP tunnel type, inter-area or inter-as prefixes will not be resolved.

This command selects the LDP tunnel type.

The ldp command instructs BGP to search for an LDP LSP with a FEC prefix corresponding to the address of the BGP next hop.

This command selects the RSVP-TE tunnel type.

The rsvp command instructs BGP to search for the best metric RSVP-TE LSP to the address of the BGP next hop. This address can correspond to the system interface or to another loopback address used by the BGP instance on the remote node. The LSP metric is provided by MPLS in the tunnel table. If there are multiple RSVP-TE LSPs with the same lowest metric, BGP selects the LSP with the lowest tunnel ID.

This command selects the segment routing (SR) tunnel type programed by an IS-IS instance in the TTM.

When the sr-isis or sr-ospf command is enabled, a segment routing (SR) tunnel to the BGP next hop is selected in the TTM from the lowest numbered IS-IS or OSPF instance.

This command selects the segment routing (SR) tunnel type programed by an OSPF instance in the TTM.

When the sr-isis or sr-ospf command is enabled, a segment routing (SR) tunnel to the BGP next hop is selected in the TTM from the lowest numbered IS-IS or OSPF instance.

This command selects the segment routing traffic engineered LSP programmed in the TTM.

The sr-te command instructs the code to search for the best metric SR-TE LSP to the address of the BGP next hop. The LSP metric is provided by MPLS in the tunnel table. If there are multiple SR-TE LSPs with the same lowest metric, BGP selects the LSP with the lowest tunnel ID.

This command enables weighted ECMP for packets using tunnels that an Epipe or VPLS automatically binds to. When weighted ECMP is enabled, packets are sprayed across LSPs in the ECMP set according to the outcome of the hash algorithm and the configured load-balancing-weight of each LSP. See the 7250 IXR MPLS Guide, “MPLS Commands” for more information on the load-balancing-weight command.

The no form of this command disables weighted ECMP for next-hop tunnel selection.

This command enables the transmission and reception of the control word. As defined in RFC 7432, the use of the control word helps avoid frame disordering.

The control-word command is enabled or disabled for all EVPN-MPLS destinations at the same time.

This command controls the number of paths allowed to reach a specified MAC address when that MAC in the FDB is associated with a remote all-active multihomed Ethernet segment.

The configuration of two or more ECMP paths to a specified MAC enables the aliasing function described in RFC 7432.

This command inserts the entropy label (EL) and entropy label indicator (ELI) in packets for which at least one LSP in the stack for the far end of the tunnel used by the service has advertised entropy-label capability. If the tunnel is the rsvp type, entropy-label can also be controlled under the config>router>mpls or config>router>mpls>lsp context.

This command allows the system to preserve the VLAN ID and 802.1p bits of the service-delimiting qtag in a new tag added in the customer frame before sending it to the EVPN-MPLS destinations.

This command may be used in conjunction with the sap ingress vlan-translation command. If it is used, the configured translated VLAN ID will be the VLAN ID sent to the EVPN-MPLS destinations as opposed to the service-delimiting tag VLAN ID. If the ingress SAP or SDP binding is null-encapsulated, the output VLAN ID and P-bits will be 0.

This command allows the user to configure the system so that a separate label is sent for BMU (broadcast, multicast, and unknown unicast) traffic in a specified service. By default, the same label is used for unicast and flooded BMU packets when forwarding traffic to remote PEs.

When saving label space, this might cause transient packet duplication for all-active multihoming. By enabling ingress-replication-bum-label, the system will advertise two labels per EVPN VPLS instance, one for unicast and one for BMU traffic. The ingress PE will use the BMU label for flooded traffic to the advertising egress PE so that the egress PE can determine if the unicast traffic has been flooded by the ingress PE. Depending on the scale required in the network, the user may choose between saving label space or avoiding transient packet duplication sent to an all-active multihomed CE for certain MAC addresses.

This command controls the administrative state of EVPN-MPLS in the service.

This command allows the user to configure an explicit split horizon group for all BGP-EVPN MPLS destinations that can be shared by other SAPs and spoke SDPs. The use of explicit split horizon groups for EVPN-MPLS and spoke SDPs allows the integration of VPLS and EVPN-MPLS networks.

If the split-horizon-group command under bgp-evpn>mpls is not used, the default split horizon group that contains all the EVPN destinations is still used, but it is not possible to refer to it on SAPs or spoke SDPs. Split horizon groups can be configured within the service context. The same group name can be associated with SAPs, spoke SDPs, and EVPN-MPLS destinations. The configuration of bgp-evpn>mpls>split-horizon-group will only be allowed if bgp-evpn>mpls is shutdown; no changes are allowed when bgp-evpn>mpls is no shutdown.

When the SAPs or spoke SDPs are configured within the same split horizon group as the EVPN-MPLS endpoints, MAC addresses are still learned on them but they are not advertised in BGP-EVPN.

This command enables the context and specifies the attachment circuit name in which the remote Ethernet tag value is configured.

This command enables the context that allows the assignment of a set of conditional static MAC addresses to a SAP, spoke SDP, or black-hole. In the FDB, the static MAC address is then associated with the active SAP or spoke SDP.

A set of conditional static MAC addresses can be created within a VPLS supporting BGP-EVPN. Unless they are configured as black-hole, conditional static MAC addresses are dependent on the SAP or SDP state.

Static MAC addresses configured in a BGP-EVPN service are advertised as protected (EVPN signals the MAC address as protected).

This command assigns a conditional static MAC address entry to an EVPN VPLS SAP, spoke SDP, or a black hole on the 7705 SAR.