CN116319547A - Network address management method, device and system, electronic equipment and storage medium - Google Patents

Abstract

The application provides a network address management method, device, system, electronic equipment and storage medium, and relates to the technical field of Internet. The network address management method comprises the following steps: acquiring a static network address under a target domain name; monitoring the network state of the static network address; responding to the target static network address with the monitored network state change, and determining a management mode of the target static network address according to the network state change of the target static network address; and managing the target static network address based on the determined management mode. According to the technical scheme, the network state of the static network address under the target domain name is monitored, and under the condition that the network state of a certain static network address (namely the target static network address) changes, a management mode corresponding to the network state change is timely decided, and is managed based on the management mode, so that a convenient and stable operation and maintenance guarantee scheme can be provided for network services adopting static routing.

Description

Network address management method, device and system, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to a method, an apparatus, a system, an electronic device, and a storage medium for managing a network address.

Background

The border gateway protocol (Border Gateway Protocol, BGP) is a dynamic routing protocol that can be used between different autonomous systems (Autonomous System, AS) and within the same AS. BGP dynamic routing (also known as dynamic bandwidth allocation) may provide stable network service but increase traffic costs. If the interconnection between the operators and the service is realized by adopting a static route (also called static bandwidth allocation), the flow cost can be greatly reduced, but because the static route is a service shared line, the disaster recovery can not be carried out in different places after the failure occurs, and the stability is generally lower than that of the BGP dynamic route.

Disclosure of Invention

The embodiment of the application provides a network address management method, device, system, electronic equipment and storage medium, so as to provide a network address management method based on static routing.

In a first aspect, an embodiment of the present application provides a method for managing a network address, including: acquiring a static network address under a target domain name; monitoring the network state of the static network address; responding to the target static network address with the monitored network state change, and determining a management mode of the target static network address according to the network state change of the target static network address; and managing the target static network address based on the determined management mode.

In a second aspect, an embodiment of the present application provides a network address management apparatus, including: a static network address acquisition unit for acquiring a static network address under the target domain name; the monitoring unit is used for monitoring the network state of the static network address; a management mode determining unit, configured to determine, in response to monitoring that a target static network address with a network state that changes, a management mode for the target static network address according to the network state change of the target static network address; and the management unit is used for managing the target static network address based on the determined management mode.

In a third aspect, an embodiment of the present application provides a management system for a network address, including: the client is used for configuring information of the target domain name to be managed according to the user command; and the management device of the network address is used for acquiring the target domain name from the client and realizing the method provided by any embodiment of the application.

In a fourth aspect, embodiments of the present application provide an electronic device including a memory, a processor, and a computer program stored on the memory, the processor implementing the method provided by any of the embodiments of the present application when the computer program is executed.

In a fifth aspect, embodiments of the present application provide a computer readable storage medium having a computer program stored therein, the computer program, when executed by a processor, implementing a method provided by any embodiment of the present application.

Compared with the prior art, the technical scheme of the embodiment of the application has the following advantages: by monitoring the network state of the static network address under the target domain name, and under the condition that the network state of a certain static network address (namely the target static network address) changes, timely deciding a management mode corresponding to the network state change, and managing the static network address based on the management mode, a convenient and stable operation and maintenance guarantee scheme can be provided for the network service adopting the static route.

The foregoing summary is for the purpose of the specification only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features of the present application will become apparent by reference to the drawings and the following detailed description.

Drawings

In the drawings, the same reference numerals refer to the same or similar parts or elements throughout the several views unless otherwise specified. The figures are not necessarily drawn to scale. It is appreciated that these drawings depict only some embodiments according to the disclosure and are not therefore to be considered limiting of its scope.

Fig. 1 is a schematic diagram of a system architecture of a network address management method according to an embodiment of the present application;

fig. 2 is a flowchart of a method for managing network addresses according to an embodiment of the present application;

FIG. 3 is a diagram illustrating an exemplary network status according to one embodiment of the present application;

fig. 4 is an exemplary diagram of a network probing method according to an embodiment of the present application;

fig. 5 is an exemplary diagram of a method for managing network addresses according to an embodiment of the present application;

FIG. 6 is an exemplary diagram of disaster recovery operation according to an embodiment of the present application;

FIG. 7 is a schematic diagram of a recovery operation according to a first embodiment of the present disclosure;

fig. 8 is an exemplary diagram of an implementation method of a network address management device according to the second embodiment of the present application;

fig. 9 is a schematic diagram of a network address management device according to a third embodiment of the present application;

fig. 10 is a block diagram of an electronic device according to a third embodiment of the present application.

Detailed Description

Hereinafter, only certain exemplary embodiments are briefly described. As will be recognized by those of skill in the pertinent art, the described embodiments may be modified in various different ways without departing from the spirit or scope of the present application. Accordingly, the drawings and description are to be regarded as illustrative in nature and not as restrictive.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description is given of related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as an alternative, which all belong to the protection scope of the embodiments of the present application.

The following terms are used herein

Domain Name (Domain Name): the network domain is the name of a computer or group of computers on the internet, which is composed of a series of names separated by points, and is used for locating and identifying the computers during data transmission.

Domain name system (Domain Name System, DNS): is a service of the internet. It acts as a distributed database mapping domain names and network addresses to each other, enabling users to more conveniently access the internet without having to remember a network address string.

Network detection: network connectivity is tested, i.e. the network connectivity of a certain static network address is detected as normal or abnormal. Such as testing network connectivity with a packet probing (Packet Internet Groper, ping) command or testing network connectivity with a transmission control protocol packet probing (Transmission Control Packet Internet Groper, tcping) command.

Network probe: an electronic device or software program for implementing network probing.

Disaster recovery operation: in the embodiment of the application, network disaster tolerance refers to that a static network address is unbound from a domain name under the condition that network connectivity of the static network address is abnormal, and the static network address is downloaded.

Recovery operation: in the embodiment of the application, a certain static network address is online, so that the static network address is rebindd under a certain domain name, and the static network address is online.

System and application scenario

In the application scenario of the data center, in order to reduce the traffic cost, the interconnection between the operators and the services may be implemented by adopting a static routing (may also be called static bandwidth allocation) manner. The static route is a service shared line, after the fault occurs, the remote disaster recovery cannot be carried out, and most of the services have no monitoring and disaster recovery processing capacity of the static route.

The embodiment of the application aims to provide a network address management method and a network address management system, which are used for automatically monitoring the network state of a static network address under a certain domain name and deciding a corresponding management mode in time under the condition that the network state of a certain static network address (such as a target static network address) changes. The management mode includes, but is not limited to, disaster recovery operation, alarm or prompt, etc. Further, it is managed based on the management manner, for example: when the management mode is disaster recovery operation, executing disaster recovery operation on the static network address to unbind the static network address from a domain name, and then disconnecting the static network address; when the management mode is a recovery operation, executing the recovery operation on the static network address so as to bind the static network address under a domain name and then to connect the static network address online; when the management mode is alarming or prompting, corresponding alarming information or prompting information is sent. Based on the method, a convenient and stable operation and maintenance guarantee scheme can be provided for the network service adopting the static route.

Fig. 1 shows an architecture diagram of a network address management system provided according to an embodiment of the present application. As shown in fig. 1, the system may include a client 101 and a management device 102 for network addresses.

The client 101 may provide an operation platform, and a user interacts with the operation platform through a user command, thereby configuring management information. Wherein the management information includes, but is not limited to: application of nanotubes, target domain names to be managed, relevant rules of network detection (such as detection parameters and network connectivity rules), relevant rules of alarm or prompt (such as automatic disaster recovery conditions and automatic recovery conditions), and the like. The client 101 may interact with the network address management device 102, and further issue management information configured by the user to the network address management device 102. Thus, flexible rule configuration capabilities may be provided to the user.

The network address management device 102 is configured to execute the network address management method provided in the embodiments of the present application, and includes monitoring a network state of a static network address under a target domain name, and deciding a corresponding management mode in time when the network state of a certain static network address (e.g., a target static network address) changes, and managing the static network address based on the management mode. Further, the management manner includes an automatic disaster recovery operation or an automatic recovery operation, and the management device 102 of the network address can perform the automatic disaster recovery operation or the automatic recovery operation on the static network address when necessary, thereby providing a reliable remote disaster recovery processing capability.

Illustratively, the management apparatus 102 of the network address may perform a management method of the network address based on the management information configured by the user. For example: determining information of a static network address under a target domain name based on information of the target domain name configured by a user; another example is: based on the network connectivity rule configured by the user, determining that the network connectivity of the static network address is normal or abnormal; and the following steps: based on the relevant rules of the alarm or prompt configured by the user, the management mode or the management execution result is sent to the client to alarm or prompt the user and the like.

The client 101 may be hardware, such as an electronic device, such as a mobile phone, a personal computer, a tablet computer, and a wearable device, and the client may also be an Application (APP) installed in the electronic device.

The network address management device 102 may be disposed on a physical server including an independent host, or may be disposed on a virtual server (such as a cloud server) carried by a host cluster, which is not limited in this embodiment of the present application.

Example 1

Fig. 2 shows a flowchart of a method of managing network addresses according to an embodiment of the present application. The network address management method can be applied to the network address management apparatus 102. In the embodiment of the present application, by starting a network address management device 102 (i.e. starting a process), the method of the embodiment of the present application is executed, so that a target domain name can be managed. It can be understood that, the method of the embodiment of the present application may also be executed by starting a plurality of processes to implement respective management of a plurality of target domain names.

As shown in fig. 2, the network address management method includes:

step S201: and acquiring a static network address under the target domain name.

The target domain name may be a domain name to be managed configured by the user based on the client 101 (as shown in fig. 1). For example, the client 101 may provide an operation platform, and the user interacts with the operation platform through a user command to configure information of the target domain name to be managed, and issues the information of the target domain name to be managed to the management device 102 of the network address through interaction with the management device 102 of the network address. Thus, flexible domain name information configuration capability can be provided for the user.

In the embodiment of the present application, the static network address is mainly a static IP address. The network address management apparatus 102 acquires a static network address under a destination domain name, such as a static IP group (including a plurality of static IP addresses), and manages the static IP group. It should be noted that, all static network addresses under the target domain name may be obtained, or a part of static network addresses may be obtained according to management information configured by a user, and the static network addresses of the part may be managed.

Step S202: the network status of the static network address is monitored.

In the embodiment of the application, the network state of the static network address can be monitored from two dimensions of network connectivity and binding relation with the target domain name. Illustratively, network connectivity includes both cases of normal network connectivity and abnormal network connectivity, i.e., whether the network connectivity of the static network address is healthy. The binding relationship with the target domain name includes both the case of binding under the target domain name and the case of not binding under the target domain name, i.e., whether the static network address survives.

Step S203: and responding to the target static network address with the monitored network state change, and determining a management mode of the target static network address according to the network state change of the target static network address.

Wherein the target static network address is the static network address with the network state changed. For example, if the network state of a static network address is monitored to change from a first network state to a second network state, the static network address is the target static network address. According to the network state change condition of the target static network address, the corresponding management mode can be decided, namely, the network state change is different, and the corresponding management mode is different. The management mode includes, but is not limited to, disaster recovery operation, alarm or prompt, etc.

Step S204: and managing the target static network address based on the determined management mode.

For example: when the management mode is disaster recovery operation, executing disaster recovery operation on the target static network address to unbind the target static network address from the target domain name, and then disconnecting the target static network address; when the management mode is a recovery operation, the recovery operation is executed on the target static network address so as to bind the target static network address under the target domain name and further to online the target static network address; when the management mode is alarming or prompting, corresponding alarming information or prompting information is sent.

Illustratively, the disaster recovery operation may include an automatic disaster recovery operation, that is, the management device 102 of the network address may perform the automatic disaster recovery operation on the target static network address; the restoration operations may include an automatic restoration operation, i.e., the management device 102 of the network address may perform an automatic restoration operation on the target static network address, thereby providing reliable off-site disaster recovery processing capability.

In one embodiment, the static network address may have four network states based on two dimensions of network connectivity and binding relationship with the target domain name. As shown in fig. 3, four boxes represent four network states. The first network state is that the network connectivity is normal (i.e. healthy) and is bound under the target domain name, the second network state is that the network connectivity is abnormal (i.e. unhealthy or network is not available) and is bound under the target domain name, the third network state is that the network connectivity is abnormal and is not bound under the target domain name, and the fourth network state is that the network connectivity is normal and is not bound under the target domain name. Therefore, the manner in which network state monitoring is performed based on two dimensions, network connectivity and binding relationship with the target domain name, may also be referred to as a state space approach.

The network state of the static network address is managed based on the state space method, and the decision of the management mode of the network address is made based on the network state, so that all possible faults and recovery scenes can be covered, conflicts with other domain name change operations can be avoided, and reliable disaster recovery bottom capability is provided for users.

In one embodiment, in step S201, monitoring the network status of the static network address includes: and monitoring the network connectivity of the static network address according to the network detection signals of the plurality of network detectors to the static network address.

Based on the method, the input of a plurality of network detection signals can be supported, and then the static network address is cross-validated based on the plurality of network detection signals, so that the accuracy and the reliability of network detection are ensured.

Multiple network probe signals cross-verify network connectivity, which may be, for example: according to the detection parameters configured by the user, the network connectivity anomaly is only decided when each network detection signal reflects the network connectivity anomaly. Of course, the confidence level of each network probe signal can also be configured according to the probe parameters configured by the user. Wherein the user may configure the probe parameters based on an operating platform provided by the client 101 (as shown in fig. 1).

In one embodiment, the plurality of network probe signals may be derived based on different network probe approaches including, but not limited to, at least one of packet probe (Packet Internet Groper, ping) command probe based and transmission control protocol packet probe (Transmission Control Packet Internet Groper, tcping) command probe based.

Based on different network detection modes, the network communication is cross-verified, and the accuracy and reliability of network detection can be further improved. The ping command is a service command of an application layer in a transmission control protocol (Transmission Control Protocol, TCP)/IP network architecture, and is used for determining whether a local host can successfully exchange data packets with another host, and then deducing whether the network is unobstructed according to the returned information. the tcping command may use the TCP transport layer protocol to detect IP port status and view ping values, which may monitor network status.

In one embodiment, the network probe includes at least one of a fourth version of an internet communication protocol (Internet Protocol Version, ipv 4) probe and a sixth version of an internet communication protocol (Internet Protocol Version, ipv 6) probe.

Network connectivity is cross-validated based on network detection signals obtained by different types of network detectors, so that the accuracy and reliability of network detection can be further improved.

Illustratively, as shown in fig. 4, the network address management apparatus may acquire network probe signals of a plurality of network probes by interfacing with already deployed network probe management platforms, such as a site monitoring platform and a fault discovery platform. The network detection signal of the ipv4 detector can be obtained through the docking station monitoring platform. Network detection signals of an edge node service (Edge Node Service, ENS) node detector (ipv 4 detector) can be obtained through the docking fault discovery platform; network probe signals of the mobile probe (ipv 6 probe) can also be acquired.

In one embodiment, monitoring network connectivity of a static network address based on network probe signals of a plurality of network probes to the static network address comprises: acquiring a network connectivity rule configured by a user; judging whether the network detection signal accords with the network connectivity rule; and determining that the network connectivity of the static network address is normal or abnormal according to the judging result.

Wherein a user may configure network connectivity rules based on an operating platform provided by client 101 (shown in fig. 1). Thus, a flexible network connectivity rule configuration capability may be provided to the user. For example: configuring detection duration and fault rate, namely determining network connectivity abnormality when the detection duration is reached and the network detection signal fault rate reaches a certain threshold value; or when the network detection signal fault rate is reduced to another threshold value within a certain detection duration range, determining that the network connectivity is normal.

In one embodiment, in step S202, monitoring the network status of the static network address includes: acquiring an analysis record of a target domain name in real time; and determining the binding relation between the static network address and the target domain name according to the analysis record.

That is, the binding relationship between the static network address and the target domain name can be obtained by continuously synchronizing the resolution record of the target domain name in real time. Illustratively, the management device of the network address may synchronize the iDNS state by calling the iDNS interface (e.g., calling the iDNS platform) to obtain the resolution record of the target domain name in real time.

Based on the embodiments, the network state of the static network address can be accurately and reliably monitored from two dimensions of network connectivity and binding relation with the target domain name. Furthermore, when the network state changes, a corresponding management mode can be decided, and the timeliness and stability of network management are improved.

The following describes how to specifically decide the corresponding management manner according to the network state change.

In one embodiment, in step S203, determining a management manner for the target static network address according to the network status change of the target static network address includes: and responding to the network state of the target static network address to change from the first network state to the second network state, determining that the management mode of the target static network address is a disaster recovery operation, wherein the disaster recovery operation is used for changing the network state of the target static network address to a third network state.

The first network state is normal in network connectivity and is bound under the target domain name, the second network state is abnormal in network connectivity and is bound under the target domain name, and the third network state is abnormal in network connectivity and is not bound under the target domain name. The network states are described in the foregoing, and are not described in detail herein.

A change in the network state of a static network address typically can only change one dimension, i.e., the network connectivity changes or the binding relationship with the target domain name changes. As shown in fig. 5, solid lines among four network states represent monitored network state changes, and broken lines represent triggered execution flows (actions), which manage the target static network address based on the determined management manner in step S204. Illustratively, the execution flow includes a disaster recovery flow and a restoration flow.

When the network connectivity of a static network address bound under the target domain name is abnormal (fault), the network state of the static network address is changed to be unhealthy, namely, the network state of the static network address is changed from a first network state to a second network state, and at the moment, a management device of the network address needs to make a decision to correspond to a disaster recovery operation in a management mode, a disaster recovery process is triggered, and the target static network address is timely and accurately ensured to be timely and accurately.

In one embodiment, in step S204, managing the target static network address based on the determined management manner includes: executing automatic disaster recovery operation on the target static network address under the condition that the management device of the network address meets the preset automatic disaster recovery condition; or sending disaster recovery alarm information to the client under the condition that the management device of the network address does not meet the automatic disaster recovery condition or the automatic disaster recovery operation fails to be executed, so as to prompt the user to perform manual disaster recovery operation on the target static network address.

Wherein the automatic disaster recovery conditions can be configured by a user based on an operation platform provided by the client 101 (as shown in fig. 1). Illustratively, the automatic disaster recovery condition needs to be configured to ensure that when a target static network address is down (the binding relationship with the target domain name is released), an error that the target domain name cannot be resolved is not caused.

For example, as shown in fig. 6, if the management device 102 (as shown in fig. 1) of the network address hits the automatic disaster recovery condition, which indicates that the management device 102 of the network address is capable of automatically recovering the disaster, the management mode is an automatic disaster recovery operation, and then the management device 102 of the network address will perform an automatic disaster recovery operation on the target static network address (such as the target static IP address), for example, by calling the iDNS interface to perform an on-line disaster recovery, and then the target static IP address is disconnected, that is, the binding relationship between the target static IP address and the target domain name is released.

If the management device 102 of the network address does not hit the automatic disaster recovery condition, or if the automatic disaster recovery operation of the management device 102 of the network address fails, which means that the management device 102 of the network address cannot automatically recover the disaster, the management mode further includes an alarm, and the management device 102 of the network address based on the management mode sends disaster recovery alarm information to the client 101 to prompt the user to perform the manual disaster recovery operation on the target static IP address. For example, the client 101 notifies the user that the target static IP address needs to be manually disconnected in a mail manner within a preset time.

Illustratively, as described above, the management manner may further include a prompt, and the management apparatus 102 based on the network address of the management manner may transmit the execution result of the management manner to the client 101 to prompt the user. For example, as shown in fig. 6, if the offline is successful, the mail notifies the user that the target static IP address has been automatically offline, and gives a reason for the automatic offline.

That is, the management device entering the disaster recovery process first determines whether the network address management device can automatically recover the disaster, if so, executes the automatic disaster recovery operation, and if not, or if the execution of the automatic disaster recovery operation fails, notifies the user of the reason through the client, and reminds the user of the manual disaster recovery operation. When the target static network address is monitored to be disconnected, the management device of the network address can identify that one manual disaster recovery operation is finished. And after the disaster recovery operation is finished, the network state of the target static network address is migrated to a third network state, namely, the network connectivity is abnormal and is not bound under the target domain name. And further, the conflict with other disaster recovery systems can be avoided, and the stability and reliability of disaster recovery operation are ensured.

In one embodiment, in step S203, determining a management manner for the target static network address according to the network status change of the target static network address includes: in response to the network state of the target static network address changing from the third network state to the fourth network state, determining that the management mode of the target static network address is a restoration operation for changing the network state of the target static network address to the first network state.

The first network state is normal in network connectivity and is bound under the target domain name, the third network state is abnormal in network connectivity and is not bound under the target domain name, and the fourth network state is normal in network connectivity and is not bound under the target domain name. The network states are described in the foregoing, and are not described in detail herein.

As shown in fig. 5, when the network connectivity of a static network address that is unhealthy (abnormal network connectivity) and not bound under the target domain name is normal (failure recovery), the network state of the static network address may change to healthy (normal network connectivity) and not bound under the target domain name, that is, the network state of the static network address changes from the third network state to the fourth network state, and at this time, the management device of the network address needs to make a decision to correspond to a recovery operation, triggers a recovery flow, and timely goes to the target static network address, thereby timely and accurately guaranteeing the reliability of the decision.

In one embodiment, in step S204, managing the target static network address based on the determined management manner includes: executing automatic recovery operation of the target static network address under the condition that the management device of the network address meets the preset automatic recovery condition; or sending recovery prompt information to the client to prompt the user to perform manual recovery operation on the target static network address under the condition that the management device of the network address does not meet the automatic recovery condition or the automatic recovery operation fails to be performed.

Wherein the automatic recovery condition may be configured by a user based on an operating platform provided by the client 101 (shown in fig. 1). Illustratively, the automatic recovery condition may be configured to include: the target static network address is subordinate to the target domain name; the target static network address has no fault; the DNS configuration for the target static network address is correct.

Illustratively, as shown in fig. 7, if the management device 102 (as shown in fig. 1) of the network address hits an auto-recovery condition, which indicates that the management device 102 of the network address is capable of auto-recovery, the management manner is an auto-recovery operation, and the management device 102 of the network address will perform an auto-recovery operation for a target static IP address (e.g., a target static IP address). For example, the iDNS interface is called to perform online recovery, and the online target static IP address is obtained, namely the target static IP address and the target domain name are rebinding.

If the network address management device 102 does not hit the automatic recovery condition, or if the network address management device 102 fails to automatically recover, indicating that the network address management device 102 cannot automatically recover, the management mode further includes a prompt, and the network address management device 102 based on the management mode sends recovery prompt information to the client 101 to prompt the user to manually recover the target static IP address. For example, the client 101 notifies the user that the target static IP address needs to be manually restored in the form of a mail within a preset time.

Illustratively, as described above, the management manner may further include a hint, based on which the management apparatus 102 of the network address may transmit a management execution result to the client 101 to notify the user. For example, as shown in fig. 7, if the online is successful, the mail notifies the user that the target static IP address has been automatically restored, and gives a reason for the automatic restoration.

That is, the entering restoration flow first determines whether the management apparatus of the network address can automatically restore, and if so, directly performs the automatic restoration operation. If the automatic recovery operation cannot be performed or the automatic recovery operation fails to be performed, the user needs to be notified of the manual recovery operation by the user. When the management device of the network address synchronizes the iDNS state and finds that the target static network address is already bound under the target domain name, the manual recovery flow is ended. The recovery operation is ended and the network state of the target static network address is migrated to the first network state, i.e. the network connectivity is normal and bound under the target domain name. And further, the static network address of the online fault recovery can be timely obtained, and timeliness and stability of recovery operation are guaranteed.

Global traffic management (Global Traffic Manager, GTM) may rely on network probe capability to modify DNS resolution records for domain names, but its decision engine is weak in function and difficult to flexibly configure rules. The site monitoring platform has the capability of monitoring the post-callback interface, but requires the user to build the network address management capability. The embodiment of the application can provide a set of network operation and maintenance stability guarantee system with multiple network detection signal inputs and based on a central decision engine. Through the interaction between the client and the management device of the network address, the user can flexibly configure the management information; the monitoring adopts a mode of cross verification of multiple schemes, so that the reliability of network detection is ensured to the maximum extent; the state space method is adopted in decision making to manage the network state of the static network address, so that the reliability of decision making can be ensured, conflicts with other disaster recovery systems or other domain name change operations can be avoided, most possible faults and recovery scenes can be covered, and reliable disaster recovery spam capability is provided for users.

Example two

The embodiment of the application provides a network address management device, where the technical solution in the first embodiment may be partially or fully introduced into the embodiment of the application.

In one implementation manner, the network address management device of the embodiment of the application may include a configuration management center, a monitoring module, an algorithm and decision module, and an execution module. The modules can be deployed on the same main body or on different main bodies. The main body may be a physical server of an independent host, or may be a virtual server (such as a cloud server) borne by a host cluster, which is not limited in this embodiment of the present application.

Wherein the configuration management center may be used to perform the method of step S201, the monitoring module may be used to perform the method of step S202, the algorithm and decision module may be used to perform the method of step S203, and the execution module may be used to perform the method of step S204.

Illustratively, as shown in fig. 8, the client provides an operation platform, through which a user interacts with the operation platform through user commands, and further configures management information, including: configuring the application of the nano tube and the information of the target domain name; relevant rules of network detection, such as detection parameters and network connectivity rules, relevant rules of alarm or prompt, such as automatic disaster recovery conditions, automatic recovery conditions, alarm threshold values, alarm modes or prompt modes, and the like are configured.

The configuration management center acquires a static network address (such as a static IP address) under the target domain name in real time based on the information of the configured target domain name. The obtained static IP addresses can be a plurality of static IP groups, and the static IP addresses are issued to the algorithm and decision module. The configuration management center also triggers the monitoring module to create or modify the detection task according to the configured relevant rules of network detection.

The data generated by the monitoring module executing the probing task, such as network probing signals of a plurality of network probes to the static IP address, can be used to monitor the network connectivity of the static IP address.

The algorithm and decision module obtains relevant rules such as alarm or prompt and the information of the static IP address from the configuration management center, judges the network state change of the target static IP address, and synchronizes the network state change of the target static IP address to the operation platform so as to alarm the user. The algorithm and decision module decides corresponding management modes, such as disaster recovery operation or recovery operation, according to the rule configured by the user and the network state change of the target static IP address, on one hand, the management modes needed to be done on the target static network are synchronized to the operation platform so as to prompt the user, and on the other hand, the management flow is triggered. Under the condition that the execution module can execute the automatic disaster recovery operation or the automatic recovery operation, the management flow executes the automatic disaster recovery operation or the automatic recovery operation by the execution module and synchronizes the execution result to the operation platform so as to prompt a user.

The execution module can call the iDNS interface to delete or recover the target static IP address in the DNS analysis record of the target domain name, thereby realizing disaster recovery and recovery of the target static IP address. The disaster recovery and recovery operations are essentially change operations, and therefore, the network address management device according to the embodiments of the present application can interface with the already deployed change management platform to record and manage all change operations of the static IP address.

Example III

Corresponding to the method provided by the embodiment of the application, the embodiment of the application also provides a device for managing the network address. As shown in fig. 9, the network address management apparatus may include: a static network address obtaining unit 901, configured to obtain a static network address under a destination domain name; a monitoring unit 902, configured to monitor a network state of the static network address; a management mode determining unit 903, configured to determine, in response to monitoring that a target static network address with a network state that changes, a management mode for the target static network address according to the network state change of the target static network address; a management unit 904, configured to manage the target static network address based on the determined management manner.

In one embodiment, where the network state includes network connectivity, the monitoring unit 902 may be specifically configured to: and monitoring the network connectivity of the static network address according to the network detection signals of the plurality of network detectors to the static network address.

In one embodiment, the monitoring unit 902 may be specifically configured to: acquiring a network connectivity rule configured by a user; judging whether the network detection signal accords with the network connectivity rule; and determining that the network connectivity of the static network address is normal or abnormal according to the judging result.

In one embodiment, the network probing signal is detected by at least one of a network packet based probing command and a transmission control protocol based network packet based probing command.

In one embodiment, the network probe includes at least one of a fourth version of an internet communication protocol probe and a sixth version of an internet communication protocol probe.

In one embodiment, the network state includes a binding relationship with the target domain name, and the monitoring unit 902 may be specifically configured to: acquiring an analysis record of a target domain name in real time; and determining the binding relation between the static network address and the target domain name according to the analysis record.

In one embodiment, the management mode determining unit 903 may be specifically configured to: responding to the network state of the target static network address to change from the first network state to the second network state, determining that the management mode of the target static network address is disaster tolerant operation, wherein the disaster tolerant operation is used for changing the network state of the target static network address to a third network state; the first network state is normal in network connectivity and is bound under the target domain name, the second network state is abnormal in network connectivity and is bound under the target domain name, and the third network state is abnormal in network connectivity and is not bound under the target domain name.

In one embodiment, the management unit 904 may be specifically configured to: executing automatic disaster recovery operation on the target static network address under the condition that the management device of the network address meets the preset automatic disaster recovery condition; or sending disaster recovery alarm information to the client under the condition that the management device of the network address does not meet the automatic disaster recovery condition or the automatic disaster recovery operation fails to be executed, so as to prompt the user to perform manual disaster recovery operation on the target static network address.

In one embodiment, the management mode determining unit 903 may be specifically configured to: in response to the network state of the target static network address changing from the third network state to the fourth network state, determining that the management mode of the target static network address is a recovery operation, wherein the recovery operation is used for changing the network state of the target static network address to the first network state; the first network state is normal in network connectivity and is bound under the target domain name, the third network state is abnormal in network connectivity and is not bound under the target domain name, and the fourth network state is normal in network connectivity and is not bound under the target domain name.

In one embodiment, the management unit 904 may be specifically configured to: executing automatic recovery operation of the target static network address under the condition that the management device of the network address meets the preset automatic recovery condition; or sending recovery prompt information to the client to prompt the user to perform manual recovery operation on the target static network address under the condition that the management device of the network address does not meet the automatic recovery condition or the automatic recovery operation fails to be performed.

The functions of each module in each device of the embodiments of the present application may be referred to the corresponding descriptions in the above methods, and have corresponding beneficial effects, which are not described herein.

It should be noted that, user information (including, but not limited to, user equipment information, user personal information, user operation information, etc.), data (including, but not limited to, data for processing, analyzed data, stored data, displayed data, etc.), and signals, etc. referred to in the present application are information, data, and signals authorized by the user or sufficiently authorized by each party, and the collection, use, and processing of related information, data, and signals is required to comply with the relevant laws and regulations and standards of the relevant country and region, and is provided with corresponding operation entries for the user to select authorization or rejection.

Fig. 10 is a block diagram of an electronic device used to implement an embodiment of the present application. As shown in fig. 10, the electronic device includes: memory 1001 and processor 1002, and memory 1001 stores a computer program executable on processor 1002. The processor 1002 when executing the computer program implements the methods of the above embodiments. The number of memories 1001 and processors 1002 may be one or more.

The electronic device further includes: and the communication interface 1003 is used for communicating with external equipment and carrying out data interaction transmission.

If the memory 1001, the processor 1002, and the communication interface 1003 are implemented independently, the memory 1001, the processor 1002, and the communication interface 1003 may be connected to each other through a bus and perform communication with each other. The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component Interconnect, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 10, but not only one bus or one type of bus.

Alternatively, in a specific implementation, if the memory 1001, the processor 1002, and the communication interface 1003 are integrated on a single chip, the memory 1001, the processor 1002, and the communication interface 1003 may complete communication with each other through internal interfaces.

Embodiments of the present application provide a computer readable storage medium storing a computer program which, when executed by a processor, implements a method provided in any of the embodiments of the present application.

The embodiment of the application also provides a chip, which comprises a processor, and is used for calling the instructions stored in the memory from the memory and running the instructions stored in the memory, so that the communication device provided with the chip executes the method provided by any embodiment of the application.

The embodiment of the application also provides a chip, which comprises: the input interface, the output interface, the processor and the memory are connected through an internal connection path, the processor is used for executing codes in the memory, and when the codes are executed, the processor is used for executing the method provided by any embodiment of the application.

It should be appreciated that the processor may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field Programmable gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or any conventional processor or the like. It is noted that the processor may be a processor supporting an advanced reduced instruction set machine (Advanced RISC Machines, ARM) architecture.

Alternatively, the memory may include a read-only memory and a random access memory, and may also include a nonvolatile random access memory. The memory may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), programmable ROM (PROM), erasable Programmable ROM (EPROM), electrically Erasable EPROM (EEPROM), or flash Memory, among others. Volatile memory can include random access memory (Random Access Memory, RAM), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available. For example: static RAM (SRAM), dynamic RAM (Dynamic Random Access Memory, DRAM), synchronous DRAM (SDRAM), double Data Rate Synchronous DRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct RAM (DRRAM).

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. Computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another.

In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.

Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.

Any process or method description in a flowchart or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process. And the scope of the preferred embodiments of the present application includes additional implementations in which functions may be performed in a substantially simultaneous manner or in an opposite order from that shown or discussed, including in accordance with the functions that are involved.

Logic and/or steps represented in the flow diagrams or otherwise described herein, e.g.: may be considered a ordered listing of executable instructions for implementing logical functions, and may be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.

It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the methods of the embodiments described above may be performed by a program that, when executed, comprises one or a combination of the steps of the method embodiments, instructs the associated hardware to perform the method.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules described above, if implemented in the form of software functional modules and sold or used as a stand-alone product, may also be stored in a computer-readable storage medium. The storage medium may be a read-only memory, a magnetic or optical disk, or the like.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of various changes or substitutions within the technical scope of the present application, and these should be covered in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (14)

1. A method of managing network addresses, comprising:

acquiring a static network address under a target domain name;

monitoring the network state of the static network address;

responding to a target static network address with the monitored network state change, and determining a management mode of the target static network address according to the network state change of the target static network address;

and managing the target static network address based on the determined management mode.

2. The method of claim 1, wherein the network state comprises network connectivity, and monitoring the network state of the static network address comprises:

and monitoring the network connectivity of the static network address according to the network detection signals of the plurality of network detectors on the static network address.

3. The method of claim 2, wherein monitoring network connectivity of the static network address based on network probe signals of a plurality of network probes to the static network address comprises:

acquiring a network connectivity rule configured by a user;

judging whether the network detection signal accords with the network connectivity rule;

and determining that the network connectivity of the static network address is normal or abnormal according to the judging result.

4. The method of claim 2, wherein the network probe signal probe manner includes at least one of a network packet probe command based probe and a transmission control protocol network packet probe command based probe.

5. The method of claim 2, wherein the network probe comprises at least one of a fourth version of an internet communication protocol probe and a sixth version of an internet communication protocol probe.

6. The method of claim 1, wherein the network state comprises a binding relationship with the target domain name, monitoring the network state of the static network address comprises:

acquiring an analysis record of the target domain name in real time;

and determining the binding relation between the static network address and the target domain name according to the analysis record.

7. The method of claim 1, wherein determining a manner of management of the target static network address based on a network state change of the target static network address comprises:

responding to the network state of the target static network address to change from a first network state to a second network state, and determining that the management mode of the target static network address is disaster recovery operation, wherein the disaster recovery operation is used for changing the network state of the target static network address to a third network state;

the first network state is normal in network connectivity and is bound under the target domain name, the second network state is abnormal in network connectivity and is bound under the target domain name, and the third network state is abnormal in network connectivity and is not bound under the target domain name.

8. The method of claim 7, wherein the network address management method is applied to a network address management device, and the target static network address is managed based on a determined management manner, and includes:

executing automatic disaster recovery operation on the target static network address under the condition that the management device of the network address meets a preset automatic disaster recovery condition; or alternatively, the process may be performed,

And sending disaster recovery alarm information to a client under the condition that the management device of the network address does not meet the automatic disaster recovery condition or the automatic disaster recovery operation fails to be executed, so as to prompt a user to perform manual disaster recovery operation on the target static network address.

9. The method of claim 1, wherein determining a manner of management of the target static network address based on a network state change of the target static network address comprises:

determining that the management mode of the target static network address is a recovery operation in response to the network state of the target static network address being changed from the third network state to the fourth network state, wherein the recovery operation is used for changing the network state of the target static network address to the first network state;

the first network state is normal in network connectivity and is bound under the target domain name, the third network state is abnormal in network connectivity and is not bound under the target domain name, and the fourth network state is normal in network connectivity and is not bound under the target domain name.

10. The method according to claim 9, wherein the network address management method is applied to a network address management device, and the target static network address is managed based on a determined management manner, and includes:

Executing automatic recovery operation of the target static network address under the condition that the management device of the network address meets the preset automatic recovery condition; or alternatively, the process may be performed,

and sending recovery prompt information to the client to prompt a user to perform manual recovery operation on the target static network address under the condition that the management device of the network address does not meet the automatic recovery condition or the automatic recovery operation fails to be performed.

11. A network address management apparatus comprising:

a static network address acquisition unit for acquiring a static network address under the target domain name;

the monitoring unit is used for monitoring the network state of the static network address;

a management mode determining unit, configured to determine, in response to monitoring that a target static network address with a network state that changes, a management mode for the target static network address according to the network state change of the target static network address;

and the management unit is used for managing the target static network address based on the determined management mode.

12. A network address management system, comprising:

the client is used for configuring information of the target domain name to be managed according to the user command;

Network address management means for obtaining the target domain name from the client and implementing the method of any of claims 1-10.

13. An electronic device comprising a memory, a processor and a computer program stored on the memory, the processor implementing the method of any one of claims 1-10 when the computer program is executed.

14. A computer readable storage medium having stored therein a computer program which, when executed by a processor, implements the method of any of claims 1-10.

Images