CN101001165A - Network failure recovery method with redundancy port - Google Patents
Network failure recovery method with redundancy port Download PDFInfo
- Publication number
- CN101001165A CN101001165A CN 200610000565 CN200610000565A CN101001165A CN 101001165 A CN101001165 A CN 101001165A CN 200610000565 CN200610000565 CN 200610000565 CN 200610000565 A CN200610000565 A CN 200610000565A CN 101001165 A CN101001165 A CN 101001165A
- Authority
- CN
- China
- Prior art keywords
- port
- node
- bridge
- spanning
- root
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Abstract
This invention relates to a method for resuming network fault with redundant ports including: 1, operating and setting tree-generation protocol on a switch bridge node and a terminal node with a redundant port, 2, setting that the PRI of all end nodes is smaller than that of the switch bridge node or setting the medium access MAC address of the switch bridge node is smaller than that of the end nodes, 3, when the root port of an end node is faulty, the redundant port is changed to a root port to enter into the transmitting state by computing the generation tree operated on said end node to realize switch of redundant ports on the end nodes, further more, this invention carries out software hierarchy fault detection between end node and switch bridge node by the communication system of the generation tree.
Description
Technical field
The present invention relates to network communication field, relate in particular to the network failure recovery method of local area network (LAN) whole network with redundancy port.
Background technology
Along with popularizing of Ethernet, the Ethernet widespread usage is in a lot of fields.See also Fig. 1, it is the Principles of Network figure of an Ethernet local area network (LAN).This local area network (LAN) comprises swap bridge node 11 and some end nodes 12.Swap bridge node 11 can be the network equipment that realization local area network (LAN)s such as bridge, switch, router and external equipment or network carry out exchanges data.End node 12 can be finished the equipment of certain or some function (as finishing data computation, data communication) for terminal, the minicomputer of local area network (LAN) inside or the special-purpose integrated circuit board with ether communication port etc.
In order to improve availability and fail safe, require the equipment in the local area network (LAN) to have the failure tolerant ability usually, particularly when the Application for Field such as telecommunications that have high availability to require, therefore provide redundant hardware device and communication port in local area network (LAN) inside.As shown in Figure 2, this local area network (LAN) comprises two swap bridge nodes 11, and end node can adopt the have redundancy port end node 12 of (first port and second port).When breaking down with a certain swap bridge node in the swap bridge node 11, can take over the work of the swap bridge node that breaks down by another swap bridge node, improve the fail safe of whole network with this.Equally, when the main port of end node breaks down, can use redundancy port to proceed the data communication of end node and other network equipment.
But the local area network (LAN) with ethernet node redundancy port forms the physics loop easily, is example with Fig. 2 still, and first port of swap bridge node 1, end node 1, second port and swap bridge node 2 form the physics loop easily.The physical rings appearance of a street easily causes the damage of whole broadcasting loop and bridge table, thereby causes the paralysis of whole network.For fear of the physics loop occurring, need on swap bridge node and end node, increase off-gauge software setting.Equally, in the fault detect and failover procedure of whole network, for fear of the physics loop occurring, self-defined software handshake mechanism or other software failure recovery mechanism on swap bridge node and end node.
The normal whole network fault handling method that adopts of local area network (LAN) with ethernet side node redundancy port is:
A1: carry out fault detect and fault recovery by standard agreement between the swap bridge node, as, swap bridge node 1 and swap bridge node 2 can be realized by the Spanning-Tree Protocol of standard, utilize the mechanism of agreement itself to determine active topology, block redundancy port.When protocol detection arrived fault, this protocol processing unit utilized the redundancy port of preservation to enter communicating by letter of activity topology recovery network of network with reserve link fast.Swap bridge node 1 and swap bridge node 2 also can adopt other mechanism, as utilize manual switchover mechanism to realize switching between swap bridge node 1 and the swap bridge node 2, overcome main swap bridge node in swap bridge node 1, the swap bridge node 2 and break down and cause the paralysis of whole network;
A2: adopt the hardware detection carrier signal to realize the detection of fault or utilize self-defining software protocol (as software handshake mechanism) to realize the detection of fault between swap bridge node and the end node, between the end node, utilize artificial pre-configured mode to solve fault again or self-defined software carries out the recovery of fault.Because the manual type underaction is convenient and recovery time is long, for fear of the physics loop occurring, self-defined software handshake mechanism or other software failure recovery mechanism are carried out failure diagnosis and fault recovery on swap bridge node and end node.There is following problem in it:
(1) all needs the software of self-defined fault recovery at the local area network (LAN) of each different network environments, not only the level to the technical staff requires very high, and whole software manufacturing process wastes time and energy very much, the most important, this software does not have versatility, only, can not be suitable for the local area network (LAN) that all have ethernet side node redundancy port at the specific non-constant of its autgmentability;
(2), adopt self-defined software to increase the also usually linear growth of the troubleshooting expense of swap bridge node peer node along with the end node number for the swap bridge node;
(3) realize fault recovery by software, need considering respectively with end node and define the swap bridge node, and produce control behavior thus to redundant hardware, enable/go the control operation that enables as redundancy port on the selection of swap bridge node or the end node, this kind action need is notified to the two-layer protocol of swap bridge node or the agreement control module of three layers of route, such two parts not only realize loaded down with trivial details, and the recovery time of fault is long.
Summary of the invention
The object of the present invention is to provide a kind of network failure recovery method with redundancy port, has the local area network (LAN) of ethernet side node redundancy port in the failover procedure of whole network to solve in the prior art, for fear of the physics loop occurring, self-defined software is realized on swap bridge node and end node, and then causes and waste time and energy and the technical problem of autgmentability, versatility difference.
For addressing the above problem, the invention discloses a kind of network failure recovery method with redundancy port, may further comprise the steps: (1) is at the swap bridge node and have and be provided with on the end node of redundancy port and the operation Spanning-Tree Protocol; (2) bridge priority that all end nodes are set is lower than the bridge priority of swap bridge node; Perhaps under the identical situation of bridge priority, the medium access control MAC Address of swap bridge node is provided with MAC Address less than each end node; (3) when breaking down on the link of the root port of end node or root port, utilize the Spanning-Tree Protocol of above-mentioned end node that redundancy port is become root port, enter forwarding state, the active-standby port of realizing having on the redundancy port end node switches, and recovers communication link.
Can detect on the link of the root port of end node or root port by following steps in the step (3) and break down: the root port of end node is not received bridge protocol data unit B PDU message in the predefined time.
Detect on the link of the root port of end node or root port by following steps in the step (3) and break down: end node according to the hardware that receives directly the fault message of report judge on the link of the root port of described end node or root port and break down.
Step (1) also comprises before: the port that each end node with redundancy port is set respectively with being connected of the port of different swap bridge nodes, and guarantee that the root bridging that end node and agreement are determined leads to.
Utilize the Spanning-Tree Protocol of described end node that redundancy port is generated root port in the step (3), and described port is entered forwarding state be specially: the conversion process of carrying out port status according to the Spanning-Tree Protocol that is provided with or BPDU consults to confirm alternately.
The conversion process of carrying out port status according to the Spanning-Tree Protocol that is provided with or BPDU consults to confirm alternately comprises: behind the process delay time, described root port is not received the BPDU message of root bridge transmission in the stand-by period after, described redundancy port is set at forwarding state, and be sent to the node of other operation Spanning-Tree Protocol in this local area network (LAN) by the configuration information that BPDU message breaks down former root port and former redundancy port is set at root port, so that form new generation tree.
The present invention also comprises: comprise the Spanning-Tree Protocol parameter of stand-by period and delay time according to Spanning-Tree Protocol default configuration values or setting, can pre-determine the recovery time that is spent of network failure.
Described Spanning-Tree Protocol version comprises Spanning-Tree Protocol STP, RSTP RSTP and many examples Spanning-Tree Protocol MISTP/ Multiple Spanning Tree Protocol MSTP.
Compared with prior art, the present invention has the following advantages: it is a bridge that the present invention will have the end node of redundancy port virtual, moves Spanning-Tree Protocol thereon.Like this, all swap bridge nodes and have the end node of redundancy port in the local area network (LAN) of the present invention all as bridge, move Spanning-Tree Protocol thereon, utilize Spanning-Tree Protocol to overcome to have end node and other swap bridge node of redundancy port to form the physics loop, and overcome in view of the above, even cause the defective of the paralysis of whole network because the physics loop brings the damage of whole broadcasting loop and bridge table.And, when breaking down, the communication of recovery system network as early as possible of may command management and utilization redundancy port.Simultaneously, also avoid carrying out the exploitation of self-defined software for the recovery of network failure, the versatility that has solved self-defined software thus is poor, the technical problem of autgmentability difference etc., also avoid simultaneously occurring along with the increasing of end node number, the troubleshooting expense of swap bridge node peer node is the technical problem of linear growth also.
The present invention is equally applicable to a processing in this respect than more complicated multilayer switching network system shown in Figure 2.
Description of drawings
Fig. 1 is the Principles of Network figure of Ethernet local area network (LAN) in the prior art;
Fig. 2 is the Principles of Network figure that has the Ethernet local area network (LAN) of redundancy port in the prior art;
Fig. 3 is the Ethernet local net network schematic diagram that shows Spanning-Tree Protocol;
Fig. 4 is the flow chart that the present invention has the network failure recovery method of redundancy port;
Fig. 5 is a network example figure of the network disaster recovery of the present invention with redundancy port.
Embodiment
Below in conjunction with accompanying drawing, specify the present invention.
Spanning-Tree Protocol is a kind of Ethernet two-layer protocol, finds the physics loop in the network and calculates the acyclic topological structure of a logic by a kind of algorithm of special use.Usually, Spanning-Tree Protocol only is used for the redundant link between the swap bridge node in the Control Network.
The basic thought of Spanning-Tree Protocol is very simple.The tree of occurring in nature growth is loop can not occur, just loop can not occur if network also can be grown as one tree.Therefore, root bridge (Root Bridge), root port (Root Port), designated port (Designated Port), path cost notions such as (Path Cost) have been defined in the Spanning-Tree Protocol, purpose with regard to be by construct one naturally the method for tree reach the purpose of the redundant loop of cutting, realize link backup and path optimization simultaneously.The algorithm that is used to construct this tree is called spanning tree algorithm SPA (Spanning Tree Algorithm).
Realize these functions, must carry out the interchange of some information between the bridge, these information interchange unit just are called BPDU (Bridge Protocol Data Unit, bridge protocol data unit) message.STPBPDU is a kind of two layer message, and purpose MAC (medium access control) address is multicast address 01-80-C2-00-00-00, and all support the bridge of Spanning-Tree Protocol all can receive and handle the BPDU message of receiving.Carried in the data field of this message and be used to generate all useful informations that tree is calculated.
Understand the course of work of Spanning-Tree Protocol and also be not difficult, at first carry out the election of root bridge.The foundation of election is the bridge ID (Bridge ID) that bridge priority and bridge MAC Address are combined into, and the bridge of bridge ID minimum will become the root bridge in the network.In network shown in Figure 3, each bridge all starts with default configuration, and for the highest, bridge id is made up of bridge priority and bridge MAC with the parameter priority of the bridge of bridge id minimum.Under the situation of bridge priority all the same (default priority is 32768), the bridge of MAC Address minimum becomes the root bridge, the SW1 among Fig. 3 for example, and the role of its all of the port becomes designated port, enters forwarding state.
Next, other bridges will select the branch of " the most sturdy " as the path to the root bridge separately, and the role of corresponding port just becomes root port.Suppose that the link between the SW2 and SW1, SW3 is a gigabit GE link among Fig. 3, link between SW1 and the SW3 is 100,000,000 FE links, the default value of the path cost of SW3 from port one to the root bridge is 19, and the path cost from port 2 process SW2 to the root bridge is 8, so the port 2 of SW3 becomes root port, enters forwarding state.In like manner, the port 2 of SW2 becomes root port, and port one becomes designated port, enters forwarding state.
One tree had just generated after root bridge and root port were all determined, shown in solid line among Fig. 3.Following task is the loop of cutting redundancy.This work realizes that by corresponding port on the obstruction nonroot bridge for example the role of the port one of SW3 becomes disabled ports, enters blocked state (representing with " * " among the figure).Generate tree after stable after a while, all of the port or enter forwarding state, or enter blocked state.STP BPDU still can be regularly sends from the designated port of each bridge, with the state of maintenance link.If network topology changes, generating tree will recomputate, and port status also can change thereupon.
Above-mentioned principle and characteristics based on Spanning-Tree Protocol, it is a bridge that the present invention will have the end node of redundancy port virtual, moves Spanning-Tree Protocol thereon.Like this, all swap bridge nodes and have the end node of redundancy port in the local area network (LAN) of the present invention all as bridge, move Spanning-Tree Protocol thereon, utilize Spanning-Tree Protocol to overcome to have end node and other swap bridge node of redundancy port to form the physics loop, and overcome in view of the above, even cause the defective of the paralysis of whole network because the physics loop brings the damage of whole broadcasting loop and bridge table.Simultaneously, also avoid carrying out the exploitation of self-defined software for the recovery of network failure.
See also Fig. 4, it is a kind of flow chart with network failure recovery method of redundancy port.It may further comprise the steps:
S110: at the swap bridge node with have and be provided with on the end node of redundancy port and the operation Spanning-Tree Protocol;
S120:, the bridge id of the virtual bridge id of all end nodes greater than the swap bridge node is set according to Spanning-Tree Protocol; Make the bridge id retention value of swap bridge node little, the Spanning-Tree Protocol parameter value on it has high priority.For example in the bridge id in Spanning-Tree Protocol, the bridge priority that all end nodes are set is lower than the bridge priority of swap bridge node; Perhaps under the identical situation of bridge priority, the medium access control MAC Address of swap bridge node is provided with MAC Address less than each end node;
S130: when breaking down on the link of the root port of end node or root port, utilize the Spanning-Tree Protocol of described end node that redundancy port is become root port, enter forwarding state, realize the switching of redundancy port on the end node, recover communication link.
Below specify each step.
One, step S110
Each has the end node of redundancy port and regards a virtual bridge node that has only two ports as, and the link on the end node between two links and two swap bridge nodes and the swap bridge node has just constituted a loop.The purpose of Spanning-Tree Protocol detects, eliminates redundant link preventing double-layer loop in the swap bridge network, and failover capability is provided.We utilize these characteristics that generate tree to eliminate on the physical node and form loop on two links and two swap bridge nodes, make on each end node one in two ports to be in forwarding state (main port), another one is in blocking state (redundancy port).
Consideration might be able to be simplified in the end node Spanning-Tree Protocol, can carry out the interactive instruction of swap bridge with the swap bridge node such as on end node, being provided with, be that end node is not necessarily leaveing no choice but move whole Spanning-Tree Protocol, can relevant interactive standards be arranged on end node get final product as the case may be.
Two, step S120
When realizing on the end node redundancy port troubleshooting, need the priority of swap bridge node in the reasonable disposition network and virtual bridge node based on above-mentioned thought.The priority of swap bridge node and end node is that the bridge ID according to swap bridge node and end node decides; Bridge ID is the field of one 8 byte, comprises a digital ordered pair, and the decimal number of two bytes is called bridge priority, back six MAC Address that byte is swap bridge node or bridge node.This value is to determine that default configuration is good when initialization before the Spanning-Tree Protocol operation.All virtual bridge nodes should not become the root bridge of network.Therefore, the priority of virtual bridge node is lower than the priority of any swap bridge node or with the MAC Address setting of all the virtual bridge nodes MAC Address greater than all swap bridge nodes, guarantee under any circumstance that with this virtual bridge node all can not become the root bridge of whole network.
Three, step S130
The present invention both can detect the fault that occurs on the link of the root port of end node or root port by hardware mode, also can detect the fault that occurs on the link of root port or root port by software mode (generating the tree mode).
If by hardware mode, then can according to hardware directly the fault message of report determine to break down on the link of root port or root port.And, this fault message can directly make the port of blocked state enter into listening state by Spanning-Tree Protocol, and in the time of determining, make the link of blocking state become the forwarding state, realized the switching of redundancy port on the end node that root port breaks down.
With the STP agreement is example, after the link that is in forwarding state breaks down, end node can detect and stop receiving BPDU on the port of forwarding state, fault Max Age (wait) occurs after the time, will force another port that is in blocked state to enter the port status processing procedure of changing to forwarding state, idiographic flow is relevant with the version that generates tree.Because can provide path from the root bridge to this node by this port now, it can become forwarding state gradually, becomes root port, realized the switching of redundancy port on the end node that root port breaks down.
No matter be by software mode or detect by hardware mode on the link of the root port of end node or root port and break down, the present invention can carry out network disaster recovery by Spanning-Tree Protocol.The detected fault of hardware mode can identify port failure by management interface, the handling process of the quick entry port state exchange of control Spanning-Tree Protocol.That is, the swap bridge node of each operation Spanning-Tree Protocol and end node form new generation tree by timed sending BPDU message.Such as:
The root port of end node is not received the BPDU message as the swap bridge node transmission of root bridge in the default stand-by period, then redundancy port is entered the port status processing procedure to the forwarding state conversion, the processing of idiographic flow and intermediateness is relevant with the version that generates tree.
As for the STP agreement, before forwarding state, be through intercepting and learn two states.Redundancy port is after through a default delay time, and described root port is not set at the state of intercepting with described redundancy port receive the BPDU message that the root bridge sends in the stand-by period after; After through a delay time of presetting, described root port is not set at learning state with described redundancy port receive the BPDU message of root bridge transmission in the stand-by period after;
When transmitting, delay through delay time, described root port is not received the BPDU message of root bridge transmission in the stand-by period after, described redundancy port is set at forwarding state, and be sent to the node of other operation Spanning-Tree Protocol in this local area network (LAN) by the configuration information that BPDU message breaks down former root port and former redundancy port is set at root port, so that form new generation tree.
By Spanning-Tree Protocol in end node operation standard, not only can realize the fault recovery of hardware carrier signal between end node and the swap bridge node, and can guarantee that each end node root bridge in the whole network must be communicated with, all can communicate by letter thereby satisfy between any two end nodes, do not need to define extra handshake mechanism end to end, expense on the end node is fixed like this, relevant with the own mechanism of using the Spanning-Tree Protocol different editions, do not have related with network size.
Below be example with Fig. 5, specify a specific embodiment of the present invention.
(1) on swap bridge node 1 and swap bridge node 2, moves Spanning-Tree Protocol.The bridge ID of swap bridge node 1 is set to 32768:00-00-00-00-00-01, and the bridge ID of swap bridge node 2 is set to 32768:00-00-00-00-00-02.
(2) network terminal end node NODE1, NODE2.。。。。。NODEn regards a virtual bridge node that has only two network interfaces as, and on each NODE node, move Spanning-Tree Protocol, the bridge ID of NODE1 is set to 36864:00-00-00-00-00-01, the bridge ID of NODE2 is set to 36864:00-00-00-00-00-02, and the bridge ID of NODEn is set to 36864:00-00-00-00-00-xx;
(3) at the port one of NODE1, port one on port 2 and the swap bridge node 1, in the loop that port one on port 4 and the swap bridge node 2 and port 4 are formed, swap bridge node 1 is the root bridge, so the port 4 on the swap bridge node 2 and and NODE1 on port one be root port, be in forwarding state.Port one on the swap bridge node 2 is that designated port also is in forwarding state.Port 2 on the NODE1 is a non-designated port, is in blocked state, has so just realized the selection that NODE1 goes up redundancy port.
(4) if the port one uplink of NODE1 breaks down: for example carrier signal is lost or is not received the BPDU that root bridge swap bridge node 1 is sent at the appointed time, and the Spanning-Tree Protocol on the NODE1 can become root port to port 2 in a definite time.After the port one fault on the NODE1, NODE1 to swap bridge node 2, arrives root bridge swap bridge node 1 by swap bridge node 2 by port 2 then.This moment, the root bridge still was a swap bridge node 1.Spanning-Tree Protocol on the NODE1 node can know that it stops on port one receiving that BPDU, fault occurred after the Max Age time, will force other to enter listening state by port 2.Because can provide path from the root bridge to this node by 2 ports now, it can become forwarding state gradually, becomes root port.So just finished the fault recovery of NODE1 upper port 1 and port 2.
In like manner, on other NODE, repeat above-mentioned steps, so just can guarantee that in two ports on each NODE plate a port must be arranged is root port, link to each other with the root bridge of whole network, and because each Node node all with the root bridge together with, so can reach by the root bridge between any two NODE nodes.
Such fault handling method is supported the active and standby switching of swap bridge node to the end node redundant link; For the swap bridge node can by the management interface that generates tree control satisfy active and standby, dual-active or based on the switching of strategy.
The fault that this method relates to comprises following common several aspects:
1. the link failure that arrives of hardware detection
2. the port failure that arrives of hardware detection
3. the link failure that arrives of software detection
4. the port failure that arrives of software detection
The processing of fault has three kinds of modes usually: artificial initiatively hand-off process, the hardware detection Fault Control is handled and the software detection Fault Control is handled.
Manual command is initiatively switched, the fault recovery step: the whole node disturbance switching of swap bridge is also identical therewith
A1: send the swap bridge node 1 of switching command to appointment
A2: swap bridge node 1 enters into failure state with all of the port
A3: swap bridge node 1 Spanning-Tree Protocol out of service
A4: the priority of the bridge of swap bridge node 1 reduction itself makes the bridge priorities of swap bridge node 2 greater than the bridge priorities of swap bridge node 1
A5: swap bridge node 1 restarts Spanning-Tree Protocol
A6: calculate each port status through Spanning-Tree Protocol
A7: the switching problem of finishing the whole node between the swap bridge node.This switching can be manual command control, or determines whole node the switching of the whole node of carrying out of having broken down according to strategy.
Fault recovery flow process after the hardware and software detection failure detects can directly be utilized the administration configuration interface configuration port failure of Spanning-Tree Protocol to swap bridge node and end node (NODE node), and Spanning-Tree Protocol has just directly been handled the fault of this port.
Fault recovery flow process after the hardware detection fault detect, this port, employing STP that sentences the NODE node is an example:
The b1:NODE node is received hardware signal, indicates certain port failure of NODE node
B2: call Spanning-Tree Protocol management interface, this port is made as the disable state
B3: if non-working port is the root port on this NODE, change b4, otherwise change b5
B4: the process Spanning-Tree Protocol calculates the new root port on the NODE node.
Fault recovery flow process after the software detection fault detect, this port, employing STP that sentences the NODE node is an example:
Certain port of c1:NODE node is not received in Max Age from the next BPDU of root bridge
C2: if this port is the root port on this NODE, change c3, otherwise change c4
Spanning-Tree Protocol on the c3:NODE node is made as listening state with the another port, after through ForwardDelay (delay time) time-delay, this port is made as learning state; After through Forward Delay time-delay, this port is made as forwarding state.
This method can the detected source of failure to above-mentioned 4 aspects and three kinds of troubleshooting modes all can well support.The fault detect of hand-off process initiatively and hardware causes can carrying out the recovery of whole network then and handle by generating the state of the direct control port of setting of management interface of switching; The link failure detection of directly utilizing Spanning-Tree Protocol mechanism to carry out software is carried out the topological communication recovery of follow-up whole network then automatically.
It is different detecting the time that needs for different faults, hardware fault can produce by modes such as hardware detection and interruptions, usually the detection time of the type fault is less than 10ms second, and and the parameter configuration of the Spanning-Tree Protocol that adopts irrelevant, the implementation by hardware decides fully; Detect by protocol software communication handshake mode for software fault, for the detection of the type fault be with the version of Spanning-Tree Protocol, and parameter configuration relevant.
For the recovery time of fault and the Spanning-Tree Protocol of employing and the configuration parameter of Spanning-Tree Protocol very big relation is arranged.As for generating tree (STP), the Forwarding Latency of its failure recovery time the chances are twice disposes different Forwarding Latencies, its failure recovery time is different, under the default situations, its Forwarding Latency is 15 seconds, so its failure recovery time probably is exactly 30 seconds; For rapid spanning-tree (RSTP), its failure recovery time, can be ignored affirming under the situation of level second detection time with respect to software fault less than 50ms.
Be listed in the software fault processing time referential data scope of Spanning-Tree Protocol (comprising common generation tree and rapid spanning-tree) under default parameters and optimized parameter configuration below: (as table 1).Those number ranges can be passed through acquisitions such as actual measurement, estimation.
Table 1
Note:
*The ms level restoration time of RSTP, relevant with the specific implementation of the processor of end points and the priority of agreement etc.Data herein are according to the MPC8260 and the estimated value that can in time be treated to condition.
From last table, can see and adopt the RSTP agreement, owing to be improved than STP when the recovery mechanism of agreement own is used with the switched ethernet network, degree failure detection time that failure recovery time all has been reduced to the ms level under very big situation, also can reach very short time with interior (as 1 second), this can use this method and also widens bigger scope, can be applied to the stricter system of failure recovery time requirement, as speech processing system, image transmission and treatment system or the like.
This method is specially adapted to meet PICMG2.16, full ether such as PICMG3.0ATCA connects the equipment of the machine frame structure of industrial standard, have the highly available system that the machine frame of comprehensive hardware redundancy is formed, also can be used in the network redundancy that the important end node of part is only supported port.
In use,, can reasonable disposition generate the parameter of setting, make fault detect and failure recovery time reach minimum according to the occasion of using.For example: if all swap bridge nodes and the operation of Node node all is the STP agreement, the following parameter value Hello time=1s of configuration stp agreement, Maxage=3s, Forward delay=2s, like this under the situation of software fault, can be through recovery in 7 seconds, hardware fault can be recovered by 4 seconds.If all swap bridge nodes and the operation of Node node all is the RSTP agreement, the following parameter value Hello time=1s of configuration RSTP agreement, Maxage=3s, Forward delay=2s, like this under the situation of software fault, can be through recovery in 3 seconds, hardware fault can be recovered by＜1 second.The Spanning-Tree Protocol version can also adopt many examples Spanning-Tree Protocol MISTP and Multiple Spanning Tree Protocol MSTP except Spanning-Tree Protocol STP, rapid spanning-tree view RSTP.Different editions at above-mentioned Spanning-Tree Protocol can be provided with corresponding spanning-tree parameter (comprising Maxage, Forward delay), so that determine the recovery time that network failure is spent.
More than disclosed only be several specific embodiment of the present invention, any those skilled in the art can think variation all should drop in protection scope of the present invention.
Claims (8)
1, a kind of network failure recovery method with redundancy port is characterized in that, may further comprise the steps:
(1) at the swap bridge node with have and be provided with on the end node of redundancy port and the operation Spanning-Tree Protocol;
(2) bridge priority that all end nodes are set is lower than the bridge priority of swap bridge node; Perhaps under the identical situation of bridge priority, the medium access control MAC Address of swap bridge node is provided with MAC Address less than each end node;
(3) when breaking down on the link of the root port of end node or root port, utilize the Spanning-Tree Protocol of above-mentioned end node that redundancy port is become root port, enter forwarding state, the active-standby port of realizing having on the redundancy port end node switches, and recovers communication link.
2, the network failure recovery method with redundancy port as claimed in claim 1, it is characterized in that can detect on the link of the root port of end node or root port by following steps in the step (3) and break down: the root port of end node is not received bridge protocol data unit B PDU message in the predefined time.
3, the network failure recovery method with redundancy port as claimed in claim 1, it is characterized in that, detect on the link of the root port of end node or root port by following steps in the step (3) and break down: end node according to the hardware that receives directly the fault message of report judge on the link of the root port of described end node or root port and break down.
4, as claim 2 or 3 described network failure recovery methods, it is characterized in that step (1) also comprises before with redundancy port:
The port that each end node with redundancy port is set respectively with being connected of the port of different swap bridge nodes, and guarantee that the root bridging that end node and agreement are determined leads to.
5, as claim 2 or 3 described network failure recovery methods, it is characterized in that, utilize the Spanning-Tree Protocol of described end node that redundancy port is generated root port in the step (3), and described port is entered forwarding state be specially with redundancy port:
Carry out the conversion process of port status according to the Spanning-Tree Protocol that is provided with or BPDU consults to confirm alternately.
6, the network failure recovery method with redundancy port as claimed in claim 5 is characterized in that, the conversion process of carrying out port status according to the Spanning-Tree Protocol that is provided with or BPDU consults to confirm alternately comprises:
Behind the process delay time, described root port is not received the BPDU message of root bridge transmission in the stand-by period after, described redundancy port is set at forwarding state, and be sent to the node of other operation Spanning-Tree Protocol in this local area network (LAN) by the configuration information that BPDU message breaks down former root port and former redundancy port is set at root port, so that form new generation tree.
7, the network failure recovery method with redundancy port as claimed in claim 5, it is characterized in that, also comprise: comprise the Spanning-Tree Protocol parameter of stand-by period and delay time according to Spanning-Tree Protocol default configuration values or setting, can pre-determine the recovery time that is spent of network failure.
8, the network failure recovery method with redundancy port as claimed in claim 1 is characterized in that, described Spanning-Tree Protocol version comprises Spanning-Tree Protocol STP, RSTP RSTP and many examples Spanning-Tree Protocol MISTP/ Multiple Spanning Tree Protocol MSTP.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100005655A CN100417094C (en) | 2006-01-11 | 2006-01-11 | Network failure recovery method with redundancy port |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100005655A CN100417094C (en) | 2006-01-11 | 2006-01-11 | Network failure recovery method with redundancy port |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101001165A true CN101001165A (en) | 2007-07-18 |
| CN100417094C CN100417094C (en) | 2008-09-03 |
Family
ID=38692985
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006100005655A Active CN100417094C (en) | 2006-01-11 | 2006-01-11 | Network failure recovery method with redundancy port |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100417094C (en) |
Cited By (35)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101917648A (en) * | 2010-08-27 | 2010-12-15 | 中兴通讯股份有限公司 | Method for implementing service control in all-fiber protection system and device thereof |
| CN101964719A (en) * | 2009-07-23 | 2011-02-02 | 中兴通讯股份有限公司 | Data processing method based on operating/standby switch of master control boards, line card and master control boards |
| CN102143057A (en) * | 2010-12-14 | 2011-08-03 | 华为数字技术有限公司 | Particular method and device for generating blocked port in tree protocol |
| CN102143026A (en) * | 2011-04-29 | 2011-08-03 | 杭州华三通信技术有限公司 | Method for avoiding loop circuit in virtual layer 2 network |
| WO2011110037A1 (en) * | 2010-03-10 | 2011-09-15 | 华为技术有限公司 | Multicast implementation method, access layer equipment and system under ring network architecture |
| CN102447576A (en) * | 2011-10-20 | 2012-05-09 | 深圳市国电科技通信有限公司 | Automatic election method for local end equipment of network |
| CN102546345A (en) * | 2011-12-30 | 2012-07-04 | Ut斯达康通讯有限公司 | Method for realizing cross-ring protection of resilient packet ring by use of spanning tree protocol |
| CN102761451A (en) * | 2012-08-09 | 2012-10-31 | 武汉迈威实达软件有限公司 | Improved single loop redundancy backup implementation based on rapid spanning tree protocol (RSTP) |
| CN102769570A (en) * | 2012-07-30 | 2012-11-07 | 杭州华三通信技术有限公司 | Route notification method and equipment |
| CN102780614A (en) * | 2012-07-12 | 2012-11-14 | 福建星网锐捷网络有限公司 | Spanning tree protocol wiring closet group function enabling method as well as equipment and system |
| CN102893560A (en) * | 2011-05-16 | 2013-01-23 | 华为技术有限公司 | Method and network device for transmitting data stream |
| US8488475B2 (en) | 2007-11-26 | 2013-07-16 | Supcon Group Co., Ltd. | Fault processing method, system and exchanging device based on industry ethernet network |
| CN103441938A (en) * | 2013-08-28 | 2013-12-11 | 南车株洲电力机车研究所有限公司 | Port switching method and communication equipment |
| CN103457778A (en) * | 2013-09-09 | 2013-12-18 | 华为技术有限公司 | Method and equipment for communication of Ethernet switched network |
| CN103973479A (en) * | 2013-02-01 | 2014-08-06 | 韩国电子通信研究院 | Method and apparatus for interworking protection switching |
| WO2014173230A1 (en) * | 2013-04-24 | 2014-10-30 | 中兴通讯股份有限公司 | Active and standby changeover method, apparatus, device, and system for network device |
| CN104270267A (en) * | 2014-09-26 | 2015-01-07 | 杭州华三通信技术有限公司 | Port switching method and veneer device |
| CN104363138A (en) * | 2014-11-14 | 2015-02-18 | 迈普通信技术股份有限公司 | Interface backup method and device |
| CN104811385A (en) * | 2014-01-23 | 2015-07-29 | 智邦科技股份有限公司 | Network system, switch, and method for operating network system |
| CN105141451A (en) * | 2015-07-30 | 2015-12-09 | 积成电子股份有限公司 | MSTP communication network with automatic repair function and automatic repair method thereof |
| WO2016045276A1 (en) * | 2014-09-24 | 2016-03-31 | 中兴通讯股份有限公司 | Packet forwarding method and device, sdn and system |
| CN102714611B (en) * | 2010-01-29 | 2016-04-27 | 惠普发展公司，有限责任合伙企业 | The configuration of network link in virtual connection environment |
| CN106209425A (en) * | 2016-06-28 | 2016-12-07 | 上海携程商务有限公司 | The method and system of the automatic bypass of fire wall based on switch |
| CN106330697A (en) * | 2015-07-03 | 2017-01-11 | 思锐科技股份有限公司 | Hybrid network spanning tree establishing method, backup method and control system thereof |
| CN106341249A (en) * | 2015-07-10 | 2017-01-18 | 中兴通讯股份有限公司 | Redundant port switching method and device |
| CN108133034A (en) * | 2018-01-08 | 2018-06-08 | 新华三云计算技术有限公司 | Shared storage access method and relevant apparatus |
| CN108337145A (en) * | 2017-01-19 | 2018-07-27 | 中兴通讯股份有限公司 | The processing method and processing device of polycyclic road network |
| CN109471675A (en) * | 2018-10-30 | 2019-03-15 | 张家口浩扬科技有限公司 | It is a kind of that the method and its system that change are executed for hardware |
| CN110192352A (en) * | 2017-01-20 | 2019-08-30 | Teko电信有限公司 | The automatic redundancy structure of wireless device |
| CN111585797A (en) * | 2020-04-27 | 2020-08-25 | 深圳震有科技股份有限公司 | Ethernet link switching method, device, equipment and computer readable storage medium |
| CN111756660A (en) * | 2020-05-18 | 2020-10-09 | 深圳震有科技股份有限公司 | Working link switching method, device, equipment and computer readable storage medium |
| CN113328910A (en) * | 2021-05-26 | 2021-08-31 | 中国电子科技集团公司第五十四研究所 | Link state monitoring method facing spanning tree protocol |
| CN113875196A (en) * | 2019-05-28 | 2021-12-31 | 小糸电工株式会社 | Communication device |
| CN115473792A (en) * | 2022-08-01 | 2022-12-13 | 上海微波技术研究所（中国电子科技集团公司第五十研究所） | Flow table-based dual-channel high-reliability communication control system and method |
| CN116668282A (en) * | 2023-06-26 | 2023-08-29 | 北京志凌海纳科技有限公司 | High availability method and system for two-layer gateway based on STP spanning tree protocol |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1778075A (en) * | 2003-02-19 | 2006-05-24 | 日本电气株式会社 | Network system, spanning tree configuration method, configuration program, and spanning tree configuration node |
| CN100440746C (en) * | 2003-12-01 | 2008-12-03 | 中兴通讯股份有限公司 | A method for multi-port multi-link communication network backup control and apparatus therefor |
-
2006
- 2006-01-11 CN CNB2006100005655A patent/CN100417094C/en active Active
Cited By (56)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8488475B2 (en) | 2007-11-26 | 2013-07-16 | Supcon Group Co., Ltd. | Fault processing method, system and exchanging device based on industry ethernet network |
| CN101964719A (en) * | 2009-07-23 | 2011-02-02 | 中兴通讯股份有限公司 | Data processing method based on operating/standby switch of master control boards, line card and master control boards |
| CN101964719B (en) * | 2009-07-23 | 2015-11-25 | 中兴通讯股份有限公司 | Based on the data processing method of master control board switching, line card and master control borad |
| CN102714611B (en) * | 2010-01-29 | 2016-04-27 | 惠普发展公司，有限责任合伙企业 | The configuration of network link in virtual connection environment |
| WO2011110037A1 (en) * | 2010-03-10 | 2011-09-15 | 华为技术有限公司 | Multicast implementation method, access layer equipment and system under ring network architecture |
| CN102195863A (en) * | 2010-03-10 | 2011-09-21 | 华为技术有限公司 | Multicasting realization method, access layer equipment and system under ring network framework |
| CN102195863B (en) * | 2010-03-10 | 2014-10-08 | 华为技术有限公司 | Multicasting realization method, access layer equipment and system under ring network framework |
| CN101917648B (en) * | 2010-08-27 | 2014-06-11 | 中兴通讯股份有限公司 | Method for implementing service control in all-fiber protection system and device thereof |
| WO2012024940A1 (en) * | 2010-08-27 | 2012-03-01 | 中兴通讯股份有限公司 | Method and device for realizing service control in all fiber protection system |
| CN101917648A (en) * | 2010-08-27 | 2010-12-15 | 中兴通讯股份有限公司 | Method for implementing service control in all-fiber protection system and device thereof |
| CN102143057A (en) * | 2010-12-14 | 2011-08-03 | 华为数字技术有限公司 | Particular method and device for generating blocked port in tree protocol |
| CN102143026A (en) * | 2011-04-29 | 2011-08-03 | 杭州华三通信技术有限公司 | Method for avoiding loop circuit in virtual layer 2 network |
| CN102143026B (en) * | 2011-04-29 | 2014-03-12 | 杭州华三通信技术有限公司 | Method for avoiding loop circuit in virtual two layer network |
| CN102893560A (en) * | 2011-05-16 | 2013-01-23 | 华为技术有限公司 | Method and network device for transmitting data stream |
| US9866486B2 (en) | 2011-05-16 | 2018-01-09 | Huawei Technologies Co., Ltd. | Method and network device for transmitting data stream |
| US9331945B2 (en) | 2011-05-16 | 2016-05-03 | Huawei Technologies Co., Ltd. | Method and network device for transmitting data stream |
| CN102893560B (en) * | 2011-05-16 | 2015-11-25 | 华为技术有限公司 | A kind of data flow transmission method and the network equipment |
| CN102447576A (en) * | 2011-10-20 | 2012-05-09 | 深圳市国电科技通信有限公司 | Automatic election method for local end equipment of network |
| CN102447576B (en) * | 2011-10-20 | 2015-05-06 | 深圳市国电科技通信有限公司 | Automatic election method for local end equipment of network |
| CN102546345A (en) * | 2011-12-30 | 2012-07-04 | Ut斯达康通讯有限公司 | Method for realizing cross-ring protection of resilient packet ring by use of spanning tree protocol |
| CN102780614A (en) * | 2012-07-12 | 2012-11-14 | 福建星网锐捷网络有限公司 | Spanning tree protocol wiring closet group function enabling method as well as equipment and system |
| CN102769570A (en) * | 2012-07-30 | 2012-11-07 | 杭州华三通信技术有限公司 | Route notification method and equipment |
| CN102769570B (en) * | 2012-07-30 | 2015-05-20 | 杭州华三通信技术有限公司 | Route notification method and equipment |
| CN102761451A (en) * | 2012-08-09 | 2012-10-31 | 武汉迈威实达软件有限公司 | Improved single loop redundancy backup implementation based on rapid spanning tree protocol (RSTP) |
| CN103973479A (en) * | 2013-02-01 | 2014-08-06 | 韩国电子通信研究院 | Method and apparatus for interworking protection switching |
| WO2014173230A1 (en) * | 2013-04-24 | 2014-10-30 | 中兴通讯股份有限公司 | Active and standby changeover method, apparatus, device, and system for network device |
| CN103441938A (en) * | 2013-08-28 | 2013-12-11 | 南车株洲电力机车研究所有限公司 | Port switching method and communication equipment |
| CN103441938B (en) * | 2013-08-28 | 2015-05-13 | 南车株洲电力机车研究所有限公司 | Port switching method and communication equipment |
| CN103457778B (en) * | 2013-09-09 | 2017-02-15 | 华为技术有限公司 | Method and equipment for communication of Ethernet switched network |
| CN103457778A (en) * | 2013-09-09 | 2013-12-18 | 华为技术有限公司 | Method and equipment for communication of Ethernet switched network |
| CN104811385B (en) * | 2014-01-23 | 2018-08-24 | 智邦科技股份有限公司 | Network system, switch, and method for operating network system |
| CN104811385A (en) * | 2014-01-23 | 2015-07-29 | 智邦科技股份有限公司 | Network system, switch, and method for operating network system |
| WO2016045276A1 (en) * | 2014-09-24 | 2016-03-31 | 中兴通讯股份有限公司 | Packet forwarding method and device, sdn and system |
| CN104270267B (en) * | 2014-09-26 | 2019-03-15 | 新华三技术有限公司 | A kind of port switching method and single-board device |
| CN104270267A (en) * | 2014-09-26 | 2015-01-07 | 杭州华三通信技术有限公司 | Port switching method and veneer device |
| CN104363138A (en) * | 2014-11-14 | 2015-02-18 | 迈普通信技术股份有限公司 | Interface backup method and device |
| CN106330697A (en) * | 2015-07-03 | 2017-01-11 | 思锐科技股份有限公司 | Hybrid network spanning tree establishing method, backup method and control system thereof |
| CN106341249A (en) * | 2015-07-10 | 2017-01-18 | 中兴通讯股份有限公司 | Redundant port switching method and device |
| WO2017008641A1 (en) * | 2015-07-10 | 2017-01-19 | 中兴通讯股份有限公司 | Method of switching redundancy port and device utilizing same |
| CN105141451A (en) * | 2015-07-30 | 2015-12-09 | 积成电子股份有限公司 | MSTP communication network with automatic repair function and automatic repair method thereof |
| CN106209425A (en) * | 2016-06-28 | 2016-12-07 | 上海携程商务有限公司 | The method and system of the automatic bypass of fire wall based on switch |
| CN108337145B (en) * | 2017-01-19 | 2021-11-23 | 中兴通讯股份有限公司 | Processing method and device of multi-loop network |
| CN108337145A (en) * | 2017-01-19 | 2018-07-27 | 中兴通讯股份有限公司 | The processing method and processing device of polycyclic road network |
| CN110192352A (en) * | 2017-01-20 | 2019-08-30 | Teko电信有限公司 | The automatic redundancy structure of wireless device |
| CN108133034A (en) * | 2018-01-08 | 2018-06-08 | 新华三云计算技术有限公司 | Shared storage access method and relevant apparatus |
| CN109471675A (en) * | 2018-10-30 | 2019-03-15 | 张家口浩扬科技有限公司 | It is a kind of that the method and its system that change are executed for hardware |
| CN109471675B (en) * | 2018-10-30 | 2021-11-19 | 北京无限自在文化传媒股份有限公司 | Method and system for changing hardware |
| CN113875196B (en) * | 2019-05-28 | 2024-01-05 | 小糸电工株式会社 | Communication device |
| CN113875196A (en) * | 2019-05-28 | 2021-12-31 | 小糸电工株式会社 | Communication device |
| CN111585797A (en) * | 2020-04-27 | 2020-08-25 | 深圳震有科技股份有限公司 | Ethernet link switching method, device, equipment and computer readable storage medium |
| CN111756660A (en) * | 2020-05-18 | 2020-10-09 | 深圳震有科技股份有限公司 | Working link switching method, device, equipment and computer readable storage medium |
| CN113328910A (en) * | 2021-05-26 | 2021-08-31 | 中国电子科技集团公司第五十四研究所 | Link state monitoring method facing spanning tree protocol |
| CN115473792A (en) * | 2022-08-01 | 2022-12-13 | 上海微波技术研究所（中国电子科技集团公司第五十研究所） | Flow table-based dual-channel high-reliability communication control system and method |
| CN115473792B (en) * | 2022-08-01 | 2023-09-22 | 上海微波技术研究所（中国电子科技集团公司第五十研究所） | Dual-channel communication control system and method based on flow table |
| CN116668282A (en) * | 2023-06-26 | 2023-08-29 | 北京志凌海纳科技有限公司 | High availability method and system for two-layer gateway based on STP spanning tree protocol |
| CN116668282B (en) * | 2023-06-26 | 2024-02-13 | 北京志凌海纳科技有限公司 | High availability method and system for two-layer gateway based on STP spanning tree protocol |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100417094C (en) | 2008-09-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100417094C (en) | Network failure recovery method with redundancy port | |
| CN101160836B (en) | Redundancy protection method for bridge mode resilient packet ring | |
| KR101204130B1 (en) | Fault processing method, system and exchanging device based on industry ethernet network | |
| EP2352253B1 (en) | Method and apparatus for protecting link aggregation group of ethernet ring | |
| CA2631023C (en) | Lightweight node based network redundancy solution leveraging rapid spanning tree protocol (rstp) | |
| CN101060485B (en) | Topology changed messages processing method and processing device | |
| CN101860492A (en) | Quick switching method, device and system | |
| CN101753397B (en) | System, method and device for rapidly self-healing Ethernet ring | |
| CN103607293B (en) | A kind of flow rate protecting method and equipment | |
| RU2505933C2 (en) | Ethernet switch ring protection method and transit node | |
| WO2006102826A1 (en) | A method for realizing the backup of the data service | |
| CN101674240B (en) | Method and device for realizing single-node dual home for distributed system | |
| CN101197733A (en) | Automatic detection method and device for network connectivity | |
| CN101277269A (en) | Terminal with dependable communication, terminal switch method and system as well as method for implementing the system | |
| CN100512220C (en) | Method for realizing service protection on elastic group ring | |
| CN101710865A (en) | Method and device for rapid active-standby switching in network equipment | |
| CN103227725A (en) | Method and device for dual-server backup of firewall | |
| CN101267392A (en) | A realizing method for notifying downstream device in case of switch of uplink link status | |
| CN103441940A (en) | Method and device for switching network device from stand-by state to main state and network device | |
| EP2426855B1 (en) | Address refresh method and system | |
| CN101136838B (en) | Bridge mode elastic grouping ring transannular bridge equipment redundancy protecting method | |
| CN102487332B (en) | Fault processing method, apparatus thereof and system thereof | |
| CN106656311A (en) | Data link backup apparatus and method | |
| CN103124235A (en) | MS-ring Ethernet redundancy access algorithm | |
| CN101820376A (en) | Method and system for realizing rapid convergence in ring network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |