Juniper Networks, Inc.

Raviraj Satish Deshmukh

Pradeep H Krishnamurthy

Rahamath Sharif

Varun S K

Chandrasekhar A

Fnu Nadeem

Praveen Bk

Gireesh Kumar Maguluru

F N U Nadeem

A controller device manages a plurality of network devices. The controller device includes a memory comprising a configuration database including a set of stored network device configurations, wherein each stored network device configuration of the set of stored network device configurations corresponds to a network device of the set of network devices. Additionally, the controller device includes processing circuitry configured to receive an intent file corresponding to an intended configuration for the set of network devices; receive a message from a network device of the set of network devices indicating an out-of-band configuration change at the network device; and determine, based on a stored network device configuration corresponding to the network device and an actual configuration of the network device, whether the intent file is compatible with the out-of-band configuration change.

Identifying out-of-band configuration changes to validate intent files

In some implementations, a system may receive an extensible markup language (XML) configuration stream that indicates one or more resource configurations. The system may maintain a data model that includes metadata that describes the XML configuration stream. The system may process the data model to generate a metadata tree. The system may generate, based on the XML configuration stream and the metadata tree, one or more XML configuration sub-streams that are respectively associated with a subset of the one or more resource configurations. The system may process, using respective resource processing modules of the system, the one or more XML configuration sub-streams to generate respective information associated with the subset of the one or more resource configurations.

Generating XML configuration sub-streams based on an XML configuration stream and a metadata tree associated with the XML configuration stream

In one example, a network management system discovers a plurality of network devices behind a network address translation device, such as a firewall. The network management system may receive a model of a seed network device, generate a first activation configuration and commit the first activation configuration on the seed network device. The network management system may connect to the seed network device and discover neighboring devices from information in the seed network device. The network management system may connect to the neighboring devices, automatically create a model of the neighboring network devices, generate s activation configurations for the neighboring network devices and commit the activation configurations on the neighboring network devices. The network management system may iterative perform these steps until it discovers all the discoverable network devices behind the network address translation device.

Bulk discovery of devices behind a network address translation device

A controller device includes a memory configured to store a tree structure comprising a plurality of nodes, wherein the tree structure comprises a set of sub-structures, and wherein the tree structure defines a configuration of a network device of a set of network devices such that each node of the plurality of nodes corresponds to a respective resource of the network device. Additionally, the controller device includes processing circuitry configured to receive an instruction to update the configuration of the network device, wherein the instruction to update the configuration of the network device indicates a node of the set of nodes corresponding to the update; and verify, based on a sub-structure of the set of sub-structures corresponding to the node indicated by the instruction, the instruction to update the configuration of the network device.

Processing instructions to configure a network device

A network management system may discover a plurality of network devices behind a network address translation device, such as a firewall. The network management system may receive a model of N network devices, generate a bulk activation configuration for the N network devices and commit the bulk activation configuration on a seed network device. The network management system may receive a request for a first connection from a first neighboring network device and may connect to the first neighboring network device. The first neighboring network device may have received the bulk activation configuration from the seed device. The network management system may determine whether the first neighboring network device is one of the N network devices and commit a second activation configuration on the first neighboring network device if it is one of the N network devices. A plurality of neighboring network device may be configured in this fashion.

In an example, a method includes receiving, by a network management system (NMS), a configuration request comprising first configuration data for a network device, the first configuration data defining a data structure comprising a first property/value pair; generating, by the NMS from the first configuration data, a corresponding first path/value pair for the first property/value pair, wherein a path of the first path/value pair uniquely identifies the first path/value pair in an associative data structure; modifying, by the NMS, the associative data structure based on the first path/value pair; generating, by the NMS, from the associative data structure, a configuration resource comprising second configuration data for the network device, the second configuration data comprising a second property/value pair that corresponds to the first path/value pair; and sending, by the NMS, the second configuration data to the network device to modify a configuration of the network device.

Sharing configuration resources for network devices among applications

Scalable, robust cloud-based network management systems (NMSs) are described. In one, an NMS includes a set of NMS applications, a pool of device communication managers (DCMs), and a pool of device operations managers (DOMs). Each of the DCMs and DOMs executed by the processors as software containers. The NMS includes an API gateway configured to route remote procedure calls (RPCs) from the DCMs to the DOMs via the APIs exposed by the DOMs and according to device identifiers of the managed elements. The DOMs are configured to establish a set of persistent application-layer communication sessions from the DOMs to the DCMs and to direct communications from the NMS applications to the DCMs over the persistent application-layer communication sessions according to a mapping between device identifiers associated with the managed elements and network addresses associated with the DCMs.

Growing community of inventors

Pune, India

Raviraj Satish Deshmukh