Automated network entity replacement based on historical topology consciousness

• US 10,425,281 B2
• Filed: 11/10/2017
• Issued: 09/24/2019
• Est. Priority Date: 11/10/2017
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Grevers, Jr., Theodore Robert, Kannan, Raja Rajaram, Klecka, III, Rudolph B., Morris, Gregory Faison
• Primary Examiner(s): Lopata, Robert J
• Application Number:
  US15/808,984
• Publication Number:
  US 20190149416A1
• Time in Patent Office: 683 Days
• Field of Search: 370254
• CPC Class Codes: H04L 41/065 involving logical or physical relationship, e.g. grouping and hierarchies
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0873 Checking configuration conflicts between network elements
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: Y02D 30/00 Reducing energy consumption in communication networks

Abstract

In one embodiment, a device in a network maintains a topology database of one or more topologies of entities in the network. The device identifies a replacement entity that has physically replaced a particular one of the entities in the network. The device determines whether neighbor information regarding one or more of the entities that neighbor the replacement entity matches neighbor information in the topology database associated with the replaced entity. The device determines whether client information regarding one of more clients of the replacement entity matches client information in the topology database associated with the replaced entity. The device sends an alert when the neighbor or client information of the replacement entity does not match the neighbor or client information in the topology database associated with the replaced entity.

Claims

1. A method comprising:

maintaining, by a device in a network, a topology database of one or more topologies of entities in the network;

identifying, by the device, a replacement entity that has physically replaced a particular one of the entities in the network;

determining, by the device, whether neighbor information regarding one or more of the entities that neighbor the replacement entity matches neighbor information in the topology database associated with the replaced entity;

determining, by the device, whether client information regarding one of more clients of the replacement entity matches client information in the topology database associated with the replaced entity; and

sending, by the device, an alert when the neighbor or client information of the replacement entity does not match the neighbor or client information in the topology database associated with the replaced entity.

2. The method as in claim 1, further comprising:

receiving, at the device and from the replacement entity, the neighbor information regarding the one or more of the entities that neighbor the replacement entity, wherein the replacement entity uses a Link Layer Discovery Protocol (LLDP) exchange to generate the neighbor information.

3. The method as in claim 1, wherein the entities are network switches.

4. The method as in claim 3, wherein determining whether the neighbor information regarding the one or more of the entities that neighbor the replacement entity matches the neighbor information in the topology database associated with the replaced entity comprises:

determining, by the device, whether port information for the replacement entity matches port information for the replaced entity.

5. The method as in claim 3, wherein determining whether the neighbor information regarding the one or more of the entities that neighbor the replacement entity matches the neighbor information in the topology database associated with the replaced entity comprises:

determining, by the device, whether port information for the replacement entity matches port information for a network entity that the replaced entity previously replaced.

6. The method as in claim 1, further comprising:

maintaining, by the device, a configuration database of configurations of the network entities; and

sending, by the device, a configuration to the replacement entity that is associated with the replaced entity in the configuration database.

7. The method as in claim 6, wherein sending the configuration to the replacement entity comprises:

causing, by the device, firmware of the replacement entity to be downgraded.

8. The method as in claim 1, further comprising:

receiving, at the device, a selection of one of the network topologies from the topology database; and

sending, by the device, control commands to the entities in the network to implement the selected topology.

9. The method as in claim 1, further comprising:

validating, by the device, a network design against the network, using the topology database.

10. An apparatus comprising:

one or more network interfaces to communicate with a network;

a processor coupled to the network interfaces and configured to execute one or more processes; and

a memory configured to store a process executable by the processor, the process when executed configured to;

maintain a topology database of one or more topologies of entities in the network;

identify a replacement entity that has physically replaced a particular one of the entities in the network;

determine whether neighbor information regarding one or more of the entities that neighbor the replacement entity matches neighbor information in the topology database associated with the replaced entity;

determine whether client information regarding one of more clients of the replacement entity matches client information in the topology database associated with the replaced entity; and

send an alert when the neighbor or client information of the replacement entity does not match the neighbor or client information in the topology database associated with the replaced entity.

11. The apparatus as in claim 10, wherein the process when executed is further configured to:

receive, from the replacement entity, the neighbor information regarding the one or more of the entities that neighbor the replacement entity, wherein the replacement entity uses a Link Layer Discovery Protocol (LLDP) exchange to generate the neighbor information.

12. The apparatus as in claim 10, wherein the entities are network switches.

13. The apparatus as in claim 12, wherein the apparatus determines whether the neighbor information regarding the one or more of the entities that neighbor the replacement entity matches the neighbor information in the topology database associated with the replaced entity by:

determining whether port information for the replacement entity matches port information for the replaced entity.

14. The apparatus as in claim 12, wherein the apparatus determines whether the neighbor information regarding the one or more of the entities that neighbor the replacement entity matches the neighbor information in the topology database associated with the replaced entity by:

determining whether port information for the replacement entity matches port information for a network entity that the replaced entity previously replaced.

15. The apparatus as in claim 10, wherein the process when executed is further configured to:

maintain a configuration database of configurations of the network entities; and

send a configuration to the replacement entity that is associated with the replaced entity in the configuration database.

16. The apparatus as in claim 15, wherein the apparatus sends the configuration to the replacement entity by:

causing firmware of the replacement entity to be downgraded.

17. The apparatus as in claim 10, wherein the process when executed is further configured to:

receive a selection of one of the network topologies from the topology database; and

send control commands to the entities in the network to implement the selected topology.

18. The apparatus as in claim 10, wherein the process when executed is further configured to:

validate a network design against the network, using the topology database.

19. The apparatus as in claim 10, wherein the network is an industrial network.

20. A tangible, non-transitory, computer-readable medium storing program instructions that cause a device in a network to execute a process comprising:

maintaining, by the device, a topology database of one or more topologies of entities in the network;

identifying, by the device, a replacement entity that has physically replaced a particular one of the entities in the network;

determining, by the device, whether neighbor information regarding one or more of the entities that neighbor the replacement entity matches neighbor information in the topology database associated with the replaced entity;

determining, by the device, whether client information regarding one of more clients of the replacement entity matches client information in the topology database associated with the replaced entity; and

sending, by the device, an alert when the neighbor or client information of the replacement entity does not match the neighbor or client information in the topology database associated with the replaced entity.