STATIC ENDPOINT VALIDATION

• US 20180367429A1
• Filed: 07/28/2017
• Published: 12/20/2018
• Est. Priority Date: 06/19/2017
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Pani, Ayas, Harneja, Sanchay, Holankar, Manali, Subramanya, Vikram
• Granted Patent: US 10,560,355 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 12/6418 Hybrid transport
• CPC Class Codes: H04L 41/044 comprising hierarchical management structures
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 41/08 Configuration management of networks or network elements address allocation H04L61/50
• CPC Class Codes: H04L 41/0866 Checking the configuration
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network
• CPC Class Codes: H04L 41/344 Out-of-band transfers
• CPC Class Codes: H04L 41/50 Network service management, e.g. ensuring proper service fulfilment according to agreements
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/12 Network monitoring probes
• CPC Class Codes: H04L 45/28 using route fault recovery

Abstract

Systems, methods, and computer-readable media are disclosed for validating endpoint information for nodes in a network. A network assurance appliance is configured to retrieve a configured static endpoint information in a logical model of a network from a network controller and connected static endpoint information from one or more nodes in the network. The network assurance appliance determines that there is an inconsistency based on a comparison of the configured static endpoint information and the connected static endpoint information and generating an event specifying the inconsistency.

Claims

1. A computer-implemented method comprising:

querying a network controller to identify a configured static endpoint in a logical model of a network;

retrieving, from one or more nodes in the network, endpoint information for a set of connected endpoints in the network;

determining that the endpoint information does not include the configured static endpoint in the set of connected endpoints; and

identifying a first static endpoint inconsistency between the logical model and the endpoint information based on the endpoint information not including the configured static endpoint in the set of connected endpoints.

2. The computer-implemented method of claim 1, further comprising generating an event specifying the first static endpoint inconsistency.

3. The computer-implemented method of claim 2, wherein the event is associated with a severity level and an event type, and wherein the event type specifies the first static endpoint inconsistency.

4. The computer-implemented method of claim 1, further comprising providing, based on the first static endpoint inconsistency, a user interface comprising network status information.

5. The computer-implemented method of claim 4, further comprising:

calculating, based on the first static endpoint inconsistency, a health score for one or more endpoints in the network,

wherein the network status information comprises the health score for the one or more endpoints.

6. The computer-implemented method of claim 1, wherein the one or more nodes in the network includes at least one of a leaf node or a spine node.

7. The computer-implemented method of claim 1, further comprising:

determining, when the endpoint information includes the configured static endpoint in the set of connected endpoints, that a static flag in the endpoint information is not set for the configured static endpoint; and

identifying a flag inconsistency based on the static flag in the endpoint information not being set for the configured static endpoint.

8. The computer-implemented method of claim 1, wherein the network is a software-defined network (SDN).

9. The computer-implemented method of claim 1, further comprising:

determining that the set of connected endpoints includes a static endpoint that is not found in the logical model; and

identifying a second static endpoint inconsistency based on the set of connected endpoints including the static endpoint that is not found in the logical model.

10. A system comprising:

one or more processors; and

at least one computer-readable storage medium having stored therein instructions which, when executed by the one or more processors, cause the system to;

retrieve endpoint information from one or more nodes in the network;

identify a connected static endpoint in the endpoint information based on a static flag for the connected static endpoint being set;

query a network controller to make a determination that the connected static endpoint does not have a corresponding static endpoint in the logical model of the network; and

identify a first static endpoint inconsistency based on the determination.

11. The system of claim 10, wherein the instructions further cause the system to:

query the network controller to identify a configured static endpoint in the logical model of a network;

determining that the endpoint information does not include the configured static endpoint; and

identifying a second static endpoint inconsistency between the logical model and the endpoint information based on the endpoint information not including the configured static endpoint.

12. The system of claim 10, wherein the instructions further cause the system to generate an event specifying the first static endpoint inconsistency.

13. The system of claim 12, wherein the event is associated with a severity level and an event type, and wherein the event type specifies the first static endpoint inconsistency.

14. The system of claim 10, wherein the instructions further cause the system to provide, based on the first static endpoint inconsistency, a user interface comprising network status information.

15. The system of claim 14, wherein the instructions further cause the system to:

calculate, based on the first static endpoint inconsistency, a health score for one or more endpoints in the network,

wherein the network status information comprises the health score for the one or more endpoints.

16. A non-transitory computer-readable medium comprising instructions stored therein which, when executed by one or more processors, cause the one or more processors to:

retrieving, from a network controller, a configured static endpoint information in a logical model of a network;

retrieve, from one or more nodes in the network, connected static endpoint information;

determining that there is an inconsistency based on a comparison of the configured static endpoint information and the connected static endpoint information; and

generating an event specifying the inconsistency.

17. The non-transitory computer-readable medium of claim 16, wherein the instructions further cause the one or more processors to provide, based on the event, a user interface comprising network status information.

18. The non-transitory computer-readable medium of claim 17, wherein the instructions further cause the one or more processors to:

calculate, based on the event, a health score for one or more endpoints in the network,

wherein the network status information comprises the health score for the one or more endpoints.

19. The non-transitory computer-readable medium of claim 16, wherein the configured static endpoint information includes a configured static endpoint, and wherein the instructions further cause the one or more processors to:

determine that the connected static endpoint information does not include an entry corresponding to the configured static endpoint.

20. The non-transitory computer-readable medium of claim 16, wherein the connected static endpoint information includes a connected static endpoint, and wherein the instructions further cause the one or more processors to:

determine that the configured static endpoint information does not include an entry corresponding to the connected static endpoint.