CN111030868A - 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
- CN111030868A CN111030868A CN201911317565.1A CN201911317565A CN111030868A CN 111030868 A CN111030868 A CN 111030868A CN 201911317565 A CN201911317565 A CN 201911317565A CN 111030868 A CN111030868 A CN 111030868A
- Authority
- CN
- China
- Prior art keywords
- issuing
- equipment
- public network
- state
- steps
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 21
- 239000012792 core layer Substances 0.000 claims abstract description 7
- 238000011084 recovery Methods 0.000 abstract description 2
- 239000010410 layer Substances 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 3
- 238000005457 optimization Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002457 bidirectional 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
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/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 discloses a method for solving the failure of elastic public network IP issuing equipment, which relates to the technical field of elastic public network IP application, and comprises the following steps of S1, establishing a public network IP and a virtual machine, and binding the public network IP and the virtual machine; s2, the Core layer triggers the binding operation, records the state table of the issuing equipment and assembles the data of the issuing equipment; s3, setting the key of the redis cache as requested, and calling the Agent by combining the issued message; s4, judging whether the Agent issues the device successfully, returning the requested, improving the two independent processes of the storage of the upper database and the issuing device into a scheme of issuing the device for multiple times which can actively trigger the retry for configuration after the issuing device fails, and adding a callback mechanism between the upper service and the Agent, so that the problem that the device data is inconsistent with the upper database due to the failure of the issuing device can be effectively solved, the problem of which specific step is taken out when the issuing device is conveniently positioned, and manual field recovery and 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 the failure of elastic public network IP issuing equipment.
Background
The elastic public network IP is used as a public network IP address resource independently purchased and held, and can be bound to an ECS (electronic communications system) example of a proprietary network type, a private network SLB (subscriber line bus) example of the proprietary network type, an auxiliary elastic network card of the proprietary network type, an NAT (network address translation) gateway and a high-availability virtual IP. When the elastic public network IP binds or unbinds the virtual machine, the NAT rule is issued on the firewall, and the bandwidth information is issued on the exit route, wherein the issued NAT rule is to perform bidirectional mapping on the public network IP and the private network IP on the virtual machine network card, so that the virtual machine can be communicated with the public network, and the issued bandwidth information is to limit the flow speed on the exit route, therefore, one operation relates to issuing configuration to a plurality of network devices, and the whole operation flow can be completed only if the configuration is successfully issued. For the operation of the prior elastic public network IP, the storage and the issuing configuration are two processes, and the configuration of the database and the network equipment is inconsistent due to the uncontrollable property of issuing equipment, so that the resource is remained, and the subsequent operation of the resource is greatly influenced. Therefore, it is necessary to provide a solution to failure of resilient public network IP delivery equipment in view of 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 issuing equipment effectively solves the problem that the equipment data is inconsistent with an upper database due to the failure of the equipment issuing, can conveniently position the specific step of the issuing equipment, and can manually recover the site and issue the issuing equipment again.
In order to achieve the above object, the method for solving the failure of the elastic public network IP issuing equipment of the invention comprises 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 the binding operation, records the state table of the issuing equipment and assembles the data of the issuing equipment;
s3, setting the key of the redis cache as requested, and calling the Agent by combining the issued message;
and S4, judging whether the Agent issuing equipment succeeds or not, and returning the requested information.
Preferably, in S4, if the issued device fails, the following steps are performed:
s5, firstly, the state table of the issuing equipment is modified, the issuing state is changed into a failure state, then the requested is analyzed, and the corresponding Id of the public network IP, the operated equipment Id and the operation attribute are obtained.
Preferably, in S4, if the issuing device is successful, the following steps are performed:
s6, firstly, the state table of the issuing equipment is modified, the issuing state is changed to a success state, and in addition, data with key values of requestId and requestId + num are removed from the redis.
Preferably, in S5, when the delivery fails, the Core layer records the number of retries, stores the retries in redis with requestId + num as a key, and automatically increments the number by one for each retry until the retry is three times.
Preferably, if all three retries end in failure, the failed requestId can be queried from the redis, and the interface can be manually called to issue the device.
The invention has the following beneficial effects:
the storage of the upper layer database and the two independent processes of the issuing equipment are improved into a scheme of issuing the equipment for multiple times, wherein the issuing equipment can actively trigger retry for configuration after the issuing equipment fails, and a callback mechanism is added between the upper layer service and the Agent, so that the problem that the equipment data is inconsistent with the upper layer database due to the issuing failure of the equipment can be effectively solved, meanwhile, the problem of specific step of the issuing equipment can be conveniently positioned, and manual field recovery and re-issuing can be realized.
Drawings
The present invention will be further described and illustrated with reference to the following drawings.
Fig. 1 is a flowchart of a method for solving 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 method for solving the failure of the flexible public network IP issuing 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 the binding operation, records the state table of the issuing equipment and assembles the data of the issuing equipment;
s3, key of redis buffer is requested, Agent is called by combining with the sent message, Agent technology receives the register of information distributor about information main points and the register of information inquirer about information demand main points, the Agent informs user actively according to the information, or informs information provider actively who needs the information;
and S4, judging whether the Agent issuing equipment succeeds or not, and returning the requested information.
As a technical optimization scheme of the present invention, if the device issuing fails in S4, the following steps are performed: s5, firstly, modifying the state table of the issuing equipment, changing the issuing state into a failure state, then analyzing the requestId, obtaining the corresponding Id of the public network IP, the operated equipment Id and the operation attribute, recording the retry times by the Core layer, storing the retry times into the redis by taking the requestId + num as a key, automatically adding one in each retry until retrying three times, if the retrying three times all end in failure, 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 layer operator, the upper layer operator can modify the issuing state of the state table of the issuing equipment into the failure state at first, then the issued message is read from the cache, the retry is performed for 3 times at most, if the 3 times of retry fail, which configurations are not successfully issued can be inquired, the issuing equipment is manually triggered for multiple times, the state table of the issuing equipment is established in the database and used for indicating the state of the issuing equipment in a certain operation, and the step of the issuing equipment which is not successful can be quickly positioned through table lookup.
As a technical optimization scheme of the present invention, if the device is successfully delivered in S4, the following steps are performed: s6, firstly, the state table of the issuing equipment is modified, the issuing state is changed to a success state, and in addition, data with key values of requestId and requestId + num are removed from the redis.
By adopting the technical scheme, the method and the device can smoothly issue and record the success state.
The working principle of the invention is as follows: establishing a state table of issuing equipment in a database, wherein the state table is used for representing the state of the issuing equipment in a certain operation, rapidly positioning which step of the issuing equipment is unsuccessful through table lookup, adding a retry mechanism and manual triggering, when the retry mechanism is that an upper operator issues the equipment, calling an Agent to issue, firstly changing the state of the state table of the issuing equipment and storing issued data into a cache, 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 into a failure state, then reads an issued message from the cache, issues the issued message for 3 times at most after retry, if the 3 times of retry fails, inquires which configurations are not successfully issued, and manually triggers for multiple times of issuing; if the transmission is successful, modifying the transmission state of the transmission equipment state table to be a successful state, and then removing the transmitted message from the cache.
The above detailed description merely describes preferred embodiments of the present invention and does not limit the scope of the invention. Without departing from the spirit and scope of the present invention, it should be understood that various changes, substitutions and alterations can be made herein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents. The scope of the invention is defined by the claims.
Claims (5)
1. A method for solving the failure of 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 the binding operation, records the state table of the issuing equipment and assembles the data of the issuing equipment;
s3, setting the key of the redis cache as requested, and calling the Agent by combining the issued message;
and S4, judging whether the Agent issuing equipment succeeds or not, and returning the requested information.
2. The method according to claim 1, wherein the method comprises the following steps: if the equipment issuing fails in S4, the following steps are performed:
s5, firstly, the state table of the issuing equipment is modified, the issuing state is changed into a failure state, then the requested is analyzed, and the corresponding Id of the public network IP, the operated equipment Id and the operation attribute are obtained.
3. The method according to claim 1, wherein the method comprises the following steps: if the device issuing is successful in S4, the following steps are performed:
s6, firstly, the state table of the issuing equipment is modified, the issuing state is changed to a success state, and in addition, data with key values of requestId and requestId + num are removed from the redis.
4. The method according to claim 2, wherein the method comprises the following steps: in S5, when the delivery fails, the Core layer records the number of retries, stores the retries in redis with requestId + num as a key, and automatically increments by one for each retry until the retry is three times.
5. The method according to claim 4, wherein the method comprises the following steps: if all three retries end in failure, the failed requestId can be inquired from the redis, and the interface can be manually called to issue the equipment.
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 true CN111030868A (en) | 2020-04-17 |
| CN111030868B 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) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111628906A (en) * | 2020-05-11 | 2020-09-04 | 紫光云技术有限公司 | Method for carrying out flow statistics and monitoring on IP of bullet-supplying public network |
| CN112671939A (en) * | 2020-08-17 | 2021-04-16 | 紫光云技术有限公司 | Method for distinguishing NAT deletion and NAT unbinding elastic public network IP |
Citations (5)
| 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 |
| US20190042367A1 (en) * | 2016-04-11 | 2019-02-07 | Alibaba Group Holding Limited | Method and apparatus for processing failure of cipher change of ciphertext in database |
| CN109688235A (en) * | 2019-03-18 | 2019-04-26 | 北京金山云网络技术有限公司 | Virtual network method for processing business, device and system, controller, storage medium |
-
2019
- 2019-12-19 CN CN201911317565.1A patent/CN111030868B/en active Active
Patent Citations (5)
| 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 |
| US20190042367A1 (en) * | 2016-04-11 | 2019-02-07 | Alibaba Group Holding Limited | Method and apparatus for processing failure of cipher change of ciphertext in database |
| 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 |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111628906A (en) * | 2020-05-11 | 2020-09-04 | 紫光云技术有限公司 | Method for carrying out flow statistics and monitoring on IP of bullet-supplying public network |
| CN111628906B (en) * | 2020-05-11 | 2023-05-09 | 紫光云技术有限公司 | Method for carrying out flow statistics and monitoring on elastic public network IP |
| CN112671939A (en) * | 2020-08-17 | 2021-04-16 | 紫光云技术有限公司 | Method for distinguishing NAT deletion and NAT unbinding elastic public network IP |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111030868B (en) | 2023-12-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7249192B1 (en) | Protocol for insuring exactly once semantics of transactions across an unordered, unreliable network | |
| TWI242958B (en) | Method for controlling a media message upload through a wireless communication network | |
| CN101635643B (en) | Method and system for changing terminal service and network management platform | |
| US7912858B2 (en) | Data synchronization method | |
| CN111030868A (en) | Method for solving failure of elastic public network IP issuing equipment | |
| CN109582335B (en) | Method, device and equipment for on-line upgrading of non-interrupt storage cluster nodes | |
| US6061807A (en) | Methods systems and computer products for error recovery of endpoint nodes | |
| CN108289060A (en) | A kind of data processing method and device based on RPC service | |
| WO2019179019A1 (en) | Automated testing method and apparatus, and computer device and storage medium | |
| CN107453922B (en) | Basic service configuration method, client and server | |
| CN106933548A (en) | Global information is obtained, processes and updated, methods, devices and systems | |
| CN111800354A (en) | Message processing method and device, message processing equipment and storage medium | |
| CN108495306A (en) | HSS fault recoveries for non-3 GPP access | |
| CN107911496A (en) | A kind of VPN service terminal acts on behalf of the method and device of DNS | |
| CN100465913C (en) | Configuration of recovery device and method thereof | |
| CN100499496C (en) | A method and device for realization of the configuration transaction and commissioning mechanism | |
| CN109241110A (en) | Order management method and system, electronic equipment, storage medium | |
| US7310614B2 (en) | System and method for operation and management of storage apparatus | |
| CN111049938B (en) | Message notification method and device, electronic equipment and readable storage medium | |
| JP7006533B2 (en) | Media gateway device and media path setting method | |
| WO2021011682A1 (en) | Systems and methods for managing software telephones | |
| EP2485510A1 (en) | System and method for implementing concentrated access of business operations support system | |
| CN116390272B (en) | Method, device and electronic equipment for realizing UPF control by using 5G core network PFCP-GW | |
| CN116760510B (en) | Message sending method, message receiving method, device and equipment | |
| CN112073466B (en) | Terminal distributed instruction issuing method |
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 |