CN103414591B - Method for rapidly converging when a kind of port failure recovers and system - Google Patents
Method for rapidly converging when a kind of port failure recovers and system Download PDFInfo
- Publication number
- CN103414591B CN103414591B CN201310362310.3A CN201310362310A CN103414591B CN 103414591 B CN103414591 B CN 103414591B CN 201310362310 A CN201310362310 A CN 201310362310A CN 103414591 B CN103414591 B CN 103414591B
- Authority
- CN
- China
- Prior art keywords
- node
- edge
- port
- ring
- main
- 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
- 238000000034 method Methods 0.000 title claims abstract description 28
- 230000005540 biological transmission Effects 0.000 claims abstract description 72
- 230000008859 change Effects 0.000 claims description 12
- 230000000903 blocking effect Effects 0.000 claims description 5
- 230000008569 process Effects 0.000 claims description 3
- 238000002360 preparation method Methods 0.000 claims 1
- 238000011084 recovery Methods 0.000 description 11
- 238000004904 shortening Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Landscapes
- Small-Scale Networks (AREA)
Abstract
The invention discloses method for rapidly converging when a kind of port failure recovers and system, the method includes: main ring host node is after sending hello packet by master port, if not receiving, from secondary port, the hello packet that master port sends, then send hello packet by secondary port；If ports having reverts to Up state from Down state on main ring transmission node, and described port is Block state, the most described main ring transmission node is receiving after the hello packet of the secondary port of described main ring host node, and from Block state, described port is become Forwarding state.In the embodiment of the present invention, it is possible to recover flow as early as possible and forward, improve network convergence performance.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method and a system for fast convergence when a port failure is recovered.
Background
RRPP (fast Ring Protection Protocol) is a link layer Protocol specifically applied to ethernet rings. The RRPP is used for preventing broadcast storm caused by a data loop when the Ethernet loop is complete; and when one link on the Ethernet ring is disconnected, the communication path between each node on the Ethernet ring can be quickly recovered. Therefore, the RRPP has a high convergence rate.
Each device on the RRPP ring is called a node, and the role of the node is determined by user configuration. (1) A master node: each RRPP ring has only one master node, and the master node is an initiator of the ring network state active detection mechanism and also a decision maker for executing operations after the network topology changes. (2) And all the nodes on the main ring except the main node and all the nodes on the subring except the main node and the intersection node of the subring and the main ring are all transmission nodes. (3) Edge nodes: the special nodes are positioned on the main ring and the sub-ring at the same time, and the edge node is also a transmission node on the main ring. (4) Auxiliary edge nodes: the special nodes are positioned on the main ring and the sub-ring at the same time, and the auxiliary edge node is also a transmission node on the main ring.
When the sub-ring and the main ring are intersected, two intersection points exist, one of devices at the two intersection points is called an edge node, the other one of the devices is called an auxiliary edge node, the edge node or the auxiliary edge node is the role of the device on the sub-ring, and the role of the device on the main ring is the main node or the transmission node. Further, the edge node and the auxiliary edge node must be configured in pairs, and there is no special requirement as to which device is configured as the edge node or the auxiliary edge node, as long as the configuration can distinguish the edge node from the auxiliary edge node.
As shown in fig. 1, the RRPP network includes a main ring and a sub-ring, where device 1 is a sub-ring main node, device 2 is a main ring transmission node and an edge node, device 3 is a main ring transmission node and a sub-ring transmission node, device 4 is a main ring transmission node and an auxiliary edge node, device 5 is a main ring transmission node, device 6 is a main ring main node, and device 7 is a main ring transmission node. In the above application scenario, the main ring master node (device 6) periodically sends a HELLO packet (health detection packet) from the master port, and the HELLO packet is transmitted on the main ring through each main ring transmission node in sequence. If the secondary port of the main node of the main ring receives the HELLO message, the ring network link where the main ring is located is complete; if the HELLO message is not received from the secondary port of the primary ring master node within the specified time, the link failure of the ring network where the primary ring is located is indicated.
When a port Down of a main ring transmission node (e.g., device 3) fails, a secondary port of a main ring master node cannot receive a HELLO packet from a main port within a specified time, and therefore the secondary port needs to be changed from a Block state to a Forwarding state; after the port of the device 3 is restored to Up (normal) from Down, the port of the device 3 needs to be set to Block state first in order to prevent a loop from occurring because the secondary port is in Forwarding state. Then, the secondary port of the main ring main node can receive a HELLO message from the main port, the secondary port needs to be changed from a Forwarding state to a Block state, and the main ring main node sends a COMPLETE-FLUSH-FDB (ring network non-negative refresh Forwarding database) message through the main port; after receiving the COMPLETE-FLUSH-FDB message, the device 3 considers that no broadcast storm occurs in the ring network, and thus changes the port from the Block state to the Forwarding state.
In the foregoing implementation manner, if a link where a main port of a main ring node is located fails, the device 3 cannot receive a COMPLETE-FLUSH-FDB message from the main ring node, and in order to enable the device 3 to change the port from a Block state to a Forwarding state, the device 3 recovers the port from Down to Up, and needs to set a fail timer after setting the port to the Block state, and after waiting for the fail timer to time out, the device 3 changes the port from the Block state to the Forwarding state.
However, in the prior art, the timeout time of the fail timer is generally 30s, so that after a port of a main ring transmission node (e.g., device 3) is restored to Up from Down, if a link where a main port of a main ring master node is located fails, the main ring transmission node needs to wait 30s before changing the port from a Block state to a Forwarding state, that is, 30s is needed before resuming traffic Forwarding, and the network convergence performance is poor.
Disclosure of Invention
The embodiment of the invention provides a method and a system for rapidly converging when a port fault is recovered, so that after the port fault is recovered, flow forwarding is recovered as soon as possible, and the network convergence performance is improved.
In order to achieve the above object, an embodiment of the present invention provides a fast convergence method for port failure recovery, where the method is applied to a fast ring protection protocol RRPP network including a primary ring node and a primary ring transmission node, where the primary ring transmission node includes an edge node and an auxiliary edge node, where a sub-ring intersects with a primary ring, and the method includes:
after the main ring main node sends the Hello message through the main port, if the Hello message sent by the main port is not received from the auxiliary port within the specified time, the Hello message is sent through the auxiliary port;
if a port on the transmission node of the main ring is recovered to a normal Up state from a fault Down state and the port is in a blocking Block state, the transmission node of the main ring changes the port from the Block state to a Forwarding state after receiving a Hello message from a secondary port of the main node of the main ring.
The process of changing the port from a Block state to a Forwarding state by the main ring transmission node specifically includes: the main ring transmission node updates the timeout time of a timeout fail timer of the main ring transmission node by using the timeout time carried in a Hello message from a secondary port of the main ring main node, and changes the port from a Block state to a Forwarding state after the fail timer is overtime; and the timeout time of the fail timer after updating is less than that of the fail timer before updating.
The method further comprises the following steps:
when the auxiliary edge node does not receive a Hello message from a secondary port of the main ring main node and a Hello message from a main port of the main ring main node, the auxiliary edge node sends a main ring Fault notification Major-Fault message to the edge node through the edge port of the auxiliary edge node, wherein the Major-Fault message carries information that the main ring main node is failed;
when the Edge node receives a Major-Fault message through an Edge port of the Edge node, if the Major-node message is found to carry information that the Major-ring host node has failed, sending a Major-ring integrity check Edge-Hello message to the auxiliary Edge node through a public port of the Edge node, wherein the Edge-Hello message carries the information that the Major-ring host node has failed;
and if the port on the main ring transmission node is restored to the Up state from the Down state and the port is in the Block state, the main ring transmission node changes the port from the Block state to the Forwarding state when receiving the Edge-Hello message and the Edge-Hello message carries the information that the main ring main node has failed.
The auxiliary edge node sends a Major-Fault message carrying information that the main ring main node has failed to the edge node through an edge port of the auxiliary edge node, and then the method further comprises the following steps:
when the auxiliary Edge node does not receive a Hello message from a main port of the main ring main node, but receives a Hello message from a secondary port of the main ring main node and does not receive an Edge-Hello message from the Edge node, the auxiliary Edge node sends a Major-Fault message to the Edge node through the Edge port of the auxiliary Edge node, and in the sent Major-Fault message, information that the main ring main node has failed, carried in the Major-Fault message, is eliminated. .
The Edge node sends an Edge-Hello message carrying information that the main ring host node has failed to the auxiliary Edge node through a public port of the Edge node, and then the method further comprises the following steps:
when the Edge node receives a Major ring-Fault message through an Edge port of the Edge node, if the Major ring-Fault message does not carry information that the Major ring master node has failed, the Edge node removes the information that the Major ring master node has failed, which is carried in the Edge-Hello message, when sending the Edge-Hello message to the auxiliary Edge node through a public port of the Edge node; or,
when the Edge node does not receive the Major-Fault message through the Edge port of the Edge node, and when the Edge-Hello message is sent to the auxiliary Edge node through the public port of the Edge node, the Edge node clears the information that the main ring main node carried in the Edge-Hello message is invalid; or,
and when the Edge node receives the Hello message from the auxiliary port of the main ring host node, and when the Edge node sends an Edge-Hello message to the auxiliary Edge node through the public port of the Edge node, clearing the information that the main ring host node fails, which is carried in the Edge-Hello message.
The embodiment of the invention provides a rapid convergence system during port fault recovery, which is applied to a rapid ring protection protocol RRPP network and comprises a main ring main node and a main ring transmission node, wherein the main ring transmission node comprises edge nodes and auxiliary edge nodes, and the edge nodes are intersected by sub rings and the main ring;
the primary ring master node is used for sending the Hello message through the secondary port if the Hello message sent by the primary port is not received from the secondary port within the specified time after the Hello message is sent through the primary port;
the main ring transmission node is configured to change a port from a Block state to a Forwarding state after receiving a Hello packet from a secondary port of the main ring master node when the port on the main ring transmission node is restored to a normal Up state from a fault Down state and the port is in a blocking Block state.
The main ring transmission node is specifically configured to update the timeout time of a timeout fail timer of the main ring transmission node by using the timeout time carried in a Hello message from a secondary port of the main ring master node, and change the port from a Block state to a Forwarding state after the fail timer is overtime; and the timeout time of the fail timer after updating is less than that of the fail timer before updating.
The auxiliary edge node is configured to send a main ring Fault notification message to the edge node through an edge port of the auxiliary edge node when not receiving a Hello message from a secondary port of the main ring host node and a Hello message from a main port of the main ring host node, where the main ring Fault notification message carries information that the main ring host node has failed;
the Edge node is configured to, when receiving a Major-Fault message through an Edge port of the Edge node, send a Major-ring integrity check Edge-Hello message to the auxiliary Edge node through a public port of the Edge node if the Major-ring-Fault message is found to carry information that the Major-ring master node has failed, where the Edge-Hello message carries the information that the Major-ring master node has failed;
the main ring transmission node is further configured to change the port from the Block state to the Forwarding state when the port on the main ring transmission node is restored from the Down state to the Up state and the port is in the Block state and an Edge-Hello message is received and carries information that the main ring host node has failed.
The auxiliary Edge node is further configured to send a Major-Fault message to the Edge node through the Edge port of the auxiliary Edge node after sending the Major-Fault message carrying the information that the Major-ring master node has failed to the Edge node through the Edge port of the auxiliary Edge node, when the Hello message from the Major port of the Major-ring master node is not received, but the Hello message from the minor port of the Major-ring master node is received, and the Edge-Hello message from the Edge node is not received, send the Major-Fault message to the Edge node through the Edge port of the auxiliary Edge node, and clear the information that the Major-ring master node has failed and is carried in the Major-Fault message in the sent Major-Fault message.
The Edge node is further configured to, after sending an Edge-Hello packet carrying information that the primary ring host node has failed to the secondary Edge node through the public port of the Edge node, when receiving a Major-Fault packet through the Edge port of the Edge node, if the Major-Fault packet does not carry the information that the primary ring host node has failed, clear the information that the primary ring host node has failed carried in the Edge-Hello packet when sending the Edge-Hello packet to the secondary Edge node through the public port of the Edge node; or after sending an Edge-Hello message carrying information that the main ring host node has failed to the auxiliary Edge node through the public port of the Edge node, when not receiving a Major-Fault message through the Edge port of the Edge node, and when sending the Edge-Hello message to the auxiliary Edge node through the public port of the Edge node, clearing the information that the main ring host node has failed carried in the Edge-Hello message; or after sending the Edge-Hello message carrying the information that the main ring host node has failed to the auxiliary Edge node through the public port of the Edge node, when receiving the Hello message from the auxiliary port of the main ring host node, and when sending the Edge-Hello message to the auxiliary Edge node through the public port of the Edge node, clearing the information that the main ring host node has failed carried in the Edge-Hello message.
Compared with the prior art, the embodiment of the invention at least has the following advantages: in the embodiment of the invention, the port on the transmission node of the main ring is recovered to the Up state from the Down state, and the port can be changed into the Forwarding state from the Block state in time after being in the Block state, so that the flow Forwarding is recovered as soon as possible after the port fault is recovered, and the network convergence performance is improved and accelerated.
Drawings
FIG. 1 is a schematic networking diagram of a RRPP network in the prior art;
fig. 2 is a flowchart of a fast convergence method for port failure recovery according to an embodiment of the present invention.
Detailed Description
To solve the problems in the prior art, an embodiment of the present invention provides a fast convergence method for port failure recovery, where the method is applied to an RRPP network including a main ring master node and a main ring transmission node, and the main ring transmission node includes an edge node and an auxiliary edge node where a sub ring intersects with a main ring.
Fig. 1 is a schematic view of an application scenario of an embodiment of the present invention, where the RRPP network includes a main ring and a sub-ring. The main node of the main ring is device 6, and the main ring transmission node includes device 2, device 3, device 4, device 5, and device 7. Further, the device 2 is an edge node, and the device 4 is an auxiliary edge node.
In the above application scenario, when a link where a main port of a main ring master node is located fails, as shown in fig. 2, the fast convergence method for recovering from a port failure includes the following steps:
step 201, after the primary ring master node sends the Hello message through the primary port, if the Hello message sent by the primary port is not received from the secondary port within a specified time, the Hello message is sent through the secondary port.
After the primary ring master node sends the Hello message through the primary port, if the Hello message sent by the primary port is not received from the secondary port within the specified time, the link where the primary port of the primary ring master node is located is considered to have a fault, and the primary ring master node sends the Hello message from the secondary port at the moment.
Step 202, if there is a port on the primary ring transmission node to recover from the Down state to the Up state, and the port is currently in the Block state, the primary ring transmission node changes the port from the Block state to the Forwarding state after receiving the Hello packet from the secondary port of the primary ring master node.
In the embodiment of the present invention, when the primary ring master node sends the Hello packet through the secondary port, it may indicate that the Hello packet is the Hello packet sent through the secondary port by using a certain reserved position 1 in the Hello packet; based on this, after receiving the Hello message from the secondary port of the primary ring master node, the primary ring transmission node may directly change the port from the Block state to the Forwarding state or change the port from the Block state to the Forwarding state based on a fail timer.
In a preferred embodiment of the present invention, a Hello message from a secondary port of a primary ring master node carries timeout (generally 3 s), and a process of a primary ring transmission node changing a port from a Block state to a Forwarding state specifically includes, but is not limited to: the main ring transmission node updates the timeout time of a fail timer of the main ring transmission node by using the timeout time carried in a Hello message from a secondary port of a main ring main node, and after the fail timer is overtime, the main ring transmission node changes the port from a Block state to a Forwarding state.
The timeout time of the fail timer after the update (i.e., the timeout time carried in the Hello packet, which is generally 3 s) is less than the timeout time of the fail timer before the update (which is generally 30 s).
In the application scenario shown in fig. 1, after receiving a Hello packet from an auxiliary port of a device 6 (a primary ring master node), if a port on the device is restored to an Up state from a Down state and the port is currently in a Block state, updating the timeout time of a fail timer of the device by using the timeout time carried in the Hello packet, so that the timeout time of the fail timer is consistent with the timeout time carried in the Hello packet; further, after the fail timer is overtime, the device 7 changes the port from the Block state to the Forwarding state, so that the time for the Block state to transition to the Forwarding state is shortened, and the convergence speed of network recovery is accelerated. Similarly, after receiving the Hello packet from the secondary port of the device 6 (primary ring master node), if a port on the device recovers to the Up state from the Down state and the port is currently in the Block state, the device 2 (or the device 3, or the device 4, or the device 5) updates the timeout time of the fail timer of the device by using the timeout time carried in the Hello packet, so that the timeout time of the fail timer is consistent with the timeout time carried in the Hello packet, and after the fail timer is overtime, the port is changed from the Block state to the Forwarding state, thereby shortening the time for migrating the Block state to the Forwarding state and accelerating the convergence speed of network recovery.
In the embodiment of the invention, after the primary ring master node sends the Hello message through the primary port, if the Hello message sent by the primary port is received from the secondary port within the specified time, the primary ring master node determines that the link where the primary port is located has failed to recover, and at the moment, the primary ring master node also recovers the secondary port into a Block state and stops sending the Hello message from the secondary port.
In the embodiment of the invention, if the auxiliary edge node does not receive the Hello message from the auxiliary port of the main ring main node and does not receive the Hello message from the main port of the main ring main node, the auxiliary edge node determines that the link where the main port of the main ring main node is positioned has a Fault and determines that the link where the auxiliary port of the main ring main node is positioned has a Fault, and based on the Fault, when the auxiliary edge node sends a Major-Fault (main ring Fault notification) message to the edge node through the edge port of the auxiliary edge node, the Major-Fault message carries the information that the main ring main node has failed.
The Edge node periodically sends an Edge-Hello (main ring integrity check) message (used for detecting whether two public links between the Edge node and the auxiliary Edge node are complete) through a public port (two public ports); if the auxiliary Edge node receives an Edge-Hello message from the Edge node through the public port, the fact that a public link between the public port of the auxiliary Edge node and the Edge node is complete is shown; otherwise, the common link between the common port of the auxiliary edge node and the edge node is not complete. When two public links between the edge node and the auxiliary edge node are incomplete, the auxiliary edge node sends a Major-Fault message to the edge node through an edge port of the auxiliary edge node.
On this basis, in the embodiment of the invention, when the auxiliary edge node does not receive the Hello message from the main port of the main ring main node, the link where the main port of the main ring main node is positioned is determined to have a fault; and when the auxiliary edge node does not receive the Hello message from the auxiliary port of the main ring main node, determining that the link where the auxiliary port of the main ring main node is positioned has a fault. Further, when the auxiliary edge node detects that a link where the primary port of the primary ring master node is located fails and detects that a link where the secondary port of the primary ring master node is located fails, it is determined that the primary ring master node has failed. Further, if the two public links between the Edge node and the auxiliary Edge node are incomplete (that is, the auxiliary Edge node does not receive the Edge-Hello packet from the Edge node), the auxiliary Edge node carries information that the main ring main node has failed in a Major-loop Fault packet sent to the Edge node by an Edge port of the auxiliary Edge node, for example, the auxiliary Edge node indicates that the main ring main node has failed by using a certain reserved position 1 in the Major-loop Fault packet.
In the embodiment of the invention, when an Edge node receives a Major-Fault message through an Edge port of the Edge node, if the Major-node message is found to carry information that a main ring main node fails, an Edge-Hello message is sent to an auxiliary Edge node through a public port (two public ports) of the Edge node, and the Edge-Hello message carries the information that the main ring main node fails.
In the embodiment of the invention, when an Edge node receives a Major-Fault message through an Edge port of the Edge node, if the Major-Fault message is found to carry information that a Major ring master node fails, the Edge node determines that a link where a Major port of the Major ring master node is located and a link where a minor port of the Major ring master node is located both fail, at this time, the Edge node carries the information that the Major ring master node has failed in an Edge-Hello message sent to an auxiliary Edge node through a public port of the Edge node, for example, the Edge node indicates that the Major ring master node has failed by using a certain reserved position 1 in the Edge-Hello message.
In the embodiment of the invention, if a port on a transmission node of a main ring is recovered to an Up state from a Down state and the port is in a Block state currently, the transmission node of the main ring changes the port from the Block state to a Forwarding state when receiving an Edge-Hello message and the Edge-Hello message carries information that a main ring main node is invalid.
For example, in the application scenario shown in fig. 1, when receiving an Edge-Hello packet from a device 2 (Edge node), if a port on the device recovers from a Down state to an Up state and the port is currently in a Block state, when finding that the Edge-Hello packet carries information that a master node of a main ring has failed, the device immediately changes the port from the Block state to a Forwarding state, thereby shortening the time for migrating the Block state to the Forwarding state and accelerating the convergence speed of network recovery. Similarly, when receiving the Edge-Hello packet from the device 2 (Edge node), if a port on the device is restored to the Up state from the Down state and the port is currently in the Block state, the device 5 immediately changes the port from the Block state to the Forwarding state when finding that the Edge-Hello packet carries information that the master node of the primary ring has failed, thereby shortening the time for migrating the Block state to the Forwarding state and accelerating the convergence speed of network restoration.
In a specific implementation manner, when an Edge node sends an Edge-Hello packet, if a port on the Edge node is restored to an Up state from a Down state and the port is currently in a Block state, the Edge node changes the port from the Block state to a Forwarding state when finding that the Edge-Hello packet carries information that a primary ring master node has failed. For example, when the device 2 sends an Edge-Hello packet, if a port on the device is restored to an Up state from a Down state and the port is currently in a Block state, the port is immediately changed from the Block state to a Forwarding state when the Edge-Hello packet is found to carry information that a master node of a primary ring has failed, so that the time for migrating the Block state to the Forwarding state is shortened, and the convergence speed of network restoration is accelerated.
In the embodiment of the invention, after an auxiliary Edge node sends a Major-Fault message (the Major-Fault message carries information that a main ring main node has failed) to the Edge node through an Edge port of the auxiliary Edge node, if the auxiliary Edge node detects that a link where a main port of the main ring main node is located fails (when the auxiliary Edge node does not receive a Hello message from the main port of the main ring main node, it is determined that the link where the main port of the main ring main node is located fails), and detects that a link where a secondary port of the main ring main node is located fails to recover (when the auxiliary Edge node receives the Hello message from the secondary port of the main ring main node, it is determined that the link where the secondary port of the main ring main node is located fails to recover), when two common links between the Edge node and the auxiliary Edge node are incomplete (namely, the auxiliary Edge node does not receive an Edge-Hello message from the Edge node), the auxiliary edge node sends a Major ring-Fault message to the edge node through an edge port of the auxiliary edge node, and the Major ring-Fault message does not carry information that the Major ring master node has failed, that is, the Major ring master node carried in the Major ring-Fault message is cleared of the information that the Major ring master node has failed, for example, a certain reserved position 0 in the Major ring-Fault message indicates that the information that the Major ring master node has failed is cleared of the information that the Major ring master node has failed.
In the embodiment of the present invention, after an Edge node sends an Edge-Hello message (the Edge-Hello message carries information that a primary ring master node has failed) to an auxiliary Edge node through a public port of the Edge node, when the Edge node receives a Major-Fault message through the Edge port of the Edge node, if the Major-Fault message does not carry information that the primary ring master node has failed (i.e., a certain reserved position 0 in the Major-Fault message), the Edge node does not carry information that the primary ring has failed when sending the Edge-Hello message to the auxiliary Edge node through the public port of the Edge node, that is, the information that the primary ring master node carried in the Edge-Hello message has failed is removed, for example, the certain reserved position 0 in the Edge-Hello message indicates that the primary ring master node has failed is removed.
In the embodiment of the present invention, after an Edge node sends an Edge-Hello packet to an auxiliary Edge node through a public port of the Edge node (the Edge-Hello packet carries information that a master node of a main ring has failed), when the Edge node does not receive a Major-Fault packet through the Edge port of the Edge node within a specified time, the Edge node does not carry information that the master node of the main ring has failed when sending the Edge-Hello packet to the auxiliary Edge node through the public port of the Edge node, that is, information that the master node of the main ring has failed carried in the Edge-Hello packet is removed, for example, a certain reserved position 0 in the Edge-Hello packet indicates that the information that the master node of the main ring has failed is removed.
In the embodiment of the invention, after an Edge node sends an Edge-Hello message (the Edge-Hello message carries information that a main ring main node has failed) to an auxiliary Edge node through a public port of the Edge node, if the Edge node detects that a link where a main port of the main ring main node is positioned fails (when the Edge node does not receive the Hello message from the main port of the main ring main node, the link where the main port of the main ring main node is positioned is determined to have failed), and detects that a link where a secondary port of the main ring main node is positioned has failed recovery (when the Edge node receives the Hello message from the secondary port of the main ring main node, the link where the secondary port of the main ring main node is positioned is determined to have failed recovery), the Edge node does not carry the information that the main ring main node has failed when sending the Edge-Hello message to the auxiliary Edge node through the public port of the Edge node, that is, the information that the main ring host node has failed, which is carried in the Edge-Hello message, is cleared, for example, a certain reserved position 0 in the Edge-Hello message indicates that the information that the main ring host node has failed is cleared.
In summary, in the embodiment of the present invention, a port on a main ring transmission node is restored from a Down state to an Up state, and after the port is in a Block state, the port can be changed from the Block state to a Forwarding state in time, so that after a port failure is restored, the port is switched to the Forwarding state as soon as possible, traffic Forwarding is resumed as soon as possible, and network convergence performance is improved and accelerated.
Based on the same inventive concept as the above method, an embodiment of the present invention further provides a fast convergence system for port failure recovery, where the system is applied in a fast ring protection protocol RRPP network, and the system includes a main ring master node and a main ring transmission node, where the main ring transmission node includes an edge node and an auxiliary edge node where a sub-ring intersects with a main ring, where:
the primary ring master node is used for sending the Hello message through the secondary port if the Hello message sent by the primary port is not received from the secondary port within the specified time after the Hello message is sent through the primary port;
the main ring transmission node is configured to change a port from a Block state to a Forwarding state after receiving a Hello packet from a secondary port of the main ring master node when the port on the main ring transmission node is restored to a normal Up state from a fault Down state and the port is in a blocking Block state.
The main ring transmission node is specifically configured to update the timeout time of a timeout fail timer of the main ring transmission node by using the timeout time carried in a Hello message from a secondary port of the main ring master node, and change the port from a Block state to a Forwarding state after the fail timer is overtime; and the timeout time of the fail timer after updating is less than that of the fail timer before updating.
The auxiliary edge node is configured to send a main ring Fault notification message to the edge node through an edge port of the auxiliary edge node when not receiving a Hello message from a secondary port of the main ring host node and a Hello message from a main port of the main ring host node, where the main ring Fault notification message carries information that the main ring host node has failed;
the Edge node is configured to, when receiving a Major node-Fault message through an Edge port of the Edge node, send an Edge-Hello message to the auxiliary Edge node through a public port of the Edge node if the Major node-Fault message is found to carry information that the Major node has failed, and the Edge-Hello message carries the information that the Major node has failed;
the main ring transmission node is further configured to change the port from the Block state to the Forwarding state when the port on the main ring transmission node is restored from the Down state to the Up state and the port is in the Block state and an Edge-Hello message is received and carries information that the main ring host node has failed.
The auxiliary Edge node is further configured to send a Major-Fault message to the Edge node through the Edge port of the auxiliary Edge node after sending the Major-Fault message carrying the information that the Major-ring master node has failed to the Edge node through the Edge port of the auxiliary Edge node, when the Hello message from the Major port of the Major-ring master node is not received, but the Hello message from the minor port of the Major-ring master node is received, and the Edge-Hello message from the Edge node is not received, send the Major-Fault message to the Edge node through the Edge port of the auxiliary Edge node, and clear the information that the Major-ring master node has failed and is carried in the Major-Fault message in the sent Major-Fault message.
The Edge node is further configured to, after sending an Edge-Hello packet carrying information that the primary ring host node has failed to the secondary Edge node through the public port of the Edge node, when receiving a Major-Fault packet through the Edge port of the Edge node, if the Major-Fault packet does not carry the information that the primary ring host node has failed, clear the information that the primary ring host node has failed carried in the Edge-Hello packet when sending the Edge-Hello packet to the secondary Edge node through the public port of the Edge node; or after sending an Edge-Hello message carrying information that the main ring host node has failed to the auxiliary Edge node through the public port of the Edge node, when not receiving a Major-Fault message through the Edge port of the Edge node, and when sending the Edge-Hello message to the auxiliary Edge node through the public port of the Edge node, clearing the information that the main ring host node has failed carried in the Edge-Hello message; or after sending the Edge-Hello message carrying the information that the main ring host node has failed to the auxiliary Edge node through the public port of the Edge node, when receiving the Hello message from the auxiliary port of the main ring host node, and when sending the Edge-Hello message to the auxiliary Edge node through the public port of the Edge node, clearing the information that the main ring host node has failed carried in the Edge-Hello message.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present invention may be implemented by software plus a necessary general hardware platform, and certainly may also be implemented by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
Those skilled in the art will appreciate that the drawings are merely schematic representations of one preferred embodiment and that the blocks or flow diagrams in the drawings are not necessarily required to practice the present invention.
Those skilled in the art will appreciate that the modules in the devices in the embodiments may be distributed in the devices in the embodiments according to the description of the embodiments, and may be correspondingly changed in one or more devices different from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
The above disclosure is only for a few specific embodiments of the present invention, but the present invention is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present invention.
Claims (10)
1. A fast convergence method when a port fault is recovered is applied to a fast ring protection protocol RRPP network comprising a main ring main node and a main ring transmission node, wherein the main ring transmission node comprises an edge node and an auxiliary edge node, and a sub-ring and the main ring are intersected, and the method is characterized by comprising the following steps:
after the main ring main node sends the Hello message through the main port, if the Hello message sent by the main port is not received from the auxiliary port within the specified time, the Hello message is sent through the auxiliary port;
if a port on the transmission node of the main ring is recovered to a normal Up state from a fault Down state and the port is in a blocking Block state, the transmission node of the main ring changes the port from the Block state to a Forwarding state after receiving a Hello message from a secondary port of the main node of the main ring.
2. The method according to claim 1, wherein the process of the primary ring transmission node changing the port from a Block state to a Forwarding state specifically includes:
the main ring transmission node updates the timeout time of a timeout fail timer of the main ring transmission node by using the timeout time carried in a Hello message from a secondary port of the main ring main node, and changes the port from a Block state to a Forwarding state after the fail timer is overtime; and the timeout time of the fail timer after updating is less than that of the fail timer before updating.
3. The method of claim 1, wherein the method further comprises:
when the auxiliary edge node does not receive a Hello message from a secondary port of the main ring main node and a Hello message from a main port of the main ring main node, the auxiliary edge node sends a main ring Fault notification Major-Fault message to the edge node through the edge port of the auxiliary edge node, wherein the Major-Fault message carries information that the main ring main node is failed;
when the Edge node receives a Major-Fault message through an Edge port of the Edge node, if the Major-node message is found to carry information that the Major-ring host node has failed, sending a Major-ring integrity check Edge-Hello message to the auxiliary Edge node through a public port of the Edge node, wherein the Edge-Hello message carries the information that the Major-ring host node has failed;
and if the port on the main ring transmission node is restored to the Up state from the Down state and the port is in the Block state, the main ring transmission node changes the port from the Block state to the Forwarding state when receiving the Edge-Hello message and the Edge-Hello message carries the information that the main ring main node has failed.
4. The method of claim 3, wherein the secondary edge node sends a Major-Fault message carrying information that the primary ring master node has failed to the edge node through an edge port of the secondary edge node, and then further comprising:
when the auxiliary Edge node does not receive a Hello message from a main port of the main ring main node, but receives a Hello message from a secondary port of the main ring main node and does not receive an Edge-Hello message from the Edge node, the auxiliary Edge node sends a Major-Fault message to the Edge node through the Edge port of the auxiliary Edge node, and in the sent Major-Fault message, information that the main ring main node has failed, carried in the Major-Fault message, is eliminated.
5. The method of claim 4, wherein the Edge node sends an Edge-Hello packet carrying information that the primary ring master node has failed to the secondary Edge node through a public port of the Edge node, and then further comprising:
when the Edge node receives a Major ring-Fault message through an Edge port of the Edge node, if the Major ring-Fault message does not carry information that the Major ring master node has failed, the Edge node removes the information that the Major ring master node has failed, which is carried in the Edge-Hello message, when sending the Edge-Hello message to the auxiliary Edge node through a public port of the Edge node; or,
when the Edge node does not receive the Major-Fault message through the Edge port of the Edge node, and when the Edge-Hello message is sent to the auxiliary Edge node through the public port of the Edge node, the Edge node clears the information that the main ring main node carried in the Edge-Hello message is invalid; or,
and when the Edge node receives the Hello message from the auxiliary port of the main ring host node, and when the Edge node sends an Edge-Hello message to the auxiliary Edge node through the public port of the Edge node, clearing the information that the main ring host node fails, which is carried in the Edge-Hello message.
6. A rapid convergence system when a port fault is recovered is applied to a rapid ring protection protocol RRPP network and comprises a main ring main node and a main ring transmission node, wherein the main ring transmission node comprises a sub-ring and main ring intersected edge node and an auxiliary edge node; it is characterized in that the preparation method is characterized in that,
the primary ring master node is used for sending the Hello message through the secondary port if the Hello message sent by the primary port is not received from the secondary port within the specified time after the Hello message is sent through the primary port;
the main ring transmission node is configured to change a port from a Block state to a Forwarding state after receiving a Hello packet from a secondary port of the main ring master node when the port on the main ring transmission node is restored to a normal Up state from a fault Down state and the port is in a blocking Block state.
7. The system of claim 6,
the main ring transmission node is specifically configured to update the timeout time of a timeout fail timer of the main ring transmission node by using the timeout time carried in a Hello message from a secondary port of the main ring master node, and change the port from a Block state to a Forwarding state after the fail timer is overtime; and the timeout time of the fail timer after updating is less than that of the fail timer before updating.
8. The system of claim 6,
the auxiliary edge node is configured to send a main ring Fault notification message to the edge node through an edge port of the auxiliary edge node when not receiving a Hello message from a secondary port of the main ring host node and a Hello message from a main port of the main ring host node, where the main ring Fault notification message carries information that the main ring host node has failed;
the Edge node is configured to, when receiving a Major-Fault message through an Edge port of the Edge node, send a Major-ring integrity check Edge-Hello message to the auxiliary Edge node through a public port of the Edge node if the Major-ring-Fault message is found to carry information that the Major-ring master node has failed, where the Edge-Hello message carries the information that the Major-ring master node has failed;
the main ring transmission node is further configured to change the port from the Block state to the Forwarding state when the port on the main ring transmission node is restored from the Down state to the Up state and the port is in the Block state and an Edge-Hello message is received and carries information that the main ring host node has failed.
9. The system of claim 8,
the auxiliary Edge node is further configured to send a Major-Fault message to the Edge node through the Edge port of the auxiliary Edge node after sending the Major-Fault message carrying the information that the Major-ring master node has failed to the Edge node through the Edge port of the auxiliary Edge node, when the Hello message from the Major port of the Major-ring master node is not received, but the Hello message from the minor port of the Major-ring master node is received, and the Edge-Hello message from the Edge node is not received, send the Major-Fault message to the Edge node through the Edge port of the auxiliary Edge node, and clear the information that the Major-ring master node has failed and is carried in the Major-Fault message in the sent Major-Fault message.
10. The system of claim 9,
the Edge node is further configured to, after sending an Edge-Hello packet carrying information that the primary ring host node has failed to the secondary Edge node through the public port of the Edge node, when receiving a Major-Fault packet through the Edge port of the Edge node, if the Major-Fault packet does not carry the information that the primary ring host node has failed, clear the information that the primary ring host node has failed carried in the Edge-Hello packet when sending the Edge-Hello packet to the secondary Edge node through the public port of the Edge node; or after sending an Edge-Hello message carrying information that the main ring host node has failed to the auxiliary Edge node through the public port of the Edge node, when not receiving a Major-Fault message through the Edge port of the Edge node, and when sending the Edge-Hello message to the auxiliary Edge node through the public port of the Edge node, clearing the information that the main ring host node has failed carried in the Edge-Hello message; or after sending the Edge-Hello message carrying the information that the main ring host node has failed to the auxiliary Edge node through the public port of the Edge node, when receiving the Hello message from the auxiliary port of the main ring host node, and when sending the Edge-Hello message to the auxiliary Edge node through the public port of the Edge node, clearing the information that the main ring host node has failed carried in the Edge-Hello message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310362310.3A CN103414591B (en) | 2013-08-19 | 2013-08-19 | Method for rapidly converging when a kind of port failure recovers and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310362310.3A CN103414591B (en) | 2013-08-19 | 2013-08-19 | Method for rapidly converging when a kind of port failure recovers and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103414591A CN103414591A (en) | 2013-11-27 |
| CN103414591B true CN103414591B (en) | 2016-08-31 |
Family
ID=49607577
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310362310.3A Active CN103414591B (en) | 2013-08-19 | 2013-08-19 | Method for rapidly converging when a kind of port failure recovers and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103414591B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104717147B (en) * | 2013-12-11 | 2018-06-15 | 新华三技术有限公司 | rapid ring protection protocol load sharing method and device |
| CN105591860B (en) * | 2015-09-25 | 2019-03-12 | 新华三技术有限公司 | Looped network protecting method and device based on RRPP |
| CN106059880B (en) * | 2016-05-27 | 2020-09-25 | 新华三技术有限公司 | Link fault processing method and device |
| CN106911380B (en) * | 2017-02-28 | 2019-07-05 | 新华三技术有限公司 | A kind of path restoration method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101068169A (en) * | 2007-06-05 | 2007-11-07 | 杭州华三通信技术有限公司 | Loop fault detecting method, subring main node and subring |
| CN101141383A (en) * | 2006-09-07 | 2008-03-12 | 华为技术有限公司 | Method, system and two-layered equipment of implementing two-layered multicast forwarding path rapid convergence |
| US7406614B2 (en) * | 2004-12-23 | 2008-07-29 | Microsemi Corp. - Analog Mixed Signal Group, Ltd. | Electronically implemented dynamic start up method for ports with inrush current limiting functionality |
| US7620846B2 (en) * | 2004-10-07 | 2009-11-17 | Cisco Technology, Inc. | Redundant power and data over a wired data telecommunications network |
-
2013
- 2013-08-19 CN CN201310362310.3A patent/CN103414591B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7620846B2 (en) * | 2004-10-07 | 2009-11-17 | Cisco Technology, Inc. | Redundant power and data over a wired data telecommunications network |
| US7406614B2 (en) * | 2004-12-23 | 2008-07-29 | Microsemi Corp. - Analog Mixed Signal Group, Ltd. | Electronically implemented dynamic start up method for ports with inrush current limiting functionality |
| CN101141383A (en) * | 2006-09-07 | 2008-03-12 | 华为技术有限公司 | Method, system and two-layered equipment of implementing two-layered multicast forwarding path rapid convergence |
| CN101068169A (en) * | 2007-06-05 | 2007-11-07 | 杭州华三通信技术有限公司 | Loop fault detecting method, subring main node and subring |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103414591A (en) | 2013-11-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8031590B2 (en) | Method, apparatus and system for ring protection | |
| EP2352253A1 (en) | Method and apparatus for protecting link aggregation group of ethernet ring | |
| US8886831B2 (en) | System and methodology for fast link failover based on remote upstream failures | |
| JP5369228B2 (en) | Method and apparatus for restoring unicast traffic | |
| US10708081B2 (en) | Failure protection method based on ring protection link, device, and system | |
| US8761052B2 (en) | Method for forwarding protocol frames in spanning rings and a shared node of multi-rings in the Ethernet | |
| EP2458797A1 (en) | Method, device and system for updating ring network topology information | |
| CN101060485B (en) | Topology changed messages processing method and processing device | |
| CN101958831B (en) | Ethernet ring network failure recovery method, Ethernet ring network and switching equipment | |
| CN103200109B (en) | A kind of ospf neighbor relationship management method and equipment | |
| WO2014090083A1 (en) | Service bearing method and apparatus during distributed resilient network interconnect | |
| CN103414591B (en) | Method for rapidly converging when a kind of port failure recovers and system | |
| CN102238067B (en) | Switching method and device on Rapid Ring Protection Protocol (RRPP) ring | |
| CN103873333A (en) | Ring network three-layer convergence method and device | |
| CN103825754B (en) | Ring network multipoint fault discovery and recovery processing method | |
| EP2533470A1 (en) | Method and equipment for preventing repeated refreshing of ethernet ring node address table | |
| WO2017000096A1 (en) | Link recovery method and network device | |
| CN103746912B (en) | Data message transmission method and equipment based on subring link | |
| CN112995002A (en) | Switch ring network design method, switch and storage medium | |
| CN108833247B (en) | Method and device for re-switching after link failure recovery | |
| CN106130783B (en) | Port fault processing method and device | |
| CN104184639B (en) | A kind of processing method and equipment of ERPS loops multipoint fault | |
| CN104869016B (en) | A kind of transmission method and equipment of data message | |
| CN105991556B (en) | LSP sequence number overturning processing method and device and routing bridge RB | |
| CN104579736A (en) | Loop circuit data transmission method and node equipment |
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 | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: NEW H3C TECHNOLOGIES Co.,Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: HANGZHOU H3C TECHNOLOGIES Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230620 Address after: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province Patentee after: H3C INFORMATION TECHNOLOGY Co.,Ltd. Address before: 310052 Changhe Road, Binjiang District, Hangzhou, Zhejiang Province, No. 466 Patentee before: NEW H3C TECHNOLOGIES Co.,Ltd. |