Tag :: MPLS

MPLS LDP traceroute utility has now been extended to support multipath traceroute. This allows network

MPLS speculative parsing is the parsing of the headers following the MPLS header. Because there is no ethertype following the MPLS header, it can be difficult to discern the following header type(s). Some headers can be misparsed, so certain configurations are provided to allow customization of the parsing behaviour.

In the 7280R3/7500R3/7800R3 platform, EXP rewrite for IP-MPLS routed flows is derived from the DSCP of the packet. Using Qos Policy map , DSCP can be set as needed. But in this process, the egress IP TOS was also changed, which may cause issues later at customer edge. 

This feature enables users to configure MPLS EXP rewrite behavior on the egress interface based upon the global TC-to-EXP mapping. Starting from software version 4.33.2F, the CLI configuration to enable or disable EXP rewrite on the egress interface introduces a clear distinction in the behavior of MPLS EXP processing during POP and SWAP operations.

E-Tree is an L2 EVPN service (defined in RFC8317) in which each attachment circuit (AC) is assigned the role of Root or Leaf. In this implementation, ACs are configured at the VLAN level, and the forwarding rules are enforced using a combination of local configuration of leaf VLANs (for local hosts), and asymmetric route targets (for remote hosts).

This feature adds control plane support for inter subnet forwarding between EVPN and IPVPN networks. It also

In the traditional data center design, inter-subnet forwarding is provided by a centralized router, where traffic traverses across the network to a centralized routing node and back again to its final destination. In a large multi-tenant data center environment this operational model can lead to inefficient use of bandwidth and sub-optimal forwarding.

This feature adds control plane support for inter subnet forwarding between EVPN networks. This support is achieved

Flexible cross-connect service is an extension of EVPN MPLS Virtual Private Wire Service (VPWS) (RFC 8214). It allows for multiplexing multiple attachment circuits across different Ethernet Segments and physical interfaces into a single EVPN VPWS service tunnel while still providing single-active and all-active multi-homing.

For MPLS forwarded traffic the tunnel destination needs to know the address-family of the payload IP/IPv6 packet to correctly parse the header. On some platforms this address-family is deduced from the address family of the Bottom of stack( BOS ) MPLS label seen by the router or by relying on the Ether Type in the Ethernet header.

MPLSoGRE Filtered Mirroring is a specialized version of Mirroring to GRE Tunnel and Filtered Mirroring in which

Prior to EOS 4.27.0F, MPLS tunnel egress counters could only be enabled for all MPLS tunnels present in the system

This feature allows transport of multicast frames to an endpoint across an IP network by tunneling them through MPLSoGRE or MPLSoGUE. The tunneling of multicast frames is achieved with a traffic policy applied on the ingress interface which will match on all packets destined to a multicast IP address and redirect that traffic to a MoG nexthop group. The traffic policy will also specify “forced routing” in order to set the fwd_layer_index to 1 so that the L2 header is removed before encapsulation.

This feature allows encapsulating (and decapsulating) L2 traffic from a given interface or subinterface over a GRE tunnel. An MPLS label is added to identify the ingress interface (similar to MPLS pseudowires) and the GRE tunnel or nexthop-group is used to transport the packets to a remote endpoint.

The Label Distribution Protocol (LDP) is a protocol in the Multiprotocol Label Switching (MPLS) context that allows label switch routers (LSRs) to exchange label mapping information. It is a distributed protocol without a central controller. Instead, each LSR generates local label mappings for Forward Equivalence Classes (FECs) and propagates this information to adjacent LSRs which it maintains LDP sessions with.

This feature allows customers to run Label Distribution Protocol (LDP) on a subset of the interfaces that run Multi

The LDP pseudowire feature provides support for emulating Ethernet connections over a Multiprotocol Label Switching (MPLS) network using the extension of the MPLS Label Distribution Protocol (LDP)

At a transit router when multiple LSP are available for a given destination from different protocols EOS does stitching based on hard coded preferences. LFIB stitching preferences give a provision to stitch together different LSPs based on configurable preferences. For each protocol(destination) preference can be configured for a given source protocol.

MPLS ping/traceroute utility is extended to support liveness checking of Nexthop Group tunnel endpoint (MPLS

Arista EOS currently supports a maximum 6 labels push on R2 and R3 series platforms. This feature increases maximum

Normally, Multiprotocol Label Switching (MPLS) determines the packet forwarding destination based on the top most

This feature allows users to preserve IP TTL and MPLS EXP (also known as TC) value on MPLS routers, as well as add a user-specified TTL/EXP value when pushing new MPLS labels in pipe mode. With the added pipe mode support, packets can traverse the network such that only the LSP ingress and egress nodes are visible to the end users and the MPLS core network can be hidden from the end user.

MPLS-over-GRE encapsulation support in EOS 4.17.0 enables tunneling IPv4 packets over MPLS over GRE tunnels. This feature leverages next-hop group support in EOS. With this feature, IPv4 routes may be resolved via MPLS-over-GRE next-hop group to be able to push one MPLS label and then GRE encapsulate the resulting labelled IPv4 packet before sending out of the egress interface.

EOS version 4.24.1F introduces support for specifying multiple vias to form ECMP in MPLS static tunnels. A new

IP traceroute and path MTU (PMTU) discovery both require that routers send ICMP reply messages to the host that invokes each network function. When the route to the destination host traverses an MPLS label-switched path (LSP), the label switching routers (LSRs) will also need to send ICMP reply messages to the originating host.

Generic UDP Encapsulation (GUE) is a general method for encapsulating packets of arbitrary IP protocols within a UDP tunnel. GUE provides an extensible header format with optional data. In this release, the ability to encapsulate MPLS over GUE packets of variant 1 header format has been added. 

This feature extends the multi-domain EVPN VXLAN feature introduced to support interconnect with EVPN MPLS networks. The following diagram shows a multi-domain deployment with EVPN VXLAN in the data center and EVPN MPLS in the WAN. Note that this is the only supported deployment model, and that an EVPN MPLS network cannot peer with an EVPN MPLS network.

This feature adds all-active (A-A) multihoming support on the multi-domain EVPN VXLAN-MPLS gateway. It allows L2 and L3 ECMP to form between the multihoming gateways on the TOR devices inside the site and on the gateways in the remote sites. Therefore, traffic can be load-balanced to the multi-homing gateway and redundancy and fast convergence can be achieved.

This feature enables Qos policy-maps to match on IPv4/IPv6 fields for L3VPN & 6PE services on the LER device core facing interface, assuming all labels are popped and packets are sent to the customer as IP.

This is an extension to BGP MPLS VPNs that allows us to use iBGP as the PE CE protocol. This feature also provides a way to

RSVP-TE P2MP LER adds ingress and egress support for Point-to-Multipoint (P2MP) LSPs to be used in Multicast Virtual Private Network (MVPN) as an extension to the LSR support which adds transit support.

RSVP-TE P2MP LSR adds transit support for Point-to-Multipoint (P2MP) LSPs. Specifically the feature adds protocol support for the transit role as described in RFC 4875.

The sFlow EVPN MPLS extension adds support for providing information related to the bridging domain in sFlow packet samples, for traffic forwarded through L2 EVPN MPLS.

This feature adds RSVP information for three tables from MPLS TE STD MIB:. mplsTunnelTable.

When MPLS (Multiprotocol Label Switching) LFIB (Label Forwarding Information Base) lookup fails, typical forwarding behavior is to drop such packets. This feature allows fallback IP lookup when MPLS lookup fails and forwards traffic to an IP path by looking up the packet’s destination IP address in the route table if the network topologies have labeled paths programmed & IP based routes are also available for the same destination. This feature is also supported with optimized IPv4 8-to-1 route scale compression.

Topology Independent Fast Reroute, or TI-LFA, uses IS-IS SR to build loop-free alternate paths along the post-convergence path. These loop-free alternates provide fast convergence.

The MPLS LFIB counters feature was enhanced to add support for counting labels that correspond to VRF termination labels. The full details of the MPLS LFIB counters feature can be found in the original

This feature allows LFIB (Label Forwarding Information Base) & associated counters export through OpenConfig mpls AFT (Abstract Forwarding Tree) YANG model.

This feature provides total ingress MPLS packet and byte counters received per interface. DCS