CN112272206A - Management method and system of load balancing equipment - Google Patents
Management method and system of load balancing equipment Download PDFInfo
- Publication number
- CN112272206A CN112272206A CN202010990357.4A CN202010990357A CN112272206A CN 112272206 A CN112272206 A CN 112272206A CN 202010990357 A CN202010990357 A CN 202010990357A CN 112272206 A CN112272206 A CN 112272206A
- Authority
- CN
- China
- Prior art keywords
- load balancing
- health index
- equipment
- balancing device
- management platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title abstract description 168
- 238000004891 communication Methods 0.000 claims abstract description 104
- 238000000034 method Methods 0.000 claims abstract description 26
- 238000004364 calculation method Methods 0.000 claims description 24
- 238000013475 authorization Methods 0.000 claims description 12
- 230000002159 abnormal effect Effects 0.000 claims description 10
- 238000012545 processing Methods 0.000 claims description 10
- 230000009977 dual effect Effects 0.000 claims description 6
- 238000011084 recovery Methods 0.000 claims description 4
- 238000007689 inspection Methods 0.000 abstract description 7
- 238000010606 normalization Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000002349 favourable effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0823—Errors, e.g. transmission errors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1034—Reaction to server failures by a load balancer
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Computer And Data Communications (AREA)
Abstract
The application discloses a management method and a system of load balancing equipment, wherein the method comprises the following steps: deploying a management platform independent of all load balancing devices; establishing communication connection between a management platform and any load balancing device according to the communication protocol type supported by any load balancing device; storing information of the load balancing device; polling each load balancing device, polling all the load balancing devices, and determining the running state health index of any load balancing device; and managing any load balancing equipment according to the running state health index of any load balancing equipment. The system comprises: the device comprises a communication module, a storage module, an inspection module and a management module. By the method and the device, centralized management of the load balancing equipment can be realized, and management efficiency of the load balancing equipment is greatly improved.
Description
Technical Field
The present application relates to the field of computer network device management technologies, and in particular, to a method and a system for managing load balancing devices.
Background
The load balancing device is a computer network device and is used for distributing loads in a plurality of computer clusters, so that resources are optimized, the maximum throughput rate of a system is improved, and the response time is reduced. Different load balancing deployment modes all need to connect the load balancing equipment to a network of a user, and the load balancing equipment is managed in a network architecture.
At present, a method for managing load balancing equipment is generally single management. Specifically, each load balancing device is configured, and corresponding manual inspection is performed according to the configuration condition, so that normal operation of the service is ensured.
However, the current method for managing the load balancing equipment is only suitable for the situation that the number of the load balancing equipment is small, when the number of the load balancing equipment in an application scene is large, the efficiency is very low due to the fact that parameters are configured one by one, the manual inspection occupies a long time, errors are prone to being generated, and the load balancing management efficiency is low.
Disclosure of Invention
The application provides a management method and a management system of load balancing equipment, which aim to solve the problem that the management efficiency of the load balancing equipment is low in the prior art.
In order to solve the technical problem, the embodiment of the application discloses the following technical scheme:
a method of managing a load balancing device, the method comprising:
deploying a management platform independent of all load balancing devices;
establishing a communication connection between a management platform and any load balancing device according to a communication protocol type supported by any load balancing device, wherein the communication protocol type comprises: SNMP (Simple Network Management Protocol) Protocol and HTTP (HyperText Transfer Protocol) Protocol;
storing information of a load balancing device, the information comprising: configuration Information, an MIB (Management Information Base) Information Base, and API (Application Programming Interface) Interface Information;
polling each load balancing device, polling all the load balancing devices, and determining the running state health index of any load balancing device, wherein the running state health index comprises: a hardware health index, a service health index, a dual machine health index, an equipment security index, and an authorized health index;
and managing any load balancing equipment according to the running state health index of the load balancing equipment.
Optionally, the establishing a communication connection between the management platform and any load balancing device according to a communication protocol type supported by any load balancing device includes:
determining a communication protocol type supported by any load balancing equipment;
when the communication protocol type supported by any load balancing equipment is an SNMP (simple network management protocol), adding any load balancing equipment on a management platform according to a set first standardized knowledge base and a set management information base, and carrying out communication between the management platform and any load balancing equipment, wherein the first standardized knowledge base is matched with the SNMP;
when the communication protocol type supported by any load balancing device is the HTTP protocol, adding any load balancing device on the management platform according to a set second standardized knowledge base and an interface document, and carrying out communication between the management platform and any load balancing device, wherein the second standardized knowledge base is matched with the HTTP protocol.
Optionally, when the type of the communication protocol supported by any load balancing device is an SNMP protocol, adding any load balancing device to the management platform according to a set first standardized knowledge base and a set management information base, and performing communication between the management platform and any load balancing device, where the method includes:
when the communication protocol type supported by any load balancing equipment is an SNMP (simple network management protocol), judging whether a management information base matched with the load balancing equipment is prestored in the management platform;
if yes, adding any load balancing equipment on the management platform;
if not, judging that any load balancing equipment cannot be added to the management platform;
after any load balancing device is added on the management platform, reading a management information base of any load balancing device;
through the SNMP protocol between any load balancing equipment and the management platform, the management platform acquires a return value from any load balancing equipment;
reading a set first standardized knowledge base, wherein the first standardized knowledge base is matched with an SNMP protocol;
and normalizing the return value according to the first normalized knowledge base.
Optionally, when the type of the communication protocol supported by any load balancing device is an HTTP protocol, adding the any load balancing device to the management platform according to a set second standardized repository and an interface document, and performing communication between the management platform and the any load balancing device includes:
when the communication protocol type supported by any load balancing equipment is an HTTP (hyper text transport protocol), judging whether an interface document matched with the load balancing equipment is prestored in the management platform;
if yes, adding any load balancing equipment on the management platform;
if not, judging that any load balancing equipment cannot be added to the management platform;
after any load balancing device is added on the management platform, reading an interface document of any load balancing device;
through an HTTP protocol between any load balancing device and a management platform, the management platform acquires a return value from any load balancing device;
reading a set second standardized knowledge base, wherein the second standardized knowledge base is matched with an HTTP (hyper text transport protocol);
and normalizing the return value according to the second normalized knowledge base.
Optionally, polling each load balancing device to patrol all the load balancing devices and determine the operating state health index of any load balancing device includes:
according to the use conditions of the CPU, the memory and the network card of any load balancing device, calculating a hardware health index of any load balancing device by using a formula I1-100-a 1-C1-a 2-M1-a 3-N1, wherein C1 is the average utilization rate of the CPU, M1 is the utilization rate of the memory, N1 is the bandwidth utilization rate of the network card, and a1, a2 and a3 are the weights of the average utilization rate of the CPU, the memory utilization rate and the bandwidth utilization rate of the network card respectively;
according to the service information, the service pool information and the node information of any load balancing device, calculating a service health index by using a formula I2-b 1-S1 + b 2-S2 + b 3-N1, wherein S1 is the proportion of normal services, S2 is the proportion of normal service pools, N1 is the proportion of normal nodes, and b1, b2 and b3 are the weights of the proportion of normal services, the proportion of normal service pools and the proportion of normal nodes respectively;
when any load balancing device is in a dual-machine state, determining a dual-machine health index according to the dual-machine state of any load balancing device;
according to the login logs, the system logs and the service logs of any load balancing device in a set time period, calculating the device safety index of any load balancing device by using a formula I4, namely 100-c 1N 1-c 2N 2-c 3N 3, wherein N1 is the number of device login failure logs, N2 is the number of system error logs, N3 service abnormal logs, and c1, c2 and c3 are the weights of the number of the device login failure logs, the number of the system error logs and the number of abnormal logs respectively;
determining an authorized health index of any load balancing equipment according to the authorization information of any load balancing equipment;
and calculating the running state health index sum of any load balancing device by using a formula I, namely w 1I 1+ w 2I 2+ w 3I 3+ w 4I 4+ w 5I 5, wherein I1 is the hardware health index of any load balancing device, I2 is the service health index, I3 is the double-machine health index, I4 is the device safety index, I5 is the authorized health index, w1, w2, w3, w4 and w5 are weights of the hardware health index, the service health index, the double-machine health index, the device safety index and the authorized health index respectively.
Optionally, the managing, according to the operation state health index of any load balancing device, any load balancing device includes:
when the hardware health index of any load balancing equipment is less than the set hardware health index threshold, restarting the equipment or upgrading the hardware;
when the service health index of any load balancing equipment is less than the set service health index threshold value, outputting failure service and performing fault recovery on the failure service;
when the double-machine health index of any load balancing equipment is less than a set double-machine health index threshold value, fault processing is carried out on the host machine in the double machines;
when the equipment safety index of any load balancing equipment is less than the set equipment safety index threshold, updating the starting-up password and upgrading the service safety guarantee;
and when the authorized health index of any load balancing equipment is less than the set authorized health index threshold, introducing formal authorization.
Optionally, the managing any load balancing device according to the operation state health index of any load balancing device further includes:
generating a report according to the running state health index;
and displaying the report.
A management system for a load balancing device, the system comprising:
a communication module, configured to establish a communication connection between a management platform and any load balancing device according to a communication protocol type supported by any load balancing device, where the communication protocol type includes: SNMP protocol and HTTP protocol;
a storage module, configured to store information of a load balancing device, where the information includes: configuration information, an MIB information base and API interface information;
the polling module is used for polling each load balancing device, polling all the load balancing devices and determining the running state health index of any load balancing device, wherein the running state health index comprises: a hardware health index, a service health index, a dual machine health index, an equipment security index, and an authorized health index;
and the management module is used for managing any load balancing equipment according to the running state health index of any load balancing equipment.
Optionally, the communication module comprises:
a communication protocol type determining unit, configured to determine a communication protocol type supported by any load balancing device;
the SNMP protocol communication unit is used for adding any load balancing equipment on a management platform according to a set first standardized knowledge base and a set management information base when the communication protocol type supported by any load balancing equipment is an SNMP protocol, and carrying out communication between the management platform and any load balancing equipment, wherein the first standardized knowledge base is matched with the SNMP protocol;
and the HTTP protocol communication unit is used for adding any load balancing equipment on the management platform according to a set second standardized knowledge base and an interface document when the communication protocol type supported by any load balancing equipment is the HTTP protocol, and carrying out communication between the management platform and any load balancing equipment, wherein the second standardized knowledge base is matched with the HTTP protocol.
Optionally, the inspection module includes:
a hardware health index calculation unit, configured to calculate, according to usage of the CPU, the memory, and the network card of any load balancing device, a hardware health index of any load balancing device according to a formula I1 ═ 100-a1 ═ C1-a2 × M1-a3 × N1, where C1 is an average utilization rate of the CPU, M1 is a memory utilization rate, N1 is a network card bandwidth utilization rate, and a1, a2, and a3 are weights of the average utilization rate of the CPU, the memory utilization rate, and the network card bandwidth utilization rate, respectively;
a service health index calculation unit, configured to calculate a service health index according to the service information, the service pool information, and the node information of any load balancing device by using a formula I2 ═ b1 × S1+ b2 × S2+ b3 × N1, where S1 is a proportion of a normal service, S2 is a proportion of a normal service pool, N1 is a proportion of a normal node, and b1, b2, and b3 are weights of the proportion of the normal service, the proportion of the normal service pool, and the proportion of the normal node, respectively;
the double-machine health index calculation unit is used for determining a double-machine health index according to the double-machine state of any load balancing equipment when the any load balancing equipment is in the double-machine state;
the equipment safety index calculation unit is used for calculating the equipment safety index of any load balancing equipment by using a formula I4 (100-c 1N 1-c 2N 2-c 3N 3) according to the login logs, the system logs and the service logs of any load balancing equipment in a set time period, wherein N1 is the number of equipment login failure logs, N2 is the number of system error logs and the number of N3 service exception logs, and c1, c2 and c3 are the weights of the number of equipment login failure logs, the number of system error logs and the number of exception logs respectively;
the authorized health index calculation unit is used for determining the authorized health index of any load balancing equipment according to the authorization information of any load balancing equipment;
and the overall operating state health index calculation unit is used for calculating the operating state health index sum of any load balancing device by using a formula I (w 1) I1+ w 2I 2+ w 3I 3+ w 4I 4+ w 5I 5), wherein I1 is the hardware health index of any load balancing device, I2 is the service health index, I3 is the double-machine health index, I4 is the device safety index, I5 is the authorized health index, w1, w2, w3, w4 and w5 are weights of the hardware health index, the service health index, the double-machine health index, the device safety index and the authorized health index respectively.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
the method comprises the steps of deploying a management platform independent of all load balancing devices, establishing communication connection between the management platform and any one of the load balancing devices according to communication protocol types, storing information of the load balancing devices, polling all the load balancing devices in a polling mode, determining the running state health index of each load balancing device, and managing the load balancing devices according to the running state health index. In this embodiment, an independent management platform is deployed, and the management platform and each load balancing device are used to establish a communication connection, so that centralized management is realized, and the efficiency of managing the load balancing devices can be greatly improved. When the communication connection between the management platform and the load balancing equipment is established, the communication connection comprises two forms of an SNMP protocol and an HTTP protocol, most common load balancing equipment can be covered, and the compatibility is strong. In the embodiment, the automatic polling of the load balancing equipment is completed in a polling mode, so that the error is effectively reduced, the time is saved, and the management efficiency of the load balancing equipment is greatly improved. The embodiment can synthesize various running state health indexes when the load balancing equipment is patrolled and examined, and is favorable for more comprehensively and accurately acquiring the running state of each load balancing equipment, thereby providing an effective basis for subsequent management, leading the management to be more targeted and being favorable for improving the management efficiency of the load balancing equipment.
The present application further provides a management system of a load balancing device, which mainly includes: the device comprises a communication module, a storage module, an inspection module and a management module. The system can form a load balancing equipment management platform. Through the communication module, the communication connection between the load balancing equipment and the management platform can be established, the storage module stores the relevant information of the load balancing equipment, the load balancing equipment is convenient to call in time, the polling module automatically finishes polling any load balancing equipment in a polling mode, and the management efficiency can be greatly improved. In addition, the health indexes of various operation states can be integrated when the inspection module inspects the load balancing equipment, so that the operation state of each load balancing equipment can be acquired more comprehensively and accurately, the management of the load balancing equipment is more targeted, when a fault occurs, the fault reason can be determined more accurately in the shortest time, and the management efficiency of the load balancing equipment is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a management method of a load balancing device according to an embodiment of the present application;
FIG. 2 is a schematic view of a management platform structure in the present embodiment;
fig. 3 is a schematic structural diagram of a management system of a load balancing device according to an embodiment of the present application.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
For a better understanding of the present application, embodiments of the present application are explained in detail below with reference to the accompanying drawings.
Example one
Referring to fig. 1, fig. 1 is a schematic flowchart of a management method of a load balancing device according to an embodiment of the present application. As shown in fig. 1, the management method of the load balancing device in this embodiment mainly includes the following steps:
s1: a management platform is deployed that is independent of all load balancing devices.
Fig. 2 shows a schematic architecture diagram between a management platform and load balancing devices in this embodiment. By deploying the management platform independent of the load balancing equipment, a user can uniformly manage all the load balancing equipment through the independent management platform, so that centralized management is realized, and the management efficiency of the load balancing equipment is greatly improved.
S2: and establishing communication connection between the management platform and any load balancing equipment according to the communication protocol type supported by any load balancing equipment.
Wherein, the communication protocol types comprise: SNMP protocol and HTTP protocol. In this embodiment, when the communication connection between the management platform and the load balancing device is established, different communication connections are performed according to the communication protocol type supported by the current load balancing device, which is beneficial to improving compatibility.
Specifically, step S2 includes the following processes:
s21: the communication protocol types supported by any load balancing device are determined.
When the communication protocol type supported by any load balancing device is the SNMP protocol, step S22 is executed: and adding any load balancing equipment on the management platform according to a set first standardized knowledge base and a set management information base, and carrying out communication between the management platform and any load balancing equipment, wherein the first standardized knowledge base is matched with the SNMP protocol.
Specifically, step S21 includes the following process:
s221: and when the communication protocol type supported by any load balancing equipment is the SNMP protocol, judging whether a management information base matched with the load balancing equipment is prestored in the management platform.
If the management platform pre-stores a management information base matched with the load balancing device, step S222 is executed: and adding any load balancing equipment on the management platform.
If the management platform does not have a pre-stored management information base matched with the load balancing device, executing step S223: and judging that any load balancing equipment cannot be added on the management platform.
As can be seen from steps S221 to S223, for the SNMP protocol, a management information base, i.e., an MIB base, of load balancing devices of different models is built in the management platform. For example: when adding a load balancing device of A type, the management platform firstly checks whether there is a pre-stored MIB base of A type, if so, the load balancing device of A type is successfully added, otherwise, the load balancing device can not be added.
S224: after any load balancing device is added on the management platform, the management information base of any load balancing device is read.
S225: and the management platform acquires a return value from any load balancing equipment through an SNMP protocol between the load balancing equipment and the management platform.
S226: the set first standardized knowledge base is read.
In this embodiment, the first standardized repository is matched to the SNMP protocol.
S227: the return value is normalized according to a first normalized knowledge base.
As can be seen from the above steps S224 to S227, after any load balancing device is successfully added to the management platform, the management platform communicates with the load balancing devices through the network, different load balancing devices have different information returned by the management platform, and the management platform performs standardized processing on the information returned by the load balancing devices through the built-in first standardized knowledge base, so that various data have comparability through standardization, thereby improving the accuracy of the management result of the load balancing devices.
S23: when the communication protocol type supported by any load balancing device is the HTTP protocol, any load balancing device is added on the management platform according to the set second standardized knowledge base and the set interface document, communication between the management platform and any load balancing device is carried out, and the second standardized knowledge base is matched with the HTTP protocol.
When the communication protocol type supported by any load balancing device is the HTTP protocol, step S231 is executed: and judging whether an interface document matched with the load balancing equipment is prestored in the management platform.
If the management platform pre-stores the interface document matched with the load balancing device, the step S232 is executed: and adding any load balancing equipment on the management platform.
If the management platform does not have the interface document matching with the load balancing device in advance, the step S233 is executed: and judging that any load balancing equipment cannot be added on the management platform.
The principle of steps S231-S233 is the same as steps S221-S223. For the HTTP protocol, the management platform is internally provided with interface documents, namely API documents, of load balancing equipment with different models. For example: when adding a load balancing device of B model, the management platform firstly checks whether there is an interface document of pre-stored B model, if so, the addition of the load balancing device of B model is successful, otherwise, the addition is failed, and the addition of the load balancing device cannot be performed.
S234: after any load balancing device is added on the management platform, the interface document of any load balancing device is read.
S235: and the management platform acquires a return value from any load balancing equipment through an HTTP (hyper text transport protocol) between the load balancing equipment and the management platform.
S236: and reading a set second standardized knowledge base, wherein the second standardized knowledge base is matched with the HTTP protocol.
S237: and normalizing the return value according to a second normalized knowledge base.
As can be seen from the above steps S234-237, taking the API interface as an example, assuming that the API interface for the C model load balancing device to obtain the CPU utilization is/sysinfo/getcpurrate, and the return value is { "rate":0.05}, the management platform calls the/sysinfo/getcpurrate interface of the C model device, and takes out 0.05 in the return information to multiply by 100, so as to obtain the CPU utilization of 5. And if the API interface for the D model device to acquire the CPU utilization rate is/getCpu and the return is 5, the management platform calls the/getCpu interface of the D model device and directly takes the 5 in the return information to obtain that the CPU utilization rate is 5. By the method, data obtained from various types of load balancing equipment can be standardized, unified in format and contrastable, so that the accuracy of management results is improved, and the standardization facilitates generation of reports, so that the management efficiency is improved. And 0.05 is taken out from the data returned by the equipment C and then multiplied by 100, and the method for directly using the data returned by the equipment D is preset by a second standardized knowledge base.
With continued reference to fig. 1, after establishing the communication connection between the management platform and any load balancing device, step S3 is executed: and storing the information of the load balancing equipment.
The information of the load balancing device in this embodiment includes: configuration information, MIB information base, and API interface information. Wherein, API interface information includes: a URL (Uniform Resource Locator), an input argument, and a return argument.
S4: and polling each load balancing device to patrol all the load balancing devices and determine the running state health index of any one load balancing device.
Wherein the operating state health index comprises: a hardware health index, a service health index, a dual machine health index, a device security index, and an authorized health index. Specifically, step S4 includes the following processes:
s41: according to the use condition of a CPU, a memory and a network card of any load balancing device, the hardware health index of any load balancing device is calculated by using a formula I1-100-a 1C 1-a 2M 1-a 3N 1.
Wherein C1 is the average utilization rate of the CPU, M1 is the memory utilization rate, N1 is the network card bandwidth utilization rate, and a1, a2, a3 are the weights of the average utilization rate of the CPU, the memory utilization rate, and the network card bandwidth utilization rate, respectively. The method comprises the steps of firstly obtaining the use conditions of a CPU, a memory and a network card of any load balancing device, and then calculating to obtain a hardware health index by using a formula I1-100-a 1-C1-a 2-M1-a 3-N1, wherein the higher the utilization rates of the CPU, the memory and the network card are, the lower the month of the hardware health index is.
S42: and calculating a service health index according to the service information, the service pool information and the node information of any load balancing device by using a formula I2-b 1-S1 + b 2-S2 + b 3-N1.
Wherein S1 is the proportion of normal service, S2 is the proportion of normal service pool, N1 is the proportion of normal node, and b1, b2 and b3 are the weight of normal service proportion, normal service pool proportion and normal node proportion, respectively. The method comprises the steps of firstly acquiring service information, service pool information and node information of any load balancing device, and then calculating to obtain a service health index by using a formula I2-b 1-S1 + b 2-S2 + b 3-N1. The most important of which is to obtain service information, the lower the service health index when more services are not available.
S43: and when any load balancing equipment is in a dual-machine state, determining a dual-machine health index according to the dual-machine state of any load balancing equipment.
Specifically, if any load balancing device is not configured with two machines, the value of the two-machine health index I3 is 100; if any load balancing device is configured with two machines and the host machine or the standby machine is in an abnormal state, the value of I3 is 0; if any load balancing device is configured with two machines and the host machine is normal, the value of I3 is 100. Under the condition that any load balancing device is configured with two machines, if the current host machine works abnormally and the standby machine is started, the lower the service health index is.
S44: and calculating the equipment safety index of any load balancing equipment by using a formula I4-100-c 1N 1-c 2N 2-c 3N 3 according to the log, the system log and the service log of any load balancing equipment in a set time period.
Wherein, N1 is the number of device login failure logs, N2 is the number of system error logs, N3 is the number of service exception logs, and c1, c2 and c3 are the weights of the number of device login failure logs, the number of system error logs and the number of exception logs, respectively. Step S44 shows that the log, system log, and service log are obtained within a period of time, and for each log, a preset built-in pattern library is compared, and the pattern library contains information such as a keyword of an abnormal log, and if matching is successful, the log is considered to be an abnormal log. For example: if a logic failed regular expression rule exists in the built-in pattern library, all logs which can be matched with the logic failed regular expression are considered as abnormal logs, and when the proportion of the abnormal logs is higher, the safety index of the equipment is lower.
S45: and determining the authorized health index of any load balancing equipment according to the authorization information of any load balancing equipment.
In this embodiment, the authorized health index I5 of any authorized load balancing device is defined as 100, and the authorized health index I5 of any unauthorized or authorized expired load balancing device is defined as 0.
S46: calculating the running state health index sum of any load balancing equipment by using a formula I (w 1) I1+ w 2I 2+ w 3I 3+ w 4I 4+ w 5I 5,
wherein, I1 is a hardware health index of any load balancing device, I2 is a service health index, I3 is a dual-machine health index, I4 is a device safety index, I5 is an authorized health index, w1, w2, w3, w4, and w5 are weights of the hardware health index, the service health index, the dual-machine health index, the device safety index, and the authorized health index, respectively.
As can be seen from fig. 1, in this embodiment, after all the load balancing devices are inspected and the operating state health index of any one of the load balancing devices is determined, step S5 is executed: and managing any load balancing equipment according to the running state health index of any load balancing equipment.
Specifically, step S5 includes the following processes:
s51: and when the hardware health index of any load balancing equipment is less than the set hardware health index threshold value, restarting the equipment or upgrading the hardware.
S52: and when the service health index of any load balancing equipment is less than the set service health index threshold, outputting the failure service and performing fault recovery on the failure service.
S53: and when the double-machine health index of any load balancing equipment is less than the set double-machine health index threshold value, carrying out fault processing on the host machine in the double machines.
S54: and when the equipment safety index of any load balancing equipment is less than the set equipment safety index threshold, updating the starting password and upgrading the service safety guarantee.
S55: and when the authorized health index of any load balancing equipment is less than the set authorized health index threshold, introducing formal authorization.
Through the steps S51-S55, different processing can be performed according to different abnormal conditions of the health indexes of the running states, so that the load balancing equipment can be managed in a targeted mode, and the management efficiency is improved.
Further, step S5 in this embodiment further includes:
s56: and generating a report according to the running state health index.
S57: and displaying the report.
As can be seen from steps S56 and S57, after the operation state health indexes of each load balancing device are calculated, a report is generated according to the operation state health indexes, and the current overall health condition of the load balancing device and the health condition of each load balancing device are presented to the same layer of the user.
Example two
Referring to fig. 3 on the basis of the embodiments shown in fig. 1 and fig. 2, fig. 3 is a schematic structural diagram of a management system of a load balancing device according to an embodiment of the present application. As can be seen from fig. 3, the management system of the load balancing device in this embodiment mainly includes: the device comprises a communication module, a storage module, an inspection module and a management module. The communication module is configured to establish a communication connection between the management platform and any load balancing device according to a communication protocol type supported by any load balancing device, where the communication protocol type includes: SNMP protocol and HTTP protocol; the storage module is used for storing information of the load balancing equipment, and the information comprises: configuration information, an MIB information base and API interface information; and the polling module is used for polling each load balancing device, polling all the load balancing devices and determining the running state health index of any load balancing device, wherein the running state health index comprises: a hardware health index, a service health index, a dual machine health index, an equipment security index, and an authorized health index; and the management module is used for managing any load balancing equipment according to the running state health index of any load balancing equipment.
Further, the communication module includes: the device comprises a communication protocol type determining unit, an SNMP protocol communication unit and an HTTP protocol communication unit. The communication protocol type determining unit is used for determining the communication protocol type supported by any load balancing equipment; the SNMP protocol communication unit is used for adding any load balancing equipment on the management platform according to a set first standardized knowledge base and a set management information base when the communication protocol type supported by any load balancing equipment is an SNMP protocol, and carrying out communication between the management platform and any load balancing equipment, wherein the first standardized knowledge base is matched with the SNMP protocol; and the HTTP protocol communication unit is used for adding any load balancing equipment on the management platform according to a set second standardized knowledge base and an interface document when the communication protocol type supported by any load balancing equipment is the HTTP protocol, and carrying out communication between the management platform and any load balancing equipment, wherein the second standardized knowledge base is matched with the HTTP protocol.
The SNMP protocol communication unit further comprises: the device comprises a first judgment subunit, a first adding subunit, a management information base reading subunit, a first return value acquisition subunit, a first standardization knowledge base reading subunit and a first standardization processing subunit. The first judging subunit is configured to, when the communication protocol type supported by any load balancing device is an SNMP protocol, judge whether a management information base matched with the load balancing device is prestored in the management platform, if yes, add any load balancing device on the management platform, and otherwise, judge that any load balancing device cannot be added on the management platform. The first adding subunit is configured to add any load balancing device to the management platform when a management information base matched with the load balancing device is pre-stored in the management platform. And the management information base reading subunit is used for reading the management information base of any load balancing device after any load balancing device is added on the management platform. And the first return value acquisition subunit is used for acquiring the return value from any load balancing device by the management platform through an SNMP protocol between any load balancing device and the management platform. And the first standardized knowledge base reading subunit is used for reading the set first standardized knowledge base, and the first standardized knowledge base is matched with the SNMP protocol. And the first normalization processing subunit is used for normalizing the return value according to the first normalization knowledge base.
The HTTP protocol communication unit further comprises: the system comprises a first judgment subunit, a first adding subunit, an interface document reading subunit, a first return value acquisition subunit, a first standardized knowledge base reading subunit and a first standardized processing subunit. The second judging subunit is configured to, when the communication protocol type supported by any load balancing device is an HTTP protocol, judge whether an interface document matching the load balancing device is prestored in the management platform, if yes, add any load balancing device to the management platform, and otherwise, judge that any load balancing device cannot be added to the management platform. And the second adding subunit is used for adding any load balancing equipment to the management platform when the interface document matched with the load balancing equipment is prestored in the management platform. And the interface document reading subunit is used for reading the interface document of any load balancing device after any load balancing device is added on the management platform. The second return value acquisition subunit is used for acquiring the return value from any load balancing device by the management platform through an HTTP (hyper text transport protocol) between any load balancing device and the management platform; the second standardized knowledge base reading subunit is used for reading a set second standardized knowledge base, and the second standardized knowledge base is matched with the HTTP; and the second normalization processing subunit is used for normalizing the return value according to the second normalization knowledge base.
Further, the module of patrolling and examining includes: the system comprises a hardware health index calculation unit, a service health index calculation unit, a dual-computer health index calculation unit, an equipment safety index calculation unit, an authorization health index calculation unit and a general running state health index calculation unit. The hardware health index calculation unit is used for calculating the hardware health index of any load balancing device according to the use conditions of a CPU, a memory and a network card of any load balancing device by using a formula I1 (100-a 1C 1-a 2M 1-a 3N 1), wherein C1 is the average utilization rate of the CPU, M1 is the memory utilization rate, N1 is the network card bandwidth utilization rate, and a1, a2 and a3 are the weights of the average utilization rate of the CPU, the memory utilization rate and the network card bandwidth utilization rate respectively; a service health index calculation unit, configured to calculate a service health index according to service information, service pool information, and node information of any load balancing device, by using a formula I2 ═ b1 × S1+ b2 × S2+ b3 × N1, where S1 is a proportion of a normal service, S2 is a proportion of a normal service pool, N1 is a proportion of a normal node, and b1, b2, and b3 are weights of the proportion of the normal service, the proportion of the normal service pool, and the proportion of the normal node, respectively; the double-machine health index calculation unit is used for determining a double-machine health index according to the double-machine state of any load balancing equipment when any load balancing equipment is in the double-machine state; the equipment safety index calculation unit is used for calculating the equipment safety index of any load balancing equipment by using a formula I4 (100-c 1N 1-c 2N 2-c 3N 3) according to a login log, a system log and a service log of any load balancing equipment in a set time period, wherein N1 is the number of equipment login failure logs, N2 is the number of system error logs, N3 service exception logs, and c1, c2 and c3 are respectively the weights of the number of equipment login failure logs, the number of system error logs and the number of exception logs; the authorized health index calculation unit is used for determining the authorized health index of any load balancing equipment according to the authorization information of any load balancing equipment; and the overall operating state health index calculation unit is used for calculating the operating state health index sum of any load balancing device by using a formula I w 1I 1+ w 2I 2+ w 3I 3+ w 4I 4+ w 5I 5, wherein I1 is the hardware health index of any load balancing device, I2 is the service health index, I3 is the double-machine health index, I4 is the device safety index, I5 is the authorized health index, w1, w2, w3, w4 and w5 are weights of the hardware health index, the service health index, the double-machine health index, the device safety index and the authorized health index respectively.
The management module comprises: the system comprises a hardware health index management unit, a service health index management unit, a dual-computer health index management unit, an equipment safety index management unit and an authorization health index management unit. The hardware health index management unit is used for restarting the equipment or upgrading the hardware when the hardware health index of any load balancing equipment is less than a set hardware health index threshold value. And the service health index management unit is used for outputting the failure service and performing fault recovery on the failure service when the service health index of any load balancing equipment is less than the set service health index threshold value. And the double-machine health index management unit is used for processing faults of the main machines in the double machines when the double-machine health index of any load balancing equipment is less than a set double-machine health index threshold value. And the equipment safety index management unit is used for updating the boot password and upgrading the service safety guarantee when the equipment safety index of any load balancing equipment is less than the set equipment safety index threshold value. And the authorized health index management unit is used for importing formal authorization when the authorized health index of any load balancing equipment is less than the set authorized health index threshold value.
Further, the management module further comprises: report unit and display element. And the report unit is used for generating a report according to the running state health index. And the display unit is used for displaying the report.
The working principle and the working method of the management system of the load balancing device in this embodiment have been explained in detail in the embodiments shown in fig. 1 and fig. 2, and the two embodiments may be referred to each other, and are not described herein again.
The above description is merely exemplary of the present application and is presented to enable those skilled in the art to understand and practice the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for managing a load balancing device, the method comprising:
deploying a management platform independent of all load balancing devices;
establishing a communication connection between a management platform and any load balancing device according to a communication protocol type supported by any load balancing device, wherein the communication protocol type comprises: SNMP protocol and HTTP protocol;
storing information of a load balancing device, the information comprising: configuration information, an MIB information base and API interface information;
polling each load balancing device, polling all the load balancing devices, and determining the running state health index of any load balancing device, wherein the running state health index comprises: a hardware health index, a service health index, a dual machine health index, an equipment security index, and an authorized health index;
and managing any load balancing equipment according to the running state health index of the load balancing equipment.
2. The method according to claim 1, wherein the establishing a communication connection between the management platform and any load balancing device according to the communication protocol type supported by any load balancing device includes:
determining a communication protocol type supported by any load balancing equipment;
when the communication protocol type supported by any load balancing equipment is an SNMP (simple network management protocol), adding any load balancing equipment on a management platform according to a set first standardized knowledge base and a set management information base, and carrying out communication between the management platform and any load balancing equipment, wherein the first standardized knowledge base is matched with the SNMP;
when the communication protocol type supported by any load balancing device is the HTTP protocol, adding any load balancing device on the management platform according to a set second standardized knowledge base and an interface document, and carrying out communication between the management platform and any load balancing device, wherein the second standardized knowledge base is matched with the HTTP protocol.
3. The method according to claim 2, wherein when the type of the communication protocol supported by any load balancing device is an SNMP protocol, adding the any load balancing device on the management platform according to a set first standardized repository and a set management information base, and performing communication between the management platform and the any load balancing device, includes:
when the communication protocol type supported by any load balancing equipment is an SNMP (simple network management protocol), judging whether a management information base matched with the load balancing equipment is prestored in the management platform;
if yes, adding any load balancing equipment on the management platform;
if not, judging that any load balancing equipment cannot be added to the management platform;
after any load balancing device is added on the management platform, reading a management information base of any load balancing device;
through the SNMP protocol between any load balancing equipment and the management platform, the management platform acquires a return value from any load balancing equipment;
reading a set first standardized knowledge base, wherein the first standardized knowledge base is matched with an SNMP protocol;
and normalizing the return value according to the first normalized knowledge base.
4. The method according to claim 2, wherein when the type of the communication protocol supported by any load balancing device is the HTTP protocol, adding the any load balancing device on the management platform according to the set second standardized repository and the interface document, and performing communication between the management platform and the any load balancing device includes:
when the communication protocol type supported by any load balancing equipment is an HTTP (hyper text transport protocol), judging whether an interface document matched with the load balancing equipment is prestored in the management platform;
if yes, adding any load balancing equipment on the management platform;
if not, judging that any load balancing equipment cannot be added to the management platform;
after any load balancing device is added on the management platform, reading an interface document of any load balancing device;
through an HTTP protocol between any load balancing device and a management platform, the management platform acquires a return value from any load balancing device;
reading a set second standardized knowledge base, wherein the second standardized knowledge base is matched with an HTTP (hyper text transport protocol);
and normalizing the return value according to the second normalized knowledge base.
5. The method for managing load balancing devices according to claim 1, wherein the determining the health index of the operating state of any load balancing device by polling each load balancing device and polling all the load balancing devices comprises:
according to the use conditions of the CPU, the memory and the network card of any load balancing device, calculating a hardware health index of any load balancing device by using a formula I1-100-a 1-C1-a 2-M1-a 3-N1, wherein C1 is the average utilization rate of the CPU, M1 is the utilization rate of the memory, N1 is the bandwidth utilization rate of the network card, and a1, a2 and a3 are the weights of the average utilization rate of the CPU, the memory utilization rate and the bandwidth utilization rate of the network card respectively;
according to the service information, the service pool information and the node information of any load balancing device, calculating a service health index by using a formula I2-b 1-S1 + b 2-S2 + b 3-N1, wherein S1 is the proportion of normal services, S2 is the proportion of normal service pools, N1 is the proportion of normal nodes, and b1, b2 and b3 are the weights of the proportion of normal services, the proportion of normal service pools and the proportion of normal nodes respectively;
when any load balancing device is in a dual-machine state, determining a dual-machine health index according to the dual-machine state of any load balancing device;
according to the login logs, the system logs and the service logs of any load balancing device in a set time period, calculating the device safety index of any load balancing device by using a formula I4, namely 100-c 1N 1-c 2N 2-c 3N 3, wherein N1 is the number of device login failure logs, N2 is the number of system error logs, N3 service abnormal logs, and c1, c2 and c3 are the weights of the number of the device login failure logs, the number of the system error logs and the number of abnormal logs respectively;
determining an authorized health index of any load balancing equipment according to the authorization information of any load balancing equipment;
and calculating the running state health index sum of any load balancing device by using a formula I, namely w 1I 1+ w 2I 2+ w 3I 3+ w 4I 4+ w 5I 5, wherein I1 is the hardware health index of any load balancing device, I2 is the service health index, I3 is the double-machine health index, I4 is the device safety index, I5 is the authorized health index, w1, w2, w3, w4 and w5 are weights of the hardware health index, the service health index, the double-machine health index, the device safety index and the authorized health index respectively.
6. The method according to claim 5, wherein the managing any load balancing device according to the operation state health index of any load balancing device includes:
when the hardware health index of any load balancing equipment is less than the set hardware health index threshold, restarting the equipment or upgrading the hardware;
when the service health index of any load balancing equipment is less than the set service health index threshold value, outputting failure service and performing fault recovery on the failure service;
when the double-machine health index of any load balancing equipment is less than a set double-machine health index threshold value, fault processing is carried out on the host machine in the double machines;
when the equipment safety index of any load balancing equipment is less than the set equipment safety index threshold, updating the starting-up password and upgrading the service safety guarantee;
and when the authorized health index of any load balancing equipment is less than the set authorized health index threshold, introducing formal authorization.
7. The method for managing load balancing devices according to claim 6, wherein the managing any load balancing device according to the operation state health index of any load balancing device further includes:
generating a report according to the running state health index;
and displaying the report.
8. A management system for a load balancing device, the system comprising:
a communication module, configured to establish a communication connection between a management platform and any load balancing device according to a communication protocol type supported by any load balancing device, where the communication protocol type includes: SNMP protocol and HTTP protocol;
a storage module, configured to store information of a load balancing device, where the information includes: configuration information, an MIB information base and API interface information;
the polling module is used for polling each load balancing device, polling all the load balancing devices and determining the running state health index of any load balancing device, wherein the running state health index comprises: a hardware health index, a service health index, a dual machine health index, an equipment security index, and an authorized health index;
and the management module is used for managing any load balancing equipment according to the running state health index of any load balancing equipment.
9. The management system of a load balancing device according to claim 8, wherein the communication module comprises:
a communication protocol type determining unit, configured to determine a communication protocol type supported by any load balancing device;
the SNMP protocol communication unit is used for adding any load balancing equipment on a management platform according to a set first standardized knowledge base and a set management information base when the communication protocol type supported by any load balancing equipment is an SNMP protocol, and carrying out communication between the management platform and any load balancing equipment, wherein the first standardized knowledge base is matched with the SNMP protocol;
and the HTTP protocol communication unit is used for adding any load balancing equipment on the management platform according to a set second standardized knowledge base and an interface document when the communication protocol type supported by any load balancing equipment is the HTTP protocol, and carrying out communication between the management platform and any load balancing equipment, wherein the second standardized knowledge base is matched with the HTTP protocol.
10. The management system of the load balancing device according to claim 8 or 9, wherein the patrol module includes:
a hardware health index calculation unit, configured to calculate, according to usage of the CPU, the memory, and the network card of any load balancing device, a hardware health index of any load balancing device according to a formula I1 ═ 100-a1 ═ C1-a2 × M1-a3 × N1, where C1 is an average utilization rate of the CPU, M1 is a memory utilization rate, N1 is a network card bandwidth utilization rate, and a1, a2, and a3 are weights of the average utilization rate of the CPU, the memory utilization rate, and the network card bandwidth utilization rate, respectively;
a service health index calculation unit, configured to calculate a service health index according to the service information, the service pool information, and the node information of any load balancing device by using a formula I2 ═ b1 × S1+ b2 × S2+ b3 × N1, where S1 is a proportion of a normal service, S2 is a proportion of a normal service pool, N1 is a proportion of a normal node, and b1, b2, and b3 are weights of the proportion of the normal service, the proportion of the normal service pool, and the proportion of the normal node, respectively;
the double-machine health index calculation unit is used for determining a double-machine health index according to the double-machine state of any load balancing equipment when the any load balancing equipment is in the double-machine state;
the equipment safety index calculation unit is used for calculating the equipment safety index of any load balancing equipment by using a formula I4 (100-c 1N 1-c 2N 2-c 3N 3) according to the login logs, the system logs and the service logs of any load balancing equipment in a set time period, wherein N1 is the number of equipment login failure logs, N2 is the number of system error logs and the number of N3 service exception logs, and c1, c2 and c3 are the weights of the number of equipment login failure logs, the number of system error logs and the number of exception logs respectively;
the authorized health index calculation unit is used for determining the authorized health index of any load balancing equipment according to the authorization information of any load balancing equipment;
and the overall operating state health index calculation unit is used for calculating the operating state health index sum of any load balancing device by using a formula I w 1I 1+ w 2I 2+ w 3I 3+ w 4I 4+ w 5I 5, wherein I1 is the hardware health index of any load balancing device, I2 is the service health index, I3 is the double-machine health index, I4 is the device safety index, I5 is the authorized health index, w1, w2, w3, w4 and w5 are weights of the hardware health index, the service health index, the double-machine health index, the device safety index and the authorized health index respectively.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010990357.4A CN112272206B (en) | 2020-09-18 | 2020-09-18 | Management method and system of load balancing equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010990357.4A CN112272206B (en) | 2020-09-18 | 2020-09-18 | Management method and system of load balancing equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112272206A true CN112272206A (en) | 2021-01-26 |
| CN112272206B CN112272206B (en) | 2022-12-02 |
Family
ID=74348482
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010990357.4A Active CN112272206B (en) | 2020-09-18 | 2020-09-18 | Management method and system of load balancing equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112272206B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102143046A (en) * | 2010-08-25 | 2011-08-03 | 华为技术有限公司 | Load balancing method, equipment and system |
| CN103139247A (en) * | 2011-11-28 | 2013-06-05 | 百度在线网络技术（北京）有限公司 | Keep-alive method, system and device for rear-end server in load balancing system |
| US8554929B1 (en) * | 2002-05-03 | 2013-10-08 | Foundry Networks, Llc | Connection rate limiting for server load balancing and transparent cache switching |
| CN108234208A (en) * | 2017-12-29 | 2018-06-29 | 三盟科技股份有限公司 | The visualization load balancing dispositions method and system of resource management based on business |
-
2020
- 2020-09-18 CN CN202010990357.4A patent/CN112272206B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8554929B1 (en) * | 2002-05-03 | 2013-10-08 | Foundry Networks, Llc | Connection rate limiting for server load balancing and transparent cache switching |
| CN102143046A (en) * | 2010-08-25 | 2011-08-03 | 华为技术有限公司 | Load balancing method, equipment and system |
| CN103139247A (en) * | 2011-11-28 | 2013-06-05 | 百度在线网络技术（北京）有限公司 | Keep-alive method, system and device for rear-end server in load balancing system |
| CN108234208A (en) * | 2017-12-29 | 2018-06-29 | 三盟科技股份有限公司 | The visualization load balancing dispositions method and system of resource management based on business |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112272206B (en) | 2022-12-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107005438B (en) | Methods, systems, and media for generating dynamically scalable network load | |
| Ma et al. | Ms-rank: Multi-metric and self-adaptive root cause diagnosis for microservice applications | |
| US20090292954A1 (en) | Ranking the importance of alerts for problem determination in large systems | |
| EP2871574B1 (en) | Analytics for application programming interfaces | |
| RU2375744C2 (en) | Model based management of computer systems and distributed applications | |
| US6973415B1 (en) | System and method for monitoring and modeling system performance | |
| US8489728B2 (en) | Model-based system monitoring | |
| US9703624B2 (en) | Event correlation and calculation engine | |
| CN102859505B (en) | The management method of management system and computer system | |
| US7647530B2 (en) | Network fault pattern analyzer | |
| US20120221898A1 (en) | System and method for determination of the root cause of an overall failure of a business application service | |
| US7369967B1 (en) | System and method for monitoring and modeling system performance | |
| CN111897697B (en) | Server hardware fault repairing method and device | |
| US11847082B2 (en) | System and method for secure management of non-registered components of an information handling system using a baseboard management controller | |
| CN112838944A (en) | Diagnosis and management, rule determination and deployment method, distributed device, and medium | |
| CN112272206B (en) | Management method and system of load balancing equipment | |
| CN115952098A (en) | Performance test tuning scheme recommendation method and system | |
| Rady | Formal definition of service availability in cloud computing using OWL | |
| CN111737130B (en) | Public cloud multi-tenant authentication service testing method, device, equipment and storage medium | |
| CN116048859B (en) | Distributed database fault diagnosis method and device, electronic equipment and storage medium | |
| CN114785673B (en) | Method and device for acquiring abnormal information during active-standby switching | |
| Zhang et al. | Hierarchical management of service accountability in service oriented architectures | |
| Li et al. | A sensor-based approach to symptom recognition for autonomic systems | |
| Koneni | Microservices Architectures Using Spring Boot: Embracing Containerization and Observability | |
| CN116107791A (en) | Test environment fault node repairing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |