Method for determining route flapping information and related device

Abstract

Embodiments of this application provide a method for determining route flapping information, to determine route flapping information based on parameter information reported by a routing device. The method in the embodiments of this application includes the following steps: receiving parameter information sent by each of at least one routing device, where parameter information sent by any routing device includes at least one of protocol packet information, count information, and identity identification information of the any routing device; and determining route flapping information of a target routing device based on the parameter information sent by each of the at least one routing device, where the target routing device is one of the at least one routing device.

What is claimed is: 
     
       1. An information obtaining device, comprising:
 a transceiver; 
 a memory storing instructions; and 
 a processor, 
 wherein the transceiver is configured to receive parameter information sent by each of at least one routing device, wherein parameter information sent by any routing device in the at least one routing device comprises protocol packet information, count information, and identity identification information of the any routing device, and wherein the protocol packet information, the count information, and the identity identification information are sent at respectively different reporting frequencies; and 
 wherein the processor is configured to execute the instructions to cause the information obtaining device to 
 determine route flapping information of a target routing device based on some or all of the parameter information sent by each of the at least one routing device, wherein the target routing device is one of the at least one routing device, 
 wherein the count information comprises count data of received hello packets of a neighboring routing device; and 
 wherein the processor is further configured to execute the instructions to cause the information obtaining device to: 
 receive the count data of received hello packets from a third routing device, wherein the count data comprises a number of hello packets received by the third routing device in a time interval, and wherein the at least one routing device comprises the third routing device; 
 determine, based on the count data of received hello packets from the third routing device and that is less than a preset value, that a flapping cause is neighbor flapping; and 
 determine that a flapping source is the third routing device, the neighboring routing device of the third routing device, or a link between the third routing device and the neighboring routing device of the third routing device. 
 
     
     
       2. The information obtaining device according to  claim 1 , wherein the transceiver is further configured to
 receive, over a network monitoring protocol, the parameter information sent by each of the at least one routing device, wherein the network monitoring protocol is a monitoring protocol of an interior gateway protocol (IGP). 
 
     
     
       3. The information obtaining device according to  claim 1 , wherein the transceiver is further configured to
 receive, over an extended monitoring protocol of a border gateway protocol (BMP), the parameter information sent by each of the at least one routing device, wherein the BMP protocol is a monitoring protocol of a border gateway protocol (BGP). 
 
     
     
       4. The information obtaining unit according to  claim 1 , wherein the transceiver is further configured to
 receive, over a Netconf protocol or an open source remote procedure call gRPC protocol, a YANG model sent by each of the at least one routing device, wherein the parameter information is encapsulated in the YANG model. 
 
     
     
       5. The information obtaining device according to  claim 1 , wherein the processor is further configured to execute the instructions to cause the information obtaining device to:
 determine that a flapping cause is a conflict of the identity identification information of the routing devices when the identity identification information of at least two first routing devices is the same, wherein the at least one routing device comprises the at least two first routing devices; and 
 determine that a flapping source is the at least two first routing devices. 
 
     
     
       6. The information obtaining device according to  claim 1 , wherein the count information comprises a quantity of interface flipping times of the routing device; and
 wherein the processor is further configured to execute the instructions to cause the information obtaining device to: 
 determine that a flapping cause is that the quantity of interface flipping times of the routing device is abnormal when a quantity of interface flipping times of a second routing device is within a preset quantity range of times, wherein the at least one routing device comprises the second routing device; and 
 determine that a flapping source is the second routing device. 
 
     
     
       7. The information obtaining device according to  claim 1 , wherein the count information comprises count data of link state packet (LSP) purge packets of the routing device; and
 wherein the processor is further configured to execute the instructions to cause the information obtaining device to: 
 determine, based on count data that is within a preset data range and that is of LSP purge packets sent by a fourth routing device, that a flapping cause is that the LSP purge packets of the routing device are abnormal, wherein the at least one routing device comprises the fourth routing device; and 
 determine that a flapping source is the fourth routing device or a neighboring routing device of the fourth routing device. 
 
     
     
       8. The information obtaining device according to  claim 1 , wherein the processor is further configured to execute the instructions to cause the information obtaining device to:
 determine a target parameter in the parameter information sent by each of the at least one routing device, wherein the target parameter is an earliest abnormal parameter; and 
 determine that a flapping source is a routing device corresponding to the target parameter. 
 
     
     
       9. A method for determining route flapping information, comprising:
 sending, by a routing device, parameter information to an information obtaining device, wherein the parameter information sent by the routing device comprises protocol packet information, count information, and identity identification information of the routing device, wherein the protocol packet information, the count information, and the identity identification information are sent at respectively different reporting frequencies, and some or all of the parameter information sent by the routing device is used by the information obtaining device to determine route flapping information of the routing device, 
 wherein the count information comprises count data of received hello packets of a neighboring routing device; and 
 wherein the processor is further configured to execute the instructions to cause the information obtaining device to: 
 receive the count data of received hello packets from a third routing device, wherein the count data comprises a number of hello packets received by the third routing device in the second time interval, and wherein the at least one routing, device comprises the third muting device; 
 determine, based on the count data, of received hello packets from the third routing device and that is less than a preset value, that a flapping cause is neighbor flapping; 
 and determine that a flapping source is the third routing device, the neighboring routing device of the third routing device, or a link between the third routing device and the neighboring routing device of the third routing device. 
 
     
     
       10. The method according to  claim 9 , wherein the sending, by a routing device, parameter information to an information obtaining device comprises
 sending, by the routing device, the parameter information to the information obtaining device over a network monitoring protocol, wherein the network monitoring protocol is a monitoring protocol of an interior gateway protocol (IGP). 
 
     
     
       11. The method according to  claim 9 , wherein the sending, by a routing device, parameter information to an information obtaining device comprises
 sending, by the routing device, the parameter information to the information obtaining device over an extended monitoring protocol of a border gateway protocol (BMP), wherein the BMP protocol is a monitoring protocol of a border gateway protocol (BGP). 
 
     
     
       12. The method according to  claim 9 , wherein the sending, by a routing device, parameter information to an information obtaining device comprises
 sending, by the routing device, a YANG model to the information obtaining device over a Netconf protocol or an open source remote procedure call gRPC protocol, wherein the parameter information is encapsulated in the YANG model. 
 
     
     
       13. A routing device, comprising:
 a transceiver; 
 a memory storing instructions; and 
 a processor, 
 wherein the transceiver is configured to send parameter information to an information obtaining device, wherein the parameter information sent by the routing device comprises protocol packet information, count information, and identity identification information of the routing device, wherein the protocol packet information, the count information, and the identity identification information are sent at respectively different reporting frequencies, and some or all of the parameter information sent by the routing device is used by the information obtaining device to determine route flapping information of the routing device, 
 wherein the count information comprises count data of received hello packets of a neighboring routing device; and 
 wherein the processor is further configured to execute the instructions to cause the information obtaining device to: 
 receive the count data of received hello packets from a third routing device, wherein the count data comprises a number of hello packets received by the third routing device in a time interval, and wherein the at least one routing device comprises the third routing device; 
 determine, based on the count data of received hello packets from the third routing device and that is less than a preset value, that a flapping cause is neighbor flapping; and 
 determine that a flapping source is the third routing device, the neighboring routing device of the third routing device, or a link between the third routing device and the neighboring routing device of the third routing device. 
 
     
     
       14. The routing device according to  claim 13 , wherein the transceiver is further configured to send the parameter information to the information obtaining device over a network monitoring protocol, wherein the network monitoring protocol is a monitoring protocol of an interior gateway protocol (IGP). 
     
     
       15. The routing device according to  claim 13 , wherein the transceiver is further configured to send the parameter information to the information obtaining device over an extended monitoring protocol of a border gateway protocol (BMP), wherein the BMP protocol is a monitoring protocol of a border gateway protocol (BGP). 
     
     
       16. The routing device according to  claim 13 , wherein the transceiver is further configured to send a YANG model to the information obtaining device over a Netconf protocol or an open source remote procedure call gRPC protocol, wherein the parameter information is encapsulated in the YANG model. 
     
     
       17. An information obtaining device, comprising:
 a transceiver; 
 a memory storing instructions; and 
 a processor, 
 wherein the transceiver is configured to receive parameter information sent by each of at least one routing device, wherein parameter information sent by any routing device in the at least one routing device comprises protocol packet information, count information, and identity identification information of the any routing device, and wherein the protocol packet information, the count information, and the identity identification information are sent at respectively different reporting frequencies; and 
 wherein the processor is configured to execute the instructions to cause the information obtaining device to 
 determine route flapping information of a target routing device based on some or all of the parameter information sent by each of the at least one routing device, wherein the target routing device is one of the at least one routing device, 
 wherein the count information, includes respective counts of routing protocol packets received by the target routing device from a neighbor routing device for each of one or more types of routing protocol packet types, respective counts of routing protocol packets received by the neighbor routing device from the target routing device for each of the one or more types of routing protocol packet types, a quantity of interface flipping times of the target routing device, a quantity of interface flipping times of the neighbor routing device, and respective counts of routing protocol packets received by the target routing device from a second neighbor routing device for each of the one or more types of routing protocol packet types; and 
 wherein the processor is further configured to execute the instructions to cause the information obtaining device to 
 determine a flapping source and a flapping cause of a route flapping associated with the target routing device based on the respective counts of routing protocol packets received by the target routing device from a neighbor routing device, the respective counts of routing protocol packets received by the neighbor routing device from the target routing device, the quantity of interface flipping times of the target routing device, the quantity of interface flipping times of the neighbor routing device, and the respective counts of routing protocol packets received by the target routing device from a second neighbor routing device for each of the one or more types of routing protocol packet types.