CN105812161B - A kind of controller failure backup method and system - Google Patents
A kind of controller failure backup method and system Download PDFInfo
- Publication number
- CN105812161B CN105812161B CN201410850673.6A CN201410850673A CN105812161B CN 105812161 B CN105812161 B CN 105812161B CN 201410850673 A CN201410850673 A CN 201410850673A CN 105812161 B CN105812161 B CN 105812161B
- 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.)
- Active
Links
Landscapes
- Hardware Redundancy (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a kind of controller failure backup method and systems.This method comprises: being ranked up the priority of failed controller from big to small when master controller and normal spare controller, and appraise and decide the current processing capabilities of each failed controller;The redundant processing capabilities of normal controller are ranked up from big to small, and successively take over the failed controller after sequence according to the normal controller after sequence.Therefore, it can preferentially ensure high-grade network service response, improve internet security and reliability.
Description
Technical field
The present invention relates to control field more particularly to a kind of controller failure backup method and systems.
Background technique
SDN controller is the core system component of SDN, once go wrong, if failing to handle in time, can not and
When respond new business demand, cause congestion, or even paralysis.Solution is to set up active and standby controller in father field, and lead at present
Father field controller is crossed to realize to the backup protection of sub- domain controller, but such mode there are the following problems:
The active and standby controller of father field generally artificially preassigns, but works as specified active and standby controller simultaneous faults, then network
It can not cope with automatically, cause network paralysis;
In addition, not all controller can act as backing up since controller performance limits, hardness backup, not only
The responding ability to business in original control subdomain, while business processing in fault restriction subdomain can be reduced;
When fault coverage is larger, the response of higher ranked business is not paid the utmost attention to, reduces customer perception.
Summary of the invention
The technical problem to be solved by the present invention is to when existing controller failure, internet security and poor reliability.
According to an aspect of the present invention, a kind of controller failure backup method is proposed, comprising:
When master controller and normal spare controller, the priority of failed controller is ranked up from big to small, and
Appraise and decide the current processing capabilities of each failed controller;
The redundant processing capabilities of normal controller are ranked up from big to small, and according to the normal controller after sequence according to
Failed controller after secondary adapter tube sequence.
Further, judge whether the maximum normal controller processing capacity of redundant processing capabilities is greater than the event of highest priority
Hinder controller current processing capabilities, if so, the maximum normal controller of the redundant processing capabilities takes over the highest priority
Failed controller interchanger, the failed controller back-up processing of the highest priority terminates, and again to normal control
The sequence of device redundant processing capabilities, starts the failed controller back-up processing of the second priority, until having taken over all failure controls
Device processed;
Otherwise, the maximum normal controller of the redundant processing capabilities takes over the failed controller of the highest priority
Part interchanger, the remaining exchange of the failed controller of second largest normal controller adapter tube highest priority of redundant processing capabilities
Machine, and so on, back-up processing is completed until having taken over the interchanger of failed controller of highest priority, and again to normal
The sequence of controller redundant processing capabilities, starts the failed controller back-up processing of the second priority, until having taken over all events
Hinder controller.
Further, if the smallest normal controller processing capacity of redundant processing capabilities is currently processed less than failed controller
Ability, the part interchanger of the normal controller taking over fault controller, back-up processing terminate.
Further, judge master controller whether failure, if so, judging whether spare controller normal, if so, by institute
It states spare controller and is revised as master controller, the maximum controller of redundant processing capabilities in other normal controllers is revised as standby
With controller, otherwise, the maximum controller of redundant processing capabilities in other normal controllers is revised as master controller, at redundancy
Second largest controller of reason ability is revised as spare controller;
If the master controller is normal, but spare controller failure, then redundant processing capabilities in other normal controllers
Maximum controller is revised as spare controller.
Further, master controller periodic maintenance daily maintenance information table, and the daily maintenance information table issued other
The information for being related to this domain master controller and spare controller is issued affiliated interchanger by each controller, other each controllers;
Wherein, the content of the daily maintenance information table includes controller type, state, address information, priority, appraises and decides
Processing capacity, 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,
Master controller matches the exchanger information received with exchanger information belonging to controller in daily maintenance information table, sentences
The disconnected controller that is out of order, alternatively, master controller is not connected to determine the controller failure by judgement with the controller;
When master controller fault and when normal spare controller, service request is sent to by the affiliated exchange opportunity of master controller
Spare controller, the spare controller pass through each control in daily maintenance information table according to the exchanger information received
The affiliated exchanger information of device judges master controller fault, alternatively, company of the spare controller by judgement and each other controllers
The relationship of connecing determines master controller fault;Or
Other controllers are not when receiving master controller and spare controller message, then according to daily maintenance information table phase
It mutually is attached application, if connection is normal, can confirm master controller and spare controller failure.
Further, when master controller judges that failed controller restores normally, to be then handed down to the failed controller information respectively
A controller, each controller judge whether there is the controller service by checking oneself internal trustship information, if so,
The controller is then sent information to, and reconstructs all information.
According to another aspect of the present invention, it is also proposed that a kind of controller failure backup method, comprising:
Judge master controller whether failure, if so, judging whether spare controller normal, if so, by described spare
Controller is revised as master controller, and the maximum controller of redundant processing capabilities in other normal controllers is revised as spare control
Otherwise the maximum controller of redundant processing capabilities in other normal controllers is revised as master controller, redundant processing capabilities by device
Second largest controller is revised as spare controller;
If the master controller is normal, but spare controller failure, then redundant processing capabilities in other normal controllers
Maximum controller is revised as spare controller.
Further, when master controller and normal spare controller, the priority of failed controller is carried out from big to small
Sequence, and appraise and decide the current processing capabilities of each failed controller;
The redundant processing capabilities of normal controller are ranked up from big to small, and according to the normal controller after sequence according to
Failed controller after secondary adapter tube sequence.
Further, judge whether the maximum normal controller processing capacity of redundant processing capabilities is greater than the event of highest priority
Hinder controller current processing capabilities, if so, the maximum normal controller of the redundant processing capabilities takes over the highest priority
Failed controller interchanger, the failed controller back-up processing of the highest priority terminates, and again to normal control
The sequence of device redundant processing capabilities, starts the failed controller back-up processing of the second priority, until having taken over all failure controls
Device processed;
Otherwise, the maximum normal controller of the redundant processing capabilities takes over the failed controller of the highest priority
Part interchanger, the remaining exchange of the failed controller of second largest normal controller adapter tube highest priority of redundant processing capabilities
Machine, and so on, back-up processing is completed until having taken over the interchanger of failed controller of highest priority, and again to normal
The sequence of controller redundant processing capabilities, starts the failed controller back-up processing of the second priority, until having taken over all events
Hinder controller.
Further, if the smallest normal controller processing capacity of redundant processing capabilities is currently processed less than failed controller
Ability, the part interchanger of the normal controller taking over fault controller, back-up processing terminate.
Further, master controller periodic maintenance daily maintenance information table, and the daily maintenance information table issued other
The information for being related to this domain master controller and spare controller is issued affiliated interchanger by each controller, other each controllers;
Wherein, the content of the daily maintenance information table includes controller type, state, address information, priority, appraises and decides
Processing capacity, 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,
Master controller matches the exchanger information received with exchanger information belonging to controller in daily maintenance information table, sentences
The disconnected controller that is out of order, alternatively, master controller is not connected to determine the controller failure by judgement with the controller;
When master controller fault and when normal spare controller, service request is sent to by the affiliated exchange opportunity of master controller
Spare controller, the spare controller pass through each control in daily maintenance information table according to the exchanger information received
The affiliated exchanger information of device judges master controller fault, alternatively, company of the spare controller by judgement and each other controllers
The relationship of connecing determines master controller fault;Or
Other controllers are not when receiving master controller and spare controller message, then according to daily maintenance information table phase
It mutually is attached application, if connection is normal, can confirm master controller and spare controller failure.
Further, when master controller judges that failed controller restores normally, to be then handed down to the failed controller information respectively
A controller, each controller judge whether there is the controller service by checking oneself internal trustship information, if so,
The controller is then sent information to, and reconstructs all information.
According to another aspect of the present invention, it is also proposed that a kind of controller failure standby system, comprising:
Fault recovery prioritization module is used for when master controller and normal spare controller, by failed controller
Priority be ranked up 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 row
Normal controller after sequence successively takes over the failed controller after sequence.
Further, the fault processing module is for judging that the maximum normal controller processing capacity of redundant processing capabilities is
The no failed controller current processing capabilities greater than highest priority, if so, the maximum normal control of the redundant processing capabilities
Device takes over the interchanger of the failed controller of the highest priority, the failed controller back-up processing knot of the highest priority
Beam, and sort again to normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until
All failed controllers are taken over;
Otherwise, the maximum normal controller of the redundant processing capabilities takes over the failed controller of the highest priority
Part interchanger, the remaining exchange of the failed controller of second largest normal controller adapter tube highest priority of redundant processing capabilities
Machine, and so on, back-up processing is completed until having taken over the interchanger of failed controller of highest priority, and again to normal
The sequence of controller redundant processing capabilities, starts the failed controller back-up processing of the second priority, until having taken over all events
Hinder controller.
Further, if the fault processing module is small for the smallest normal controller processing capacity of redundant processing capabilities
In failed controller current processing capabilities, the part interchanger of the normal controller taking over fault controller, back-up processing knot
Beam.
Further, breakdown judge module, for judge master controller and/or spare controller whether failure;
Failure analysis module, if spare controller is normal for master controller fault, by the spare controller
It is revised as master controller, the maximum controller of redundant processing capabilities in other normal controllers is revised as spare controller;Such as
Fruit master controller and spare controller all failures then modify the maximum controller of redundant processing capabilities in other normal controllers
For master controller, second largest controller of redundant processing capabilities is revised as spare controller;If the master controller is normal, but
Spare controller failure, then the maximum controller of redundant processing capabilities is revised as spare controller in other normal controllers.
Further, maintenance of information module is used for master controller periodic maintenance daily maintenance information table, and by the daily dimension
Shield information table issues other each controllers, and other each controllers will be related to the information of this domain master controller and spare controller
Issue affiliated interchanger;
Wherein, the content of the daily maintenance information table includes controller type, state, address information, priority, appraises and decides
Processing capacity, current processing capabilities, affiliated exchanger information and/or switch type.
Further, the breakdown judge module is used for when master controller is normal, and the exchange opportunity of failed controller is by industry
Business request is sent to master controller, and master controller will be belonging to controller in the exchanger information that received and daily maintenance information table
Exchanger information is matched, and judges failed controller, alternatively, master controller is not connected to determine by judging with the controller
The controller failure;
When master controller fault and when normal spare controller, service request is sent to by the affiliated exchange opportunity of master controller
Spare controller, the spare controller pass through each control in daily maintenance information table according to the exchanger information received
The affiliated exchanger information of device judges master controller fault, alternatively, company of the spare controller by judgement and each other controllers
The relationship of connecing determines master controller fault;Or
Other controllers are not when receiving master controller and spare controller message, then according to daily maintenance information table phase
It mutually is attached application, if connection is normal, can confirm master controller and spare controller failure.
Further, Failure Recovery Module, for judging that failed controller restores normal when master controller, then by the failure control
Device information processed is handed down to each controller, and each controller judges whether there is the control by checking oneself internal trustship information
Device business processed if so, then sending information to the controller, and reconstructs all information.
According to another aspect of the present invention, it is also proposed that a kind of controller failure standby system, comprising:
Breakdown judge module, for judge master controller and/or spare controller whether failure;
Failure analysis module, if spare controller is normal for master controller fault, by the spare controller
It is revised as master controller, the maximum controller of redundant processing capabilities in other normal controllers is revised as spare controller;Such as
Fruit master controller and spare controller all failures then modify the maximum controller of redundant processing capabilities in other normal controllers
For master controller, second largest controller of redundant processing capabilities is revised as spare controller;If the master controller is normal, but
Spare controller failure, then the maximum controller of redundant processing capabilities is revised as spare controller in other normal controllers.
Further, fault recovery prioritization module is used for when master controller and normal spare controller, by failure
The priority of controller is ranked up from big to small, and appraises and decides 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 row
Normal controller after sequence successively takes over the failed controller after sequence.
Further, the fault processing module is for judging that the maximum normal controller processing capacity of redundant processing capabilities is
The no failed controller current processing capabilities greater than highest priority, if so, the maximum normal control of the redundant processing capabilities
Device takes over the interchanger of the failed controller of the highest priority, the failed controller back-up processing knot of the highest priority
Beam, and sort again to normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, until
All failed controllers are taken over;
Otherwise, the maximum normal controller of the redundant processing capabilities takes over the failed controller of the highest priority
Part interchanger, the remaining exchange of the failed controller of second largest normal controller adapter tube highest priority of redundant processing capabilities
Machine, and so on, back-up processing is completed until having taken over the interchanger of failed controller of highest priority, and again to normal
The sequence of controller redundant processing capabilities, starts the failed controller back-up processing of the second priority, until having taken over all events
Hinder controller.
Further, if the fault processing module is small for the smallest normal controller processing capacity of redundant processing capabilities
In failed controller current processing capabilities, the part interchanger of the normal controller taking over fault controller, back-up processing knot
Beam.
Further, maintenance of information module is used for master controller periodic maintenance daily maintenance information table, and by the daily dimension
Shield information table issues other each controllers, and other each controllers will be related to the information of this domain master controller and spare controller
Issue affiliated interchanger;
Wherein, the content of the daily maintenance information table includes controller type, state, address information, priority, appraises and decides
Processing capacity, current processing capabilities, affiliated exchanger information and/or switch type.
Further, the breakdown judge module is used for when master controller is normal, and the exchange opportunity of failed controller is by industry
Business request is sent to master controller, and master controller will be belonging to controller in the exchanger information that received and daily maintenance information table
Exchanger information is matched, and judges failed controller, alternatively, master controller is not connected to determine by judging with the controller
The controller failure;
When master controller fault and when normal spare controller, service request is sent to by the affiliated exchange opportunity of master controller
Spare controller, the spare controller pass through each control in daily maintenance information table according to the exchanger information received
The affiliated exchanger information of device judges master controller fault, alternatively, company of the spare controller by judgement and each other controllers
The relationship of connecing determines master controller fault;Or
Other controllers are not when receiving master controller and spare controller message, then according to daily maintenance information table phase
It mutually is attached application, if connection is normal, can confirm master controller and spare controller failure.
Further, Failure Recovery Module, for judging that failed controller restores normal when master controller, then by the failure control
Device information processed is handed down to each controller, and each controller judges whether there is the control by checking oneself internal trustship information
Device business processed if so, then sending information to the controller, and reconstructs all information.
In the present invention, when master controller and normal spare controller, by the priority of failed controller from big to small into
Row sequence, and appraise and decide the current processing capabilities of each failed controller;By the redundant processing capabilities of normal controller from big to small into
Row sequence, and the failed controller after sequence is successively taken over according to the normal controller after sequence.Therefore, height can be preferentially ensured
Hierarchical network service response gives client to provide differentiated service, promotes customer perception, and then improves internet security and reliable
Property.
By referring to the drawings to the detailed description of exemplary embodiment of the present invention, other feature of the invention and its
Advantage will become apparent.
Detailed description of the invention
The attached drawing for constituting part of specification describes the embodiment of the present invention, and together with the description for solving
Release the principle of the present invention.
The present invention can be more clearly understood according to following detailed description referring to attached drawing, in which:
Fig. 1 is the flow diagram of one embodiment of controller failure backup method of the present invention.
Fig. 2 is the flow diagram of another embodiment of controller failure backup method of the present invention.
Fig. 3 is the structural schematic diagram of one embodiment of controller failure standby system of the present invention.
Fig. 4 is the structure chart of one embodiment of the network of controller of the present invention composition.
Specific embodiment
Carry out the various exemplary embodiments of detailed description of the present invention now with reference to attached drawing.It should also be noted that unless in addition having
Body explanation, the unlimited system of component and the positioned opposite of step, numerical expression and the numerical value otherwise illustrated in these embodiments is originally
The range of invention.
Simultaneously, it should be appreciated that for ease of description, the size of various pieces shown in attached drawing is not according to reality
Proportionate relationship draw.
Be to the description only actually of at least one exemplary embodiment below it is illustrative, never as to the present invention
And its application or any restrictions used.
Technology, method and apparatus known to person of ordinary skill in the relevant may be not discussed in detail, but suitable
In the case of, the technology, method and apparatus should be considered as authorizing part of specification.
It is shown here and discuss all examples in, any occurrence should be construed as merely illustratively, without
It is as limitation.Therefore, the other examples of exemplary embodiment can have different values.
It should also be noted that similar label and letter indicate similar terms in following attached drawing, therefore, once a certain Xiang Yi
It is defined in a attached drawing, then in subsequent attached drawing does not need that it is further discussed.
To make the objectives, technical solutions, and advantages of the present invention clearer, below in conjunction with specific embodiment, and reference
Attached drawing, the present invention is described in more detail.
Fig. 1 is the flow diagram of one embodiment of controller failure backup method of the present invention.This method includes following
Step:
In step 110, when master controller and normal spare controller, by the priority of failed controller from big to small into
Row sequence, and appraise and decide the current processing capabilities of each failed controller.
In step 120, the redundant processing capabilities of normal controller are ranked up from big to small.
Wherein, redundant processing capabilities are that controller design processing capacity subtracts used processing capacity.
In step 130, the failed controller after sequence is successively taken over according to the normal controller after sequence.
Wherein, judge whether the maximum normal controller processing capacity of redundant processing capabilities is greater than the failure of highest priority
Controller current processing capabilities, if so, the maximum normal controller of the redundant processing capabilities takes over the highest priority
The failed controller back-up processing of the interchanger of failed controller, the highest priority terminates, and again to normal controller
Redundant processing capabilities sequence, starts the failed controller back-up processing of the second priority, until having taken over all Fault Controls
Device.
Otherwise, the maximum normal controller of the redundant processing capabilities takes over the failed controller of the highest priority
Part interchanger, the remaining exchange of the failed controller of second largest normal controller adapter tube highest priority of redundant processing capabilities
Machine, and so on, back-up processing is completed until having taken over the interchanger of failed controller of highest priority, and again to normal
The sequence of controller redundant processing capabilities, starts the failed controller back-up processing of the second priority, until having taken over all events
Hinder controller.
If processing is to the end, it is current that the smallest normal controller processing capacity of redundant processing capabilities is less than failed controller
Processing capacity, the part interchanger of the normal controller taking over fault controller, back-up processing terminate.
In this embodiment, when master controller and normal spare controller, by the priority of failed controller from greatly to
It is small to be ranked up, and appraise and decide the current processing capabilities of each failed controller;By the redundant processing capabilities of normal controller from greatly to
It is small to be ranked up, and the failed controller after sequence is successively taken over according to the normal controller after sequence.It therefore, can be according to event
Hinder priority, processing capacity preferentially ensures high-grade network service response, provides differentiated service to client, promotes client's sense
Know, and then improves internet security and reliability.
In addition, in order to make the affiliated interchanger of failed controller back up to domain as few as possible as far as possible, therefore take it
In distribution to the maximum controller of processing redundancy, the appearance of cross-domain calculating is reduced.If there is being originally a domain, but it is standby
When the case where becoming cross-domain calculating after part, the nodal information of same area can also be found out according to trustship information, to make it as far as possible
It is limited in the domain of the original same failed controller management and completes, less information interaction amount.
Fig. 2 is the flow diagram of another embodiment of controller failure backup method of the present invention.
In step 210, judge whether otherwise failure if so, thening follow the steps 220, executes step 230 to master controller.
In step 220, whether normal spare controller is judged, if so, thening follow the steps 240, otherwise, execute step 250.
In step 230, judge whether otherwise failure if so, thening follow the steps 260, executes step 210 to spare controller.
In step 240, the spare controller is revised as master controller, redundancy in other normal controllers is handled into energy
The maximum controller of power is revised as spare controller.
In step 250, the maximum controller of redundant processing capabilities in other normal controllers is revised as master controller, it is superfluous
Second largest controller of remaining processing capacity is revised as spare controller.
The maximum controller of redundant processing capabilities is revised as spare controller in step 260, other normal controllers.
Above-mentioned deterministic process be circulate operation, that is, monitor in real time primary, spare controller whether failure.If it is judged that master control
Device and spare controller processed are all normal, and when the failure of other controllers, then step 110 is continued to execute, i.e., according to failure control
The priority of device processed preferentially ensures high-grade network service response.
In this embodiment, using flexible controller backup scenario, primary, spare controller is elected automatically, guarantees the whole network
Primary controller and spare controller are existed simultaneously, reducing active and standby controller simultaneous faults causes the whole network information to be lost and network paralysis
The probability of paralysis, further improves internet security and reliability.
Another embodiment of the invention, master controller periodic maintenance daily maintenance information table, and by the daily maintenance
Information table issues other each controllers, and other each controllers send out the information for being related to this domain master controller and spare controller
To affiliated interchanger.
Wherein, the content of the daily maintenance information table includes controller type, state, address information, priority, appraises and decides
Processing capacity, current processing capabilities, affiliated exchanger information and/or switch type, as shown in the table:
If being set as local, refer to this controller control range, refers specifically to the detailed of the interchanger of each controller control
Thin information.If being set as master controller, refer to belonging to exchange fault when the master controller address that contacts.Master controller is completed
Spare controller distributes when breakdown judge and failure occur;If being set as spare controller, refer to the spare control of master controller
The second standby address that interchanger contacts in device and this subdomain;If being set as other, refers to and manage model in other controllers
It encloses.
Status information refers to each controller operating status;Address information refers to each controller address;Priority refers to affiliated subdomain
Business processing priority;Processing capacity is appraised and decided, refers to each controller design processing capacity;Current processing capabilities refer to each control
The current used processing capacity of device;Affiliated exchanger information refers to the switch address of each controller control;Switch type
If being set as this domain, refer to the interchanger (this domain or trustship) in this original domain, if being set as trustship, refers to as the management of other domains
Interchanger.
When master controller is normal, service request is sent to master controller, main control by the exchange opportunity of failed controller
Device matches the exchanger information received with exchanger information belonging to controller in daily maintenance information table, judges event
Hinder controller, alternatively, master controller is not connected to determine the controller failure by judgement with the controller.
When master controller fault and when normal spare controller, service request is sent to by the affiliated exchange opportunity of master controller
Spare controller, the spare controller pass through each control in daily maintenance information table according to the exchanger information received
The affiliated exchanger information of device judges master controller fault, alternatively, company of the spare controller by judgement and each other controllers
The relationship of connecing determines master controller fault.Or
Other controllers are not when receiving master controller and spare controller message, then according to daily maintenance information table phase
It mutually is attached application, if connection is normal, can confirm master controller and spare controller failure.
In this embodiment, by the way that daily maintenance information table, master controller periodic maintenance is arranged, and table is issued into other controls
Device processed.Other controllers will be related to the primary, spare controller information in this domain and issue affiliated interchanger, and each controller is according to daily maintenance
Information table can judge failed controller.
Another embodiment of the invention, when master controller judges that failed controller restores normal, then by the Fault Control
Device information is handed down to each controller, and each controller judges whether there is the control by checking oneself internal trustship information
Device business if so, then sending information to the controller, and reconstructs all information.
For example, failed controller C restores normal, master controller is normal to all controller notification controller C at this time, each
Controller checks the information table of oneself, some controller discovery at this time has the trustship of controller C to exchange in self information table
Machine, therefore controller C management is returned by the interchanger that master controller is directly related to controller C, information table is then updated again.
In this embodiment, at the end of failed controller failure, master controller passes through the friendship in daily maintenance information table
Trustship relationship of changing planes by during failure Internet resources and business establish information re-synchronization and further mentioned to other controllers
Internet security and reliability are risen.Also, the present invention is to the influence very little of existing net equipment, it is easy to affix one's name in existing wet end.
The present invention also provides a kind of controller failure backup methods, the i.e. process of corresponding diagram 2, are implemented by this method
Example, using flexible controller backup scenario, elects primary, spare controller automatically, guarantees that the whole network exists simultaneously primary controller
And spare controller, reducing active and standby controller simultaneous faults causes the whole network information to lose the probability with network paralysis, further mentions
Internet security and reliability are risen.Detailed process as shown in Fig. 2, be no longer described in detail herein.
Above-mentioned deterministic process be circulate operation, that is, monitor in real time primary, spare controller whether failure.If it is judged that master control
Device and spare controller processed are all normal, and when the failure of other controllers, then the process of Fig. 1 is continued to execute, i.e., according to failure
The priority of controller preferentially ensures high-grade network service response.Detailed process as shown in Figure 1, be no longer described in detail herein.
In this embodiment, when master controller and normal spare controller, by the priority of failed controller from greatly to
It is small to be ranked up, and appraise and decide the current processing capabilities of each failed controller;By the redundant processing capabilities of normal controller from greatly to
It is small to be ranked up, and the failed controller after sequence is successively taken over according to the normal controller after sequence.It therefore, can be according to event
Hinder priority, processing capacity preferentially ensures high-grade network service response, provides differentiated service to client, promotes client's sense
Know, and then improves internet security and reliability.
In addition, in order to make the affiliated interchanger of failed controller back up to domain as few as possible as far as possible, therefore take it
In distribution to the maximum controller of processing redundancy, the appearance of cross-domain calculating is reduced.If there is being originally a domain, but it is standby
When the case where becoming cross-domain calculating after part, the nodal information of same area can also be found out according to trustship information, to make it as far as possible
It is limited in the domain of the original same failed controller management and completes, less information interaction amount.
Wherein, master controller periodic maintenance daily maintenance information table, and the daily maintenance information table issued other each
The information for being related to this domain master controller and spare controller is issued affiliated interchanger by a controller, other each controllers.It is logical
Setting daily maintenance information table, master controller periodic maintenance are crossed, and table is issued into other controllers.Other controllers will be related to this
The primary, spare controller information in domain issues affiliated interchanger, and each controller can judge control of being out of order according to daily maintenance information table
Device processed.
If master controller and spare controller are all normal, other controllers break down, then according to failed controller
Priority preferentially ensures high-grade network service response, provides differentiated service to client, promotes customer perception, and then promoted
Internet security and reliability.
At the end of failed controller failure, master controller will by the interchanger trustship relationship in daily maintenance information table
Internet resources and business during failure establish information re-synchronization and further improve internet security to other controllers
And reliability.Also, the present invention is to the influence very little of existing net equipment, it is easy to affix one's name in existing wet end.
The specific operation process of the embodiment is embodied in above each embodiment, is no longer done herein specifically
It is bright.
Fig. 3 is the structural schematic diagram of one embodiment of controller failure standby system of the present invention.The system includes failure
Restore prioritization module 310 and fault processing module 320, in which:
Fault recovery prioritization module 310 is used for when master controller and normal spare controller, by Fault Control
The priority of device is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller.
Fault processing module 320, for the redundant processing capabilities of normal controller to be ranked up from big to small, and according to
Normal controller after sequence successively takes over the failed controller after sequence.
Wherein, redundant processing capabilities are that controller design processing capacity subtracts used processing capacity.
The fault processing module 320 is for judging whether the maximum normal controller processing capacity of redundant processing capabilities is big
In the failed controller current processing capabilities of highest priority, if so, the maximum normal controller of the redundant processing capabilities connects
The interchanger of the failed controller of the highest priority is managed, the failed controller back-up processing of the highest priority terminates,
And sort again to normal controller redundant processing capabilities, start the failed controller back-up processing of the second priority, Zhi Daojie
All failed controllers are managed.
Otherwise, the maximum normal controller of the redundant processing capabilities takes over the failed controller of the highest priority
Part interchanger, the remaining exchange of the failed controller of second largest normal controller adapter tube highest priority of redundant processing capabilities
Machine, and so on, back-up processing is completed until having taken over the interchanger of failed controller of highest priority, and again to normal
The sequence of controller redundant processing capabilities, starts the failed controller back-up processing of the second priority, until having taken over all events
Hinder controller.
If processing is to the end, it is current that the smallest normal controller processing capacity of redundant processing capabilities is less than failed controller
Processing capacity, the part interchanger of the normal controller taking over fault controller, back-up processing terminate.
In this embodiment, when master controller and normal spare controller, by the priority of failed controller from greatly to
It is small to be ranked up, and appraise and decide the current processing capabilities of each failed controller;By the redundant processing capabilities of normal controller from greatly to
It is small to be ranked up, and the failed controller after sequence is successively taken over according to the normal controller after sequence.It therefore, can be according to event
Hinder priority, processing capacity preferentially ensures high-grade network service response, provides differentiated service to client, promotes client's sense
Know, and then improves internet security and reliability.
In addition, in order to make the affiliated interchanger of failed controller back up to domain as few as possible as far as possible, therefore take it
In distribution to the maximum spare controller of processing redundancy, the appearance of cross-domain calculating is reduced.If there is being originally a domain,
But when the case where becoming cross-domain calculating after backing up, the nodal information of same area can also be found out according to trustship information, to keep it most
It may be limited in the domain of the original same failed controller management and complete, less information interaction amount.
Another embodiment of the invention, this system further include breakdown judge module 330 and failure analysis module 340.Its
In:
Breakdown judge module 330, for judge master controller and/or spare controller whether failure.
Failure analysis module 340, if spare controller is normal for master controller fault, by the spare control
Device is revised as master controller, and the maximum controller of redundant processing capabilities in other normal controllers is revised as spare controller;
If master controller and spare controller all failures repair the maximum controller of redundant processing capabilities in other normal controllers
It is changed to master controller, second largest controller of redundant processing capabilities is revised as spare controller;If the master controller is normal,
But spare controller failure, then the maximum controller of redundant processing capabilities is revised as spare controller in other normal controllers.
In this embodiment, using flexible controller backup scenario, primary, spare controller is elected automatically, is reduced active and standby
Controller simultaneous faults causes the whole network information to be lost and the probability of network paralysis, further improves internet security and reliable
Property.
Another embodiment of the invention, this system further include maintenance of information module 350, are used for master controller periodic maintenance
Daily maintenance information table, and the daily maintenance information table is issued into other each controllers, other each controllers will be related to
The information of this domain master controller and spare controller issues affiliated interchanger.
Wherein, the content of the daily maintenance information table includes controller type, state, address information, priority, appraises and decides
Processing capacity, current processing capabilities, affiliated exchanger information and/or switch type, as shown in the table:
If being set as local, refer to this controller control range, refers specifically to the detailed of the interchanger of each controller control
Thin information.If being set as master controller, refer to belonging to exchange fault when the master controller address that contacts.Master controller is completed
Spare controller distributes when breakdown judge and failure occur;If being set as spare controller, refer to the spare control of master controller
The second standby address that interchanger contacts in device and this subdomain;If being set as other, refers to and manage model in other controllers
It encloses.
Status information refers to each controller operating status;Address information refers to each controller address;Priority refers to affiliated subdomain
Business processing priority;Processing capacity is appraised and decided, refers to each controller design processing capacity;Current processing capabilities refer to each control
The current used processing capacity of device;Affiliated exchanger information refers to the switch address of each controller control;Switch type
If being set as this domain, refer to the interchanger (this domain or trustship) in this original domain, if being set as trustship, refers to as the management of other domains
Interchanger.
Maintenance of information module 350 complete daily maintenance information table maintenance, in time with the information mutual communication of master controller, it is ensured that
The accuracy and timeliness of information.
When master controller is normal, service request is sent to master controller, main control by the exchange opportunity of failed controller
Device matches the exchanger information received with exchanger information belonging to controller in daily maintenance information table, judges event
Hinder controller, alternatively, master controller is not connected to determine the controller failure by judgement with the controller.
When master controller fault and when normal spare controller, service request is sent to by the affiliated exchange opportunity of master controller
Spare controller, the spare controller pass through each control in daily maintenance information table according to the exchanger information received
The affiliated exchanger information of device judges master controller fault, alternatively, company of the spare controller by judgement and each other controllers
The relationship of connecing determines master controller fault.Or
Other controllers are not when receiving master controller and spare controller message, then according to daily maintenance information table phase
It mutually is attached application, if connection is normal, can confirm master controller and spare controller failure.
In this embodiment, by the way that daily maintenance information table, master controller periodic maintenance is arranged, and table is issued into other controls
Device processed.Other controllers will be related to the primary, spare controller information in this domain and issue affiliated interchanger, and each controller is according to daily maintenance
Information table can judge failed controller.
Another embodiment of the invention, the system further include Failure Recovery Module 360, for when master controller judgement event
Hinder controller and restore normal, then the failed controller information is handed down to each controller, each controller is by checking oneself
Internal trustship information, judges whether there is the controller service, if so, then sending information to the controller, and reconstructs institute
There is information.
For example, failed controller C restores normal, master controller is normal to all controller notification controller C at this time, each
Controller checks the information table of oneself, some controller discovery at this time has the trustship of controller C to exchange in self information table
Machine, therefore controller C management is returned by the interchanger that master controller is directly related to controller C, information table is then updated again.
In this embodiment, at the end of failed controller failure, master controller passes through the friendship in daily maintenance information table
Trustship relationship of changing planes by during failure Internet resources and business establish information re-synchronization and further mentioned to other controllers
Internet security and reliability are risen.Also, the present invention is to the influence very little of existing net equipment, it is easy to affix one's name in existing wet end.
The present invention also provides a kind of controller failure standby system, which can be as shown in Figure 3.It is at this
In system, breakdown judge module 330 and failure analysis module 340 elect primary, spare controller automatically, guarantee that the whole network exists simultaneously master
With controller and spare controller, reducing active and standby controller simultaneous faults causes the whole network information to lose the probability with network paralysis,
Further improve internet security and reliability.Specific embodiment as described above, be no longer described in detail herein.
Above-mentioned deterministic process be circulate operation, that is, monitor in real time primary, spare controller whether failure.If it is judged that master control
Device and spare controller processed are all normal, and when the failure of other controllers, then continue the priority according to failed controller, it is excellent
First ensure high-grade network service response.Specific embodiment as described above, be no longer described in detail herein.
In this embodiment, when master controller and normal spare controller, by the priority of failed controller from greatly to
It is small to be ranked up, and appraise and decide the current processing capabilities of each failed controller;By the redundant processing capabilities of normal controller from greatly to
It is small to be ranked up, and the failed controller after sequence is successively taken over according to the normal controller after sequence.It therefore, can be according to event
Hinder priority, processing capacity preferentially ensures high-grade network service response, provides differentiated service to client, promotes client's sense
Know, and then improves internet security and reliability.
In addition, in order to make the affiliated interchanger of failed controller back up to domain as few as possible as far as possible, therefore take it
In distribution to the maximum controller of processing redundancy, the appearance of cross-domain calculating is reduced.If there is being originally a domain, but it is standby
When the case where becoming cross-domain calculating after part, the nodal information of same area can also be found out according to trustship information, to make it as far as possible
It is limited in the domain of the original same failed controller management and completes, less information interaction amount.
Wherein, maintenance of information module 350 is used for master controller periodic maintenance daily maintenance information table, and by the daily dimension
Shield information table issues other each controllers, and other each controllers will be related to the information of this domain master controller and spare controller
Issue affiliated interchanger.By the way that daily maintenance information table, master controller periodic maintenance is arranged, and table is issued into other controllers.
Other controllers will be related to the primary, spare controller information in this domain and issue affiliated interchanger, and each controller is according to daily maintenance information
Table can judge failed controller.
If master controller and spare controller are all normal, other controllers break down, then fault processing module 320
According to fault recovery prioritization module 310 to the priority ranking of failed controller, preferentially ensure that high-grade network service is rung
It answers, provides differentiated service to client, promote customer perception, and then improve internet security and reliability.
At the end of failed controller failure, Failure Recovery Module 360 passes through daily maintenance information table for master controller
In interchanger trustship relationship by during failure Internet resources and business establish information re-synchronization to other controllers, into one
Step, improves internet security and reliability.Also, the present invention is to the influence very little of existing net equipment, it is easy to affix one's name in existing wet end.
The specific operation process of the embodiment is embodied in above each embodiment, is no longer done herein specifically
It is bright.
The present invention will be described further with a specific embodiment below.
As shown in figure 4, wherein controller A is elected as master controller, controller B in the network of controller A-F composition
It is elected as spare controller, then daily maintenance information table is respectively the following contents in each controller:
1), controller A (master):
2), controller B (spare)
3), controller C
4), controller D
5), controller E
6), controller F
When master controller and spare master controller are normal, when other controller failures, master controller restores priority first
High failed controller obtains its current processing capabilities;By state, normally all controllers appraise and decide processing energy to master controller
Power and current processing capabilities obtain each alternate controller redundant processing capabilities;And by the maximum controller of redundant processing capabilities with
Failed controller current processing capabilities comparison match obtains backup controller list, and failure is issued in backup controller address
The affiliated interchanger of controller subdomain completes adapter tube.
Such as controller C/D/F simultaneous faults, first compare priority, find controller priority D > C > F, then first considers backup
Controller D.
1) backup of controller D
Controller A is 10, B 15, E 10, is arranged according to redundancy backup ability by the controller to backup is prepared are as follows: B/
A/E, that is, paying the utmost attention to B is backup controller.
And it is 8 that the current processing capabilities of failed controller, which are respectively as follows: D, at this time, therefore has backup scenario are as follows: in B adapter tube D
8 interchangers, therefore the back-up processing of D terminates.
At this point, the information of controller B becomes:
2) backup of controller C
In order to prepare the backup to controller C, it can be found that it is 10, B 7, E that controller redundancy backup ability, which is A, at this time
It is 10, is arranged according to redundancy backup ability by the controller to backup is prepared are as follows: A/E/B, that is, paying the utmost attention to A is Standby control
Device.
And it is 15 that the current processing capabilities of failed controller, which are respectively as follows: C, at this time, therefore backup scenario are as follows: in A adapter tube C
10 interchangers, 5 interchangers in E adapter tube C, the back-up processing of this controller C terminate.
The information of controller A and E becomes at this time:
Controller A information are as follows:
Controller E information are as follows:
3) backup of controller F
In order to prepare the backup to controller F, it can be found that it is 5, B 7 that controller redundancy backup ability, which is E, at this time, this
When failed controller F current processing capabilities be 6, therefore 6 interchangers in B adapter tube F, the back-up processing knot of this controller F
Beam.
Controller B information at this time are as follows:
When master controller and spare controller simultaneous faults, other each controllers, which interact, to be appraised and decided and currently processed energy
Power, the maximum controller of redundancy announce itself for master controller, at this point, daily by the master controller reconstruct after election
Safeguard information table, maximum redundant processing capabilities of the declaration in addition to itself are spare controller, and obtain backup controller, are backed up
Process is as described above.
At the end of failed controller failure, master controller will by the interchanger trustship relationship in daily maintenance information table
Internet resources and business during failure establish information re-synchronization to other controllers.If failed controller C restores normal, this
When master controller it is normal to all controller notification controller C, each controller checks the daily maintenance information table of oneself, at this time
Controller A and E have found in self information table, have the trustship interchanger of controller C, therefore be directly related to control by master controller
The interchanger of device C processed returns controller C management, then updates information table again.
So far, the present invention is described in detail.In order to avoid covering design of the invention, it is public that this field institute is not described
The some details known.Those skilled in the art as described above, completely it can be appreciated how implementing technology disclosed herein
Scheme.
Method and device of the invention may be achieved in many ways.For example, can by software, hardware, firmware or
Person's software, hardware, firmware any combination realize method and device of the invention.The step of for the method it is above-mentioned
Sequence is merely to be illustrated, and the step of method of the invention is not limited to sequence described in detail above, unless with other sides
Formula illustrates.In addition, in some embodiments, the present invention can be also embodied as recording program in the recording medium, these
Program includes for realizing machine readable instructions according to the method for the present invention.Thus, the present invention also covers storage for executing
The recording medium of program according to the method for the present invention.
Although some specific embodiments of the invention are described in detail by example, the skill of this field
Art personnel it should be understood that above example merely to being illustrated, the range being not intended to be limiting of the invention.The skill of this field
Art personnel are it should be understood that can without departing from the scope and spirit of the present invention modify to above embodiments.This hair
Bright range is defined by the following claims.
Claims (24)
1. a kind of controller failure backup method, comprising:
When master controller and normal spare controller, 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 are ranked up from big to small, and are successively connect according to the normal controller after sequence
Failed controller after pipe sequence;
Master controller periodic maintenance daily maintenance information table, and the daily maintenance information table is issued into other each controllers,
The information for being related to this domain master controller and spare controller is issued affiliated interchanger by other each controllers;Wherein, the day
Often the content of maintenance information table includes controller type, state, address information, priority, appraises and decides processing capacity, currently processed energy
Power, affiliated exchanger information and/or switch type.
2. controller failure backup method according to claim 1, comprising:
The failed controller for judging whether the maximum normal controller processing capacity of redundant processing capabilities is greater than highest priority is worked as
Pre-treatment ability, if so, the maximum normal controller of the redundant processing capabilities takes over the Fault Control of the highest priority
The failed controller back-up processing of the interchanger of device, the highest priority terminates, and again to the processing of normal controller redundancy
Ability sequence, starts the failed controller back-up processing of the second priority, until having taken over all failed controllers;
Otherwise, the maximum normal controller of the redundant processing capabilities takes over the part of the failed controller of the highest priority
Interchanger, the remaining switch of the failed controller of second largest normal controller adapter tube highest priority of redundant processing capabilities,
And so on, back-up processing is completed until having taken over the interchanger of failed controller of highest priority, and again to normal control
Device redundant processing capabilities sequence processed, starts the failed controller back-up processing of the second priority, until having taken over all failures
Controller.
3. controller failure backup method according to claim 2, comprising:
If the smallest normal controller processing capacity of redundant processing capabilities be less than failed controller current processing capabilities, it is described just
The part interchanger of normal controller taking over fault controller, back-up processing terminate.
4. controller failure backup method according to any one of claims 1 to 3, comprising:
Judge master controller whether failure, if so, judging whether spare controller normal, if so, by the spare control
Device is revised as master controller, and the maximum controller of redundant processing capabilities in other normal controllers is revised as spare controller,
Otherwise, the maximum controller of redundant processing capabilities in other normal controllers is revised as master controller, redundant processing capabilities
Two big controllers are revised as spare controller;
If the master controller is normal, but spare controller failure, then redundant processing capabilities are maximum in other normal controllers
Controller be revised as spare controller.
5. controller failure backup method according to claim 1, comprising:
When master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, and master controller will
The exchanger information received is matched with exchanger information belonging to controller in daily maintenance information table, judges control of being out of order
Device processed, alternatively, master controller is not connected to determine the controller failure by judgement with the controller;
When master controller fault and when normal spare controller, service request is sent to spare by the affiliated exchange opportunity of master controller
Controller, the spare controller pass through controller each in daily maintenance information table institute according to the exchanger information received
Belong to exchanger information and judge master controller fault, alternatively, spare controller is closed by judgement and the connection of each other controllers
It is to determine master controller fault;Or
Other controllers when not receiving master controller and spare controller message, then according to daily maintenance information table mutually into
Row connection application can confirm master controller and spare controller failure if connection is normal.
6. controller failure backup method according to any one of claims 1 to 3, comprising:
When master controller judges that failed controller restores normally, then the failed controller information to be handed down to each controller, respectively
A controller judges whether there is the controller service, if so, then sending information by checking oneself internal trustship information
The controller is given, and reconstructs all information.
7. a kind of controller failure backup method, comprising:
Judge master controller whether failure, if so, judging whether spare controller normal, if so, by the spare control
Device is revised as master controller, and the maximum controller of redundant processing capabilities in other normal controllers is revised as spare controller,
Otherwise, the maximum controller of redundant processing capabilities in other normal controllers is revised as master controller, redundant processing capabilities
Two big controllers are revised as spare controller;
If the master controller is normal, but spare controller failure, then redundant processing capabilities are maximum in other normal controllers
Controller be revised as spare controller;
Master controller periodic maintenance daily maintenance information table, and the daily maintenance information table is issued into other each controllers,
The information for being related to this domain master controller and spare controller is issued affiliated interchanger by other each controllers;Wherein, the day
Often the content of maintenance information table includes controller type, state, address information, priority, appraises and decides processing capacity, currently processed energy
Power, affiliated exchanger information and/or switch type.
8. controller failure backup method according to claim 7, further includes:
When master controller and normal spare controller, 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 are ranked up from big to small, and are successively connect according to the normal controller after sequence
Failed controller after pipe sequence.
9. controller failure backup method according to claim 8, comprising:
The failed controller for judging whether the maximum normal controller processing capacity of redundant processing capabilities is greater than highest priority is worked as
Pre-treatment ability, if so, the maximum normal controller of the redundant processing capabilities takes over the Fault Control of the highest priority
The failed controller back-up processing of the interchanger of device, the highest priority terminates, and again to the processing of normal controller redundancy
Ability sequence, starts the failed controller back-up processing of the second priority, until having taken over all failed controllers;
Otherwise, the maximum normal controller of the redundant processing capabilities takes over the part of the failed controller of the highest priority
Interchanger, the remaining switch of the failed controller of second largest normal controller adapter tube highest priority of redundant processing capabilities,
And so on, back-up processing is completed until having taken over the interchanger of failed controller of highest priority, and again to normal control
Device redundant processing capabilities sequence processed, starts the failed controller back-up processing of the second priority, until having taken over all failures
Controller.
10. controller failure backup method according to claim 9, comprising:
If the smallest normal controller processing capacity of redundant processing capabilities be less than failed controller current processing capabilities, it is described just
The part interchanger of normal controller taking over fault controller, back-up processing terminate.
11. controller failure backup method according to claim 7, comprising:
When master controller is normal, service request is sent to master controller by the exchange opportunity of failed controller, and master controller will
The exchanger information received is matched with exchanger information belonging to controller in daily maintenance information table, judges control of being out of order
Device processed, alternatively, master controller is not connected to determine the controller failure by judgement with the controller;
When master controller fault and when normal spare controller, service request is sent to spare by the affiliated exchange opportunity of master controller
Controller, the spare controller pass through controller each in daily maintenance information table institute according to the exchanger information received
Belong to exchanger information and judge master controller fault, alternatively, spare controller is closed by judgement and the connection of each other controllers
It is to determine master controller fault;Or
Other controllers when not receiving master controller and spare controller message, then according to daily maintenance information table mutually into
Row connection application can confirm master controller and spare controller failure if connection is normal.
12. according to any controller failure backup method of claim 7 to 11, comprising:
When master controller judges that failed controller restores normally, then the failed controller information to be handed down to each controller, respectively
A controller judges whether there is the controller service, if so, then sending information by checking oneself internal trustship information
The controller is given, and reconstructs all information.
13. a kind of controller failure standby system, comprising:
Fault recovery prioritization module is used for when master controller and normal spare controller, by the excellent of failed controller
First grade is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller;
Fault processing module, for the redundant processing capabilities of normal controller to be ranked up from big to small, and according to sequence after
Normal controller successively take over sequence after failed controller;
Maintenance of information module is used for master controller periodic maintenance daily maintenance information table, and the daily maintenance information table is sent out
To other each controllers, the information for being related to this domain master controller and spare controller is issued affiliated friendship by other each controllers
It changes planes;Wherein, the content of the daily maintenance information table includes controller type, state, address information, priority, appraises and decides place
Reason ability, current processing capabilities, affiliated exchanger information and/or switch type.
14. controller failure standby system according to claim 13, comprising:
The fault processing module is for judging whether the maximum normal controller processing capacity of redundant processing capabilities is greater than preferentially
The highest failed controller current processing capabilities of grade, if so, described in the maximum normal controller adapter tube of the redundant processing capabilities
The failed controller back-up processing of the interchanger of the failed controller of highest priority, the highest priority terminates, and again
It sorts to normal controller redundant processing capabilities, starts the failed controller back-up processing of the second priority, until having taken over
Some failed controllers;
Otherwise, the maximum normal controller of the redundant processing capabilities takes over the part of the failed controller of the highest priority
Interchanger, the remaining switch of the failed controller of second largest normal controller adapter tube highest priority of redundant processing capabilities,
And so on, back-up processing is completed until having taken over the interchanger of failed controller of highest priority, and again to normal control
Device redundant processing capabilities sequence processed, starts the failed controller back-up processing of the second priority, until having taken over all failures
Controller.
15. controller failure standby system according to claim 14, comprising:
If the fault processing module is less than Fault Control for the smallest normal controller processing capacity of redundant processing capabilities
Device current processing capabilities, the part interchanger of the normal controller taking over fault controller, back-up processing terminate.
16. 3 to 15 any controller failure standby system according to claim 1, further includes:
Breakdown judge module, for judge master controller and/or spare controller whether failure;
Failure analysis module modifies the spare controller if spare controller is normal for master controller fault
For master controller, the maximum controller of redundant processing capabilities in other normal controllers is revised as spare controller;If main
Controller and spare controller all failures, then will be based on the maximum controller modification of redundant processing capabilities in other normal controllers
Controller, second largest controller of redundant processing capabilities are revised as spare controller;If the master controller is normal, but spare
Controller failure, then the maximum controller of redundant processing capabilities is revised as spare controller in other normal controllers.
17. controller failure standby system according to claim 16, comprising:
The breakdown judge module is used for when master controller is normal, and service request is sent to by the exchange opportunity of failed controller
Master controller, master controller by exchanger information belonging to controller in the exchanger information received and daily maintenance information table into
Row matching, judges failed controller, alternatively, master controller is not connected to determine controller event with the controller by judgement
Barrier;
When master controller fault and when normal spare controller, service request is sent to spare by the affiliated exchange opportunity of master controller
Controller, the spare controller pass through controller each in daily maintenance information table institute according to the exchanger information received
Belong to exchanger information and judge master controller fault, alternatively, spare controller is closed by judgement and the connection of each other controllers
It is to determine master controller fault;Or
Other controllers when not receiving master controller and spare controller message, then according to daily maintenance information table mutually into
Row connection application can confirm master controller and spare controller failure if connection is normal.
18. 3 to 15 any controller failure standby system according to claim 1, comprising:
Failure Recovery Module then will be under the failed controller information for judging that failed controller restores normal when master controller
Each controller is issued, each controller judges whether there is the controller service, such as by checking oneself internal trustship information
Fruit has, then sends information to the controller, and reconstructs all information.
19. a kind of controller failure standby system, comprising:
Breakdown judge module, for judge master controller and/or spare controller whether failure;
Failure analysis module modifies the spare controller if spare controller is normal for master controller fault
For master controller, the maximum controller of redundant processing capabilities in other normal controllers is revised as spare controller;If main
Controller and spare controller all failures, then will be based on the maximum controller modification of redundant processing capabilities in other normal controllers
Controller, second largest controller of redundant processing capabilities are revised as spare controller;If the master controller is normal, but spare
Controller failure, then the maximum controller of redundant processing capabilities is revised as spare controller in other normal controllers;
Maintenance of information module is used for master controller periodic maintenance daily maintenance information table, and the daily maintenance information table is sent out
To other each controllers, the information for being related to this domain master controller and spare controller is issued affiliated friendship by other each controllers
It changes planes;Wherein, the content of the daily maintenance information table includes controller type, state, address information, priority, appraises and decides place
Reason ability, current processing capabilities, affiliated exchanger information and/or switch type.
20. controller failure standby system according to claim 19, further includes:
Fault recovery prioritization module is used for when master controller and normal spare controller, by the excellent of failed controller
First grade is ranked up from big to small, and appraises and decides the current processing capabilities of each failed controller;
Fault processing module, for the redundant processing capabilities of normal controller to be ranked up from big to small, and according to sequence after
Normal controller successively take over sequence after failed controller.
21. controller failure standby system according to claim 20, comprising:
The fault processing module is for judging whether the maximum normal controller processing capacity of redundant processing capabilities is greater than preferentially
The highest failed controller current processing capabilities of grade, if so, described in the maximum normal controller adapter tube of the redundant processing capabilities
The failed controller back-up processing of the interchanger of the failed controller of highest priority, the highest priority terminates, and again
It sorts to normal controller redundant processing capabilities, starts the failed controller back-up processing of the second priority, until having taken over
Some failed controllers;
Otherwise, the maximum normal controller of the redundant processing capabilities takes over the part of the failed controller of the highest priority
Interchanger, the remaining switch of the failed controller of second largest normal controller adapter tube highest priority of redundant processing capabilities,
And so on, back-up processing is completed until having taken over the interchanger of failed controller of highest priority, and again to normal control
Device redundant processing capabilities sequence processed, starts the failed controller back-up processing of the second priority, until having taken over all failures
Controller.
22. controller failure standby system according to claim 21, comprising:
If the fault processing module is less than Fault Control for the smallest normal controller processing capacity of redundant processing capabilities
Device current processing capabilities, the part interchanger of the normal controller taking over fault controller, back-up processing terminate.
23. controller failure standby system according to claim 19, comprising:
The breakdown judge module is used for when master controller is normal, and service request is sent to by the exchange opportunity of failed controller
Master controller, master controller by exchanger information belonging to controller in the exchanger information received and daily maintenance information table into
Row matching, judges failed controller, alternatively, master controller is not connected to determine controller event with the controller by judgement
Barrier;
When master controller fault and when normal spare controller, service request is sent to spare by the affiliated exchange opportunity of master controller
Controller, the spare controller pass through controller each in daily maintenance information table institute according to the exchanger information received
Belong to exchanger information and judge master controller fault, alternatively, spare controller is closed by judgement and the connection of each other controllers
It is to determine master controller fault;Or
Other controllers when not receiving master controller and spare controller message, then according to daily maintenance information table mutually into
Row connection application can confirm master controller and spare controller failure if connection is normal.
24. 9 to 23 any controller failure standby system according to claim 1, comprising:
Failure Recovery Module then will be under the failed controller information for judging that failed controller restores normal when master controller
Each controller is issued, each controller judges whether there is the controller service, such as by checking oneself internal trustship information
Fruit has, then sends information to the controller, and reconstructs all information.
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 CN105812161A (en) | 2016-07-27 |
CN105812161B true 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) |
Families Citing this family (6)
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 |
CN106972964B (en) * | 2017-03-27 | 2019-11-22 | 北京邮电大学 | A kind of restoration methods of SDN network system and its controller failure |
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 |
CN115933565B (en) * | 2022-12-23 | 2023-10-20 | 广东职业技术学院 | AGV task exchange method, device, system and medium |
Citations (5)
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 |
-
2014
- 2014-12-31 CN CN201410850673.6A patent/CN105812161B/en active Active
Patent Citations (5)
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 |
Also Published As
Publication number | Publication date |
---|---|
CN105812161A (en) | 2016-07-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN105812161B (en) | A kind of controller failure backup method and system | |
CN105187249B (en) | A kind of fault recovery method and device | |
CN105406980B (en) | A kind of multinode backup method and device | |
CN105337780B (en) | A kind of server node configuration method and physical node | |
CN104158707B (en) | A kind of method and apparatus for detecting and handling cluster fissure | |
US8880703B2 (en) | Address distribution method, device and system thereof | |
CN102882704B (en) | Link protection method in the soft reboot escalation process of a kind of ISSU and equipment | |
CN106301952A (en) | A kind of SDN datum plane link backup method and device | |
CN103199972A (en) | Double machine warm backup switching method and warm backup system achieved based on SOA and RS485 bus | |
CN104137477A (en) | Technique for handling a status change in an interconnect node | |
WO2019128670A1 (en) | Method and apparatus for enabling self-recovery of management capability in distributed system | |
CN105516292A (en) | Hot standby method of cloud platform of intelligent substation | |
CN104317803A (en) | Data access structure and method of database cluster | |
CN103441863A (en) | Double-server hot standby system in blank pipe automatic system and control method thereof | |
CN109194514A (en) | A kind of two-shipper monitoring method, device, server and storage medium | |
US10929254B2 (en) | Data processing system providing service continuity protection | |
CN108847879A (en) | Two-shipper fault detection and restoration methods based on bus control unit | |
CN109842505A (en) | A kind of cloud clustering fault processing method and processing device | |
CN106713132B (en) | Method and apparatus for updating forwarding table entry | |
CN105915426A (en) | Failure recovery method and device of ring network | |
CN114338670B (en) | Edge cloud platform and network-connected traffic three-level cloud control platform with same | |
JP5647561B2 (en) | Power system supervisory control system | |
CN105490847B (en) | A kind of private cloud storage system interior joint failure real-time detection and processing method | |
WO2024179146A1 (en) | Traffic scheduling method and apparatus, electronic device, and storage medium | |
CN108445857B (en) | Design method for 1+ N redundancy mechanism of SCADA system |
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 |