Juniper Networks, Inc.

Nirmal Anburose

Chandrasekhar A

Jayanthi R

Sankar Ramamoorthi

Tong Jiang

Premchandar N

Roshan Joyce

R Jayanthi

A Chandrasekhar

In one example, a network management system (NMS) device manages a plurality of network devices. The device includes a memory configured to store data representing a data model for a plurality of network devices managed by the NMS, and one or more processors configured to retrieve data representing the data model, construct a GraphQL model having a plurality of nodes, each of the nodes corresponding to one of the network devices according to the data model store data representing properties of the network devices associated with corresponding nodes of the GraphQL model according to the data model, receive a GraphQL query including data representing at least one query property, determine which of the nodes has a property matching the at least one query property, and return data identifying which of the network devices corresponds to the nodes having the property matching the at least one query property.

Supporting graphQL based queries on yang based configuration data models

Techniques are disclosed for managing a network. In one example, a device configuration manager is configured to generate, in accordance with a device management protocol, a configuration change request representing a transaction having a first sub-transaction specifying a first configuration change for a network device of the network and a second sub-transaction specifying a second configuration change for the same network device. The device configuration manager is further configured to output the configuration change request to the network device and receive a reply message from the network device. The reply message includes a first response element specifying whether the first configuration change is successfully committed at the network device and a second response element specifying whether the second configuration change is successfully committed at the network device.

Concurrent transactions on NETCONF devices across network services

In general, techniques are described for automatic intent provisioning and management in computer networks. A device comprising a processor, a memory, and an interface may perform the techniques. The processor may obtain a policy that includes high-level configuration data defining a service to be deployed within a network, the high-level configuration data including resource selector criteria that identifies one or more criteria for selecting a resource to support the service from a plurality of potential resources. The processor may also determine, based on the resource selector criteria, the resource to support the service from the plurality of potential resources, and translate the high-level configuration data to low-level configuration data specific to the determined resource. The memory may store the low-level configuration data specific to the determined resource. The interface may enable configuration, when provisioning the service, the determined resource using the low-level configuration data specific to the determined resource.

Dynamic intent assurance and programmability in computer networks

In one example, a network management system (NMS) and method discovers device roles for network devices. The NMS includes a learning module configured to include a learning model, the learning model trained to associate configuration segments for each of a plurality of network devices with device roles performed by the network devices. The NMS discovers a network service on a network, receives configuration information from the discovered network service and splits the configuration information received from the discovered network service into configuration segments based on a vendor neutral yang model associated with the discovered network service. The NMS then determines if the discovered network service performs one or more of the device roles performed by the network devices used to train the learning model, wherein determining includes applying the learning model to the configuration segments of the discovered network service.

Intelligent device role discovery

In one example, a network management system (NMS) device manages a plurality of network devices. The NMS device includes one or more processing units, implemented using digital logic circuitry, configured to receive configuration data for a plurality of network devices managed by the NMS device, construct a graph database representing the configuration data, wherein to construct the graph database, the one or more processing units are configured to construct a plurality of vertices representing respective elements of the configuration data, and connect related vertices of the plurality of vertices with edges. The one or more processing units are further configured to manage the plurality of network devices using the graph database.

Configuring and managing network devices using program overlay on Yang-based graph database

A system and method for service discovery. A network management system constructs, based on configuration data associated with a first network device and a second network device, respectively, a first partial service instance associated with a service executing on a first network device and a second partial service instance associated with the service executing on a second network device. The network management system merges the first partial service instance and a second partial service instance to form a merged partial service instance. The network management system promotes the merged partial service instance as a service instance.

Network configuration service discovery

A system may receive network device configuration information associated with a network service. The system may determine multiple settings associated with the network service based on receiving the network device configuration information. The multiple settings may include a common setting and a device-specific setting. The system may generate a first network service model of the network service based on the multiple settings. The first network service model may include multiple nodes corresponding to the multiple settings. The system may re-configure one or more nodes associated with the first network service model, and may generate a second network service model of the network service. The system may generate a user interface template based on the second network service model and may provide the user interface template to a client device for display. The client device may allow a configuration of the multiple settings based on the user interface template.

Generating network service models

In one example, a network management system (NMS) and method models services in a network. The NMS identifies externally mapped attributes in a vendor neutral yang model of a network service, assigns an attribute type to one or more of the externally mapped attributes, wherein assigning includes determining, by a learning system, the attribute type of one or more of the externally mapped attributes based on an analysis of attribute types assigned to the externally mapped attributes of other network services, constructs a separate dependency graph for each of the externally mapped attributes and builds a separate hidden service model for each of the externally mapped attributes, wherein the externally mapped attribute for each hidden service model is a merge attribute for that hidden service model.

A system and method for responding to exceptions in network services. A network management system (NMS) configures a first network service having an endpoint and a plurality of externally mapped attributes, the externally mapped attributes including one or more service level attributes and an endpoint attribute associated with the endpoint. The NMS detects an exception in the first network service, modifies the first network service in response to the exception, wherein modifying the first network service includes assigning the current value of the endpoint attribute of the first network service to the endpoint attribute of a second network service and validates the externally mapped attributes of the second network service.

Intelligent exception recovery in network services

In one example, a network management system (NMS) is configured to enable a target network device to support a particular network service based on service configuration information for the particular network service. The service configuration information may include information about nodes in a vendor neutral model that need to be added or modified in order to support the particular network service. The NMS determines similarity scores between nodes in a vendor neutral model and nodes in a target device specific model. Based on the similarity scores, the NMS generates a mapping from the vendor neutral model to the target device specific model. Using the mapping, the NMS may configure a target device to support the particular service.

Multi vendor device support in network management systems

In general, techniques are described for generating reversible mappings for management systems. The management system may include an interface and a processor. The interface may communicatively couple the management system to network devices. The processor may generate a data structure that represents each expression of a forward mapping as a separate node of the data structure. The processor may also translate one or more of the expressions represented as the separate nodes in the data structure to corresponding one or more negated expressions so as to form a reverse mapping. Further, the processor may apply the reverse mapping to the low-level configuration of the first network device to obtain the high-level configuration.

Reversible yang-based translators

In one example, a network management system (NMS) device manages a plurality of network devices. The NMS device includes a processor configured to determine a first set of differences between an existing high-level configuration for the plurality of network devices and a first received high-level configuration for the plurality of network devices, determine a second set of differences between the existing high-level configuration and a second received high-level configuration, wherein the second received high-level configuration is received separately from the first received high-level configuration, translate the first set of differences to a first low-level configuration modification, translate the second set of differences to a second low-level configuration modification, merge the first low-level configuration modification and the second low-level configuration modification, and apply the merged low-level configuration modification to low-level configuration of the plurality of network devices.

Growing community of inventors

Bengaluru, India

Nirmal Anburose