Juniper Networks, Inc.

Vamsi Krishna A

Viswanath K J

Paleti Venkata Ramana

Prabhu Raj V K

Sudheendra Bellamkonda

Prabhu Raj Vk

Venkata Ramana P

Viswanath Kj

The disclosed method may include (1) detecting, within at least one interface of a first endpoint device, a connectivity failure that disrupts a Layer 2 service based on an MPLS connection between the interface of the first endpoint device and at least one interface of a second endpoint device, (2) in response to detecting the connectivity failure, sending, to the second endpoint device, a first bidirectional BFD packet that prompts the second endpoint device to at least partially disable the interface of the second endpoint device, (3) determining that the connectivity failure has been corrected, and then (4) re-establishing the Layer 2 service based on the MPLS connection by sending, to the second endpoint device, a second BFD packet that prompts the second endpoint device to re-enable the interface of the second endpoint device. Various other apparatuses, systems, and methods are also disclosed.

Systems and methods for deadlock avoidance within MPLS networks

A device may receive a network policy, the network policy specifying: a matching criteria and an action to be performed on network traffic that matches the matching criteria. The device may generate type-length-value (TLV) data based on the network policy, a value portion of the TLV data including data specifying the network policy. In addition, the device may add the TLV data to a Connectivity Fault Management (CFM) packet and transmit the CFM packet to a separate device to cause the network policy to be implemented on the separate device.

Distributing a network policy using connectivity fault management

A first maintenance endpoint (MEP) device may identify that a first interface of the first MEP device is associated with a connectivity failure. The first MEP device may provide, to a second MEP device, a first continuity check message (CCM), that includes a MEP identifier of the first MEP device. The first CCM may cause the second MEP device to designate a second interface of the second MEP device as being offline. The first MEP device may receive, from the second MEP device, a second CCM, that includes the MEP identifier of the first MEP device and information indicating that the second interface of the second MEP device is offline. The first MEP device may execute a rule to avoid a deadlock situation based on the second CCM including the MEP identifier of the first MEP device.

Deadlock avoidance using modified ethernet connectivity fault management signaling

A device may receive an indication to perform a loopback test to identify a source of a communication error among a set of devices. The device may configure a value in a data structure to permit identification of a set of packets during the loopback test. The value may be associated with a parameter related to the set of packets. The device may perform the loopback test using the set of packets. A header of the set of packets may be configured with a same value for a same parameter as the value configured in the data structure. The device may identify the source of the communication error based on a result of performing the loopback test. The device may perform an action related to addressing the communication error based on identifying the source of the communication error.

Growing community of inventors

Bengaluru, India

Vamsi Krishna A