Juniper Networks, Inc.

Sandip Kumar Ghosh

Reji Thomas

Jimmy Jose

Jameesh Kundanthodika

Jonathan C Barth

Swamy Sadashivaiah Renu Kananda

Eswaran Srinivasan

Srihari Ramachandra Sangli

Srinivasan Venkatakrishnan

Vyasraj Satyanarayana

Vineet Sharma

Marius Horia Marius Miclea

Lohith H Nayak

James R Henderson

Kishan Illur

Venkata Durga Pradeep Kumar Kasula

In some implementations, a network device may cause instantiation of a base container associated with a line card of the network device. The network device may cause, based on causing the instantiation of the base container, instantiation of a module container associated with a physical interface module of the line card of the network device. The network device may manage, using the base container, a forwarding table associated with the line card. The network device may manage, using the module container, one or more physical components of the physical interface module.

Enabling online insertion and removal of a physical interface module of a line card of a network device

A first network device may create a port group for a plurality of links directly connected to a second network device, and may select the first network device as a controller network device and the second network device as a worker network device. The first network device may rank the plurality of links of the port group to generate a list of ranked links, and may select, from the list of ranked links, a highest ranked link as a control channel. The first network device may power off one or more of the plurality of links, except the control channel, based on one of a configuration, a policy, or a traffic prediction, and may identify a termination of a time period associated with powering off the one or more of the plurality of links. The first network device may power on the one or more of the plurality of links based on the termination of the time period.

Power optimization using dynamic bandwidth management between connected network devices

A network device sends, via a first port of the network device and to a server device, first traffic, wherein the server device provides a NFV service line card of the network device, and wherein the first traffic is at least one of first management plane traffic associated with the NFV service line card, first control plane traffic associated with the NFV service line card, or first data plane traffic associated with the NFV service line card. The network device receives, via a second port of the network device and from the server device, second traffic, wherein the second traffic is at least one of second management plane traffic associated with the NFV service line card, second control plane traffic associated with the NFV service line card, or second data plane traffic associated with the NFV service line card.

Facilitating elasticity of a network device

In some implementations, a system may identify historical utilization data associated with a network device. The system may determine, based on the historical utilization data, a utilization forecast for the network device. The system may determine, based on the utilization forecast, a power management plan for the network device. The system may selectively control, based on the power management plan, enablement and disablement of one or more non-forwarding components of the network device.

Power management of a network device

A device may receive a lock request associated with using an embedded device of a containerized environment from a first instance of an application being executed in a first container of the containerized environment. The device may perform a lock operation associated with the embedded device to permit the first instance of the application to use the embedded device and to prevent a second instance of the application, executing in a second container of the containerized environment, from using the embedded device. The device may monitor use of the embedded device during an access operation of the first instance of the application to detect an unlock event associated with unlocking the embedded device. The device may perform an unlock operation based on detecting the unlock event to permit the second instance of the application to use the embedded device.

Device access control for applications of multiple containers

In some implementations, a network device may determine a maximum bandwidth requirement (MBR) associated with a network device. The network device may reduce based at least in part on the MBR, a power level of a component of the network device.

Power level reduction based on maximum bandwidth requirement

In the present disclosure, systems and techniques for network device hardware containerization is described. In one example, a network device of a network having a topology of network devices includes processing circuitry of a routing component wherein the processing circuitry generates user space containers to operate forwarding engines in each of a plurality of forwarding components of the network device; stores information for directing communications involving the plurality of forwarding components and the network devices; and configures, by at least one user space container running on the processing circuitry of the routing component, one or more corresponding forwarding engines in a respective forwarding component using the information.

Containerized management of forwarding components in a router using routing engine processor

A network device may determine, based on at least one network egress characteristic associated with a network device, a measure of priority associated with a network address. The network device may provide the measure of priority to a plurality of other routers, determine that a particular network egress characteristic of the at least one network egress characteristic has changed, and update the measure of priority based on the particular network egress characteristic. Based on the updated measure of priority, the network device may perform an action.

Adaptive network routing

In general, techniques provide a mapping of host devices to different virtual router identifiers used to identify the source MAC address used for forwarding packets to the participating host devices. For example, a method may include receiving an Address Resolution Protocol (ARP) request for a first Internet protocol (IP) address from a host device, the first IP address comprising a virtual IP address of the virtual router. The method may also include determining a virtual router redundancy protocol (VRRP) virtual router identifier (VRID) associated with the first IP address. The method may further include generating a mapping between the host device and the determined VRID. The method may also include determining a virtual source MAC address of the virtual router based on the mapping and forwarding a second packet to the host device that specifies a virtual source MAC address for the second packet.

Source MAC access controls in a virtual redundant router protocol environment

A device may determine first configuration information associated with configuring a chassis. The device may configure the chassis in a first mode using the first configuration information to cause the chassis to perform routing for a network. The device may determine, after a first period of routing for the network, second configuration information associated with configuring the chassis. The second configuration information may relate to utilizing one or more computing resources of a server device external to the chassis to perform routing for the chassis. The device may configure the chassis in a second mode using the second configuration information to cause the chassis to perform, in a second period, routing for the network.

Hybrid network function virtualization

In some examples, a computing device includes one or more processors and a physical interface device (IFD) connected to one or more of the processors. One or more of the processors are configured to detect a change in physical link status for a physical link in a network interface card, receive a list of active virtual machines associated with the physical link, and transmit a virtual IFD status notification message to the active virtual machines of virtual IFDs impacted by the physical link status change, the virtual IFD status notification message identifying the physical link status change.

Physical interface to virtual interface fault propagation

A first network device may activate the first network device as being associated with a Virtual Router Redundancy Protocol (VRRP) group. The first network device may receive, from a second network device, a duplicate address detection message. The first network device may compare a data link layer address associated with the duplicate address detection message and a Virtual Media Access Control (VMAC) address of the VRRP group. The first network device may disregard the duplicate address detection message after comparing the data link layer address and the VMAC address of the VRRP group.

Avoiding false duplicate network address detection in virtual router redundancy protocol (VRRP) scenarios

A configurable advertisement count and skew timer in a virtual router can be used to improve the speed with which a backup virtual router assumes the role of master upon the master router's failure. Enhanced VRRP packets having a type other than one may be used to cause MAC address movement from a failed master router to a backup router assuming the role of master router without placing an undue load on other routers in the network, such as by dropping the enhanced VRRP packets having a type other than one without processing the packets in the control plane of a receiving virtual router.

Growing community of inventors

Bengaluru, India

Sandip Kumar Ghosh