Juniper Networks, Inc.

Wing Eng

Pallavi Mahajan

Philip Austin Shafer

Nischal Sheth

Manoj Leelanivas

Steven Lin

Paul S Traina

Andrew H Heffernan

Kireeti Kompella

Gregory Allan Sidebottom

Sriram Raghunathan

Karthikeyan Ramasamy

Sherine El-Medani

Sri Ram Sankar

An example computing device is configured to receive an instance of a customer service model representative of a plurality of customer services. Each of the plurality of customer services associated with a corresponding at least one requirement and a corresponding at least one constraint. The computing device is configured to receive an instance of a resource model representative of a plurality of resources and map the instance of the customer service model and the instance of the resource model to an internal placement model. The computing device is configured to allocate the plurality of resources to the plurality of customer services such that the at least one requirement and the at least one constraint for each of the plurality of customer services are satisfied and inverse map data indicating how the plurality of resources are allocated to a format consumable by the customer device and output the inverse mapped data.

Model-based service placement

Techniques are described for implementing one or more logical routers within a single physical routing device. These logical routers, as referred to herein, are logically isolated in the sense that they achieve operational and organizational isolation within the routing device without requiring the use of additional or redundant hardware, e.g., additional hardware-based routing controllers. The routing device may, for example, include a computing platform, and a plurality of software process executing within the computing platform, wherein the software processes operate as logical routers. The routing device may include a forwarding component shared by the logical routers to forward network packets received from a network in accordance with the forwarding tables.

Routing device having multiple logical routers

In general, techniques are described for a batch configuration mode for configuring network devices. A network device comprising a committed data source and a control unit may implement the techniques. The control unit may receive a plurality of separate commit commands instructing the network device to commit configuration changes to the committed data source. Each of the plurality of commit commands instructs the network device to commit an associated portion of the configuration changes to the committed data source. The control unit then groups two or more of the plurality of separate commit commands to form a batch of commit commands and executes the batch of commit commands to commit the portions of the configuration changes associated with the grouped commit commands to the committed data source as if the grouped portions of the configuration changes were associated with a single commit command.

Batch configuration mode for configuring network devices

A multi-chassis router allows an administrator to install software from a single user interface. The multi-chassis router automatically forwards the software to each chassis within the multi-chassis router when given a single command to install the software from an administrator. The multi-chassis router also automatically validates the software on each chassis. After reporting the results of the validations, the multi-chassis router may wait for the administrator to issue a commit command before committing each chassis within the multi-chassis router to the software. Alternatively, in response to a failed validation or for other reason, an administrator can issue a single ROLLBACK command. This allows each chassis within the multi-chassis router to have the same software during all stages of a software installation and ensures software on each chassis is compatible with software on every other chassis.

Software installation on a multi-chassis network device

Software installation in a multi-chassis network device

A multi-chassis router allows an administrator to distribute configuration data from a single user interface. Additionally, the multi-chassis router presents a software image consistent with that of a standalone router and uses configuration data syntax that is consistent with that of a standalone router. The multi-chassis router automatically distributes and validates relevant configuration data at each chassis within the multi-chassis router. In effect, an administrator does not need to account for the multiple chassis configuration, and an administrator familiar with the configuration data syntax for a standalone router can use that knowledge to configure the multi-chassis router.

Centralized configuration of a multi-chassis router

A multi-chassis router allows an administrator to deliver commands from a single interface. Additionally, the multi-chassis router presents a software image consistent with that of a standalone router and uses commands and configurations consistent with those used by a standalone router. The multi-chassis router automatically distributes, processes and responds to administrator commands a single unit, minimizing time required to administer the multi-chassis router. In effect, an administrator does not need to account for the multiple chassis configuration, and an administrator familiar with the control and commands for a standalone router can use that knowledge to effectively control the operation of the multi-chassis router.

Extending standalone router syntax to multi-chassis routers

A multi-chassis router allows an administrator to install software from a single user interface. The multi-chassis router automatically forwards the software to each chassis within the multi-chassis router when given a single command to install the software from an administrator. The multi-chassis router also automatically validates the software on each chassis. This allows each chassis within the multi-chassis router to have the same software during all stages of a software installation and ensures software on each chassis is compatible with software on every other chassis. In effect, an administrator does not need to account for the multiple chassis configuration, and an administrator familiar with software installation on a standalone router can use that knowledge to install software on the multi-chassis router.

Growing community of inventors

Ithaca, NY, United States of America

Wing Eng