Abstract:
A method and system are disclosed for distributing (advertising) segment identifiers in network functions virtualization and/or software defined networking environments. An exemplary method includes receiving a route advertisement that includes a prefix with a forwarding address for a first network element and receiving a segment identifier (SID) advertisement that includes a prefix SID for the prefix. The route advertisement may be received from a second network element proxying control plane functions for the first network element. Reachability information for the first network element is updated based on the route advertisement and the SID advertisement.
Abstract:
An example method for seamless path monitoring and rapid fault isolation using bidirectional forwarding detection (BFD) in a network environment is provided and includes determining a BFD target identifier type for communicating in a BFD session in a network environment, determining a non-zero globally assigned BFD discriminator value associated with the BFD target identifier type, populating a Your Discriminator field in a BFD Control Packet with the non-zero globally assigned BFD discriminator value, with a My Discriminator field in the BFD Control Packet being populated with a locally assigned BFD Discriminator value, and initiating the BFD session by transmitting the BFD Control Packet to a target node in the network. In a specific embodiment, the BFD target identifier type is type 3, and the non-zero globally assigned BFD discriminator is an Alert Discriminator reserved by substantially all nodes in the network exclusively for BFD traceroute operations.
Abstract:
In one embodiment, a circuit that extends between a head-end label switching router (LSR) and a tail-end LSR and traverses one or more intermediate LSRs is locked to data plane traffic. The head-end LSR transmits a packet along the circuit that includes a particular time-to-live (TTL) value configured to expire at a particular intermediate LSR at which loopback is to occur. The circuit is used in a loopback mode. The head-end LSR transmits along the circuit a packet that includes a cease loopback request. The circuit ceases to be used in the loopback mode. The circuit is unlocked to permit the circuit to pass data plane traffic.
Abstract:
Particular embodiments may enable setup and signaling of co-routed and non co-routed label switched paths (LSPs) of a bidirectional packet traffic engineering (TE) tunnel in an unambiguous manner with respect to provisioning of the LSPs/tunnel. A head-end node may set up the bidirectional packet TE tunnel by computing a forward (and possibly a reverse) direction LSP, and then signal the bidirectional TE tunnel utilizing, e.g., extensions to an associated Resource Reservation Protocol (RSVP) signaling method. The extensions to the associated RSVP signaling method include a plurality of additional Association Types of an Extended Association object carried in a RSVP Path message transmitted by the head-end node to the tail-end node over the forward direction LSP, wherein the additional Association Types explicitly identify the provisioning of the forward and reverse direction LSPs as co-routed or non co-routed.
Abstract:
In one embodiment, a maintenance intermediate point (MIP) receives a packet traveling along a multi-protocol label switching (MPLS) label switched path (LSP) that extends from a first maintenance end point (MEP) to a second MEP. The receiving MIP decrements a time-to-live (TTL) value in a header of the packet. In response the TTL value in the header of the packet equaling a particular value, the receiving MIP examines an associated channel header (ACH) field in an operations, administration, and maintenance (OAM) message stored in a payload of the packet, and determines a particular OAM function to perform based on a code in the ACH field. The receiving MIP performs the particular OAM function.
Abstract:
Particular embodiments may enable setup and signaling of co-routed and non co-routed label switched paths (LSPs) of a bidirectional packet traffic engineering (TE) tunnel in an unambiguous manner with respect to provisioning of the LSPs/tunnel. A head-end node may set up the bidirectional packet TE tunnel by computing a forward (and possibly a reverse) direction LSP, and then signal the bidirectional TE tunnel utilizing, e.g., extensions to an associated Resource Reservation Protocol (RSVP) signaling method. The extensions to the associated RSVP signaling method include a plurality of additional Association Types of an Extended Association object carried in a RSVP Path message transmitted by the head-end node to the tail-end node over the forward direction LSP, wherein the additional Association Types explicitly identify the provisioning of the forward and reverse direction LSPs as co-routed or non co-routed.
Abstract:
In one embodiment, a circuit that extends between a head-end label switching router (LSR) and a tail-end LSR and traverses one or more intermediate LSRs is locked to data plane traffic. The head-end LSR transmits a packet along the circuit that includes a particular time-to-live (TTL) value configured to expire at a particular intermediate LSR at which loopback is to occur. The circuit is used in a loopback mode. The head-end LSR transmits along the circuit a packet that includes a cease loopback request. The circuit ceases to be used in the loopback mode. The circuit is unlocked to permit the circuit to pass data plane traffic.
Abstract:
A method for teleprotection over a segment routed network comprises receiving network requirements for communication between a first teleprotection relay and a second teleprotection relay, the first teleprotection relay associated with a first router of the segment routed network, and the second teleprotection relay associated with a second router of the segment routed network, identifying a primary path from the first router to the second router satisfying the network requirements, determining a congruent reverse of the primary path satisfies the network requirements, sending, to the first router, the primary path, the first router routing traffic from the first teleprotection relay to the second teleprotection relay using the primary path, and sending, to the second router, the congruent reverse of the primary path, the second router routing traffic from the second teleprotection relay to the first teleprotection relay using the congruent reverse of the primary path.
Abstract:
In one example embodiment, a first path computation element of a first segment routing domain includes a plurality of path computation clients. The first path computation element obtains, from at least one path computation client of the plurality of path computation clients, telemetry data indicating network traffic congestion for the at least one path computation client. Based on the telemetry data, the first path computation element determines that the at least one path computation client is experiencing at least a predetermined amount of network traffic congestion. In response to determining that the at least one path computation client is experiencing at least the predetermined amount of network traffic congestion, the first path computation element sends, to a second path computation element of a second segment routing domain, an indication of the network traffic congestion for the at least one path computation client.
Abstract:
A method is provided in one example embodiment and includes receiving a request to create a path through a network, wherein the path originates on a first network device and terminates on the second network device; identifying a first controller associated with the first network device, wherein the first controller proxies control plane functions for the first network device; identifying a second controller associated with the second network device, wherein the second controller proxies control plane functions for the second network device; and computing the path using the first controller as a source and the second controller as a destination. The first controller installs the computed path on the first network device and the second controller installs the computed path on the second network device.