CN111314126B - Service IP deployment method and system and monitoring equipment - Google Patents

Service IP deployment method and system and monitoring equipment Download PDF

Info

Publication number
CN111314126B
CN111314126B CN202010086090.6A CN202010086090A CN111314126B CN 111314126 B CN111314126 B CN 111314126B CN 202010086090 A CN202010086090 A CN 202010086090A CN 111314126 B CN111314126 B CN 111314126B
Authority
CN
China
Prior art keywords
service
server group
scheduling
traffic
allocated
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
Application number
CN202010086090.6A
Other languages
Chinese (zh)
Other versions
CN111314126A (en
Inventor
刘铅香
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Wangsu Science and Technology Co Ltd
Original Assignee
Wangsu Science and Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Wangsu Science and Technology Co Ltd filed Critical Wangsu Science and Technology Co Ltd
Priority to CN202010086090.6A priority Critical patent/CN111314126B/en
Publication of CN111314126A publication Critical patent/CN111314126A/en
Application granted granted Critical
Publication of CN111314126B publication Critical patent/CN111314126B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • 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/0893—Assignment of logical groups to network elements
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • 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/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • 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
    • 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/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The embodiment of the invention relates to the technical field of networks and discloses a service IP deployment method, a service IP deployment system and a service IP monitoring device. The deployment method of the service IP comprises the following steps: determining whether the first service IP is abnormal or not according to the acquired state information of the server group corresponding to the first service IP; if the first service IP is determined to be abnormal, a second service IP is acquired, and the flow of the server group is scheduled to a target server group through scheduling equipment; and replacing the second service IP with the service IP of the server group, and recovering the traffic of the server group. In the invention, the dynamic deployment of the service IP is realized, and in the dynamic deployment process of the whole service IP, only the server group corresponding to the first service IP with abnormality is involved, other server groups belonging to the same service cluster with the server group are not influenced, the influence range of the dynamic deployment process is reduced, the processing load of the monitoring equipment is reduced, and the timely processing capacity of the monitoring equipment is further improved.

Description

Service IP deployment method and system and monitoring equipment
Technical Field
The embodiment of the invention relates to the technical field of networks, in particular to a service IP deployment method, a service IP deployment system and a monitoring device.
Background
For a service IP that provides acceleration services for clients, the service IP is a traffic portal for the cache server cluster, and is also a portal for CDN network traffic. The service cluster architecture is generally an edge server and four-layer balancing layer server mode, or an edge server, seven-layer balancing layer server and four-layer balancing layer server mode, the service IP is a VIP (Virtual IP Address, abbreviated as VIP) of the four-layer balancing layer server, the service IP is provided for clients to use, namely is a virtual IP of the four-layer balancing layer server, a plurality of groups of edge server groups can be hung below the four-layer balancing layer server of the service cluster, and one group of edge server groups provides acceleration service for at least one client. The types of service IP include: VIP address, HIP protocol (Host Identity Protocol, HIP) address, routing information protocol (Routing Information Protocol, RIP) address, etc.
In the process of providing acceleration service for clients, if faults occur, a large-scale source returning request can be generated, so that the pressure of a client source station is increased, even a client source station server is crashed, large-area users cannot access the server, and the user experience is affected. At present, the service IP can be monitored through the monitoring platform, when the service IP is monitored to be unavailable, the monitoring platform sends alarm information to staff, and the staff can repair or replace the unavailable service IP.
However, the inventors found that there are at least the following problems in the prior art: when the service IP under a certain service cluster is unavailable, a new service IP needs to be manually applied, then a traffic backup scheme is searched to reserve traffic of all server groups hung under the service cluster, the service IP of the new application is utilized to replace the unavailable service IP, and then the traffic of all the server groups hung under the service cluster is recovered. In the backup process, all servers hung under the service cluster are unavailable, so that the use experience of a user is affected, the processing time is too long, and timeliness cannot be guaranteed.
Disclosure of Invention
The invention aims to provide a service IP deployment method, a system and a monitoring device, which realize the dynamic deployment of the service IP, and in the whole dynamic deployment process of the service IP, only a server group corresponding to a first service IP with abnormality is involved, other server groups belonging to the same service cluster with the server group are not affected, the scope of influence of the dynamic deployment process is reduced, the processing load of the monitoring device is reduced, and the timely processing capacity of the monitoring device is further improved.
In order to solve the above technical problems, an embodiment of the present invention provides a service IP deployment method, which is applied to a monitoring device, and the method includes: determining whether the first service IP is abnormal or not according to the acquired state information of the server group corresponding to the first service IP; if the first service IP is determined to be abnormal, a second service IP is acquired, and the flow of the server group is scheduled to a target server group through scheduling equipment; and replacing the second service IP with the service IP of the server group, and recovering the traffic of the server group.
The embodiment of the invention also provides monitoring equipment, which comprises: at least one processor; and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the service IP deployment method described above.
The embodiment of the invention also provides a service IP deployment system, which comprises the monitoring equipment.
Compared with the prior art, the embodiment of the invention can determine whether the first service IP is abnormal or not according to the state information after the monitoring equipment acquires the state information of the server group corresponding to the first service IP, if the first service IP is abnormal, the second service IP is acquired, the flow of the server group is scheduled to the target server group through the scheduling equipment, then the second service IP is replaced with the service IP of the server group, and the flow of the server group is restored, so that the dynamic deployment of the service IP is realized, and in the dynamic deployment process of the whole service IP, only the server group corresponding to the first service IP with the abnormality is involved, the range of the influence of the dynamic deployment process is not influenced, the processing load of the monitoring equipment is reduced, and the timely processing capacity of the monitoring equipment is further improved. Meanwhile, the service IP with abnormality can be automatically replaced, the unavailable time of a server group corresponding to the server IP with abnormality is shortened, and the user experience is improved.
In addition, before the second service IP is acquired and the traffic of the server group is scheduled to the target server group by the scheduling device, the method further includes: judging whether the first service IP is limited or not; if the first service IP is limited, a step of scheduling traffic of the server group to the target server group is entered. In this embodiment, when the first service IP is abnormal and limited, the replacement process of the first service IP is performed, so that the resource consumption of the monitoring device is reduced, and the consumption of unused service IP is reduced.
In addition, determining whether the first service IP is limited includes: judging whether a preset port of the first service IP is in a blocking state or not; and if the preset port of the first service IP is in a blocking state, judging that the first service IP is limited. The present embodiment provides a specific implementation manner for determining whether the first service IP is limited.
In addition, determining whether the first service IP is limited includes: judging whether the ping value of the first service IP meets a first preset condition, wherein the first preset condition is that the intranet ping value of the first service IP is matched with the extranet ping value of the first service IP; and if the ping value of the first service IP meets a first preset condition, judging that the first service IP is limited. The present embodiment provides another specific implementation way of determining whether the first service IP is limited.
In addition, before the traffic of the server group is scheduled to the target server group by the scheduling device, the method further includes: judging whether the traffic of the server group is already scheduled; if the flow of the server group is not scheduled, a step of scheduling the flow of the server group to a target server group through scheduling equipment is entered; if the traffic of the server group has been scheduled, the second service IP is replaced with the service IP of the server group. In the embodiment, the judgment on whether the flow of the server group is processed is increased, repeated scheduling of the flow of the server group is avoided, the processing load of the monitoring equipment is further reduced, and the processing flow is shortened.
In addition, the scheduling device schedules the traffic of the server group to the target server group, including: and acquiring a flow scheduling scheme from the resource management platform through the scheduling equipment, so that the scheduling equipment schedules the flow of the server group to the target server group according to the flow scheduling scheme. The embodiment provides a specific implementation manner of scheduling the traffic of the server group to the target server group through the scheduling device.
In addition, the method for acquiring the traffic scheduling scheme from the resource management platform through the scheduling device comprises the following steps: and sending the coverage information of the server group to the scheduling equipment so as to select a flow scheduling scheme from a resource pool of the resource management platform according to the coverage information. The embodiment provides a specific implementation mode for acquiring a flow scheduling scheme from a resource management platform through scheduling equipment.
In addition, acquiring the second service IP includes: receiving the allocated service IP after issuing the service IP application, and judging whether the allocated service IP is available; and if the allocated service IP is available, taking the allocated service IP as a second service IP. The embodiment provides a specific implementation manner for acquiring the second service IP.
In addition, before the assigned service IP is used as the second service IP, the method further comprises: judging whether the allocated service IP meets a second preset condition or not; if the allocated service IP meets the second preset condition, the step of taking the allocated service IP as the second service IP is entered. In this embodiment, the judgment of whether the allocated service IP meets the second preset condition is added, so that the service IP meeting the second preset condition can be obtained, and the situation that the allocated service IP is not matched with the server group is avoided to a certain extent.
In addition, the second preset condition is that the allocated service IP and the first service IP are in the same network segment and/or the allocated service IP and the first service IP are located in the same virtual local area network.
Drawings
One or more embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements, and in which the figures of the drawings are not to be taken in a limiting sense, unless otherwise indicated.
Fig. 1 is a specific flowchart of a deployment method of service IP in a first embodiment according to the present invention;
fig. 2 is a specific flowchart of a deployment method of service IP in a second embodiment according to the present invention;
fig. 3 is a specific flowchart of a deployment method of service IP in a third embodiment according to the present invention;
fig. 4 is a specific flowchart of a deployment method of service IP in a fourth embodiment according to the present invention;
fig. 5 is a specific flowchart of a deployment method of service IP according to a fifth embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the following detailed description of the embodiments of the present invention will be given with reference to the accompanying drawings. However, those of ordinary skill in the art will understand that in various embodiments of the present invention, numerous technical details have been set forth in order to provide a better understanding of the present application. However, the technical solutions claimed in the present application can be implemented without these technical details and with various changes and modifications based on the following embodiments.
The first embodiment of the present invention relates to a service IP deployment method, which is applied to a monitoring device, where the monitoring device may be used as a monitoring platform and may monitor a server group in a server cluster, where the server cluster may include a plurality of server groups, that is, a plurality of server groups are suspended under four-layer balanced layer servers of the server cluster, a service IP of each server group may be VIP (Virtual IP Address, abbreviated as VIP) of the four-layer balanced layer servers, each server group includes a plurality of servers, and one server group may provide an acceleration service for one or more clients.
A specific flow of the service IP deployment method of the present embodiment is shown in fig. 1.
Step 101, determining whether the first service IP is abnormal according to the acquired state information of the server group corresponding to the first service IP. If it is determined that there is an abnormality, step 102 is entered; if no abnormality is determined, the process is directly finished.
Specifically, each server group in the server cluster has a corresponding service IP, and when the server group corresponding to each service IP provides a service for a user, a corresponding status code is generated, where the status code is status information of the server group corresponding to the service IP, and the status information can represent an available status of the service IP. The monitoring device may acquire state information of a server group corresponding to each service IP according to a preset period, taking the service IP as a first service IP as an example, and after acquiring the state information of the server group corresponding to the first service IP, determine whether the first service IP is abnormal according to the state information; for example, when the status code in the acquired status information is 1, the monitoring device determines that there is an anomaly in the first service IP, which indicates that the first service IP is in an unavailable state, and proceeds to step 102. When the state code in the acquired state information is 0, the monitoring equipment determines that the first service IP is not abnormal, and indicates that the first service IP is in an available state and directly ends.
In one example, when determining that the first service IP is abnormal, the monitoring platform may send, according to a preset manner, failure alarm information to a maintainer, where the failure alarm information includes a server group corresponding to the first service IP having the abnormality, state information of the server group, and the like, so that the maintainer may maintain the first service IP in time.
And 102, acquiring a second service IP, and scheduling the flow of the server group to a target server group through scheduling equipment.
Specifically, when the monitoring device determines that the first service IP is abnormal, the monitoring device acquires an available second service IP, and then triggers the scheduling device to process the flow of the server group corresponding to the first service IP, and schedule the flow of the server group to an available target server group, so that the target server group can provide corresponding services for clients served by the server group corresponding to the first service IP.
And 103, replacing the second service IP with the service IP of the server group, and recovering the traffic of the server group.
Specifically, the monitoring equipment starts service IP replacement, eliminates the first service IP with abnormality, and then replaces the available second service IP with the service IP of the server group; taking the first service IP as the VIP of the four-layer balancing layer server as an example, at this time, the VIP (first service IP) is removed, the old VIP (first service IP) in the four-layer balancing layer server is replaced with the second service IP, then global deployment information of the service cluster is reconfigured, seven-layer load balancing configuration and frequency division channel configuration are carried out, and therefore the first service IP related in the service cluster can be replaced with the second service IP, and the first service IP in the server group corresponding to the first service IP is replaced with the second service IP. After each configuration is finished, the configuration result can be detected, and when an abnormality exists, error reporting information is sent out.
In one example, after completing the replacement process from the first service IP to the second service IP, the first service IP may be released, set to an unavailable state, and wait for a maintainer to unseal the first service IP after subsequent maintenance.
After the replacement of the service IP of the server group is completed, whether the second service IP can provide service or not can be judged through modes such as PO and Curl, when the second server can provide service is judged, the second service IP of the server group is adjusted to be in an available state, at the moment, the second service IP is in a service-capable mode, the flow of the server group is recovered to the server group from the target server group through the scheduling system, and then the server group can continue to provide service for clients.
Compared with the prior art, the monitoring device can determine whether the first service IP is abnormal according to the state information after acquiring the state information of the server group corresponding to the first service IP, if the first service IP is abnormal, the second service IP is acquired, the flow of the server group is scheduled to the target server group through the scheduling device, then the second service IP is replaced with the service IP of the server group, and the flow of the server group is restored, so that the dynamic deployment of the service IP is realized, in the dynamic deployment process of the whole service IP, only the server group corresponding to the first service IP with the abnormality is involved, the range of the influence of the dynamic deployment process is reduced, the processing load of the monitoring device is reduced, and the timely processing capacity of the monitoring device is further improved. Meanwhile, the service IP with abnormality can be automatically replaced, the unavailable time of a server group corresponding to the server IP with abnormality is shortened, and the user experience is improved.
A second embodiment of the present invention relates to a service IP deployment method, which is an improvement based on the first embodiment, and the main improvement is that: only the limited first service IP is replaced.
A specific flow of the service IP deployment method of the present embodiment is shown in fig. 2.
Step 201, determining whether the first service IP is abnormal according to the acquired state information of the server group corresponding to the first service IP. If it is determined that there is an abnormality, step 202 is entered; if no abnormality is determined, the process is directly finished.
Specifically, the steps are substantially the same as step 101 in the first embodiment, and will not be described here again.
Step 202, it is determined whether the first service IP is limited. If yes, go to step 203; if not, the method is directly finished.
Specifically, when the monitoring platform determines that the first service IP is abnormal, determining whether the first service IP is limited, that is, determining whether the first service IP needs to be replaced, if the first service IP is limited, determining that the first service IP needs to be replaced, entering step 203 to obtain a second service IP, and scheduling the flow of the server group to the target server group through the scheduling device; if the first service IP is not limited, the first service IP can be repaired manually, and at the moment, fault alarm information can be sent to maintenance personnel to recover the available state of the first service IP through the manual abnormal repair.
In this embodiment, whether the first service IP is limited may be determined in two ways.
Firstly, judging whether a preset port of a first service IP is in a blocking state or not, namely judging that the preset port of the first service IP is not communicated, and judging that the first service IP is limited and the service IP needs to be replaced when the preset port of the first service IP is not communicated; otherwise, it indicates that the first service IP is not limited. The preset port is, for example, an 80 port, and the 80 port is judged to be not enabled by a telnet ip port mode, a port scanning tool mode or the like.
And secondly, judging whether the ping value of the first service IP meets a first preset condition, wherein the first preset condition is that the intranet ping value of the first service IP is matched with the extranet ping value of the first service IP. Specifically, the ping value refers to the time from the test end to the sending of data to the network server to the receiving of data fed back by the server, the monitoring equipment respectively obtains an intranet ping value of the first service IP and an extranet ping value of the first service IP, judges whether the absolute value of the difference value of the intranet ping value and the extranet ping value of the first service IP is smaller than a preset threshold, and judges whether the ping value of the first service IP meets a first preset condition or not when the absolute value of the difference value of the intranet ping value and the extranet ping value of the first service IP is smaller than the preset threshold, and the first service IP is not limited; otherwise, it indicates that the first service IP is limited.
And 203, acquiring a second service IP, and scheduling the flow of the server group to the target server group through the scheduling equipment. The steps are substantially the same as step 102 in the first embodiment, and will not be described in detail herein.
Step 204, replacing the second service IP with the service IP of the server group, and recovering the traffic of the server group. The steps are substantially the same as the step 103 in the first embodiment, and will not be described in detail here.
Compared with the first embodiment, the present embodiment enters the replacement process of the first service IP when the first service IP is abnormal and limited, thereby reducing the resource consumption of the monitoring device and reducing the consumption of the unused service IP.
A third embodiment of the present invention relates to a service IP deployment method, which is an improvement based on the first embodiment, and the main improvement is that: the determination of whether the traffic of the server farm has been processed is increased.
The specific flow of the service IP deployment method in this embodiment is shown in fig. 3.
Step 301, determining whether the first service IP is abnormal according to the acquired state information of the server group corresponding to the first service IP. If it is determined that there is an abnormality, go to step 302; if no abnormality is determined, the process is directly finished.
Specifically, the steps are substantially the same as step 101 in the first embodiment, and will not be described here again.
Step 302, a second service IP is acquired.
Specifically, the monitoring device acquires the available second service IP when determining that the first service IP is abnormal.
In step 303, it is determined whether the traffic of the server group has been scheduled. If yes, go to step 305; if not, go to step 304.
And step 304, dispatching the flow of the server group to the target server group through the dispatching equipment.
Specifically, after the monitoring device obtains the available second service IP and before replacing the first service IP, the monitoring device needs to process the traffic of the server group, firstly, determine whether the traffic of the server group is already scheduled, and in the process of providing the service, the server group can trigger automatic traffic scheduling in modes of standby, self-cutting and the like, if it is detected that the traffic of the server group is already scheduled, it is indicated that the traffic of the server group does not need to be processed, and directly enter step 305 to replace the second service IP with the service IP of the server group, and recover the traffic of the server group; otherwise, it is indicated that the traffic of the server group is not yet scheduled, and at this time, a scheduling instruction needs to be sent to the scheduling device to trigger the scheduling device to process the traffic of the server group corresponding to the first service IP, and schedule the traffic of the server group to an available target server group, so that the target server group can provide corresponding services for clients served by the server group corresponding to the first service IP.
Step 305, replacing the second service IP with the service IP of the server group, and recovering the traffic of the server group.
Specifically, the steps are substantially the same as step 103 in the first embodiment, and are not described herein, and the main differences are that: when the flow of the server group is restored, if the flow of the server group is scheduled to be scheduled to a target server group through the scheduling equipment, the monitoring equipment needs to initiate a flow restoration instruction to the scheduling equipment so as to control the scheduling equipment to restore the flow of the server group; if the traffic of the server group is not scheduled to the target server group through scheduling, after the service IP of the server group is replaced to be the second service IP, the second service IP is set to be in a normal state, and the server group can automatically recover the traffic.
Compared with the first embodiment, the method increases the judgment on whether the flow of the server group is processed, avoids repeated scheduling of the flow of the server group, further reduces the processing load of the monitoring equipment, and shortens the processing flow. The present embodiment may be modified from the second embodiment, and the same technical effects can be achieved.
A fourth embodiment of the present invention relates to a service IP deployment method, where the present embodiment is a refinement based on the first embodiment, and the main refinement is that: one particular implementation of scheduling traffic of a server farm to a target server farm by a scheduling device is provided.
The specific flow of the service IP deployment method in this embodiment is shown in fig. 4.
The steps 401 and 403 are substantially the same as the steps 101 and 103, and are not described herein, and the main difference is that the step 402 includes the following sub-steps:
sub-step 4021, a second service IP is acquired.
Specifically, the monitoring device acquires the available second service IP when determining that the first service IP is abnormal.
Sub-step 4022, sending the coverage information of the server group to the scheduling device, so as to select a traffic scheduling scheme from the resource pool of the resource management platform according to the coverage information, and scheduling the traffic of the server group to the target server group according to the traffic scheduling scheme.
Specifically, after the monitoring device acquires the available second service IP and before replacing the first service IP, the monitoring device needs to process the traffic of the server group, firstly, acquire coverage information of the server group, where the coverage information includes information of a city, a large area, an operator and the like to which the server group belongs, acquire a traffic scheduling scheme from a resource management platform through a scheduling device, specifically, the monitoring device sends the acquired coverage information of the server group to the scheduling device, and the scheduling device selects the traffic scheduling scheme from a resource pool of the resource management platform according to the coverage information, where the resource pool of the resource management platform includes information of the server group in a plurality of server clusters; wherein the scheduling device may be in the following priority order: the method comprises the steps of selecting a flow scheduling scheme by adopting modes of attempting to reduce, changing groups, forcing to reduce and the like, wherein the flow scheduling scheme comprises information of a target server group. Therefore, after the flow scheduling scheme is acquired, the flow of the server group can be scheduled to the target server group according to the information of the target server group in the flow scheduling scheme.
In this embodiment, compared to the first embodiment, a specific implementation manner of scheduling, by a scheduling device, traffic of a server group to a target server group is provided. The present embodiment may be modified from the second or third embodiment, and the same technical effects can be achieved.
A fifth embodiment of the present invention relates to a service IP deployment method, and the main difference between the present embodiment and the first embodiment is that: a specific implementation of obtaining the second service IP is provided.
The specific flow of the service IP deployment method in this embodiment is shown in fig. 5.
The steps 501 and 503 are substantially the same as the steps 101 and 103, and are not described herein, and the main difference is that the step 502 includes the following sub-steps:
sub-step 5021 receives the service IP allocated after the service IP application is issued and determines whether the allocated service IP is available. If so, go to sub-step 5022; if not, return to sub-step 5021.
Specifically, when the monitoring device determines that the first service IP is abnormal, the service flow of the monitoring device determines that the service flow needs to replace the service IP, initiates a service IP application to a preset service IP management platform, and the service IP management platform is responsible for managing the distribution of available service IP. The monitoring device determines whether the service IP is available, for example, in a ping test, if the service IP cannot be ping-enabled, indicating that the service IP is not currently used, and then enters a sub-step 5022; if the service IP is able to be ping-enabled, indicating that the service IP is currently used, the service IP cannot be used as the second service IP, returning to the substep 5021, initiating a service IP application to the service IP management platform again, and determining whether the allocated service IP is available or not until the available service IP is obtained.
Sub-step 5022, determines whether the allocated service IP satisfies a second preset condition. If so, go to sub-step 5023; if not, return to sub-step 5021.
Specifically, the monitoring device may obtain a preset change IP constraint condition from four balanced layers to which the server group belongs, where the change IP constraint condition is a second preset condition, determine whether the allocated service IP meets the second preset condition, and if the allocated service IP meets the second preset condition, enter a substep 5023 to use the allocated service IP as the second service IP; otherwise, it is indicated that the allocated service IP does not meet the second preset condition, and the service IP cannot be used as the second service IP, and the process returns to the sub-step 5021 until the service IP which is available and meets the second preset condition is obtained, and then the process proceeds to the sub-step 5023 to use the service IP as the second service IP.
The second preset condition may be set according to a type of the server group, for example, if the server group belongs to a four-layer balanced layer server group in the main mode, the service IP may be different from the first service IP in network segments; if the server group belongs to a four-layer balancing layer server group in the active-standby mode, the service IP may have to be the same network segment as the first service IP. In addition, the service IP needs to be located in the same virtual local area network as the first service IP.
Sub-step 5023 takes the allocated service IP as the second service IP.
This embodiment provides a specific implementation manner of obtaining the second service IP, compared to the first embodiment. The present embodiment may be modified from the second to fourth embodiments, and similar technical effects can be achieved.
A sixth embodiment of the present invention relates to a monitoring device, applied to a deployment system of a service IP, where the monitoring device may be a server, which may be used as a monitoring platform, and the monitoring device includes at least one processor; and a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the service IP deployment method according to any one of the first to fifth embodiments.
A seventh embodiment of the present invention relates to a service IP deployment system, including the monitoring device of the sixth embodiment, and a scheduling device connected to the monitoring device.
In this embodiment, the service IP deployment system may further include a resource management platform and a service IP management platform.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples of carrying out the invention and that various changes in form and details may be made therein without departing from the spirit and scope of the invention.

Claims (11)

1. A method for deploying service IP, applied to a monitoring device, the method comprising:
determining whether the first service IP is abnormal or not according to the acquired state information of a server group corresponding to the first service IP; the server group is one of the server groups hung down in the service cluster;
if the first service IP is determined to be abnormal, a second service IP is acquired, and the flow of the server group is scheduled to a target server group through scheduling equipment;
taking the second service IP as the service IP of the server group, and recovering the flow of the server group;
before the second service IP is acquired and the traffic of the server group is scheduled to the target server group by the scheduling device, the method further includes:
judging whether the first service IP is limited or not;
and if the first service IP is limited, entering the step of scheduling the traffic of the server group to a target server group.
2. The method for deploying service IP according to claim 1, wherein the determining whether the first service IP is limited comprises:
judging whether a preset port of the first service IP is in a blocking state or not;
and if the preset port of the first service IP is in a blocking state, judging that the first service IP is limited.
3. The method for deploying service IP according to claim 1, wherein the determining whether the first service IP is limited comprises:
judging whether the ping value of the first service IP meets a first preset condition or not, wherein the first preset condition is that the intranet ping value of the first service IP is matched with the extranet ping value of the first service IP;
and if the ping value of the first service IP meets a first preset condition, judging that the first service IP is limited.
4. The method for deploying service IP according to claim 1, further comprising, before the scheduling, by the scheduling device, the traffic of the server group to a target server group:
judging whether the traffic of the server group is already scheduled;
if the flow of the server group is not scheduled, entering a step of scheduling the flow of the server group to a target server group through scheduling equipment;
and if the traffic of the server group is scheduled, replacing the second service IP with the service IP of the server group.
5. The method for deploying service IP according to claim 1, wherein the scheduling, by the scheduling device, the traffic of the server group to the target server group comprises:
and acquiring a flow scheduling scheme from a resource management platform through the scheduling equipment so that the scheduling equipment schedules the flow of the server group to a target server group according to the flow scheduling scheme.
6. The method for deploying service IP according to claim 5, wherein the obtaining, by the scheduling device, the traffic scheduling scheme from the resource management platform comprises:
and sending the coverage information of the server group to the scheduling equipment so as to select the flow scheduling scheme from a resource pool of a resource management platform according to the coverage information.
7. The method for deploying service IP according to claim 1, wherein the obtaining the second service IP comprises:
receiving a service IP allocated after issuing a service IP application, and judging whether the allocated service IP is available;
and if the allocated service IP is available, taking the allocated service IP as the second service IP.
8. The method for deploying service IP according to claim 7, further comprising, before the service IP to be allocated as the second service IP:
judging whether the allocated service IP meets a second preset condition or not;
and if the allocated service IP meets a second preset condition, entering the step of taking the allocated service IP as the second service IP.
9. The service IP deployment method according to claim 8, wherein the second preset condition is that the allocated service IP is in the same network segment as the first service IP and/or that the allocated service IP is in the same virtual local area network as the first service IP.
10. A monitoring device, comprising: at least one processor; and a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of deploying a service IP according to any one of claims 1 to 9.
11. A service IP deployment system, comprising: the monitoring device of claim 10, and a scheduling device coupled to the monitoring device.
CN202010086090.6A 2020-02-11 2020-02-11 Service IP deployment method and system and monitoring equipment Active CN111314126B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010086090.6A CN111314126B (en) 2020-02-11 2020-02-11 Service IP deployment method and system and monitoring equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010086090.6A CN111314126B (en) 2020-02-11 2020-02-11 Service IP deployment method and system and monitoring equipment

Publications (2)

Publication Number Publication Date
CN111314126A CN111314126A (en) 2020-06-19
CN111314126B true CN111314126B (en) 2023-05-09

Family

ID=71148910

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010086090.6A Active CN111314126B (en) 2020-02-11 2020-02-11 Service IP deployment method and system and monitoring equipment

Country Status (1)

Country Link
CN (1) CN111314126B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116112569B (en) * 2023-02-23 2023-07-21 安超云软件有限公司 Micro-service scheduling method and management system

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000062502A2 (en) * 1999-04-12 2000-10-19 Rainfinity, Inc. Distributed server cluster for controlling network traffic

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103227839B (en) * 2013-05-10 2016-08-17 网宿科技股份有限公司 The management system of regional autonomy of content distribution network server
US20140359340A1 (en) * 2013-05-30 2014-12-04 Alcatel-Lucent Usa Inc. Subscriptions that indicate the presence of application servers
CN103905531A (en) * 2014-03-14 2014-07-02 浪潮电子信息产业股份有限公司 Method for converting load balancing among nodes in cluster storage system
CN107231399B (en) * 2016-03-25 2020-11-06 阿里巴巴集团控股有限公司 Capacity expansion method and device for high-availability server cluster
CN107483260B (en) * 2017-08-28 2021-03-02 北京三快在线科技有限公司 Fault processing method and device and electronic equipment

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000062502A2 (en) * 1999-04-12 2000-10-19 Rainfinity, Inc. Distributed server cluster for controlling network traffic

Also Published As

Publication number Publication date
CN111314126A (en) 2020-06-19

Similar Documents

Publication Publication Date Title
CN106209447B (en) The fault handling method and device of distributed caching
CN109474465A (en) A kind of method and system of the high availability that can dynamically circulate based on server cluster
CN104038376A (en) Method and device for managing real servers and LVS clustering system
CN105515812A (en) Fault processing method of resources and device
CN112583648B (en) Intelligent service fault processing method based on DNS
CN107276839B (en) Self-monitoring method and system of cloud platform
CN110932914B (en) Deployment method, deployment device, hybrid cloud system architecture and computer storage medium
CN111314126B (en) Service IP deployment method and system and monitoring equipment
CN102984184A (en) A method and a device for service load balancing for a distributed system
CN109697078B (en) Repairing method of non-high-availability component, big data cluster and container service platform
CN105812161B (en) A kind of controller failure backup method and system
CN111752140A (en) Controller application module coordinator
CN111988347B (en) Data processing method of board hopping machine system and board hopping machine system
CN109039795A (en) A kind of Cloud Server resource monitoring method and system
CN109788012B (en) Health examination method and device, health examination control method and controller
KR20150124642A (en) Communication failure recover method of parallel-connecte server system
CN107026762B (en) Disaster recovery system and method based on distributed cluster
CN104125079A (en) Method and device for determining double-device hot-backup configuration information
CN108092829A (en) Processing method, SDN controllers and the storage medium of cluster division
CN113890850B (en) Route disaster recovery system and method
CN108196441B (en) Method for realizing hot standby redundancy for system application
CN110618664A (en) Decentralized distributed control system and control method thereof
JP3563338B2 (en) Time synchronization method and communication device
CN112491464B (en) Distributed fault real-time monitoring and standby equipment switching method for satellite communication
CN110365936A (en) Code stream acquisition methods, apparatus and system

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