WO2008064585A1 - Procédé, système et périphérique d'anneau de paquets résilients qui permettent d'éviter l'apparence d'une boucle après reprise après défaillance - Google Patents

Procédé, système et périphérique d'anneau de paquets résilients qui permettent d'éviter l'apparence d'une boucle après reprise après défaillance Download PDF

Info

Publication number
WO2008064585A1
WO2008064585A1 PCT/CN2007/070438 CN2007070438W WO2008064585A1 WO 2008064585 A1 WO2008064585 A1 WO 2008064585A1 CN 2007070438 W CN2007070438 W CN 2007070438W WO 2008064585 A1 WO2008064585 A1 WO 2008064585A1
Authority
WO
WIPO (PCT)
Prior art keywords
cross
ring
node
ring node
fault recovery
Prior art date
Application number
PCT/CN2007/070438
Other languages
English (en)
Chinese (zh)
Inventor
Yilong Zhang
Zhongkai Zhang
Zhifeng He
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008064585A1 publication Critical patent/WO2008064585A1/fr

Links

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

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a method, a system, and a Resilient Packet Ring (RPR) device for avoiding loops after failure recovery.
  • RPR Resilient Packet Ring
  • RPR technology has many advantages, gradually Into the field of metro transport networks, and become one of the hot spots.
  • RPR technology is a new network architecture designed to meet the requirements of packet metropolitan area networks.
  • RPR is a ring network composed of packet switching nodes. Adjacent nodes are connected by a pair of optical fibers.
  • the network topology is based on two A ring that transmits in the opposite direction.
  • the packet switching node on the ring network is further divided into a cross-ring node and a non-cross-ring node.
  • Non-cross-ring nodes when multiple RPR rings intersect, on the RPR ring, but there is no RPR device at the ring intersection.
  • a cross-ring node is an RPR device at the intersection of a ring when multiple RPR rings intersect. When the cross-ring node processes the cross-ring service forwarding, it is in the active master state.
  • RPR has many technical advantages such as effective bandwidth multiplexing, fast ring protection switching function, and automatic automatic discovery of topology, with the continuous development of science and technology, people have higher requirements for technology, and the current RPR communication There are still some shortcomings in the technology. These shortcomings will be explained below.
  • the RPR device carries Layer 2 Ethernet packets in the Ethernet Over RPR mode.
  • the RPR extension frame is forwarded on the RPR ring.
  • FIG. 1 is a schematic diagram of a prior art RPR ring network communication. Because the RPR carries Layer 2 Ethernet packets, if two cross-ring nodes are not controlled, loops will occur on the two cross-ring nodes, which is prone to broadcast storms.
  • STP Spanning Tree Protocol
  • RSTP Rapid Spanning Tree Protocol
  • the working modes of the non-cross-ring node 1 and the non-cross-ring node 2 are both wrap, and no packet will pass at the fault point, and no loop will appear. If the fault point 1 recovers, there is no fault point in the adjacent interval of the non-cross-ring node 1 and the non-cross-ring node 2, then the working modes of the non-cross-ring node 1 and the non-cross-ring node 2 will change to normal, and the recovered fault recovery The node can forward the data message.
  • the cross-ring node 1 and the cross-ring node 2 cannot immediately perceive this change without changing the state, they are still in the master state, the cross-ring node 1, the non-cross-ring node 1, the non-cross-ring node 2, and the cross-ring node 2
  • the non-cross-ring node 4 and the non-cross-ring node 3 form a loop, which easily causes broadcast packets to be cyclically transmitted in the loop, which causes broadcast storms and the like to occur.
  • non-cross-ring node 1 and non-cross-ring node 2 are failover nodes.
  • the embodiment of the present invention provides a method for avoiding a loop after a fault is recovered, and solves the problem that a loop is easily generated in the case where one of the two fault points located at both ends of the cross-ring node recovers.
  • the embodiment of the present invention further provides a system for avoiding loops after fault recovery, and solves the problem that loops are likely to occur in the case where one of two fault points located at both ends of the cross-ring node recovers.
  • the embodiment of the present invention further provides an RPR device that solves the problem that loops are likely to occur in the case where one of the two fault points located at both ends of the cross-ring node recovers.
  • a method for avoiding a loop after failure recovery characterized in that the method comprises the following steps:
  • the fault recovery node After the fault is recovered, the fault recovery node sets the delay time and sends a fault recovery notification message to the cross-ring node from the RPR ring. When the delay time expires, the fault recovery node sets the working state to normal.
  • the cross-ring node After receiving the fault recovery notification packet sent by the fault recovery node, the cross-ring node sets the working state of the cross-ring node according to the packet.
  • a system for avoiding loops after failure recovery characterized in that the system includes a fault recovery node and a cross-ring node;
  • Failback node used to set the delay time after failure recovery, and two from the RPR ring Sends a fault recovery notification message to the cross-ring node in one direction; when the delay time expires, sets its working state to normal;
  • the cross-ring node is configured to receive a fault recovery notification message sent by the fault recovery node, and set its working state according to the packet.
  • An RPR device the RPR device includes: a status module, a delay module, and a message sending module;
  • a status module configured to send a delay notification to the delay module, and send a trigger notification to the message sending module; set the working state to normal after receiving the arrival notification sent by the delay module;
  • a delay module configured to receive a delay notification sent by the status module, set a delay time, and send a notification to the status module when the delay time expires;
  • the packet sending module is configured to send a fault recovery notification message to the cross-ring node from the two directions of the RPR ring after receiving the trigger notification of the status module.
  • An RPR device includes: a message receiving module, and a status module; a message receiving module, configured to receive a fault recovery notification message sent by the fault recovery node, and then send a setting working state notification to the status module;
  • the status module is configured to receive a setting working state notification sent by the packet receiving module, and set a working state of the cross-ring node.
  • the fault recovery node sends a fault recovery notification message to the cross-ring node from the two RPR rings by setting the delay time. After the delay, the working state is set to normal; during the delay period, the cross-ring node Receives a fault recovery notification message sent by the fault recovery node, and sets the working status of the cross-ring node according to the status. Therefore, the problem that the loop is prone to occur when one of the two fault points located at both ends of the cross-ring node recovers is solved, thereby avoiding the occurrence of a broadcast storm or the like.
  • FIG. 1 is a schematic diagram of a prior art RPR ring network communication
  • Figure 2 is a schematic diagram of a fault point failure recovery loop
  • FIG. 3 is a structural diagram of a system in which a loop occurs after fault recovery is avoided in an RPR according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a method for avoiding a loop after a fault is recovered in an RPR according to an embodiment of the present invention
  • FIG. 5 is a detailed flowchart of a method for avoiding a loop after failure recovery in an RPR according to an embodiment of the present invention. Mode for carrying out the invention
  • FIG. 3 is a structural diagram of a system in which a loop occurs after failure recovery.
  • the system is mainly composed of: a fault recovery node 300 and a cross-ring node 310.
  • the fault recovery node that appears in the embodiment of the present invention is a non-cross-loop node.
  • the fault recovery node 300 sets a delay time after the fault is recovered, and then sends a fault recovery notification message to the cross-ring node from the two directions of the RPR ring; when the delay time expires, the working state is set to normal radicals
  • the cross-ring node 310 receives the fault recovery notification message sent by the fault recovery node, and sets its own working state according to the packet.
  • the failover node 300 and the cross-ring node 310 are not necessarily adjacent connections, and there may be other non-cross-ring nodes in between.
  • the fault recovery node 300 may include the following parts: a delay module 301, a text sending module 302, and a status module 303, where
  • the delay module 301 after receiving the delay notification sent by the status module, sets the delay time, and sends a notification to the status module 303 when the delay time expires.
  • the purpose of the set delay time is to ensure that the cross-ring node 310 can receive the fault recovery notification message sent by the fault recovery node 300 and process the corresponding state before the state of the fault recovery node is restored.
  • the length of the delay time can be set according to the number of hops that the fault recovery node is farthest from the two cross-ring nodes. For example, if the hop count is N, the delay time is N*10ms, where 10ms mainly considers the processing delay of each line and each node in the line, which is an empirical value. In addition, this value can also be based on the specific line condition. And different settings for each node device.
  • the message sending module 302 is configured to send a fault recovery notification message from two directions of the RPR ring after receiving the trigger notification of the status module 303, to notify the cross-ring node 310 that the fault has been recovered.
  • the fault recovery notification message can be extended based on the existing packet or a new packet type.
  • the status module 303 is configured to set the working status of the fault recovery node 300, send a delay notification to the delay module 301, and send a trigger notification to the message sending module 302; and receive the arrival notification sent by the delay module 301.
  • the fault recovery node 300 further includes:
  • the detecting module 304 is configured to: when the working state of the fault recovery node is to be changed to normal, the triggering state module 303 performs the operation of sending the delay notification and sending the trigger notification.
  • the state module 303 sends a delay notification to the delay module 301, and the delay module 301 starts to set the delay. Time, and the status module 303 sends a trigger notification to the message sending module 302.
  • the cross-ring node 310 can include the following parts: a message receiving module 311, and a state module 312, where
  • the message receiving module 311 is configured to receive the fault recovery notification message sent by the fault recovery node 300, and then send a setting working state notification to the status module 312.
  • the status module 312 receives the set working status notification sent by the message receiving module 311, and sets the working status of the cross-ring node 310.
  • cross-ring node 310 further includes a determining module 313:
  • the determining module 313 is configured to determine the working state of the cross-ring node 310, determine the working state of the cross-ring node connected thereto, and the priority of the two cross-ring nodes; and send the result of the judgment to the status module. 312.
  • the status module 312 sets the operational status of the cross-loop node 310 based on the result of the determination sent by the determination module 312.
  • the cross-ring node 310 If the cross-ring node 310 is not in the master state, the working state of the cross-ring node is not changed; if the cross-ring node 310 is in the master state, and there is only a cross-ring node of the connected master state on one RPR ring, and the cross-ring node If the priority is low, the cross-ring node is set to other states that are not in the master state;
  • cross-ring node 310 If the cross-ring node 310 is in the master state, and there is only a cross-ring node of the associated master state on one RPR ring, and the priority of the cross-ring node is high, the working state of the cross-ring node is not changed;
  • cross-ring node 310 If the cross-ring node 310 is in the master state, and there is no cross-ring node of the associated master state on the two RPR rings, the working state of the cross-ring node is not changed;
  • FIG. 4 is a flowchart of a method for avoiding a loop after failure recovery in an RPR.
  • the flow shown in FIG. 4 is adopted to avoid the loop problem that may be caused when one of the fault points is recovered, wherein the two The fault points are at each end of a cross-ring node.
  • the process mainly includes:
  • Step 401 After the fault is recovered, the fault recovery node sets the delay time, and then sends a fault recovery notification from the two directions of the RPR ring to the cross-ring node.
  • the purpose of setting the delay time is: ensuring that the cross-ring node 310 can receive the fault recovery notification message sent by the fault recovery node 300 and perform correspondingly before the state of the delay recovery node is restored. State processing.
  • the length of the delay time can be set according to the number of hops that the fault recovery node is farthest from the two cross-ring nodes. For example, if the hop count is N, the delay time is N*10ms, and 10ms here mainly considers the processing delay of the line and each node in the line, which is an empirical value.
  • the hop count of the distance cross-ring node may be determined according to the MAC address information of the cross-ring node and the non-cross-ring node on the RPR ring.
  • the delay time may also be manually configured in advance in each non-cross-ring node.
  • the fault recovery notification is used to notify the two cross-ring nodes that the fault is recovered. More preferably, during the delay, in order to avoid the lost fault recovery notification packet, the fault recovery notification packet may be sent multiple times. You can also ask the other party to respond.
  • the fault recovery notification message can be extended based on the existing packet or a new packet type.
  • Step 402 After receiving the fault recovery notification message sent by the fault recovery node, the cross-ring node sets the working state of the cross-ring node.
  • cross-ring node Because if the cross-ring node is not in the master state, it is not responsible for the forwarding of the cross-ring service, and thus no loop is formed, so the working state of the cross-ring node does not change.
  • this situation includes two situations: First, the cross-ring node is the master state, and the other cross-ring node is the other state of the non-master state, then there is no loop formation, so the cross-ring node is not changed. Working status. Second, the two cross-ring nodes are in the master state, but there are fault points between the two cross-ring nodes, that is, there are fault points on both ends of the cross-ring nodes on the two rings, that is, on the two rings. There are four fault points, then when there is a fault point recovery, no loop will be formed, so the working state of the cross-ring node will not be changed.
  • the working state of the cross-ring node is set to non- Other states of the master state.
  • Both cases have a faulty node between the two spanning nodes. Because both spanning nodes are in the master state, it is easy to form a loop as shown in Figure 2 on the ring, so The level sets one of the two cross-ring nodes to the master state, and the other sets the other states to the non-master state, and no loop is formed.
  • Step 403 After the delay time expires, the fault recovery node sets the working state to Normal
  • FIG. 5 is a detailed flowchart of a method for avoiding a loop after failure recovery. The process includes the following steps:
  • Step 501 After the fault is recovered, it is determined whether the working mode of the fault recovery node is to be set to normal. If yes, go to step 502; if no, end the process.
  • Step 502 The fault recovery node sets a delay time, and then sends a fault recovery notification message to the cross-ring node from two directions of the RPR ring to notify the cross-ring node that the fault has been recovered.
  • the purpose of the delay time is to ensure that the fault recovery notification message sent by the fault recovery node can be received by the cross-ring node in time and set the working state of the cross-ring node.
  • the fault recovery notification is used to notify the two cross-ring nodes that the fault is recovered. More preferably, during the delay, in order to avoid the lost fault recovery notification message, the fault recovery notification may be sent multiple times.
  • the fault recovery notification message can be extended on the existing message base or a new packet type.
  • Step 503 The cross-ring node receives the fault recovery notification message sent by the fault recovery node. This step is performed by the message receiving module 311 in the system of Fig. 3.
  • Step 504 Determine whether the cross-ring node is in the master state. If yes, go to step 505; if no, go to step 507.
  • Step 505 Determine whether the cross-ring node has a connected cross-ring node in the master state on only one RPR ring, and the cross-ring node has a low priority. If yes, go to step 506; if no, go to step 507.
  • step 507 if the cross-ring node does not have a connected cross-ring node in the master state on both RPR rings, step 507 is performed;
  • step 507 is performed;
  • cross-ring node has a cross-link point of the connected master state on only one RPR ring, and the cross-ring node has a low priority, if yes, go to step 506.
  • the device ID can be used to determine who exits the master state, and the sequence is performed according to regulations. .
  • Step 506 Set the working state of the cross-ring node to other states that are not in the master state.
  • Step 507 When the delay time expires, set the working state of the fault recovery node to normal.
  • the fault recovery node sends a fault recovery notification message to the cross-ring node from the two RPR rings by setting the delay time. After the delay, the working state is set to normal; during the delay, the cross-ring node receives the fault recovery.
  • the fault recovery notification message sent by the node, and the working state of the cross-ring node is set according to the status.

Abstract

La présente invention concerne un procédé, un système et un périphérique d'anneau de paquets résilients qui permettent d'éviter l'apparence d'une boucle après reprise après défaillance. Le procédé comprend les étapes suivantes : le nœud de reprise après défaillance configure un délai et transmet un message de notification de reprise après défaillance au nœud inter-anneaux par le biais de deux sens de RPR lorsque la défaillance est rattrapée; le nœud de reprise après défaillance définit son état de travail comme normal une fois le délai écoulé; le nœud inter-anneaux configure son état de travail basé sur la conditiond'état après réception du message de notification de reprise après défaillance envoyé par le nœud de reprise après défaillance dans les délais, spécifiquement parlant, le nœud inter-anneaux détermine s'il faut changer son propre état de travail selon son état et l'état d'autres nœuds inter-anneaux sur RPR. Le procédé, système et périphérique résolvent le problème de boucle lorsque l'une des deux positions de défaillance situées de deux côtés du nœud inter-anneaux est reprise par coopération entre le nœud de reprise après défaillance et le nœud inter-anneaux.
PCT/CN2007/070438 2006-11-27 2007-08-09 Procédé, système et périphérique d'anneau de paquets résilients qui permettent d'éviter l'apparence d'une boucle après reprise après défaillance WO2008064585A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610140355.6 2006-11-27
CNB2006101403556A CN100464528C (zh) 2006-11-27 2006-11-27 一种避免故障恢复后出现环路的方法和系统

Publications (1)

Publication Number Publication Date
WO2008064585A1 true WO2008064585A1 (fr) 2008-06-05

Family

ID=38076733

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/070438 WO2008064585A1 (fr) 2006-11-27 2007-08-09 Procédé, système et périphérique d'anneau de paquets résilients qui permettent d'éviter l'apparence d'une boucle après reprise après défaillance

Country Status (2)

Country Link
CN (1) CN100464528C (fr)
WO (1) WO2008064585A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217445B (zh) * 2008-01-21 2011-07-06 杭州华三通信技术有限公司 防止环路产生的方法和以太环网系统
CN101615989A (zh) * 2008-06-26 2009-12-30 中兴通讯股份有限公司 以太网双归组网及其mac地址表刷新方法
CN101997753B (zh) * 2009-08-20 2015-06-03 中兴通讯股份有限公司 一种环网双发机制的保护方法和系统
US10007586B2 (en) 2016-01-08 2018-06-26 Microsoft Technology Licensing, Llc Deferred server recovery in computing systems

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030012129A1 (en) * 2001-07-10 2003-01-16 Byoung-Joon Lee Protection system and method for resilient packet ring (RPR) interconnection
US20030117946A1 (en) * 2001-12-26 2003-06-26 Alcatel Method to protect RPR networks of extended topology, in particular RPR ring-to-ring and meshed backbone networks, and relating RPR network
US20060209859A1 (en) * 2005-03-17 2006-09-21 Fujitsu Limited Inter-ring connection method and device
CN1863126A (zh) * 2005-05-13 2006-11-15 中兴通讯股份有限公司 一种弹性分组环默认环的确定方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ITMI20012088A1 (it) * 2001-10-10 2003-04-10 Cit Alcatel Metodo per propagare l'informazione di guasto in una rete rpr e relativo tipo di pacchetto rpr
CN1266896C (zh) * 2002-08-29 2006-07-26 华为技术有限公司 弹性分组环网的快速倒换方法
CN1773952A (zh) * 2004-11-10 2006-05-17 华为技术有限公司 通信设备或网络故障时高优先级报文的带宽保证方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030012129A1 (en) * 2001-07-10 2003-01-16 Byoung-Joon Lee Protection system and method for resilient packet ring (RPR) interconnection
US20030117946A1 (en) * 2001-12-26 2003-06-26 Alcatel Method to protect RPR networks of extended topology, in particular RPR ring-to-ring and meshed backbone networks, and relating RPR network
US20060209859A1 (en) * 2005-03-17 2006-09-21 Fujitsu Limited Inter-ring connection method and device
CN1863126A (zh) * 2005-05-13 2006-11-15 中兴通讯股份有限公司 一种弹性分组环默认环的确定方法

Also Published As

Publication number Publication date
CN100464528C (zh) 2009-02-25
CN1968174A (zh) 2007-05-23

Similar Documents

Publication Publication Date Title
JP4899959B2 (ja) Ｖｐｎ装置
EP2245472B1 (fr) Système et procédé pour une récupération de réseau à partir de multiples échecs de liaison
EP2458797B1 (fr) Procédé, dispositif et système de mise à jour d'informations de topologie de réseau en anneau
CN100369436C (zh) 环网及其保护方法
WO2010045832A1 (fr) Procédé et appareil destinés à protéger un groupe d'agrégation de liaisons d'un réseau en anneau ethernet
JP4526423B2 (ja) リング間接続方法及び装置
CN100450036C (zh) 一种rrpp与局部stp组网故障恢复时防止环路的方法和装置
CN101345683B (zh) 以太网自动保护切换系统中的协议报文传输控制方法
WO2008046358A1 (fr) Procédé et dispositif destinés à réaliser une pénétration d'un statut de liaison de réseau point à multipoint
WO2008089701A1 (fr) Procédé, dispositif et système de protection d'anneau
WO2011120438A1 (fr) Procédé, système et dispositif pour la protection de messages en multidiffusion dans un réseau de communication
WO2012000234A1 (fr) Procédé, appareil et système de commutation rapide entre des liaisons
WO2009082923A1 (fr) Procédé de traitement de défaut de liaison et dispositif de transfert de données
JP2009524332A (ja) リング・ネットワークのｖｐｌｓ障害保護
WO2014026512A1 (fr) Procédé de traitement destiné à appliquer un protocole d'arbre couvrant rapide à une topologie de réseau en anneau unique
WO2008089633A1 (fr) Procédé et appareil pour protéger un anneau éthernet
JP2002330152A (ja) 障害時／増設時におけるスパニングツリー制御装置及び方法
JP2007174119A (ja) レイヤ２ネットワーク
WO2012171378A1 (fr) Procédé et routeur pour prévenir une interruption de flux provoquée par basculement de vpls vers l3
WO2011095101A1 (fr) Procédé, dispositif et système de protection 1 : n linéaire pour réseau de transport par paquets
WO2011076024A1 (fr) Système de réseau de commutation d'étiquettes multiprotocoles de transmission et procédé de protection des liaisons
WO2012079313A1 (fr) Procédé de protection de liaison et système associé
CN102238067B (zh) 一种快速环网保护协议环上的切换方法和装置
WO2010031295A1 (fr) Procédé de contrôle pour reprise après une panne ethernet
WO2012000243A1 (fr) Procédé de commutation de protection pour un réseau en anneau à commutation de protection automatique ethernet (eaps) et nœud maître dans un réseau en anneau eaps

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07800915

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07800915

Country of ref document: EP

Kind code of ref document: A1