CN111030868B - Method for solving failure of elastic public network IP issuing equipment - Google Patents
Method for solving failure of elastic public network IP issuing equipment Download PDFInfo
- Publication number
- CN111030868B CN111030868B CN201911317565.1A CN201911317565A CN111030868B CN 111030868 B CN111030868 B CN 111030868B CN 201911317565 A CN201911317565 A CN 201911317565A CN 111030868 B CN111030868 B CN 111030868B
- Authority
- CN
- China
- Prior art keywords
- issuing
- equipment
- public network
- request
- issuing equipment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 12
- 239000012792 core layer Substances 0.000 claims abstract description 7
- 239000010410 layer Substances 0.000 abstract description 7
- 230000007246 mechanism Effects 0.000 abstract description 5
- 230000008569 process Effects 0.000 abstract description 4
- 238000011084 recovery Methods 0.000 abstract description 2
- 238000005457 optimization Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0866—Checking the configuration
- H04L41/0869—Validating the configuration within one network element
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a solution for failure of an elastic public network IP issuing device, which relates to the technical field of elastic public network IP application, and comprises the following steps of S1, creating a public network IP and a virtual machine, and binding the public network IP and the virtual machine; s2, the Core layer triggers binding operation, records a state table of the issuing equipment and assembles data of the issuing equipment; s3, calling an Agent by combining the issued message with the key of the redis cache as the request; s4, judging whether the Agent issuing equipment is successful or not, simultaneously returning the request, improving two independent processes of the storage of the upper layer database and the issuing equipment into a scheme of the issuing equipment capable of actively triggering retry to perform configuration after the issuing equipment fails, and adding a callback mechanism between the upper layer service and the Agent, so that the problem that equipment data caused by the equipment issuing failure are inconsistent with the upper layer database can be effectively solved, meanwhile, the problem of specific step out in the process of positioning the issuing equipment can be conveniently solved, and the manual recovery on site and the re-issuing can be realized.
Description
Technical Field
The invention relates to the technical field of elastic public network IP application, in particular to a method for solving failure of elastic public network IP issuing equipment.
Background
The elastic public network IP can be used as a public network IP address resource purchased and held independently and can be bound to an ECS instance of a proprietary network type, a private network SLB instance of the proprietary network type, an auxiliary elastic network card of the proprietary network type, an NAT gateway and a high-availability virtual IP. When the elastic public network IP binds the virtual machine or unbinds the virtual machine, NAT rules are issued on the firewall and bandwidth information is issued on the exit route, the issued NAT rules are used for two-way mapping the public network IP and the private network IP on the virtual machine network card, so that the virtual machine can communicate with the public network, the bandwidth information is issued on the exit route for traffic speed limiting, therefore, one operation involves issuing configuration to a plurality of network devices, and the whole operation flow can be completed only if the configuration issuing is successful. Aiming at the operation of the traditional elastic public network IP, the repository and the issuing configuration are two processes, and the uncontrollability of the issuing equipment can lead to inconsistent configuration of the database and the network equipment, so that the resource residue is caused, and the operation of the subsequent resource is greatly influenced. It is therefore necessary to provide a solution for failure of the elastic public network IP delivery device in order to address the deficiencies of the prior art.
Disclosure of Invention
In order to overcome the defects in the prior art, the method for solving the failure of the elastic public network IP delivery equipment effectively solves the problem that equipment data and an upper layer database are inconsistent due to the failure of the equipment delivery, can conveniently position the specific step of the delivery equipment, and can manually recover the site and deliver again.
In order to achieve the above object, the method for solving the failure of the elastic public network IP delivery device of the present invention includes the following steps:
s1, creating a public network IP and a virtual machine, and binding the public network IP and the virtual machine;
s2, the Core layer triggers binding operation, records a state table of the issuing equipment and assembles data of the issuing equipment;
s3, calling an Agent by combining the issued message with the key of the redis cache as the request;
s4, judging whether the Agent issuing equipment is successful or not, and simultaneously returning the request.
Preferably, in S4, if the issuing device fails, the following steps are performed:
s5, firstly, modifying a state table of the issuing equipment, changing the issuing state into a failure state, and then analyzing the request to obtain the Id of the corresponding public network IP, the Id of the operating equipment and the operation attribute.
Preferably, in S4, if the issuing device is successful, the following steps are performed:
s6, firstly, modifying a state table of the issuing equipment, changing the issuing state into a successful state, and additionally removing data with key values of requestId and requestId+num from redis.
Preferably, in S5, when the issuing fails, the Core layer records the number of retries, stores the retries in redis with the requestid+num as key, and automatically increments one for each retry until three retries.
Preferably, if three retries all end in failure, the failed requestId can be queried from the redis, and the interface is manually invoked for device delivery.
The invention has the following beneficial effects:
the method has the advantages that two independent processes of the storage of the upper layer database and the issuing equipment are improved to be a scheme of the issuing equipment which can actively trigger the retry to be configured after the issuing equipment fails, and a callback mechanism is added between the upper layer service and the Agent, so that the problem that equipment data caused by the issuing failure of the equipment are inconsistent with the upper layer database can be effectively solved, meanwhile, the problem of specific step in the issuing equipment can be conveniently located, and the on-site recovery and the re-issuing can be realized manually.
Drawings
The invention is further described and illustrated below with reference to the accompanying drawings.
Fig. 1 is a flow chart of a solution for failure of an elastic public network IP delivery device.
Detailed Description
The technical solution of the present invention will be more clearly and completely explained by the description of the preferred embodiments of the present invention with reference to the accompanying drawings.
Examples
As shown in fig. 1, a solution for failure of an elastic public network IP delivery device,
s1, creating a public network IP and a virtual machine, and binding the public network IP and the virtual machine;
s2, the Core layer triggers binding operation, records a state table of the issuing equipment and assembles data of the issuing equipment;
s3, the key of the redis cache is a request, and by combining the issued message, an Agent is called, the Agent technology receives the registration of the information key points related to the information distributor and the registration of the information requirement key points related to the information inquirer, and the Agent actively informs the user who can provide the required information or actively informs the information provider who needs the information which can be provided by the information inquirer according to the information;
s4, judging whether the Agent issuing equipment is successful or not, and simultaneously returning the request.
As a technical optimization scheme of the invention, if the issuing equipment fails in S4, the following steps are carried out: s5, firstly, modifying a state table of the issuing equipment, changing the issuing state into a failure state, then analyzing the request, obtaining the Id of the corresponding public network IP, the operating equipment Id and the operating attribute, recording the retry times by the Core layer, storing the Redis by taking the RequestId+num as a key, automatically adding one for each retry until the retry is performed three times, and if the retry is finished in failure for three times, inquiring the failed RequestId from the redis, manually calling an interface, and issuing the equipment.
By adopting the technical scheme, a retry mechanism and manual triggering are added, the state of the state table of the issuing equipment is changed at first, the issued data is stored in the cache, the issuing equipment fails, the Agent informs an upper operator, the upper operator firstly modifies the issued state of the state table of the issuing equipment into a failure state, then reads the issued message from the cache, performs the issuing for 3 times at most, can inquire which configurations are not successfully issued if the 3 times of retry fails, manually triggers the issuing for multiple times, establishes the state table of the issuing equipment in the database, is used for indicating the state of the issuing equipment operated, and can quickly position which step of the issuing equipment is unsuccessful through looking up the table.
As a technical optimization scheme of the invention, if the issuing equipment is successful in S4, the following steps are carried out: s6, firstly, modifying a state table of the issuing equipment, changing the issuing state into a successful state, and additionally removing data with key values of requestId and requestId+num from redis.
By adopting the technical scheme, the successful state can be successfully issued and recorded.
The working principle of the invention is as follows: the method comprises the steps that a state table of the issuing equipment is established in a database and used for indicating the state of the issuing equipment in a certain operation, which step of the issuing equipment is unsuccessful can be rapidly located through table lookup, a retry mechanism and manual triggering are added, the retry mechanism is used for calling an Agent to issue when an upper operator issues the equipment, the state of the state table of the issuing equipment is changed firstly, issued data are stored in a cache and the issuing equipment fails, the Agent informs the upper operator, the upper operator firstly modifies the issuing state of the state table of the issuing equipment to be a failure state, then the issued message is read from the cache, the issuing is performed for 3 times at most, if the 3 times of retry fails, which configurations are not issued successfully, and the issuing is manually triggered for multiple times; if the issuing is successful, modifying the issuing state of the issuing equipment state table to be a successful state, and then clearing the issued message from the cache.
The above detailed description is merely illustrative of the preferred embodiments of the present invention and is not intended to limit the scope of the present invention. Various modifications, substitutions and improvements of the technical scheme of the present invention will be apparent to those skilled in the art from the description and drawings provided herein without departing from the spirit and scope of the invention. The scope of the invention is defined by the claims.
Claims (1)
1. The method for solving the failure of the elastic public network IP issuing equipment is characterized by comprising the following steps:
s1, creating a public network IP and a virtual machine, and binding the public network IP and the virtual machine;
s2, the Core layer triggers binding operation, records a state table of the issuing equipment and assembles data of the issuing equipment;
s3, calling an Agent by combining the issued message with the key of the redis cache as the request;
s4, judging whether the Agent issuing equipment is successful or not, and simultaneously returning the request;
s5, if the equipment fails in S4, firstly modifying a state table of the equipment, changing the issuing state into a failure state, then analyzing the request, obtaining the Id of the corresponding public network IP, the Id of the equipment and the operation attribute, recording the retry times by the Core layer when the equipment fails in issuing, taking the request+num as a key, storing the retry, automatically adding one when each retry is performed until the retry is performed three times, and if the retry is performed three times, inquiring the failed request from the retry, manually calling an interface, and performing equipment issuing;
s6, if the issuing equipment succeeds in S4, firstly modifying a state table of the issuing equipment, changing the issuing state into a successful state, and additionally removing data with key values of request and request+num from redis.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911317565.1A CN111030868B (en) | 2019-12-19 | 2019-12-19 | Method for solving failure of elastic public network IP issuing equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911317565.1A CN111030868B (en) | 2019-12-19 | 2019-12-19 | Method for solving failure of elastic public network IP issuing equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111030868A CN111030868A (en) | 2020-04-17 |
| CN111030868B true CN111030868B (en) | 2023-12-05 |
Family
ID=70210487
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911317565.1A Active CN111030868B (en) | 2019-12-19 | 2019-12-19 | Method for solving failure of elastic public network IP issuing equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111030868B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111628906B (en) * | 2020-05-11 | 2023-05-09 | 紫光云技术有限公司 | Method for carrying out flow statistics and monitoring on elastic public network IP |
| CN112671939B (en) * | 2020-08-17 | 2022-07-05 | 紫光云技术有限公司 | Method for distinguishing NAT deletion and NAT unbinding elastic public network IP |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103812704A (en) * | 2014-02-25 | 2014-05-21 | 国云科技股份有限公司 | Public network IP (Internet Protocol) dynamic management method for virtual machine |
| CN104717139A (en) * | 2013-12-12 | 2015-06-17 | 华为技术有限公司 | Data communication method, control equipment and nodes |
| CN108111325A (en) * | 2016-11-24 | 2018-06-01 | 北京金山云网络技术有限公司 | A kind of resource allocation methods and device |
| CN109688235A (en) * | 2019-03-18 | 2019-04-26 | 北京金山云网络技术有限公司 | Virtual network method for processing business, device and system, controller, storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107292618B (en) * | 2016-04-11 | 2020-04-28 | 阿里巴巴集团控股有限公司 | Method and device for processing ciphertext data encryption failure in database |
-
2019
- 2019-12-19 CN CN201911317565.1A patent/CN111030868B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104717139A (en) * | 2013-12-12 | 2015-06-17 | 华为技术有限公司 | Data communication method, control equipment and nodes |
| CN103812704A (en) * | 2014-02-25 | 2014-05-21 | 国云科技股份有限公司 | Public network IP (Internet Protocol) dynamic management method for virtual machine |
| CN108111325A (en) * | 2016-11-24 | 2018-06-01 | 北京金山云网络技术有限公司 | A kind of resource allocation methods and device |
| CN109688235A (en) * | 2019-03-18 | 2019-04-26 | 北京金山云网络技术有限公司 | Virtual network method for processing business, device and system, controller, storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111030868A (en) | 2020-04-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111030868B (en) | Method for solving failure of elastic public network IP issuing equipment | |
| US8780925B2 (en) | Mobile use of a PBX system | |
| JP6852068B2 (en) | Equipment, systems and methods for retrieving, processing and updating global information | |
| WO2019179019A1 (en) | Automated testing method and apparatus, and computer device and storage medium | |
| CN108289060A (en) | A kind of data processing method and device based on RPC service | |
| CN109039743B (en) | Centralized management method of distributed storage ceph cluster network | |
| CN106933548A (en) | Global information is obtained, processes and updated, methods, devices and systems | |
| WO2018214928A1 (en) | Method and apparatus for locating resolution fault, computer readable storage medium thereof, and computer device | |
| CN107453922A (en) | Infrastructure service collocation method, client and server | |
| CN103875268B (en) | HSS fault recoveries for non-3 GPP access | |
| JP2014219936A (en) | Migration support device, migration support method and program | |
| CN107911496A (en) | A kind of VPN service terminal acts on behalf of the method and device of DNS | |
| EP2149249A1 (en) | Fully redundant call recording | |
| CN113114857B (en) | Outbound dynamic display method and device and electronic equipment | |
| CN103023726B (en) | Method and system for testing maximum mainframe connection number of network storage device | |
| CN104378449A (en) | Virtual IP realization method | |
| CN103843450A (en) | PMIPV6 MAG restoration | |
| CN101789855B (en) | Server and double-link backup method thereof | |
| CN105847070A (en) | Switch fault processing method and device | |
| EP3306471B1 (en) | Automatic server cluster discovery | |
| CN112671723B (en) | Call control system, method and computer readable medium | |
| JP6408721B2 (en) | Domain name system DNS resolution processing method and apparatus, program, and recording medium | |
| US7310614B2 (en) | System and method for operation and management of storage apparatus | |
| JP7006533B2 (en) | Media gateway device and media path setting method | |
| WO2021011682A1 (en) | Systems and methods for managing software telephones |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |