CN102857398A - Method for transferring ring protection link (RPL) of sub ring during failure of multiple links of main ring - Google Patents
Method for transferring ring protection link (RPL) of sub ring during failure of multiple links of main ring Download PDFInfo
- Publication number
- CN102857398A CN102857398A CN2012103843857A CN201210384385A CN102857398A CN 102857398 A CN102857398 A CN 102857398A CN 2012103843857 A CN2012103843857 A CN 2012103843857A CN 201210384385 A CN201210384385 A CN 201210384385A CN 102857398 A CN102857398 A CN 102857398A
- Authority
- CN
- China
- Prior art keywords
- subring
- ring
- rpl
- message
- main ring
- 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.)
- Pending
Links
Images
Landscapes
- Small-Scale Networks (AREA)
Abstract
The invention discloses a method for transferring a ring protection link (RPL) of a sub ring during failure of multiple links of a main ring. When a middle node, which is connected with the sub ring, of the main ring detects that a plurality of ring interfaces on a main ring node are subjected to SF, and the RPL of the sub ring is not arranged on a sub ring interface of the main ring node, the middle node sends a plurality of SF-RT messages to inform an Owner of the rub ring to transfer the RPL and block the sub ring interface; the Owner of the sub ring receives the SF-RT messages sent by the middle node of the main ring, then opens the RPL and sends an NR-RB-RT message; other nodes of the sub ring receive the NR-RB-RT message and then update a functional data base (FDB); and when a failed link of the main ring receives the NR-RB-RT message, the sub ring interface connected with the main ring is recorded as an RPL proxy, and after the failure of the main ring is eliminated, the RPL proxy is canceled, so that normal communication between the main ring and the sub ring under the condition of failure of multiple types of the main ring is guaranteed.
Description
Technical field
The present invention relates to the network communications technology field, the method that subring RPL shifts when relating in particular to main ring multilink fault under a kind of G8032 standard.
Background technology
ITU G..8032 has defined APS (Automatic ProtectionSwitching, automatic protection switching) agreement and the automatic protection switching mechanism of Ethernet ring topology.G.8032 first version is fairly simple; model is switched in the protection that has only proposed single ring; behavior under switching of triggering in the situation of signal fault and the revertive mode only has been described, the situation of non-revertive mode and Manual Switch/Forced Switch has not been mentioned in front page.The revised edition of G..8032 is switched model in the protection that the basis of front page has increased multiple ring interconnection; and the situation of Manual Switch/Forced Switch had been described in detail; because consider the situation of multiple ring interconnection, the control procedure that ring protection is switched is also relatively complicated.
Looped network protection is automatically to protect ethernet ring network, shown in Figure 1A, in normal operation, is provided with the obstruction link that prevents into ring in looped network, i.e. RPL (Ring Protecting State, ring protection link).When other link occurs fault, such as Figure 1B and shown in Figure 2, this section ring protection link is opened, and data service is switched on the ring protection link to be transmitted, and realizes switching protection.And after fault recovery, the ring protection link gets clogged again, and data service switches back to original link.
However, G.8032 connectedness that can only the bonding link failure before the standard mesh, the reachability problem of communicating by letter when not solving the main ring multilink fault, and the situation of main ring multilink fault can appear in actual applications, in the situation of multilink segmentation, the problem that can not carry out proper communication between certain several point will inevitably appear.
Summary of the invention
The object of the invention is to overcome the defective of prior art, the method that subring RPL shifted when a kind of main ring multilink fault was provided is to guarantee when the main ring multilink breaks down the proper communication between main ring and subring.
For achieving the above object, the present invention proposes following technical scheme: the method that subring RPL shifts during a kind of main ring multilink fault comprises:
SF occurs in a plurality of ring interfaces that the intermediate node that links to each other with subring when main ring detects on the main link, and the RPL of subring is not when being configured on the subring interface of described main link, described intermediate node sends several SF-RT messages and carries out the RPL transfer with the Owner that notifies described subring, and blocks described subring interface;
Subring Owner opens RPL and sends the NR-RB-RT message after receiving the SF-RT message that is sent by described main ring intermediate node;
Other node of subring refreshes FDB after receiving described NR-RB-RT message.
Further, when the looped network normal operating conditions, be provided with the ID of main ring intermediate node at the Owner of subring, when subring Owner received the SF-RT message, the ID by described main ring intermediate node judged what whether described SF-RT message was sent by correct intermediate node.
The described SF-RT message of receiving as subring Owner is not when being sent by described main ring intermediate node, then dropping packets.
When other intermediate node is received described NR-RB-RT message, then record neighbours' fault, need before sending SF-RT message to check whether neighbours' fault value is zero.
SF occur in a plurality of ring interfaces that the intermediate node that links to each other with subring when main ring detects on the main link, and the RPL of all subrings only blocks the interface that SF occurs when being configured on the subring interface of described main link, do not make the relevant treatment that subring RPL shifts.
After the main ring faulty link was received described NR-RB-RT message, the described subring interface that will link to each other with main ring was recorded as the RPL agency.
When the main ring faulty link recover and main ring WTR overtime after, described intermediate node sends the NR-RB-RT message to subring RPL agency, be when being sent by correct RPL agency when subring Owner confirms this message, block the RPL link, and send NR-RB message informing cancellation RPL agency.Described intermediate node is after receiving the NR-RB message that subring Owner sends, and replacement neighbours fault value is zero.
Compared with prior art, the method that subring RPL shifts during disclosed main ring multilink fault, when having guaranteed in G8032 the main ring multilink fault, by shifting the method for subring RPL, and behind the main ring Failure elimination, again recover the function of subring RPL, guaranteed data are transmitted between main ring and subring connectedness and communicated by letter normally.
Description of drawings
Figure 1A is the schematic diagram when being provided with normal operation in the ethernet ring network of RPL;
When being one section link occurs fault of main ring among Figure 1A, Figure 1B starts the schematic diagram behind the RPL;
Flow chart when Fig. 2 is one section link occurs fault of main ring;
Fig. 3 A is the schematic diagram when on the main ring multilink fault occuring in the ethernet ring network of the present invention;
Fig. 3 B is the schematic diagram that occurs among Fig. 3 A after subring RPL shifts;
Fig. 4 be the present invention when subring RPL shifts, the flow chart of main ring intermediate contact state conversion;
Fig. 5 be the present invention when subring RPL shifts, the flow chart of subring Owner contact state conversion;
The state variation flow chart of subring when Fig. 6 is main ring trouble shooting of the present invention.
Embodiment
Below in conjunction with accompanying drawing of the present invention, the technical scheme of the embodiment of the invention is carried out clear, complete description.
In the ethernet ring network as shown in Figure 3A, comprise the main ring Major link that is comprised of node C, D, E, F and the subring Sub link that is comprised of node E, F, G, H, node E, F are the intermediate node that main ring Major and subring Sub share.Be provided with RPL on the subring Sub, namely the node G among Fig. 2 A and the link J between node H are RPL, and node G is the node (being the node that has of RPL) of the Owner of this section RPL.
The operating state of looped network protection group comprises normal operating conditions and Protection state, and when two ring interfaces of network topology link point all worked, protection group was in normal operating conditions; Under this state, looped network is in idle condition, and all nodes connect in the mode of ring, and the mode of the Owner node by blocking RPL is guaranteed can not become ring, is RPL such as the link J between node G among Fig. 3 A and node H.
In conjunction with Fig. 3 A, 3B and shown in Figure 4; when any one interface in the network topology ring breaks down; protection group enters the Protection state; at this moment; when network topology was main ring and subring, when any one interface in main ring and the subring broke down, malfunctioning node all can be given separately Owner node from SF (Signal Fail) message that ring interface sends link failure; notice Owner node link occurs fault this moment prepares to open standby link RPL.Single link failure on each ring can not affect communicating by letter of main ring and subring like this.
Fault has occured simultaneously on the link between the node D on the main ring and the link between node F and node E and node F, so that communicating by letter between main ring Major and subring Sub is when being interrupted, at this moment, method by subring RPL transfer of the present invention, the service link of subring is transferred on the subring RPL, to realize the proper communication between main ring and subring.
Specifically; in subring automatic protection switching APS message G.8032, in the Status field, whether shift with a new bit bit representation RPL, i.e. RT (RPL transferred); and this field only just works in the APS of subring message, specifically is expressed as:
During RT=1, expression RPL shifts;
During RT=0, expression RPL does not shift.
Message structure is as follows:
When the main ring multilink fault occurs when, if still expecting main ring this moment communicates by letter with subring, just can adopt subring RPL transfer techniques, when the looped network normal operating conditions, the node-id of two its main ring intermediate nodes (such as node E and node F) is set at the Owner of subring node G, shifts message SF-RT to prevent from receiving the link failure of pretending to be main ring to send.If the Owner of subring receives the SF-RT message of pretending to be then abandons.Simultaneously, enable the subring ID of RPL forwarding function intermediate node (such as node E and the node F) setting of main ring, such as the subring Sub among Fig. 3 A.
The intermediate node F that links to each other with subring when main ring detects two ring interfaces on the main link during treatment S F, at first whether there is the RPL of subring to be configured on certain subring interface of this link point with regard to checking, if the RPL of its all subrings is arranged on the subring interface of this main link, then do not do any processing; If the RPL of certain subring is configured on the interface of this main link, check the value of neighbours' fault (Neighbor Fail) of this moment.If the value of Neighbor Fail is 0, this intermediate node sends fast several (in the present embodiment being 3) link failures transfer messages SF-RT and carries out the RPL transfer with the owner that notifies this subring, blocks simultaneously this subring interface, such as Fig. 2 B.If the value of Neighbor Fail is 1, even this node two ring interface faults detecting main ring can not send the SF-RT message to subring yet so, be 0 could send the SF-RT message at Neighbor Fail only.
Whether each interconnected intermediate node can break down with two main ring interfaces that Neighbor Fail records the intermediate node of other interconnection.Being that the expression neighbours break down when Neighbor Fail is 1, is the expression Failure elimination when being zero, all can represent whether two main ring interfaces of the other side all break down with Neighbor Fail such as the node E among Fig. 2 A and F.
Show in conjunction with Fig. 5; after subring Owner receives that link failure shifts message SF-RT; at first the node-id by default intermediate node checks whether this message is sent by the main ring intermediate node; if; then the RPL with subring opens; send fast several (in the present embodiment being 3) and shift message NR-RB-RT without request ring protection line lockout, and state recording that will this moment is that RPL shifts (RPL Transferred).
When other node of subring is received the NR-RB-RT message of subring Owner transmission, carry out the action that refreshes FDB;
Other intermediate node (such as the node E among Fig. 3 A) is when receiving the NR-RB-RT message of subring, and the value of record neighbours' faults (Neighbor Fail) is 1.
The main ring faulty link is received the NR-RB-RT message of subring, this subring interface place subring link that then links to each other with main ring begins to serve as the function (if the link J ' between the F among the 3B and the H) of RPL, and the state recording of described intermediate node is RPL Proxy (RPL agency).
Show in conjunction with Fig. 6; when the main ring faulty link all recovers; wait for main ring WTR (Wait to Restore; the Wait-to-Restore timer) after overtime; subring RPL Proxy sends the NR-RB-RT message; after subring Owner receives message; contrast node-id information; confirm that this message is when being sent by correct RPL Proxy; block the RPL link, and send fast the message NR-RB without request ring protection line lockout, notice Proxy opens interface; cancellation RPL agent functionality, whole topology is recovered normal state.And be not when being sent by correct RPL Proxy when Owner detects NR-RB-RT, dropping packets then.
The interconnection intermediate node is received the NR-RB message that subring Owner sends, and after the validity of confirmation message, the value of record neighbours' faults (Neighbor Fail) is 0.
Technology contents of the present invention and technical characterictic have disclosed as above; yet those of ordinary skill in the art still may be based on teaching of the present invention and announcements and are done all replacement and modifications that does not deviate from spirit of the present invention; therefore; protection range of the present invention should be not limited to the content that embodiment discloses; and should comprise various do not deviate from replacement of the present invention and modifications, and contained by the present patent application claim.
Claims (9)
1. the method that subring RPL shifts during a main ring multilink fault is characterized in that:
SF occurs in a plurality of ring interfaces that the intermediate node that links to each other with subring when main ring detects on the main link, and the RPL of subring is not when being configured on the subring interface of described main link, described intermediate node sends several SF-RT messages and carries out the RPL transfer with the Owner that notifies described subring, and blocks described subring interface;
Subring Owner opens RPL and sends the NR-RB-RT message after receiving the SF-RT message that is sent by described main ring intermediate node;
Other node of subring refreshes FDB after receiving described NR-RB-RT message.
2. method according to claim 1, it is characterized in that: during the looped network normal operation, be provided with the ID of main ring intermediate node at the Owner of subring, when subring Owner received the SF-RT message, the ID by described main ring intermediate node judged what whether described SF-RT message was sent by correct intermediate node.
3. method according to claim 1 and 2 is characterized in that: the described SF-RT message of receiving as subring Owner is not when being sent by described main ring intermediate node, then dropping packets.
4. method according to claim 1, it is characterized in that: described intermediate node records the Interface status of other intermediate nodes by neighbours' fault value is set, and needs before sending the SF-RT message to check that neighbours' fault value just sends the SF-RT message when being zero.
5. method according to claim 4 is characterized in that: when looped network worked, the initial value that the intermediate node neighbours fault that main ring links to each other with subring is set all was zero; When other intermediate node was received described NR-RB-RT message, then recording neighbours' fault value was 1.
6. method according to claim 1, it is characterized in that: SF occurs in a plurality of ring interfaces that the intermediate node that links to each other with subring when main ring detects on the main link, and when the RPL of all subrings is configured on the subring interface of described main link, then do not do the processing that subring RPL shifts.
7. method according to claim 1 is characterized in that: after the main ring faulty link was received described NR-RB-RT message, the described subring interface that will link to each other with main ring was recorded as the RPL agency.
8. method according to claim 7, it is characterized in that: when the main ring faulty link recover and main ring WTR overtime after, described intermediate node sends the NR-RB-RT message to subring RPL agency, when being sent by correct RPL agency when subring Owner confirms this message, block the RPL link, and send NR-RB message informing cancellation RPL agency.
9. method according to claim 8 is characterized in that: described intermediate node is after receiving the NR-RB message that subring Owner sends, and resetting neighbours' fault value is zero.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2012103843857A CN102857398A (en) | 2012-10-12 | 2012-10-12 | Method for transferring ring protection link (RPL) of sub ring during failure of multiple links of main ring |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2012103843857A CN102857398A (en) | 2012-10-12 | 2012-10-12 | Method for transferring ring protection link (RPL) of sub ring during failure of multiple links of main ring |
Publications (1)
Publication Number | Publication Date |
---|---|
CN102857398A true CN102857398A (en) | 2013-01-02 |
Family
ID=47403604
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2012103843857A Pending CN102857398A (en) | 2012-10-12 | 2012-10-12 | Method for transferring ring protection link (RPL) of sub ring during failure of multiple links of main ring |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN102857398A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115714698A (en) * | 2022-09-26 | 2023-02-24 | 重庆长安汽车股份有限公司 | Ring network communication method and device of vehicle-mounted Ethernet, vehicle and storage medium |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101702684A (en) * | 2009-11-06 | 2010-05-05 | 中兴通讯股份有限公司 | Method for realizing to refresh Ethernet ring network forwarding database and device |
CN101741673A (en) * | 2008-11-25 | 2010-06-16 | 中兴通讯股份有限公司 | Address refreshing method of Ethernet ring |
CN102025584A (en) * | 2010-11-30 | 2011-04-20 | 迈普通信技术股份有限公司 | G.8032-based ring network protecting method and system |
CN102055661A (en) * | 2009-11-06 | 2011-05-11 | 中兴通讯股份有限公司 | Ethernet multi-ring network protection method under multipoint fault condition and interconnected nodes |
-
2012
- 2012-10-12 CN CN2012103843857A patent/CN102857398A/en active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101741673A (en) * | 2008-11-25 | 2010-06-16 | 中兴通讯股份有限公司 | Address refreshing method of Ethernet ring |
CN101702684A (en) * | 2009-11-06 | 2010-05-05 | 中兴通讯股份有限公司 | Method for realizing to refresh Ethernet ring network forwarding database and device |
CN102055661A (en) * | 2009-11-06 | 2011-05-11 | 中兴通讯股份有限公司 | Ethernet multi-ring network protection method under multipoint fault condition and interconnected nodes |
CN102025584A (en) * | 2010-11-30 | 2011-04-20 | 迈普通信技术股份有限公司 | G.8032-based ring network protecting method and system |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115714698A (en) * | 2022-09-26 | 2023-02-24 | 重庆长安汽车股份有限公司 | Ring network communication method and device of vehicle-mounted Ethernet, vehicle and storage medium |
CN115714698B (en) * | 2022-09-26 | 2024-04-16 | 重庆长安汽车股份有限公司 | Looped network communication method and device of vehicle-mounted Ethernet, vehicle and storage medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN101127674B (en) | Initialization method for transmission nodes of Ethernet loop network system | |
CN101001192B (en) | Method, system and equipment for protecting ring network link | |
CN100486204C (en) | Multi-loop contact Ethernet loop network loop protection switchover method | |
CN101212366B (en) | Failure detection method, system, and main node in Ethernet loop network | |
CN101479992B (en) | A method and device to realize punch-through of point-to-multipoint network link status | |
JP4790591B2 (en) | Ring node device | |
CN101127653B (en) | Ethernet loop device with backup and implementation method for master device backup | |
CN101483570B (en) | Method, system and device for preventing looped network temporary loop circuit of relaying link | |
EP2194676A1 (en) | Ethernet ring system, its main node and intialization method | |
CN101958831B (en) | Ethernet ring network failure recovery method, Ethernet ring network and switching equipment | |
CN101640622B (en) | Ethernet ring net protection method and transit node | |
CN101686158B (en) | Control method for Ethernet loop guard fault recovery and Ethernet loop node | |
CN100454880C (en) | Method and system of realizing rig network protection | |
CN100479411C (en) | Processing method for node link switching of the distributed system and its device | |
CN101227371B (en) | Method and apparatus of backup switch among same level switch equipments | |
CN101141381B (en) | Network node and method of reducing medium access control address learning in looped network thereof | |
CN101340346A (en) | Ring control method and apparatus of Ethernet looped network system | |
CN101072154A (en) | Loop Ethernet switching method | |
CN101686167A (en) | Method for controlling recovery of faults of Ethernet | |
CN101980478B (en) | Method and device for detecting and processing equipment failures and network equipment | |
CN101534234B (en) | Interworking Ethernet ring network protection method and system | |
RU2304849C2 (en) | Method affording transmission of information about communication line condition in network | |
CN110635940B (en) | Main/standby switching method of EAPS Ethernet ring network | |
CN102025584A (en) | G.8032-based ring network protecting method and system | |
KR100968939B1 (en) | Method and apparatus for protection switching of ring network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C05 | Deemed withdrawal (patent law before 1993) | ||
WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20130102 |