Abstract:
The present disclosure provides for avoiding packet loss and delay that occurs during conventional link switchover by moving link switchover logic from a downstream PORT (Protocol Independent Multicast Over Reliable Transport) routing element to an upstream PORT routing element. An upstream PORT routing element detects the failure of a forwarding interface for a multicast datastream, where the forwarding interface is coupled to a downstream PORT routing element. In response to detecting the failure, the upstream PORT routing element determines a set of candidate interfaces that are also coupled to the downstream PORT routing element. The upstream PORT routing element selects a new interface from the set of candidate interfaces and installs the new interface as a replacement forwarding interface for the multicast datastream.
Abstract:
The present disclosure provides for carrying downstream mapping information in an echo request message and/or echo reply message, which can describe both IP (Internet Protocol) multipath information and label multipath information. A transit node (e.g., an LSR element) that receives an echo request message from an initiator node determines downstream mapping information, which is returned to the initiator node. Transit node determines whether a newly defined type of multipath information (type 10) should be generated to return the downstream mapping information, based on whether transit node performs load balancing based on labels or IP header information, and whether transit node imposes entropy labels. A multipath information type 10 element includes either IP multipath information or label multipath information, as well as associated label multipath information that includes one or more entropy labels that map to the IP or label multipath information being returned.
Abstract:
The present disclosure provides for carrying reachability information in an echo request message and/or an echo reply message, which can be used to reach an initiator when the initiator's address is unknown. An echo request message includes an FEC (forwarding equivalence class) stack that identifies a label switched path (LSP). The echo request message is received by a label switching routing element (LSR) on the LSP, and the echo request is originated by an initiator. In response to a detection that the FEC stack changes at the LSR, a segment reachability (SR) sub-TLV (type-length-value) element can be generated, where the SR sub-TLV includes reachability information that can be used to reach the initiator, and the reachability information includes an incoming label allocated by the LSR to reach the initiator.
Abstract:
In one embodiment, a method comprises generating, by a first provider edge router associated with a first segment identifier, a primary label for reaching a destination, and repair information for reaching the destination if a second provider edge router is unavailable to reach the destination; allocating, by the first provider edge router, a first protected next-hop address associated with the first segment identifier for protected reachability to at least the destination; and sending via a core network, by the first provider edge router, an advertisement specifying the label and the repair information, enabling an ingress provider edge router to insert, into a data packet destined for the destination, the labels from the first provider edge router and the second provider edge router based on the repair information, for fast rerouting to the destination via one of the first or second provider edge router if the other is unavailable.
Abstract:
A receiving node receives a virtual LDP initialization (vInit) message from a first node, where the vInit message comprises a request to establish a vLDP session between a requesting node and a target node. If the receiving node does not own a destination address of the vInit message, the receiving node is determined to be a relay node. The relay node inserts a relay label into the vInit message, where the relay label is an outgoing label that the relay node uses to reach the first node, and forwards the vInit message toward the destination address. If the receiving node owns the destination address, the receiving node is determined to be the target node, which extracts a stack of relay labels from the vInit message. The relay labels are used to define a return path to the requesting node for messages transmitted over the vLDP session.
Abstract:
In one embodiment, an ingress network virtualization edge (NVE) in a computer network generates an echo packet, and sets an indication in the echo packet that the echo packet is for overlay path validation. In addition, the ingress NVE sets a message type of the echo packet to a generic echo request, and includes virtualization network (VN) context information within the echo packet. Once setting a destination address of the echo packet as an egress NVE address and including an indication to the egress NVE that the echo packet is an operations, administration, and management (OAM) message, the ingress NVE may then send the echo packet toward the egress NVE (e.g., to validate the VN context information and/or to reveal multipath traces).