Detecting miswirings in a spine and leaf topology of network devices
A network device may receive topology data identifying a spine and leaf topology of network devices, and may set link metrics to a common value to generate modified topology data. The network device may remove data identifying connections from leaf network devices to any devices outside the topology from the modified topology data to generate further modified topology data, and may process the further modified topology data, with a model, to determine path data identifying paths to destinations. The network device may determine particular path data identifying shorter paths and longer paths to corresponding destinations, and may determine hop counts associated with the paths. The network device may determine whether the hop counts are all odd values, all even values, or odd and even values, and may perform actions based on whether the hop counts are all odd values, all even values, or odd and even values.
1. A method, comprising:
processing, by a network device, topology data associated with the network device, with a shortest path first model, to determine path data identifying paths to destinations identified in the topology data;
processing, by the network device, the topology data, with the shortest path first model, to determine hop counts associated with shorter paths and longer paths to corresponding destinations;
comparing, by the network device, the hop counts of different possible paths to reach a particular destination, of the corresponding destinations, to determine whether the hop counts from the different possible paths are all odd values, all even values, or a combination of odd and even values; and
performing, by the network device, one or more actions based on determining whether the hop counts associated with the shorter paths and the longer paths to the corresponding destinations are all odd values, all even values, or a combination of odd and even values,
wherein performing the one or more actions comprises: performing a first action when the hop counts associated with the different possible paths to the particular destination are determined to be all odd values or all even values, and
performing a second action when the hop counts associated with the different possible paths to the particular destination are determined to be a combination of odd values and even values.
2. The method of claim 1 , wherein performing the one or more actions comprises:
determining there are not miswirings in the topology data of network devices when the hop counts associated with the shorter paths and the longer paths to corresponding destinations are determined to be all odd values or all even values.
3. The method of claim 1 , wherein performing the one or more actions comprises one or more of:
providing data identifying a miswiring in the topology data of network devices in a log file when the miswiring is identified based on determining whether the hop counts associated with the shorter paths and the longer paths to corresponding destinations are all odd values, all even values, or a combination of odd and even values.
4. The method of claim 1 , further comprising:
discarding the longer paths to corresponding destinations; and
generating shortest path topology data identifying the shorter paths to corresponding destinations.
5. The method of claim 1 , further comprising:
identifying a cost associated with traffic being transmitted from the network device to another network device connected to the network device via a spine and leaf topology.
6. The method of claim 1 , further comprising:
storing all paths with costs that satisfy a threshold in the shortest path topology data.
7. The method of claim 1 , wherein performing the one or more actions comprises:
performing one or more tests on the topology data when a miswiring is identified based on determining whether the hop counts associated with the different possible paths to corresponding destinations are all odd values, all even values, or a combination of odd and even values.
8. A network device, comprising:
one or more memories; and
one or more processors to:
determine, with a shortest path first model, path data identifying paths to destinations identified in topology data;
process the path data and the topology data, with the shortest path first model, to determine hop counts associated with different possible paths to corresponding destinations;
compare the hop counts of the different possible paths to reach a particular destination, of the corresponding destinations, to determine whether the hop counts from the different possible paths are all odd values, all even values, or a combination of odd and even values; and
perform one or more actions based on determining whether the hop counts associated with the shorter paths to the corresponding destinations are all odd values, all even values, or a combination of odd and even values,
wherein the one or more processors, to perform the one or more actions, are to: perform a first action when the hop counts associated with the different possible paths to the particular destination are determined to be all odd values or all even values, and
perform a second action when the hop counts associated with the different possible paths to the particular destination are determined to be a combination of odd values and even values.
9. The network device of claim 8 , wherein the one or more processors are to:
receive the topology data identifying a spine and leaf topology of network devices,
wherein the network device is included in the spine and leaf topology of network devices.
10. The network device of claim 8 , wherein the one or more processors, to compare the hop counts of the different possible paths to reach the particular destination, are to:
compare the hop counts of all possible paths to reach a particular destination, of the corresponding destinations, to determine whether the hop counts from the different possible paths are all odd values, all even values, or a combination of odd and even values.
11. The network device of claim 8 , wherein the one or more processors are further to:
identify a cost associated with traffic being transmitted from the network device to another network device connected to the network device.
12. The network device of claim 8 , wherein the one or more processors, to perform the one or more actions, are to:
provide an alert identifying miswiring to an endpoint device.
13. The network device of claim 8 , wherein the one or more processors, to perform the one or more actions, are to:
provide data identifying a miswiring in the topology data of network devices to a tool that determines physical locations of the miswiring when the miswiring is identified based on determining whether the hop counts associated with the different possible paths to corresponding destinations are all odd values, all even values, or a combination of odd and even values.
14. The network device of claim 8 , wherein the one or more processors, to perform the one or more actions, are to:
perform one or more tests on the topology data when a miswiring is identified based on determining whether the hop counts associated with the different possible paths to corresponding destinations are all odd values, all even values, or a combination of odd and even values.
15. A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors of a network device, cause the network device to:
determine, with a shortest path first model, path data identifying paths to destinations identified in topology data identifying a spine and leaf topology of network devices,
wherein the network device is included in the spine and leaf topology of network devices;
compare hop counts of different possible paths to reach a particular destination to determine whether the hop counts from the different possible paths are all odd values, all even values, or a combination of odd and even values; and
perform one or more actions based on determining whether the hop counts associated with the different possible paths to reach the particular destination are all odd values, all even values, or a combination of odd and even values,
wherein the one or more instructions, that cause the one or more processors to perform the one or more actions, cause the one or more processors to: perform a first action when the hop counts associated with the different possible paths to the particular destination are determined to be all odd values or all even values, and
perform a second action when the hop counts associated with the different possible paths to the particular destination are determined to be a combination of odd values and even values.
16. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the one or more processors to:
identify a cost associated with traffic being transmitted from the network device to another network device connected to the network device.
17. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the one or more processors to:
store one or more paths in a data structure.
18. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the one or more processors to:
store all paths with costs that satisfy a threshold in the shortest path topology data.
19. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the one or more processors to perform the second action, cause the one or more processors to:
automatically dispatch a robot or an autonomous vehicle to correct a miswiring.
20. The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions, that cause the one or more processors to perform the second action, cause the one or more processors to:
provide data identifying a miswiring to a tool that determines a physical location of the miswiring.