Abstract: Systems and methods include operating a label distribution protocol (LDP) session with a peer node in a network; responsive to a change in graceful restart of the LDP session, sending a notification message to the peer node with a graceful restart capability change indication; responsive to receiving a second notification message from the peer node with graceful restart capability change indication, updating the graceful restart capability for the LDP session; and, responsive to failing to receive the second notification message, leaving the graceful restart capability as it was prior to the change.

Abstract: A Point of Local Repair (PLR) network element includes one or more ports and circuitry connected thereto for forwarding and control, wherein the circuitry is configured to receive a PATH message for a Label Switched Path (LSP) tunnel in a Multiprotocol Label Switching (MPLS) network with a specified DiffSery Traffic Engineering (DSTE) Class Type, determine the DSTE Class Type based on the PATH message, and store the DSTE Class Type for the LSP tunnel to ensure a Facility Bypass tunnel used for the LSP tunnel supports the specified DSTE Class Type. The circuitry can be further configured to, responsive to a failure of the LSP tunnel, select the Facility Bypass tunnel for the LSP tunnel such that the Facility Bypass tunnel supports the specified DSTE Class Type.

Abstract: A node, in a first network, includes circuitry configured to determine a next hop as decided by Border Gateway Protocol (BGP) is an anycast prefix to a Route Reflector (RR) interconnecting the first network with a second network, responsive to the next hop being the anycast prefix to the RR, create a tunnel with a destination based on the anycast prefix, and utilize the tunnel for traffic having the next hop as the anycast prefix to the RR. The anycast prefix is assigned to two or more RRs interconnecting the first network and the second network. A first path is decided by BGP based on a BGP Path Selection Algorithm that is independent of a second path determined by Interior Gateway Protocol (IGP). The first path and the second path can be different, and wherein tunnel is utilized to ensure the traffic always follows the first path.

Abstract: A node, in a first network, includes circuitry configured to add a label stack to a packet associated with one of a Layer 2 Virtual Private Network (L2VPN) and a Layer 3 Virtual Private Network (L3VPN), wherein the packet is destined for a second network having at least a pair of Border Gateway Protocol-Label Unicast (BGP-LU) Route Reflector (RR) nodes interconnecting the first network, and wherein the label stack includes an anycast Segment Identifier (SID) for the RR nodes, in Segment Routing, and transmit the packet to the second network. The label stack also includes a BGP-LU label for a destination in the second network. Responsive to isolation of one of the RR nodes, a Point of Local Repair (PLR) node in the first network is configured to implement Topology-Independent Loop-Free Alternate (TI-LFA) for the anycast SID.

Abstract: A node, in a first network, includes circuitry configured to add a label stack to a packet associated with one of a Layer 2 Virtual Private Network (L2VPN) and a Layer 3 Virtual Private Network (L3VPN), wherein the packet is destined for a second network having at least a pair of Border Gateway Protocol-Label Unicast (BGP-LU) Route Reflector (RR) nodes interconnecting the first network, and wherein the label stack includes an anycast Segment Identifier (SID) for the RR nodes, in Segment Routing, and transmit the packet to the second network. The label stack also includes a BGP-LU label for a destination in the second network. Responsive to isolation of one of the RR nodes, a Point of Local Repair (PLR) node in the first network is configured to implement Topology-Independent Loop-Free Alternate (TI-LFA) for the anycast SID.

Abstract: A network element includes a plurality of ports interconnected by a switching fabric, wherein a port includes a plurality of connections including an infrastructure connection that operates a Bidirectional Forwarding Detection (BFD) session and a group of connections that share a similar fate for a fault as the infrastructure connection; and a controller configured to detect a fault on the infrastructure connection via the BFD session, and cause a protection switch for one or more of the group of connections based on the fault on the infrastructure connection. The infrastructure connection and the group of connections can be Pseudowires (PWE) or Label Switched Paths (LSPs) in a Multiprotocol Label Switching (MPLS) network.

Abstract: A node includes one or more line cards interconnected to one another via a switching fabric and configured to implement a data plane; and a first router processor and a second router processor communicatively coupled to the one or more line cards, and each configured to implement a separate control plane, such that the node appears in a link-state database as two separate nodes. Responsive to an in-service software upgrade, the first router processor is upgraded and down while the second router processor is active, thereby preserving routing and forwarding. The one or more line cards include a first Virtual Local Area Networking (VLAN) for the first router processor and a second VLAN for the second router processor, and the first VLAN and the second VLAN are associated with a same physical interface on the one or more line cards.

Abstract: Systems and methods include receiving one or more Ethernet Virtual Private Network (EVPN) advertisements from one or more peer nodes with information including any of traffic characterization information and traffic control information; and providing traffic to the EVPN and to the corresponding one or more peer nodes based on the information from the corresponding one or more peer nodes. The one or more EVPN advertisements can be in an EVPN Network Layer Reachability Information (NLRI) advertisement, and the EVPN NLRI can have Route Type 1 for the information to apply to an EVPN Instance (EVI) and the EVPN NLRI can have Route Type 2 for the information to apply to a specific customer node based on a Media Access Control (MAC).

Abstract: Systems and methods include receiving one or more Ethernet Virtual Private Network (EVPN) advertisements from one or more peer nodes with information including any of traffic characterization information and traffic control information; and providing traffic to the EVPN and to the corresponding one or more peer nodes based on the information from the corresponding one or more peer nodes. The one or more EVPN advertisements can be in an EVPN Network Layer Reachability Information (NLRI) advertisement, and the EVPN NLRI can have Route Type 1 for the information to apply to an EVPN Instance (EVI) and the EVPN NLRI can have Route Type 2 for the information to apply to a specific customer node based on a Media Access Control (MAC).

Abstract: A node includes one or more line cards interconnected to one another via a switching fabric and configured to implement a data plane; and a first router processor and a second router processor communicatively coupled to the one or more line cards, and each configured to implement a separate control plane, such that the node appears in a link-state database as two separate nodes. Responsive to an in-service software upgrade, the first router processor is upgraded and down while the second router processor is active, thereby preserving routing and forwarding. The one or more line cards include a first Virtual Local Area Networking (VLAN) for the first router processor and a second VLAN for the second router processor, and the first VLAN and the second VLAN are associated with a same physical interface on the one or more line cards.

Abstract: A Point of Local Repair (PLR) network element includes one or more ports and circuitry connected thereto for forwarding and control, wherein the circuitry is configured to receive a PATH message for a Label Switched Path (LSP) tunnel in a Multiprotocol Label Switching (MPLS) network with a specified DiffSery Traffic Engineering (DSTE) Class Type, determine the DSTE Class Type based on the PATH message, and store the DSTE Class Type for the LSP tunnel to ensure a Facility Bypass tunnel used for the LSP tunnel supports the specified DSTE Class Type. The circuitry can be further configured to, responsive to a failure of the LSP tunnel, select the Facility Bypass tunnel for the LSP tunnel such that the Facility Bypass tunnel supports the specified DSTE Class Type.

Abstract: 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.

Abstract: A node includes a plurality of ports configured to provide a service over a primary Multi-Segment Pseudowire (MS-PW) and a backup MS-PW in a network; a switching fabric interconnecting the plurality of ports; and a controller communicatively coupled to the plurality of ports and the switching fabric, wherein the controller is configured to receive a pseudowire status message for each of the primary MS-PW and the backup MS-PW, determine a Signal Degrade condition on one of the primary MS-PW and the backup MS-PW based on the pseudowire status message, and cause a switch of the service to an inactive one of the primary MS-PW and the backup MS-PW based on a Signal Degrade condition on an active one of the primary MS-PW and the backup MS-PW. The controller can further provide a trap to a management system based on the determined Signal Degrade condition.

Abstract: A network element includes a plurality of ports interconnected by a switching fabric, wherein a port includes a plurality of connections including an infrastructure connection that operates a Bidirectional Forwarding Detection (BFD) session and a group of connections that share a similar fate for a fault as the infrastructure connection; and a controller configured to detect a fault on the infrastructure connection via the BFD session, and cause a protection switch for one or more of the group of connections based on the fault on the infrastructure connection. The infrastructure connection and the group of connections can be Pseudowires (PWE) or Label Switched Paths (LSPs) in a Multiprotocol Label Switching (MPLS) network.

Abstract: A node includes a plurality of ports configured to provide a service over a primary Multi-Segment Pseudowire (MS-PW) and a backup MS-PW in a network; a switching fabric interconnecting the plurality of ports; and a controller communicatively coupled to the plurality of ports and the switching fabric, wherein the controller is configured to receive a pseudowire status message for each of the primary MS-PW and the backup MS-PW, determine a Signal Degrade condition on one of the primary MS-PW and the backup MS-PW based on the pseudowire status message, and cause a switch of the service to an inactive one of the primary MS-PW and the backup MS-PW based on a Signal Degrade condition on an active one of the primary MS-PW and the backup MS-PW. The controller can further provide a trap to a management system based on the determined Signal Degrade condition.

Abstract: Systems and methods for auto creation of bypass tunnels in Fast Reroute (FRR) downstream routers include configuring one or more Label Switched Path (LSP) tunnels between an ingress Label Edge Router (LER) and an egress LER via one or more Label Switch Routers (LSRs); signaling at least one LSP tunnel of the one or more LSP tunnels with a Resource Reservation Protocol (RSVP) PATH message containing a FAST_REROUTE object with a first flag indicating Facility Backup protection is desired and a second flag indicating auto generation of an associated FB bypass tunnel; and configuring the associated FB bypass tunnel between a Point of Local Repair (PLR) and a Merge Point (MP) based on the first flag and the second flag. The systems and methods can further include bypass tunnel reselection requests to a bypass tunnel with better protection.

Abstract: 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.

Abstract: Systems and methods for auto creation of bypass tunnels in Fast Reroute (FRR) downstream routers include configuring one or more Label Switched Path (LSP) tunnels between an ingress Label Edge Router (LER) and an egress LER via one or more Label Switch Routers (LSRs); signaling at least one LSP tunnel of the one or more LSP tunnels with a Resource Reservation Protocol (RSVP) PATH message containing a FAST_REROUTE object with a first flag indicating Facility Backup protection is desired and a second flag indicating auto generation of an associated FB bypass tunnel; and configuring the associated FB bypass tunnel between a Point of Local Repair (PLR) and a Merge Point (MP) based on the first flag and the second flag. The systems and methods can further include bypass tunnel reselection requests to a bypass tunnel with better protection.