Juniper Networks, Inc.

Shrish Mahishi

Sunil Mekad

Pramod Srinivasan

Vyasraj Satyanarayana

Gopinath Ramasamy

Sanjeev Anandrao Mahajan

Ramesh Rajan

Atit Jain

Dhaval Bakulesh Bhodia

Saleem Rahim

Prashant M Iliger

Shrishail Halbhavi

Nitesh Bahadur Sinha

Kathiresan Kandasamy

Vijay Paul

Murali P T

A disclosed computing device capable of instantly switching over between routing engines may include (1) a packet forwarding board configured to (A) forward control traffic via a first link to a traffic replication device and (B) forward data traffic via a second link to a first routing engine, (2) the traffic replication device configured to (A) replicate the control traffic received from the packet forwarding board and (B) select control signals received from the first routing engine, (3) the first routing engine configured to receive control traffic from the traffic replication device, and (4) a second routing engine configured to receive control traffic from the traffic replication device. Various other apparatuses, systems, and methods are also disclosed.

Apparatus, system, and method for instant routing engine switchovers

A network device may be configured to identify a first configuration data structure included in the network device and may be configured to obtain a data package associated with an ISSU procedure that includes a second configuration data structure. The network device may be configured to identify, based on the first configuration data structure and the second configuration data structure, one or more configuration functionalities of the network device that are to not be active during performance of the ISSU procedure. The network device may be configured to cause the one or more configuration functionalities of the network device to be deactivated and to thereafter cause the ISSU procedure to be performed. The network device may be configured to cause, after causing the ISSU procedure to be performed, the one or more configuration functionalities of the network device to be activated.

Automatic deactivation and activation of configuration functionalities of a network device that are incompatible with performance of an in-service software upgrade procedure

A network device may receive packets, wherein the network device includes a first routing component, a second routing component, a first forwarding component, a second forwarding component, and a physical interface card concentrator with multiple physical interface cards. The first routing component may provide, to the physical interface card concentrator, a signal indicating that the second forwarding component is to be an active forwarding component. The physical interface card concentrator may cause, based on the signal, a data path for the multiple physical interface cards to be switched from the first forwarding component to the second forwarding component. The first routing component may provide the packets to the second forwarding component. The second forwarding component may provide the packets to the multiple physical interface cards via the data path. The multiple physical interface cards may forward the packets toward destinations associated with the packets.

Hardware-assisted fast data path switchover for a network device with redundant forwarding components

A network device obtains a data package associated with an ISSU procedure and determines, based on the data package, that a control plane of the network device is to be rebooted to facilitate performance of the ISSU procedure. The network device causes, based on determining that the control plane is to be rebooted, a plurality of applications of the network device to stop executing on the network device and a control plane state of the network device to be frozen. The network device then causes the ISSU procedure to be performed. The network causes, based on causing the ISSU procedure to be performed, the control plane state of the network device to be restored and the plurality of applications to resume executing on the network device.

Hitless upgrade of a network device

In one example, a management component executes on a network device, a first routing component executing on a first server device physically separate from the network device to provide control plane routing functionality for a virtual node on the network device, and a second routing component executing on a second server device physically separate from the network device to provide control plane routing functionality for the virtual node, wherein the first routing component and the second routing component operate as a redundant master-backup pair for the virtual node. The management component is configured to detect first reachability of the network device with a first routing component and second reachability of the network device with a second routing component, and send a control message to each of the first routing component and the second routing component, the control message specifying reachability information indicating the first reachability and the second reachability.

Arbitrating mastership between redundant control planes of a virtual node

Growing community of inventors

Bengaluru, India

Shrish Mahishi