CN101136830B - Loop prevention method after RPR bridge fault recovery - Google Patents
Loop prevention method after RPR bridge fault recovery Download PDFInfo
- Publication number
- CN101136830B CN101136830B CN2006100374378A CN200610037437A CN101136830B CN 101136830 B CN101136830 B CN 101136830B CN 2006100374378 A CN2006100374378 A CN 2006100374378A CN 200610037437 A CN200610037437 A CN 200610037437A CN 101136830 B CN101136830 B CN 101136830B
- Authority
- CN
- China
- Prior art keywords
- rpr
- ring
- fault
- cross
- fault recovery
- 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.)
- Expired - Fee Related
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/42—Loop networks
- H04L12/437—Ring fault isolation or reconfiguration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
Abstract
The method includes steps: (1) when learning that fault of the fault point in RPR bridge ring is recovered to normal, the method sets up maximal transmission unit value of the fault recovery node (FRN) to a prearranged value, and sends notification message in use for informing the fault point that the fault is recovered to transannular bridge device (TBD) in RPR bridge ring; (2) each RPR TBD in RPR bridge ring receives the notification message sent from FRN, as well as tests operating mode of each RPR TBD, and makes only one RPR TBD keep in main use state. Through cooperation between FRN and TBD, the invention ensures that transannular operation is forwarded correctly so as to solve loop issue occurs possibly after the fault point is recovered.
Description
Technical field
The present invention relates to network communications technology field, relate in particular to the loop prevention method after a kind of fault recovery of RPR bridge.
Background technology
Stretch grouped data ring (Resilient Packet Ring, RPR) technology is new network architecture and the technology that designs based on the requirement of grouping metropolitan area network in order to satisfy; Be a kind of loop network of being made up of Packet Switch Node, adjacent node connects by a pair of optical fiber; Its network topology is based on the ring of two rightabout transmission.RPR has the technical characterstic of the following aspects: 1, transmission bandwidth is effectively multiplexing; 2, encircle bridge protection switch function fast; 3, Tuo Pu automatic discovery.
The loop network of using RPR technology composition is called the RPR loop network, can abbreviate the RPR ring as; PSE on the loop network is called RPR equipment.The 48 bit mac addresses of using in RPR equipment adopts Ethernet are used for unique identification RPR equipment as address designation, and when carrying two layers of Ethernet message by the mode of Ethernet Over RPR, then the RPR ring can also be called RPR bridged ring or bridge mode RPR ring.Equipment on the RPR bridged ring can also be called the RPR bridge device, and the MAC Address on the RPR bridge device can be called the RPR MAC Address again.As shown in Figure 1, the structural representation that two RPR bridged rings intersect at two RPR bridge devices has been described.
In Fig. 1, there are two RPR bridged rings, are respectively RPR bridged ring 1 and RPR bridged ring 2.Have 4 RPR bridge devices on each RPR bridged ring respectively, RPR bridged ring 1 and RPR bridged ring 2 intersect at RPR cross-ring bridge device 1 and cross-ring bridge device 2 simultaneously.Wherein, described cross-ring bridge device be cross-over connection simultaneously on two RPR bridged rings, be responsible for the forwarding of data message between two RPR bridged rings.In order to simplify description, abbreviate the RPR cross-ring bridge device as cross-ring bridge device in the following description.
On the RPR bridged ring, because what carry on the RPR bridged ring is two layers of Ethernet message, and the message between the RPR bridged ring is to transmit by address resolution protocol (MAC), therefore the RPR cross-ring bridge device that intersects at two RPR bridged rings will produce the loop, also promptly between as shown in Figure 1 RPR cross-ring bridge device 1 and RPR cross-ring bridge device 2, produce the loop, the broadcast storm phenomenon occurs.
Current existent method is by Spanning-Tree Protocol (Spanning Tree Protocol, STP) or RSTP (Rapid Spanning Tree Protocol, RSTP) agreement is carried out the link reduction, generate loop-free minimum spanning tree, transmit message on two layers of Ethernet according to minimum spanning tree then, form loop to prevent double layer network communication.When occurring equipment or link failure on the double layer network, STP or RSTP can carry out minimum spanning tree calculating again, obtain a new forwarding tree, thereby after having guaranteed that fault takes place, protect professional operate as normal.
Though said method can solve the problem that may occur between the cross-ring bridge device, but this method is but because the convergence rate of STP, RSTP is slow, even RSTP also can only reach second the convergence rate level of level, make the network service time lengthening, the load of emphasis network communication.
Also gone out the guard method of a kind of RPR bridge redundancy now, this method is by having introduced a kind of new protocol type, the triggering that utilizes the mutual of this agreement and monocycle RPR protection to switch, and ability is switched in the protection that can reach the 100ms level.
But when between two RPR cross-ring bridge devices, occurring two place faults in the ring, reach the both sides that appear at a RPR cross-ring bridge device respectively, under the situation as shown in Figure 2, for guaranteeing that the arbitrfary point all can reach between two bridged rings (RPR bridged ring 1 and RPR bridged ring 2), two RPR cross-ring bridge devices all need to be responsible for the forwarding (all being in the main state of using) of transannular business.In this case, after one of them node failure (as fault point 1) recovers, there is not the fault point to exist between RPR bridge device 1 and RPR bridge device 2 adjacent regions, the mode of operation of RPR bridge device 1 and RPR bridge device 2 all can be changed to normal (normal) state, recovers the fault point, back and just can transmit data message.Because the RPR cross-ring bridge device can not perceive this variation immediately and can not change self working state immediately, these two RPR cross-ring bridge devices still all are in main with (Master) state, be responsible for the forwarding of the data service of transannular link simultaneously, will broadcast loop problem like this, as shown in Figure 3.
In existing a kind of RPR bridge redundancy guard method of mentioning in front, it is to adopt just having recovered normal former fault point on the RPR ring, and delay a period of time carries out the message forwarding again or carries out the forwarding of broadcasting data messages.And, a clear and definite solution is not proposed in the existing this scheme for when the situation that two fault points occur.
Summary of the invention
In view of above-mentioned existing in prior technology problem, the purpose of this invention is to provide the loop prevention method behind a kind of RPR bridge fault recovery, this method solves under the application scenarios of RPR phase cross ring, issuable broadcasting loop problem when having occurred simultaneously on RPR bridged ring that recover one of them fault point after the situation of two fault points.
To achieve these goals, the invention provides the loop prevention method behind a kind of RPR bridge fault recovery, this method may further comprise the steps:
A. after the fault recovery of the fault point in knowing the RPR bridged ring, the maximum transmission unit value of fault recovery node is made as a predetermined value, and cross-ring bridge device sends the notice message that the fault that is used to notify this fault point has been recovered in described RPR bridged ring; Wherein, the predetermined value of described maximum transmission unit value is for passing through by the guarantee agreement message, and the intransitable value of data message, it is worth between 30 to 81 bytes; Described fault recovery node is the equipment contiguous with described fault point;
B. each the RPR cross-ring bridge device in the described RPR bridged ring receives the notice message that the fault recovery node is sent, and detects the operating state of RPR cross-ring bridge device separately, only makes one of them master remain the main state of using with the RPR cross-ring bridge device.
Preferable, described steps A also comprises:
Before the maximum transmission unit value of fault recovery node is set, write down the normal maximum transmission unit value of described fault recovery node.
Preferable, after the fault recovery of the fault point in described steps A in the RPR bridged ring is normal, the maximum transmission unit value of fault recovery node is made as before the predetermined value, also comprise:
Trigger network topological convergence process;
After steps A, also comprise: after topological convergence, the maximum transmission unit value of described fault recovery node is reverted to the normal maximum transmission unit value that is write down.
Preferable, described steps A also comprises:
Maximum transmission unit value is made as after the described predetermined value, and the operating state of setting described fault recovery node is a normal condition.
Preferable, the predetermined value of described maximum transmission unit value is for passing through by the guarantee agreement message, and the intransitable value of data message, it is worth between 30 to 81.
Preferable, described step B also comprises:
Respectively be in the main priority of using the RPR cross-ring bridge device of state, make the RPR cross-ring bridge device of limit priority remain the main state of using.
Preferable, the fault of knowing the fault point in the RPR bridged ring in the described steps A has returned to normally and has been:
When described fault point is RPR bridge device in the described RPR bridged ring, self know that by described fault point its fault recovered normal;
When described fault point is link in the described RPR bridged ring, by knowing that with the contiguous described fault recovery node in described fault point the fault of described fault point recovered normal.
Preferable, the fault recovery node in the described RPR bridged ring is RPR bridge device or RPR cross-ring bridge device.
Preferable, described notice message is a kind of message that expands realization on existing message basis, or a kind of message of redetermination.
Preferable, among the described step B, be stand-by state when a cross-ring bridge device detects self operating state, then its received described notice message is not handled.
Preferable, among the described step B, be mainly use state when a cross-ring bridge device detects self operating state, but when not having connected other cross-ring bridge devices that are in main usefulness state; Be mainly use state perhaps, but its priority is not then handled its received described notice message when all being higher than the connected priority that is in main other cross-ring bridge devices with state when a cross-ring bridge device detects self operating state.
Preferable, among the described step B, when a cross-ring bridge device detects self operating state is mainly use state, and connected being in when having the higher cross-ring bridge device of priority in main other cross-ring bridge devices with state, and the cross-ring bridge device that priority is low withdraws from the state of using of leading.
Implement the present invention, have following beneficial effect: the present invention sends the notice message to cross-ring bridge device by the fault recovery node, behind the notified message of cross-ring bridge device, cross-ring bridge device can be according to own operating state/priority and the operating state of other cross-ring bridge devices/preferential utmost point, carry out follow-up action (as keep main with state or withdraw from the master and use state).Like this can be after the fault recovery of fault point, have only a cross-ring bridge device to be in the master and use state, guarantee the correct forwarding of transannular business, solved the fault point and recovered the loop problem of appearance in the information transmission of back, to business in encircling also not influence, simultaneously to the monocycle protocol convergence without any influence.
Description of drawings
Fig. 1 is a prior art RPR bridged ring network topology structure schematic diagram.
Fig. 2 is the communication scheme under the situation that has occurred two faults on RPR bridged ring in the prior art RPR bridged ring network simultaneously.
Fig. 3 is under the situation that has occurred two faults on RPR bridged ring in the prior art RPR bridged ring network simultaneously and produce the schematic diagram of broadcasting loop when a fault recovery.
Fig. 4 in the RPR bridge of the present invention during non-cross-ring bridge device fault recovery the fault recovery node avoid producing the method flow diagram of broadcasting loop.
Fig. 5 in the RPR bridge of the present invention during non-cross-ring bridge device fault recovery cross-ring bridge device avoid producing the method flow diagram of broadcasting loop.
Embodiment
Describe the preferred embodiments of the present invention in detail below in conjunction with accompanying drawing.
The invention provides the loop prevention method behind a kind of RPR bridge fault recovery, this method solves under the application scenarios of RPR phase cross ring, issuable broadcasting loop problem when recovering a fault point has appearred under the situation of two fault points on the RPR bridged ring simultaneously.Loop prevention method behind the RPR bridge fault recovery is by fault recovery node and cross-ring bridge device cooperation each other, and the passing through of data message on the control RPR ring avoids RPR to encircle and the loop phenomenon occurs.
At first please consult Fig. 2 again, exemplified a RPR bridged ring network, two crossing RPR bridged rings are wherein arranged, comprise RPR bridge device 1, RPR bridge device 2, RPR bridge device 3, RPR bridge device 4 and RPR cross-ring bridge device 1 and RPR cross-ring bridge device 2 in these two RPR bridged rings.Under fault point 1 and fault point 2 simultaneous situations, the mode of operation of RPR bridge device 1 and RPR bridge device 2 all is a protected mode, i.e. wrap state, and 1 does not have message and passes through in the fault point, does not have the appearance of broadcasting loop yet.And can visit mutually between the arbitrfary point on two RPR bridged rings for guaranteeing, the operating state of RPR cross-ring bridge device 1 and RPR2 cross-ring bridge device all is main with (Master) state, be in main cross-ring bridge device with state, can be responsible for the forwarding of transannular business, promptly data service can be transmitted in different RPR bridged rings, can visit mutually between the arbitrary node in such two RPR bridged rings.
After recover fault point 1, there is not the fault point to exist between RPR bridge device 1 and RPR bridge device 2 adjacent regions, the mode of operation of RPR bridge device 1 and RPR bridge device 2 all can be changed to normal condition.After the mode of operation of RPR bridge device 1 and RPR bridge device 2 became normal condition, data message just can pass through this fault point.Because the RPR cross-ring bridge device can not perceive this variation immediately and can not carry out the migration of state, will may broadcast loop problem as shown in Figure 3.Below in conjunction with accompanying drawing 4 and accompanying drawing 5, illustrate among the present invention, in the fault point 1 or fault point 2 when recovering, how, fault recovery node and cross-ring bridge device handle by having been carried out corresponding cooperation, avoid the appearance of Fig. 3 intermediate ring road phenomenon.
See also Fig. 4, this figure be among the present invention to the main flow chart of fault recovery node processing, alleged herein fault recovery node refers to the equipment contiguous with this fault point, for fault point 1, its fault recovery node refers to RPR bridge device 1 or the RPR bridge device 2 with fault point 1 vicinity.When recovering with the fault point among Fig. 31 is that example describes, and this handling process may further comprise the steps:
Step 40: the fault of the fault point 1 in knowing the RPR bridged ring can trigger the topological convergence process one time after having recovered normally; In the RPR bridged ring, the fault point can be the RPR bridge device, also can be the link that connects the RPR bridge device.Herein, because fault point 1 is a link, after its fault recovery, its limit state disappears, and fault recovery node (RPR bridge device 1 or RPR bridge device 2) can know that the fault of this fault point 1 recovered normal.Under other certain situation, for example, this fault point is a RPR bridge device in the RPR bridged ring, and in this case, this fault point self just can know whether its fault has returned to normally.
Step 41: after topology changes, finish before the topological convergence, need to judge whether the operating state of this fault recovery node (RPR bridge device 1 or RPR bridge device 2) or fault point (when this fault point is equipment in the RPR bridged ring) changes;
Is step 42: the operating state that this fault recovery node (RPR bridge device 1 or RPR bridge device 2) detects himself normal (normal) state from guard mode (wrap) state variation? herein, if testing result is when being, be fault recovery node when having become normally (normal) state, then go to step 43; If testing result for not the time, when promptly the fault recovery node still is in protection (wrap) state, is then waited for the scheduled time (as 1～3 second), go to step 41 and proceed detection;
In this step, if when the fault point is the RPR bridge device, whether the operating state that then detects this fault point is changed to normal condition from guard mode, same, when the test results is yes, goes to step 43; When testing result for not the time, wait for the scheduled time, go to step 41 and proceed to detect;
Step 43: this fault recovery node sends the notice message on two RPR bridged rings, the fault at this 1 place, fault point has been recovered normal information be notified to RPR cross-ring bridge device 1 and RPR cross-ring bridge device 2;
The described notice message that the fault recovery node is sent can be to expand to realize on existing message basis, also can be to adopt new type of message to realize;
Step 44: the MTU (Maximum TransmissionUnit, current normal value MTU) that write down this fault recovery node; And the MTU value of this fault recovery node is provided with a predetermined value, preferably, this definite value is the value that is between the 30-81;
The purpose of the MTU definite value of this setting is to guarantee that protocol massages such as TP, TC can pass through this fault point 1, and data message can not pass through.Because the length of TP message is 26 bytes, the length of TC message is 29 bytes, the value of this MTU requires more than or equal to 30 bytes, and the RPR message length that comprises growth data is at least 18+64 byte (the Ethernet minimum length is 64 bytes)=82 bytes, so the value of this MTU requires to be less than or equal to 81 bytes, the scope that this MTU value can be provided with is 30 to 81 bytes.Such as being set to 64 bytes, when the information of carrying out in the RPR bridged ring was transmitted, because MTU is revised as after the predetermined value, data message can't pass through described fault point, can effectively avoid loop.
Step 45: after topological convergence, the MTU value of this fault recovery node is reverted to the normal value of the MTU that previous step writes down; Further, operating state that can this fault recovery node is set to normal condition;
Step 47: EP (end of program).
In like manner, for fault point 2, its fault recovery node is respectively RPR cross-ring bridge device 1 or RPR cross-ring bridge device 2, when recover fault point 2, the fault recovery node can perceive fault point 2 at an easy rate and recover normal, and can according to the change self working state, to avoid occurring loop, the process of this change oneself state will 5 describe in conjunction with the accompanying drawings.
When a certain cross-ring bridge device receive in the step 43 of above-mentioned Fig. 4 inform the notice message that has recovered fault point 1 time, perhaps when its fault that detects contiguous fault point 2 had been recovered, then this cross-ring bridge device will carry out corresponding data handling procedure according to own own operating state and priority.Main purpose is to make in all cross-ring bridge devices, making wherein only has a cross-ring bridge device to keep the main state of using, carrying out the transannular of data message transmits, other cross-ring bridge device withdraws from the main state of using, become stand-by state, can not carry out the transannular forwarding of data message, thereby avoid the loop among Fig. 3.Priority described herein is meant in advance and is a set property value of each cross-ring bridge device according to certain rule, being provided with of the priority of cross-ring bridge device can be disposed as required voluntarily, for example, the device id of cross-ring bridge device number, IP address, MAC Address, self-defining identifier or self-defining sequence number or the like.
The processing procedure of cross-ring bridge device is described below in conjunction with flow chart 5:
Step 51: cross-ring bridge device (for example cross-ring bridge device 1 or cross-ring bridge device 2) receives the notice message that sends over from the fault recovery node, perhaps detects contiguous fault point and recovers;
Step 52: judge this moment, whether the operating state of itself was in the main state of using, and did not use state if it is not the master, then the notice message that is received was not handled, and was gone to step 56; Use state if it is the master, then forward step 53 to;
Step 53: whether this cross-ring bridge device has coupled other cross-ring bridge devices that are in main with state on the RPR bridged ring, if do not have, then this cross-ring bridge device still keeps the master to use state, and the notice message that is received is not handled, and goes to step 56; If coupled main other cross-ring bridge devices with state that are in are arranged, then forward step 54 to;
Step 54: whether the priority of judging this cross-ring bridge device is lower than the coupled main priority of using other cross-ring bridge devices of state that is in, if judged result is for denying, then this cross-ring bridge device still keeps the main state of using, and the notice message that is received do not handled, and commentaries on classics step 56, if judged result is for being then to go to step 55;
Step 55: this cross-ring bridge device withdraws from the main state of using, and no longer is responsible for the forwarding of transannular business;
Step 56: flow process finishes.
In sum, the present invention sends the notice message to cross-ring bridge device by the fault recovery node, behind the notified message of cross-ring bridge device, cross-ring bridge device 1 and cross-ring bridge device 2 all can be according to the operating state/priority of oneself and the operating state of other cross-ring bridge devices/preferential utmost points, carry out follow-up action (as keep main with state or withdraw from the main state of using).Like this can be after the fault recovery of fault point, have only a cross-ring bridge device still to be in the main state of using, guarantee the correct forwarding of transannular business, solve the fault point and recovered the loop problem of appearance in the information transmission of back, to business in encircling also not influence, simultaneously to the monocycle protocol convergence without any influence.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.
Claims (11)
1. the loop prevention method behind the RPR bridge fault recovery is characterized in that, said method comprising the steps of:
A. the fault recovery of the fault point in knowing the RPR bridged ring normal after, the maximum transmission unit value of fault recovery node is made as a predetermined value, and cross-ring bridge device sends the notice message that the fault that is used to notify this fault point has been recovered in described RPR bridged ring; Wherein, the predetermined value of described maximum transmission unit value is for passing through by the guarantee agreement message, and the intransitable value of data message, it is worth between 30 to 81 bytes; Described fault recovery node is the equipment contiguous with described fault point;
B. each the RPR cross-ring bridge device in the described RPR bridged ring receives the notice message that the fault recovery node is sent, and detects the operating state of RPR cross-ring bridge device separately, only makes one of them master remain the main state of using with the RPR cross-ring bridge device.
2. the loop prevention method behind the RPR bridge fault recovery as claimed in claim 1 is characterized in that, described steps A also comprises:
Before the maximum transmission unit value of fault recovery node is set, write down the normal maximum transmission unit value of described fault recovery node.
3. the loop prevention method behind the RPR bridge fault recovery as claimed in claim 2, it is characterized in that, after the fault recovery of the fault point in described steps A in the RPR bridged ring is normal, the maximum transmission unit value of fault recovery node is made as before the predetermined value, also comprises:
Trigger network topological convergence process;
After steps A, also comprise: after topological convergence, the maximum transmission unit value of described fault recovery node is reverted to the normal maximum transmission unit value that is write down.
4. the loop prevention method behind the RPR bridge fault recovery as claimed in claim 1 is characterized in that: described steps A also comprises:
Maximum transmission unit value is made as after the described predetermined value, and the operating state of setting described fault recovery node is a normal condition.
5. as the loop prevention method behind each described RPR bridge fault recovery of claim 1 to 4, described step B also comprises:
Respectively be in the main priority of using the RPR cross-ring bridge device of state, make the RPR cross-ring bridge device of limit priority remain the main state of using.
6. the loop prevention method behind the RPR bridge fault recovery as claimed in claim 4 is characterized in that, the fault of knowing the fault point in the RPR bridged ring in the described steps A has returned to normally and has been:
When described fault point is RPR bridge device in the described RPR bridged ring, self know that by described fault point its fault recovered normal;
When described fault point is link in the described RPR bridged ring, by knowing that with the contiguous described fault recovery node in described fault point the fault of described fault point recovered normal.
7. the loop prevention method behind the RPR bridge fault recovery as claimed in claim 6 is characterized in that, the fault recovery node in the described RPR bridged ring is RPR bridge device or RPR cross-ring bridge device.
8. as the loop prevention method behind each described RPR bridge fault recovery of claim 1 to 4, it is characterized in that described notice message is a kind of message that expands realization on existing message basis, or a kind of message of redetermination.
9. as the loop prevention method behind each described RPR bridge fault recovery of claim 1 to 4, it is characterized in that, among the described step B, be stand-by state, then its received described notice message do not handled when a cross-ring bridge device detects self operating state.
10. the loop prevention method behind the RPR bridge fault recovery as claimed in claim 5, it is characterized in that, among the described step B, be mainly use state when a cross-ring bridge device detects self operating state, but when not having connected other cross-ring bridge devices that are in main usefulness state; Be mainly use state perhaps, but its priority is not then handled its received described notice message when all being higher than the connected priority that is in main other cross-ring bridge devices with state when a cross-ring bridge device detects self operating state.
11. the loop prevention method behind the RPR bridge fault recovery as claimed in claim 5, it is characterized in that, among the described step B, when a cross-ring bridge device detects self operating state is the main state of using, and connected being in when having the higher cross-ring bridge device of priority in main other cross-ring bridge devices with state, the cross-ring bridge device that priority is low withdraws from the state of using of leading.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006100374378A CN101136830B (en) | 2006-09-01 | 2006-09-01 | Loop prevention method after RPR bridge fault recovery |
| PCT/CN2007/002082 WO2008028392A1 (en) | 2006-09-01 | 2007-07-06 | A loop avoidance method after the recovery from the rpr faults |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006100374378A CN101136830B (en) | 2006-09-01 | 2006-09-01 | Loop prevention method after RPR bridge fault recovery |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101136830A CN101136830A (en) | 2008-03-05 |
| CN101136830B true CN101136830B (en) | 2011-01-12 |
Family
ID=39156829
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2006100374378A Expired - Fee Related CN101136830B (en) | 2006-09-01 | 2006-09-01 | Loop prevention method after RPR bridge fault recovery |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101136830B (en) |
| WO (1) | WO2008028392A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107547331A (en) * | 2017-09-25 | 2018-01-05 | 新华三技术有限公司 | The forwarding state control method and device of RPR nodes in RPR intersecting rings |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0349099A2 (en) * | 1988-06-27 | 1990-01-03 | Digital Equipment Corporation | Transparent load sharing for parallel networks |
| CN1479455A (en) * | 2002-08-29 | 2004-03-03 | 华为技术有限公司 | Fast replacing method of elastic group loop network |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7792023B2 (en) * | 2000-06-30 | 2010-09-07 | Arris Group | Per-flow rate control for an asynchronous metro packet transport ring |
| JP2005130049A (en) * | 2003-10-21 | 2005-05-19 | Fujitsu Ltd | Node |
| CN1941730A (en) * | 2005-09-26 | 2007-04-04 | 华为技术有限公司 | Method for protecting RPR bridge redundancy |
-
2006
- 2006-09-01 CN CN2006100374378A patent/CN101136830B/en not_active Expired - Fee Related
-
2007
- 2007-07-06 WO PCT/CN2007/002082 patent/WO2008028392A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0349099A2 (en) * | 1988-06-27 | 1990-01-03 | Digital Equipment Corporation | Transparent load sharing for parallel networks |
| CN1479455A (en) * | 2002-08-29 | 2004-03-03 | 华为技术有限公司 | Fast replacing method of elastic group loop network |
Non-Patent Citations (1)
| Title |
|---|
| JP特开2005-130049A 2005.05.19 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101136830A (en) | 2008-03-05 |
| WO2008028392A1 (en) | 2008-03-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100409634C (en) | Fast ring network protecting method and system | |
| EP1768319A1 (en) | Method of inter-RPR-ring bridge redundancy | |
| EP2352253A1 (en) | Method and apparatus for protecting link aggregation group of ethernet ring | |
| CN100450036C (en) | Method and apparatus for preventing loop when RRPP and partial STP network damage recovery | |
| CN101345683B (en) | Protocol packet transmission control method of Ethernet automatic protection switch system | |
| CN101060485B (en) | Topology changed messages processing method and processing device | |
| US8570858B2 (en) | Control method for protecting failure recovery of ethernet ring and ethernet ring nodes | |
| WO2009101531A2 (en) | System and method for network recovery from multiple link failures | |
| WO2011095101A1 (en) | Linear 1: n protection method, device and system for packet transport network | |
| JP2007174119A (en) | Layer 2 network | |
| CN100512220C (en) | Method for realizing service protection on elastic group ring | |
| WO2012142870A1 (en) | Method, active device and standby device for automatic protection switching | |
| CN101989930B (en) | Method and switching equipment for realizing Ethernet double loop | |
| WO2010102490A1 (en) | Address update method for ports of switching node, and switching node in ethernet ring network | |
| CN110635940B (en) | Main/standby switching method of EAPS Ethernet ring network | |
| JP5491623B2 (en) | Address refresh method and system | |
| CN102957588A (en) | Method and system for protecting looped network from broadcast storm | |
| CN101534234B (en) | Interworking Ethernet ring network protection method and system | |
| CN101136838B (en) | Bridge mode elastic grouping ring transannular bridge equipment redundancy protecting method | |
| CN101237319B (en) | Time synchronization method in Ethernet ring network and Ethernet ring system | |
| WO2008106874A1 (en) | Two node fault handling method and system for two loop-span rpr | |
| CN101136830B (en) | Loop prevention method after RPR bridge fault recovery | |
| CN100464528C (en) | Method and system for preventing circuit loop after failure recovery | |
| CN103840965B (en) | Method for enhancing quick fault convergence in RSTP | |
| WO2011000184A1 (en) | Method and system for refreshing the single ring address in an ethernet ring |
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 | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110112 Termination date: 20120901 |