Network event locus descriptor
View Patent ↗That each switch is configured with a series of new commands, such as NELD, which include various parameters, the parameters matching predefined terms, such as STP, BGP or DROP, and specifying a particular port or interface, if relevant. By predefining the parameters, the switch is configured to obtain data relevant to a particular problem. When a problem occurs, the administrator sends the command to all relevant switches with a parameter relevant to the problem being analyzed. Preferably, this sending of the command is done using a management application, so that the command can be sent to each switch by the management application in an extremely short period. By capturing all of the data in a small window, the odds are greatly improved on obtaining the relevant data. By having the preprogrammed commands, all of the desired data can be obtained in a single command rather than a series of commands.
1. A method, comprising:
configuring a plurality of network devices with a data collection command with a network event locus descriptor (NELD) command, the NELD command specifying an event of a network formed at least in part by the plurality of network devices, and the data collection command having a plurality of pre-configured switch commands to be executed in the collection of data for the NELD command;
transmitting, after occurrence of the event from a network management device, a responsive data collection command to each of a relevant subset of the plurality of network devices, the responsive data collection command including the NELD command;
receiving, from each of the subset of the plurality of network devices, data of the plurality of pre-configured switch commands of the command in response to the responsive data collection command;
combining the data to produce an analysis data set for the network event;
forming, using the analysis data set, a NELD object; and
drawing a topology of the network by utilizing the NELD object.
2. The method of claim 1 , further comprising forming a YANG model of the network from the analysis data set.
3. The method of claim 2 , further comprising developing the topology of the network from the YANG model.
4. The method of claim 2 , further comprising:
transmitting a configuration command to each of the subset of the network devices, the configuration command requesting topology-related data from each network device, and the configuration commands being transmitted in association with the data collection commands; and
receiving, from each of the subset of the plurality of network devices, the configuration information responsive to the configuration command, wherein
data items for a data collection command do not provide sufficient topology-related data to develop a complete topology.
5. The method of claim 4 , further comprising developing the topology of the network from the received configuration information.
6. The method of claim 2 , further comprising configuring the network to conform to the YANG model.
7. The method of claim 6 , wherein the network is a physical network.
8. The method of claim 2 , further comprising developing a virtual network to conform to the YANG model.
9. The method of claim 2 , wherein the YANG model is analyzed by analytics software.
10. The method of claim 1 , wherein the data includes data items that relate to a physical element of at least a network device of the subset of the plurality of network devices.
11. The method of claim 1 , wherein the data includes data items that are on a virtual element representing at least a network device of the subset of the plurality of network devices.
12. The method of claim 1 , wherein the relevant subset of the plurality of network devices is determined by selection of a user.
13. The method of claim 1 , wherein the relevant subset of the plurality of network devices is within a number of hops from a given network device.
14. The method of claim 1 , further comprising utilizing the topology to troubleshoot the network.
15. The method of claim 1 , further comprising:
detecting a problem within the network; and
selecting the subset of the plurality of network devices based on the problem within the network.
16. The method of claim 15 , further comprising utilizing the topology to troubleshoot the problem within the network.
17. A diagnostic device, comprising:
a processor; and
a memory coupled to said processor for storing programs executed by said processor, wherein
the processor is configured to:
configure a plurality of network devices with a data collection command with a network event locus descriptor (NELD) command, the NELD command specifying an event of the network, and the data collection command including a plurality of pre-configured switch commands to be executed in the collection of data for the NELD command,
transmit, after occurrence of the event from a network management device, a responsive data collection command to each of a relevant subset of the plurality of network devices, the responsive data collection command including the NELD command,
receive, from each of the subset of the plurality of network devices, data of the plurality of pre-configured switch commands of the command in response to the responsive data collection command,
combine the data to produce an analysis data set for the network event,
form, using the analysis data set, a NELD object, and
draw a topology of the network by utilizing the NELD object.
18. The diagnostic device of claim 17 , wherein the processor is further configured to utilize the topology to troubleshoot the network.
19. The diagnostic device of claim 17 , wherein the processor is further configured to:
detect a problem within the network; and
select the subset of the plurality of network devices based on the problem within the network.
20. The diagnostic device of claim 19 , wherein the processor is further configured to utilize the topology to troubleshoot the problem within the network.