Cross-isolation equipment multi-segment network path splicing method

Abstract

The invention discloses a cross-isolation equipment multi-segment network path splicing method, which comprises the following steps of: 1, opening corresponding network protocols for all equipment in a cross-isolation equipment multi-segment network, and inputting accounts and passwords into a system; 2, configuring a periodic collection task in the system, and after the task is started, carrying out concurrent collection on routing information of all network devices; 3, the collected routing information is adapted and stored in a database, the IP addresses of the end and Z end devices of the path are retrieved according to needs, end-to-end path retrieval and splicing are carried out, and the path is displayed. Based on the association from the CE device to the PE cross-isolation device, multi-segment network path splicing of the cross-isolation device is realized, all links between the PE and the CE are acquired, the optimal active link is searched through the link time delay and the flow to determine the opposite-end PE device, and the problem that the cross-isolation device network path cannot be completely retrieved by a general network tool is solved.

Description

Technical Field

[0001] The present invention belongs to the technical field of network path detection, and in particular relates to a method for splicing multiple network paths across isolated devices. Background Art

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

[0003] The basic working principle of the traceroute network diagnostic tool is as follows: First, a network data packet is sent to the destination address. This data packet is usually an ICMP packet, that is, an Internet Control Message Protocol packet, and its Time-to-Live (TTL) field is set to 1. TTL is a mechanism used to prevent data packets from looping infinitely in the network. Every time a data packet passes through a network node (such as a router or firewall), the TTL value is reduced by 1. 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 traceroute receives the "ICMP timeout" message, it knows the address of the first network node, that is, the node that sent the "ICMP timeout" message. Then, it sends a new data packet, but this time sets the TTL value to 2. Traceroute continues this process, increasing the TTL value and sending new data packets each time, until the data packet reaches the destination address. In this way, it can track and display all the network nodes that the data packet passes through. Traceroute usually sends three data packets at each TTL value so that it can display the average delay time of each step. If a node does not respond, traceroute will display a timeout.

[0004] Traceroute can be used to determine the path of a data packet in the network, which is very effective for diagnosing network problems such as network delays and path loops. However, trace route also has its limitations. For example, some routers or firewalls may block "traceroute" packets, which will result in incomplete path information. In addition, some networks may use asymmetric routing strategies, resulting in a return path that is different from the sending path, which cannot be captured by "traceroute". In a network using multi-path routing (ECMP, Equal Cost Multipath), different "traceroute" probes may take different paths, which may lead to inconsistent results. Summary of the invention

[0005] The technical problem to be solved by the present invention is to provide a method for splicing multiple network paths across isolated devices in view of the deficiencies of the above-mentioned prior art, which can realize the restoration of the network path in a network environment blocked by the isolated device.

[0006] In order to achieve the above technical objectives, the technical solution adopted by the present invention is:

[0007] A method for splicing multiple network paths across isolated devices includes the following steps:

[0008] Step 1: Enable the corresponding network protocol for all devices in the multi-segment network across isolated devices, 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 retrieve the IP addresses of the A-end and Z-end devices of the path as needed, and then perform end-to-end path retrieval and splicing, and display the path.

[0011] To optimize the above technical solutions, the specific measures taken also include:

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

[0013] The above-mentioned equipment includes routers, switches, firewalls and servers.

[0014] The above-mentioned protocol is the snmp protocol, the telnet protocol or the ssh protocol.

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

[0016] (1) Initial input:

[0017] A-side device IP address A_IP, Z-side device IP address Z_IP

[0018] (2) Determine the PE devices at both ends:

[0019] Perform IP management search for 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 CE device to which it belongs based on the IP address and subnet mask association, and then associate it with the corresponding PE device through the CE device;

[0020] (3) Recursive search process:

[0021] Starting from the PE device PE_A corresponding to the A end, search for all directly connected network devices. For each directly connected device, determine 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, record the edge device and continue to search for its connected devices from the device downward;

[0022] (4) Path splicing:

[0023] Arrange all edge devices recorded in the recursive process in the order of access to form a complete network path, ensuring that the path starts from the A-end PE device, passes through all intermediate edge devices, and finally reaches the Z-end PE device;

[0024] (5)Exception handling:

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

[0026] The above recursive search uses a depth-first search algorithm and limits the recursive depth to prevent infinite recursion. During the recursive process, the IP addresses of the devices that have been visited are recorded to avoid repeated visits and prevent circular paths.

[0027] The above (3) includes:

[0028] According to the IP address of each end device, check whether the IP is managed. If it is managed, determine whether the local end is a CE device. If it is not managed, determine whether the local end can be associated with the CE device through the IP address and subnet mask;

[0029] If the local end is a CE device or the local end can be associated with the CE device through the IP address and subnet mask, then determine whether the other end of the CE device link at the local end has a corresponding PE device. If so, the local side of the link is the local network element device, the local CE device, and the local PE device. Otherwise, the local side of the link is the local network element device and the local CE device. The network element device includes but is not limited to routers, switches, firewalls, and servers.

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

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

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

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

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

[0035] (1) Data collection:

[0036] Regularly collect real-time delay and traffic data of each link through SNMP, Telnet or SSH protocol, and store the collected data for subsequent analysis and decision-making;

[0037] (2) Data analysis:

[0038] Link delay analysis: Calculate the average delay of each link and identify the link with the minimum delay;

[0039] Traffic analysis: Evaluate the current traffic load of each link and identify the link with the least 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 changes in network load;

[0042] (4) Path determination and refinement:

[0043] Determine the peer device IP of the PE device based on the selected optimal link;

[0044] (5) Conditional judgment:

[0045] When at least one link that meets the low latency and low traffic standards can be identified through the above analysis, and a 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, the path splicing failure is marked and the network administrator is prompted to check.

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

[0048] The present invention is based on the association between CE devices and PE across isolation devices, realizes the splicing of multiple network paths across isolation devices, collects all links between PE and CE, and searches for the optimal active link through link delay and traffic to determine the opposite PE device, solving the problem that general network tools cannot retrieve the complete network path across isolation devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 It is a flow chart of the method for splicing multiple network paths across isolation devices in the present invention;

[0050] Figure 2It is the key algorithm for end-to-end path splicing in the present invention;

[0051] Figure 3 This is a screenshot of the interface of end-to-end path splicing in the present invention. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0053] Although the steps in the present invention are arranged with numbers, they are not used to limit the order of the steps. Unless the order of the steps is clearly stated or the execution of a certain step requires other steps as a basis, the relative order of the steps can be adjusted. It is understood that the term "and / or" used in this article involves and covers any and all possible combinations of one or more of the associated listed items.

[0054] The method for splicing multiple network paths across isolated devices of the present invention includes the following steps for splicing multiple network paths across isolated devices: Figure 1 As shown, including:

[0055] Step 1: Enable the corresponding network protocol for all devices in the multi-segment network across isolated devices, and enter the account and password into the system;

[0056] First, you need to enable the SNMP protocol for all CE and PE devices in the entire network, and enter the SNMP account and password into the system.

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

[0058] The devices include routers, switches, firewalls and servers.

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

[0060] That is, the present invention is applicable to private networks within units or organizations, and network devices include but are not limited to routers, switches, firewalls, servers, etc., and open snmp protocols, telnet and ssh protocols and their related ports.

[0061] Isolation devices are an important security tool in the network. They can provide protection for the network from 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 to pass based on specific rules. These rules can be based on IP addresses, port numbers, protocol types, etc.

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

[0064] Intrusion Detection System / Intrusion Prevention System (IDS / IPS): These systems monitor network traffic, looking for malicious behavior or attack patterns. If they detect this activity, they can alert administrators or automatically take action to block 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, and after starting the task, concurrently collect the routing information of all network devices;

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

[0068] (1) Initial input:

[0069] A-side device IP address (A_IP)

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

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

[0072] Perform IP management search on A_IP and Z_IP to confirm whether they are PE devices.

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

[0074] (3) Recursive search process:

[0075] Start from the PE device (PE_A) corresponding to end A and search for 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 splicing is completed.

[0078] If it is an edge device: Record the edge device and continue from it downward to find the devices it is connected to.

[0079] Furthermore, a depth-first search (DFS) algorithm is used, and the recursion depth is limited (as set in the configuration, for example, graphDepth=15) to prevent infinite recursion.

[0080] During the recursive process, the IP addresses of devices that have been accessed are recorded to avoid repeated access and prevent circular paths.

[0081] (4) Path splicing:

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

[0083] Ensure that the path from the A-end PE device passes through all intermediate edge devices and finally reaches 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 recursive process, the path splicing failure is marked and related exception information is prompted.

[0086] Then enter the A and Z end device IPs of the paths you need to retrieve on the page, and you can perform path retrieval and display the retrieved paths.

[0087] like Figure 2 and Figure 3 As shown, the key algorithm steps of end-to-end path splicing.

[0088] 1) Enter the IP addresses of the devices at both ends of A and Z;

[0089] 2) First check whether the IP address is managed based on the IP address;

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

[0091] 4) Determine whether the other end of the CE device link has a corresponding PE device;

[0092] 5) Recursively search the PE devices to obtain all the devices between the PE devices at both ends;

[0093] 6) Perform path splicing for edge devices, CE devices, and PE devices.

[0094] In summary, the present invention is based on the association from CE devices to PE across isolation devices, realizes the splicing of multiple network paths across isolation devices, collects all links between PE and CE, and searches for the optimal active link through link delay and traffic to determine the opposite PE device, thereby solving the problem that general network tools cannot fully retrieve the network path across isolation devices.

[0095] The process of finding the optimal active link based on link delay and traffic to determine the peer PE device is as follows:

[0096] (1) Data collection:

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

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

[0099] (2) Data analysis:

[0100] Link delay analysis: Calculate the average delay of each link and identify the link with the minimum delay.

[0101] Traffic analysis: Evaluate the current traffic load on each link and identify the link with the least traffic.

[0102] (3) Optimal link selection algorithm:

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

[0104] (4) Path determination and refinement:

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

[0106] (5) Conditional judgment:

[0107] · The corresponding PE device exists: When at least one link that meets the low latency and low traffic standards can be identified through the above analysis, and a corresponding PE device exists, the system confirms that the corresponding PE device exists.

[0108] No corresponding PE device exists: When the delay 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 splicing failure and prompts the network administrator to check.

[0109] It will be apparent to those skilled in the art that the invention is not limited to the details of the exemplary embodiments described above and that the invention can be implemented in other specific forms without departing from the spirit or essential features of the invention. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description, and it is intended that all variations falling within the meaning and scope of the equivalent elements of the claims be included in the invention. Any reference numeral in a claim should not be considered as limiting the claim to which it relates.

[0110] In addition, it should be understood that although the present specification is described according to implementation modes, not every implementation mode contains only one independent technical solution. This description of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment may also be appropriately combined to form other implementation modes that can be understood by those skilled in the art.

Claims

1. A method for splicing multiple network paths across isolated devices, characterized in that: The following steps are involved: Step 1: Enable the corresponding network protocol for all devices in the multi-segment network across isolated devices, and enter the account and password into the system; Step 2: Configure a periodic collection task in the system, and after starting the task, concurrently collect the routing information of all network devices; Step 3: Adapt the collected routing information and store it in the database, and retrieve the IP addresses of the A-end and Z-end devices of the path as needed, and then perform end-to-end path retrieval and splicing, and display the path.

2. The method for splicing multi-segment network paths across isolated devices according to claim 1, characterized in that: The network is a private network within a unit or organization.

3. The method for splicing multi-segment network paths across isolated devices according to claim 1, characterized in that: The devices include routers, switches, firewalls and servers.

4. The method for splicing multi-segment network paths across isolated devices according to claim 1, characterized in that: The protocol is the snmp protocol, the telnet protocol or the ssh protocol.

5. The method for splicing multi-segment network paths across isolated devices according to claim 1, characterized in that: The specific process of retrieving the IP addresses of the devices at the A and Z ends of the path as needed and then performing end-to-end path retrieval and splicing is as follows: (1) Initial input: A-side device IP address A_IP, Z-side device IP address Z_IP (2) Determine the PE devices at both ends: Perform IP management search for 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 CE device to which it belongs based on the IP address and subnet mask association, and then associate it with the corresponding PE device through the CE device; (3) Recursive search process: Starting from the PE device PE_A corresponding to the A end, search for all directly connected network devices. For each directly connected device, determine 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, record the edge device and continue to search for its connected devices from the device downward; (4) Path splicing: Arrange all edge devices recorded in the recursive process in the order of access to form a complete network path, ensuring that the path starts from the A-end PE device, passes through all intermediate edge devices, and finally reaches the Z-end PE device; (5)Exception handling: If the path connected to the Z-end PE device cannot be found during the recursive process, the path splicing failure is marked and relevant abnormal information is prompted.

6. The method for splicing multi-segment network paths across isolated devices according to claim 5, characterized in that: The recursive search uses a depth-first search algorithm and limits the recursive depth to prevent infinite recursion. During the recursive process, the IP addresses of the devices that have been visited are recorded to avoid repeated visits and prevent circular paths.

7. The method for splicing multi-segment network paths across isolated devices according to claim 5, characterized in that: The (3) includes: According to the IP address of each end device, check whether the IP is managed. If it is managed, determine whether the local end is a CE device. If it is not managed, determine whether the local end can be associated with the CE device through the IP address and subnet mask; If the local end is a CE device or the local end can be associated with the CE device through the IP address and subnet mask, then determine whether the other end of the CE device link at the local end has a corresponding PE device. If so, the local side of the link is the local network element device, the local CE device, and the local PE device. Otherwise, the local side of the link is the local 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 local end is not a CE device, the local side of the link is the local 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 local side of the link is the local end.

8. The method for splicing multi-segment network paths across isolated devices according to claim 7, characterized in that: The present side includes a left side and a right side, which correspond to the A end and the Z end respectively.

9. The method for splicing multi-segment network paths across isolated devices according to claim 7, characterized in that: The determining whether the other end of the link of the local CE device has a corresponding PE device includes: The optimal active link is found through link delay and traffic analysis to determine the peer PE device. The process is as follows: (1) Data collection: Regularly collect real-time delay and traffic data of each link through SNMP, Telnet or SSH protocol, and store the collected data for subsequent analysis and decision-making; (2) Data analysis: Link delay analysis: Calculate the average delay of each link and identify the link with the minimum delay; Traffic analysis: Evaluate the current traffic load of each link and identify the link with the least traffic; (3) Optimal link selection algorithm: 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 changes in network load; (4) Path determination and refinement: Determine the peer device IP of the PE device based on the selected optimal link; (5) Conditional judgment: When at least one link that meets the low latency and low traffic standards can be identified through the above analysis, and a corresponding PE device exists, it is confirmed that the corresponding PE device exists; When the delay or traffic of all links exceeds the set threshold, or the corresponding PE device cannot be determined, the path splicing failure is marked and the network administrator is prompted to check.

Images