Systems and methods, in a Label Edge Router (LER) which includes one or more ports and a switching fabric therebetween, include, responsive to a request for a Label Switched Path (LSP) tunnel with a specified DiffServ Traffic Engineering (DSTE) Class Type, signaling a PATH message via a port for the LSP tunnel in a Multiprotocol Label Switching (MPLS) network; incorporating a FAST_REROUTE object in the PATH message which indicates Facility Bypass is desired; and incorporating the DSTE Class Type in the FAST_REROUTE object of the PATH message for a Point of Local Repair (PLR) node in the MPLS network to ensure a Facility Bypass tunnel used for the LSP tunnel supports the specified DSTE Class Type.

A router is configured for deployment in a network. The router includes a memory configured to store a first identifier that uniquely identifies the router in the network. The router also includes a processor configured to push the first identifier onto a first labeled data packet prior to transmission of the first labeled data packet. In response to detecting the first identifier in a second labeled data packet received from the network, the processor is configured to drop the second labeled data packet.

Various example embodiments for supporting multicast communications in a communication system are presented. Various embodiments for supporting multicast communications may be configured to support multicast communications of multiple virtual private networks over a single multicast distribution tree. Various embodiments for supporting multicast communications of multiple virtual private networks over a single multicast distribution tree may support communication of a packet of a virtual private network within a network, wherein the packet includes a set of tuples associated with a set of egress devices to which the packet is to be delivered via a multicast distribution tree supported within the network, wherein, for each of the egress devices, the respective tuple associated with the respective egress device includes a respective device identifier of the egress device that uniquely identifies the respective egress device within the network and a respective label assigned by the respective egress device for the virtual private network.

A logical router includes disaggregated network elements that function as a single router and that are not coupled to a common backplane. The logical router includes spine elements and leaf elements implementing a network fabric with front panel ports being defined by leaf elements. Control plane elements program the spine units and leaf to function a logical router. The control plane may define operating system interfaces mapped to front panel ports of the leaf elements and referenced by tags associated with packets traversing the logical router. Redundancy and checkpoints may be implemented for a route database implemented by the control plane elements. The logical router may include a standalone fabric and may implement label tables that are used to label packets according to egress port and path through the fabric.

A system and method for managing congestion in a multi-hop wireless network, employing congestion notification messages. The technology has three main components: a mechanism at the Medium Access (MAC) layer for determining when a given source or transit node is deemed congested; a mechanism at the Network Layer (NL) determining how to propagate this information to applications, including suitably combining overload indications received from neighbors; and a mechanism at the Transport Layer (TL) of each source of traffic for determining when a source is generating excessive traffic, and combining it with Medium Access Control (MAC)-based overload indication from downstream nodes, thus providing a multi-layer approach to traffic throttling.

A network element configured to implement an Ethernet Virtual Private Network (EVPN) Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) local switching service includes a plurality of ports; and a switching fabric configured to switch traffic between the plurality of ports; wherein a set of ports is configured in a distributed Link Aggregation Group (LAG) with two nodes, and an inter-chassis link configured with a second network element, and wherein, responsive to a failure of the inter-chassis link, a distribution state of members in the distributed LAG is coordinated.

Ping or traceroute functionality is supported in a path spanning multiple autonomous systems (ASes) having segment routing (SR) enabled, the path including an ingress node in a first autonomous system (AS) and an egress node in an AS other than the first AS, using a reverse path label pair including (1) a node segment identifier (SID) corresponding to an AS Border Router (ASBR) of the second AS (second ASBR), and (2) an egress peer engineering (EPE) SID corresponding to a segment between the second ASBR to an ASBR of the first AS (first ASBR). Responsive to receiving a ping or traceroute request by a router in the second AS, the router generates a ping or traceroute reply including the reverse path label pair. The ping or traceroute reply is forwarded to the second ASBR using the node SID of the reverse path label pair. The ping or traceroute reply is then forwarded from the second ASBR to the first ASBR using the EPE SID of the reverse path label pair. Finally, the ping or traceroute reply can be forwarded (e.g., using standard IP forwarding) from the first ASBR to the headend router.

Systems and methods for incorporating a new channel-type value in the header of a Generic Associated Channel (G-ACh) for Connectivity Fault Management (CFM) Layer-2 packets over Multi-Protocol Label Switching (MPLS) networks are provided. The channel-type value of the G-ACh header may be used for identification of the network-generated CFM Layer-2 packets. In one implementation, a system may include a processing device and a memory device, where the memory device may be configured to store instructions that, when executed, cause the processing device to obtain a Connectivity Fault Management (CFM) packet, encapsulate the CFM packet with Pseudo-Wire (PW) and Label-Switched Path (LSP) labels to create an expanded packet, and incorporate a specific channel-type value in a G-ACh header of the expanded packet to uniquely identify the CFM packet.

Some embodiments provide a method for quantifying quality of several service classes provided by a link between first and second forwarding nodes in a wide area network (WAN). At a first forwarding node, the method computes and stores first and second path quality metric (PQM) values based on packets sent from the second forwarding node for the first and second service classes. The different service classes in some embodiments are associated with different quality of service (QoS) guarantees that the WAN offers to the packets. In some embodiments, the computed PQM value for each service class quantifies the QoS provided to packets processed through the service class. In some embodiments, the first forwarding node adjusts the first and second PQM values as it processes more packets associated with the first and second service classes. The first forwarding node also periodically forwards to the second forwarding node the first and second PQM values that it maintains for the first and second service classes. In some embodiments, the second forwarding node performs a similar set of operations to compute first and second PQM values for packets sent from the first forwarding node for the first and second service classes, and to provide these PQM values to the first forwarding node periodically.

A first provider edge device may receive device information from a second provider edge device included in an Ethernet virtual private network (EVPN). The device information may identify a media access control (MAC) address and may indicate that the device is connected to the second provider edge device. The first provider edge device may receive data transmitted by the device and may determine, based on information included in the data, that the device has moved from the second provider edge device to the first provider edge device. The first provider edge device may generate a data packet including mobility information indicating that the device has moved to the first provider edge device. The first provider edge device may transmit, via a data plane of the EVPN, the data packet to the second provider edge device to permit the second provider edge device to update routing information for the device.