WO2016065925A1 - Dispositif et procédé de remplacement de contrôleur - Google Patents

Dispositif et procédé de remplacement de contrôleur Download PDF

Info

Publication number
WO2016065925A1
WO2016065925A1 PCT/CN2015/083594 CN2015083594W WO2016065925A1 WO 2016065925 A1 WO2016065925 A1 WO 2016065925A1 CN 2015083594 W CN2015083594 W CN 2015083594W WO 2016065925 A1 WO2016065925 A1 WO 2016065925A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain controller
single domain
controller
message
dcn
Prior art date
Application number
PCT/CN2015/083594
Other languages
English (en)
Chinese (zh)
Inventor
朱玉婷
蒋宁宁
吕文祥
陈倩雪
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016065925A1 publication Critical patent/WO2016065925A1/fr

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • the present invention relates to the field of communications, and in particular to a controller replacement method and apparatus.
  • SDN Software Defined Network
  • Controllor The centralized and unified controller implements the management of the network in the scope, solves the problem that the large number of forwarding devices in the network are distributed and independently operated, and eliminates the underlying network differences.
  • the problem with centralized management is that when any controller fails, it may cause a whole network crash.
  • the backup of the controller is often implemented by the controller in the active/standby mode.
  • the reliability and resource usage of this method are not high.
  • some methods have been derived to improve system reliability.
  • the controller is faulty, only the standby controller replacement at the same level can be performed, and there is no related method for the multi-domain controller failure processing.
  • the invention provides a controller replacement method and device, which at least solves the problem that the backup controller can be replaced at the same level when the fault of the controller is solved in the related art, resulting in a problem that the resource use efficiency is not high.
  • a controller replacement method including: transmitting a first message to a first single domain controller; determining whether the first single domain controller is received according to a first predetermined time The response message returned by the first message; if the determination result is no, the second single domain controller in the primary multi-domain controller is replaced with the replacement process of the first single domain controller.
  • performing the replacement process of the second single domain controller in the primary multi-domain controller to replace the first single domain controller includes: performing a query for performing fault query on the first single domain controller The request is sent to the data control network DCN; the processing of replacing the first single domain controller is performed in accordance with the received message returned by the DCN.
  • the processing of replacing the first single domain controller according to the received message returned by the DCN includes: when the received message returned by the DCN is a normal response of the first single domain controller And replacing the first single domain controller when the message is received; and replacing the first single domain controller when the received message returned by the DCN is the first single domain controller fault response message.
  • the replacing the first single domain controller includes: configuring an attribute parameter of the second single domain controller to be the same parameter as an attribute parameter of the first single domain controller; The second single domain controller after the attribute parameter configuration; connecting the activated second single domain controller with the DCN.
  • a controller replacement method including: determining whether a first message sent by a primary multi-domain controller is received within a second predetermined time; and if the determination result is negative, performing Replace the processing of the primary multi-domain controller.
  • performing the process of replacing the primary multi-domain controller includes: sending a second message to the standby multi-domain controller with the highest priority, wherein the second message is used to indicate the standby multi-domain The controller is converted to a primary multi-domain controller.
  • a controller replacement apparatus including: a sending module, configured to send a first message to a first single domain controller; and a first determining module configured to determine that in a first predetermined time Whether the response message returned by the first single domain controller according to the first message is received; the first processing module is configured to execute the second single domain in the primary multi-domain controller if the determination result is negative
  • the controller replaces the replacement process of the first single domain controller.
  • the first processing module includes: a first sending unit, configured to send a query request for performing a fault query on the first single domain controller to the data control network DCN; and the processing unit is configured to The process of replacing the first single domain controller is performed in accordance with the received message returned by the DCN.
  • the processing unit includes: abandoning the subunit, and setting to abandon and replace the first single domain control when the received message returned by the DCN is the first single domain controller normal response message And a replacement subunit configured to replace the first single domain controller when the received message returned by the DCN is a first single domain controller failure response message.
  • the replacing subunit includes: configuring a secondary subunit, configured to configure an attribute parameter of the second single domain controller to be the same parameter as an attribute parameter of the first single domain controller And starting the second sub-unit, configured to start the second single-domain controller after the attribute parameter configuration is performed; and connecting the second sub-unit, configured to connect the activated second single-domain controller with the DCN.
  • a controller replacement apparatus including: a second determining module, configured to determine whether a first message sent by a primary multi-domain controller is received within a second predetermined time; The module is set to perform a process of replacing the primary multi-domain controller in a case where the determination result is negative.
  • the second processing module includes: a second sending unit, configured to send a second message to the standby multi-domain controller with the highest priority, wherein the second message is used to indicate the standby Multi-domain controllers are converted to primary multi-domain controllers.
  • the first message is sent to the first single domain controller, and it is determined whether the response message returned by the first single domain controller according to the first message is received in the first predetermined time; If the result is no, the second single domain controller in the primary multi-domain controller is replaced with the replacement processing of the first single domain controller, and the related technology exists to solve the fault of the controller.
  • the replacement of the standby controller at the same level can lead to the problem that the resource usage efficiency is not high, thereby achieving the effect of improving the resource utilization rate and improving the stability of the system.
  • FIG. 1 is a flow chart 1 of a controller replacement method according to an embodiment of the present invention.
  • FIG. 2 is a second flowchart of a controller replacement method according to an embodiment of the present invention.
  • FIG. 3 is a structural block diagram 1 of a controller replacement device according to an embodiment of the present invention.
  • FIG. 4 is a block diagram showing the structure of a first processing module 36 in a controller replacement device according to an embodiment of the present invention
  • FIG. 5 is a structural block diagram of a processing unit 44 in a controller replacement device according to an embodiment of the present invention.
  • FIG. 6 is a block diagram showing the structure of a replacement subunit 54 in a controller replacement device according to an embodiment of the present invention
  • FIG. 7 is a structural block diagram 2 of a controller replacement device according to an embodiment of the present invention.
  • FIG. 8 is a structural block diagram of a second processing module 74 in a controller replacement device according to an embodiment of the present invention.
  • FIG. 9a is a general architectural diagram of an SDN according to an embodiment of the present invention.
  • FIG. 9b is a SDN scene diagram according to an embodiment of the present invention.
  • FIG. 10 is a flow chart of a process controller failure in accordance with an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a multi-domain controller address Sub-TLV format according to an embodiment of the present invention.
  • FIG. 12 is a schematic diagram of a single domain controller address Sub-TLV format according to an embodiment of the present invention.
  • FIG. 13 is a structural diagram of a multi-domain controller according to an embodiment of the present invention.
  • FIG. 1 is a flowchart 1 of a controller replacement method according to an embodiment of the present invention. As shown in FIG. 1, the process includes the following steps:
  • Step S102 sending a first message to the first single domain controller
  • Step S104 determining whether a response message returned by the first single domain controller according to the first message is received in the first predetermined time
  • Step S106 if the determination result is no, the replacement process of the second single domain controller in the primary multi-domain controller is replaced by the first single domain controller.
  • the periodic transmission may be performed at the same time interval.
  • the first message may also be sent according to a specific time interval (each time interval may be different), and the single domain controller replaced by the multi-domain controller is implemented, and the solution in the related art is solved.
  • performing the replacement process of the second single domain controller in the primary multi-domain controller to replace the first single domain controller includes: a query request for performing a fault query on the first single domain controller The data is sent to the data control network DCN; and the process of replacing the first single domain controller is performed according to the received message returned by the DCN.
  • the performing the process of replacing the first single domain controller according to the received message returned by the DCN comprises: discarding the replacement when the received message returned by the DCN is the first single domain controller normal response message
  • the first single domain controller replaces the first single domain controller when the received message returned by the DCN is the first single domain controller failure response message.
  • replacing the first single domain controller includes: configuring an attribute parameter of the second single domain controller to be the same parameter as an attribute parameter of the first single domain controller; and performing attribute parameter configuration The second single domain controller is followed; the second single domain controller that is started is connected to the DCN.
  • FIG. 2 is a second flowchart of a controller replacement method according to an embodiment of the present invention. As shown in FIG. 2, the process includes the following steps:
  • Step S202 determining whether the first message sent by the primary multi-domain controller is received in the second predetermined time
  • step S204 if the determination result is no, the process of replacing the primary multi-domain controller is performed.
  • the second predetermined time may be the same as or different from the first predetermined time.
  • performing the process of replacing the primary multi-domain controller includes transmitting a second message to the alternate multi-domain controller having the highest priority, wherein the second message is used to indicate alternate multi-domain controller conversion The main multi-domain controller.
  • a controller replacement device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and will not be described again.
  • the term “module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 3 is a structural block diagram of a controller replacement device according to an embodiment of the present invention. As shown in FIG. 3, the device includes a transmitting module 32, a first determining module 34, and a first processing module 36. .
  • the sending module 32 is configured to send the first message to the first single domain controller
  • the first determining module 34 is connected to the sending module 32, and is configured to determine whether the first single domain controller is received according to the first predetermined time.
  • the first processing module 36 is connected to the first determining module 34, and is set to determine If the result is no, the second single domain controller in the primary multi-domain controller is replaced with the replacement process of the first single domain controller.
  • FIG. 4 is a structural block diagram of a first processing module 36 in a controller replacement device according to an embodiment of the present invention. As shown in FIG. 4, the first processing module 36 includes a first transmitting unit 42 and a processing unit 44. The first processing module 36 is described.
  • the first sending unit 42 is configured to send a query request for performing fault query on the first single domain controller to the data control network DCN; and the processing unit 44 is connected to the first sending unit 42 to be set according to the received The message returned by the DCN performs the process of replacing the first single domain controller.
  • FIG. 5 is a structural block diagram of a processing unit 44 in a controller replacement device according to an embodiment of the present invention. As shown in FIG. 5, the processing unit 44 includes a discarding subunit 52 or a replacement subunit 54, and the processing unit 44 is performed below. Description.
  • the abandoning subunit 52 is configured to abandon the replacement of the first single domain controller when the received message returned by the DCN is the first single domain controller normal response message; the replacement subunit 54 is set to be returned by the DCN when received The message replaces the first single domain controller when the first single domain controller failure response message is received.
  • FIG. 6 is a structural block diagram of a replacement subunit 54 in a controller replacement device according to an embodiment of the present invention.
  • the replacement subunit 54 includes a configuration sub subunit 62, a startup sub subunit 64, and a connection sub subunit. 66.
  • the replacement subunit 54 will be described below.
  • the configuration sub-subunit 62 is configured to configure the attribute parameter of the second single domain controller to be the same parameter as the attribute parameter of the first single domain controller; to activate the secondary sub-unit 64, to connect to the configuration sub-sub-unit 62, and set
  • the second single domain controller is configured to start the attribute parameter configuration;
  • the connection secondary subunit 66 is connected to the startup secondary subunit, and is configured to connect the activated second single domain controller with the DCN.
  • FIG. 7 is a block diagram showing the structure of a controller replacing apparatus according to an embodiment of the present invention. As shown in FIG. 7, the apparatus includes a second judging module 72 and a second processing module 74, which will be described below.
  • the second determining module 72 is configured to determine whether the first message sent by the primary multi-domain controller is received in the second predetermined time; the second processing module 74 is connected to the second determining module 72, and is configured to Otherwise, the process of replacing the primary multi-domain controller is performed.
  • FIG. 8 is a structural block diagram of a second processing module 74 in the controller replacement device according to an embodiment of the present invention. As shown in FIG. 8, the second processing module 74 includes a second transmitting unit 82, which will be described below.
  • the second sending unit 82 is configured to send a second message to the standby multi-domain controller with the highest priority, wherein the second message is used to indicate that the standby multi-domain controller is converted into the primary multi-domain controller.
  • the present invention will be described below by taking the processing of controller failure in SDN as an example.
  • a processing method when the controller fails in a multi-domain scenario is provided.
  • FIG. 9a is a general architectural diagram of an SDN according to an embodiment of the present invention.
  • a multi-domain controller two single-domain controllers, and a DCN are included.
  • the nodes in the DCN are omitted, and according to the content of the invention, as shown in FIG. 9b, FIG. 9b is an SDN scene diagram according to an embodiment of the present invention.
  • the primary multi-domain controller can only have one in the system, and the main functions include path calculation, connection management, protection recovery, and transmission of resources across the domain connection.
  • the standby multi-domain controller can only accept the information of the primary multi-domain controller.
  • the primary multi-domain controller When the primary multi-domain controller can work normally, it cannot control the single-domain controller. Specifies to set up one multi-domain controller as the primary multi-domain controller and the other as the alternate multi-domain controller.
  • the alternate multi-domain controller also sets different priorities to identify which alternate multi-domain controller is set as the primary multi-domain controller when the primary multi-domain controller fails.
  • a single-domain controller can have many stations in the system.
  • the main functions are intra-domain connection path calculation, establishment deletion recovery, network topology management, and top-level information of the intra-domain transmission resources provided to the upper layer.
  • multiple multi-domain controllers may be configured to interface with a single domain controller and a data control network (DCN); wherein one of the plurality of multi-domain controllers is set The main multi-domain controller, the other is the standby multi-domain controller; the main multi-domain controller communicates with the single-domain controller in real time, if it is normal, the current communication is maintained, and the main multi-domain controller and the single-domain controller need to communicate abnormally. Perform an operation to replace a single domain controller or replace a primary multi-domain controller.
  • DCN data control network
  • FIG. 10 is a flowchart of processing a controller failure according to an embodiment of the present invention. As shown in FIG. 10, the method includes the following steps:
  • step S1002 multiple multi-domain controllers are deployed, and multiple multi-domain controllers deployed are multiple peer devices.
  • step S1004 one of the plurality of peer multi-domain controllers is configured as the primary multi-domain controller, and the other one is the standby multi-domain controller.
  • FIG. 11 is a schematic diagram of a multi-domain controller address Sub-TLV format according to an embodiment of the present invention.
  • the value of 1 indicates the primary multi-domain controller
  • the Type 2 indicates the standby multi-domain controller
  • the priority indicates the priority of the standby multi-domain controller (the primary multi-domain controller has priority 1).
  • Address-type indicates the IP address type, 1 is IPV4 type, 2 is IPV6 type, and Controllor IP Address is the IP address of the controller.
  • Step S1006 configuring basic information of the controller and the controller.
  • the single domain controller address and the domain ID are configured.
  • the format of the single domain controller is as shown in FIG. 12 .
  • FIG. 12 is a schematic diagram of a single domain controller address Sub-TLV format according to an embodiment of the present invention.
  • Single-domain controller, address-type indicates the IP address type, 1 is IPV4 type, 2 is IPV6 type, and Controllor IP Address is the IP address of the controller.
  • the Domain ID is the configured domain ID and is used to identify the domain to which the controller acts.
  • Step S1008 determining whether the primary multi-domain controller and the single domain controller communicate normally, wherein the primary multi-domain controller periodically sends a hello message (same as the first message) to the single domain controller to determine whether If the result of the determination is YES, the process goes to step S1010. If the result of the determination is NO, the process goes to step S1012.
  • step S1010 normal communication is maintained.
  • step S1012 it is determined whether the primary multi-domain controller is faulty or the single-domain controller is faulty.
  • the process goes to step S1014.
  • the process goes to Step S1022, wherein when the primary multi-domain controller fails to receive the response message of the single domain controller, it is determined that the single domain controller is faulty.
  • step S1014 the primary multi-domain controller performs an operation instead of the single domain controller.
  • step S1016 the primary multi-domain controller initiates a request message to the DCN request instead of the single domain controller.
  • Step S1018 The DCN sends a message to the single domain controller to query whether the single domain controller sends a fault, receives a corresponding message within the set time, and sends a response message (same as the above response message) to the primary multi-domain controller.
  • the single-domain controller sends the hello message to the multi-domain controller to maintain the original normal communication; the corresponding message is not received within the set time, and the response message (the same response message as above) is sent to the primary multi-domain controller. Close the interface information with the single domain controller.
  • step S1020 the primary multi-domain controller replaces the single domain controller.
  • FIG. 13 is a structural diagram of a multi-domain controller according to an embodiment of the present invention.
  • an internal single-domain controller is added to a multi-domain controller, and when a single-domain controller has a problem, it may temporarily Instead of a single domain controller.
  • the internal single-domain controller also needs to configure basic properties, except that the Domain ID is set to 0, indicating that it is a single-domain controller belonging to a multi-domain controller.
  • the primary multi-domain controller is to replace the failed single-domain controller, Inside the main multi-domain controller, the single-domain controller of the main domain controller is required to replace the faulty single-domain controller through the flowmod message.
  • the forp_port structure of the message needs to be extended by work_status (this indicates whether the internal single-domain controller is started, which is 1 Start, 0 for no use) and domain_ID (for domains that need to be replaced).
  • work_status this indicates whether the internal single-domain controller is started, which is 1 Start, 0 for no use
  • domain_ID for domains that need to be replaced
  • the internal single-domain controller When the internal single-domain controller receives a work_status of 1, it modifies its own Domain ID according to the domain_ID, and controls the DCN instead of the single-domain controller that is faulty. After the original single-domain controller fails, it actively sends a message to the primary multi-domain controller, indicating that it has been restored. Then the primary multi-domain controller sends a message to the internal single-domain controller. Through the flowmod message, the work_status is 0 and the domain_ID is 0, and the attributes of the internal single-domain controller are modified. The internal single domain controller closes the interface to the DCN.
  • step S1022 the standby multi-domain controller replaces the original primary multi-domain controller.
  • step S1024 the single domain controller sends a message to the alternate multi-domain controller to request to replace the primary multi-domain controller.
  • the single domain controller does not receive the hello message in the corresponding time, and actively sends a hello message to the standby multi-domain controller.
  • step S1026 the standby multi-domain controller becomes the primary multi-domain controller.
  • the standby multi-domain controller with the highest priority receives the message, and the standby multi-domain controller turns to the primary multi-domain controller, the Type is 1, and then The hello message is sent periodically to the single domain controller.
  • the new primary multi-domain controller sends messages to other backup multi-domain controllers to modify the priority. After the previous primary multi-domain controller fails, modify the Type and priority to become the standby multi-domain controller.
  • modules or steps of the embodiments of the present invention can be implemented by a general computing device, which can be concentrated on a single computing device or distributed in multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from The steps shown or described are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
  • the above-mentioned embodiments and the preferred embodiments solve the problem that the replacement of the standby controller at the same level can be performed only when the controller is faulty, which causes the resource use efficiency to be low. It has achieved the effect of improving resource utilization and improving system stability.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un dispositif et un procédé de remplacement de contrôleur. Le procédé comprend les étapes consistant : à envoyer un premier message à un premier contrôleur à domaine unique ; à déterminer si un message de réponse renvoyé par le premier contrôleur à domaine unique en fonction du premier message est reçu dans une première période de temps prédéterminée ; et si ce n'est pas le cas, à remplacer le premier contrôleur à domaine unique par un second contrôleur à domaine unique dans des principaux contrôleurs à multidomaine. La présente invention résout le problème dans la technique associée de faible taux d'utilisation de ressources du fait que le remplacement par un contrôleur de réserve ne peut être effectué au même niveau seulement lorsque la défaillance d'un contrôleur est éliminée, et par conséquent, le taux d'utilisation de ressources est augmenté et la stabilité du système est améliorée.
PCT/CN2015/083594 2014-10-29 2015-07-08 Dispositif et procédé de remplacement de contrôleur WO2016065925A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410592321.5 2014-10-29
CN201410592321.5A CN105634765A (zh) 2014-10-29 2014-10-29 控制器替换方法及装置

Publications (1)

Publication Number Publication Date
WO2016065925A1 true WO2016065925A1 (fr) 2016-05-06

Family

ID=55856540

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/083594 WO2016065925A1 (fr) 2014-10-29 2015-07-08 Dispositif et procédé de remplacement de contrôleur

Country Status (2)

Country Link
CN (1) CN105634765A (fr)
WO (1) WO2016065925A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106792843B (zh) * 2016-11-18 2021-04-16 新华三技术有限公司 一种设备管理方法及装置
CN108574627B (zh) * 2017-03-08 2021-08-31 国网信息通信产业集团有限公司 一种sdn网络多控制域协同管理方法和系统
CN113055195B (zh) * 2019-12-26 2022-11-29 中移雄安信息通信科技有限公司 基于sdon的多域控制器集群和sdon系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130346530A1 (en) * 2010-12-20 2013-12-26 Schneider Electric Automation Gmbh Communication system, method for operating such a communication system, and communication module
CN103607310A (zh) * 2013-11-29 2014-02-26 华为技术有限公司 一种异地容灾的仲裁方法
CN103618621A (zh) * 2013-11-21 2014-03-05 华为技术有限公司 一种软件定义网络sdn的自动配置方法、设备及系统
CN103795530A (zh) * 2012-10-31 2014-05-14 华为技术有限公司 一种跨域控制器认证的方法、装置及主机

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130346530A1 (en) * 2010-12-20 2013-12-26 Schneider Electric Automation Gmbh Communication system, method for operating such a communication system, and communication module
CN103795530A (zh) * 2012-10-31 2014-05-14 华为技术有限公司 一种跨域控制器认证的方法、装置及主机
CN103618621A (zh) * 2013-11-21 2014-03-05 华为技术有限公司 一种软件定义网络sdn的自动配置方法、设备及系统
CN103607310A (zh) * 2013-11-29 2014-02-26 华为技术有限公司 一种异地容灾的仲裁方法

Also Published As

Publication number Publication date
CN105634765A (zh) 2016-06-01

Similar Documents

Publication Publication Date Title
EP3016316B1 (fr) Procédé et appareil de commande de réseau
EP2878105B1 (fr) Système et procédé utilisant la suppression d'accueil rsvp pour le redémarrage progressif de voisins compétents
CN102035676B (zh) 基于arp协议交互的链路故障检测与恢复的方法和设备
EP2985952B1 (fr) Procédé et dispositif de protection de la fiabilité d'un service, et système de virtualisation de réseau
WO2016165463A1 (fr) Procédé de compte rendu de défaillance de liaison basé sur un réseau défini par logiciel et dispositif de réacheminement
WO2018188425A1 (fr) Procédé et appareil d'accès hybride à simple et double anneau vxlan, dispositif pe et support de stockage
WO2015117385A1 (fr) Procédé, dispositif et système de traitement de virtualisation d'un réseau
US10819659B2 (en) Direct replying actions in SDN switches
JP2022533238A (ja) Tsn内のコントローラ間の通信のための方法、装置、およびシステム
US20150304218A1 (en) Control Channel Establishing Method, Forwarding Point, and Controller
US11616724B2 (en) Packet transmission method and apparatus
US10516599B1 (en) Link priority for loop-protect
CN105656645A (zh) 堆叠系统的故障处理的决策方法和装置
CN107645394B (zh) 一种sdn网络中的交换机配置方法
US9497104B2 (en) Dynamic update of routing metric for use in routing return traffic in FHRP environment
US9912592B2 (en) Troubleshooting openflow networks
WO2016065925A1 (fr) Dispositif et procédé de remplacement de contrôleur
WO2019157871A1 (fr) Réseau de liaison terrestre sans fil, procédé et appareil de communication
US11095514B2 (en) System and method for propagating anima network objective changes
WO2009062351A1 (fr) Procédé permettant de fusionner des systèmes d'empilement
US11870646B2 (en) Fabric availability and synchronization
US20170155543A1 (en) Control apparatus, communication system, and control method
US9667554B2 (en) DS domain generating method, device and system
CN105553864B (zh) 降低lmp中消息数量的方法及装置
US8867405B2 (en) Voice service discovery

Legal Events

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

Ref document number: 15855036

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15855036

Country of ref document: EP

Kind code of ref document: A1