WO2008014639A1 - A distributed master and standby managing method and system based on the network element - Google Patents

A distributed master and standby managing method and system based on the network element Download PDF

Info

Publication number
WO2008014639A1
WO2008014639A1 PCT/CN2006/001882 CN2006001882W WO2008014639A1 WO 2008014639 A1 WO2008014639 A1 WO 2008014639A1 CN 2006001882 W CN2006001882 W CN 2006001882W WO 2008014639 A1 WO2008014639 A1 WO 2008014639A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
server
station
primary station
primary
Prior art date
Application number
PCT/CN2006/001882
Other languages
English (en)
French (fr)
Inventor
Xia Jiang
Original Assignee
Zte Corporation
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zte Corporation filed Critical Zte Corporation
Priority to ES06761596.3T priority Critical patent/ES2526809T3/es
Priority to CN200680055272.5A priority patent/CN101485139B/zh
Priority to PCT/CN2006/001882 priority patent/WO2008014639A1/zh
Priority to EP06761596.3A priority patent/EP2053780B1/en
Priority to BRPI0621898-9A priority patent/BRPI0621898A2/pt
Priority to PT67615963T priority patent/PT2053780E/pt
Publication of WO2008014639A1 publication Critical patent/WO2008014639A1/zh
Priority to HK09106261.0A priority patent/HK1128564A1/xx

Links

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/04—Network management architectures or arrangements
    • H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2023—Failover techniques
    • G06F11/2033—Failover techniques switching over of hardware resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2035—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant without idle spare hardware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40169—Flexible bus arrangements
    • H04L12/40176—Flexible bus arrangements involving redundancy
    • H04L12/40202—Flexible bus arrangements involving redundancy by using a plurality of master stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/42—Loop networks
    • H04L12/437—Ring fault isolation or reconfiguration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1034—Reaction to server failures by a load balancer

Definitions

  • the invention relates to a method for active and standby management in a network management system in the field of optical communication, in particular to a method and system for distributed active and standby management based on a network element.
  • the network management system of the communication field when the centralized network management system is running, if the network management system is abnormal, the network management system will be unavailable and the reliability will not be high.
  • there is a scheme of the active and standby network management in the communication industry system that is, two sets of network management systems work at the same time, one master one standby or one master multiple standby, the main network management collects historical data, and manages the network element, the active/standby
  • the network management method is usually based on network system management.
  • the existing active and standby network management methods usually have two usage methods:
  • One method is based on the upper-layer database mirroring, that is, the secondary network management completely mirrors the data of the main network management system, so that all data is retained when the main network management system fails.
  • the primary server manages the network element as the primary network management system
  • the secondary server as the secondary network management server completely mirrors the data of the primary server.
  • all data can be recovered from the secondary server. .
  • Another method is the thermal monitoring method.
  • the main manager (Manager) exists when managing the network element, in order to enhance the reliability of network management, one or more sub-managers, primary and secondary management are required.
  • the data is synchronized, and in the event that the primary manager fails, the secondary manager can be switched to the primary administrator to manage the network management system.
  • the primary server serves as the primary administrator to manage the system network element
  • the secondary server as the secondary administrator can also monitor and manage the network element
  • the primary and secondary servers perform data synchronization, and the primary server fails or
  • the sub-manager is directly switched as the main manager of the network element to manage the network element.
  • the main network management load is too large.
  • all network element data of the network management system interacts with the main network management system, causing the main network management load to be too large and there are security risks.
  • the technical problem to be solved by the present invention is to provide a method and system for distributed primary and secondary management based on a network element, so that the primary and secondary network management systems share the load and improve the reliability of the network management.
  • the present invention provides a method for distributed primary and backup management based on a network element, including the following steps:
  • the two servers are connected to each other and connected to an access network element that configures itself as the primary station. After the work, the two servers are managed as the primary station. Partial network elements allocated by each, as a secondary station to monitor another part of the network element;
  • the server is restored as the primary station to manage the network elements according to the return policy.
  • the above method can also have the following characteristics:
  • the step of connecting all the network elements in the step (a) and configuring the routing of the network element to be bidirectional interworking includes:
  • the step of configuring the management rights of the two servers in the network element in the step (a) is as follows: According to the principle of load balancing of the two servers, all the network elements are equally divided into two parts; part of the network elements configures the server A as The primary station configures server B as a secondary station; the other part of network element server B is configured as a primary station, and server A is configured as a secondary station.
  • the server in the step (b) is configured as a primary station to configure the network element as the primary station
  • the historical data of the network element is collected, and the corresponding configuration query is performed on the network element;
  • the server is managed as a secondary station. Query and monitor NEs when configuring the NEs of the primary station.
  • step (b) data synchronization is performed between the servers configured as the primary station and the secondary station, and data synchronization between the primary and secondary stations is maintained by performing database synchronization, wherein historical data in the primary and secondary stations are Full amount.
  • the step (c) includes:
  • the network element When the network element detects that the communication with the server configured as the primary station is interrupted, the network element notifies the server configured as the secondary station to manage the network element as the primary station;
  • the secondary server When the server configured as the secondary station by the network element detects that the server configured by the network element is the primary station, the secondary server actively requests the primary station authority from the network element, where the network element belongs to the current primary. The state of the station server determines whether to switch the secondary station to manage the network element for the primary station.
  • the return policy described in the step (b) is configured as a primary station return mode or a non-return mode, and if it is a primary station return mode, the communication recovery of the network element and the server configured as the primary station in the step (d) is restored. Recovering the server configured as the primary station as the primary station to manage the network element, and switching the current primary station as the secondary station, and simultaneously recovering the data of the primary station server during the synchronization interruption; if the primary station is not returning, In the step (d), when the communication between the network element and the server configured as the primary station is restored, the server configured as the primary station is restored as the secondary station to manage the network element, and the data during the interruption period is synchronized. When the server of the current primary station is disconnected, the network element is accessed in the form of a primary station.
  • the two servers that is, the server A and the server ⁇ are respectively connected to the first-end network element and the end network element in the serial-connected network element.
  • the present invention further provides a network element-based distributed active/standby management system, comprising a plurality of network elements and a server A and a server B for managing the network elements, wherein:
  • All the network elements are connected to each other, and the routing is configured to be bidirectional.
  • the management rights of server A and server B are configured in each network element. Some of the network elements configure server A as the primary station and server B as the secondary station. Another part of the network element configures server B as the primary station and server A as the secondary station.
  • the network element switches when the communication with the server configured as the primary station is interrupted, and the other server configured as the secondary station serves as the primary station; after the communication with the server configured as the primary station is resumed, Return the strategy to switch it back;
  • the two servers are connected to each other and configured with a return policy of the primary station, and each server is respectively connected to an access network element that configures itself as a primary station, and manages each of the allocated network elements as a primary station during operation.
  • the secondary station monitors another part of the network element;
  • the two-month server changes the primary and secondary status of the network element when the network element switches, and the server restores the communication with the network element that configures the primary station.
  • the management of these network elements is resumed according to the return policy.
  • the above system may also have the following features:
  • the server when the primary station manages the network element configured as the primary station, collects the historical data of the network element, performs corresponding configuration query on the network element, and configures the network element as the secondary station as the secondary station management.
  • the network element is queried and monitored.
  • the two-month server performs data synchronization when the primary station and the secondary station configured as the network element work normally, and maintains data synchronization between the primary and secondary stations by performing database synchronization, wherein the primary and secondary stations Historical data is full.
  • the returning policy of the server as a primary station is configured as a return mode or a non-return mode of the primary station. If the primary station returns a mode, the network element restores its configuration when the communication with the server configured as the primary station is restored.
  • the server of the station acts as a primary station to manage the network element, and switches the data of the current primary station to the secondary station and the restored primary station server during the synchronization interruption;
  • the network element communicates with the server configured as the primary station.
  • the server configured as the primary station is restored as the secondary station to manage the network element, and the data during the interruption is synchronized, and the network element is accessed as the primary station when the server of the current primary station is disconnected.
  • the network element when detecting that the communication with the server configured as the primary station is interrupted, notifying the server configured as the secondary station as the primary station to manage the network element; or detecting the network element configuration on the network element configured as the secondary station
  • the secondary station server actively requests the primary station authority from the network element, and the network element determines whether to switch the secondary station to manage the network element according to the status of the current primary station server.
  • All the network elements are connected in series with each other, and the weapon is connected to the two servers, that is, the server A and the server respectively through the head end network element and the end network element.
  • the two servers when managing the network element as the primary station management, balance the number of network elements that are configured to be the primary station, and load balance the respective network elements.
  • two-way routing needs to be configured for the network element, and the two network management systems are connected to the network element.
  • the network element-based distributed active/standby management technical measures are adopted.
  • the load balancing of the primary and secondary network management is implemented, and the reliability of the network management is improved. Further, load balancing can also be obtained, and the effect of the entire network management can be achieved even if the local ECC is disconnected.
  • FIG. 1 is a schematic diagram of a commonly used active and standby management technology based on upper layer database mirroring
  • FIG. 2 is a schematic diagram of a commonly used existing active and standby management technology based on thermal monitoring
  • FIG. 3 is a schematic diagram of a network element-based distributed active/standby management method according to an embodiment of the present invention
  • FIG. 4 is an example of a server 1 interrupt in a network element distributed active/standby management method according to a technical solution of the present invention
  • FIG. 5 is an example of a network element ECC interrupt in a network element distributed active/standby management method according to the technical solution of the present invention. Preferred embodiment of the invention
  • This embodiment proposes a method for distributed active/standby management based on network elements of a dense wavelength division multiplexing system, but is also used in a network management system in other types of optical communication networks.
  • the method is a distributed active/standby management system based on a network element, and is a dynamic protection mode of the network management system, where two network management servers are equal to each other, and two network management servers are connected to different gateway network elements, and There are corresponding primary and secondary permissions for each different network element. All the NEs in the system are ECC interworking, and bidirectional routing is configured. Each NE can independently configure the active and standby administrators (that is, the active and standby network management servers). The functions and roles of these administrators are equal. That is, one manager is the primary station for one network element, but may be a secondary station for another network element.
  • the active and standby network management servers manage all the NEs, and the two network management servers are allocated as the number of NEs managed by the primary station to achieve load balancing.
  • the backup network management unit corresponding to the NE The server is only in the monitoring state and cannot be configured.
  • the secondary network management server of the corresponding network element replaces the primary network management server of the network element, and has all the management functions of the primary network management server. Continue to manage part of the network or the entire network.
  • a network element-based distributed active/standby management method may refer to FIG. 3 and may include the following steps:
  • Step 1 Connect all NEs and configure the routing of the NEs to work in both directions. Configure the management rights of Server A and Server B in the NE. Some NEs configure Server A as the primary station and Server B. For the secondary station, another part of the network element configures server B as the primary station and server A as the secondary station.
  • all network elements can be connected in series.
  • the routing of the NEs is configured to ensure that the routing of the NEs is two-way. If one direction fails, you can switch to the routing of the other direction.
  • the network element 11-ln is planned to use the server 1 as the primary station
  • the network element 21-2n is planned to be Server 2 is the master station.
  • the main network management system collects historical data, and the historical data volume in the wavelength division network management system is relatively large. Therefore, the load balancing of the two network management systems should be performed as much as possible during normal operation.
  • the corresponding authority of the relevant manager in the network element is planned and configured, and the network element 11-ln is configured with the server 1 as the primary station and the server 2 as the secondary station; the network element 21-2n is configured to use the server 2 as the primary station.
  • Server 1 is the secondary station.
  • Step 2 Configure the return policy of the primary station in the two servers.
  • the two servers are connected to each other and connected to an access NE that configures itself as the primary station. After the work, the two servers serve as the primary station. Manage some of the assigned network elements as a secondary station to monitor another part of the network element.
  • the return policy when the primary station takes effect is configured on the two servers, including: the primary station return mode, that is, the primary station becomes the corresponding primary station immediately after recovery;
  • the non-return mode of the primary station means that the primary station becomes the secondary station after it is restored, and becomes the primary station when the primary station applies.
  • the server 1 is connected to the server 2, and the server 1 is accessed through the network element 11, as the primary station of the network element 11-ln, and the server 2 is accessed through the network element 2n as the primary station of the network element 21-2n.
  • the server 1 is connected to the server 2, and the server 1 is accessed through the network element 11, as the primary station of the network element 11-ln, and the server 2 is accessed through the network element 2n as the primary station of the network element 21-2n.
  • the server 1 in the normal operation is the main network management of the network element 11...the network element In, and the corresponding server 2 is the secondary network management of these network elements; the server 2. at the same time is the network element 21. ..
  • the main network management of network element 2n, server 1 is their secondary network management.
  • 5 are interoperable.
  • the master station manages the corresponding NEs, collects historical data of the NEs, and performs operations such as configuration query for the NEs.
  • the backup network management system can only query and monitor NEs, cannot perform configuration operations, and does not collect history.
  • the data is synchronized between the secondary network management system and the primary network management system to ensure that the data between the primary and secondary network management systems is the same.
  • the management rights of the primary and secondary stations may have different management rights and management functions depending on the requirements of the specific system, but the secondary station must be able to monitor the network elements.
  • Step 3 If the communication between the network element and the server configured as the primary station is interrupted, the network element switches The network element is managed for another server configured as a secondary station as a primary station.
  • the network element selects the network management device configured as the secondary station as the primary station according to the previously configured administrator authority, and sends a notification to the corresponding secondary station network management to switch to the primary station.
  • Management network element with all permissions of the primary station;
  • one server detects another server abnormality, it actively requests the network element to request the authority of the primary station, and the network element determines whether the corresponding primary station authority can be given to the secondary station according to the currently managed network management.
  • Step 4 After the communication between the network element and the server configured as the primary station is restored, the server is restored as the primary station to manage the network elements according to the return policy.
  • the network element When the communication between the network element and the primary station is resumed, the network element is managed according to a pre-configured return policy, wherein the data of the primary station needs to be synchronized with another secondary station that is replaced with the primary station.
  • the NE detects that the primary server is normal, notifies the secondary server to switch back to the secondary station; and the primary server synchronizes the data during the interruption;
  • the secondary server detects that the primary server is normal, it performs switching between the primary and secondary stations and data synchronization.
  • the configured return policy is the master non-return mode
  • the primary station when the primary station recovers, the primary station is first restored as the secondary station management network element, and the data during the interruption period is synchronized with the secondary server currently serving as the primary station, and waits until the secondary server is disconnected. It is then accessed in the form of a primary station to manage the network element as the primary station.
  • Figure 4 is a schematic diagram of the system when the server 1 and the network element are disconnected and fails.
  • the active/standby management when the server 1 and the network element are disconnected mainly includes the following steps:
  • the network element 11-ln is configured to use the server 1 as the primary station and the server 2 as the secondary station, and the network The element 21-2n is configured such that the server 2 is the primary station and the server 1 is the secondary station.
  • the server 1 and the server 2 are connected to the network element.
  • the server 1 serves as the primary station management network element 11...the network element In, and the server 2 manages the network elements as the secondary station; the server 2 serves as the primary station management.
  • the server 1 switches to the primary station of the network element 11...the network element In, and the server 2 still switches and resumes. It is a secondary station of the network element 11...network element In, wherein during the handover, the server 1 needs to perform data synchronization with the server 2 to recover data during the communication interruption.
  • FIG. 5 is a schematic diagram of a system when the ECC is disconnected between the network element 11 and the network element 12.
  • the active/standby management when the ECC is disconnected between the network elements mainly includes The following steps:
  • the network element 11-ln is configured with the server 1 as the primary station and the server 2 as the secondary station, and the network element 21-2n is configured to use the server 2 as the primary station and the server 1 as the secondary station.
  • the server 1 and the server 2 are connected to the network element.
  • the server 1 serves as the primary station management network element 11...the network element ln, and the server 2 manages the network elements as the secondary station;
  • the server 2 As the primary station management network element 21...network element 2n, the server 1 manages these network elements as a secondary station;
  • the data synchronization is configured between the server 1 and the server 2, ensuring that the data of the two servers are completely identical and all are full. data.
  • the In notification server 2 switches the primary station as the network element. At this time, the server 2 manages all the historical data as part of the network element of the network element 1 series and all the network elements of the network element 2 series, and the server 1 can only serve as the primary station.
  • the master station manages some network elements of the network element 1 series.
  • the system load balances during normal operation the system can still be managed normally when ECC is disconnected, and all data is not lost.
  • the network element-based active/standby management method of the present invention ensures that the active and standby network management systems manage a part of network elements, and the number of network elements managed by the manager as the primary station can be load balanced; The network elements that are accessed by them are different. When there is an ECC interruption, all the network elements can be managed, which can improve the reliability of the system.
  • the access gateway network element of the server may not be set to be the first or last of the serial connection network element.
  • the server 2 is connected to the network element 21.
  • the network element 22-2n is not connected to any one of the server A and the server B, thereby causing The network management server cannot manage these network elements. Therefore, the reliability of this connection is poor.
  • a method and system for distributed primary and secondary management based on a network element disclosed in the present invention is a dynamic network management protection mode of a distributed active/standby management system based on a network element, where two network management servers are mutually Equally, the two network management servers are connected to different gateway network elements, and have corresponding primary and secondary rights for each different network element.
  • two-way routing needs to be configured for the network element, and the two network management servers are connected to the network element. By properly allocating the two network management servers as the number of network elements managed by the primary station, the two servers are common.
  • the secondary network management of the corresponding NE replaces the primary network management of the NE and continues to manage part of the network or the entire network. The reliability of system network management.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Hardware Redundancy (AREA)
  • Computer And Data Communications (AREA)

Description

一种基于网元的分布式主备管理的方法及系统 技术领域
本发明涉及光通讯领域网管系统中主备管理的方法，尤其涉及一种基于 网元的分布式主备管理的方法及系统。
背景技术
目前， 在通讯领域的网管管理系统中， 集中式网管运行时， 如果网管系 统异常， 将会导致网管不可用， 可靠性不高。 为了解决这个问题， 在通信行 业系统中存在主备网管的方案， 即两套网管同时工作， 一主一备或者一主多 备， 主网管采集历史数据， 对于网元进行管理， 这种主备网管方法通常是基 于网络系统管理的。
现有的主备网管方法， 通常有两种使用方式：
( 1 )一种方式是基于上层数据库镜像， 即副网管对于主网管的数据完 全镜像， 这样保证在主网管运行失效时所有的数据均会保留。 参考图 1 , 主 服务器作为主网管对网元进行管理，而作为副网管的副服务器对主服务器的 数据进行完全镜像， 在主服务器出现异常而运行失效时， 所有数据均可以从 副服务器中恢复。
( 2 ) 另一种方式是热监控方法， 由于对网元进行管理时， 存在主管理 者 （Manager ) , 为了增强网络管理的可靠性， 需要存在一个或多个副管理 者， 主、 副管理者数据进行同步， 在主管理者失效的情况下， 可以将副管理 者切换为主管理者管理网管系统。 参考图 2, 主服务器作为主管理者管理系 统网元， 而副服务器作为副管理者也能对所述网元也进行监测管理， 主、 副 服务器两者进行数据同步， 在主服务器出现故障或异常而运行失效时， 直接 切换副管理者作为网元的主管理者， 对网元进行管理。
但是， 如图 1和图 2所示的传统主副网管系统存在如下问题：
( 1 )主网管负荷过大。 系统运行时， 网管系统的所有网元数据都和主 网管进行交互， 造成主网管负荷过大， 存在安全隐患。 ( 2 )在系统中， 由于主副服务器仅采用一个接入网元进行接入， 且各 网元为单向连通， 所以在网元 ECC (嵌入控制通道 Embedded Control Channel ) 中断时， 会有部分网元监控失效。 例如， 在图 1或者图 2中， 当 网元 11和网元 12之间 ECC断开时， 主、 副网管都只能管理网元 11 , 对于 网元 11后面的网元均不能管理。
为此， 需要一种能够解决主网管负荷太大、 ECC 中断时会有部分网元 监控失效、 系统运行可靠性低等缺点的主备管理方法。 发明内容
本发明所要解决的技术问题在于，提供一种基于网元的分布式主备管理 的方法及系统， 使得主副网管负载分担、 提高网管管理的可靠性。
本发明提供一种基于网元的分布式主备管理的方法， 包括如下步驟：
( a )连接所有网元并将网元的路由配置为双向互通， 并配置好网元中 服务器 A和服务器 B的管理权限，其中一部分网元将服务器 A配置为主站， 将服务器 B配置为副站， 另一部分网元将服务器 B配置为主站， 将服务器 A配置为副站；
( b )在两个服务器中配置好主站的返回策略， 两个服务器彼此相接， 并分别连接到将自己配置为主站的一个接入网元， 工作后， 两个服务器作为 主站管理各自分配的部分网元， 作为副站监测另一部分网元；
( c )如有网元与其配置为主站的^^务器的通讯中断， 所述网元进行切 换， 以其配置为副站的另一服务器作为主站对所述网元进行管理；
( d ) 当所述网元与其配置为主站的服务器的通讯恢复后， 按照所述返 回策略恢复该服务器作为主站对这些网元的管理。 进一步地， 上 方法还可具有以下特点：
所述步骤（a ) 中连接所有网元并将网元的路由配置为双向互通的步驟 包括：
串连连接所有网元， 使得所述网元嵌入控制通道是互通的； 将每一网元的路由配置为双向互通。
所述步骤（a ) 中配置网元中两个服务器的管理权限的步骤为： 依据两个服务器负载均衡的原则， 将所有网元均衡地分为两个部分； 一部分网元将服务器 A配置为主站， 将服务器 B配置为副站； 另一部分网元 服务器 B配置为主站， 将服务器 A配置为副站。
所述步骤（b ) 中所述服务器作为主站管理将其配置为主站的网元时， 采集网元的历史数据，对于网元进行相应的配置查询； 所述服务器作为副站 管理将其配置为主站的网元时， 查询及监控网元。
所述步骤（b )中配置为主站和副站的服务器之间工作时进行数据同步， 通过进行数据库同步来保持主副站之间的数据同步， 其中， 主副站中的历史 数据都是全量的。
所述步驟（ c ) 包括：
当网元检测到与其配置为主站的服务器通讯中断时，所述网元通知其配 置为副站的服务器作为主站管理该网元；
或被网元配置为副站的服务器检测到被网元配置为主站的服务器异常 时， 所述副站月良务器主动向所述网元请求主站权限， 所述网元 居当前主站 服务器的状态决定是否切换副站为主站管理所述网元。
步骤（b ) 中所述返回策略配置为主站返回方式或非返回方式， 如果是主站返回方式， 则所述步驟（d ) 中当所述网元与其配置为主站 的服务器的通讯恢复时，恢复其配置为主站的服务器作为主站来管理所述网 元，并切换当前主站为副站，同时恢复后的主站服务器同步中断期间的数据； 如果是主站非返回方式， 则所述步骤（d ) 中当所述网元与其配置为主 站的服务器的通讯恢复时，恢复其配置为主站的服务器作为副站来管理所述 网元， 并同步中断期间的数据，待当前主站的服务器断开时再以主站形式接 入所述网元。
所述步骤（b ) 中， 所述两个服务器， 即服务器 A和服务器^ 分别接 入到串接网元中的首端网元与末端网元。 本发明还提供一种基于网元的分布式主备管理系统，包括多个网元和用 于对这些网元进行管理的服务器 A和服务器 B, 其特点在于：
所有网元相互连接， 其路由配置为双向互通， 且在各网元中配置有服务 器 A和服务器 B的管理权限， 其中一部分网元将服务器 A配置为主站， 将 服务器 B配置为副站， 另一部分网元将服务器 B配置为主站， 将服务器 A 配置为副站；
所述网元在与其配置为主站的服务器的通讯中断时进行切换，以其配置 为副站的另一服务器作为主站； 在与其配置为主站的服务器的通讯恢复后， 再按照所述返回策略将其切换回来；
所述两个服务器彼此相接且配置有主站的返回策略，每个服务器分别连 接到将自己配置为主站的一个接入网元，工作时作为主站管理各自分配的部 分网元， 作为副站监测另一部分网元；
所述两个月良务器在发生通讯中断， 收到网元切换的通知时， 变换自己对 于所述网元的主副状态，服务器恢复与将其配置为主站的网元的通讯后，按 照所述返回策略恢复对这些网元的管理。 进一步地， 上述系统还可具有以下特点：
所述服务器， 作为主站管理将其配置为主站的网元时， 采集网元的历史 数据，对于所述网元进行相应的配置查询； 作为副站管理将其配置为副站的 网元时， 查询及监控所述网元。
所述两个月良务器， 在配置为网元的主站和副站正常工作时， 进行数据同 步， 通过进行数据库同步来保持主副站之间的数据同步， 其中， 主副站中的 历史数据都是全量的。 '
所述服务器作为主站的返回策略， 配置为主站返回方式或非返回方式， 如果是主站返回方式，所述网元在与其配置为主站的服务器的通讯恢复 时， 恢复其配置为主站的服务器作为主站来管理所述网元， 并切换当前主站 为副站， 同时恢复后的主站服务器同步中断期间的数据；
如果是主站非返回方式，则所述网元在与其配置为主站的服务器的通讯 恢复时， 恢复其配置为主站的服务器作为副站来管理所述网元， 并同步中断 期间的数据， 待当前主站的服务器断开时再以主站形式接入所述网元。
所述网元，在检测到与其配置为主站的服务器通讯中断时， 通知其配置 为副站的服务器作为主站管理该网元；或在网元配置为副站的服务器检测到 网元配置为主站的服务器异常时，所述副站服务器主动向所述网元请求主站 权限，所述.网元根据当前主站服务器的状态决定是否切换副站为主站管理所 述网元。
所述所有网元，彼此串接相连， 兵器通过首端网元与末端网元与所述两 个服务器， 即即服务器 A和服务器 分别相接。
所述两个服务器， 在作为主站管理分别管理所述网元时， 所管理的将其 配置为主站的网元数目均衡， 负载均衡的分别管理相应网元。
采用本发明所述的技术方案， 与现有技术相比， 对于网元需要配置双向 路由， 两个网管都和网元进行接入； 由于采取了基于网元的分布式主备管理 技术措施，实现了主副网管负载分担、提高了网管管理的可靠性。进一步地， 还可以取得负载均衡， 在局部 ECC断开仍然可实现全网管理等效果。 附图概述
图 1是一种常用现有的基于上层数据库镜像的主备管理技术原理图； 图 2是一种较常用现有的基于热监控的主备管理技术原理图；
图 3 是根据本发明实施例的一种基于网元的分布式主备管理方法的原 理图；
图 4是根据本发明技术方案的基于网元分布式主备管理方法中， 一个 服务器 1中断的实例；
图 5 是根据本发明技术方案的基于网元分布式主备管理方法中， 一个 网元 ECC中断的实例。 本发明的较佳实施方式
下面结合附图及较佳的具体实施方式，对本发明的技术方案的作进一步 的详细描述。
本实施例提出了一种基于密集波分复用系统网元的分布式主备管理的 方法， 但是也用于其它类型的光通讯网络中的网管系统。
该方法是基于网元的分布式主备管理系统， 是网管的一种动态保护方 式， 其中， 两个网管服务器之间都是互相平等的， 两个网管服务器与不同的 网关网元连接， 并且针对于每个不同的网元有相应的主副权限。 系统中的所 有的网元都是 ECC互通的， 而且配置了双向路由， 每一网元都可以独立配 置主备管理者（即主备网管服务器），这些管理者的功能和角色都是平等的， 即一个管理者对于一个网元是主站， 但对另一个网元就可能是副站。
正常情况下， 主备网管服务器都会管理所有网元， 合理分配两个网管服 务器作为主站管理的网元个数，做到负载均衡； 当主网管服务器处于正常工 作状态时， 网元对应的备网管服务器只处于监视状态不能进行配置。 当网络 处于异常状态， 或主网管服务器异常的情况下， 或者网元的 ECC 出现中断 时， 相应网元的副网管服务器取代该网元的主网管服务器， 具有主网管服务 器所有的管理功能， 以继续管理部分网絡或整个网络。
本实施例所述的一种基于网元的分布式主备管理方法， 参照图 3 , 可以 包括如下步骤：
第一步： 连接所有网元并将网元的路由配置为双向互通， 并配置好网元 中服务器 A和服务器 B的管理权限， 其中一部分网元将服务器 A配置为主 站， 将服务器 B配置为副站， 另一部分网元将服务器 B配置为主站， 将服 务器 A配置为副站。
首先， 所有网元可以串连的方式进行连接， 同时， 配置好网元的路由， 保证网元路由都是双向互通的， 当有一个方向不通时， 能够切换到另一个方 向的路由上。
才艮据实际的系统运行情况，需要规划好两个服务器作为主站管理的网元 数目， 例如将网元 11-ln规划为以服务器 1为主站， 将网元 21-2n规划为以 服务器 2为主站。 由于对于网元来说只有主网管采集历史数据， 而作为波分 网管系统中历史数据量是比较大的，所以尽量要做到正常运行时两个网管负 载均衡。
然后， 才 居规划配置好网元中相关管理者的相应权限， 配置网元 11-ln 以服务器 1为主站，以服务器 2为副站；配置网元 21-2n以服务器 2为主站， 以服务器 1为副站。
第二步：在两个服务器中配置好主站的返回策略，两个服务器彼此相接， 并分别连接到将自己配置为主站的一个接入网元， 工作后， 两个服务器作为 主站管理各自分配的部分网元， 作为副站监测另一部分网元。
首先， 需要在两个服务器上分别配置主站生效时的返回策略， 包括： 主站返回方式， 即主站恢复后立即成为相应的主站；
主站非返回方式， 指主站恢复后先成为副站， 等到主站申请时才成为主 站。
然后， 将服务器 1与服务器 2相连接， 将服务器 1通过网元 11接入， 作为网元 11-ln的主站,将服务器 2通过网元 2n接入,作为网元 21-2n的主 站， 如图 3所示， 当然也可以将两个服务器接入其它将其配置为主站的任一 网元。
在图 3所示的网管系统中， 正常运行时服务器 1为网元 11...网元 In的 主网管， 相应的服务器 2为这些网元的副网管； 服务器 2.同时为网元 21... 网元 2n的主网管， 服务器 1为它们的副网管。 这些网元 ECC (嵌入控制通 道 Embedded Control Channel )啫 |5是互通的。
正常运行时， 主站管理相应的网元， 采集网元的历史数据， 对于网元能 够进行相应的配置查询等操作； 而备网管只能查询及监控网元， 不能进行配 置操作， 不采集历史数据； 副网管通过和主网管之间进行数据库同步， 保证 主备网管之间的数据完全一致， 主副网管中的历史数据都是全量的。
在不同的通讯系统中 ,主站和副站的管理权限可能会依具体系统的不同 要求而具有不同的管理权限和管理职能， 但副站必须能够对网元进行监测。
第三步： 如有网元与其配置为主站的艮务器的通讯中断， 所述网元切换 为以其配置为副站的另一服务器作为主站对所述网元进行管理。
在正常运行时， 需要检测网元与其主站之间的通讯状态：
当网元检测和网管的心跳包不再有响应时，网元根据事先配置好的管理 者权限，选择其配置为副站的网管作为主站， 并发送通知相应的副站网管切 换为主站管理网元， 具有主站的所有权限；
或者当一个服务器检测到另一个服务器异常时，主动去 ... ...网元请求主 站权限， 网元根据当前管理的网管判断是否可以给予副站相应的主站权限。
第四步： 当所述网元与其配置为主站的服务器的通讯恢复后， 按照所述 返回策略恢复该服务器作为主站对这些网元的管理。
在网元与主站之间的通讯恢复时，才艮据预先配置好的返回策略对网元进 行管理， 其中主站的数据需要和另一个被替换为主站的副站进行同步。
如果配置的返回策略为主站返回方式， 则服务器和网元建链时， 网元探 测到主服务器正常，通知副服务器切换恢复重新作为副站； 同时主服务器同 步中断期间的数据； 也可以是副服务器探测到主服务器正常时， 进行主副站 的切换及数据同步。
如果配置的返回策略为主站非返回方式， 则主站恢复时， 主站首先被恢 复作为副站管理网元， 与当前作为主站的副服务器同步中断期间的数据， 等 到副服务器断开时再以主站形式接入， 以作为主站管理网元。
该步骤在技术实现与热监控主控方法是基本类似的。 应用实例 1: 服务器 1和网元中断连接失效的情况。
图 4显示了服务器 1和网元中断连接而失效时系统的示意图，依据本发 明所述主备管理方法的技术方案，对服务器 1和网元中断连接时的主备管理 主要包括如下步骤：
( 1 )连接网元 11…网元 In…网元 21…网元 2n, 并在所述网元上配置 好网元的双向路由， 配置好网元中服务器 1和服务器 2的权限， 配置好主站 的返回策略为主站返回式。
其中， 网元 11-ln被配置为以服务器 1为主站， 服务器 2为副站， 而网 元 21-2n被配置为以服务器 2为主站， 服务器 1为副站。
( 2 )将服务器 1和服务器 2接入到网元中， 正常运行时， 服务器 1作 为主站管理网元 11…网元 In, 服务器 2作为副站管理这些网元； 服务器 2 作为主站管理网元 21…网元 2n, 服务器 1作为副站管理这些网元； 服务器 1和服务器 2之间配置好数据同步， 保证两个服务器的数据都是完全一致的 而且都是全量的数据。
( 3 )参照图 4所示， 当服务器 1和网元 11之间通讯失效时， 此时网元 11…网元 In的通讯机制探测到和^ _务器 1之间断开时， 此时网元 11...网元 In通知作为其副站的服务器 2切换作为这些网元的主站， 此时， 服务器 2 作为主站管理网络上所有网元， 采集所有的历史数据，服务器 1管理不上任 何网元。
( 4 )当服务器 1和网元 11的通讯恢复后， 由于网元中配置的返回策略 为主站返回式， 所以服务器 1切换为网元 11…网元 In的主站， 服务器 2仍 然切换恢复为网元 11…网元 In的副站， 其中， 切换过程中， 服务器 1需要 与服务器 2进行数据同步， 恢复通讯中断期间的数据。
从该实例可以看到， 正常运行时系统负载均衡，服务器断开时系统仍然 能够正常管理， 所有的数据均不会丢失。 应用实例 2: 网元之间 ECC断开的情况。
图 5显示了网元 11到网元 12之间 ECC断开时系统的示意图， 依据本 发明所述主备管理方法的技术方案， 对网元之间 ECC断开连接时的主备管 理主要包括如下步骤：
( 1 )连接网元 11…网元 In…网元 21…网元 2n, 并在所述网元上配置 好网元的双向路由， 配置好网元中服务器 1和服务器 2的权限， 配置好主站 的返回策略为主站返回式。
其中， 网元 11-ln被配置为以服务器 1为主站， 服务器 2为副站， 而网 元 21-2n被配置为以服务器 2为主站， 服务器 1为副站。
( 2 )将服务器 1和服务器 2接入到网元中， 正常运行时， 服务器 1作 为主站管理网元 11…网元 ln， 服务器 2作为副站管理这些网元； 服务器 2 作为主站管理网元 21…网元 2n, 服务器 1作为副站管理这些网元； 服务器 1和服务器 2之间配置好数据同步， 保证两个服务器的数据都是完全一致的 而且都是全量的数据。
( 3 )参考图 5所示， 当网元 11和网元 12之间 ECC断开时， 此时网元 12…网元 2n的通讯机制探测到和服务器 1之间断开时， 此时网元 12…网元
In通知服务器 2切换作为这些网元的主站， 此时服务器 2作为主站管理网 元 1系列的部分网元和网元 2系列的所有网元， 采集所有的历史数据， 服务 器 1仅能作为主站管理网元 1系列的部分网元。
( 4 )当网元 11和网元 12之间 ECC通讯恢复后， 由于网元中配置的主 站返回策略为主站返回方式，所以服务器 1切换为网元 12…网元 In的主站， 服务器 2仍然为网元 11…网元 In的副站。
从该实例可以看到， 正常运行时系统负载均衡， ECC 断开时系统仍然 能够正常管理， 所有的数据均不会丟失。
本发明所述的基于网元的主备管理方法，保证主备网管各自管理一部分 网元，合理分配管理者作为主站管理的网元个数能够做到负载均衡； 同时因 为对于主、 备管理者， 其接入的网元不同， 当其中有 ECC中断时， 还能够 管理上所有网元， 能够提高系统的可靠性。
本说明书所附实施例是体现本发明构思的一些典型例子，并不排除使用 体现本发明设计方案的其他实施例。
比如， 在另一实施例中， 服务器的接入网关网元也可以不设置为串行连 接网元的第一个或最后一个， 例如， 在图 3中， 将服务器 2接入到网元 21 , 相比于连接至网元 2n, 其在网元 21与网元 22之间发生网元 ECC中断时， 将使得网元 22-2n不在与服务器 A和服务器 B中任一个相连接， 从而造成 网管服务器不能对这些网元进行管理， 因而， 此种接法的可靠性较差。
又如， 不一定非要负载均衡的将所有网元规划分配与两个服务器相连 接， 在划分网元时， 对两个服务器而言必须做到负载分担， 仅需依据系统实 际运行时的负载情况， 使得负载分担能够使系统能够进入最佳运行状态即 可。 工业实用性
本发明公开的一种基于网元的分布式主备管理的方法及系统，是基于网 元的分布式主备管理系统的一种动态网管保护方式， 其中， 两个网管服务器 之间都是互相平等的， 两个网管服务器与不同的网关网元连接， 并且针对于 每个不同的网元有相应的主副权限。 与现有技术相比，对于网元需要配置双 向路由， 两个网管服务器都和网元进行接入； 通过合理分配两个网管服务器 作为主站管理的网元个数，使得两个 务器共同分担负载； 当网络处于异常 状态， 或主网管异常的情况下，或者网元的 ECC 出现中断时， 相应网元的 副网管取代该网元的主网管， 继续管理部分网络或整个网络，提高了系统网 管管理的可靠性。

Claims

权 利 要 求 书
1、 一种基于网元的分布式主备管理的方法， 其特征在于， 包括如下步 骤：
( a )连接所有网元并将网元的路由配置为双向互通， 并配置好网元中 服务器 A和服务器 B的管理权限，其中一部分网元将服务器 A配置为主站， 将服务器 B配置为副站， 另一部分网元将服务器 B配置为主站， 将服务器 A配置为副站；
( b )在两个服务器中配置好主站的返回策略， 两个服务器彼此相接， 并分别连接到将自己配置为主站的一个接入网元， 工作后， 两个服务器作为 主站管理各自分配的部分网元， 作为副站监测另一部分网元；
( c )如有网元与其配置为主站的服务器的通讯中断， 所述网元进行切 换， 以其配置为副站的另一服务器作为主站对所述网元进行管理；
( d ) 当所述网元与其配置为主站的服务器的通讯恢复后， 按照所述返 回策略恢复该服务器作为主站对这些网元的管理。
2、 如权利要求 1所述的方法， 其特征在于， 步骤（a ) 中连接所有网元 并将网元的路由配置为双向互通的步骤包括：
串连连接所有网元， 使得所述网元嵌入控制通道是互通的；
将每一网元的路由配置为双向互通。
3、 如权利要求 1所述的方法， 其特征在于， 步骤（a ) 中配置网元中两 个服务器的管理权限的步驟为：
依据两个服务器负载均衡的原则， 将所有网元均衡地分为两个部分； 一部分网元将服务器 A配置为主站， 将服务器 B配置为副站； 另一部分网元将服务器 B配置为主站， 将服务器 A配置为副站。
4、 如权利要求 1所述的方法， 其特征在于， 所述步骤（b ) 中所述服务 器作为主站管理将其配置为主站的网元时， 采集网元的历史数据，对于网元 进行相应的配置查询； 所述服务器作为副站管理将其配置为主站的网元时， 查询及监控网元。
5、 如权利要求 1所述的方法， 其特征在于， 所述步骤（b ) 中配置为主 站和副站的服务器之间工作时进行数据同步，通过进行数据库同步来保持主 副站之间的数据同步， 其中， 主副站中的历史数据都是全量的。
6、 如权利要求 1所述的方法， 其特征在于， 所述步骤（c ) 包括： 当网元检测到与其配置为主站的服务器通讯中断时，所述网元通知其配 置为副站的服务器作为主站管理该网元；
或被网元配置为副站的服务器检测到被网元配置为主站的服务器异常 时， 所述副站服务器主动向所述网元请求主站权限， 所述网元根据当前主站 服务器的状态决定是否切换副站为主站管理所述网元。
7、 如权利要求 1所述的方法， 其特征在于， 步骤（b ) 中所述返回策略 配置为主站返回方式或非返回方式，
如果是主站返回方式， 则所述步骤（d ) 中当所述网元与其配置为主站 的服务器的通讯恢复时，恢复其配置为主站的服务器作为主站来管理所述网 元，并切换当前主站为副站，同时恢复后的主站月良务器同步中断期间的数据； 如果是主站非返回方式， 则所述步骤（d ) 中当所述网元与其配置为主 站的服务器的通讯恢复时，恢复其配置为主站的服务器作为副站来管理所述 网元， 并同步中断期间的数据，待当前主站的服务器断开时再以主站形式接 入所述网元。
8、 如权利要求 1或 2所述的方法， 其特征在于， 所述步骤（b ) 中， 所 述两个服务器， 即服务器 A和服务器 B,分别接入到串接网元中的首端网元 与末端网元。
9、 一种基于网元的分布式主备管理系统， 包括多个网元和用于对这些 网元进行管理的服务器 A和服务器 B, 其特征在于：
所有网元相互连接， 其路由配置为双向互通， 且在各网元中配置有服务 器 A和服务器 B的管理权限， 其中一部分网元将服务器 A配置为主站， 将 服务器 B配置为副站， 另一部分网元将服务器 B配置为主站， 将服务器 A 配置为副站；
所述网元在与其配置为主站的服务器的通讯中断时进行切换，以其配置 为副站的另一服务器作为主站； 在与其配置为主站的 ϋ 务器的通讯恢复后， 再按照所述返回策略将其切换回来；
所述两个服务器彼此相接且配置有主站的返回策略，每个服务器分别连 接到将自己配置为主站的一个接入网元，工作时作为主站管理各自分配的部 分网元， 作为副站监测另一部分网元；
所述两个服务器在发生通讯中断， 收到网元切换的通知时， 变换自己对 于所述网元的主副状态，服务器恢复与将其配置为主站的网元的通讯后，按 照所述返回策略恢复对这些网元的管理。
10、 如权利要求 9所述的系统， 其特征在于， 所述 务器作为主站管理 将其配置为主站的网元时， 采集网元的历史数据，对于所述网元进行相应的 配置查询； 作为副站管理将其配置为副站的网元时， 查询及监控所述网元。
11、 如权利要求 9所述的系统， 其特征在于， 所述两个服务器在配置为 网元的主站和副站正常工作时，进行数据同步， 通过进行数据库同步来保持 主副站之间的数据同步， 其中， 主副站中的历史数据都是全量的。
12、 如权利要求 9所述的系统， 其特征在于， 所述服务器作为主站的返 回策略配置为主站返回方式或非返回方式，
如果是主站返回方式，所述网元在与其配置为主站的服务器的通讯恢复 时， 恢复其配置为主站的l 务器作为主站来管理所述网元， 并切换当前主站 为副站， 同时恢复后的主站服务器同步中断期间的数据；
如果是主站非返回方式，则所述网元在与其配置为主站的服务器的通讯 恢复时， 恢复其配置为主站的服务器作为副站来管理所述网元， 并同步中断 期间的数据， 待当前主站的服务器断开时再以主站形式接入所述网元。
13、 如权利要求 9所述的方法， 其特征在于， 所述网元在检测到与其配 置为主站的服务器通讯中断时，通知其配置为副站的服务器作为主站管理该 网元； 或在网元配置为副站的服务器检测到网元配置为主站的服务器异常 时， 所述副站服务器主动向所述网元请求主站权限， 所述网元根据当前主站 服务器的状态决定是否切换副站为主站管理所述网元。
14、 如权利要求 9所述的系统， 其特征在于， 所述所有网元， 彼此串接 相连， 并且通过首端网元与末端网元与所述两个服务器， 即服务器 A和服 务器 B， 分别相接。
15、 如权利要求 9所述的系统， 其特征在于， 所述两个服务器， 在作为 主站管理分别管理所述网元时， 所管理的将其配置为主站的网元数目均衡， 负载均衡的分别管理相应网元。
PCT/CN2006/001882 2006-07-28 2006-07-28 A distributed master and standby managing method and system based on the network element WO2008014639A1 (en)

Priority Applications (7)

Application Number Priority Date Filing Date Title
ES06761596.3T ES2526809T3 (es) 2006-07-28 2006-07-28 Método y sistema de gestión maestro y de reserva distribuido basado en el elemento de red
CN200680055272.5A CN101485139B (zh) 2006-07-28 2006-07-28 一种基于网元的分布式主备管理的方法及系统
PCT/CN2006/001882 WO2008014639A1 (en) 2006-07-28 2006-07-28 A distributed master and standby managing method and system based on the network element
EP06761596.3A EP2053780B1 (en) 2006-07-28 2006-07-28 A distributed master and standby managing method and system based on the network element
BRPI0621898-9A BRPI0621898A2 (pt) 2006-07-28 2006-07-28 método de administração mestre e auxiliar distribuìda e sistema baseado no elemento de rede
PT67615963T PT2053780E (pt) 2006-07-28 2006-07-28 Um método e sistema de gestão distribuída principal e de reserva com base no elemento de rede
HK09106261.0A HK1128564A1 (en) 2006-07-28 2009-07-13 A distributed master and standby managing method and system based on the network element

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2006/001882 WO2008014639A1 (en) 2006-07-28 2006-07-28 A distributed master and standby managing method and system based on the network element

Publications (1)

Publication Number Publication Date
WO2008014639A1 true WO2008014639A1 (en) 2008-02-07

Family

ID=38996848

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/001882 WO2008014639A1 (en) 2006-07-28 2006-07-28 A distributed master and standby managing method and system based on the network element

Country Status (7)

Country Link
EP (1) EP2053780B1 (zh)
CN (1) CN101485139B (zh)
BR (1) BRPI0621898A2 (zh)
ES (1) ES2526809T3 (zh)
HK (1) HK1128564A1 (zh)
PT (1) PT2053780E (zh)
WO (1) WO2008014639A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102480369A (zh) * 2010-11-23 2012-05-30 中兴通讯股份有限公司 一种网络管理系统及性能采集的方法
US11575741B2 (en) 2021-04-29 2023-02-07 Zoom Video Communications, Inc. System and method for active-active standby in phone system management
US11785077B2 (en) 2021-04-29 2023-10-10 Zoom Video Communications, Inc. Active-active standby for real-time telephony traffic

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101616440B (zh) * 2009-07-31 2012-05-23 华为技术有限公司 多级双机系统及其倒换方法
CN102752325A (zh) * 2011-04-18 2012-10-24 贾金原 基于对等网的大规模虚拟场景的高效下载方法
CN102724234A (zh) * 2011-09-29 2012-10-10 新奥特（北京）视频技术有限公司 一种内外网环境文稿系统与制作系统交互的方法和系统
CN102724061B (zh) * 2012-04-16 2016-02-17 成都广达新网科技股份有限公司 一种网络接口管理方法
CN102857371B (zh) * 2012-08-21 2016-04-20 曙光信息产业(北京)有限公司 一种面向集群系统的动态配置管理方法
CN103118055A (zh) * 2012-10-10 2013-05-22 中兴通讯股份有限公司 一种多媒体接入的方法和设备
CN103200018A (zh) * 2013-04-11 2013-07-10 天脉聚源(北京)传媒科技有限公司 一种信息交互的系统和方法
CN103974022A (zh) * 2014-05-23 2014-08-06 无锡矽太恒科电子有限公司 一种基于sip的楼宇可视对讲的方法及其系统
CN108647113B (zh) * 2018-03-30 2022-02-18 创新先进技术有限公司 一种灾难恢复方法及服务器
CN110266522A (zh) * 2019-05-30 2019-09-20 深圳市中航比特通讯技术有限公司 一种无缝切换管理装置的军用通信设备管理方法
CN112714461B (zh) * 2021-01-29 2022-05-31 四川安迪科技实业有限公司 一种dama卫星网络中心站保护倒换方法
CN113253643A (zh) * 2021-05-12 2021-08-13 南瑞集团有限公司 一种基于d5000主备调系统的主从模式控制方法及管理系统
CN113259185B (zh) * 2021-07-07 2021-10-26 中兴通讯股份有限公司 网管代理以及网元管理平台
CN113766002A (zh) * 2021-07-21 2021-12-07 深圳拓邦股份有限公司 一种局域组网的换电柜数据传输方法及系统

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH01175338A (ja) * 1987-12-28 1989-07-11 Fuji Electric Co Ltd 伝送系の二重化方法
JPH03232397A (ja) * 1990-02-08 1991-10-16 Toshiba Corp バックアップ切替方式
EP0751464A1 (en) 1995-06-26 1997-01-02 Hewlett-Packard Company Storage system
US5696895A (en) 1995-05-19 1997-12-09 Compaq Computer Corporation Fault tolerant multiple network servers
US20040034807A1 (en) * 2002-08-14 2004-02-19 Gnp Computers, Inc. Roving servers in a clustered telecommunication distributed computer system
US20050066216A1 (en) 2003-09-18 2005-03-24 Cisco Technology, Inc. High availability virtual switch
US20060020854A1 (en) * 2004-07-22 2006-01-26 International Business Machines Corporation Method and apparatus for high-speed network adapter failover
WO2006025839A1 (en) 2004-08-30 2006-03-09 Galactic Computing Corporation Bvi/Ibc Maintenance unit architecture for a scalable internet engine

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6687222B1 (en) * 1999-07-02 2004-02-03 Cisco Technology, Inc. Backup service managers for providing reliable network services in a distributed environment
CA2388712A1 (en) * 2000-06-30 2002-01-10 Internap Network Services Corporation Distributed network management system and method
JP4459018B2 (ja) * 2004-10-28 2010-04-28 富士通株式会社 ノード装置

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH01175338A (ja) * 1987-12-28 1989-07-11 Fuji Electric Co Ltd 伝送系の二重化方法
JPH03232397A (ja) * 1990-02-08 1991-10-16 Toshiba Corp バックアップ切替方式
US5696895A (en) 1995-05-19 1997-12-09 Compaq Computer Corporation Fault tolerant multiple network servers
EP0751464A1 (en) 1995-06-26 1997-01-02 Hewlett-Packard Company Storage system
US20040034807A1 (en) * 2002-08-14 2004-02-19 Gnp Computers, Inc. Roving servers in a clustered telecommunication distributed computer system
US20050066216A1 (en) 2003-09-18 2005-03-24 Cisco Technology, Inc. High availability virtual switch
US20060020854A1 (en) * 2004-07-22 2006-01-26 International Business Machines Corporation Method and apparatus for high-speed network adapter failover
WO2006025839A1 (en) 2004-08-30 2006-03-09 Galactic Computing Corporation Bvi/Ibc Maintenance unit architecture for a scalable internet engine

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2053780A4

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102480369A (zh) * 2010-11-23 2012-05-30 中兴通讯股份有限公司 一种网络管理系统及性能采集的方法
US11575741B2 (en) 2021-04-29 2023-02-07 Zoom Video Communications, Inc. System and method for active-active standby in phone system management
US11785077B2 (en) 2021-04-29 2023-10-10 Zoom Video Communications, Inc. Active-active standby for real-time telephony traffic
US11985187B2 (en) 2021-04-29 2024-05-14 Zoom Video Communications, Inc. Phone system failover management

Also Published As

Publication number Publication date
CN101485139A (zh) 2009-07-15
EP2053780A1 (en) 2009-04-29
ES2526809T3 (es) 2015-01-15
CN101485139B (zh) 2011-09-14
HK1128564A1 (en) 2009-10-30
EP2053780B1 (en) 2014-10-08
BRPI0621898A2 (pt) 2012-10-16
EP2053780A4 (en) 2011-04-13
PT2053780E (pt) 2015-01-05

Similar Documents

Publication Publication Date Title
WO2008014639A1 (en) A distributed master and standby managing method and system based on the network element
US11075795B2 (en) Arbitration method, apparatus, and system used in active-active data centers
KR100491541B1 (ko) 네트웍 환경에서의 컨텐츠 동기화 시스템 및 동기화 방법
CN107465721B (zh) 基于双活架构的全局负载均衡方法和系统及调度服务器
EP1982447B1 (en) System and method for detecting and recovering from virtual switch link failures
JP5743809B2 (ja) 網管理システムおよび網管理方法
WO2018171565A1 (zh) 容灾部署方法、装置及系统
WO2016058307A1 (zh) 资源的故障处理方法及装置
US20030018927A1 (en) High-availability cluster virtual server system
JP2005521334A (ja) ネットワーク管理システム
CN112181660A (zh) 一种基于服务器集群的高可用方法
WO2012145963A1 (zh) 数据管理系统及方法
WO2012083669A1 (zh) 基于接入网关的主备用设备切换方法和装置
WO2013113228A1 (zh) 网络设备冗余备份的方法、路由设备及系统
CN111371625A (zh) 一种双机热备的实现方法
US8935564B2 (en) Method for backing up user information and apparatus in standby service node for backing up user information
EP1712067B1 (en) A method, apparatus and system of organizing servers
CN103297279A (zh) 一种多软件进程系统上软件控制的主备单盘倒换方法
KR101358995B1 (ko) 고가용성 관리 방법 및 시스템
CN102255741B (zh) 用户业务信息备份方法和装置
CN101262400A (zh) 一种桥模式弹性分组环冗余保护的方法和系统
CN115408199A (zh) 一种边缘计算节点的容灾处理方法及装置
WO2005055517A1 (fr) Appareil de realisation de la recuperation d'un systeme allopatrique de commutateur logiciel utilisant un reseau a paquets
WO2012009914A1 (zh) 保护倒换方法及系统
CN115037674B (zh) 一种中央控制系统单机及多设备冗余备份方法

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680055272.5

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 06761596

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2006761596

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: RU

REG Reference to national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1128564

Country of ref document: HK

ENP Entry into the national phase

Ref document number: PI0621898

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20090123