Methods and apparatus to track changes to a network topology
First Claim
1. A topology tool to track a change to a network topology, the topology tool comprising:
- a message processor to, in response to a reporting message generated by a software defined network controller, identify a unique identifier (UID) associated with a network element to be subject to a topology change event, the reporting message including topology change information corresponding to the topology change event scheduled to occur at a future time;
a database search tool to;
search a first topology database for a first post-confirmation data record corresponding to the UID;
in response to the first post-confirmation data record missing from the first topology database, search a second topology database for a first pre-confirmation data record corresponding to the UID;
a database controller to generate a second pre-confirmation data record in response to the first pre-confirmation data record missing from the second topology database; and
a message generator to generate a confirmation-seeking message to confirm occurrence of the topology change event after the first pre-confirmation data record is stored in the second topology database, the message generator to generate the confirmation-seeking message by sending a loopback address of the network element subject to the topology change event, a type of the topology change event, a status of the topology change event, and information indicating a position of the network element within the network topology.
1 Assignment
0 Petitions
Accused Products
Abstract
Methods and apparatus to track network topology changes are disclosed. An example topology tool to track a change to a network topology includes a message processor to, in response to a reporting message generated by a software defined network controller, identify a unique identifier (UID) associated with a network element to be subject to a topology change event, where the reporting message including topology change information corresponding to the topology change event scheduled to occur at a future time. A database search tool is to search a first topology database for a first post-confirmation data record corresponding to the UID and in response to the first post-confirmation data record missing from the first topology database, search a second topology database for a first pre-confirmation data record corresponding to the UID. A database controller is to generate a second pre-confirmation data record in response to the first pre-confirmation data record missing from the second topology database.
-
Citations
14 Claims
-
1. A topology tool to track a change to a network topology, the topology tool comprising:
-
a message processor to, in response to a reporting message generated by a software defined network controller, identify a unique identifier (UID) associated with a network element to be subject to a topology change event, the reporting message including topology change information corresponding to the topology change event scheduled to occur at a future time; a database search tool to; search a first topology database for a first post-confirmation data record corresponding to the UID; in response to the first post-confirmation data record missing from the first topology database, search a second topology database for a first pre-confirmation data record corresponding to the UID; a database controller to generate a second pre-confirmation data record in response to the first pre-confirmation data record missing from the second topology database; and a message generator to generate a confirmation-seeking message to confirm occurrence of the topology change event after the first pre-confirmation data record is stored in the second topology database, the message generator to generate the confirmation-seeking message by sending a loopback address of the network element subject to the topology change event, a type of the topology change event, a status of the topology change event, and information indicating a position of the network element within the network topology. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A tangible computer-readable medium comprising instructions that, when executed, cause a processor to at least:
-
identify, in response to a reporting message generated by a software defined network controller, a unique identifier (UID) associated with a network element to be subject to a topology change event, the reporting message including topology change information corresponding to the topology change event scheduled to occur at a future time; search a first topology database for a first post-confirmation data record corresponding to the UID; in response to the first post-confirmation data record missing from the first topology database, search a second topology database for a first pre-confirmation data record corresponding to the UID; generate a second pre-confirmation data record in response to the first pre-confirmation data record missing from the second topology database; and generate a confirmation-seeking message to confirm occurrence of the topology change event after the first pre-confirmation data record is stored in the second topology database by sending a loopback address of the network element subject to the topology change event, a type of the topology change event, a status of the topology change event, and information indicating a position of the network element within a network topology. - View Dependent Claims (7, 8, 9, 10)
-
-
11. A topology tool to track a change to a network topology, the tool comprising:
-
memory including instructions; and processor circuitry to execute the instructions to; identify, in response to a reporting message from a software defined network controller, a unique identifier (UID) associated with a network element to be subject to a topology change event, the reporting message to include topology change information corresponding to the topology change event scheduled to occur at a future time; search a first topology database for a first post-confirmation data record corresponding to the UID; search, in response to the first post-confirmation data record missing from the first topology database, a second topology database for a first pre-confirmation data record corresponding to the UID; generate a second pre-confirmation data record in response to the first pre-confirmation data record missing from the second topology database; and generate a confirmation-seeking message to confirm occurrence of the topology change event in response to the first pre-confirmation data record being present in the second topology database by sending a loopback address of the network element subject to the topology change event, a type of the topology change event, a status of the topology change event, and information indicative of a position of the network element within the network topology. - View Dependent Claims (12, 13, 14)
-
Specification