A system and method for implementing multiple load balancing device traffic maps

Abstract

The application relates to the technical field of information display, and provides a system and method for realizing a plurality of load balancing equipment flow maps, which comprise a collection module, an improved cognitive module, an automatic matching module for different load balancing and a network flow-based map module; the collection module reads configuration information of relevant load balancing equipment, supports a plurality of equipment types such as F5 and A10; the collection module saves the configuration information in a LOG mode and downloads relevant certificate files to a local place, and the collection module can quickly acquire configuration data of a plurality of load balancing equipment; the improved cognitive module is adapted to a plurality of load balancing equipment environments, identifies and processes 4-layer and 7-layer configuration information, and the improved cognitive module newly adds LTM and SLB modules to classify and process configuration fields. The application can enhance the management capability of a plurality of load balancing configurations.

Description

Technical Field

[0001] The present invention relates to the field of information display technology, and in particular to a system and method for realizing traffic maps of multiple load balancing devices. Background Art

[0002] Currently, although each load balancing vendor has an independent interface for display technology, there is no centralized related system for unified management and configuration. Therefore, each configuration is highly independent and the logical nesting is different. As a result, the configuration cannot be displayed or managed uniformly. When there are many devices, there is no global traffic map perspective for devices passing through multiple load balancing, which directly increases the difficulty of management.

[0003] According to the query of the existing relevant patent publication number CN114285719A, the name: "Strategy method and system for centralized identification of different types of network devices in multiple IDC environments" solves the configuration display problem of different types of network devices, but its patent only solves the basic configuration identification of firewalls and a load balancing method.

[0004] However, there are still technical challenges in individually identifying and processing the configurations of multiple load balancing devices and drawing traffic maps. Current solutions are not oriented towards multiple types of load balancing, nor do they effectively address the subdivision function of processing the 4-layer and 7-layer rules contained in load balancing. There are also no strategic methods and systems for processing the network maps of load-balancing devices. This makes it very difficult for users to manage the configurations of multiple types of load balancing devices and manage the queries of paths passing through multiple types of load balancing devices. Summary of the Invention

[0005] In response to the above problems, the present invention provides a system and method for implementing traffic maps of multiple load balancing devices.

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

[0007] A system and method for implementing traffic maps for multiple load balancing devices, including a collection module, an improved cognitive module, an automatic matching module for different load balancing devices, and a map module based on network traffic;

[0008] The acquisition module reads the configuration information of relevant load balancing devices and supports multiple device types, such as F5 and A10. The acquisition module uses LOG mode to save the configuration information and downloads relevant certificate files to the local computer. The acquisition module can quickly obtain the configuration data of various load balancing devices.

[0009] The improved cognitive module is adapted to a variety of load balancing device environments, identifies and processes 4-layer and 7-layer configuration information. The improved cognitive module adds LTM and SLB modules, classifies and processes configuration fields, and splits them into valid information of 7-layer and 4-layer loads; the improved cognitive module improves the ability to interpret load balancing configurations, supports multiple types of load balancing devices, and realizes refined management of configurations.

[0010] Preferably, the automatic matching module uniformly processes the L4 and L7 configuration logics of two different load balancing devices. The automatic matching module converts the configuration logics of the two load balancing devices into a unified format through an automatic matching algorithm to facilitate subsequent processing. The automatic matching module simplifies the complexity of configuration management and improves management efficiency.

[0011] Preferably, the network traffic-based map module draws a network traffic-based map according to the processed configuration information to display the traffic path of the load balancing device. The network traffic-based map module adopts XYZ loop logic, takes L4 as the basic dimension and L7 as the enhanced dimension, and constructs a three-dimensional traffic map. The network traffic-based map module intuitively displays the traffic path of the load balancing device, which is convenient for managers to quickly locate problems and optimize the network structure.

[0012] A method for implementing a system for traffic mapping of multiple load balancing devices, comprising the following steps:

[0013] S1: Collection load balancing configuration:

[0014] Use Python scripts to collect configuration data for load balancing devices and adopt corresponding collection strategies based on the device model;

[0015] S2: Use the cognitive module to process the collected configuration data:

[0016] Read the configuration information in the local file and classify the configuration fields using the cognitive module;

[0017] S3: The automatic matching module logically integrates the processed load balancing configuration:

[0018] Use automatic matching algorithms to unify L4 and L7 configurations, eliminating configuration differences between different load balancing devices;

[0019] S4: Draw the actual network traffic map:

[0020] According to the processed configuration information, a drawing module is used to draw a map based on network traffic.

[0021] Preferably, in step S1, the collected configuration information is saved as a local file for subsequent processing.

[0022] Preferably, in step S2, the configuration information is split into two categories, L4 and L7, and stored in corresponding data structures respectively, and the L7 template and its related attributes are specially processed to support more complex configuration logic.

[0023] Preferably, in step S3, the processed configuration information is integrated into a unified logical format to facilitate subsequent drawing of a traffic map.

[0024] Preferably, in step S4, XYZ loop logic is adopted, with L4 as the basic dimension, L7 as the enhanced dimension, and the Y axis representing related information such as service groups.

[0025] Preferably, in step S4, the traffic path of the load balancing device is displayed on the map, including information such as the load policy name, service group, service member and L7 template.

[0026] The beneficial effects of the present invention are:

[0027] 1. Adapt to multiple load balancing devices. The original load balancing configuration can only support multiple types of devices, and the L4 and L7 modules are introduced to strengthen the actual configuration, enhancing the management capabilities of multiple types of load balancing configurations.

[0028] 2. A network map that can display the network traffic processing path based on the configuration and integrate multiple load balancing configurations makes it more efficient for maintainers to query the traffic processing of a certain device in the relevant logic. The emergence of a centralized network map fundamentally solves the problem of difficulty in querying device traffic after it passes through multiple load balancing. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 Flowchart of the present invention. DETAILED DESCRIPTION

[0030] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0031] In the description of the present invention, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "up", "down", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", "clockwise", "counterclockwise" and the like to indicate directions or positional relationships based on the directions or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific direction, be constructed and operate in a specific direction, and therefore should not be understood as limiting the present invention.

[0032] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the said features. In the description of the present invention, "multiple" means two or more, unless otherwise clearly and specifically defined. In addition, the terms "installed", "connected", and "connected" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be an indirect connection through an intermediate medium, or it can be a communication between the two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to the specific circumstances.

[0033] Reference Figure 1 , a system and method for implementing traffic maps of multiple load balancing devices, including a collection module, an improved cognitive module, an automatic matching module for different load balancing, and a map module based on network traffic;

[0034] The acquisition module reads the configuration information of relevant load balancing devices and supports multiple device types, such as F5 and A10. The acquisition module uses the LOG mode to save the configuration information and download the relevant certificate files to the local computer. The acquisition module can quickly obtain the configuration data of various load balancing devices. This module is used to read the device configuration of relevant load balancing devices. Developers can use the simplest LOG mode to save it, and the relevant certificate files can be downloaded directly to the local computer.

[0035] The improved cognitive module is adapted to various load balancing device environments, identifies and processes 4-layer and 7-layer configuration information, the improved cognitive module adds LTM and SLB modules, classifies and processes configuration fields, and splits into 7-layer and 4-layer load effective information; the improved cognitive module improves the interpretation ability of load balancing configuration, supports various types of load balancing devices, realizes fine management of configuration, and the method in the current solution is based on network equipment, cannot identify non-LTM load balancer, and does not integrate L7 related functions, in the scheme, the load balancer is separately faced, the logic processing of the configuration is more complex, the LTM load balancing is integrated, the traditional F5 device is added, the SLB series load balancing is added, and the A10 series is added. At the same time, the effective information related to 7-layer and 4-layer is identified, and the configuration interpretation ability of load balancing is further improved, the ltm and SLB modules in the cognitive module need to be operated, and the main attribute classification is two kinds:

[0036] The first kind is the LTM module, and the main fields are: template type, name, Switching Type, MatchString, Match String, Service Group, Action, and the main key fields are: virtual, ip-protocol, destination, pool, ltm pool, members, ratio, priority-group, and policies.

[0037] The second kind is the SLB module, and the main fields are: slb template, host-switching, equals, service-group, and the main key fields are: virtual-server, port, service-group, method, member, and priority.

[0038] Through the processing of the fields, the identification module in the cognitive module is synchronized and split into 7-layer and 4-layer load effective information.

[0039] Further, the automatic matching module uniformly processes the L4 and L7 configuration logic of two different load balancing devices, the automatic matching module converts the configuration logic of two load balancing devices into a unified format through an automatic matching algorithm, which is convenient for subsequent processing, the automatic matching module simplifies the complexity of configuration management and improves management efficiency, through the matching module, the L4 configuration logic of two different load balancing devices is uniformly processed into the same kind of logic, the L7 configuration logic of two different load balancing devices is uniformly processed into the same kind of logic. The processed two L4 and L7 logics are spliced into the same kind of logic.

[0040] Example: Processing based on the LTM load balancer configuration snippet

[0041] When processing Layer 4 load information, the following logic is used:

[0042] ltm virtual tyzb_HTTPS{ / / Load policy name

[0043] ip-protocol tcp / / load protocol

[0044] destination 11.81.12.129:https / / load IP / port

[0045]

[0046]

[0047] Furthermore, the network traffic-based map module draws a network traffic-based map according to the processed configuration information to display the traffic path of the load balancing device. The network traffic-based map module adopts XYZ loop logic, takes L4 as the basic dimension and L7 as the enhanced dimension, to construct a three-dimensional traffic map. The network traffic-based map module intuitively displays the traffic path of the load balancing device, which is convenient for managers to quickly locate problems and optimize the network structure. In order to more efficiently manage the load balancing configuration, ordinary modules can only roughly cross-display relevant information based on the XY point part, which does not conform to the actual load balancing environment. In order to be able to efficiently only target the load balancing configuration and achieve tracking capabilities, it is necessary to process based on the network map. After combining the previous two modules to classify multiple types of load balancing data, the data based on the network map is displayed. First, the grid distribution is arranged based on the load policy name according to the 4-layer dimension, including the main name, IP, service group, service member information, and other parameters are associated and displayed. At the same time, the second layer uses L7 data to further associate the L4 data of the first layer, and adds the Z-axis dimension based on L7 from the X and Y of L4. The Z-axis will take precedence over the Y-axis data processing in the configuration and needs to be sorted by priority. In addition, due to the large number of Z rules, it can handle more complex scenarios. Z has the development of Z-layer loops. The actual configuration of path tracing shows the XYZ loop logic: X is the load name, Yn is the service group, and data request X enters Y. However, after Z is added, some data requests from X will flow into Z first, and Z can be superimposed on Zn. Z can also return for processing without flowing into Y. Zn may also point to X. In addition, the 7-layer data logic processing can only process the data of the current request fragment. If the other half is not hit, the remaining irregular data will flow into Y. This is similar to a bottom-line policy, so logically all paths need to be traced. Based on this feature, XYZ is used for tracking to generate a unified network map.

[0048] Example: XY map

[0049] Display 1:

[0050] tyzb_HTTPS / / Load policy name

[0051] 101.89.132.129:https / / Load IP / Port

[0052] TYZB-https / / Service Group

[0053] 172.18.250.10:http / / service member

[0054] 172.18.250.11:http / / service member

[0055] Display N:

[0056] Tyzb1_HTTPS / / Load strategy name

[0057] 101.89.132.130:https / / Load IP / Port

[0058] TYZB-https / / Service Group

[0059] 172.18.250.13:http / / service member

[0060] 172.18.250.14:http / / service member

[0061] After adding the Z map:

[0062] Display 1:

[0063] tyzb_HTTPS / / Load policy name

[0064] 101.89.132.129:https / / Load IP / Port

[0065] TYZB-https / / Service group / / Mask display service mode

[0066] 172.18.250.10:http / / Service member / / Mask display weight

[0067] 172.18.250.11:http / / service member

[0068] http_gw_vms / / L7 template name

[0069] 172.18.250.20: http / / service member, belonging to i.vms.tv189.com service group

[0070] 172.18.250.20: http / / service member, belonging to i.vms.tv189.com service group

[0071] i2.vms.tv189.com

[0072] 172.18.250.20: http / / service member, belonging to i2.vms.tv189.com service group

[0073] i2.vms.tv189.com / / L7 service group / / mask layer according to action backtracking rules and mode, when the case has no service member, display code side processing logic, can be ringed other Z or Z itself, or may be ringed to other X.

[0074] A method for implementing a system of a plurality of load balancing device traffic maps, comprising the steps of:

[0075] S1: Collecting load balancing configuration:

[0076] The load balancing device is configured and collected using a Python script, and the corresponding collection strategy is adopted according to the device model; the developer uses the py script to collect the configuration of the load balancing, which mainly needs to be judged according to the device model, the collection of A10 is identified by taking the carriage return symbol slb open field, the end, and each new field under the field is marked as a new row field, then each row field is read and columned until the end. The template of F5 is to take the ltm policy field as the start and the end, and each new field in the field is marked as a new row field, then each row field is read and columned until the end. The required resources are saved, and the local file is generated. The subsequent user cognitive module processes the configuration data;

[0077] S2: Using the cognitive module to process the collected configuration data:

[0078] Read the configuration information in the local file, and use the cognitive module to classify and process the configuration field; the developer uses the cognitive module to classify and process the 4-layer information and 7-layer information of two kinds of load balancing configurations, which includes the following operation methods: reading the collected configuration to generate 16 kinds of configuration information that can be classified, which are 4-layer configuration set and 7-layer configuration set of two kinds of load balancing, containing 6 categories, mainly for load strategy name, service group, member and their associated attributes; 7-layer configuration set, containing 2 categories, mainly for L7 template and its associated attributes;

[0079] S3: The automatic matching module logically integrates the processed load balancing configuration:

[0080] Use the automatic matching algorithm to unify the L4 and L7 configurations to eliminate the configuration differences between different load balancing devices; developers use the automatic matching module to unify the configurations of the two types of load balancing in S2 into eight categories for L4 and L7 data integration and processing, which includes the following operations:

[0081] Unify two different load balancing L4 configurations into one logic.

[0082] Unify two different load balancing L7 configurations into one logic.

[0083] Unify the two already unified L4 and L7 configurations into one logic;

[0084] S4: Draw the actual network traffic map:

[0085] According to the processed configuration information, the drawing module is used to draw a map based on network traffic. Developers use the drawing module to draw a network map, which includes the following operation methods

[0086] XY is drawn based on L4 basic data. X is the load policy name, and Y is the L4-related entity. Each XY is a square, and all XY information is displayed.

[0087] Insert Z based on the XY information, with Z as the main body of L7, and arrange the traffic paths in the order of Z1 to ZN to Y. When Z points to other Y or Z, tracking processing is performed, and Z will also point to X, actually tracing the logical closed loop and finally forming the actual network map.

[0088] Furthermore, in step S1, the collected configuration information is saved as a local file for subsequent processing.

[0089] Furthermore, in step S2, the configuration information is split into two categories, L4 and L7, and stored in corresponding data structures respectively. The L7 template and its related attributes are specially processed to support more complex configuration logic.

[0090] Furthermore, in step S3, the processed configuration information is integrated into a unified logical format to facilitate subsequent drawing of a traffic map.

[0091] Furthermore, in step S4, XYZ loop logic is adopted, with L4 as the basic dimension, L7 as the enhanced dimension, and the Y axis representing related information such as service groups.

[0092] Furthermore, in step S4, the traffic path of the load balancing device is displayed on the map, including information such as the load policy name, service group, service member, and L7 template.

[0093] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A system for implementing traffic maps of multiple load balancing devices, characterized in that: It includes an acquisition module, an improved cognitive module, an automatic matching module for different load balancing, and a map module based on network traffic; The acquisition module reads the configuration information of the relevant load balancing devices and supports multiple device types; the acquisition module uses the LOG mode to save the configuration information and download the relevant certificate files to the local computer. The acquisition module can quickly obtain the configuration data of various load balancing devices; The improved cognitive module adapts to various load balancing device environments, identifies and processes Layer 4 and Layer 7 configuration information. The improved cognitive module adds LTM and SLB modules to classify and process configuration fields, splitting them into valid Layer 7 and Layer 4 load information. The improved cognitive module improves the ability to interpret load balancing configurations, supports various types of load balancing devices, and enables refined configuration management. The automatic matching module unifies the L4 and L7 configuration logics of two different load balancing devices. The automatic matching module converts the configuration logics of the two load balancing devices into a unified format through an automatic matching algorithm to facilitate subsequent processing. The automatic matching module simplifies the complexity of configuration management and improves management efficiency. The network traffic-based map module draws a network traffic-based map based on the processed configuration information to display the traffic path of the load balancing device. The network traffic-based map module adopts XYZ loop logic, takes L4 as the basic dimension and L7 as the enhanced dimension, and constructs a three-dimensional traffic map. The network traffic-based map module intuitively displays the traffic path of the load balancing device, which is convenient for managers to quickly locate problems and optimize the network structure.

2. A method for implementing a system for traffic mapping of multiple load balancing devices according to claim 1, characterized in that: The following steps are involved: S1: Collection load balancing configuration: Use Python scripts to collect configuration data for load balancing devices and adopt corresponding collection strategies based on the device model; S2: Use the cognitive module to process the collected configuration data: Read the configuration information in the local file and classify the configuration fields using the cognitive module; S3: The automatic matching module logically integrates the processed load balancing configuration: Use automatic matching algorithms to unify L4 and L7 configurations, eliminating configuration differences between different load balancing devices; S4: Draw the actual network traffic map: According to the processed configuration information, a drawing module is used to draw a map based on network traffic.

3. The method according to claim 2, characterized in that In step S1, the collected configuration information is saved as a local file for subsequent processing.

4. The method according to claim 2, characterized in that In step S2, the configuration information is split into two categories, L4 and L7, and stored in corresponding data structures respectively. The L7 template and its related attributes are specially processed to support more complex configuration logic.

5. The method according to claim 2, characterized in that In step S3, the processed configuration information is integrated into a unified logical format to facilitate subsequent drawing of the traffic map.

6. The method according to claim 2, characterized in that In step S4, XYZ loop logic is adopted, with L4 as the basic dimension, L7 as the enhanced dimension, and the Y axis representing the service group.

7. The method according to claim 2, characterized in that In step S4, the traffic path of the load balancing device is displayed on the map, including the load policy name, service group, service member and L7 template.

Images