CN105812161A - Controller fault backup method and system - Google Patents

Controller fault backup method and system Download PDF

Info

Publication number
CN105812161A
CN105812161A CN201410850673.6A CN201410850673A CN105812161A CN 105812161 A CN105812161 A CN 105812161A CN 201410850673 A CN201410850673 A CN 201410850673A CN 105812161 A CN105812161 A CN 105812161A
Authority
CN
China
Prior art keywords
controller
normal
failed
spare
processing capabilities
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
Application number
CN201410850673.6A
Other languages
Chinese (zh)
Other versions
CN105812161B (en
Inventor
王占京
霍晓莉
荆瑞泉
李俊杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
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 China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN201410850673.6A priority Critical patent/CN105812161B/en
Publication of CN105812161A publication Critical patent/CN105812161A/en
Application granted granted Critical
Publication of CN105812161B publication Critical patent/CN105812161B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Hardware Redundancy (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses a controller fault backup method and a system. The method comprises steps that when a main controller and standby controllers are in a normal state, priorities of fault controllers are ordered from large to small, and the present processing capability of each fault controller is approved; redundant processing capability of the normal controllers are ordered from large to small, and the ordered fault controllers are sequentially replaced by the ordered normal controllers. The method is advantaged in that high-level network business response can be guaranteed preferably, and network safety and reliability are improved.

Description

A kind of controller failure backup method and system
Technical field
The present invention relates to control field, particularly relate to a kind of controller failure backup method and system.
Background technology
SDN controller is the core system assembly of SDN, once go wrong, failing to process in time, then can timely respond to new business demand, cause and block up, or even paralysis.Current solution is to set up active and standby controller at father field, and is realized the backup protection of antithetical phrase domain controller by father field controller, but this kind of mode there is also problems with:
The active and standby controller of father field is generally artificially specified in advance, but when the active and standby controller simultaneous faults specified, then network cannot be tackled automatically, causes network paralysis；
Further, since controller performance restriction, not all controller can act as backup, rigid backup, not only can reduce the responding ability of business in original control subdomain, simultaneously Business Processing in fault restriction subdomain；
When fault coverage is bigger, do not pay the utmost attention to the response of higher ranked business, reduce client perception.
Summary of the invention
When the technical problem to be solved in the present invention is existing controller fault, internet security and poor reliability.
According to an aspect of the present invention, it is proposed to a kind of controller failure backup method, including:
When master controller and spare controller are normal, the priority of failed controller is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller；
The redundant processing capabilities of normal controller is ranked up from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.
Further, judge the failed controller the current processing capabilities whether maximum normal controller disposal ability of redundant processing capabilities is the highest more than priority, if, the maximum normal controller of described redundant processing capabilities takes over the switch of the highest failed controller of described priority, the failed controller back-up processing that described priority is the highest terminates, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller；
Otherwise, the maximum normal controller of described redundant processing capabilities takes over the part switch of the highest failed controller of described priority, the remaining switch of the failed controller that the second largest normal controller adapter priority of redundant processing capabilities is the highest, the like, until the switch having taken over the highest failed controller of priority completes back-up processing, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
Further, if the minimum normal controller disposal ability of redundant processing capabilities is less than failed controller current processing capabilities, the part switch of described normal controller taking over fault controller, back-up processing terminates.
Further, judge master controller whether fault, if, then judge that whether spare controller is normal, if so, then described spare controller is revised as master controller, controller maximum for redundant processing capabilities in other normal controller is revised as spare controller, otherwise, controller maximum for redundant processing capabilities in other normal controller being revised as master controller, the second largest controller of redundant processing capabilities is revised as spare controller；
If described master controller is normal, but spare controller fault, then the controller that in other normal controller, redundant processing capabilities is maximum is revised as spare controller.
Further, master controller periodic maintenance regular maintenance information table, and described regular maintenance information table is issued other each controller, the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller；
Wherein, the content of described regular maintenance information table includes controller type, state, address information, priority, appraises and decides disposal ability, current processing capabilities, affiliated exchanger information and/or switch type.
Further, when master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, the exchanger information received is mated by master controller with the exchanger information belonging to regular maintenance information table middle controller, judge failed controller, or, master controller is not connected to determine this controller failure by judgement and this controller；
When master controller fault, spare controller is normal, belonging to master controller, service request is sent to spare controller by exchange opportunity, described spare controller is according to the exchanger information received, master controller fault is judged by exchanger information belonging to each controller in regular maintenance information table, or, spare controller is by judging that the annexation with each other controller determines master controller fault；Or
Other controller when not receiving master controller and spare controller message, being then mutually attached application, if connecting normal, then can confirm that master controller and spare controller fault according to regular maintenance information table.
Further, when master controller failure judgement controller recovers normal, then this failed controller information is handed down to each controller, each controller is by checking oneself internal trustship information, determine whether this controller service, if it has, then send information to this controller, and reconstruct all information.
According to a further aspect in the invention, it is also proposed that a kind of controller failure backup method, including:
Judge master controller whether fault, if, then judge that whether spare controller is normal, if, then described spare controller is revised as master controller, controller maximum for redundant processing capabilities in other normal controller is revised as spare controller, otherwise, controller maximum for redundant processing capabilities in other normal controller is revised as master controller, and the second largest controller of redundant processing capabilities is revised as spare controller；
If described master controller is normal, but spare controller fault, then the controller that in other normal controller, redundant processing capabilities is maximum is revised as spare controller.
Further, when master controller and spare controller are normal, the priority of failed controller is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller；
The redundant processing capabilities of normal controller is ranked up from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.
Further, judge the failed controller the current processing capabilities whether maximum normal controller disposal ability of redundant processing capabilities is the highest more than priority, if, the maximum normal controller of described redundant processing capabilities takes over the switch of the highest failed controller of described priority, the failed controller back-up processing that described priority is the highest terminates, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller；
Otherwise, the maximum normal controller of described redundant processing capabilities takes over the part switch of the highest failed controller of described priority, the remaining switch of the failed controller that the second largest normal controller adapter priority of redundant processing capabilities is the highest, the like, until the switch having taken over the highest failed controller of priority completes back-up processing, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
Further, if the minimum normal controller disposal ability of redundant processing capabilities is less than failed controller current processing capabilities, the part switch of described normal controller taking over fault controller, back-up processing terminates.
Further, master controller periodic maintenance regular maintenance information table, and described regular maintenance information table is issued other each controller, the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller；
Wherein, the content of described regular maintenance information table includes controller type, state, address information, priority, appraises and decides disposal ability, current processing capabilities, affiliated exchanger information and/or switch type.
Further, when master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, the exchanger information received is mated by master controller with the exchanger information belonging to regular maintenance information table middle controller, judge failed controller, or, master controller is not connected to determine this controller failure by judgement and this controller；
When master controller fault, spare controller is normal, belonging to master controller, service request is sent to spare controller by exchange opportunity, described spare controller is according to the exchanger information received, master controller fault is judged by exchanger information belonging to each controller in regular maintenance information table, or, spare controller is by judging that the annexation with each other controller determines master controller fault；Or
Other controller when not receiving master controller and spare controller message, being then mutually attached application, if connecting normal, then can confirm that master controller and spare controller fault according to regular maintenance information table.
Further, when master controller failure judgement controller recovers normal, then this failed controller information is handed down to each controller, each controller is by checking oneself internal trustship information, determine whether this controller service, if it has, then send information to this controller, and reconstruct all information.
According to a further aspect in the invention, it is also proposed that a kind of controller failure standby system, including:
Fault recovery prioritization module, for when master controller and spare controller are normal, being ranked up the priority of failed controller from big to small, and appraise and decide the current processing capabilities of each failed controller；
Fault processing module, for being ranked up the redundant processing capabilities of normal controller from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.
Further, the failed controller current processing capabilities whether described fault processing module is the highest more than priority for judging the maximum normal controller disposal ability of redundant processing capabilities, if, the maximum normal controller of described redundant processing capabilities takes over the switch of the highest failed controller of described priority, the failed controller back-up processing that described priority is the highest terminates, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller；
Otherwise, the maximum normal controller of described redundant processing capabilities takes over the part switch of the highest failed controller of described priority, the remaining switch of the failed controller that the second largest normal controller adapter priority of redundant processing capabilities is the highest, the like, until the switch having taken over the highest failed controller of priority completes back-up processing, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
Further, if described fault processing module is used for the minimum normal controller disposal ability of redundant processing capabilities less than failed controller current processing capabilities, the part switch of described normal controller taking over fault controller, back-up processing terminates.
Further, breakdown judge module, it is used for judging master controller and/or spare controller whether fault；
Failure analysis module, if spare controller is normal for master controller fault, is then revised as described spare controller master controller, controller maximum for redundant processing capabilities in other normal controller is revised as spare controller；If master controller and spare controller all faults, then controller maximum for redundant processing capabilities in other normal controller being revised as master controller, the second largest controller of redundant processing capabilities is revised as spare controller；If described master controller is normal, but spare controller fault, then the controller that in other normal controller, redundant processing capabilities is maximum is revised as spare controller.
Further, maintenance of information module, for master controller periodic maintenance regular maintenance information table, and described regular maintenance information table being issued other each controller, the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller；
Wherein, the content of described regular maintenance information table includes controller type, state, address information, priority, appraises and decides disposal ability, current processing capabilities, affiliated exchanger information and/or switch type.
Further, described breakdown judge module is for when master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, the exchanger information received is mated by master controller with the exchanger information belonging to regular maintenance information table middle controller, judge failed controller, or, master controller is not connected to determine this controller failure by judgement and this controller；
When master controller fault, spare controller is normal, belonging to master controller, service request is sent to spare controller by exchange opportunity, described spare controller is according to the exchanger information received, master controller fault is judged by exchanger information belonging to each controller in regular maintenance information table, or, spare controller is by judging that the annexation with each other controller determines master controller fault；Or
Other controller when not receiving master controller and spare controller message, being then mutually attached application, if connecting normal, then can confirm that master controller and spare controller fault according to regular maintenance information table.
Further, Failure Recovery Module, for recovering normal when master controller failure judgement controller, then this failed controller information is handed down to each controller, each controller is by checking oneself internal trustship information, it may be judged whether have this controller service, if had, then send information to this controller, and reconstruct all information.
According to a further aspect in the invention, it is also proposed that a kind of controller failure standby system, including:
Breakdown judge module, is used for judging master controller and/or spare controller whether fault；
Failure analysis module, if spare controller is normal for master controller fault, is then revised as described spare controller master controller, controller maximum for redundant processing capabilities in other normal controller is revised as spare controller；If master controller and spare controller all faults, then controller maximum for redundant processing capabilities in other normal controller being revised as master controller, the second largest controller of redundant processing capabilities is revised as spare controller；If described master controller is normal, but spare controller fault, then the controller that in other normal controller, redundant processing capabilities is maximum is revised as spare controller.
Further, fault recovery prioritization module, for when master controller and spare controller are normal, being ranked up the priority of failed controller from big to small, and appraise and decide the current processing capabilities of each failed controller；
Fault processing module, for being ranked up the redundant processing capabilities of normal controller from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.
Further, the failed controller current processing capabilities whether described fault processing module is the highest more than priority for judging the maximum normal controller disposal ability of redundant processing capabilities, if, the maximum normal controller of described redundant processing capabilities takes over the switch of the highest failed controller of described priority, the failed controller back-up processing that described priority is the highest terminates, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller；
Otherwise, the maximum normal controller of described redundant processing capabilities takes over the part switch of the highest failed controller of described priority, the remaining switch of the failed controller that the second largest normal controller adapter priority of redundant processing capabilities is the highest, the like, until the switch having taken over the highest failed controller of priority completes back-up processing, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
Further, if described fault processing module is used for the minimum normal controller disposal ability of redundant processing capabilities less than failed controller current processing capabilities, the part switch of described normal controller taking over fault controller, back-up processing terminates.
Further, maintenance of information module, for master controller periodic maintenance regular maintenance information table, and described regular maintenance information table being issued other each controller, the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller；
Wherein, the content of described regular maintenance information table includes controller type, state, address information, priority, appraises and decides disposal ability, current processing capabilities, affiliated exchanger information and/or switch type.
Further, described breakdown judge module is for when master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, the exchanger information received is mated by master controller with the exchanger information belonging to regular maintenance information table middle controller, judge failed controller, or, master controller is not connected to determine this controller failure by judgement and this controller；
When master controller fault, spare controller is normal, belonging to master controller, service request is sent to spare controller by exchange opportunity, described spare controller is according to the exchanger information received, master controller fault is judged by exchanger information belonging to each controller in regular maintenance information table, or, spare controller is by judging that the annexation with each other controller determines master controller fault；Or
Other controller when not receiving master controller and spare controller message, being then mutually attached application, if connecting normal, then can confirm that master controller and spare controller fault according to regular maintenance information table.
Further, Failure Recovery Module, for recovering normal when master controller failure judgement controller, then this failed controller information is handed down to each controller, each controller is by checking oneself internal trustship information, it may be judged whether have this controller service, if had, then send information to this controller, and reconstruct all information.
In the present invention, when master controller and spare controller are normal, the priority of failed controller is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller；The redundant processing capabilities of normal controller is ranked up from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.Therefore, it is possible to preferentially ensure high-grade Network response, provide differentiated service to client, promote client perception, and then improve internet security and reliability.
By referring to the accompanying drawing detailed description to the exemplary embodiment of the present invention, the further feature of the present invention and advantage thereof will be made apparent from.
Accompanying drawing explanation
The accompanying drawing of the part constituting description describes embodiments of the invention, and is used for together with the description explaining principles of the invention.
With reference to accompanying drawing, according to detailed description below, it is possible to be more clearly understood from the present invention, wherein:
Fig. 1 is the schematic flow sheet of an embodiment of controller failure backup method of the present invention.
Fig. 2 is the schematic flow sheet of another embodiment of controller failure backup method of the present invention.
Fig. 3 is the structural representation of an embodiment of controller failure standby system of the present invention.
Fig. 4 is the structure chart of an embodiment of the network of controller of the present invention composition.
Detailed description of the invention
The various exemplary embodiments of the present invention are described in detail now with reference to accompanying drawing.It should also be noted that unless specifically stated otherwise, the parts otherwise set forth in these embodiments and positioned opposite, the numerical expression of step and numerical value do not limit the scope of the invention.
Simultaneously, it should be appreciated that for the ease of describing, the size of the various piece shown in accompanying drawing is not draw according to actual proportionate relationship.
Description only actually at least one exemplary embodiment is illustrative below, never as any restriction to the present invention and application or use.
The known technology of person of ordinary skill in the relevant, method and apparatus are likely to be not discussed in detail, but in the appropriate case, described technology, method and apparatus should be considered to authorize a part for description.
Shown here with in all examples discussed, any occurrence should be construed as merely exemplary, not as restriction.Therefore, other example of exemplary embodiment can have different values.
It should also be noted that similar label and letter below figure represent similar terms, therefore, once a certain Xiang Yi accompanying drawing is defined, then it need not be further discussed in accompanying drawing subsequently.
For making the object, technical solutions and advantages of the present invention clearly understand, below in conjunction with specific embodiment, and with reference to accompanying drawing, the present invention is described in more detail.
Fig. 1 is the schematic flow sheet of an embodiment of controller failure backup method of the present invention.The method comprises the following steps:
In step 110, when master controller and spare controller are normal, the priority of failed controller is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller.
In step 120, the redundant processing capabilities of normal controller is ranked up from big to small.
Wherein, redundant processing capabilities is that controller Design Treatment ability deducts the disposal ability used.
In step 130, according to the failed controller after the normal controller adapter sequence successively after sequence.
Wherein, judge the failed controller the current processing capabilities whether maximum normal controller disposal ability of redundant processing capabilities is the highest more than priority, if, the maximum normal controller of described redundant processing capabilities takes over the switch of the highest failed controller of described priority, the failed controller back-up processing that described priority is the highest terminates, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
Otherwise, the maximum normal controller of described redundant processing capabilities takes over the part switch of the highest failed controller of described priority, the remaining switch of the failed controller that the second largest normal controller adapter priority of redundant processing capabilities is the highest, the like, until the switch having taken over the highest failed controller of priority completes back-up processing, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
If processing last, the minimum normal controller disposal ability of redundant processing capabilities is less than failed controller current processing capabilities, and the part switch of described normal controller taking over fault controller, back-up processing terminates.
In this embodiment, when master controller and spare controller are normal, the priority of failed controller is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller；The redundant processing capabilities of normal controller is ranked up from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.Therefore, it is possible to according to fault priority, disposal ability, preferential guarantee high-grade Network response, provide differentiated service to client, promote client perception, and then improve internet security and reliability.
It addition, in order to make switch belonging to failed controller as far as possible back up to the least possible territory, therefore take and distributed to the maximum controller of processing redundancy, reduce the appearance of cross-domain calculating.If there is being originally a territory, but when becoming the situation of cross-domain calculating after backup, it is possible to according to trustship information, find out the nodal information of same area, complete so that it is limited in the territory of original same failed controller management as far as possible, less information interaction amount.
Fig. 2 is the schematic flow sheet of another embodiment of controller failure backup method of the present invention.
In step 210, it is judged that master controller whether fault, if so, then perform step 220, otherwise, perform step 230.
In step 220, it is judged that whether spare controller is normal, if so, then perform step 240, otherwise, perform step 250.
In step 230, it is judged that spare controller whether fault, if so, then perform step 260, otherwise, perform step 210.
In step 240, described spare controller is revised as master controller, controller maximum for redundant processing capabilities in other normal controller is revised as spare controller.
In step 250, controller maximum for redundant processing capabilities in other normal controller being revised as master controller, the second largest controller of redundant processing capabilities is revised as spare controller.
The controller that redundant processing capabilities is maximum in step 260, other normal controller is revised as spare controller.
Above-mentioned judge process is circulation operation, the i.e. primary, spare controller of monitor in real time whether fault.If it is judged that master controller and spare controller are all normal, and when other controller breaks down, then continue executing with step 110, i.e. the priority according to failed controller, preferential guarantee high-grade Network response.
In this embodiment, adopt controller backup scenario flexibly, automatically primary, spare controller is elected, ensure that the whole network exists primary controller and spare controller simultaneously, reduce active and standby controller simultaneous faults and cause the probability of the whole network information dropout and network paralysis, improve internet security and reliability further.
An alternative embodiment of the invention, master controller periodic maintenance regular maintenance information table, and described regular maintenance information table is issued other each controller, the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller.
Wherein, the content of described regular maintenance information table includes controller type, state, address information, priority, appraises and decides disposal ability, current processing capabilities, affiliated exchanger information and/or switch type, as shown in the table:
If set to local, then refer to this controller span of control, refer specifically to the details of the switch that each controller controls.If provided as master controller, then refer to the master controller address of contact during affiliated exchange fault.Master controller completes spare controller distribution when breakdown judge and fault generation；If provided as spare controller, refer to the spare controller of master controller, be also the second standby address of switch contact in this subdomain；If provided as other, then refer to range of management in other controller.
Status information, refers to each controller running status；Address information refers to each controller address；Priority, refers to affiliated subdomain Business Processing priority；Appraise and decide disposal ability, refer to each controller Design Treatment ability；Current processing capabilities, refers to the disposal ability that each controller has currently used；Affiliated exchanger information, refers to the switch address that each controller controls；Switch type, if provided as this territory, refers to the switch (this territory or trustship) in this territory original, if provided as trustship, then refers to as the switch that other territories manage.
When master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, the exchanger information received is mated by master controller with the exchanger information belonging to regular maintenance information table middle controller, judge failed controller, or, master controller is not connected to determine this controller failure by judgement and this controller.
When master controller fault, spare controller is normal, belonging to master controller, service request is sent to spare controller by exchange opportunity, described spare controller is according to the exchanger information received, master controller fault is judged by exchanger information belonging to each controller in regular maintenance information table, or, spare controller is by judging that the annexation with each other controller determines master controller fault.Or
Other controller when not receiving master controller and spare controller message, being then mutually attached application, if connecting normal, then can confirm that master controller and spare controller fault according to regular maintenance information table.
In this embodiment, by arranging regular maintenance information table, master controller periodic maintenance, and table is issued other controller.Other controller will relate to the primary, spare controller information in this territory and issue affiliated switch, and each controller is according to regular maintenance information table, it is possible to judge failed controller.
An alternative embodiment of the invention, when master controller failure judgement controller recovers normal, then this failed controller information is handed down to each controller, each controller is by checking oneself internal trustship information, determine whether this controller service, if it has, then send information to this controller, and reconstruct all information.
Such as, failed controller C recovers normal, now master controller is normal to all controller notification controller C, the information table of oneself checked by each controller, now certain controller finds in self information table, there is the trustship switch of controller C, be therefore directly related to the switch of controller C by master controller and return controller C management, then update information table again.
In this embodiment, when failed controller fault terminates, Internet resources during fault and business are set up information re-synchronization to other controller by the switch trustship relation in regular maintenance information table by master controller, further, improve internet security and reliability.Further, the present invention is only small on the impact of existing network equipment, it is easy to dispose at existing network.
Present invention also offers a kind of controller failure backup method, the i.e. flow process of corresponding diagram 2, by the method embodiment, adopt controller backup scenario flexibly, automatically primary, spare controller is elected, ensure that the whole network exists primary controller and spare controller simultaneously, reduce active and standby controller simultaneous faults and cause the probability of the whole network information dropout and network paralysis, improve internet security and reliability further.Idiographic flow is as in figure 2 it is shown, no longer describe in detail at this.
Above-mentioned judge process is circulation operation, the i.e. primary, spare controller of monitor in real time whether fault.If it is judged that master controller and spare controller are all normal, and when other controller breaks down, then continue executing with the flow process of Fig. 1, i.e. the priority according to failed controller, preferential guarantee high-grade Network response.Idiographic flow is as it is shown in figure 1, no longer describe in detail at this.
In this embodiment, when master controller and spare controller are normal, the priority of failed controller is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller；The redundant processing capabilities of normal controller is ranked up from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.Therefore, it is possible to according to fault priority, disposal ability, preferential guarantee high-grade Network response, provide differentiated service to client, promote client perception, and then improve internet security and reliability.
It addition, in order to make switch belonging to failed controller as far as possible back up to the least possible territory, therefore take and distributed to the maximum controller of processing redundancy, reduce the appearance of cross-domain calculating.If there is being originally a territory, but when becoming the situation of cross-domain calculating after backup, it is possible to according to trustship information, find out the nodal information of same area, complete so that it is limited in the territory of original same failed controller management as far as possible, less information interaction amount.
Wherein, master controller periodic maintenance regular maintenance information table, and described regular maintenance information table is issued other each controller, the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller.By arranging regular maintenance information table, master controller periodic maintenance, and table is issued other controller.Other controller will relate to the primary, spare controller information in this territory and issue affiliated switch, and each controller is according to regular maintenance information table, it is possible to judge failed controller.
If master controller and spare controller are all normal, other controller breaks down, then the priority according to failed controller, preferential guarantee high-grade Network response, there is provided differentiated service to client, promote client perception, and then improve internet security and reliability.
When failed controller fault terminates, the Internet resources during fault and business are set up information re-synchronization to other controller by the switch trustship relation in regular maintenance information table by master controller, further, improve internet security and reliability.Further, the present invention is only small on the impact of existing network equipment, it is easy to dispose at existing network.
The specific operation process of this embodiment is all embodied in each embodiment above, no longer elaborates herein.
Fig. 3 is the structural representation of an embodiment of controller failure standby system of the present invention.This system includes fault recovery prioritization module 310 and fault processing module 320, wherein:
Fault recovery prioritization module 310, for when master controller and spare controller are normal, being ranked up the priority of failed controller from big to small, and appraise and decide the current processing capabilities of each failed controller.
Fault processing module 320, for being ranked up the redundant processing capabilities of normal controller from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.
Wherein, redundant processing capabilities is that controller Design Treatment ability deducts the disposal ability used.
The failed controller current processing capabilities whether described fault processing module 320 is the highest more than priority for judging the maximum normal controller disposal ability of redundant processing capabilities, if, the maximum normal controller of described redundant processing capabilities takes over the switch of the highest failed controller of described priority, the failed controller back-up processing that described priority is the highest terminates, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
Otherwise, the maximum normal controller of described redundant processing capabilities takes over the part switch of the highest failed controller of described priority, the remaining switch of the failed controller that the second largest normal controller adapter priority of redundant processing capabilities is the highest, the like, until the switch having taken over the highest failed controller of priority completes back-up processing, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
If processing last, the minimum normal controller disposal ability of redundant processing capabilities is less than failed controller current processing capabilities, and the part switch of described normal controller taking over fault controller, back-up processing terminates.
In this embodiment, when master controller and spare controller are normal, the priority of failed controller is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller；The redundant processing capabilities of normal controller is ranked up from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.Therefore, it is possible to according to fault priority, disposal ability, preferential guarantee high-grade Network response, provide differentiated service to client, promote client perception, and then improve internet security and reliability.
It addition, in order to make switch belonging to failed controller as far as possible back up to the least possible territory, therefore take and distributed to the maximum spare controller of processing redundancy, reduce the appearance of cross-domain calculating.If there is being originally a territory, but when becoming the situation of cross-domain calculating after backup, it is possible to according to trustship information, find out the nodal information of same area, complete so that it is limited in the territory of original same failed controller management as far as possible, less information interaction amount.
An alternative embodiment of the invention, native system also includes breakdown judge module 330 and failure analysis module 340.Wherein:
Breakdown judge module 330, is used for judging master controller and/or spare controller whether fault.
Failure analysis module 340, if spare controller is normal for master controller fault, is then revised as described spare controller master controller, controller maximum for redundant processing capabilities in other normal controller is revised as spare controller；If master controller and spare controller all faults, then controller maximum for redundant processing capabilities in other normal controller being revised as master controller, the second largest controller of redundant processing capabilities is revised as spare controller；If described master controller is normal, but spare controller fault, then the controller that in other normal controller, redundant processing capabilities is maximum is revised as spare controller.
In this embodiment, adopt controller backup scenario flexibly, automatically elect primary, spare controller, reduce active and standby controller simultaneous faults and cause the probability of the whole network information dropout and network paralysis, improve internet security and reliability further.
An alternative embodiment of the invention, native system also includes maintenance of information module 350, for master controller periodic maintenance regular maintenance information table, and described regular maintenance information table is issued other each controller, the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller.
Wherein, the content of described regular maintenance information table includes controller type, state, address information, priority, appraises and decides disposal ability, current processing capabilities, affiliated exchanger information and/or switch type, as shown in the table:
If set to local, then refer to this controller span of control, refer specifically to the details of the switch that each controller controls.If provided as master controller, then refer to the master controller address of contact during affiliated exchange fault.Master controller completes spare controller distribution when breakdown judge and fault generation；If provided as spare controller, refer to the spare controller of master controller, be also the second standby address of switch contact in this subdomain；If provided as other, then refer to range of management in other controller.
Status information, refers to each controller running status；Address information refers to each controller address；Priority, refers to affiliated subdomain Business Processing priority；Appraise and decide disposal ability, refer to each controller Design Treatment ability；Current processing capabilities, refers to the disposal ability that each controller has currently used；Affiliated exchanger information, refers to the switch address that each controller controls；Switch type, if provided as this territory, refers to the switch (this territory or trustship) in this territory original, if provided as trustship, then refers to as the switch that other territories manage.
Maintenance of information module 350 completes the maintenance of regular maintenance information table, in time and the information mutual communication of master controller, it is ensured that the accuracy of information and promptness.
When master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, the exchanger information received is mated by master controller with the exchanger information belonging to regular maintenance information table middle controller, judge failed controller, or, master controller is not connected to determine this controller failure by judgement and this controller.
When master controller fault, spare controller is normal, belonging to master controller, service request is sent to spare controller by exchange opportunity, described spare controller is according to the exchanger information received, master controller fault is judged by exchanger information belonging to each controller in regular maintenance information table, or, spare controller is by judging that the annexation with each other controller determines master controller fault.Or
Other controller when not receiving master controller and spare controller message, being then mutually attached application, if connecting normal, then can confirm that master controller and spare controller fault according to regular maintenance information table.
In this embodiment, by arranging regular maintenance information table, master controller periodic maintenance, and table is issued other controller.Other controller will relate to the primary, spare controller information in this territory and issue affiliated switch, and each controller is according to regular maintenance information table, it is possible to judge failed controller.
An alternative embodiment of the invention, this system also includes Failure Recovery Module 360, for recovering normal when master controller failure judgement controller, then this failed controller information is handed down to each controller, each controller is by checking oneself internal trustship information, it may be judged whether have this controller service, if had, then send information to this controller, and reconstruct all information.
Such as, failed controller C recovers normal, now master controller is normal to all controller notification controller C, the information table of oneself checked by each controller, now certain controller finds in self information table, there is the trustship switch of controller C, be therefore directly related to the switch of controller C by master controller and return controller C management, then update information table again.
In this embodiment, when failed controller fault terminates, Internet resources during fault and business are set up information re-synchronization to other controller by the switch trustship relation in regular maintenance information table by master controller, further, improve internet security and reliability.Further, the present invention is only small on the impact of existing network equipment, it is easy to dispose at existing network.
Present invention also offers a kind of controller failure standby system, this system embodiment can be as shown in Figure 3.Within the system, breakdown judge module 330 and failure analysis module 340 elect primary, spare controller automatically, ensure that the whole network exists primary controller and spare controller simultaneously, reduce active and standby controller simultaneous faults and cause the probability of the whole network information dropout and network paralysis, improve internet security and reliability further.Specific embodiment is as it has been described above, no longer describe in detail at this.
Above-mentioned judge process is circulation operation, the i.e. primary, spare controller of monitor in real time whether fault.If it is judged that master controller and spare controller are all normal, and when other controller breaks down, then continue the priority according to failed controller, preferential guarantee high-grade Network response.Specific embodiment is as it has been described above, no longer describe in detail at this.
In this embodiment, when master controller and spare controller are normal, the priority of failed controller is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller；The redundant processing capabilities of normal controller is ranked up from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.Therefore, it is possible to according to fault priority, disposal ability, preferential guarantee high-grade Network response, provide differentiated service to client, promote client perception, and then improve internet security and reliability.
It addition, in order to make switch belonging to failed controller as far as possible back up to the least possible territory, therefore take and distributed to the maximum controller of processing redundancy, reduce the appearance of cross-domain calculating.If there is being originally a territory, but when becoming the situation of cross-domain calculating after backup, it is possible to according to trustship information, find out the nodal information of same area, complete so that it is limited in the territory of original same failed controller management as far as possible, less information interaction amount.
Wherein, maintenance of information module 350 is for master controller periodic maintenance regular maintenance information table, and described regular maintenance information table is issued other each controller, the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller.By arranging regular maintenance information table, master controller periodic maintenance, and table is issued other controller.Other controller will relate to the primary, spare controller information in this territory and issue affiliated switch, and each controller is according to regular maintenance information table, it is possible to judge failed controller.
If master controller and spare controller are all normal, other controller breaks down, then fault processing module 320 is according to the fault recovery prioritization module 310 prioritization to failed controller, preferential guarantee high-grade Network response, differentiated service is provided to client, promote client perception, and then improve internet security and reliability.
When failed controller fault terminates, Internet resources during fault and business are set up information re-synchronization to other controller for master controller by the switch trustship relation in regular maintenance information table by Failure Recovery Module 360, further, internet security and reliability are improved.Further, the present invention is only small on the impact of existing network equipment, it is easy to dispose at existing network.
The specific operation process of this embodiment is all embodied in each embodiment above, no longer elaborates herein.
With a specific embodiment, the present invention will be described further below.
As shown in Figure 4, in the network of controller A-F composition, its middle controller A is elected as master controller, and controller B is elected as spare controller, then regular maintenance information table respectively herein below in each controller:
1), controller A (master):
2), controller B (standby)
3), controller C
4), controller D
5), controller E
6), controller F
When master controller and standby master controller are normal, during other controller failure, first master controller recovers the failed controller that priority is high, obtains its current processing capabilities；Master controller appraises and decides disposal ability and current processing capabilities by the normal all controllers of state, it is thus achieved that each alternate controller redundant processing capabilities；And by controller maximum for redundant processing capabilities and failed controller current processing capabilities comparison match, obtain backup controller list, and switch belonging to failed controller subdomain is issued in backup controller address, complete adapter.
Such as controller C/D/F simultaneous faults, first compare priority, it has been found that controller priority D > C > F, then first consider backup controller D.
1) backup of controller D
Controller A is 10, B be 15, E is 10, is arranged as by the controller going to backup according to redundancy backup ability: B/A/E, and namely paying the utmost attention to B is backup controller.
And now the current processing capabilities of failed controller is respectively as follows: D is 8, therefore possessing backup scenario is: 8 switches in B adapter D, therefore the back-up processing of D terminates.
Now, the information of controller B becomes:
2) backup of controller C
In order to prepare the backup to controller C, it is possible to find that now controller redundancy backup ability is A be 10, B be 7, E is 10, is arranged as by the controller going to backup according to redundancy backup ability: A/E/B, and namely paying the utmost attention to A is backup controller.
And now the current processing capabilities of failed controller is respectively as follows: C is 15, therefore backup scenario is: 10 switches in A adapter C, and 5 switches in E adapter C, the back-up processing of this controller C terminates.
Now the information of controller A and E becomes:
Controller A information is:
Controller E information is:
3) backup of controller F
In order to prepare the backup to controller F, it is possible to find that now controller redundancy backup ability is E be 5, B is 7, and now the current processing capabilities of failed controller F is 6, therefore 6 switches in B adapter F, and the back-up processing of this controller F terminates.
Now controller B information is:
When master controller and spare controller simultaneous faults, other each controller interacts to be appraised and decided and current processing capabilities, the maximum controller of redundancy is announced from as master controller, now, master controller reconstruct regular maintenance information table after election terminates, what declaration redundant processing capabilities except self was maximum is spare controller, and obtains backup controller, and backup procedure is described above.
When failed controller fault terminates, the Internet resources during fault and business are set up information re-synchronization to other controller by the switch trustship relation in regular maintenance information table by master controller.As failed controller C recovers normal, now master controller is normal to all controller notification controller C, the regular maintenance information table of oneself checked by each controller, now controller A and E finds in self information table, there is the trustship switch of controller C, therefore it is directly related to the switch of controller C by master controller and returns controller C management, then update information table again.
So far, the present invention is described in detail.In order to avoid covering the design of the present invention, it does not have describe details more known in the field.Those skilled in the art are as described above, complete it can be appreciated how implement technical scheme disclosed herein.
It is likely to be achieved in many ways the method for the present invention and device.Such as, can by software, hardware, firmware or software, hardware, firmware any combination realize method and the device of the present invention.For the said sequence of step of described method merely to illustrate, the step of the method for the present invention is not limited to order described in detail above, unless specifically stated otherwise.Additionally, in certain embodiments, can being also record program in the recording medium by the invention process, these programs include the machine readable instructions for realizing the method according to the invention.Thus, the present invention also covers the record medium of the storage program for performing the method according to the invention.
Although some specific embodiments of the present invention being described in detail already by example, but it should be appreciated by those skilled in the art, above example is merely to illustrate, rather than in order to limit the scope of the present invention.It should be appreciated by those skilled in the art, can without departing from the scope and spirit of the present invention, above example be modified.The scope of the present invention be defined by the appended claims.

Claims (28)

1. a controller failure backup method, including:
When master controller and spare controller are normal, the priority of failed controller is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller；
The redundant processing capabilities of normal controller is ranked up from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.
2. controller failure backup method according to claim 1, including:
Judge the failed controller the current processing capabilities whether maximum normal controller disposal ability of redundant processing capabilities is the highest more than priority, if, the maximum normal controller of described redundant processing capabilities takes over the switch of the highest failed controller of described priority, the failed controller back-up processing that described priority is the highest terminates, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller；
Otherwise, the maximum normal controller of described redundant processing capabilities takes over the part switch of the highest failed controller of described priority, the remaining switch of the failed controller that the second largest normal controller adapter priority of redundant processing capabilities is the highest, the like, until the switch having taken over the highest failed controller of priority completes back-up processing, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
3. controller failure backup method according to claim 2, including:
If the minimum normal controller disposal ability of redundant processing capabilities is less than failed controller current processing capabilities, the part switch of described normal controller taking over fault controller, back-up processing terminates.
4. according to the arbitrary described controller failure backup method of claims 1 to 3, including:
Judge master controller whether fault, if, then judge that whether spare controller is normal, if, then described spare controller is revised as master controller, controller maximum for redundant processing capabilities in other normal controller is revised as spare controller, otherwise, controller maximum for redundant processing capabilities in other normal controller is revised as master controller, and the second largest controller of redundant processing capabilities is revised as spare controller；
If described master controller is normal, but spare controller fault, then the controller that in other normal controller, redundant processing capabilities is maximum is revised as spare controller.
5. according to the arbitrary described controller failure backup method of Claims 1-4, including:
Master controller periodic maintenance regular maintenance information table, and described regular maintenance information table is issued other each controller, the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller；
Wherein, the content of described regular maintenance information table includes controller type, state, address information, priority, appraises and decides disposal ability, current processing capabilities, affiliated exchanger information and/or switch type.
6. controller failure backup method according to claim 5, including:
When master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, the exchanger information received is mated by master controller with the exchanger information belonging to regular maintenance information table middle controller, judge failed controller, or, master controller is not connected to determine this controller failure by judgement and this controller；
When master controller fault, spare controller is normal, belonging to master controller, service request is sent to spare controller by exchange opportunity, described spare controller is according to the exchanger information received, master controller fault is judged by exchanger information belonging to each controller in regular maintenance information table, or, spare controller is by judging that the annexation with each other controller determines master controller fault；Or
Other controller when not receiving master controller and spare controller message, being then mutually attached application, if connecting normal, then can confirm that master controller and spare controller fault according to regular maintenance information table.
7. according to the arbitrary described controller failure backup method of claim 1 to 6, including:
When master controller failure judgement controller recovers normal, then this failed controller information being handed down to each controller, each controller is by checking oneself internal trustship information, determine whether this controller service, if it has, then send information to this controller, and reconstruct all information.
8. a controller failure backup method, including:
Judge master controller whether fault, if, then judge that whether spare controller is normal, if, then described spare controller is revised as master controller, controller maximum for redundant processing capabilities in other normal controller is revised as spare controller, otherwise, controller maximum for redundant processing capabilities in other normal controller is revised as master controller, and the second largest controller of redundant processing capabilities is revised as spare controller；
If described master controller is normal, but spare controller fault, then the controller that in other normal controller, redundant processing capabilities is maximum is revised as spare controller.
9. controller failure backup method according to claim 8, also includes:
When master controller and spare controller are normal, the priority of failed controller is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller；
The redundant processing capabilities of normal controller is ranked up from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.
10. controller failure backup method according to claim 9, including:
Judge the failed controller the current processing capabilities whether maximum normal controller disposal ability of redundant processing capabilities is the highest more than priority, if, the maximum normal controller of described redundant processing capabilities takes over the switch of the highest failed controller of described priority, the failed controller back-up processing that described priority is the highest terminates, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller；
Otherwise, the maximum normal controller of described redundant processing capabilities takes over the part switch of the highest failed controller of described priority, the remaining switch of the failed controller that the second largest normal controller adapter priority of redundant processing capabilities is the highest, the like, until the switch having taken over the highest failed controller of priority completes back-up processing, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
11. controller failure backup method according to claim 10, including:
If the minimum normal controller disposal ability of redundant processing capabilities is less than failed controller current processing capabilities, the part switch of described normal controller taking over fault controller, back-up processing terminates.
12. according to Claim 8 to 11 arbitrary described controller failure backup methods, including:
Master controller periodic maintenance regular maintenance information table, and described regular maintenance information table is issued other each controller, the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller；
Wherein, the content of described regular maintenance information table includes controller type, state, address information, priority, appraises and decides disposal ability, current processing capabilities, affiliated exchanger information and/or switch type.
13. controller failure determination methods according to claim 12, including:
When master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, the exchanger information received is mated by master controller with the exchanger information belonging to regular maintenance information table middle controller, judge failed controller, or, master controller is not connected to determine this controller failure by judgement and this controller；
When master controller fault, spare controller is normal, belonging to master controller, service request is sent to spare controller by exchange opportunity, described spare controller is according to the exchanger information received, master controller fault is judged by exchanger information belonging to each controller in regular maintenance information table, or, spare controller is by judging that the annexation with each other controller determines master controller fault；Or
Other controller when not receiving master controller and spare controller message, being then mutually attached application, if connecting normal, then can confirm that master controller and spare controller fault according to regular maintenance information table.
14. according to Claim 8 to 13 arbitrary described controller failure backup methods, including:
When master controller failure judgement controller recovers normal, then this failed controller information being handed down to each controller, each controller is by checking oneself internal trustship information, determine whether this controller service, if it has, then send information to this controller, and reconstruct all information.
15. a controller failure standby system, including:
Fault recovery prioritization module, for when master controller and spare controller are normal, being ranked up the priority of failed controller from big to small, and appraise and decide the current processing capabilities of each failed controller；
Fault processing module, for being ranked up the redundant processing capabilities of normal controller from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.
16. controller failure standby system according to claim 15, including:
The failed controller current processing capabilities whether described fault processing module is the highest more than priority for judging the maximum normal controller disposal ability of redundant processing capabilities, if, the maximum normal controller of described redundant processing capabilities takes over the switch of the highest failed controller of described priority, the failed controller back-up processing that described priority is the highest terminates, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller；
Otherwise, the maximum normal controller of described redundant processing capabilities takes over the part switch of the highest failed controller of described priority, the remaining switch of the failed controller that the second largest normal controller adapter priority of redundant processing capabilities is the highest, the like, until the switch having taken over the highest failed controller of priority completes back-up processing, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
17. controller failure standby system according to claim 16, including:
If described fault processing module is used for the minimum normal controller disposal ability of redundant processing capabilities less than failed controller current processing capabilities, the part switch of described normal controller taking over fault controller, back-up processing terminates.
18. according to the arbitrary described controller failure standby system of claim 15 to 17, also include:
Breakdown judge module, is used for judging master controller and/or spare controller whether fault；
Failure analysis module, if spare controller is normal for master controller fault, is then revised as described spare controller master controller, controller maximum for redundant processing capabilities in other normal controller is revised as spare controller；If master controller and spare controller all faults, then controller maximum for redundant processing capabilities in other normal controller being revised as master controller, the second largest controller of redundant processing capabilities is revised as spare controller；If described master controller is normal, but spare controller fault, then the controller that in other normal controller, redundant processing capabilities is maximum is revised as spare controller.
19. according to the arbitrary described controller failure standby system of claim 15 to 18, also include:
Maintenance of information module, for master controller periodic maintenance regular maintenance information table, and issues other each controller by described regular maintenance information table, and the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller；
Wherein, the content of described regular maintenance information table includes controller type, state, address information, priority, appraises and decides disposal ability, current processing capabilities, affiliated exchanger information and/or switch type.
20. controller failure standby system according to claim 19, including:
Described breakdown judge module is for when master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, the exchanger information received is mated by master controller with the exchanger information belonging to regular maintenance information table middle controller, judge failed controller, or, master controller is not connected to determine this controller failure by judgement and this controller；
When master controller fault, spare controller is normal, belonging to master controller, service request is sent to spare controller by exchange opportunity, described spare controller is according to the exchanger information received, master controller fault is judged by exchanger information belonging to each controller in regular maintenance information table, or, spare controller is by judging that the annexation with each other controller determines master controller fault；Or
Other controller when not receiving master controller and spare controller message, being then mutually attached application, if connecting normal, then can confirm that master controller and spare controller fault according to regular maintenance information table.
21. according to the arbitrary described controller failure standby system of claim 15 to 20, including:
Failure Recovery Module, for recovering normal when master controller failure judgement controller, then this failed controller information is handed down to each controller, each controller is by checking oneself internal trustship information, determine whether this controller service, if it has, then send information to this controller, and reconstruct all information.
22. a controller failure standby system, including:
Breakdown judge module, is used for judging master controller and/or spare controller whether fault；
Failure analysis module, if spare controller is normal for master controller fault, is then revised as described spare controller master controller, controller maximum for redundant processing capabilities in other normal controller is revised as spare controller；If master controller and spare controller all faults, then controller maximum for redundant processing capabilities in other normal controller being revised as master controller, the second largest controller of redundant processing capabilities is revised as spare controller；If described master controller is normal, but spare controller fault, then the controller that in other normal controller, redundant processing capabilities is maximum is revised as spare controller.
23. controller failure standby system according to claim 22, also include:
Fault recovery prioritization module, for when master controller and spare controller are normal, being ranked up the priority of failed controller from big to small, and appraise and decide the current processing capabilities of each failed controller；
Fault processing module, for being ranked up the redundant processing capabilities of normal controller from big to small, and according to the failed controller after the normal controller adapter sequence successively after sequence.
24. controller failure standby system according to claim 23, including:
The failed controller current processing capabilities whether described fault processing module is the highest more than priority for judging the maximum normal controller disposal ability of redundant processing capabilities, if, the maximum normal controller of described redundant processing capabilities takes over the switch of the highest failed controller of described priority, the failed controller back-up processing that described priority is the highest terminates, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller；
Otherwise, the maximum normal controller of described redundant processing capabilities takes over the part switch of the highest failed controller of described priority, the remaining switch of the failed controller that the second largest normal controller adapter priority of redundant processing capabilities is the highest, the like, until the switch having taken over the highest failed controller of priority completes back-up processing, and again align the sequence of normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until having taken over all of failed controller.
25. controller failure standby system according to claim 24, including:
If described fault processing module is used for the minimum normal controller disposal ability of redundant processing capabilities less than failed controller current processing capabilities, the part switch of described normal controller taking over fault controller, back-up processing terminates.
26. according to the arbitrary described controller failure standby system of claim 22 to 25, including:
Maintenance of information module, for master controller periodic maintenance regular maintenance information table, and issues other each controller by described regular maintenance information table, and the information relating to this territory master controller and spare controller is issued affiliated switch by other each controller；
Wherein, the content of described regular maintenance information table includes controller type, state, address information, priority, appraises and decides disposal ability, current processing capabilities, affiliated exchanger information and/or switch type.
27. controller failure standby system according to claim 26, including:
Described breakdown judge module is for when master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, the exchanger information received is mated by master controller with the exchanger information belonging to regular maintenance information table middle controller, judge failed controller, or, master controller is not connected to determine this controller failure by judgement and this controller；
When master controller fault, spare controller is normal, belonging to master controller, service request is sent to spare controller by exchange opportunity, described spare controller is according to the exchanger information received, master controller fault is judged by exchanger information belonging to each controller in regular maintenance information table, or, spare controller is by judging that the annexation with each other controller determines master controller fault；Or
Other controller when not receiving master controller and spare controller message, being then mutually attached application, if connecting normal, then can confirm that master controller and spare controller fault according to regular maintenance information table.
28. according to the arbitrary described controller failure standby system of claim 22 to 27, including:
Failure Recovery Module, for recovering normal when master controller failure judgement controller, then this failed controller information is handed down to each controller, each controller is by checking oneself internal trustship information, determine whether this controller service, if it has, then send information to this controller, and reconstruct all information.
CN201410850673.6A 2014-12-31 2014-12-31 A kind of controller failure backup method and system Active CN105812161B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201410850673.6A CN105812161B (en) 2014-12-31 2014-12-31 A kind of controller failure backup method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410850673.6A CN105812161B (en) 2014-12-31 2014-12-31 A kind of controller failure backup method and system

Publications (2)

Publication Number Publication Date
CN105812161A true CN105812161A (en) 2016-07-27
CN105812161B CN105812161B (en) 2019-08-06

Family

ID=56420706

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410850673.6A Active CN105812161B (en) 2014-12-31 2014-12-31 A kind of controller failure backup method and system

Country Status (1)

Country Link
CN (1) CN105812161B (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106603272A (en) * 2016-11-17 2017-04-26 上海斐讯数据通信技术有限公司 Controller protection method and system based on smooth restart
CN106972964A (en) * 2017-03-27 2017-07-21 北京邮电大学 A kind of restoration methods of SDN system and its controller failure
CN108528266A (en) * 2017-03-01 2018-09-14 华为技术有限公司 The method and apparatus of troubleshooting
CN108540317A (en) * 2018-03-29 2018-09-14 西安交通大学 A kind of double-deck detection method of multiple domain SDN control node failures
CN110879522A (en) * 2019-12-02 2020-03-13 浙江明度智控科技有限公司 Redundant gateway system and redundant switching method
CN115933565A (en) * 2022-12-23 2023-04-07 广东职业技术学院 AGV task exchange method, device, system and medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103596652A (en) * 2013-07-30 2014-02-19 华为技术有限公司 Network control method and device
CN103929333A (en) * 2014-05-08 2014-07-16 陈桂芳 Implementation method for SDN controller pool
WO2014114119A1 (en) * 2013-01-23 2014-07-31 Hangzhou H3C Technologies Co., Ltd. Redundant server operation by a software defined network controller
CN104158642A (en) * 2014-08-08 2014-11-19 上海斐讯数据通信技术有限公司 Method and system for providing backup for software defined network controller
WO2014202026A1 (en) * 2013-06-21 2014-12-24 中兴通讯股份有限公司 Method and system for virtual network mapping protection and computer storage medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014114119A1 (en) * 2013-01-23 2014-07-31 Hangzhou H3C Technologies Co., Ltd. Redundant server operation by a software defined network controller
WO2014202026A1 (en) * 2013-06-21 2014-12-24 中兴通讯股份有限公司 Method and system for virtual network mapping protection and computer storage medium
CN103596652A (en) * 2013-07-30 2014-02-19 华为技术有限公司 Network control method and device
CN103929333A (en) * 2014-05-08 2014-07-16 陈桂芳 Implementation method for SDN controller pool
CN104158642A (en) * 2014-08-08 2014-11-19 上海斐讯数据通信技术有限公司 Method and system for providing backup for software defined network controller

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106603272A (en) * 2016-11-17 2017-04-26 上海斐讯数据通信技术有限公司 Controller protection method and system based on smooth restart
CN108528266A (en) * 2017-03-01 2018-09-14 华为技术有限公司 The method and apparatus of troubleshooting
CN106972964A (en) * 2017-03-27 2017-07-21 北京邮电大学 A kind of restoration methods of SDN system and its controller failure
CN106972964B (en) * 2017-03-27 2019-11-22 北京邮电大学 A kind of restoration methods of SDN network system and its controller failure
CN108540317A (en) * 2018-03-29 2018-09-14 西安交通大学 A kind of double-deck detection method of multiple domain SDN control node failures
CN108540317B (en) * 2018-03-29 2020-03-31 西安交通大学 Double-layer detection method for multi-domain SDN control node fault
CN110879522A (en) * 2019-12-02 2020-03-13 浙江明度智控科技有限公司 Redundant gateway system and redundant switching method
CN115933565A (en) * 2022-12-23 2023-04-07 广东职业技术学院 AGV task exchange method, device, system and medium
CN115933565B (en) * 2022-12-23 2023-10-20 广东职业技术学院 AGV task exchange method, device, system and medium

Also Published As

Publication number Publication date
CN105812161B (en) 2019-08-06

Similar Documents

Publication Publication Date Title
CN105812161A (en) Controller fault backup method and system
CN103199972B (en) The two-node cluster hot backup changing method realized based on SOA, RS485 bus and hot backup system
US8862928B2 (en) Techniques for achieving high availability with multi-tenant storage when a partial fault occurs or when more than two complete faults occur
CN107404394B (en) IPTV system disaster tolerance method and IPTV disaster tolerance system
TWI701916B (en) Method and device for self-recovering management ability in distributed system
CN102916825A (en) Management equipment of dual-computer hot standby system, management method and dual-computer hot standby system
US8880703B2 (en) Address distribution method, device and system thereof
CN104639367B (en) A kind of method and system for realizing active/standby server switching
CN105681077A (en) Fault processing method, device and system
CN103905247B (en) Two-unit standby method and system based on multi-client judgment
CN104158707A (en) Method and device of detecting and processing brain split in cluster
CN105554074A (en) NAS resource monitoring system and monitoring method based on RPC communication
CN112118130B (en) Self-adaptive distributed cache active-standby state information switching method and device
CN104317803A (en) Data access structure and method of database cluster
CN109194514A (en) A kind of two-shipper monitoring method, device, server and storage medium
CN105577444B (en) A kind of wireless controller management method and wireless controller
CN104506372A (en) Method and system for realizing host-backup server switching
CN113127270A (en) Cloud computing-based 2-out-of-3 safety computer platform
CN104065526A (en) Server fault alarming method and device thereof
CN105426213A (en) Software update method and system
JP2009129409A (en) Failure recovery method, computer, cluster system, management computer, and failure recovery program
CN110979404A (en) Dual-machine hot standby system and method of automatic train supervision system
CN109104325B (en) Train network data transmission method, system and device based on CANopen protocol
CN105959145B (en) A kind of method and system for the concurrent management server being applicable in high availability cluster
EP2479926B1 (en) Method and device for backing up user information

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant