Method for concatenating multi-segment network paths across isolation devices

Abstract

The application discloses a method for splicing multi-section network paths across isolation devices, comprising the following steps: step 1, opening corresponding network protocols for all devices in the multi-section network across the isolation devices, and inputting account passwords into the system; step 2, configuring a periodic collection task in the system, and after starting the task, collecting the routing information of all network devices concurrently; step 3, adapting the collected routing information and storing the same into a database, and according to the need, retrieving the IP addresses of the end and Z-end devices of the path, and then performing end-to-end path retrieval and splicing, and displaying the path. The application is based on the association of CE devices to PE across the isolation devices, realizes the splicing of the multi-section network paths across the isolation devices, collects all links between the PE and the CE, and finds the optimal active link through the link delay and the traffic to determine the opposite PE device, and solves the problem that the general network tools cannot retrieve the complete network path across the isolation devices.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of network path detection, and particularly relates to a method for splicing a multi-segment network path across an isolation device. BACKGROUND

[0002] Currently, the trace route network diagnostic tool is mainly used for network path detection, and is used for displaying the path of a data packet from one network node (usually a computer or a server) to another network node (such as another server). It is achieved by sending special types of data packets and listening to their responses.

[0003] The basic working principle of the trace route network diagnostic tool is as follows: first, a network data packet is sent to a target address, and the data packet is usually an ICMP (Internet Control Message Protocol) packet, and the TTL (Time-to-Live) field is set to 1. TTL is a mechanism for preventing data packets from circulating indefinitely in the network, and the TTL value is reduced by 1 each time the data packet passes through a network node (such as a router or a firewall). When the TTL value reaches 0, the network node will discard the data packet and send an "ICMP timeout" message back to the sender. After the traceroute receives the "ICMP timeout" message, it knows the address of the first network node, i.e., the node that sent the "ICMP timeout" message. Then, it sends a new data packet, but this time the TTL value is set to 2. The traceroute continues this process, increasing the TTL value and sending a new data packet each time, until the data packet reaches the target address. In this way, it can track and display all the network nodes through which the data packet passes. The traceroute usually sends three data packets at each TTL value, so that the average delay time of each step can be displayed. If a node does not respond, the traceroute will display a timeout.

[0004] The path of the data packet in the network can be determined through the traceroute, which is very effective for diagnosing network delays, path loops and other network problems. However, the trace route also has its limitations, for example, some routers or firewalls may block the "traceroute" data packet, which will result in incomplete path information. In addition, some networks may use asymmetric routing strategies, resulting in different return paths and sending paths, which cannot be captured by "traceroute". In networks using multi-path routing (ECMP, Equal Cost Multipath), different "traceroute" probes may take different paths, which may result in inconsistency of the results. SUMMARY

[0005] The technical problem solved by the present application is to overcome the deficiencies of the prior art, and to provide a method for splicing a multi-section network path across an isolated device, which can restore the network path in a network environment blocked by an isolated device.

[0006] To achieve the above technical purpose, the technical solution adopted by the present application is:

[0007] The method for splicing a multi-section network path across an isolated device comprises the following steps:

[0008] Step 1: Open the corresponding network protocol for all devices in the multi-section network across the isolated device, and enter the account and password into the system;

[0009] Step 2: Configure a periodic collection task in the system, and after starting the task, concurrently collect the routing information of all network devices;

[0010] Step 3: Adapt the collected routing information and store it in the database, and according to the need, retrieve the IP addresses of the A-end and Z-end devices of the path, and then perform end-to-end path retrieval and splicing, and display the path.

[0011] To optimize the above technical solution, the specific measures adopted include:

[0012] The network mentioned above is a private network within a unit or organization.

[0013] The devices mentioned above include routers, switches, firewalls and servers.

[0014] The protocols mentioned above are snmp protocols, telnet protocols or ssh protocols.

[0015] The specific process of retrieving the IP addresses of the A-end and Z-end devices of the path according to the need, and then performing end-to-end path retrieval and splicing is as follows:

[0016] (1) Initial input:

[0017] A_IP, the IP address of the A-end device, and Z_IP, the IP address of the Z-end device

[0018] (2) Determine the PE devices of the two-end devices:

[0019] Perform IP management retrieval on A_IP and Z_IP to confirm whether they are PE devices, if the A-end or Z-end is not a direct PE device, find the corresponding CE device according to the association of IP address and subnet mask, and then associate the CE device to the corresponding PE device;

[0020] (3) Recursive search process:

[0021] From the PE device PE_A corresponding to the A end, all directly connected network devices are found, for each directly connected device, it is judged whether it is a PE device or an edge device: if it is a PE device and is the target PE device PE_Z, the path splicing is completed; if it is an edge device, the edge device is recorded, and the device connected thereto is continuously found from the device downward;

[0022] (4) Path splicing:

[0023] All edge devices recorded in the recursive process are arranged in the access order to form a complete network path, ensuring that the path passes through all intermediate edge devices from the A end PE device to the Z end PE device;

[0024] (5) Abnormal processing:

[0025] If the path connected to the Z end PE device cannot be found in the recursive process, the path splicing is marked as failed, and relevant abnormal information is prompted.

[0026] The above-mentioned recursive finding uses a depth-first search algorithm, and the recursive depth is limited to prevent infinite recursion, and in the recursive process, the IP of the device that has been accessed is recorded to avoid repeated access and prevent a circular path.

[0027] The above-mentioned (3) includes:

[0028] According to the respective end device IP addresses, it is searched whether the IP is managed, if the IP is managed, it is judged whether the end is a CE device, if the IP is not managed, it is judged whether the end can be associated to a CE device through the IP address and the subnet mask;

[0029] If the end is a CE device or the end can be associated to a CE device through the IP address and the subnet mask, it is judged whether the opposite end of the CE device link of the end has a corresponding PE device, if yes, the link local side is the end network element device, the local side CE device, and the local side PE device, otherwise, the link local side is the end network element device and the local side CE device, and the network element device includes but is not limited to a router, a switch, a firewall, and a server;

[0030] If the end is not a CE device, the link local side is the end network element device and the local side CE device;

[0031] If the end cannot be associated to a CE device through the IP address and the subnet mask, the link local side is the end.

[0032] The above-mentioned local side includes a left side and a right side, corresponding to the A end and the Z end respectively.

[0033] The above-mentioned judgment of whether the opposite end of the CE device link of the end has a corresponding PE device includes:

[0034] The optimal active link is found through link delay and traffic analysis to determine the opposite PE device, and the process is as follows:

[0035] (1) Data collection:

[0036] Real-time delay and traffic data of each link are collected periodically through SNMP, Telnet or SSH protocol, and the collected data are stored for subsequent analysis and decision-making;

[0037] (2) Data analysis:

[0038] Link delay analysis: calculate the average delay value of each link, and identify the link with the smallest delay;

[0039] Traffic analysis: evaluate the current traffic load of each link, and identify the link with the smallest traffic;

[0040] (3) Optimal link selection algorithm:

[0041] The optimal link selection algorithm is used to select the optimal link, and the link selection strategy is dynamically adjusted based on real-time monitoring and historical data to adapt to network load changes;

[0042] (4) Path determination and refinement:

[0043] According to the selected optimal link, the opposite device IP of the PE device is determined;

[0044] (5) Condition judgment:

[0045] When at least one link meeting the low delay and low traffic standard can be identified through the above analysis, and the corresponding PE device exists, it is confirmed that the corresponding PE device exists;

[0046] When the delay or traffic of all links exceeds the set threshold, or the corresponding PE device cannot be determined, mark the path splicing failure, and prompt the network administrator to check.

[0047] The present application has the following beneficial effects:

[0048] The present application is based on the association of CE device to PE across the isolated device, realizes the multi-segment network path splicing across the isolated device, collects all links between PE and CE, and finds the optimal active link through link delay and traffic to determine the opposite PE device, solves the problem that general network tools cannot retrieve the complete network path across the isolated device. BRIEF DESCRIPTION OF DRAWINGS

[0049] Figure 1 The flow chart of the multi-segment network path splicing method across the isolated device in the present application;

[0050] Figure 2Key algorithm for end-to-end path splicing in the application;

[0051] Figure 3 Interface screenshot for end-to-end path splicing in the application. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical scheme and advantages of the application more clear, the application will be further described in detail below in combination with the drawings and examples. It should be understood that the specific examples described herein are only used to explain the application and do not limit the application.

[0053] The steps in the application are arranged with labels, but are not used to limit the order of the steps, unless the order of the steps is explicitly stated or the execution of a certain step needs other steps as a basis, otherwise the relative order of the steps can be adjusted. It can be understood that the term "and / or" used herein relates to and covers any and all possible combinations of one or more of the associated listed items.

[0054] The overall steps of the cross-isolation device multi-segment network path splicing method of the application are as shown in Figure 1 , which includes:

[0055] Step 1: Open the corresponding network protocol for all devices in the cross-isolation device multi-segment network, and enter the account and password into the system;

[0056] First, snmp protocol needs to be opened for all CE devices and PE devices in the entire network, and snmp account and password are entered into the system.

[0057] The network is a private network within a unit or organization.

[0058] The device includes a router, a switch, a firewall and a server.

[0059] The protocol is snmp protocol, telnet protocol or ssh protocol.

[0060] That is, the application is applicable to a private network within a unit or organization, and the network device includes but is not limited to a router, a switch, a firewall, a server and the like, and snmp protocol, telnet and ssh protocol and related ports are opened.

[0061] In a network, isolation devices are an important security tool that can provide protection for the network, preventing malicious behavior and unauthorized access. The following are some common network isolation devices:

[0062] Firewalls: Firewalls are the most common network isolation devices that can block or allow data packets based on specific rules. These rules can be based on IP addresses, port numbers, protocol types, etc.

[0063] Virtual Local Area Networks (VLANs): VLANs can divide a physical network into multiple logical networks, each isolated from the others. This can effectively limit network traffic and improve security.

[0064] Intrusion Detection Systems / Intrusion Prevention Systems (IDS / IPS): These systems can monitor network traffic for malicious behavior or attack patterns. If they detect such activities, they can alert administrators or automatically take action to stop it.

[0065] VPN Gateways: VPN gateways can provide secure remote access. By creating encrypted tunnels, they can isolate remote users from the internal network while allowing them to access internal resources in a secure manner.

[0066] Step 2: Then configure a periodic collection task in the system, after starting the task, collect the routing information of all network devices concurrently;

[0067] Step 3: Adapt the routing information collected through snmp and store it in the database, and retrieve the A-end and Z-end device IP addresses of the path as needed, then perform end-to-end path retrieval and splicing, and display the path;

[0068] (1) Initial input:

[0069] • A-end device IP address (A_IP)

[0070] • Z-end device IP address (Z_IP)

[0071] (2) Determine the PE devices of both ends:

[0072] • Perform IP containment retrieval on A_IP and Z_IP to confirm whether they are PE devices.

[0073] • If the A-end or Z-end is not a direct PE device, find the corresponding CE device based on the IP address and subnet mask association, and then associate the CE device to the corresponding PE device.

[0074] (3) Recursive search process:

[0075] • Start from the A-end corresponding PE device (PE_A) and find all directly connected network devices.

[0076] • For each directly connected device, determine whether it is a PE device or an edge device:

[0077] If it is a PE device and is the target PE device (PE_Z): path stitching is complete.

[0078] If it is an edge device: record the edge device and continue to search for the devices connected to it from the device.

[0079] Further, using the depth-first search (DFS) algorithm, limit the recursion depth (as configured, for example, graphDepth = 15) to prevent infinite recursion.

[0080] During the recursion process, record the IP of the visited devices to avoid repeated visits and prevent circular paths.

[0081] (4) Path stitching:

[0082] • Arrange all edge devices recorded during the recursion process in the order of access to form a complete network path.

[0083] • Ensure that the path passes through all intermediate edge devices from the A-end PE device to the Z-end PE device.

[0084] (5) Exception handling:

[0085] • If the path connected to the Z-end PE device cannot be found during the recursion process, mark the path stitching as failed and prompt the relevant exception information.

[0086] Then enter the A and Z-end device IP addresses required for path retrieval on the page, and the path retrieval and post-retrieval path display can be performed.

[0087] As shown in Figure 2 and Figure 3 , it is the key algorithm steps for end-to-end path stitching.

[0088] 1) Enter the A and Z-end device IP addresses;

[0089] 2) According to the IP address, first search whether the IP is managed;

[0090] 3) If it is managed, determine whether it is a CE device. If it is not managed, determine whether it can be associated to a CE device through the IP address and subnet mask;

[0091] 4) Determine whether the opposite end of the link of the two-end CE devices has a corresponding PE device;

[0092] 5) Recursively search for PE devices to obtain all devices between the two-end PE devices;

[0093] 6) Path stitching for edge devices, CE devices, and PE devices.

[0094] In summary, based on the association of CE devices to PE across isolation devices, the present application realizes multi-segment network path stitching across isolation devices, collects all links between PE and CE, and determines the opposite PE device through optimal active link selection based on link latency and traffic, thereby solving the problem that general network tools cannot retrieve complete network paths across isolation devices.

[0095] The process of determining the opposite PE device through optimal active link selection based on link latency and traffic is as follows:

[0096] (1) Data collection:

[0097] Periodically collect real-time latency and traffic data of each link through SNMP, Telnet, or SSH protocols.

[0098] Store the collected data for subsequent analysis and decision-making.

[0099] (2) Data analysis:

[0100] Link latency analysis: Calculate the average latency value of each link to identify the link with the smallest latency.

[0101] Traffic analysis: Evaluate the current traffic load of each link to identify the link with the smallest traffic.

[0102] (3) Optimal link selection algorithm:

[0103] Dynamic adjustment: Based on real-time monitoring and historical data, dynamically adjust the link selection strategy to adapt to network load changes.

[0104] (4) Path determination and refinement:

[0105] Determine the IP of the opposite PE device based on the selected optimal link.

[0106] (5) Condition judgment:

[0107] Existence of corresponding PE device: When at least one link that meets the low latency and low traffic standards can be identified through the above analysis, and there is a corresponding PE device, the system confirms the existence of the corresponding PE device.

[0108] Non-existence of corresponding PE device: When the latency or traffic of all links exceeds the set threshold, or the corresponding PE device cannot be determined through link analysis, the system marks the path stitching as failed and prompts the network administrator to check.

[0109] It will be obvious to a person skilled in the art that the application is not limited to the details of the foregoing exemplary embodiments and can be implemented in other concrete forms without departing from the spirit or essential characteristics of the application. The embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. No reference signs in the claims should be considered as limiting the scope of the claims to the identity of the reference signs therein.

[0110] Furthermore, it should be understood that although the description is made on the basis of the embodiments, not every embodiment contains only one independent technical solution, and the description of the specification is only for the sake of clarity, and those skilled in the art should consider the specification as a whole, and the technical solutions in each embodiment can also be appropriately combined to form other embodiments that those skilled in the art can understand.

Claims

1. A method for splicing multiple network paths across isolated devices, characterized in that, The method comprises the following steps: Step 1: open corresponding network protocols for all devices in the multi-section network across the isolation device, and input the account and password into the system; Step 2: configure a periodic collection task in the system, and after starting the task, collect the routing information of all network devices concurrently; Step 3: adapt the collected routing information and store it in the database, retrieve the A-end and Z-end device IP addresses of the path as needed, then perform end-to-end path retrieval and splicing, and display the path; The specific process of retrieving the A-end and Z-end device IP addresses of the path as needed, then performing end-to-end path retrieval and splicing is as follows: (1) initial input: A-end device IP address A_IP, Z-end device IP address Z_IP; (2) determine the PE devices of the two-end devices: perform IP management retrieval on A_IP and Z_IP to confirm whether they are PE devices, if the A-end or Z-end is not a direct PE device, find the corresponding CE device according to the association of the IP address and the subnet mask, and then associate the CE device to the corresponding PE device; (3) recursive search process: start from the PE device PE_A corresponding to the A-end, search all directly connected network devices, for each directly connected device, judge whether it is a PE device or an edge device: if it is a PE device and the target PE device PE_Z, the path splicing is completed; if it is an edge device, record the edge device and continue to search the connected devices from the device; (4) path splicing: arrange all the edge devices recorded in the recursive process in the order of access to form a complete network path, ensuring that the path passes through all intermediate edge devices from the A-end PE device to the Z-end PE device; (5) exception handling: if the path connecting to the Z-end PE device cannot be found in the recursive process, mark the path splicing as failed and prompt the relevant exception information.

2. The cross-isolation device multi-segment network path stitching method of claim 1, wherein, The network is a private network within a unit or organization.

3. The method of claim 1, wherein, The devices include routers, switches, firewalls and servers.

4. The method of claim 1, wherein, The protocol is snmp protocol, telnet protocol or ssh protocol.

5. The method of claim 1, wherein, The recursive search uses a depth-first search algorithm, and the recursive depth is limited to prevent infinite recursion. In the recursive process, the IP of the visited device is recorded to avoid repeated access and prevent circular paths.

6. The method of claim 1, wherein, The (3) comprises: According to the IP address of each end-end device, it is judged whether the IP is managed, if it is managed, it is judged whether the end is a CE device, if it is not managed, it is judged whether the end can be associated to the CE device through the IP address and the subnet mask; If the end is a CE device or the end can be associated to the CE device through the IP address and the subnet mask, it is judged whether the opposite end of the link of the end CE device has a corresponding PE device, if yes, the link local side is the end network element device, the local CE device and the local PE device, otherwise, the link local side is the end network element device and the local CE device, the network element device includes but is not limited to routers, switches, firewalls and servers; If the end is not a CE device, the link local side is the end network element device and the local CE device. If the local end cannot be associated with the CE device through the IP address and subnet mask, the link local side is the local end.

7. The cross-isolation device multi-segment network path stitching method of claim 6, wherein, The local side includes the left side and the right side, corresponding to the A end and the Z end respectively.

8. The cross-isolation device multi-segment network path stitching method of claim 6, wherein, The judgment whether the opposite end of the local end CE device link has a corresponding PE device includes: Find the optimal active link to determine the opposite end PE device through link delay and traffic analysis, the process is as follows: (1) Data collection: Collect real-time delay and traffic data of each link regularly through SNMP, Telnet or SSH protocol, store the collected data for subsequent analysis and decision-making; (2) Data analysis: Link delay analysis: calculate the average delay value of each link, identify the link with the smallest delay; Traffic analysis: evaluate the current traffic load of each link, identify the link with the smallest traffic; (3) Optimal link selection algorithm: Select the optimal link by using the optimal link selection algorithm, and dynamically adjust the link selection strategy based on real-time monitoring and historical data to adapt to network load changes; (4) Path determination and refinement: Determine the opposite end device IP of the PE device according to the selected optimal link; (5) Condition judgment: When at least one link that meets the low delay and low traffic standards can be identified through the above analysis, and there is a corresponding PE device, it is confirmed that there is a corresponding PE device; When the delay or traffic of all links exceeds the set threshold, or the corresponding PE device cannot be determined, mark the path splicing as failed, and prompt the network administrator to check.

Images