A method and apparatus for automatic verification and self-healing of FIP binding

Abstract

This invention discloses an automatic verification and self-healing method and apparatus for FIP binding. The method includes: a customer initiating a request to bind an FIP to the network console; after receiving a successful binding message, the FIP binding verification module calls the dial-up analysis capability provided by the dial-up probe to initiate a dial-up test on the FIP binding; a data acquisition module collects the dial-up test results and session information; analyzes whether inbound traffic has increased; collects configuration information for Neutron and NATGW to obtain the latest configuration information data; analyzes the consistency of the configuration information data; if the Neutron and NATGW configuration information data are inconsistent, updates the NATGW parameter configuration; analyzes whether inbound traffic has increased; if it has not increased, the binding failure or ineffectiveness is due to unknown reasons; in unknown scenarios, an alarm message is sent and manual intervention is performed, completing the process loop. This invention verifies the FIP binding effect in a timely and effective manner by establishing a procedural verification mechanism and self-healing rules, and performs self-healing processing when verification fails.

Description

Technical Field

[0001] This invention relates to the field of communications, and in particular to a method and apparatus for automatic verification and self-healing of FIP binding. Background Technology

[0002] Floating IP addresses (FIPs) are a common feature in public clouds. By directly binding a public IP address to a host's network interface card (NIC), they enable direct communication between the host and the external network. They can be unbound at any time and associated with any other host. Essentially, a floating IP is a one-to-one static NAT (Network Address Translation), translating the host's internal network address into a public IP address, enabling communication between the host and the outside world. When a tenant creates an FIP association, neutron L3agent, as an API extension (creating routers or floating IPs via APIs to provide routing and NAT functionality), creates a network namespace on the node, acting as a Layer 3 plugin to implement NAT address translation. The FIP connects to the external network on one end and to the router on the other. FIPs allow the external network to directly access instances within the tenant's network.

[0003] During the FIP binding process, the user initiates an FIP binding request to the network console. After completing the FIP binding operation, the network console sends a successful binding message to the user. However, in reality, binding may fail or not take effect, resulting in the binding not achieving the expected results and the function not working properly.

[0004] The traditional FIP binding process involves the user initiating a FIP binding request, sending the request information to the network console, and then the network console sending the configuration parameters to Neutron to complete the FIP binding configuration. Because OpenStack virtualization technology is used, there are situations where the network console has completed the FIP binding configuration update, but Neutron has not actually configured it or the configuration is incomplete. This results in no increase in inbound traffic, meaning the expected binding effect is not achieved.

[0005] After FIP binding is completed, the user is unaware of the actual binding result. Faults are only reported when problems occur during subsequent use. Maintenance personnel then investigate the cause of the unsuccessful FIP binding and perform repairs. This process is highly reactive, with high timeliness requirements for problem-solving, placing significant workload on maintenance personnel. Summary of the Invention

[0006] To address the problems existing in the prior art, this invention provides an automatic verification and self-healing method and apparatus for FIP binding. By establishing a procedural verification mechanism and self-healing rules, the FIP binding effect is verified in a timely and effective manner. When the verification fails, self-healing is performed, thereby minimizing the workload of maintenance personnel and improving maintenance efficiency.

[0007] To achieve the above objectives, the present invention adopts the following technical solution:

[0008] In one embodiment of the present invention, an automatic verification and self-healing method for FIP binding is proposed, the method comprising:

[0009] S01. The customer initiates a request to bind the FIP to the network console. The network console sends a binding success message to the customer and the FIP binding verification module at the same time.

[0010] S02. Receive the binding success information through the FIP binding verification module, call the dial test analysis capability provided by the dial test probe, and initiate the dial test of the FIP binding;

[0011] S03. Collect dial test results and session information through the data acquisition module;

[0012] S04. Based on the latest cloud traffic collected in the previous step, compare it with the historical cloud traffic and analyze whether the latest cloud traffic collected has increased compared with the historical cloud traffic. If there is no increase, proceed to S05.

[0013] Furthermore, S04 also includes the following: if the latest collected inbound cloud traffic increases compared to the historical inbound cloud traffic, then the FIP binding has been verified and the automatic verification process ends.

[0014] S05. Collect configuration information for Neutron and NATGW respectively, and obtain the latest configuration information data;

[0015] S06. Analyze the consistency of Neutron and NATGW configuration information data. If the Neutron and NATGW configuration information data are consistent, it means that there is no problem with the configuration. The reason for the binding failure or the binding not taking effect is unknown. Proceed to S09.

[0016] Furthermore, the Neutron and NATGW configuration information data in S06 includes: instance name, inbound bandwidth, outbound bandwidth, public IP address, version, FIP_ID, internal IP, Dummy IP, bandwidth ID, PORTID, tenant ID, VPCID, etc.

[0017] If the configuration information data of S07 Neutron and NATGW is inconsistent, then update the NATGW parameter configuration, that is, call the NATGW update capability to perform self-healing work;

[0018] S08. Analyze whether the inbound traffic has increased. If it has not increased and the binding is not effective for unknown reasons, proceed to S09.

[0019] Furthermore, once the inbound traffic increases and self-healing is successful, the FIP binding self-healing is completed, and the process ends.

[0020] S09: For unknown scenarios, send alarm information and require manual intervention, thus completing the closed-loop process.

[0021] In one embodiment of the present invention, an automatic verification and self-healing device for FIP binding is also proposed, the device comprising:

[0022] When binding the FIP module, the customer sends a request to the network console to bind the FIP. The network console will simultaneously send a binding success message to the customer and the FIP binding verification module.

[0023] After receiving the successful binding information, the FIP binding verification module calls the dial-up analysis capability provided by the dial-up probe to initiate a dial-up test on the FIP binding.

[0024] The data acquisition module collects test results and session information.

[0025] The cloud traffic analysis module compares the latest cloud traffic collected in the previous step with the historical cloud traffic to analyze whether the latest cloud traffic collected has increased compared with the historical cloud traffic. If there is no increase, it proceeds to the configuration information acquisition module.

[0026] Furthermore, the inbound traffic analysis module also includes a condition where, if the latest collected inbound traffic increases compared to historical inbound traffic, then the FIP binding has been verified and the automatic verification process ends.

[0027] The configuration information acquisition module collects configuration information from Neutron and NATGW respectively, and obtains the latest configuration information data.

[0028] The configuration information consistency judgment module analyzes the consistency of Neutron and NATGW configuration information data. If the Neutron and NATGW configuration information data are consistent, it means that there is no problem with the configuration. If the binding fails or does not take effect for unknown reasons, the alarm information sending module 190 is entered.

[0029] Furthermore, the Neutron and NATGW configuration information data in the configuration information consistency judgment module include: instance name, inbound bandwidth, outbound bandwidth, public IP address, version, FIP_ID, internal IP, Dummy IP, bandwidth ID, PORTID, tenant ID, VPCID, etc.

[0030] If the configuration information data of the NATGW update module, Neutron and NATGW are inconsistent, the NATGW parameter configuration will be updated, that is, the NATGW update capability will be invoked to perform self-healing.

[0031] The cloud traffic growth judgment module analyzes whether the cloud traffic has increased. If it still has not increased, and the binding is unsuccessful or ineffective for unknown reasons, it enters the alarm information sending module.

[0032] Furthermore, the cloud traffic growth judgment module also includes: successful cloud traffic growth self-healing, that is, FIP binding self-healing is completed and the process ends.

[0033] Alarm message sending module: In unknown scenarios, send alarm messages and require manual intervention, creating a closed-loop process.

[0034] In one embodiment of the present invention, a computer device is also proposed, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the aforementioned FIP binding automatic verification and self-healing method.

[0035] In one embodiment of the present invention, a computer-readable storage medium is also provided, which stores a computer program that performs an FIP binding automatic verification and self-healing method.

[0036] Beneficial effects:

[0037] 1. This invention provides an automatic verification and self-healing method and apparatus for FIP binding. By establishing a standardized verification mechanism and self-healing rules, the FIP binding effect is verified in a timely and effective manner, and self-healing is performed when verification fails. This minimizes the workload of maintenance personnel and improves maintenance efficiency.

[0038] 2. Through the capability-based interface design, this invention can call and connect to the relevant capabilities provided by various platforms, and can also open its own capabilities to other platforms and scenarios for use, forming capability reuse and quickly adapting to changes in fault self-healing requirements.

[0039] 3. The standardized capability interface design of this invention means that when specific instructions or interface parameters change, there is no need to modify the interface; only the corresponding instructions or interface parameters need to be modified to complete the adaptation, resulting in high scalability of the device. Attached Figure Description

[0040] Figure 1 This is a schematic diagram of the automatic verification and self-healing method for FIP binding in this invention;

[0041] Figure 2 This is a schematic diagram of the FIP binding automatic verification and self-healing device of the present invention;

[0042] Figure 3 This is a schematic diagram of a computer device structure according to an embodiment of the present invention. Detailed Implementation

[0043] The principles and spirit of the present invention will now be described with reference to several exemplary embodiments. It should be understood that these embodiments are provided merely to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. Rather, these embodiments are provided to make this disclosure more thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art.

[0044] Those skilled in the art will recognize that embodiments of the present invention can be implemented as a system, apparatus, device, method, or computer program product. Therefore, this disclosure can be specifically implemented in the following forms: entirely hardware, entirely software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0045] The terms involved in this invention and their Chinese explanations are as follows:

[0046] NAT: Network Address Translation;

[0047] NATGW: NAT gateway;

[0048] DummyIP: Virtual IP, disguised IP;

[0049] RocketMQ is a pure Java, distributed, queue-based open-source message middleware that supports transactional messages, sequential messages, batch messages, timed messages, and message backtracking.

[0050] According to an embodiment of the present invention, an automatic verification and self-healing method and apparatus for FIP binding is proposed. By formulating a procedural verification mechanism and self-healing processing rules, the FIP binding effect is verified in a timely and effective manner. When the verification fails, self-healing processing is performed, thereby minimizing the workload of operation and maintenance personnel and improving operation and maintenance efficiency.

[0051] The principles and spirit of the present invention will be explained in detail below with reference to several representative embodiments.

[0052] This invention relates to an automatic verification and self-healing method for FIP binding, the method comprising:

[0053] S01. The customer initiates a request to bind the FIP to the network console. The network console sends a binding success message to the customer and the FIP binding verification module at the same time.

[0054] S02. After receiving the successful binding information, the FIP binding verification module calls the dial-up analysis capability provided by the dial-up probe to initiate a dial-up test on the FIP binding.

[0055] S03, The data acquisition module collects the dial-up test results and session information;

[0056] Session information includes: scheduling serial number, address pool ID, queried FIP information, inbound traffic, and anomaly description information;

[0057] S04. Based on the latest cloud traffic collected in the previous step, compare it with the historical cloud traffic and analyze whether the latest cloud traffic collected has increased compared with the historical cloud traffic. If there is no increase, proceed to S05.

[0058] S04 also includes the following: if the latest collected inbound traffic increases compared to the historical inbound traffic, then the FIP binding has been verified and the automatic verification process ends.

[0059] S05. Collect configuration information for Neutron and NATGW respectively, and obtain the latest configuration information data;

[0060] S06. Analyze the consistency of Neutron and NATGW configuration information data. If the Neutron and NATGW configuration information data are consistent, it means that there is no problem with the configuration. The reason for the binding failure or the binding not taking effect is unknown. Proceed to S09.

[0061] The Neutron and NATGW configuration information includes: instance name, inbound bandwidth, outbound bandwidth, public IP address, version, FIP_ID, internal IP, Dummy IP, bandwidth ID, PORTID, tenant ID, VPCID, etc.

[0062] If the configuration information data of S07 Neutron and NATGW is inconsistent, then update the NATGW parameter configuration, that is, call the NATGW update capability to perform self-healing work;

[0063] S08. Analyze whether the inbound traffic has increased. If it has not increased and the binding is not effective for unknown reasons, proceed to S09.

[0064] The cloud traffic growth and successful self-healing indicate that the FIP binding self-healing is complete and the process ends.

[0065] S09: For unknown scenarios, send alarm information and require manual intervention, thus completing the closed-loop process.

[0066] It should be noted that although the operation of the method of the present invention has been described in a specific order in the above embodiments and figures, this does not require or imply that the operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0067] To provide a clearer explanation of the above-mentioned FIP binding automatic verification and self-healing method, a specific embodiment is described below. However, it is worth noting that this embodiment is only for better illustrating the present invention and does not constitute an improper limitation of the present invention.

[0068] like Figure 1 As shown, the method includes:

[0069] S01. The customer initiates a request to bind the FIP to the network console. The network console sends a binding success message to the customer and the FIP binding verification module at the same time.

[0070] S02. After receiving the successful binding information, the FIP binding verification module calls the dial-up analysis capability provided by the dial-up probe to initiate a dial-up test on the FIP binding.

[0071] Test interface:

[0072] Interface field descriptions and input parameters are shown in Table 1 below.

[0073] Attribute Code Attribute type Attribute Description Is it non-empty? Format ID String Dispatch serial number Required For example: 2017081164732 CAPACITY String Interface capabilities Required FIP dial test POOLID String Address pool ID Required

[0074] Table 1

[0075] Example of a JSON object:

[0076] {

[0077] "ID":"XXXXX",

[0078] "CAPACITY":"XXXXX",

[0079] "POOLID":"XXXXX"

[0080] }

[0081] The interface fields are described in Table 2 below.

[0082] Attribute Code Attribute type Attribute Description Is it non-empty? Format ID String Dispatch serial number Required For example: 2017081164732 POOLID String Address pool ID Required For example: 10001 RESULT String Request result Required For example: 0, normal; 1, abnormal. ERRORRESULT String Exception Description Required For example: Description of the cause of the abnormality

[0083] Table 2

[0084] Example of a JSON object:

[0085] {

[0086] "ID":"XXXXX",

[0087] "POOLID":"XXXXX",

[0088] "RESULT":"XXXXX",

[0089] "ERRORRESULT":"XXXXX"

[0090] S03, The data acquisition module collects the dial-up test results and session information;

[0091] Interface for collecting test results and session information:

[0092] The interface fields are described in Table 3 below.

[0093]

[0094] Table 3

[0095] Example of a JSON object:

[0096] {

[0097] "ID":"XXXXX",

[0098] "POOLID":"XXXXX",

[0099] "FIP":"XXXXX",

[0100] "FlUX":"XXXXX",

[0101] "ERRORRESULT":"XXXXX"

[0102] S04. Based on the latest cloud traffic collected in the previous step, compare it with the historical cloud traffic and analyze whether the latest cloud traffic collected has increased compared with the historical cloud traffic. If there is no increase, proceed to S05.

[0103] S04 also includes the following: if the latest collected inbound traffic increases compared to the historical inbound traffic, then the FIP binding has been verified and the automatic verification process ends.

[0104] S05. Collect configuration information for Neutron and NATGW respectively, and obtain the latest configuration information data;

[0105] S06. Analyze the consistency of Neutron and NATGW configuration information data. If the Neutron and NATGW configuration information data are consistent, it means that there is no problem with the configuration. The reason for the binding failure or the binding not taking effect is unknown. Proceed to S09.

[0106] The Neutron and NATGW configuration information includes: instance name, inbound bandwidth, outbound bandwidth, public IP address, version, FIP_ID, internal IP, Dummy IP, bandwidth ID, PORTID, tenant ID, VPCID, etc.

[0107] If the configuration information data of S07 Neutron and NATGW is inconsistent, then update the NATGW parameter configuration, that is, call the NATGW update capability to perform self-healing work;

[0108] Interface method: RESTful

[0109] URL: {URL} / checknat

[0110] Request method: POST

[0111] The request parameters are shown in Table 4 below:

[0112] Parameter encoding Parameter meaning Parameter type Is it mandatory? Remark fip public IP address String yes fipid FIP corresponding ID String yes az Used to distinguish resource pools from different provincial nodes String yes

[0113] Table 4

[0114] Input parameter example:

[0115]

[0116]

[0117] The returned parameters are shown in Table 5 below.

[0118] Parameter encoding Parameter meaning Parameter type Is it mandatory? Remark detail Details Object yes status_code status codes Integer yes

[0119] Table 5

[0120] The detail objects are shown in Table 6 below:

[0121] Parameter encoding Parameter meaning Parameter type Is it mandatory? Remark message information String yes

[0122] Table 6

[0123] Example of inverse parameter:

[0124] (1) Success:

[0125]

[0126]

[0127]

[0128] S08. Analyze whether the inbound traffic has increased. If it has not increased and the binding is not effective for unknown reasons, proceed to S09.

[0129] The cloud traffic growth and successful self-healing indicate that the FIP binding self-healing is complete and the process ends.

[0130] S09: For unknown scenarios, send alarm information and require manual intervention, thus completing the closed-loop process.

[0131] The Java client connects to RocketMQ as a consumer, subscribes to a specified topic, and receives real-time alarm information for parsing and processing.

[0132] The alarm information parameter parsing explanation is shown in Table 7 below:

[0133]

[0134]

[0135] Table 7

[0136] Based on the same inventive concept, this invention also proposes an automatic verification and self-healing device for FIP binding. The implementation of this device can refer to the implementation of the method described above, and repeated details will not be elaborated further. The term "module" used below can refer to a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0137] Figure 2 This is a schematic diagram of the FIP binding automatic verification and self-healing device of the present invention. Figure 2 As shown, the device includes:

[0138] Module 110: When the customer initiates a request to bind an FIP to the network console, the network console sends a successful binding message to the customer and the FIP binding verification module.

[0139] After receiving the successful binding information, the FIP binding verification module 120 calls the dialing analysis capability provided by the dialing probe to initiate a dialing test on the FIP binding.

[0140] Data acquisition module 130 collects dial test results and session information;

[0141] The cloud traffic analysis module 140 compares the latest cloud traffic collected in the previous step with the historical cloud traffic to analyze whether the latest cloud traffic collected has increased compared with the historical cloud traffic. If there is no increase, it proceeds to the configuration information acquisition module 150.

[0142] The cloud traffic analysis module 140 also includes a condition where the FIP binding has been verified if the latest collected cloud traffic has increased compared to the historical cloud traffic, and the automatic verification process ends.

[0143] Configuration information acquisition module 150 collects configuration information from Neutron and NATGW respectively, and obtains the latest configuration information data;

[0144] Configuration information consistency judgment module 160 analyzes the consistency of Neutron and NATGW configuration information data. If Neutron and NATGW configuration information data are consistent, it means that there is no problem with the configuration. If the binding fails or does not take effect for unknown reasons, proceed to alarm information sending module 190.

[0145] The Neutron and NATGW configuration information data in the configuration information consistency judgment module 160 include: instance name, inbound bandwidth, outbound bandwidth, public IP address, version, FIP_ID, internal IP, Dummy IP, bandwidth ID, PORTID, tenant ID, VPCID, etc.

[0146] If the configuration information data of NATGW update module 170, Neutron and NATGW are inconsistent, then update the NATGW parameter configuration, that is, call the NATGW update capability to perform self-healing work;

[0147] The cloud traffic growth judgment module 180 analyzes whether the cloud traffic has increased. If it has not increased and the binding is unsuccessful or ineffective for unknown reasons, it enters the alarm information sending module 190.

[0148] The cloud traffic growth judgment module 180 also includes: cloud traffic growth self-healing successful, that is, FIP binding self-healing completed, and the process ends.

[0149] Alarm message sending module 190: In unknown scenarios, send alarm messages and require manual intervention, creating a closed-loop process.

[0150] It should be noted that although several modules of the FIP binding automatic verification and self-healing device are mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of the present invention, the features and functions of two or more modules described above can be embodied in one module. Conversely, the features and functions of one module described above can be further divided and embodied by multiple modules.

[0151] Based on the aforementioned inventive concept, such as Figure 3 As shown, the present invention also proposes a computer device 200, including a memory 210, a processor 220, and a computer program 230 stored in the memory 210 and executable on the processor 220. When the processor 220 executes the computer program 230, it implements the aforementioned FIP binding automatic verification and self-healing method.

[0152] Based on the aforementioned inventive concept, the present invention also proposes a computer-readable storage medium storing a computer program that executes the aforementioned FIP binding automatic verification and self-healing method.

[0153] This invention provides an automatic verification and self-healing method and apparatus for FIP binding. By establishing a standardized verification mechanism and self-healing rules, the method effectively and promptly verifies the FIP binding effect and performs self-healing when verification fails. This minimizes the workload of maintenance personnel and improves maintenance efficiency.

[0154] This invention, through a capability-based interface design, can call and connect to relevant capabilities provided by various platforms, and can also open its own capabilities to other platforms and scenarios for use, forming capability reuse and quickly adapting to changes in fault self-healing requirements;

[0155] The standardized capability interface design of this invention allows for adaptation without modifying the interface itself when specific instructions or interface parameters change; only the corresponding instructions or interface parameters need to be modified. This results in high scalability of the device.

[0156] While the spirit and principles of the invention have been described with reference to several specific embodiments, it should be understood that the invention is not limited to the disclosed specific embodiments, and the division of aspects does not imply that features in these aspects cannot be combined for benefit; such division is merely for ease of description. The invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

[0157] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0158] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0159] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0160] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0161] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0162] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0163] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0164] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

[0165] Regarding the limitation of the scope of protection of this invention, those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art without creative effort based on the technical solution of this invention are still within the scope of protection of this invention.

Claims

1. A method for automatic verification and self-healing of FIP binding, characterized in that, The method includes: S01. The customer initiates a request to bind the FIP to the network console. The network console sends a binding success message to the customer and the FIP binding verification module at the same time. S02. After receiving the successful binding information, the FIP binding verification module calls the dial-up analysis capability provided by the dial-up probe to initiate a dial-up test on the FIP binding. S03. The data acquisition module collects the test results and session information; the session information includes: scheduling serial number, address pool ID, queried FIP information, inbound traffic, and anomaly description information; S04. Compare the inbound cloud traffic collected in S03 with the historical inbound cloud traffic, and analyze whether the collected inbound cloud traffic has increased compared with the historical inbound cloud traffic. If there is no increase, proceed to S05. S05. Collect configuration information for Neutron and NATGW respectively, and obtain the latest configuration information data; S06. Analyze the consistency of Neutron and NATGW configuration information data. If the Neutron and NATGW configuration information data are consistent, it means that there is no problem with the configuration. The reason for the binding failure or the binding not taking effect is unknown. Proceed to S09. If the configuration information data of S07 Neutron and NATGW is inconsistent, then update the NATGW parameter configuration, that is, call the NATGW update capability to perform self-healing work; S08. Analyze whether the inbound traffic has increased. If it has not increased and the binding is not effective for unknown reasons, proceed to S09. S09. In unknown scenarios, send alarm information and require manual intervention, thus completing the process loop.

2. The FIP binding automatic verification and self-healing method according to claim 1, characterized in that, S04 also includes the following: if the latest collected inbound traffic increases compared to the historical inbound traffic, then the FIP binding has been verified and the automatic verification process ends.

3. The FIP binding automatic verification and self-healing method according to claim 1, characterized in that, The Neutron and NATGW configuration information data in S06 includes: instance name, inbound bandwidth, outbound bandwidth, public IP address, version, FIP_ID, internal IP, Dummy IP, bandwidth ID, PORT ID, tenant ID, and VPC ID.

4. The FIP binding automatic verification and self-healing method according to claim 1, characterized in that, In step S08, the inbound traffic to the cloud increases, and self-healing is successful, meaning the FIP binding self-healing is complete and the process ends.

5. An automatic verification and self-healing device for FIP bonding, characterized in that, The device includes: When binding the FIP module, the customer sends a request to the network console to bind the FIP. The network console will simultaneously send a binding success message to the customer and the FIP binding verification module. After receiving the successful binding information, the FIP binding verification module calls the dial-up analysis capability provided by the dial-up probe to initiate a dial-up test on the FIP binding. The data acquisition module collects test results and session information; session information includes: scheduling serial number, address pool ID, queried FIP information, inbound traffic, and anomaly description information; The cloud traffic analysis module compares the cloud traffic collected by the data collection module with the historical cloud traffic to analyze whether the collected cloud traffic has increased compared with the historical cloud traffic. If there is no increase, it proceeds to the configuration information acquisition module. The configuration information acquisition module collects configuration information from Neutron and NATGW respectively, and obtains the latest configuration information data. The configuration information consistency judgment module analyzes the consistency of Neutron and NATGW configuration information data. If the Neutron and NATGW configuration information data are consistent, it means that there is no problem with the configuration. If the binding fails or does not take effect for unknown reasons, the alarm information sending module will be entered. If the configuration information data of the NATGW update module, Neutron and NATGW are inconsistent, the NATGW parameter configuration will be updated, that is, the NATGW update capability will be invoked to perform self-healing. The cloud traffic growth judgment module analyzes whether the cloud traffic has increased. If it still has not increased, and the binding is unsuccessful or ineffective for unknown reasons, it enters the alarm information sending module. The alarm information sending module sends alarm information and allows manual intervention in unknown scenarios, creating a closed-loop process.

6. The FIP binding automatic verification and self-healing method according to claim 5, characterized in that, The inbound traffic analysis module also includes a step where, if the latest collected inbound traffic increases compared to historical inbound traffic, then the FIP binding has been verified and the automatic verification process ends.

7. The FIP binding automatic verification and self-healing method according to claim 5, characterized in that, The configuration information consistency judgment module includes Neutron and NATGW configuration information data such as: instance name, inbound bandwidth, outbound bandwidth, public IP address, version, FIP_ID, internal IP, Dummy IP, bandwidth ID, PORT ID, tenant ID, and VPC ID.

8. The FIP binding automatic verification and self-healing method according to claim 5, characterized in that, The cloud traffic growth judgment module also includes: cloud traffic growth self-healing successful, that is, FIP binding self-healing completed, and the process ends.

9. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 1-4.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that performs the method according to any one of claims 1-4.

Images