CN101227372B - Ether ring net protection method, transmission node and host node - Google Patents
Ether ring net protection method, transmission node and host node Download PDFInfo
- Publication number
- CN101227372B CN101227372B CN2008100579432A CN200810057943A CN101227372B CN 101227372 B CN101227372 B CN 101227372B CN 2008100579432 A CN2008100579432 A CN 2008100579432A CN 200810057943 A CN200810057943 A CN 200810057943A CN 101227372 B CN101227372 B CN 101227372B
- Authority
- CN
- China
- Prior art keywords
- message
- timer
- ring
- flush
- fdb
- 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
Images
Landscapes
- Small-Scale Networks (AREA)
Abstract
The invention provides an looped network protecting method, a transmission node and a main node, the main node is provided with a timer, the transmission node which detects looped network faults and sends the faults to the main node, the main node sends looped network refreshing message after the main node receives looped network fault message, and meanwhile the timer is started, if the main node does not receive response message in predetermined time, and then looped network refreshing message is sent again, wherein, the response message is sent to the main node after the transmission node which detects looped network faults receives the looped network refreshing message. The method, the transmission node and the main node prevent the looped network refreshing message from loosing in the process of transmitting, avoid serious results such as obstructed looped network link circuit, interrupted business and the like which are caused by the lost of the looped network refreshing message.
Description
Technical field
The present invention relates to the network communications technology, particularly a kind of Ethernet ring protection method, transmission node and host node.
Background technology
It is online that the method for Ethernet automatic protection switching is applied in Ethernet ring, and there is a host node in an Ethernet looped network, and other network node is a transmission node.Fig. 1 is the structural representation of an Ethernet looped network in the prior art, S1 is a host node among the figure, and other S2 to S6 is a transmission node, wherein, host node is connected in two online ports of Ethernet ring one and is master port (P1 among Fig. 1), and another is secondary port (P2 among Fig. 1).If looped network does not break down, then the secondary port of host node is a blocked state; If looped network breaks down, then the open secondary port of host node is transmitted data message, to keep the connectedness of looped network.
The guard method of breaking down at looped network in the prior art is: when looped network breaks down; as shown in Figure 1; suppose that ring network fault point is between transmission node S4 and S5; after S4 and S5 detect the fault generation; on looped network, send ring network fault (LINK_DOWN) message; each transmission node is left intact to this LINK_DOWN message after receiving this LINK_DOWN message, directly this LINK_DOWN message is transmitted until host node S1.Host node S1 opens secondary port after receiving this LINK_DOWN message; and on looped network, send looped network by Primary port and secondary port and refresh (RING_DOWN_FLUSH_FDB) message; each transmission node refreshes the MAC address entries of self when receiving this RING_DOWN_FLUSH_FDB message, thereby realizes the looped network protection of Ethernet.
But in this method of prior art, if the RING_DOWN_FLUSH_FDB message is lost in transmission course, then each transmission node on the ethernet ring network can not refresh the MAC address entries of self, can cause serious consequences such as loop network link is obstructed, service disconnection equally.
Summary of the invention
The invention provides a kind of Ethernet ring protection method, transmission node and host node, so that avoid serious consequences such as the loop network link that causes owing to the RING_DOWN_FLUSH_FDB message dropping is obstructed, service disconnection.
A kind of Ethernet ring protection method, this method comprises:
After transmission node on A, the ethernet ring network detects ring network fault, send ring network fault LINK_DOWN message to host node;
After B, described host node receive the LINK_DOWN message, send the RING_DOWN_FLUSH_FDB message simultaneously, and start the 3rd timer and pick up counting from Primary port and secondary port;
C, the transmission node that detects ring network fault send back message using to described host node after receiving described RING_DOWN_FLUSH_FDB message;
If described the 3rd timer of D does not reach the 3rd default time threshold as yet, described host node all receives back message using from Primary port and secondary port, then stops the timing of described the 3rd timer; If described host node reaches the 3rd default time threshold at the timing duration of the 3rd timer, do not receive back message using as yet from master port or secondary port, then resend described RING_DOWN_FLUSH_FDB message according to back message using reception situation, and restart described the 3rd timer and pick up counting, go to step C.
A kind of host node, this host node comprises: fault message receiving element, back message using receiving element, update transmitting element, the 3rd timer and the 3rd judging unit;
Described fault message receiving element is used to receive the LINK_DOWN message;
Described back message using receiving element is used for receiving back message using from Primary port and secondary port;
Described update transmitting element is used for sending the RING_DOWN_FLUSH_FDB message simultaneously from Primary port and secondary port after described fault message receiving element receives the LINK_DOWN message, and sends initiate notification to described the 3rd timer; After receiving the back message using reception situation of described the 3rd judging unit transmission, resend described RING_DOWN_FLUSH_FDB message according to this back message using reception situation, and send initiate notification to described the 3rd timer;
Described the 3rd timer, after being used to receive initiate notification, startup picks up counting; Receive when stopping notice, stop timing;
Described the 3rd judging unit, be used to judge that the timing duration of described the 3rd timer is in the 3rd default time threshold, whether described back message using receiving element all receives back message using from Primary port and secondary port, if send the termination notice to described the 3rd timer; If not, then send back message using and receive situation to described update transmitting element;
Wherein, described back message using is that the transmission node that detects ring network fault sends to described host node after receiving described RING_DOWN_FLUSH_FDB message.
As can be seen from the above technical solutions; a kind of Ethernet ring protection method provided by the invention; in transmission node and the host node; host node is provided with timer; after host node sends the RING_DOWN_FLUSH_FDB message; if in the setting time limit, do not receive back message using; then resend the RING_DOWN_FLUSH_FDB message; wherein; back message using is to send to host node after the transmission node that detects ring network fault receives the RING_DOWN_FLUSH_FDB message; this method; transmission node and host node have prevented that the RING_DOWN_FLUSH_FDB message from losing in transmission course, avoided the RING_DOWN_FLUSH_FDB message dropping and the loop network link that causes is obstructed; serious consequences such as service disconnection.
Description of drawings
Fig. 1 is the structural representation of an Ethernet looped network in the prior art;
The method flow diagram of the transmission node side that Fig. 2 provides for the embodiment of the invention;
The method flow diagram of the host node side that Fig. 3 provides for the embodiment of the invention;
The structure chart that Fig. 4 provides for the embodiment of the invention;
The host node structure chart that Fig. 5 provides for the embodiment of the invention.
Embodiment
In order to make the purpose, technical solutions and advantages of the present invention clearer, describe the present invention below in conjunction with the drawings and specific embodiments.
Method provided by the invention mainly comprises: when detecting the transmission node transmission LINK_DOWN message of ring network fault, start first timer; If the timing duration at described first timer reaches default very first time thresholding, do not receive the RING_DOWN_FLUSH_FDB message as yet, then resend described LINK_DOWN message, and restart described first timer.
After host node on the ethernet ring network receives the LINK_DOWN message, send the RING_DOWN_FLUSH_FDB message simultaneously, and start the 3rd timer from Primary port and secondary port; If reach the 3rd default time threshold at the 3rd timer, do not receive back message using as yet from master port or secondary port, then resend the RING_DOWN_FLUSH_FDB message, and restart described the 3rd timer.
Lift a specific embodiment below the method for the transmission node side that detects ring network fault is described in detail, the method flow diagram of the transmission node side that Fig. 2 provides for the embodiment of the invention, as shown in Figure 2, this method can may further comprise the steps:
Step 201: the transmission node that detects ring network fault starts first timer when sending the LINK_DOWN message.
Step 202: the timing duration of judging first timer is in default very first time thresholding, and whether this transmission node receives the RING_DOWN_FLUSH_FDB message that host node sends, if, execution in step 203; If not, execution in step 204 then.
In this step, this very first time thresholding is set at an of short duration time usually, 0.5s for example, and its value can specifically be determined according to the message processing speed of host node and transmission node.
Step 203: when this transmission node that detects ring network fault receives the RING_DOWN_FLUSH_FDB message, stop the timing of first timer, refresh the MAC address entries of self, and send back message using to host node.Process ends.
In this step, this transmission node receives the RING_DOWN_FLUSH_FDB message, illustrates that then host node has successfully received the LINK-DOWN message, and carried out respective handling, therefore, this transmission node can stop the timing of first timer, finishes the transmission that repeats of LINK-DOWN message.
In addition, in this step, sending back message using is to be used to notify host node to receive the RING_DOWN_FLUSH_FDB message.In this flow process, also can not send this back message using.
Step 204: the timing duration of first timer reaches the very first time during thresholding, resends the LINK_DOWN message, and restarts first timer, goes to step 202.
In addition, if host node breaks down, then this transmission node is retransmitted how many times LINK_DOWN message and can not received the RING_DOWN_FLUSH_FDB message that host node sends, therefore, unrestrictedly retransmit the LINK_DOWN message for fear of the transmission node that this situation causes, in the step 201 of above-mentioned flow process, the transmission node that detects ring network fault can also start second timer when sending the LINK_DOWN message, do not receive the RING_DOWN_FLUSH_FDB message if the timing duration of this second timer reaches the second default time threshold fashion, then no longer retransmit the LINK_DOWN message.Wherein, this second time threshold is greater than very first time thresholding, and for example, can set second time threshold is 5s, does not also receive the RING_DOWN_FLUSH_FDB message in the 5s, then no longer retransmits the LINK_DOWN message.
The method flow diagram of the host node side that Fig. 3 provides for the embodiment of the invention, as shown in Figure 3, this method can may further comprise the steps:
Step 301: after host node received the LINK_DOWN message, open secondary port sent the RING_DOWN_FLUSH_FDB message simultaneously from Primary port and secondary port, and started the 3rd timer and pick up counting.
Step 302: judge whether this host node all receives back message using from Primary port and secondary port in the 3rd time threshold that the timing duration of the 3rd timer is being preset, if then execution in step 303, if not, then execution in step 304.
Receive the RING_DOWN_FLUSH_FDB message if detect the transmission node of ring network fault, then send back message using, indicate and self received the RING_DOWN_FLUSH_FDB message to host node.
The 3rd time threshold is an of short duration time value, 0.5s for example, and the 3rd time threshold can specifically be set according to the message processing speed of host node and transmission node.
Step 303: when this host node all receives back message using from Primary port and secondary port, stop the timing of the 3rd timer.Process ends.
In this step, this host node receives back message using, illustrates that then the transmission node that detects ring network fault has successfully received the RING_DOWN_FLUSH_FDB message, therefore, this host node can stop the timing of the 3rd timer, finishes the transmission that repeats of RING_DOWN_FLUSH_FDB message.
Step 304: when the timing duration of the 3rd timer reached default the 3rd time threshold, this host node resend the RING_DOWN_FLUSH_FDB message, and restarted described the 3rd timer and pick up counting, and went to step 302.
In this step,, then can resend the RING_DOWN_FLUSH_FDB message from Primary port and secondary port if any one does not receive back message using from master port or secondary port when host node reaches the 3rd time threshold; The port that also can only never receive back message using resends the RING_DOWN_FLUSH_FDB message, and the port that receives back message using no longer resends the RING_DOWN_FLUSH_FDB message.
In addition, if detecting the faults such as transmission node receiving port obstruction of ring network fault takes place, this transmission node does not receive the RING_DOWN_FLUSH_FDB message, can not send back message using, then host node can't receive back message using, therefore, unrestrictedly retransmit the RING_DOWN_FLUSH_FDB message for fear of the host node that this situation causes, in the step 301 of above-mentioned flow process, host node can also start the 4th timer when sending the RING_DOWN_FLUSH_FDB message, all do not receive back message using if the timing duration of the 4th timer reaches the 4th default time threshold fashion, then no longer retransmit the RING_DOWN_FLUSH_FDB message from Primary port and secondary port.Wherein, the 4th time threshold is greater than the 3rd time threshold.
In addition, each transmission node on this looped network might repeat to receive a plurality of FLUSH messages at short notice, at this moment, for fear of repeatedly refreshing MAC address entries at short notice, each transmission node can be when receiving the RING_DOWN_FLUSH_FDB message, refresh the MAC address entries of self, and start the 5th timer and pick up counting, when the timing duration of the 5th timer received the RING_DOWN_FLUSH_FDB message once more in the 5th default time threshold, each transmission node did not refresh the MAC address entries of self.When the timing duration of the 5th timer reaches described the 5th time threshold, stop timing, after the 5th timer stops timing, receive the RING_DOWN_FLUSH_FDB message once more, then can restart the 5th timer.
Fig. 2 and method flow shown in Figure 3 can select one independently to carry out arbitrarily, are respectively applied for and prevent losing of LINK_DOWN message or RING_DOWN_FLUSH_FDB message; The execution that also can cooperatively interact is used for preventing simultaneously losing of LINK_DOWN message and RING_DOWN_FLUSH_FDB message.
Below transmission node provided by the invention is described in detail, the structure chart that Fig. 4 provides for the embodiment of the invention, as shown in Figure 4, this transmission node comprises: fault packet sending unit 401, update receiving element 403 and back message using transmitting element 407.
Fault packet sending unit 401 is used to send the LINK_DOWN message.
Update receiving element 403 is used to receive the RING_DOWN_FLUSH_FDB message.
Back message using transmitting element 407 is used for when update receiving element 403 receives the RING_DOWN_FLUSH_FDB message, sends back message using.
This transmission node also comprises: first timer 402 and first judging unit 404.
Fault packet sending unit 401 sends initiate notification to first timer 402 when sending the LINK_DOWN message.
First timer 402 when being used to receive initiate notification, picks up counting.
First judging unit 404, be used to judge that the timing duration of first timer 402 is in default very first time thresholding, whether update receiving element 403 receives the RING_DOWN_FLUSH_FDB message, if not, then reach default very first time during thresholding, trigger fault packet sending unit 401 and resend the LINK_DOWN message at the timing duration of first timer 402.
This transmission node can also comprise: list item refresh unit 405.
First judging unit 404, do not reach default very first time thresholding as yet if can also be used for the timing duration of first timer 402, update receiving element 403 receives the RING_DOWN_FLUSH_FDB message, then sends to first timer 401 and stops notice.
First timer 402, also be used to receive stop notice after, stop timing.
List item refresh unit 405 is used for refreshing the MAC address entries of this transmission node when update receiving element 403 receives the RING_DOWN_FLUSH_FDB message.
In addition, this transmission node can also comprise: the 5th timer 406.
The 5th timer 406 is used for when update receiving element 403 receives the RING_DOWN_FLUSH_FDB message first, and startup picks up counting.
List item refresh unit 405 also is used for the 5th timer 406 in the 5th default time threshold, and update receiving element 403 receives the RING_DOWN_FLUSH_FDB message, does not then refresh MAC address entries.
In addition, if host node breaks down, then this transmission node is retransmitted how many times LINK_DOWN message and can not received the RING_DOWN_FLUSH_FDB message that host node sends, therefore, unrestrictedly retransmit the LINK_DOWN message for fear of the transmission node that this situation causes, this transmission node can also comprise: second timer 408 and second judging unit 409.
Second timer 408 is used for when fault generation back fault packet sending unit 401 sends the LINK_DOWN message first, and startup picks up counting.
Second judging unit 409, the timing duration that is used to judge second timer 408 is in the second default time threshold time, whether update receiving element 403 receives the RING_DOWN_FLUSH_FDB message, if not, forbids that then fault packet sending unit 401 sends the LINK_DOWN message.
Wherein, second time threshold is greater than very first time thresholding.
The host node structure chart that Fig. 5 provides for the embodiment of the invention, as shown in Figure 5, this host node comprises: fault message receiving element 501, back message using receiving element 502, update transmitting element 503, the 3rd timer 504 and the 3rd judging unit 505.
Fault message receiving element 501 is used to receive the LINK_DOWN message.
Back message using receiving element 502 is used for receiving back message using from Primary port and secondary port.
Update transmitting element 503 is used for sending the RING_DOWN_FLUSH_FDB message simultaneously from Primary port and secondary port after fault message receiving element 501 receives the LINK_DOWN message, and sends initiate notification to the 3rd timer 504; After receiving the back message using reception situation of the 3rd judging unit 505 transmissions, resend the RING_DOWN_FLUSH_FDB message, and send initiate notifications to the 3rd timer 504 according to this back message using reception situation.
Wherein, receive back message using reception situation after, can send described RING_DOWN_FLUSH_FDB message simultaneously from Primary port and secondary port, perhaps, the port that only never receives back message using resends described RING_DOWN_FLUSH_FDB message.
The 3rd timer 504, after being used to receive initiate notification, startup picks up counting.
The 3rd judging unit 505, be used to judge that the timing duration of the 3rd timer 504 is in the 3rd default time threshold, whether back message using receiving element 502 all receives back message using from Primary port and secondary port, if not, then sends back message using to update transmitting element 503 and receives situation.
The 3rd judging unit 505 can also be used for when the timing duration of the 3rd timer 504 reaches the 3rd time threshold, sends to the 3rd timer 504 and stops notice.
The 3rd timer also is used for stopping timing when receiving the termination notice.
In addition, if detecting the faults such as transmission node receiving port obstruction of ring network fault takes place, this transmission node does not receive the RING_DOWN_FLUSH_FDB message, can not send back message using, then host node can't receive back message using, therefore, unrestrictedly retransmit the RING_DOWN_FLUSH_FDB message for fear of the host node that this situation causes, host node can also comprise: the 4th timer 506, the 4th judging unit 507.
The 4th timer 506 is used for picking up counting when update transmitting element 503 sends the RING_DOWN_FLUSH_FDB message first.
The 4th judging unit 507, be used to judge that the timing duration of the 4th timer 506 is in the 4th default time threshold, whether back message using receiving element 502 receives back message using, if not, forbids that then update transmitting element 503 resends the RING_DOWN_FLUSH_FDB message.
Wherein, the 4th time threshold is greater than the 3rd time threshold.
By above description as can be seen, in embodiments of the present invention, host node on the ethernet ring network is provided with timer, the transmission node that detects ring network fault sends back message using to host node after receiving the RING_DOWN_FLUSH_FDB message, after host node sends the RING_DOWN_FLUSH_FDB message, if in the setting time limit, do not receive back message using, then resend the RING_DOWN_FLUSH_FDB message, thereby prevent that the RING_DOWN_FLUSH_FDB message from losing in transmission course, avoided the RING_DOWN_FLUSH_FDB message dropping and the loop network link that causes is obstructed, serious consequences such as service disconnection.
In addition, can also timer be set to the transmission node that detects ring network fault, after detecting the transmission node transmission LINK_DOWN message of ring network fault, if in the time limit of setting, do not receive the RING_DOWN_FLUSH_FDB message that host node sends, then resend the LINK_DOWN message, thereby prevent that LINK_DOWN from losing in transmission course, avoided LINK_DOWN to lose and serious consequence such as the loop network link that causes is obstructed, service disconnection.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being made, is equal to replacement, improvement etc., all should be included within the scope of protection of the invention.
Claims (8)
1. an Ethernet ring protection method is characterized in that, this method comprises:
After transmission node on A, the ethernet ring network detects ring network fault, send ring network fault LINK_DOWN message to host node;
After B, described host node receive the LINK_DOWN message, send the RING_DOWN_FLUSH_FDB message simultaneously, and start the 3rd timer and pick up counting from Primary port and secondary port;
C, the transmission node that detects ring network fault send back message using to described host node after receiving described RING_DOWN_FLUSH_FDB message;
If described the 3rd timer of D does not reach the 3rd default time threshold as yet, described host node all receives back message using from Primary port and secondary port, then stops the timing of described the 3rd timer; If described host node reaches the 3rd default time threshold at the timing duration of the 3rd timer, do not receive back message using as yet from master port or secondary port, then resend described RING_DOWN_FLUSH_FDB message according to back message using reception situation, and restart described the 3rd timer and pick up counting, go to step C.
2. method according to claim 1 is characterized in that, this method also comprises:
The transmission node that detects ring network fault is carried out following steps when sending ring network fault LINK_DOWN message:
A1, startup first timer pick up counting;
If B1 reaches default very first time thresholding at the timing duration of described first timer, do not receive looped network as yet and refresh the RING_DOWN_FLUSH_FDB message, then resend described LINK_DOWN message, and restart described first timer and pick up counting, go to step B1.
3. method according to claim 2, it is characterized in that, between described steps A 1 and step B1, also comprise: if do not reach default very first time thresholding as yet at the timing duration of described first timer, described transmission node receives the RING_DOWN_FLUSH_FDB message, then stop the timing of described first timer, and refresh the MAC address entries of self; Otherwise, continue execution in step B1.
4. method according to claim 2 is characterized in that, this method also comprises: described transmission node starts second timer and picks up counting when sending described LINK_DOWN message;
If the timing duration at described second timer reaches the second default time threshold, do not receive the RING_DOWN_FLUSH_FDB message as yet, then stop to resend described LINK_DOWN message, process ends;
Wherein, described second time threshold is greater than described very first time thresholding.
5. method according to claim 1 is characterized in that, described step B also comprises: when sending described RING_DOWN_FLUSH_FDB message, start the 4th timer and pick up counting;
If the timing duration at described the 4th timer reaches the 4th default time threshold, do not receive back message using as yet from master port or secondary port, then stop to resend described RING_DOWN_FLUSH_FDB message;
Wherein, described the 4th time threshold is greater than described the 3rd time threshold.
6. method according to claim 1, it is characterized in that, each transmission node on this looped network, when receiving the RING_DOWN_FLUSH_FDB message, refresh the MAC address entries of self, and start the 5th timer and pick up counting, when the timing duration of described the 5th timer receives the RING_DOWN_FLUSH_FDB message once more in the 5th default time threshold, do not refresh the MAC address entries of self.
7. a host node is characterized in that, this host node comprises: fault message receiving element, back message using receiving element, update transmitting element, the 3rd timer and the 3rd judging unit;
Described fault message receiving element is used to receive the LINK_DOWN message;
Described back message using receiving element is used for receiving back message using from Primary port and secondary port;
Described update transmitting element is used for sending the RING_DOWN_FLUSH_FDB message simultaneously from Primary port and secondary port after described fault message receiving element receives the LINK_DOWN message, and sends initiate notification to described the 3rd timer; After receiving the back message using reception situation of described the 3rd judging unit transmission, resend described RING_DOWN_FLUSH_FDB message according to this back message using reception situation, and send initiate notification to described the 3rd timer;
Described the 3rd timer, after being used to receive initiate notification, startup picks up counting; Receive when stopping notice, stop timing;
Described the 3rd judging unit, be used to judge that the timing duration of described the 3rd timer is in the 3rd default time threshold, whether described back message using receiving element all receives back message using from Primary port and secondary port, if send the termination notice to described the 3rd timer; If not, then send back message using and receive situation to described update transmitting element;
Wherein, described back message using is that the transmission node that detects ring network fault sends to described host node after receiving described RING_DOWN_FLUSH_FDB message.
8. host node according to claim 7 is characterized in that, described host node also comprises: the 4th timer, the 4th judging unit;
Described the 4th timer is used for picking up counting when described update transmitting element sends the RING_DOWN_FLUSH_FDB message first;
Described the 4th judging unit, be used to judge that the timing duration of described the 4th timer is in the 4th default time threshold, whether described back message using receiving element receives back message using, if not, forbids that then described update transmitting element resends the RING_DOWN_FLUSH_FDB message;
Described the 4th time threshold is greater than described the 3rd time threshold.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100579432A CN101227372B (en) | 2008-02-21 | 2008-02-21 | Ether ring net protection method, transmission node and host node |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100579432A CN101227372B (en) | 2008-02-21 | 2008-02-21 | Ether ring net protection method, transmission node and host node |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101227372A CN101227372A (en) | 2008-07-23 |
| CN101227372B true CN101227372B (en) | 2010-09-08 |
Family
ID=39859137
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008100579432A Active CN101227372B (en) | 2008-02-21 | 2008-02-21 | Ether ring net protection method, transmission node and host node |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101227372B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101964718B (en) * | 2009-07-23 | 2015-09-16 | 中兴通讯股份有限公司 | Ethernet dual homed link protection changing method and system |
| CN101989934B (en) * | 2009-08-06 | 2017-04-05 | 中兴通讯股份有限公司 | A kind of data ring network fault detect and the method and system of positioning |
| CN102111306B (en) * | 2009-12-23 | 2013-06-26 | 杭州华三通信技术有限公司 | Method, system and device for detecting virtual link faults based on fiber channel over Ethernet (FCoE) |
| CN101883038B (en) * | 2010-06-30 | 2015-08-12 | 中兴通讯股份有限公司 | Host node in the method for EAPS looped network protection switching and EAPS looped network |
| CN101977135B (en) * | 2010-09-27 | 2012-08-15 | 南京邮电大学 | Address updating method of subring without virtual channel |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1791049A (en) * | 2005-12-16 | 2006-06-21 | 杭州华为三康技术有限公司 | Looped network and its protecting method |
| CN101001192A (en) * | 2007-01-17 | 2007-07-18 | 华为技术有限公司 | Method, system and equipment for protecting ring network link |
| CN101079781A (en) * | 2007-02-01 | 2007-11-28 | 北京东土科技股份有限公司 | An implementation method for industrial Ethernet fast-speed redundancy |
-
2008
- 2008-02-21 CN CN2008100579432A patent/CN101227372B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1791049A (en) * | 2005-12-16 | 2006-06-21 | 杭州华为三康技术有限公司 | Looped network and its protecting method |
| CN101001192A (en) * | 2007-01-17 | 2007-07-18 | 华为技术有限公司 | Method, system and equipment for protecting ring network link |
| CN101079781A (en) * | 2007-02-01 | 2007-11-28 | 北京东土科技股份有限公司 | An implementation method for industrial Ethernet fast-speed redundancy |
Non-Patent Citations (1)
| Title |
|---|
| Allied Telesis.Inc.Configure EPSR(Ethernet Protection Switching Ring)ToProtect A Ring From Loops.2007,1-6,55-56. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101227372A (en) | 2008-07-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101001192B (en) | Method, system and equipment for protecting ring network link | |
| CN101227372B (en) | Ether ring net protection method, transmission node and host node | |
| CN101558609B (en) | Method, device and system for ring protection | |
| EP3823411B1 (en) | Control method for user equipment, and user equipment for mcg failure processing | |
| EP2352253A1 (en) | Method and apparatus for protecting link aggregation group of ethernet ring | |
| CN102075436A (en) | Ethernet, and data transmitting method and device thereof | |
| EP2117176A2 (en) | Method for implementing intersecting ring network with arbitrary topology, node and intersecting ring network | |
| CN101483570B (en) | Method, system and device for preventing looped network temporary loop circuit of relaying link | |
| CN101677267B (en) | Method for retransmitting protocol frames in transannular way and sharing nodes in multiple rings of Ethernet | |
| AU2009295116B2 (en) | Control method for protecting failure recovery of Ethernet ring and Ethernet ring nodes | |
| CN101640646B (en) | Protection reversion method and device of Ethernet ring network | |
| WO2009023996A1 (en) | Method for implementing network interconnect via link aggregation | |
| CN101141366A (en) | Method of preventing data loop in ring ethernet | |
| KR20100030672A (en) | A method for triggering status report of automatic repeat request | |
| CN102780593B (en) | Based on the method for BFD protocol detection link, device and network processing unit | |
| EP2477359A1 (en) | Method for ethernet loop network protection and transmission node | |
| US8264954B2 (en) | Method and device for operating a network and communication system comprising such device | |
| CN101478469B (en) | Method and system for RRPP loop link switching | |
| CN103139818A (en) | Method, system, area of effect (AOE), always on line (AOG) and terminal of maintaining long connection in acquisition of signal (AOS) | |
| CN101072154A (en) | Loop Ethernet switching method | |
| CN102055658B (en) | Method and equipment for realizing failure protection in rapid ring protection protocol single-ring networking | |
| CN101217445B (en) | A method of loop generation protection and Ethernet ring system | |
| CN101217443A (en) | Ethernet loop network protection method and transmission node | |
| CN102035695A (en) | Bidirectional forwarding detection method and device | |
| CN101425952B (en) | Method and apparatus for ensuring Ether ring network reliable operation |
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: Xinhua three Technology 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: Huasan Communication Technology Co., Ltd. |