Abstract: A router configured to implement Border Gateway Protocol (BGP) includes circuitry configured receive BGP update messages from the one or more BGP peers, monitor one or more operational criteria associated with handling of the received BGP update messages, detect a trigger event indicative of a risk that continued reception of BGP update messages at a current rate could exceed a capacity of the router, and, in response to detecting the trigger event, transmit a BGP notification message to at least one of the BGP peers, the BGP notification message instructing the BGP peer to lock its BGP session with the router so that no prefixes are sent, thereby providing an automatic session lockout mechanism that prevents network fallout without terminating the BGP neighborship or causing route withdrawals.

Abstract: A router configured to implement Border Gateway Protocol (BGP) includes circuitry configured to receive BGP updates from one or more BGP peers connected to the router, detect a trigger related to BGP updates where the trigger is indicative of a need to apply backpressure by the one or more BGP peers, and send a backpressure notification message to the one or more BGP peers based on the trigger, such that the one or more BGP peers apply the backpressure. The circuitry can be further configured to monitor one or more criteria associated with operation of the router, for the trigger.

Abstract: A router configured to implement Border Gateway Protocol (BGP) includes circuitry configured to receive BGP updates from one or more BGP peers connected to the router, detect a trigger related to BGP updates where the trigger is indicative of a need to apply backpressure by the one or more BGP peers, and send a backpressure notification message to the one or more BGP peers based on the trigger, such that the one or more BGP peers apply the backpressure. The circuitry can be further configured to monitor one or more criteria associated with operation of the router, for the trigger.

Abstract: Systems and methods include, in a first Label Edge Router (LER) in a Multiprotocol Label Switching (MPLS) network, creating a primary tunnel with a second LER; creating a Make Before Break (MBB) tunnel with the second LER for the primary tunnel; prior to switching to the MBB tunnel from the primary tunnel, sending an MPLS request to the second LER via the MBB tunnel and receiving an MPLS response from the second LER via the MBB tunnel indicating successfully creation of the MBB tunnel; switching to the MBB tunnel responsive to the successfully creation of the MBB tunnel; and, prior to tearing down the primary tunnel, checking statistics of the MBB tunnel to ensure traffic has moved to the MBB tunnel from the primary tunnel.

Abstract: Systems and methods include, in a first Label Edge Router (LER) in a Multiprotocol Label Switching (MPLS) network, creating a primary tunnel with a second LER; creating a Make Before Break (MBB) tunnel with the second LER for the primary tunnel; prior to switching to the MBB tunnel from the primary tunnel, sending an MPLS request to the second LER via the MBB tunnel and receiving an MPLS response from the second LER via the MBB tunnel indicating successfully creation of the MBB tunnel; switching to the MBB tunnel responsive to the successfully creation of the MBB tunnel; and, prior to tearing down the primary tunnel, checking statistics of the MBB tunnel to ensure traffic has moved to the MBB tunnel from the primary tunnel.