BGP Down fault positioning method and device

Abstract

The invention discloses a BGP Down fault positioning method and device, and the method comprises the steps: S01, loading network data, and detecting a BGP state; s02, logging in the home terminal equipment, and detecting the state of the home terminal equipment; and S03, logging in the opposite-end equipment, and detecting the state of the opposite-end equipment. According to the BGP Down fault positioning method and device, expert ability is attached, alarm information, a network protocol and a test command are combined, BGP Down fault diagnosis is automatically carried out, check result data are analyzed and processed in real time, timeliness is guaranteed, BGP Down faults are processed and analyzed in a flow mode, network operation and maintenance personnel are helped to rapidly position service faults, and the fault positioning efficiency of the BGP Down is improved. And the working pressure is reduced, the fault positioning process is standardized and automatic, the possibility of manual error checking and missing checking is reduced, the accuracy of fault diagnosis is improved, and the efficiency of fault positioning is improved.

Description

Technical Field

[0001] The present invention relates to the field of communications, and in particular to a BGP Down fault locating method and device. Background Art

[0002] BGP Border Gateway Protocol is a routing protocol widely used in IP networks, responsible for transmitting routing information between different autonomous systems. When a BGP Down failure occurs, the network will be interrupted, affecting data transmission and user experience. Because it is a protocol-level failure, fault location is complex. Operation and maintenance personnel need to spend a long time manually to determine and locate the fault, resulting in long-term lag and adverse effects on customers.

[0003] Operation and maintenance personnel need to use various protocols and commands to perform fault analysis based on their professional knowledge, and spend a long time manually determining the cause of the BGP Down fault. This is time-consuming and labor-intensive, and the timely fault handling rate is low, which puts a lot of pressure on maintenance personnel. Summary of the invention

[0004] In order to solve the problems existing in the prior art, the present invention provides a BGP Down fault locating method and device, which locates the cause of the BGP Down fault by collecting and analyzing alarms and protocol status of network elements with BGP Down faults, and initiating tests for the faulty network elements, thereby reducing the work pressure of network operation and maintenance personnel and improving operation and maintenance efficiency.

[0005] To achieve the above object, the present invention adopts the following technical solutions:

[0006] In one embodiment of the present invention, a BGP Down fault locating method is proposed, the method comprising:

[0007] S01. Select the service for grayscale release and configure the grayscale release task;

[0008] Further, the S01 includes:

[0009] S011. Select the service that needs to be released in grayscale, and then add a grayscale release task;

[0010] S012. Configure the grayscale release task;

[0011] Furthermore, the grayscale release task includes: task name, release time, task description, grayscale release strategy, rollback method and rollback conditions;

[0012] Furthermore, the grayscale release strategy includes: grayscale by proportion, grayscale by content, and grayscale by signature;

[0013] The proportional grayscale: flows traffic to services of different versions according to the traffic ratio;

[0014] Content-based grayscale: uses the content of the request as a matching condition to control the service version of the traffic flow;

[0015] Grayscale by signature: uses the signature in the traffic as the matching condition and is suitable for grayscale release for different users.

[0016] For example, before a new version goes online, testers are required to conduct online testing. You can configure signature grayscale to direct the testers' requests to the new version.

[0017] Furthermore, the rollback method includes: manual intervention and automatic rollback;

[0018] Manual intervention: During the grayscale release process, the operation and maintenance team monitors the system traffic in real time and decides whether to roll back based on the actual situation;

[0019] Automatic rollback: The API gateway automatically rolls back to the previous version according to the rollback conditions;

[0020] Furthermore, the rollback conditions include: error rate, response time, and thresholds can be customized for the indicators. Exceeding the thresholds can trigger automatic rollback;

[0021] S013. Configure the grayscale release plan and select the backend environment and version corresponding to the release plan;

[0022] Furthermore, the release plan includes immediate release and scheduled release;

[0023] Furthermore, the backend environment includes a test environment, a pre-release environment, and an online environment;

[0024] Furthermore, the version is: a service version released in grayscale, where the newly released service version is newer than the currently running version;

[0025] S02. The control plane of the API gateway updates the release strategy and monitors the release status of the grayscale release.

[0026] Further, the S02 includes:

[0027] S021. After the grayscale release starts, the grayscale release status changes to releasing, and the control plane of the API gateway can update the release strategy;

[0028] Furthermore, the creation of a grayscale release task includes but is not limited to one, and a grayscale release task can only have one status of "releasing".

[0029] In specific implementation, if this release is released in proportion, 20% of the traffic will be configured for the new version during the initial release, and 80% of the traffic will go to the old version. During the release process, if the new version is running normally, the traffic proportion of the new version can be gradually increased;

[0030] S022. The control plane of the API gateway monitors the grayscale release status;

[0031] Furthermore, the API gateway control plane monitors the operation of the new and old versions of the service in real time, including request latency, upstream and downstream traffic, number of errors, and request RPS;

[0032] S03. The API gateway confirms whether the grayscale release is successful based on the traffic monitoring results of the release task;

[0033] Further, the S03 includes:

[0034] S031. During the grayscale release process, if the real-time monitoring results are abnormal, the released version can be rolled back;

[0035] Further, the S031 includes:

[0036] S0311. For the rollback method with manual intervention, click the version offline, and the API gateway will roll back the service;

[0037] S0312. For the automatic rollback method, the API gateway automatically triggers the rollback according to the rollback conditions;

[0038] S0313. After the rollback, the service will be restored to the version before the release, and the status of the release task will be changed to pending release.

[0039] S032. During the grayscale release process, if the real-time monitoring results are normal, click the grayscale version to take over all traffic. At this time, the node configuration of the grayscale release will overwrite the configuration of the service node, and the task status will change to released.

[0040] Furthermore, after the grayscale release is successful, the released version cannot be changed;

[0041] Furthermore, the published version will not be displayed in the release task list, but only in the release history;

[0042] S04. After the grayscale release is successful, the API gateway stores the old version of the service in the release history, and you can switch to other versions in the release history.

[0043] Furthermore, you can only view and switch historical versions, but you cannot change the configuration of historical versions;

[0044] Furthermore, you can specify the backend environment, select a version, and then switch to this version. This operation will cause this version to directly replace the previous version and take effect in real time.

[0045] In one embodiment of the present invention, a BGP Down fault locating device is also proposed, the device comprising:

[0046] Network data loading module, detecting BGP status;

[0047] Log in to the local device module and check the status of the local device;

[0048] Log in to the peer device module and check the peer device status.

[0049] In one embodiment of the present invention, a computer device is also proposed, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the aforementioned BGP Down fault locating method is implemented.

[0050] In one embodiment of the present invention, a computer-readable storage medium is further provided. The computer-readable storage medium stores a computer program for executing the BGP Down fault locating method.

[0051] Beneficial effects:

[0052] The present invention provides a BGP Down fault locating method and device, which attaches expert capabilities, automatically performs BGP Down fault diagnosis in combination with alarm information, network protocols, and test commands, performs real-time analysis and processing on inspection result data to ensure its timeliness, performs process-based processing and analysis on BGP Down faults, helps network operation and maintenance personnel quickly locate service faults, reduces their work pressure, and standardizes and automates the fault locating process, reduces the possibility of human misdiagnosis and missed detection, improves the accuracy of fault diagnosis, and improves the efficiency of fault locating. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 It is a flow chart of the BGP Down fault locating method of the present invention;

[0054] Figure 2 It is a structural schematic diagram of the BGP Down fault locating device of the present invention;

[0055] Figure 3 It is a schematic diagram of the structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0059] The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

[0060] Those skilled in the art will appreciate that the embodiments of the present invention may be implemented as a system, device, apparatus, method or computer program product. Therefore, the present disclosure may be implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0061] According to the implementation mode of the present invention, a BGP Down fault locating method and device are proposed. By collecting and analyzing alarms and protocol status of network elements with BGP Down faults, and initiating tests for the faulty network elements, the cause of the BGP Down fault is located, the work pressure of network operation and maintenance personnel is reduced, and the operation and maintenance efficiency is improved.

[0062] The principle and spirit of the present invention are explained in detail below with reference to several representative embodiments of the present invention.

[0063] like Figure 1 As shown, the present invention relates to a BGP Down fault locating method, the method comprising:

[0064] S01, network data loading, BGP status detection;

[0065] The S01 includes:

[0066] S011. Load network alarm data. Alarms include: device port Down alarm, BGP Down alarm. When a device network element has a port Down alarm, and a BGP Down alarm occurs 3 times or more, it is determined that the BGP protocol Down is caused by the device port Down.

[0067] S012, check whether the BGP status is restored;

[0068] The S012 includes:

[0069] S0121, check whether the normal BGP status is restored. If the BGP status is ESTABLISHED, the BGP connection has been self-healed during the detection, the fault has been restored, and the process ends; if the BGP status is not restored, enter S013;

[0070] S0122. Check whether the VPN BGP status is restored. If the BGP status is ESTABLISHED, the BGP connection has self-healed during the detection, the fault has been restored, and the process ends. If the BGP status has not been restored, enter S013.

[0071] S013, check whether the BGP state is idle (admin). If the BGP state is idle (admin), locate the cause of the fault and the process ends; if the BGP state is not idle (admin), enter S014;

[0072] S014, check whether the BGP route exceeds the limit. If the BGP route exceeds the limit, check the BGP route setting, which does not directly affect BGPDOWN and does not interrupt the diagnosis process, and enter S015;

[0073] S015, detecting whether an error message is received. If an error message is received, the BGP error message does not directly affect BGPDOWN, and the diagnosis process is not interrupted when the error message is received. The BGP error message is received and the process proceeds to S016;

[0074] S016. Check whether the BGP configuration causes the neighbor to lose connection;

[0075] The S016 includes:

[0076] S0161. Execute the command: show running-config bgp|inc[neighbor IP];

[0077] S0162: If result information is returned and the neighbor connection is not disconnected, then go to S017;

[0078] S0163: No result information is returned, indicating that the neighbor is disconnected. The neighbor is disconnected. The prompt is: BGP configuration error. Check the BGP peer settings, locate the cause of the fault, and the process ends.

[0079] S017, detect whether the BGP direct connection port is disconnected. If both the Current state and Line protocol states of the port are UP, the test passes; otherwise, it fails.

[0080] Current state refers to the current state of the BGP neighbor, and Line protocol state refers to the line protocol state of the interface.

[0081] The S017 includes:

[0082] S0171, if the port is a physical port, query the physical port twice to check whether the CRC and Symbol have increased;

[0083] S0172: If the port is an Eth-Trunk, query the corresponding physical port, and query the physical port twice to check whether the CRC and Symbol values ​​increase.

[0084] When CRC increases rapidly, the physical port may go Down, causing all protocols to go Down.

[0085] S0173, if the test fails, it will prompt: BGP direct connection interface is disconnected, check the interconnection interface, load the test information, locate the cause of the fault, and the process ends;

[0086] S0174. Detection passed, enter S018.

[0087] S018, check whether the Notification message, Hold timer expiration, and remote peer unreachable information are received. If not, transfer to manual processing; if the above information is received, enter S02.

[0088] S02, log in to the local device and check the status of the local device;

[0089] The S02 includes:

[0090] S021. Check whether the interconnection interface status is normal and whether the error counts of crc, symbol, error, etc. are increasing. If the port status is UP, it is normal, otherwise it is abnormal. If the error counts of crc, symbol, error, etc. are increasing, it means that the interconnection port is abnormal.

[0091] If there is an abnormality, it will prompt: The abnormality of the interconnection port on this end causes BGP to be interrupted. The cause of the fault is located and the process ends;

[0092] If normal, go to S022;

[0093] S022. Execute the command to check whether the VPN BFD status is normal. If the state is UP, it is normal. Otherwise, it is abnormal.

[0094] If there is an abnormality, it will prompt: BGP is interrupted, the BFD status of the local VPN is abnormal, the cause of the fault is located, and the process ends;

[0095] If normal, go to S023;

[0096] S023, Ping the interconnection IP to see if it is reachable. If the port interconnection address can be pinged, the test passes and the process goes to S024. If the ping test fails, it is prompted that the interconnection address of the other end cannot be reached when pinged by this end. The cause of the fault is located and the process ends.

[0097] S024, Ping the neighbor IP to see if it is reachable. If the neighbor address ping passes, the test passes and the process goes to S025. If it fails, it prompts: The neighbor address of the other end is unreachable when pinged by this end. The cause of the fault is located and the process ends.

[0098] S025, check whether the CPU utilization is normal, execute the command: display cpu-usage. If the CPU utilization is lower than the threshold (initialized to 75%), the detection is passed; if the CPU utilization exceeds the threshold, it is abnormal, and the prompt is: the CPU utilization of the local end is abnormal (too high). The detection result of the CPU utilization does not interrupt the diagnosis process, and enters S25;

[0099] S026, check whether ACL 179 is restricted. If BGP (179) is configured to allow traffic, the check passes and the process goes to S026. If the check fails, it prompts: ACL 179 on the local end is restricted. The cause of the fault is located and the process ends.

[0100] S027, trace neighbor address, determine whether the two-way trace paths at both ends are consistent, if not, it will prompt: the round-trip paths of this / the other end are inconsistent. The consistency judgment result does not interrupt the diagnosis process, and enter S028;

[0101] S028. Check whether there is a flash disconnection alarm on the port. Check whether a flash disconnection alarm occurs on the interconnection port within the range of -10 minutes from the time when the BGP Down alarm occurs to +10 minutes from the time when the last alarm occurs. If no flash disconnection alarm occurs, the check passes and goes to S03. If a flash disconnection alarm occurs, the check fails and it is prompted: a flash disconnection alarm occurs on the interconnection port on this end. The cause of the fault is located and the process ends.

[0102] S03. Log in to the peer device and check the status of the peer device.

[0103] The S03 includes:

[0104] S031. Check whether the Peer IP configuration is correct. Execute the display bgp peer command to view the status and configuration information of the BGP neighbor. If the configuration is correct, the check passes and the process goes to S032. If the configuration is abnormal, the check fails and the message is: There is no problem on the local end, but the BGP peer IP configuration is incorrect. The cause of the fault is located and the process ends.

[0105] The state and configuration information of the BGP neighbor in S031 includes: IP address, AS number, state, and whether a BGP session has been established, etc.;

[0106] S032. Check whether the BGP status is idle (admin). If the BGP status is idle (admin), it will prompt: TCP 179 is unreachable and is manually closed. The cause of the fault is located and the process ends. If the BGP status is not idle (admin), enter S033.

[0107] S033, check whether the VPN BFD status is normal. The inspection method is the same as S022. If the VPN BFD status is abnormal, it will prompt: BGP is interrupted, the peer VPN BFD status is abnormal, locate the cause of the fault, and the process ends; if the VPN BFD status is normal, go to S034;

[0108] S034, Ping the interconnection IP to see if it is reachable. The inspection method is the same as S023. If it fails, it will prompt: BGP is interrupted, and the ping test of the interconnection address of the other end is unreachable. The cause of the fault is located and the process ends. If the inspection passes, enter S035;

[0109] S035, Ping the neighbor IP to see if it is reachable. The checking method is the same as S024. If it fails, it will prompt: BGP is interrupted, and the ping test of the neighbor address is unreachable. The cause of the fault is located and the process ends. If the check passes, enter S036;

[0110] S036, check whether the CPU utilization is normal. The inspection method is the same as S025. If the CPU utilization is abnormal, it will prompt: The CPU utilization of the other end is abnormal (too high). Whether it is normal or abnormal, the diagnosis process will not be interrupted and enter 037;

[0111] S037, check whether ACL 179 is restricted. The checking method is the same as S026. If BGP (179) is configured to allow traffic, the check passes and the process goes to S038. If it fails, it prompts: BGP is interrupted and the peer ACL 179 restricts traffic. The cause of the fault is located and the process ends.

[0112] S038, trace neighbor address, determine whether the two-way trace paths at both ends are consistent, the inspection method is the same as S027, if not, it will prompt: the two-way paths are inconsistent, consistent detection results, do not interrupt the diagnosis process, enter S039;

[0113] S039. Check whether there is a flash disconnection alarm on the port. If there is a flash disconnection alarm, the check fails and a prompt is given: BGP is interrupted, the other port flash disconnection alarm occurs. The cause of the fault is located and the process ends. If there is no flash disconnection alarm, manual processing is performed.

[0114] It should be noted that, although the operations of the method of the present invention are described in a specific order in the above embodiments and the accompanying drawings, this does not require or imply that the operations must be performed in the specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0115] In order to explain the above BGP Down fault locating method more clearly, it is described below in conjunction with a specific embodiment. However, it should be noted that this embodiment is only for better illustrating the present invention and does not constitute an improper limitation to the present invention.

[0116] S01, network data loading, BGP status detection;

[0117] The S01 includes:

[0118] S011. Load network alarm data. Alarms include: device port Down alarm, BGP Down alarm. When a device network element has a port Down alarm, and a BGP Down alarm occurs 3 times or more, it is determined that the BGP protocol Down is caused by the device port Down.

[0119] S012, check whether the BGP status is restored;

[0120] The S012 includes:

[0121] S0121, check whether the normal BGP status is restored. If the BGP status is ESTABLISHED, the BGP connection has been self-healed during the detection, the fault has been restored, and the process ends; if the BGP status is not restored, enter S013;

[0122] The "ESTABLISHED" state in the BGP state machine indicates that the BGP neighbor relationship has been successfully established and BGP peers can exchange routing information.

[0123] ipv4: dis bgp peer 36.133.59.254verbose;

[0124] ipv6: dis bgp ipv6 peer 2409:8000::1:1verbose;

[0125] S0122. Check whether the VPN BGP status is restored. If the BGP status is ESTABLISHED, the BGP connection has self-healed during the detection, the fault has been restored, and the process ends. If the BGP status has not been restored, enter S013.

[0126] ipv4: display bgp vpnv4 all peer;

[0127] display bgp vpnv4 vpn-instance ChinaMobile_CBOSS peer 10.5.90.214verbose;

[0128] ipv6: display bgp vpnv6 all peer;

[0129] display bgp vpnv6 vpn-instance ChinaMobile_CBOSS peer 2409:8000:4820:B401::1verbose

[0130] S013, check whether the BGP state is idle (admin). If the BGP state is idle (admin), locate the cause of the fault and the process ends; if the BGP state is not idle (admin), enter S014;

[0131] The idle (admin) state is a state in BGP (Border Gateway Protocol), where "idle" indicates the initial state of BGP, and "admin" indicates the state caused by administrator intervention (such as manually closing the BGP session). In the "idle" state, the BGP process will not attempt to establish a TCP connection with the neighbor, nor will it send or receive BGP messages.

[0132] S014, check whether the BGP route exceeds the limit. If the BGP route exceeds the limit, check the BGP route setting, which does not directly affect BGPDOWN and does not interrupt the diagnosis process, and enter S015;

[0133] For common BGP, execute:

[0134] display bgp peer 36.133.59.254 verbose;

[0135] display bgp routing-table peer 36.133.59.254 received-routes;

[0136] VPN BGP, execute:

[0137] display ip vpn-instance verbose vpn-instance-name

[0138] The results show:

[0139] For address family:IPv4 Unicast

[0140] Med attribute sent to th1s neighbor

[0141] Weight is O

[0142] Community attribute sent to this neighbor

[0143] Advertised prefixes limit 4294967295

[0144] Maximum limit 4294967295

[0145] Threshold for warning message 75%

[0146] The Maximum limit is 4294967295, and the Threshold for warning message is 75%.

[0147] S015, detecting whether an error message is received. If an error message is received, the BGP error message does not directly affect BGPDOWN, and the diagnosis process is not interrupted when the error message is received. The BGP error message is received and the process proceeds to S016;

[0148] S016. Check whether the BGP configuration causes the neighbor to lose connection;

[0149] The S016 includes:

[0150] S0161. Execute the command: show running-config bgp|inc[neighbor IP];

[0151] S0162: If result information is returned and the neighbor connection is not disconnected, then go to S017;

[0152] S0163: No result information is returned, indicating that the neighbor is disconnected. The neighbor is disconnected. The prompt is: BGP configuration error. Check the BGP peer settings, locate the cause of the fault, and the process ends.

[0153] Run the command "show running-config bgp|inc 221.130.169.252[neighbor IP]",

[0154] Execution result example:

[0155] show running-config bgp|include 221.130.169.252

[0156] neighbor 221.130.169.252 remote-as 64810

[0157] neighbor 221.130.169.252 peer-group MAN_CORE_RR

[0158] neighbor 221.130.169.252 description XXX

[0159] S017, detect whether the BGP direct connection port is disconnected. If both the Current state and Line protocol states of the port are UP, the test passes; otherwise, it fails.

[0160] Current state refers to the current state of the BGP neighbor, and Line protocol state refers to the line protocol state of the interface.

[0161] The S017 includes:

[0162] S0171, if the port is a physical port, query the physical port twice to check whether the CRC and Symbol have increased;

[0163] S0172: If the port is an Eth-Trunk, query the corresponding physical port, and query the physical port twice to check whether the CRC and Symbol values ​​increase.

[0164] When CRC increases rapidly, the physical port may go Down, causing all protocols to go Down.

[0165] S0173, if the test fails, it will prompt: BGP direct connection interface is disconnected, check the interconnection interface, load the test information, locate the cause of the fault, and the process ends;

[0166] S0174. Detection passed, enter S018.

[0167] Detection method:

[0168] Ordinary BGP:

[0169] ipv4:

[0170] display ip routing-table 36.133.59.254;

[0171] dis curr|in route-static|in 36.133.59.254;

[0172] disp inte Eth-Trunk44;

[0173] ipv6:

[0174] display ip routing-table 2409:8000::1:1;

[0175] dis curr|in route-static|in 2409:8000::1:1;

[0176] disp ipv6 inte Eth-Trunk27;

[0177] VPN BGP:

[0178] ipv4:

[0179] display ip routing-table vpn-instance ChinaMobile_CBOSS 10.5.90.214;

[0180] disp inte Eth-Trunk6.419;

[0181] IPv6:

[0182] display ipv6 routing-table vpn-instance ChinaMobile_CBOSS 2409:8000:4820:B401::1;

[0183] disp ipv6 inte Eth-Trunk6.419;

[0184] S018, check whether the Notification message, Hold timer expiration, and remote peer unreachable information are received. If not, transfer to manual processing; if the above information is received, enter S02.

[0185] S02, log in to the local device and check the status of the local device;

[0186] The S02 includes:

[0187] S021. Check whether the interconnection interface status is normal and whether the error counts of crc, symbol, error, etc. are increasing. If the port status is UP, it is normal, otherwise it is abnormal. If the error counts of crc, symbol, error, etc. are increasing, it means that the interconnection port is abnormal.

[0188] If there is an abnormality, it will prompt: The abnormality of the interconnection port on this end causes BGP to be interrupted. The cause of the fault is located and the process ends;

[0189] If normal, go to S022;

[0190] S022. Execute the command to check whether the VPN BFD status is normal. If the state is UP, it is normal. Otherwise, it is abnormal.

[0191] If there is an abnormality, it will prompt: BGP is interrupted, the BFD status of the local VPN is abnormal, the cause of the fault is located, and the process ends;

[0192] If normal, go to S023;

[0193] Detection method:

[0194] Execute the command:

[0195] V6:

[0196] display bgp ipv6 bfd session peer ipv6-address;

[0197] V4:

[0198] display bgp bfd session peer ipv4-address

[0199] Execution Result:

[0200] display bgp bfd session peer ipv4-address 10.10.1.1

[0201] Local|Remote|PeerIpAddr|State|Type|InterfaceName

[0202] 1 / 1|1 / 1|10.10.1.1|UP|S_IP_IF|GigabitEthernet / 0 / 0 / 0

[0203] Total UP / DOWN Session Number:1 / 0

[0204] S023, Ping the interconnection IP to see if it is reachable. If the port interconnection address can be pinged, the test passes and the process goes to S024. If the ping test fails, it is prompted that the interconnection address of the other end cannot be reached when pinged by this end. The cause of the fault is located and the process ends.

[0205] Ping test method:

[0206] V6:

[0207] ping ipv62409:8080::2D3

[0208] V4:

[0209] ping 221.183.20.82

[0210] S024, Ping the neighbor IP to see if it is reachable. If the neighbor address ping passes, the test passes and the process goes to S025. If it fails, it prompts: The neighbor address of the other end is unreachable when pinged by this end. The cause of the fault is located and the process ends.

[0211] Ping test method:

[0212] V6:

[0213] ping ipv62409:8080::2D3

[0214] V4:

[0215] ping 221.183.20.82

[0216] S025, check whether the CPU utilization is normal, execute the command: display cpu-usage. If the CPU utilization is lower than the threshold (initialized to 75%), the detection is passed; if the CPU utilization exceeds the threshold, it is abnormal, and the prompt is: the CPU utilization of the local end is abnormal (too high). The detection result of the CPU utilization does not interrupt the diagnosis process, and enters S25;

[0217] S026, check whether ACL 179 is restricted. If BGP (179) is configured to allow traffic, the check passes and the process goes to S026. If the check fails, it prompts: ACL 179 on the local end is restricted. The cause of the fault is located and the process ends.

[0218] Inspection method:

[0219] IPv4:

[0220] display acl all|i 36.133.59.254

[0221] IPv6:

[0222] display acl ipv6 all|i 2409:8000::1:1

[0223] S027, trace neighbor address, determine whether the two-way trace paths at both ends are consistent, if not, it will prompt: the round-trip paths of this / the other end are inconsistent. The consistency judgment result does not interrupt the diagnosis process, and enter S028;

[0224] Inspection method:

[0225] IPv4:

[0226] tracert 192.168.3.9

[0227] IPv6:

[0228] tracert ipv62409:8080::2D3

[0229] S028. Check whether there is a flash disconnection alarm on the port. Check whether a flash disconnection alarm occurs on the interconnection port within the range of -10 minutes from the time when the BGP Down alarm occurs to +10 minutes from the time when the last alarm occurs. If no flash disconnection alarm occurs, the check passes and goes to S03. If a flash disconnection alarm occurs, the check fails and it is prompted: a flash disconnection alarm occurs on the interconnection port on this end. The cause of the fault is located and the process ends.

[0230] S03. Log in to the peer device and check the status of the peer device.

[0231] The S03 includes:

[0232] S031. Check whether the Peer IP configuration is correct. Execute the display bgp peer command to view the status and configuration information of the BGP neighbor. If the configuration is correct, the check passes and the process goes to S032. If the configuration is abnormal, the check fails and the message is: There is no problem on the local end, but the BGP peer IP configuration is incorrect. The cause of the fault is located and the process ends.

[0233] The state and configuration information of the BGP neighbor in S031 includes: IP address, AS number, state, and whether a BGP session has been established, etc.;

[0234] S032. Check whether the BGP status is idle (admin). If the BGP status is idle (admin), it will prompt: TCP 179 is unreachable and is manually closed. The cause of the fault is located and the process ends. If the BGP status is not idle (admin), enter S033.

[0235] S033, check whether the VPN BFD status is normal. The inspection method is the same as S022. If the VPN BFD status is abnormal, it will prompt: BGP is interrupted, the peer VPN BFD status is abnormal, locate the cause of the fault, and the process ends; if the VPN BFD status is normal, go to S034;

[0236] S034, Ping the interconnection IP to see if it is reachable. The inspection method is the same as S023. If it fails, it will prompt: BGP is interrupted, and the ping test of the interconnection address of the other end is unreachable. The cause of the fault is located and the process ends. If the inspection passes, enter S035;

[0237] S035, Ping the neighbor IP to see if it is reachable. The checking method is the same as S024. If it fails, it will prompt: BGP is interrupted, and the ping test of the neighbor address is unreachable. The cause of the fault is located and the process ends. If the check passes, enter S036;

[0238] S036, check whether the CPU utilization is normal. The inspection method is the same as S025. If the CPU utilization is abnormal, it will prompt: The CPU utilization of the other end is abnormal (too high). Whether it is normal or abnormal, the diagnosis process will not be interrupted and enter 037;

[0239] S037, check whether ACL 179 is restricted. The checking method is the same as S026. If BGP (179) is configured to allow traffic, the check passes and the process goes to S038. If it fails, it prompts: BGP is interrupted and the peer ACL 179 restricts traffic. The cause of the fault is located and the process ends.

[0240] S038, trace neighbor address, determine whether the two-way trace paths at both ends are consistent, the inspection method is the same as S027, if not, it will prompt: the two-way paths are inconsistent, consistent detection results, do not interrupt the diagnosis process, enter S039;

[0241] S039. Check whether there is a flash disconnection alarm on the port. If there is a flash disconnection alarm, the check fails and a prompt is given: BGP is interrupted, the other port flash disconnection alarm occurs. The cause of the fault is located and the process ends. If there is no flash disconnection alarm, manual processing is performed.

[0242] Based on the same inventive concept, the present invention also proposes a BGP Down fault locating device. The implementation of the device can refer to the implementation of the above method, and the repeated parts will not be repeated. The term "module" used below can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0243] Figure 2FIG. 1 is a schematic diagram of the structure of the BGP Down fault location device of the present invention. Figure 2 As shown, the device comprises:

[0244] The network data loading module 110 detects the BGP status;

[0245] Log in to the local device module 120 to detect the status of the local device;

[0246] The module 130 for logging into the opposite device detects the status of the opposite device.

[0247] It should be noted that although several modules of the BGP Down fault location device are mentioned in the above detailed description, this division is only exemplary and not mandatory. In fact, according to the embodiment of the present invention, the features and functions of two or more modules described above can be embodied in one module. Conversely, the features and functions of one module described above can be further divided into multiple modules for embodiment.

[0248] Based on the above invention concept, Figure 3 As shown, the present invention also proposes a computer device 200, including a memory 210, a processor 220, and a computer program 230 stored in the memory 210 and executable on the processor 220. When the processor 220 executes the computer program 230, the aforementioned BGP Down fault locating method is implemented.

[0249] Based on the aforementioned inventive concept, the present invention further proposes a computer-readable storage medium, which stores a computer program for executing the aforementioned BGP Down fault locating method.

[0250] The present invention provides a BGP Down fault locating method and device, which attaches expert capabilities, automatically performs BGP Down fault diagnosis in combination with alarm information, network protocols, and test commands, performs real-time analysis and processing on inspection result data to ensure its timeliness, performs process-based processing and analysis on BGP Down faults, helps network operation and maintenance personnel quickly locate service faults, reduces their work pressure, and standardizes and automates the fault locating process, reduces the possibility of human misdiagnosis and missed detection, improves the accuracy of fault diagnosis, and improves the efficiency of fault locating.

[0251] Although the spirit and principle of the present invention have been described with reference to several specific embodiments, it should be understood that the present invention is not limited to the disclosed specific embodiments, and the division of various aspects does not mean that the features in these aspects cannot be combined to benefit, and such division is only for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements contained in the spirit and scope of the attached claims.

[0252] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0253] The program code for implementing the method of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0254] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0255] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0256] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0257] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.

[0258] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved, and this document does not limit this.

[0259] The above specific implementations do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present disclosure shall be included in the protection scope of the present disclosure.

[0260] Regarding the limitation of the protection scope of the present invention, those skilled in the art should understand that, based on the technical solution of the present invention, various modifications or variations that can be made by those skilled in the art without creative work are still within the protection scope of the present invention.

Claims

1. A BGP Down fault location method, characterized in that: The method includes: S01, network data loading, BGP status detection; S02, log in to the local device and check the status of the local device; S03. Log in to the peer device and check the status of the peer device.

2. The BGP Down fault locating method according to claim 1, characterized in that: The S01 includes: S011. Load network alarm data. Alarms include: device port Down alarm, BGP Down alarm. When a device network element has a port Down alarm, and a BGP Down alarm occurs 3 times or more, it is determined that the BGP protocol Down is caused by the device port Down. S012, check whether the BGP status is restored; S013, check whether the BGP state is idle (admin). If the BGP state is idle (admin), locate the cause of the fault and the process ends; if the BGP state is not idle (admin), enter S014; S014, check whether the BGP route exceeds the limit. If the BGP route exceeds the limit, check the BGP route setting, which does not directly affect BGPDOWN and does not interrupt the diagnosis process, and enter S015; S015, detecting whether an error message is received. If an error message is received, the BGP error message does not directly affect BGPDOWN, and the diagnosis process is not interrupted when the error message is received. The BGP error message is received and the process proceeds to S016; S016. Check whether the BGP configuration causes the neighbor to lose connection; S017, detect whether the BGP direct connection port is disconnected. If both the Current state and Line protocol states of the port are UP, the test passes; otherwise, it fails. Current state refers to the current state of the BGP neighbor, and Line protocol state refers to the line protocol state of the interface; S018, check whether the Notification message, Hold timer expiration, and remote peer unreachable information are received. If not, transfer to manual processing; if the above information is received, enter S02.

3. The BGP Down fault locating method according to claim 2, characterized in that: The S012 includes: S0121, check whether the normal BGP status is restored. If the BGP status is ESTABLISHED, the BGP connection has been self-healed during the detection, the fault has been restored, and the process ends; if the BGP status is not restored, enter S013; S0122. Check whether the VPN BGP status is restored. If the BGP status is ESTABLISHED, the BGP connection has self-healed during the detection, the fault has been restored, and the process ends. If the BGP status has not been restored, enter S013.

4. The BGP Down fault locating method according to claim 2, characterized in that: The S016 includes: S0161. Execute the command: show running-config bgp|inc[neighbor IP]; S0162: If result information is returned and the neighbor connection is not disconnected, then go to S017; S0163: No result information is returned, indicating that the neighbor is disconnected. The neighbor is disconnected. The prompt is: BGP configuration error. Check the BGPpeer settings, locate the cause of the fault, and the process ends.

5. The BGP Down fault locating method according to claim 2, characterized in that: The S017 includes: S0171, if the port is a physical port, query the physical port twice to check whether the CRC and Symbol have increased; S0172: If the port is an Eth-Trunk, query the corresponding physical port, and query the physical port twice to check whether the CRC and Symbol values ​​increase. S0173, if the test fails, it will prompt: BGP direct connection interface is disconnected, check the interconnection interface, load the test information, locate the cause of the fault, and the process ends; S0174. Detection passed, enter S018.

6. The BGP Down fault locating method according to claim 1, characterized in that: The S02 includes: S021. Check whether the interconnection interface status is normal and whether the CRC, symbol, and error bit error counts are increasing. If the port status is UP, it is normal, otherwise it is abnormal. If the CRC, symbol, and error bit error counts are increasing, it means that the interconnection port is abnormal. If there is an abnormality, it will prompt: The abnormality of the interconnection port on this end causes BGP to be interrupted. The cause of the fault is located and the process ends; If normal, go to S022; S022. Execute the command to check whether the VPN BFD status is normal. If the state is UP, it is normal. Otherwise, it is abnormal. If there is an abnormality, it will prompt: BGP is interrupted, the BFD status of the local VPN is abnormal, the cause of the fault is located, and the process ends; If normal, go to S023; S023, Ping the interconnection IP to see if it is reachable. If the port interconnection address can be pinged, the test passes and the process goes to S024. If the ping test fails, it is prompted that the interconnection address of the other end cannot be reached when pinged by this end. The cause of the fault is located and the process ends. S024, Ping the neighbor IP to see if it is reachable. If the neighbor address ping passes, the test passes and the process goes to S025. If it fails, it prompts: The neighbor address of the other end is unreachable when pinged by this end. The cause of the fault is located and the process ends. S025. Check whether the CPU utilization is normal. Execute the command: display cpu-usage. If the CPU utilization is lower than the threshold, the test passes. If the CPU utilization exceeds the threshold, it is abnormal, and the prompt is: The CPU utilization of this end is abnormal / too high. The CPU utilization test result does not interrupt the diagnosis process, and enters S25. S026, check whether ACL 179 is restricted. If BGP (179) is configured to allow traffic, the check passes and the process goes to S026. If the check fails, it prompts: ACL 179 on the local end is restricted. The cause of the fault is located and the process ends. S027, trace neighbor address, determine whether the two-way trace paths at both ends are consistent, if not, it will prompt: the round-trip paths of this / the other end are inconsistent. The consistency judgment result does not interrupt the diagnosis process, and enter S028; S028. Check whether there is a flash disconnection alarm on the port. Check whether a flash disconnection alarm occurs on the interconnection port within the range of -10 minutes from the time when the BGP Down alarm occurs to +10 minutes from the time when the last alarm occurs. If no flash disconnection alarm occurs, the check passes and goes to S03. If a flash disconnection alarm occurs, the check fails and it is prompted: a flash disconnection alarm occurs on the interconnection port on this end. The cause of the fault is located and the process ends.

7. The BGP Down fault locating method according to claim 1, characterized in that: The S03 includes: S031. Check whether the PeerIP configuration is correct. Execute the display bgp peer command to view the status and configuration information of the BGP neighbor. If the configuration is correct, the check passes and the process goes to S032. If the configuration is abnormal, the check fails and the message is: There is no problem on the local end, but the BGP peer IP configuration is incorrect. The cause of the fault is located and the process ends. S032. Check whether the BGP status is idle (admin). If the BGP status is idle (admin), it will prompt: TCP 179 is unreachable and is manually closed. The cause of the fault is located and the process ends. If the BGP status is not idle (admin), enter S033. S033, check whether the VPN BFD status is normal. The inspection method is the same as S022. If the VPN BFD status is abnormal, it will prompt: BGP is interrupted, the peer VPN BFD status is abnormal, locate the cause of the fault, and the process ends; if the VPN BFD status is normal, go to S034; S034, Ping the interconnection IP to see if it is reachable. The inspection method is the same as S023. If it fails, it will prompt: BGP is interrupted, and the ping test of the interconnection address of the other end is unreachable. The cause of the fault is located and the process ends. If the inspection passes, enter S035; S035, Ping the neighbor IP to see if it is reachable. The checking method is the same as S024. If it fails, it will prompt: BGP is interrupted, and the ping test of the neighbor address is unreachable. The cause of the fault is located and the process ends. If the check passes, enter S036; S036, check whether the CPU utilization is normal. The inspection method is the same as S025. If the CPU utilization is abnormal, it will prompt: The CPU utilization of the other end is abnormal / too high. Whether it is normal or abnormal, the diagnosis process will not be interrupted, and enter, 037; S037, check whether ACL 179 is restricted. The checking method is the same as S026. If BGP (179) is configured to allow traffic, the check passes and the process goes to S038. If it fails, it prompts: BGP is interrupted and the peer ACL 179 restricts traffic. The cause of the fault is located and the process ends. S038, trace neighbor address, determine whether the two-way trace paths at both ends are consistent, the inspection method is the same as S027, if not, it will prompt: the two-way paths are inconsistent, consistent detection results, do not interrupt the diagnosis process, enter S039; S039. Check whether there is a flash disconnection alarm on the port. If there is a flash disconnection alarm, the check fails and a prompt is given: BGP is interrupted, the other port flash disconnection alarm occurs. The cause of the fault is located and the process ends. If there is no flash disconnection alarm, manual processing is performed.

8. The BGP Down fault locating method according to claim 7, characterized in that: The state and configuration information of the BGP neighbor in S031 includes: IP address, AS number, state, and whether a BGP session has been established.

9. A BGP Down fault locating device, characterized in that: The device includes: Network data loading module, detecting BGP status; Log in to the local device module and check the status of the local device; Log in to the peer device module and check the status of the peer device.

10. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 8 is implemented.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program for executing the method according to any one of claims 1 to 8.

Images