CN101227333A - Disaster tolerance network managing system and login method of network managing subscriber end - Google Patents
Disaster tolerance network managing system and login method of network managing subscriber end Download PDFInfo
- Publication number
- CN101227333A CN101227333A CNA2008100575018A CN200810057501A CN101227333A CN 101227333 A CN101227333 A CN 101227333A CN A2008100575018 A CNA2008100575018 A CN A2008100575018A CN 200810057501 A CN200810057501 A CN 200810057501A CN 101227333 A CN101227333 A CN 101227333A
- Authority
- CN
- China
- Prior art keywords
- server
- node server
- disaster tolerance
- service
- host node
- 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
Images
Abstract
The invention discloses a method for landing on network management client ends, which comprises following steps: renewing domain name analyzing data by a dynamic domain name server, renewing the domain name analyzing data into an IP address of a host node or disaster recovery node server which provides services at present, filling in a service name which is used to land on the network management client ends by the network management client ends, sending an analyzing request of the service name to the dynamic domain name server, analyzing the service name by the dynamic domain name server, taking the IP address of the host node or disaster recovery node server which provides the services at present as an analyzing result to the network management client ends, and using the IP address of the host node or disaster recovery node server, which is obtained, to land on a host node server or a disaster recovery node server. The invention also correspondingly discloses a disaster recovery network management system, and thereby the invention not only increases the friendliness of user operations in the network management system and simultaneously lowers the complexity of the network management system.
Description
Technical field
The present invention relates to the realization technology in the network management system networking plan, relate in particular to the login method of a kind of disaster tolerance network management system and NM client thereof.
Background technology
Along with developing rapidly of the communication technology, the Communications Market scale further enlarges, and the equipment complexity of operation improves constantly on the net at present, and increasing crucial application and service is based upon on the data network.For telecom operation department, guarantee that network is normal, high-efficient operation is most important.Telecom operators must effectively manage and plan the network system of supporting service, to satisfy ever-increasing user's request to greatest extent, guarantee that network moves normally and efficiently.For monitor network ruuning situation better, improve the efficient of network operation, cut operating costs, improve service quality, operator has proposed strict demand to the reliability of network management system, network management system is as the core application system of monitoring and supervising the network, the operation that requirement can be long-term, stable.
After the original Single-Server operation of network management system can not be satisfied the demand of long-term, stable operation, the reliability scheme that proposes at network management system mainly contains two kinds: a kind of local high-availability arrangement, by hardware and software redundant configuration completely is provided in this locality, and under the control of cluster module (software), provide the service of local high availability webmaster; Another kind is long-range long-distance disaster scheme, and the fully redundance configuration of hardware and software is provided in different physics region, and realizes the webmaster service of long-distance disaster under cluster module control.
Compare with long-range long-distance disaster scheme, local high-availability arrangement can only solve the situation of scheduled maintenance, local part hardware damage, can take over the webmaster service this moment by redundant software and hardware, have a power failure but can not solve the webmaster machine room, or even the problem of the webmaster end of service that generation brought of region disaster.So all adopt the reliability scheme of long-range long-distance disaster scheme as a rule, but so brought new problem again as network management system.
Because in local high-availability arrangement, network management system server redundancy hardware is in the same subnet, can use the mode of floating IP address to land use for NM client, when the webmaster service was switched between different server, NM client used same IP address to land like this.And in long-range long-distance disaster scheme, because may be at a distance of hundreds and thousands of kilometers between the different physics region, if use fiber plant to draw special line that subnet is provided, lower deployment cost is too high.So network management system Disaster Recovery Service redundant hardware unlikely is in the middle of the same subnet, if use 2 layers of VPN (Virtual Private Network, VPN (virtual private network)) mode provides floating IP address, then need some specification requirements be proposed for bearer network, improved the complexity of networking like this, and might bring some other network problem, the reliability that strengthened the difficulty that network management system is disposed, has reduced network management system.
In the long-range long-distance disaster scheme of network management system; if the webmaster service can't obtain Floating IP address; then when the host node server externally provides service; NM client need use the IP address A of host node server to land; when the host node server is shut down because of scheduled overhaul or accidental disaster; when the disaster tolerance node server externally provides service; NM client need use the IP address B of disaster tolerance node server to land, and this NM client when landing the variation of IP address need give notify party to the NM client operating personnel by the network management system attendant and can carry out.Because when NM client can't land by the IP address A of host node server, the NM client operating personnel can't distinguish and landing failure is because network interrupts causing between NM client and the server, and still the webmaster service is being led, switching taken place between the disaster tolerance node server and cause.
In addition, when the webmaster service also inserts Upper NM Station system or OSS (OperationSupport System as subordinate's webmaster, OSS) system, and when Upper NM Station connects network management system as the Socket telecommunication customer end, use CORBA (Common Object Request BrokerArchitecture as higher level's webmaster, common object request broker system), FTP (File Transfer Protocol, file transfer protocol (FTP)) etc. when agreement connects network management system, the webmaster service is being led, switching between the disaster tolerance node server also needs Upper NM Station, OSS carries out switching notice, and this has also increased the development difficulty and the complexity of network management system.
In summary, existing network management system networking plan obviously exists inconvenience and defective, so be necessary to be improved on reality is used.
Summary of the invention
At above-mentioned defective, the object of the present invention is to provide the login method of a kind of disaster tolerance network management system and NM client thereof, it has not only strengthened the network management system user and has operated friendly, has reduced the network management system complexity simultaneously.
To achieve these goals, the invention provides a kind of login method of NM client, be applied to comprise the disaster tolerance network management system of NM client and NM server end, this NM server end includes DDNS server, host node server and disaster tolerance node server again, and described method comprises that step has:
A, described DDNS server update domain name mapping data are the current IP address that the host node server or the disaster tolerance node server of service are provided with this domain name mapping Data Update;
B, NM client are filled in the service name that is used to land the webmaster server end, and send the analysis request of service name to described DDNS server;
C, described DDNS server are resolved this service name, and the current host node server of service or the IP address of disaster tolerance node server of providing sent to NM client as analysis result;
After D, NM client obtained this analysis result, host node server or disaster tolerance node server were landed in the host node server that use is received or the IP address of disaster tolerance node server.
According to login method of the present invention, described NM server end comprises that also one is used to switch the cluster module that described host node server or disaster tolerance node server provide service,
In the described steps A, current host node server that service is provided or disaster tolerance node server are under the control of described cluster module, upgrade the domain name mapping data to described DDNS server requests, so that the domain name mapping Data Update is the current IP address that the host node server or the disaster tolerance node server of service are provided.
According to login method of the present invention, described steps A also comprises:
After A1, host node server or disaster tolerance node server start, upgrade the domain name mapping data to described DDNS server requests;
After A2, described DDNS server are received this update request, the domain name resolution data is updated to the current IP address that the host node server or the disaster tolerance node server of service are provided;
A3, described cluster module detect the host node server or whether the disaster tolerance node server takes place unusually, if unusual, then will provide the server of service to switch to disaster tolerance node server or host node server;
Behind A4, described disaster tolerance node server or the host node startup of server, upgrade the domain name mapping data to described DDNS server requests;
After A5, described DDNS server are received this update request, the domain name resolution data is updated to the IP address of disaster tolerance node server or host node server.
According to login method of the present invention, comprise also between described steps A and the B that described NM client is configured to the dns server address in its operating system the IP address of described DDNS server.
According to login method of the present invention, comprise also between described steps A and the B that the described NM client dns server address that it is embedded is configured to the IP address of described DDNS server.
According to login method of the present invention, NM client sends the analysis request of service name among the described step B to described DDNS server by DNS Protocol.
According to login method of the present invention, described host node server and disaster tolerance node server be long-distance disaster or local disaster tolerance each other.
According to login method of the present invention, comprise a plurality of host node servers and/or disaster tolerance node server in the described disaster tolerance network management system.
The present invention also provides a kind of disaster tolerance network management system, comprises NM client, NM server end and DDNS server end, and this NM server end includes DDNS server, host node server and disaster tolerance node server again;
Described NM client is used to fill in the service name that is used to land the webmaster server end, and sends the analysis request of service name to described DDNS server; And after obtaining the analysis result of this service name, host node server or disaster tolerance node server are landed in the host node server that use is received or the IP address of disaster tolerance node server;
Described NM server end, its DDNS server is used to upgrade the domain name mapping data, this domain name mapping Data Update is the current IP address that the host node server or the disaster tolerance node server of service are provided, and this service name that NM client is sent resolved, the current host node server of service or the IP address of disaster tolerance node server of providing sent to described NM client as analysis result.
According to disaster tolerance network management system of the present invention, described NM server end also comprises a cluster module, this cluster module is used to switch described host node server or the disaster tolerance node server provides service, and the current host node server of service or the disaster tolerance node server of providing is provided upgraded the domain name mapping data to described DDNS server requests, so that this domain name mapping Data Update is the current IP address that the host node server or the disaster tolerance node server of service are provided.
The present invention introduces the parsing that the DDNS server carries out service name, and DDNS server domain name resolution data can be automatically updated into the current IP address that the server of service is provided after host node server or the startup of disaster tolerance node server, when NM client to the NM server end send land request before, by the DDNS server service name is resolved, and the current host node server of service or the IP address of disaster tolerance node server of providing sent to NM client as analysis result, NM client uses the IP address of being received to land host node server or disaster tolerance node server.Whereby, the present invention introduces service name as the unique identification that lands the webmaster service, guaranteed on the one hand when service is switched between the server under the network management system Disaster Tolerant Scheme deployment scenario transparent for NM client, operated friendly thereby strengthened the network management system user; On the other hand, when the webmaster service inserts Upper NM Station as the subordinate webmaster, active and standby switching does not need Upper NM Station is carried out switching notice, thereby has reduced the network management system complexity.In addition, the present invention has used the DNS Protocol of standard, makes NM client can directly use DNS client functionality embedded or that operating system provides, thereby has improved the flexibility of system design.
Description of drawings
Fig. 1 is the structural representation of network management system provided by the invention;
Fig. 2 is the login method flow chart of NM client in the network management system of the present invention;
Fig. 3 is the method flow diagram that DDNS server of the present invention carries out the domain name Data Update.
Embodiment
In order to make purpose of the present invention, technical scheme and advantage clearer,, the present invention is further elaborated below in conjunction with drawings and Examples.Should be appreciated that specific embodiment described herein only in order to explanation the present invention, and be not used in qualification the present invention.
Fig. 1 shows the structure of disaster tolerance network management system provided by the invention, this system comprises NM client 10 and NM server end 20, this NM server end 20 comprises host node server 21, disaster tolerance node server 22 and DDNS server 23 again, wherein:
NM client 10, it is deployed with NM client and uses, and the webmaster man-machine interface is provided.NM client 10 of the present invention is used to fill in the service name that is used to land webmaster server end 20, and sends the analysis request of service name to described DDNS server 23; And after obtaining the analysis result of this service name, host node server 21 or disaster tolerance node server 22 are landed in the host node server 21 that use is received or the IP address of disaster tolerance node server 22.Preferably, described NM client 10 is configured to the dns server address in its operating system the IP address of DDNS server 23; Perhaps, described NM client 10 dns server address that it is embedded is configured to the IP address of DDNS server 23.Like this, NM client 10 just can send the analysis request of service name by DNS Protocol to DDNS server 23.Because the present invention has used the DNS Protocol of standard, the DNS client functionality that NM client 10 can use embedded DNS client functionality or directly use operating system to provide is provided, thereby improved the flexibility of system design.
Described NM server end 20 is made of redundant software and hardware, its DDNS server 23 also is a kind of DNS (Domain Name Server, name server) server, be mainly used in the analysis request of the service name that receives NM client 10, so that the current IP address information of the server of service that provides is returned to NM client 10 in response.
DDNS server 23 among the present invention is used to upgrade the domain name mapping data, this domain name mapping Data Update can be the current IP address that the host node server 21 of service is provided, for example with the IP address A of host node server 21 as the domain name mapping data; Perhaps so that this domain name mapping Data Update is the current IP address that the disaster tolerance node server 22 of service is provided, for example with the IP address B of disaster tolerance node server 22 as the domain name mapping data.And this service name that 23 pairs of NM clients 10 of DDNS server are sent is resolved, and the current host node server 21 of service or the IP address of disaster tolerance node server 22 of providing sent to NM client 10 as analysis result.
Preferably, described NM server end 20 also comprises at least one cluster module 24, normally a kind of Control Software, and being used to switch described host node server 21 or disaster tolerance node server 22 outwards provides the webmaster service.Particularly, described cluster module 24 provides functions such as heartbeat detection between network management system master, the disaster tolerance node server 22 and 22, duplicating remote data, and by the server hardware availability being detected and the service application state detects to finish the switching of webmaster service processes between webmaster master, disaster tolerance node server 21 and 22.
Among the present invention, the current host node server 21 of service or the disaster tolerance node server 22 of providing of described cluster module 24 controls upgrades the domain name mapping data to 23 requests of DDNS server, so that this domain name mapping Data Update is the current IP address that the host node server 21 or the disaster tolerance node server 22 of service are provided, promptly the domain name mapping data in the DDNS server 23 correspond to the IP address (externally provide webmaster service by host node server 21 this moment) of host node server 21 or the IP address (externally provide webmaster service by disaster tolerance node server 22 this moment) of disaster tolerance node server 22.
The present invention is particularly useful for network management system long-distance disaster scheme, i.e. host node server 21 and disaster tolerance node server 22 long-distance disaster each other.Certainly, the present invention is also applicable to local high-availability arrangement, i.e. the local each other disaster tolerance of host node server 21 and disaster tolerance node server 22.In addition, can comprise a plurality of host node servers 21 in the described disaster tolerance network management system or/and a plurality of disaster tolerance node server 22, promptly belong to the N+N Disaster Tolerant Scheme, described some disaster tolerance node servers 22 can be in local and remote, and the quantity of principal point server 21 and disaster tolerance node server 22 can be a plurality of arbitrarily.
Whereby, the present invention introduces DDNS server 23 and carries out the parsing of service name in network management system, makes NM client 10 can use service name to land.NM client 10 first request dynamic name servers 23 carry out dns resolution and get the externally actual up till now server ip address that the webmaster service is provided, and NM client 10 initiates to land to the actual server of service that provides again then.Guaranteed on the one hand when service is switched between the server under the network management system Disaster Tolerant Scheme deployment scenario to have strengthened transparent for NM client 10 the network management system user and to have operated friendly; Reduce the development of service switching notice on the other hand, and reduced the network management system complexity.
Fig. 2 shows the login method flow process of NM client of the present invention, and it is realized by disaster tolerance network management system shown in Figure 1, comprises that specifically step is as follows:
Step S201, DDNS server 23 upgrades the domain name mapping data, and this domain name mapping Data Update is the current IP address that the host node server 21 or the disaster tolerance node server 22 of service are provided.This step preferably, current host node server 21 that service is provided or disaster tolerance node server 22 are under the control of described cluster module 24, upgrade the domain name mapping data to described DDNS server 23 requests, so that this domain name mapping Data Update is the current IP address that the host node server 21 or the disaster tolerance node server 22 of service are provided.
Step S202, NM client 10 is filled in the service name that is used to land webmaster server end 20, and sends the analysis request of service name to described DDNS server 23.Can comprise that also described NM client 10 is configured to the dns server address in its operating system the IP address of DDNS server 23 before this step; Perhaps, described NM client 10 dns server address that it is embedded is configured to the IP address of described DDNS server 23.Like this, NM client 10 just can be filled in service name as the unique sign that lands the webmaster service, and sends the analysis request of service name to DDNS server 23 by DNS Protocol.
Step S203,23 pairs of these service names of DDNS server are resolved, the current host node server 21 of service or the IP address of disaster tolerance node server 22 of providing sent to NM client 10 as analysis result, and just DDNS server 23 sends to NM client 10 after the actual IP address that the server of webmaster service is provided is packaged into bag.
Step S204, after NM client 10 obtains this analysis result, enter normal landing program, host node server 21 or disaster tolerance node server 22 are landed in the host node server 21 that i.e. use is received or the IP address of disaster tolerance node server 22, to host node server 21 that service is provided or the 22 request webmaster service registrys of disaster tolerance node server, and then realize network operation and management.
Fig. 3 shows the method flow that DDNS server of the present invention carries out the domain name Data Update, and it is realized by disaster tolerance network management system shown in Figure 1, comprises that specifically step is as follows:
Step S301 after host node server 21 or disaster tolerance node server 22 start, upgrades the domain name mapping data to 23 requests of DDNS server.What generally speaking, at first start is host node server 21.
Step S302 after DDNS server 23 is received this update request, is updated to the current IP address that the host node server 21 or the disaster tolerance node server 22 of service are provided with the domain name resolution data, and the response that returns success.At this moment, DDNS server 23 can respond the analysis request of the service name that NM client 10 initiates, and the IP address of returning host node server 21 or disaster tolerance node server 22 is as analysis result.
Step S303, cluster module 24 detects host node server 21 or whether disaster tolerance node server 22 takes place unusually, comprise that all kinds of software and hardwares are unusual, for example inside the plan maintenance or other accidental disasters can make the current host node server 21 of service or the disaster tolerance node server 22 of providing can't continue to provide service, in case taking place then will provide the server of service to switch to disaster tolerance node server 22 or host node server 21 unusually.
Step S304 after disaster tolerance node server 22 or host node server 21 start, upgrades the domain name mapping data to described DDNS server 23 requests.
Step S305 after DDNS server 23 is received this update request, is updated to the domain name resolution data IP address of disaster tolerance node server 22 or host node server 21.At this moment, DDNS server 23 can respond the analysis request of the service name that NM client 10 initiates, and the IP address of returning disaster tolerance node server 22 or host node server 21 is as analysis result.
In summary, the present invention introduces the parsing that the DDNS server carries out service name, and DDNS server domain name resolution data can be automatically updated into the current IP address that the server of service is provided after host node server or the startup of disaster tolerance node server, when NM client to the NM server end send land request before, by the DDNS server service name is resolved, and the current host node server of service or the IP address of disaster tolerance node server of providing sent to NM client as analysis result, NM client uses the IP address of being received to land host node server or disaster tolerance node server.Whereby, the present invention introduces service name as the unique identification that lands the webmaster service, guaranteed on the one hand when service is switched between the server under the network management system Disaster Tolerant Scheme deployment scenario transparent for NM client, operated friendly thereby strengthened the network management system user; On the other hand, when the webmaster service inserts Upper NM Station as the subordinate webmaster, active and standby switching does not need Upper NM Station is carried out switching notice, thereby has reduced the network management system complexity.In addition, the present invention has used the DNS Protocol of standard, makes NM client can directly use DNS client functionality embedded or that operating system provides, thereby has improved the flexibility of system design.
Certainly; the present invention also can have other various embodiments; under the situation that does not deviate from spirit of the present invention and essence thereof; those of ordinary skill in the art work as can make various corresponding changes and distortion according to the present invention, but these corresponding changes and distortion all should belong to the protection range of the appended claim of the present invention.
Claims (10)
1. the login method of a NM client, it is characterized in that, be applied to comprise the disaster tolerance network management system of NM client and NM server end, this NM server end includes DDNS server, host node server and disaster tolerance node server again, and described method comprises that step has:
A, described DDNS server update domain name mapping data are the current IP address that the host node server or the disaster tolerance node server of service are provided with this domain name mapping Data Update;
B, NM client are filled in the service name that is used to land the webmaster server end, and send the analysis request of service name to described DDNS server;
C, described DDNS server are resolved this service name, and the current host node server of service or the IP address of disaster tolerance node server of providing sent to NM client as analysis result;
After D, NM client obtained this analysis result, host node server or disaster tolerance node server were landed in the host node server that use is received or the IP address of disaster tolerance node server.
2. login method according to claim 1 is characterized in that, described NM server end comprises that also one is used to switch the cluster module that described host node server or disaster tolerance node server provide service,
In the described steps A, current host node server that service is provided or disaster tolerance node server are under the control of described cluster module, upgrade the domain name mapping data to described DDNS server requests, so that this domain name mapping Data Update is the current IP address that the host node server or the disaster tolerance node server of service are provided.
3. login method according to claim 2 is characterized in that, described steps A also comprises:
After A1, host node server or disaster tolerance node server start, upgrade the domain name mapping data to described DDNS server requests;
After A2, described DDNS server are received this update request, the domain name resolution data is updated to the current IP address that the host node server or the disaster tolerance node server of service are provided;
A3, described cluster module detect the host node server or whether the disaster tolerance node server takes place unusually, if unusual, then will provide the server of service to switch to disaster tolerance node server or host node server;
Behind A4, described disaster tolerance node server or the host node startup of server, upgrade the domain name mapping data to described DDNS server requests;
After A5, described DDNS server are received this update request, the domain name resolution data is updated to the IP address of disaster tolerance node server or host node server.
4. login method according to claim 2 is characterized in that, also comprises between described steps A and the B, and described NM client is configured to the dns server address in its operating system the IP address of described DDNS server.
5. login method according to claim 2 is characterized in that, also comprises between described steps A and the B, and the described NM client dns server address that it is embedded is configured to the IP address of described DDNS server.
6. login method according to claim 2 is characterized in that, NM client sends the analysis request of service name among the described step B to described DDNS server by DNS Protocol.
7. login method according to claim 1 is characterized in that, described host node server and disaster tolerance node server be long-distance disaster or local disaster tolerance each other.
8. login method according to claim 1 is characterized in that, comprises a plurality of host node servers and/or disaster tolerance node server in the described disaster tolerance network management system.
9. the disaster tolerance network management system of a realization such as each method of claim 1～8, it is characterized in that, comprise NM client, NM server end and DDNS server end, this NM server end includes DDNS server, host node server and disaster tolerance node server again;
Described NM client is used to fill in the service name that is used to land the webmaster server end, and sends the analysis request of service name to described DDNS server; And after obtaining the analysis result of this service name, host node server or disaster tolerance node server are landed in the host node server that use is received or the IP address of disaster tolerance node server;
Described NM server end, its DDNS server is used to upgrade the domain name mapping data, this domain name mapping Data Update is the current IP address that the host node server or the disaster tolerance node server of service are provided, and this service name that NM client is sent resolved, the current host node server of service or the IP address of disaster tolerance node server of providing sent to described NM client as analysis result.
10. disaster tolerance network management system according to claim 9, it is characterized in that, described NM server end also comprises a cluster module, this cluster module is used to switch described host node server or the disaster tolerance node server provides service, and the current host node server of service or the disaster tolerance node server of providing is provided upgraded the domain name mapping data to described DDNS server requests, so that this domain name mapping Data Update is the current IP address that the host node server or the disaster tolerance node server of service are provided.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100575018A CN101227333B (en) | 2008-02-02 | 2008-02-02 | Disaster tolerance network managing system and login method of network managing subscriber end |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100575018A CN101227333B (en) | 2008-02-02 | 2008-02-02 | Disaster tolerance network managing system and login method of network managing subscriber end |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101227333A true CN101227333A (en) | 2008-07-23 |
| CN101227333B CN101227333B (en) | 2010-12-29 |
Family
ID=39859100
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008100575018A Active CN101227333B (en) | 2008-02-02 | 2008-02-02 | Disaster tolerance network managing system and login method of network managing subscriber end |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101227333B (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010149117A1 (en) * | 2009-11-04 | 2010-12-29 | 中兴通讯股份有限公司 | Method and apparatus for implementing service system protection |
| CN102215271A (en) * | 2010-04-07 | 2011-10-12 | 上海交通大学医学院附属瑞金医院 | Addressing processing method and device for FTP (file transfer protocol)-based disaster recovery server |
| CN104836689A (en) * | 2015-05-21 | 2015-08-12 | 武汉新芯集成电路制造有限公司 | Server fault transfer method and system |
| CN105024855A (en) * | 2015-07-13 | 2015-11-04 | 浪潮(北京)电子信息产业有限公司 | Distributed cluster management system and method |
| CN106878254A (en) * | 2016-11-16 | 2017-06-20 | 国家数字交换系统工程技术研究中心 | Improve the method and device of DNS securities of system |
| CN108900572A (en) * | 2018-05-31 | 2018-11-27 | 康键信息技术（深圳）有限公司 | Primary database domain name method for handover control, computer equipment and storage medium |
| CN109560903A (en) * | 2019-02-14 | 2019-04-02 | 湖南智领通信科技有限公司 | A kind of vehicle-mounted command communications system of complete disaster tolerance |
| CN112887109A (en) * | 2019-11-29 | 2021-06-01 | 北京百度网讯科技有限公司 | Disaster recovery processing method, device, equipment and readable medium for infrastructure area |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1536811A (en) * | 2003-04-09 | 2004-10-13 | 华为技术有限公司 | Network authentication charging method |
| CN100375458C (en) * | 2005-05-13 | 2008-03-12 | 中兴通讯股份有限公司 | Method for coordination working of multi-servicer apparatus in domestic network |
| CN100446495C (en) * | 2006-06-28 | 2008-12-24 | 华为技术有限公司 | Method and system for sharing connection dynamically |
-
2008
- 2008-02-02 CN CN2008100575018A patent/CN101227333B/en active Active
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010149117A1 (en) * | 2009-11-04 | 2010-12-29 | 中兴通讯股份有限公司 | Method and apparatus for implementing service system protection |
| CN102215271A (en) * | 2010-04-07 | 2011-10-12 | 上海交通大学医学院附属瑞金医院 | Addressing processing method and device for FTP (file transfer protocol)-based disaster recovery server |
| CN104836689A (en) * | 2015-05-21 | 2015-08-12 | 武汉新芯集成电路制造有限公司 | Server fault transfer method and system |
| CN105024855A (en) * | 2015-07-13 | 2015-11-04 | 浪潮(北京)电子信息产业有限公司 | Distributed cluster management system and method |
| CN105024855B (en) * | 2015-07-13 | 2018-09-04 | 浪潮(北京)电子信息产业有限公司 | Distributed type assemblies manage system and method |
| CN106878254B (en) * | 2016-11-16 | 2020-09-25 | 国家数字交换系统工程技术研究中心 | Method and device for improving safety of DNS (Domain name System) |
| CN106878254A (en) * | 2016-11-16 | 2017-06-20 | 国家数字交换系统工程技术研究中心 | Improve the method and device of DNS securities of system |
| CN108900572A (en) * | 2018-05-31 | 2018-11-27 | 康键信息技术（深圳）有限公司 | Primary database domain name method for handover control, computer equipment and storage medium |
| CN108900572B (en) * | 2018-05-31 | 2022-08-09 | 康键信息技术（深圳）有限公司 | Main database domain name switching control method, computer equipment and storage medium |
| CN109560903A (en) * | 2019-02-14 | 2019-04-02 | 湖南智领通信科技有限公司 | A kind of vehicle-mounted command communications system of complete disaster tolerance |
| CN109560903B (en) * | 2019-02-14 | 2024-01-19 | 湖南智领通信科技有限公司 | Vehicle-mounted command communication system for complete disaster recovery |
| CN112887109A (en) * | 2019-11-29 | 2021-06-01 | 北京百度网讯科技有限公司 | Disaster recovery processing method, device, equipment and readable medium for infrastructure area |
| US11362885B2 (en) | 2019-11-29 | 2022-06-14 | Beijing Baidu Netcom Science And Technology Co., Ltd. | Method, apparatus, device and readable medium for disaster recovery processing for infrastructure areas |
| CN112887109B (en) * | 2019-11-29 | 2023-01-06 | 北京百度网讯科技有限公司 | Disaster recovery processing method, device, equipment and readable medium for infrastructure area |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101227333B (en) | 2010-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101227333B (en) | Disaster tolerance network managing system and login method of network managing subscriber end | |
| US10140112B2 (en) | Update management system and update management method | |
| CN107846315B (en) | Service migration method, device and system of data center | |
| CN102664747B (en) | Cloud calculating platform system | |
| CN101145972B (en) | A disaster tolerance network management system and login method of network management clients | |
| CN101729290A (en) | Method and device for realizing business system protection | |
| CN103368768A (en) | Automatically scaled network overlay with heuristic monitoring in hybrid cloud environment | |
| CN105099789A (en) | Network element uploading method and equipment | |
| EP1924086B1 (en) | Method and system for upgrading distributed set top box and device thereof | |
| CN101902361B (en) | Disaster tolerance business system and disaster tolerance method | |
| WO2006065661A2 (en) | Systems and methods providing high availability for distributed systems | |
| CN103312809A (en) | Distributed management method for service in cloud platform | |
| CN101595689B (en) | Change of subscriber information in a multi-chassis network access environment | |
| EP3806395A1 (en) | Virtual network function (vnf) deployment method and apparatus | |
| US9451483B2 (en) | Mobile communication system, communication system, control node, call-processing node, and communication control method | |
| CN107682411A (en) | A kind of extensive SDN controllers cluster and network system | |
| US8614943B2 (en) | Method and apparatus for protecting subscriber access network | |
| CN101005399A (en) | Network device managing method, network device and network managing system | |
| CN100563263C (en) | In network storage service, realize the method and system of system high-available | |
| CN107733717B (en) | Network configuration method for mobile operation and maintenance of cloud platform | |
| US20180367427A1 (en) | Method for performing connectivity check and apparatus | |
| KR20140061534A (en) | Scalable distributed multicluster device management server architecture and method of operation thereof | |
| CN104618148A (en) | Firewall device and backup method thereof | |
| CN110661651A (en) | SDN controller data management method, system, device and readable storage medium | |
| CN114338670B (en) | Edge cloud platform and network-connected traffic three-level cloud control platform with same |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |