CN107666401B - Configuration information acquisition method and terminal - Google Patents
Configuration information acquisition method and terminal Download PDFInfo
- Publication number
- CN107666401B CN107666401B CN201610604798.XA CN201610604798A CN107666401B CN 107666401 B CN107666401 B CN 107666401B CN 201610604798 A CN201610604798 A CN 201610604798A CN 107666401 B CN107666401 B CN 107666401B
- Authority
- CN
- China
- Prior art keywords
- load balancer
- configuration information
- unit
- address
- configuration
- 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.)
- Active
Links
Images
Classifications
-
- 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/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- 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/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
Abstract
The embodiment of the invention discloses a configuration information acquisition method and a terminal, wherein the method comprises the following steps: acquiring an IP address of each F5 load balancer; accessing the F5 load balancer according to the IP address; collecting the configuration of the F5 load balancer to obtain the configuration information corresponding to the equipment identifier; and storing the configuration information. The embodiment of the invention also discloses a terminal. The embodiment of the invention acquires the IP address of each F5 load balancer, accesses the corresponding F5 load balancer according to the IP address, acquires the configuration of the F5 load balancer to obtain the configuration information of the corresponding equipment identifier, and stores the configuration information. The embodiment of the invention can obtain the corresponding configuration information from different F5 load balancers, and provides convenience for the user to uniformly manage the F5 load balancer.
Description
Technical Field
The present invention relates to the field of computer networks, and in particular, to a configuration information obtaining method and a terminal.
Background
At present, due to bottlenecks in processing capacity and I/O performance of a single server, if a large number of concurrent service requests occur on the single server, the server is busy or even down. In order to solve the above problems, an F5 load balancer is generally used to distribute all requests to multiple node servers through a load balancing mechanism, so as to reduce the traffic pressure of a single server and prevent the server from being too busy or down. However, with the increase of the number of F5 load balancers, how to obtain the configuration information of each F5 load balancer, so as to facilitate the unified management of the numerous F5 load balancers, which is a problem to be solved urgently.
Disclosure of Invention
The embodiment of the invention provides a configuration information acquisition method and a terminal, which can acquire corresponding configuration information from different F5 load balancers so as to facilitate unified management of users.
In a first aspect, an embodiment of the present invention provides a method for acquiring configuration information, where the method includes: acquiring an IP address of each F5 load balancer; accessing the F5 load balancer according to the IP address; collecting configuration information of the F5 load balancer; and storing the configuration information.
In another aspect, an embodiment of the present invention provides a terminal, where the terminal includes: a first obtaining unit, configured to obtain an IP address of each F5 load balancer; an accessing unit, configured to access the F5 load balancer according to the IP address; the acquisition unit is used for acquiring the configuration information of the F5 load balancer; and the storage unit is used for storing the configuration information.
The embodiment of the invention acquires the IP address of each F5 load balancer, accesses the corresponding F5 load balancer according to the IP address, then collects the configuration information of the F5 load balancer and stores the configuration information. The embodiment of the invention can obtain the corresponding configuration information from different F5 load balancers, and provides convenience for the user to uniformly manage the F5 load balancer.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flow chart of a configuration information obtaining method according to an embodiment of the present invention;
FIG. 2 is a schematic view of a sub-flow of step S102 in FIG. 1;
FIG. 3 is a schematic view of a sub-flow of step S103 in FIG. 1;
fig. 4 is a schematic flow chart of a configuration information obtaining method according to another embodiment of the present invention;
fig. 5 is a schematic block diagram of a terminal according to an embodiment of the present invention;
FIG. 6 is a schematic block diagram of the access unit of FIG. 5;
FIG. 7 is a schematic block diagram of the acquisition unit of FIG. 5;
fig. 8 is a schematic block diagram of a terminal according to another embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. 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 invention.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Fig. 1 is a schematic flowchart of a configuration information obtaining method according to an embodiment of the present invention. As shown in the figure, the configuration information acquisition method includes steps S101 to S104.
S101, obtain the IP address of each F5 load balancer.
Specifically, in order to distinguish the plurality of F5 load balancers, in the embodiment of the present invention, each F5 load balancer is configured with a device identifier corresponding thereto, where the device identifier is an identifier code of the F5 load balancer and corresponds to the F5 load balancer one by one. Before the F5 load balancer is used in networking, physical connection planning, namely IP address planning, is needed, network segments are divided and IP addresses are allocated according to needs so that the F5 load balancer can be connected with the network, and the IP addresses correspond to the F5 load balancer in meaning. In an embodiment of the present invention, the device identification and IP address of each F5 load balancer may be automatically obtained.
And S102, accessing the F5 load balancer according to the IP address.
In the embodiment of the invention, the corresponding F5 load balancer can be accessed according to the acquired IP address.
Specifically, referring to fig. 2, it is a sub-flowchart of step S102. As shown, step S102 includes steps S201 to S203.
And S201, performing communication connection with the F5 load balancer according to the IP address.
Specifically, in order to test whether the operation state of the F5 load balancer is normal, in the embodiment of the present invention, a link is sent to each F5 load balancer to perform a corresponding communication connection, so as to facilitate grasping whether the F5 load balancer is online. Since the technique of testing whether the F5 load balancer is on-line is well known to those skilled in the art, it is not described here in detail.
S202, if the communication connection is successful, logging in the corresponding F5 load balancer to access the F5 load balancer.
Specifically, in the embodiment of the present invention, if the communication connection is successful, it indicates that the F5 load balancer performing the communication connection is in an online state, and the F5 load balancer may be registered for access. It should be noted that, when the load balancer F5 is logged in for access, not only configuration information such as node server configuration, load balancing pool configuration, virtual server configuration, IRule (script processing engine based on TCL language), monitor configuration, SNAT configuration, etc. can be viewed, but also the operating system, environment information, etc. of the load balancer F5 can be viewed.
S203, if the communication connection fails, displaying fault prompt information corresponding to the IP address.
Specifically, in the embodiment of the present invention, if the communication connection fails, it indicates that the F5 load balancer performing the communication connection is in an offline state, where the offline state may be a communication connection failure due to a network connection abnormality of the corresponding F5 load balancer or a failure of the F5 load balancer itself, and at this time, fault notification information corresponding to the IP address, such as "communication connection abnormality", "communication connection disabled", and the like, is displayed, so that a user can timely grasp the operating state of the F5 load balancer device.
S103, collecting configuration information of the F5 load balancer.
Specifically, in the embodiment of the present invention, the configuration information of the F5 load balancer is mainly service configuration information, which includes, for example, node server configuration, load balancing pool configuration, virtual server configuration, and an IRule (script processing engine based on TCL language), where the virtual server is configured to receive an access request of a client and distribute the request to a load balancing node server, the load balancing pool includes node servers to which requests can be sent for processing, and the IRule is a script processing engine based on TCL language, and can implement some special traffic processing requirements very flexibly. After accessing the F5 load balancer based on the IP address, i.e., logging onto the F5 load balancer, the configuration of the F5 load balancer may be collected to obtain configuration information for the corresponding device identification.
Referring to fig. 3, a sub-flow diagram of step S103 is shown. As shown, step S103 includes steps S301 to S303.
S301, obtaining the CPU utilization rate of each F5 load balancer.
Specifically, in the embodiment of the present invention, in order to determine whether the CPU usage state of each F5 load balancer is in a busy state, the CPU usage rate of each F5 load balancer needs to be acquired. The CPU utilization rate is a CPU resource occupied by the running program, and indicates a case where the F5 load balancer runs the program at a certain point in time. The higher the CPU utilization, the less the F5 load balancer runs many programs at this time, and vice versa.
S302, judging whether the CPU utilization rate of each F5 load balancer exceeds a preset threshold value.
Specifically, the obtained CPU utilization of the F5 load balancer is compared with a preset threshold to determine whether the CPU utilization of the F5 load balancer is in a busy state, for example, in the embodiment of the present invention, the preset threshold may be set at 55%, that is, the current CPU utilization exceeds 55%, the process is ended, thereby avoiding adding an operation burden to the F5 load balancer in the busy state.
S303, acquiring the configuration of the F5 load balancer with the CPU utilization rate less than a preset threshold value to obtain the configuration information corresponding to the equipment identifier.
Specifically, in the embodiment of the present invention, the configuration of the F5 load balancer with the CPU utilization rate less than the preset threshold is obtained to obtain the configuration information corresponding to the device identifier, for example, the configuration information of the F5 load balancer with the CPU utilization rate less than 55% may be obtained, and since each F5 load balancer uniquely corresponds to one device identifier, the configuration of the F5 load balancer with the CPU utilization rate less than the preset threshold is obtained to correspond to the device identifier of the F5 load balancer.
And S104, storing the configuration information.
Specifically, in order to facilitate uniform management of configuration information of different F5 load balancers, after the configuration of the F5 load balancer is collected to obtain configuration information corresponding to the device identifier, the configuration information needs to be stored, and preferably, the device identifiers and the configuration information are stored in a one-to-one correspondence manner, so that uniform management of the configuration information of the F5 load balancer is achieved.
The embodiment of the invention acquires the IP address of each F5 load balancer, accesses the corresponding F5 load balancer according to the IP address, acquires the configuration of the F5 load balancer to obtain the configuration information of the corresponding equipment identifier, and stores the configuration information. The embodiment of the invention can obtain the corresponding configuration information from different F5 load balancers, and provides convenience for the user to uniformly manage the F5 load balancer.
Fig. 4 is a schematic flowchart of a configuration information obtaining method according to another embodiment of the present invention. As shown, the method includes steps S401 to S406.
S401, acquiring the device identification and the IP address of each F5 load balancer.
S402, accessing the F5 load balancer according to the IP address.
And S403, collecting configuration information of the F5 load balancer.
S404, storing the configuration information.
Steps S401 to S404 are the same as above, and are not described herein again.
S405, if the device identification input by the user is received, inquiring configuration information corresponding to the device identification.
Specifically, in order to facilitate the user to view the configuration information of different F5 load balancers, in the embodiment of the present invention, an interactive interface interacting with the user may be provided so that the user performs query of the configuration information of the F5 load balancer, for example, an input box may be provided for the user to input a device identifier of the F5 load balancer, so as to query the configuration information corresponding to the device identifier. It is to be understood that the user may also input the name of the virtual server and so on for query, which is not limited herein.
S406, displaying the configuration information.
Specifically, in order to facilitate the user to visually view the configuration information of the F5 load balancer, in the embodiment of the present invention, the configuration information corresponding to the device identifier is displayed, so that the user can conveniently view the configuration information.
The embodiment of the invention acquires the P address of each F5 load balancer, accesses the corresponding F5 load balancer according to the IP address, acquires the configuration of the F5 load balancer to obtain the configuration information of the corresponding equipment identifier, stores the configuration information, inquires the configuration information corresponding to the equipment identifier and displays the configuration information if the equipment identifier input by a user is received. The embodiment of the invention can obtain the corresponding configuration information from different F5 load balancers, so that the unified management of users is facilitated, and the users can conveniently check the configuration information of different F5 load balancers.
Fig. 5 is a schematic block diagram of a terminal according to an embodiment of the present invention. The terminal 50 in the present embodiment as shown in the figure includes a first acquisition unit 51, an access unit 52, an acquisition unit 53, and a storage unit 54.
A first obtaining unit 51, configured to obtain an IP address of each F5 load balancer.
An accessing unit 52, configured to access the F5 load balancer according to the IP address.
And the collecting unit 53 is configured to collect configuration information of the F5 load balancer.
A storage unit 54 for storing the configuration information.
Further, the first obtaining unit 51 is further configured to obtain the device identifier storage unit 54 of each F5 load balancer, and specifically, to store the device identifier and the configuration information in a one-to-one correspondence manner.
Further, referring to fig. 6, a schematic block diagram of the access unit of fig. 5 is shown. As shown, the access unit 52 includes a test unit 521, a login unit 522, and a second display unit 523.
And the test unit 521 is configured to perform communication connection with the F5 load balancer according to the IP address.
The login unit 522 is configured to log in the corresponding F5 load balancer to access the F5 load balancer if the communication connection is successful.
The second display unit 523 is configured to display a fault notification message corresponding to the IP address if the communication connection fails.
Further, referring to fig. 7, a schematic block diagram of the acquisition unit in fig. 5 is shown. As shown in the figure, the access unit 53 includes a second acquisition unit 531, a judgment unit 532, and a third acquisition unit 533.
A second obtaining unit 531, configured to obtain a CPU utilization of each of the F5 load balancers.
A judging unit 532, configured to judge whether the CPU utilization of each F5 load balancer exceeds a preset threshold.
A third obtaining unit 533, configured to obtain the configuration of the F5 load balancer with the CPU utilization smaller than the preset threshold to obtain the configuration information corresponding to the device identifier.
The embodiment of the invention obtains the IP address of each F5 load balancer through the first obtaining unit 51, accesses the corresponding F5 load balancer according to the IP address through the accessing unit 52, then collects the configuration information of the F5 load balancer through the collecting unit 53, and stores the configuration information in the storage unit 54. The embodiment of the invention can obtain the corresponding configuration information from different F5 load balancers, and provides convenience for the user to uniformly manage the F5 load balancer.
Fig. 8 is a schematic block diagram of a terminal according to another embodiment of the present invention. The terminal 60 in the present embodiment as shown in the figure includes a first acquiring unit 61, an accessing unit 62, an acquiring unit 63, a storing unit 64, an inquiring unit 65, and a first displaying unit 66.
The first obtaining unit 61 is configured to obtain a device identifier and an IP address of each F6 load balancer.
An accessing unit 62, configured to access the F6 load balancer according to the IP address.
And the collecting unit 63 is configured to collect configuration information of the F6 load balancer.
A storage unit 64 for storing the configuration information.
The querying unit 65 is configured to query, if the device identifier input by the user is received, the configuration information corresponding to the device identifier.
A first display unit 66 for displaying the configuration information.
In the embodiment of the invention, the first obtaining unit 61 obtains the device identifier and the IP address of each F6 load balancer, the accessing unit 62 accesses the corresponding F6 load balancer according to the IP address, the collecting unit 63 collects the configuration information of the F6 load balancer, the storing unit 64 stores the configuration information, and if the device identifier input by the user is received, the querying unit 65 queries the configuration information corresponding to the device identifier, and the first displaying unit 66 displays the configuration information. The embodiment of the invention can obtain the corresponding configuration information from different F5 load balancers, so that the unified management of users is facilitated, and the users can conveniently check the configuration information of different F5 load balancers.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the terminal and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed terminal and method can be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, device apparatuses or units, and may also be an electrical, mechanical or other form of connection.
The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs.
The units in the terminal of the embodiment of the invention can be merged, divided and deleted according to actual needs.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above are preferred embodiments of the invention and are not intended to limit the invention in any way. Various equivalent changes and modifications can be made by those skilled in the art based on the above-described embodiments, and all equivalent changes and modifications within the scope of the claims should be considered as falling within the scope of the present invention.
Claims (4)
1. A method for acquiring configuration information is characterized by comprising the following steps:
acquiring an IP address of each F5 load balancer;
acquiring a device identifier configured by each F5 load balancer to access the F5 load balancer according to the IP address, wherein the device identifiers are in one-to-one correspondence with the F5 load balancers;
collecting configuration information of the F5 load balancer;
storing the device identification and the configuration information in a one-to-one correspondence manner;
if the equipment identification input by the user is received, inquiring configuration information corresponding to the equipment identification; and
displaying the configuration information;
wherein the collecting the configuration information of the F5 load balancer includes:
acquiring the CPU utilization rate of each F5 load balancer; and
the method comprises the steps of obtaining configuration information of an F5 load balancer with the CPU utilization rate smaller than a preset threshold value, wherein the configuration information is service configuration information, and the service configuration information comprises node server configuration, load balancing pool configuration, virtual server configuration, a script processing engine based on TCL language, Monitor configuration and SNAT configuration.
2. The method of claim 1, wherein said accessing said F5 load balancer based on said IP address comprises:
performing communication connection with the F5 load balancer according to the IP address;
if the communication connection is successful, logging in a corresponding F5 load balancer to access the F5 load balancer;
and if the communication connection fails, displaying fault prompt information corresponding to the IP address.
3. A terminal, comprising:
a first obtaining unit, configured to obtain an IP address of each F5 load balancer;
the access unit is used for acquiring a device identifier configured by each F5 load balancer to access the F5 load balancer according to the IP address, wherein the device identifiers correspond to the F5 load balancers one by one;
the acquisition unit is used for acquiring the configuration information of the F5 load balancer;
the storage unit is used for correspondingly storing the equipment identification and the configuration information one by one;
the query unit is used for querying the configuration information corresponding to the equipment identification if the equipment identification input by a user is received; and
a first display unit for displaying the configuration information;
wherein, the collection unit includes:
a second obtaining unit, configured to obtain a CPU utilization of each of the F5 load balancers;
the judging unit is used for judging whether the CPU utilization rate of each F5 load balancer exceeds a preset threshold value;
and a third obtaining unit, configured to obtain configuration information of the F5 load balancer with the CPU utilization rate smaller than a preset threshold to obtain configuration information corresponding to the device identifier, where the configuration information is service configuration information, and the service configuration information includes node server configuration, load balancing pool configuration, virtual server configuration, a script processing engine based on a TCL language, Monitor configuration, and SNAT configuration.
4. The terminal of claim 3, wherein the access unit comprises:
the testing unit is used for carrying out communication connection with the F5 load balancer according to the IP address;
the login unit is used for logging in the corresponding F5 load balancer to access the F5 load balancer if the communication connection is successful;
and the second display unit is used for displaying fault prompt information corresponding to the IP address if the communication connection fails.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610604798.XA CN107666401B (en) | 2016-07-28 | 2016-07-28 | Configuration information acquisition method and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610604798.XA CN107666401B (en) | 2016-07-28 | 2016-07-28 | Configuration information acquisition method and terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107666401A CN107666401A (en) | 2018-02-06 |
| CN107666401B true CN107666401B (en) | 2021-05-04 |
Family
ID=61115399
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610604798.XA Active CN107666401B (en) | 2016-07-28 | 2016-07-28 | Configuration information acquisition method and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107666401B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109726013B (en) * | 2018-12-28 | 2021-01-26 | 杭州迪普科技股份有限公司 | Method and device for managing multiple LB (local area network) devices by LBaaS (local area service) |
| CN112035243A (en) * | 2019-06-04 | 2020-12-04 | 顺丰科技有限公司 | Data query method, device, terminal and medium |
| CN111556177B (en) * | 2020-04-22 | 2021-04-06 | 腾讯科技（深圳）有限公司 | Network switching method, device, equipment and storage medium |
| CN113254204A (en) * | 2021-05-24 | 2021-08-13 | 山东中创软件商用中间件股份有限公司 | Method, system and equipment for controlling soft load balancer |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102932444A (en) * | 2012-10-29 | 2013-02-13 | 上海银商资讯有限公司 | Load balancing module in financial real-time trading system |
| US9344493B1 (en) * | 2013-07-11 | 2016-05-17 | Juniper Networks, Inc. | Server health monitoring for traffic load balancer |
-
2016
- 2016-07-28 CN CN201610604798.XA patent/CN107666401B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102932444A (en) * | 2012-10-29 | 2013-02-13 | 上海银商资讯有限公司 | Load balancing module in financial real-time trading system |
| US9344493B1 (en) * | 2013-07-11 | 2016-05-17 | Juniper Networks, Inc. | Server health monitoring for traffic load balancer |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107666401A (en) | 2018-02-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110266716B (en) | Unified service platform system of power grid | |
| EP2563062B1 (en) | Long connection management apparatus and link resource management method for long connection communication | |
| CN107666401B (en) | Configuration information acquisition method and terminal | |
| US8271632B2 (en) | Remote access providing computer system and method for managing same | |
| CN111124850A (en) | MQTT server performance testing method, system, computer equipment and storage medium | |
| CN108156240B (en) | Method and system for accessing industrial adapter to server | |
| EP2838228A1 (en) | Alarm correlation analysis method, apparatus, and system | |
| EP2869495A1 (en) | Node de-duplication in a network monitoring system | |
| CN104618161A (en) | Application cluster monitoring device and method | |
| CN110247812A (en) | A kind of more cluster management methods, device, system and associated component | |
| CN111181800B (en) | Test data processing method and device, electronic equipment and storage medium | |
| CN103731287A (en) | Method for selecting server to take over fault server | |
| CN114070707A (en) | Internet performance monitoring method and system | |
| CN116886490A (en) | Server inspection method and device and computer readable storage medium | |
| CN107508765B (en) | Message processing method and device | |
| EP3306471B1 (en) | Automatic server cluster discovery | |
| CN110875831B (en) | Method and device for monitoring network quality | |
| CN111147899B (en) | Fault early warning method and device | |
| CN110222084B (en) | Method and device for reporting monitoring information of hotspot equipment, storage medium and terminal | |
| CN110247802B (en) | Resource configuration method and device for cloud service single-machine environment | |
| CN103731460A (en) | Pooling device for establishing network server pool | |
| KR101375099B1 (en) | An apparatus and system for managing application delivery controller syntagmatically and managing method thereof | |
| CN112164414A (en) | Method and assembly for testing stability of storage device | |
| CN109889619A (en) | Abnormal domain name monitoring method and device based on block chain | |
| CN112087336B (en) | Deployment and management method and device of virtual IP service system and electronic equipment |
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 |