Multi vendor device support in network management systems

• US 10,476,755 B1
• Filed: 12/06/2018
• Issued: 11/12/2019
• Est. Priority Date: 09/30/2016
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: A, Chandrasekhar, Anburose, Nirmal
• Primary Examiner(s): Pollack, Melvin H
• Application Number:
  US16/212,150
• Time in Patent Office: 341 Days
• Field of Search: 709223
• CPC Class Codes: H04L 41/022 Multivendor or multi-standard integration
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 43/045 for graphical visualisation of monitoring data
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

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.

Claims

1. A method comprising:

receiving, by a network management device, service configuration information for a particular network service, the service configuration information including a mapping from a service model for the particular network service to a vendor neutral model;

determining, by the network management device and based on the mapping from the service model to the vendor neutral model, a subset of the plurality of nodes included in the vendor neutral model as a set of source nodes;

for each node in the set of source nodes, generating, by the network management device and based on a target device specific model for a target network device, a mapping of nodes of the vendor neutral model to nodes of the target device specific model, the mapping to include at least one source node and an associated target node, wherein the target device does not currently support the particular network service; and

configuring, by the network management device and using the mapping, the target network device to support the particular network service.

2. The method of claim 1, wherein configuring the target network device to support the particular network service comprises:

generating, by the network management device and based on the mapping, an updated device specific configuration file; and

configuring, by the network management device and using the updated device specific configuration file, the target network device such that the configured target network device supports the particular network service.

3. The method of claim 1, further comprising:

modifying, by the network management device, the vendor neutral model to include one or more nodes required to support the particular network service.

4. The method of claim 1, further comprising:

prior to generating the mapping, determining, by the network management device, a respective similarity score for each unique source node and target node pair, the respective similarity score indicating an amount of similarity between the source node and the target node of the corresponding source node and target node pair,

wherein generating the mapping is further based on the respective similarity scores for the source node and target node pairs.

5. The method of claim 4, wherein determining the respective similarity score for each unique source node and target node pair comprises:

determining, by the network management device, a respective similarity score for each ancestor of the target node; and

determining, by the network management device and based on a combination of the respective similarity scores for the one or more ancestors of the target node and the respective similarity score for the target node, the respective similarity score for the source node and target node pair.

6. The method of claim 4, wherein generating the mapping comprises:

generating a similarity matrix including the respective similarity scores for the source node and target node pairs;

for each source node, determining, based on the similarity matrix, a respective source node and target node pair having a maximum similarity score; and

generating, by the management device, the mapping to include, for each source node, the source node and target node pairs having the maximum similarity scores.

7. The method of claim 6, further comprising:

determining whether the maximum similarity score for each source node from the set of source nodes satisfies a threshold similarity score; and

if the maximum similarity score for a particular source node does not satisfy the threshold similarity score, marking the mapping from the particular source node to the target node as being error prone.

8. The method of claim 6, further comprising:

outputting, by the network management device, a graphical indication of the mapping of the one or more nodes of the vendor neutral model to the one or more nodes of the target device specific model;

receiving, by the network management device, an indication of a user input to modify at least one source node and associated target node mapping; and

updating, by the network device and based on the indication of the user input, the mapping.

9. The method of claim 1, further comprising:

determining, by the management device, a respective module similarity score for each module of a plurality of modules of the target device specific model for the target network device, wherein each module from the plurality of modules includes a respective set of nodes from the plurality of nodes included in the target device specific model;

selecting, by the management device, a particular module from the plurality of modules having a highest value of the respective module similarity scores; and

for each unique source node and target node pair for the respective set of nodes included in the particular module;

determining, by the network management device, a type similarity score for a data type of the source node and a data type of the target node;

determining, by the network management device, a name distance similarity score of a name of the source node and a name of the target node;

determining, by the network management device, a structural similarity score; and

determining, by the network management device and based on a combination of the type similarity score, the name distance similarity score, and the structural similarity score, a respective similarity score for the corresponding unique source node and target node pair,

wherein generating the mapping is further based on the respective similar scores for the source node and target node pairs.

10. The method of claim 9, wherein determining the type similarity score comprises:

determining, by the network management device, a metadata type similarity score for metadata associated with the source node and metadata associated with the target node;

determining, by the network management device, a data type similarity score for an expressed type of the source node and an expressed type of the target node; and

determining, by the management device and based on a combination of the metadata type similarity score and the data type similarity score, the type similarity score.

11. The method of claim 9, wherein the respective similarity score for the corresponding unique source node and target node pair is a first respective similarity score for the corresponding unique source node and target node pair, and wherein determining the respective similarity score for each unique source node and target node pair further comprises, responsive to determining that the first respective similarity score for the corresponding unique source node and target node pair does not satisfy a first threshold similarity score:

determining, by the network management device, a name similarity score for a name of the source node and a name of the target node; and

determining, by the network management device and based on a combination of the first respective similarity score for the corresponding unique source node and target node pair and the name similarity score, a second respective similarity score.

12. The method of claim 11, wherein determining the respective similarity score for each unique source node and target node pair further comprises, in response to determining that the second respective similarity score for the corresponding unique source node and target node pair does not satisfy a threshold second similarity score:

determining, by the network management device, a description similarity score for a description of the source node and a description of the target node; and

determining, by the network management device and based on a combination of the second respective similarity score for the corresponding unique source node and target node pair and the description similarity score, a third respective similarity score for the source node and target node pair.

13. A network management system comprising:

an interface configured to receive service configuration information for a particular network service and a target device specific configuration file, the service configuration information including a mapping from a service model for the particular network service to a vendor neutral model;

one or more network interfaces communicatively coupled to a plurality of network devices, wherein the target network device is one of the plurality of network devices; and

one or more hardware-based processors, implemented using discrete logic circuitry, configured to;

determine, based on the mapping from the service model to the vendor neutral model, a subset of the plurality of nodes included in the vendor neutral model as a set of source nodes;

for each node in the set of source nodes, generate, based on a target device specific model for a target network device, a mapping of nodes of the vendor neutral model to nodes of the target device specific model, the mapping to include at least one source node and an associated target node, wherein the target device does not currently support the particular network service;

configure, using the mapping, the target network device to support the particular network service.

14. The network management system of claim 13, wherein, to configure the target network device to support the particular network service, the one or more processors are configured to:

generate, based on the mapping, an updated device specific configuration file; and

configure, using the updated device specific configuration file, the target network device such that the configured target network device supports the particular network service.

15. The network management system of claim 13, wherein the one or more processors are further configured to:

modify the vendor neutral model to include one or more nodes required to support the particular network service.

16. The network management system of claim 13, wherein the one or more processors are further configured to:

determine a respective module similarity score for each module of a plurality of modules of the target device specific model for the target network device, wherein each module from the plurality of modules includes a respective set of nodes from the plurality of nodes included in the target device specific model;

select a particular module from the plurality of modules having a highest value of the respective module similarity scores;

for each unique source node and target node pair for the respective set of nodes included in the particular module;

determine a type similarity score for a data type of the source node and a data type of the target node;

determine a name distance similarity score of a name of the source node and a name of the target node;

determine a structural similarity score; and

determine, based on a combination of the type similarity score, the name distance similarity score, and the structural similarity score, a respective similarity score for the corresponding unique source node and target node pair; and

generate the mapping further based on the respective similar scores for the source node and target node pairs.

17. The network management system of claim 13, wherein the one or more processors are further configured to:

prior to generating the mapping, determine a respective similarity score for each unique source node and target node pair, the respective similarity score indicating an amount of similarity between the source node and the target node of the corresponding source node and target node pair; and

generate the mapping further based on the respective similarity scores for the source node and target node pairs.

18. The network management system of claim 17, wherein the one or more processors are further configured to:

determine the respective similarity score for each unique source node and target node pair by at least being configured to;

determine a respective similarity score for each ancestor of the target node; and

determine, based on a combination of the respective similarity scores for the one or more ancestors of the target node and the respective similarity score for the target node, the respective similarity score for the source node and target node pair; and

generate the mapping by at least being configured to;

generate a similarity matrix including the respective similarity scores for the source node and target node pairs;

for each source node, determine, based on the similarity matrix, a respective source node and target node pair having a maximum similarity score;

generate the mapping to include, for each source node, the source node and target node pairs having the maximum similarity scores.

19. A computer-readable storage medium comprising instructions that, when executed, cause a processor of a network management system to:

receive service configuration information for a particular network service, the service configuration information including a mapping from a service model for the particular network service to a vendor neutral model;

determine, based on the mapping from the service model to the vendor neutral model, a subset of the plurality of nodes included in the vendor neutral model as a set of source nodes;

for each node in the set of source nodes, generate, based on a target device specific model for a target network device, a mapping of nodes of the vendor neutral model to nodes of the target device specific model, the mapping to include at least one source node and an associated target node, wherein the target device does not currently support the particular network service; and

configure, using the mapping, the target network device to support the particular network service.