WO2008028392A1 - Procédé d'évitement de boucles après la reprise sur erreur de rpr - Google Patents

Procédé d'évitement de boucles après la reprise sur erreur de rpr Download PDF

Info

Publication number
WO2008028392A1
WO2008028392A1 PCT/CN2007/002082 CN2007002082W WO2008028392A1 WO 2008028392 A1 WO2008028392 A1 WO 2008028392A1 CN 2007002082 W CN2007002082 W CN 2007002082W WO 2008028392 A1 WO2008028392 A1 WO 2008028392A1
Authority
WO
WIPO (PCT)
Prior art keywords
ring
bridge
packet data
fault
cross
Prior art date
Application number
PCT/CN2007/002082
Other languages
English (en)
Chinese (zh)
Inventor
Eloong Zhang
Yanchun Liu
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 WO2008028392A1 publication Critical patent/WO2008028392A1/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
    • 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

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a loop avoidance method after a fault recovery of an RPR (Resilient Packet Ring) bridge.
  • RPR Resilient Packet Ring
  • RPR technology is a new network architecture and technology designed to meet the requirements of packet metropolitan area networks. It 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 rings transmitted in opposite directions. RPR has the following technical features: 1. Effective reuse of transmission bandwidth; 2. Fast loop bridge protection switching function; 3. Automatic discovery of topology.
  • a ring network composed of RPR technology is called an RPR ring network and can be simply referred to as an RPR ring.
  • a packet switching device on a ring network is called an RPR device.
  • the RPR device uses the 48-bit MAC address used in the Ethernet as the address identifier to uniquely identify the RPR device and carries Layer 2 Ethernet packets through the Ethernet Over RPR, the RPR ring can also be called the RPR bridge ring. Or bridge mode RPR ring.
  • the device on the RPR bridge ring can also be called an RPR bridge device.
  • the MAC address on the RPR bridge device can also be called the RPR MAC address. As shown in Figure 1, the structure of the two RPR bridge rings intersects the two RPR bridge devices.
  • RPR bridge rings there are two RPR bridge rings, which are RPR bridge ring 1 and RPR bridge ring 2, respectively.
  • the cross-ring bridge device is an RPR bridge device that is connected to two RPR bridge rings at the same time and is responsible for forwarding data packets between two RPR bridge rings.
  • the RPR cross-ring bridge device is simply referred to as a cross-loop bridge device in the following description.
  • the RPR bridge ring On the RPR bridge ring, the RPR bridge ring carries Layer 2 Ethernet packets, and the packets between the RPR bridges are forwarded through the Address Resolution Protocol (MAC). Therefore, The RPR cross-loop bridge device where the two RPR bridge rings intersect generates a loop, that is, a loop occurs between the RPR cross-bridge device 1 and the RPR cross-bridge device 2 as shown in FIG. 1, and a broadcast storm occurs.
  • MAC Address Resolution Protocol
  • the current method is through the Spanning Tree Protocol (STP), or Rapid Spanning Tree Protocol (RSTP) protocol performs link reduction, generates a minimum spanning tree without loops, and then forwards packets on Layer 2 Ethernet according to the minimum spanning tree to prevent Layer 2 network communication from forming. Loop.
  • STP Spanning Tree Protocol
  • RSTP Rapid Spanning Tree Protocol
  • STP or RSTP re-calculates the minimum spanning tree and obtains a new forwarding tree to ensure that the fault can occur after the fault occurs.
  • this method can solve the problems that may occur between the cross-ring bridge devices, this method is slow because the STP and RSTP convergence speed is slow. Even if the RSTP can only reach the convergence speed level of the second-level, the network communication time is prolonged. Increase the load of network communication.
  • a RPR bridge redundancy protection method is also available. The method is to enter a new protocol type. With the interaction of the protocol and the triggering of the single-loop RPR protection switching, the protection switching capability of 100 ms can be achieved.
  • an object of embodiments of the present invention is to provide an RPR bridge.
  • the loop avoidance method after the fault recovery the method solves the broadcast loop problem that may occur when one fault point recovers after two fault points occur on one RPR bridge loop in the application scenario of the RPR intersecting loop.
  • an embodiment of the present invention provides a loop avoiding method after RPR bridge fault recovery, and the method includes the following steps:
  • Each RPR cross-ring bridge device in the RPR bridge ring receives the notification message sent by the fault recovery node, detects the working status of the respective RPR cross-ring bridge device, and only maintains one of the primary RPR cross-bridge devices. Main state.
  • the step A further includes:
  • the normal maximum transmission unit value of the failure recovery node is recorded.
  • the method further includes:
  • the network topology convergence is initiated, and after the topology is converged, the maximum transmission unit value of the fault recovery node is restored to the recorded normal maximum transmission unit value.
  • the step A further includes:
  • the operational state of the fault recovery node is set to a normal state.
  • the predetermined value of the maximum transmission unit value is a value that can ensure that the protocol message passes, and the data message cannot pass, and the value is between 30 and 81.
  • the step B further includes:
  • step A it is known that the fault of the fault point in the RPR bridge loop has returned to normal: when the fault point is the RPR bridge device in the RPR bridge ring, the fault point itself is known. Its The fault has returned to normal;
  • the fault recovery node in the RPR bridge ring is an RPR bridge device or an RPR span bridge device.
  • the notification message is a type of message that is extended on the basis of the existing message, or is a newly defined message.
  • step B when a cross-ring bridge device detects that its working state is a standby state, the received notification message is not processed.
  • step B when a cross-ring bridge device detects that its working state is the active state, but does not have other cross-ring bridge devices connected to it in the active state; or when a cross-bridge device If the working status of the working state is detected as the active state, but the priority is higher than the priority of other cross-ring bridge devices connected to the active state, the received notification message will not be processed. .
  • step B when a cross-ring bridge device detects that its working state is in the active state, and the other cross-ring bridge devices connected to the active state have a higher priority cross-ring bridge When the device is in use, the low-priority cross-ring bridge device exits the active state.
  • the fault recovery node sends a notification message to the cross-ring bridge device.
  • the cross-loop bridge device works according to its working status/priority and other cross-ring bridge devices. Status/Priority, for subsequent actions (such as maintaining the active state or exiting the active state). In this way, after the fault at the fault point is restored, only one cross-ring bridge device is in the active state, ensuring correct forwarding of the cross-ring service, and solving the loop problem occurring in the information transmission after the fault point is recovered, and there is no service in the ring. Impact, while having no effect on the convergence of the single-ring protocol.
  • FIG. 1 is a schematic diagram of a topology structure of an RPR bridge ring network in the prior art
  • 2 is a schematic diagram of communication in the case where two faults occur simultaneously on one RPR bridge ring in the RPR bridge ring network in the prior art
  • 3 is a schematic diagram of a broadcast loop generated when one fault occurs simultaneously on one RPR bridge ring in the RPR bridge ring network in the prior art
  • FIG. 4 is a flowchart of a method for avoiding a broadcast loop by a fault recovery node when a non-cross-bridge device fails to recover in the RPR bridge according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a method for avoiding a broadcast loop of a cross-loop bridge device when a non-cross-bridge device fails to recover in the RPR bridge according to an embodiment of the present invention.
  • the embodiment of the invention provides a loop avoidance method after the RPR bridge is faulty.
  • the method solves the problem that in the application scenario of the RPR intersecting ring, when two fault points occur simultaneously on one RPR bridge ring, at one fault point A broadcast loop problem that may occur when recovering.
  • the loop avoidance method after the fault recovery of the RPR bridge is to control the passage of data packets on the RPR ring through the cooperation of the fault recovery node and the cross-ring bridge device to avoid loop phenomenon on the RPR ring.
  • an RPR bridge ring network in which there are two intersecting RPR bridge rings, and the two RPR bridge rings include RPR bridge device 1, RPR bridge device 2, and RPR bridge device 3.
  • the working modes of the RPR bridge device 1 and the RPR bridge device 2 are in the protection mode, that is, the wrap state, and no packet will pass at the fault point 1, and there will be no The emergence of a broadcast loop.
  • the working status of the RPR cross-bridge device 1 and the RPR2 cross-ring bridge device are both in the master state and the cross-ring in the active state.
  • the bridge device can be responsible for forwarding the cross-ring service, that is, the data service can be forwarded in different RPR bridge rings, so that any node in the two RPR bridge rings can access each other.
  • FIG. 4 is a main flowchart of processing a fault recovery node according to an embodiment of the present invention.
  • the fault recovery node referred to herein refers to a device adjacent to the fault point, and for the fault point 1 , the fault recovery node Refers to RPR bridge device 1 or RPR bridge device 2 adjacent to fault point 1.
  • the recovery point 1 in Figure 3 is taken as an example.
  • the process flow includes the following steps:
  • Step 40 After learning that the fault of the fault point 1 in the RPR bridge ring has returned to normal, triggering a topology convergence process; in the RPR bridge ring, the fault point may be an RPR bridge device or a chain connecting the RPR bridge devices. road.
  • the fault point 1 is a link
  • the fault recovery node RPR bridge device 1 or RPR bridge device 2
  • the point of failure is an RPR bridge device in the RPR bridge ring, in which case the point of failure itself can be informed whether its fault has returned to normal.
  • Step 41 After the topology changes, determine the fault recovery node (RPR bridge device 1 or RPR bridge device 2) or the fault point (when the fault point is a device in the RPR bridge ring) before completing topology convergence. Whether the working status has changed;
  • Step 42 The fault recovery node (the RPR bridge device 1 or the RPR bridge device 2) detects whether its own working state changes from a protected state (wrap state) to a normal state. If the detection result is yes, the fault is recovered. When the node has changed to the normal state, go to step 43. If the detection result is no, that is, the fault recovery node is still in the wrap state, wait for a predetermined time (such as 1 ⁇ 3 seconds). Go to step 41 to continue the test;
  • step 41 if the fault point is an RPR bridge device, it is detected whether the working state of the fault point changes from the protection state to the normal state. Similarly, when the detection result is yes, go to step 43; when the detection result is no Wait for a predetermined time, go to step 41 to continue the test;
  • Step 43 The fault recovery node sends a notification message on the two RPR bridge rings, and notifies the RPR cross-bridge device 1 and the RPR cross-bridge device 2 that the fault at the fault point 1 has returned to normal;
  • the notification message sent by the fault recovery node may be a packet that is extended based on an existing packet, or may be a packet that uses a new packet type;
  • Step 44 Record the current normal value of the Maximum Transmission Unit (MTU) of the fault recovery node; and set the MTU value of the fault recovery node to a predetermined value.
  • the predetermined value is in the range of 30-81 words. The value between the sections;
  • Step 46 After the topology convergence, restore the MTU value of the fault recovery node to the normal value of the MTU recorded in step 44; further, the working state of the fault recovery node may be set to a normal state;
  • Step 47 The program ends.
  • the fault recovery node is RPR cross-loop bridge device 1 or RPR cross-loop bridge device 2, when the fault point 2 is restored, the fault recovery node can easily perceive that the fault point 2 has returned to normal. According to the change of its own working state, to avoid the occurrence of a loop, the process of changing its own state will be described with reference to FIG.
  • a cross-ring bridge device When a cross-ring bridge device receives the notification message indicating that the fault point 1 has been recovered in step 43 of FIG. 4 described above, or when it detects that the fault of the adjacent fault point 2 has been recovered, then the cross-ring The bridge device should perform the corresponding data processing process according to its own working state and priority.
  • the main purpose is to keep only one cross-ring bridge device in all cross-ring bridge devices in the active state and to forward data packets across the ring. Other cross-ring bridge devices exit the active state and become standby.
  • the data packets are forwarded across the ring to avoid the loop in Figure 3.
  • the priority described herein refers to an attribute value set for each cross-bridge device according to a certain rule in advance.
  • the priority setting of the cross-bridge device can be Configure it yourself as needed, for example, the device ID number, IP address, MAC address, custom identifier, or custom serial number of the cross-ring bridge device.
  • Step 51 The cross-ring bridge device (for example, the cross-ring bridge device 1 or the cross-ring bridge device 2) receives the notification message sent from the fault recovery node, or detects that the adjacent fault point has been restored;
  • Step 52 The cross-ring bridge device determines whether its own working state is in the active state at this time. If it is in the standby state, the received notification message is not processed, and the process proceeds to step 56; if it is the primary use State, go to step 53;
  • Step 53 Determine whether the cross-ring bridge device has other cross-ring bridge devices connected to the RPR bridge ring in the active state. If not, the cross-ring bridge device remains in the active state, and receives the notification. " ⁇ " is not processed, and proceeds to step 56; if there are other cross-bridge devices in its active state connected to it, then go to step 54;
  • Step 54 Determine whether the priority of the cross-ring bridge device is lower than the priority of other cross-ring bridge devices connected to the primary state. If the judgment result is no, the cross-ring bridge device remains in the active state. And the received notification message is not processed, and proceeds to step 56, if the determination result is yes, then proceeds to step 55;
  • Step 55 The cross-ring bridge device exits the active state and is no longer responsible for forwarding the cross-ring service.
  • Step 56 The process ends.
  • the embodiment of the present invention sends a notification message to the cross-ring bridge device through the fault recovery node.
  • the cross-ring bridge device 1 and the cross-ring bridge device 2 both according to their own Work status/priority and other working status/priority of the cross-bridge device to perform subsequent actions (such as maintaining the active state or exiting the active state).
  • subsequent actions such as maintaining the active state or exiting the active state.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne un procédé d'évitement de boucles après la reprise sur erreurs de RPR, qui consiste en ce qui suit : régler une valeur d'unité de transmission maximale d'un noeud de reprise sur erreur en tant que valeur prédéterminée après l'acquisition de la reprise sur erreur d'un noeud d'erreur dans un RPR; transmettre le message de notification à un dispositif fonctionnant à travers l'anneau dans le RPR qui notifie que la reprise a été effectuée dans le noeud d'erreur; recevoir par chaque dispositif fonctionnant à travers l'anneau dans le RPR le message de notification transmis par le dispositif du noeud de reprise sur erreur, dans le RPR; détecter l'état de fonctionnement de chaque dispositif fonctionnant à travers l'anneau dans le RPR; et maintenir en tant que maître uniquement un seul des dispositifs fonctionnant à travers l'anneau dans le RPR.
PCT/CN2007/002082 2006-09-01 2007-07-06 Procédé d'évitement de boucles après la reprise sur erreur de rpr WO2008028392A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2006100374378A CN101136830B (zh) 2006-09-01 2006-09-01 Rpr桥故障恢复后的环路避免方法
CN200610037437.8 2006-09-01

Publications (1)

Publication Number Publication Date
WO2008028392A1 true WO2008028392A1 (fr) 2008-03-13

Family

ID=39156829

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/002082 WO2008028392A1 (fr) 2006-09-01 2007-07-06 Procédé d'évitement de boucles après la reprise sur erreur de rpr

Country Status (2)

Country Link
CN (1) CN101136830B (fr)
WO (1) WO2008028392A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107547331A (zh) * 2017-09-25 2018-01-05 新华三技术有限公司 Rpr相交环中rpr节点的转发状态控制方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050002392A1 (en) * 2000-06-30 2005-01-06 Nader Vijeh Per-flow rate control for an asynchronous metro packet transport ring
JP2005130049A (ja) * 2003-10-21 2005-05-19 Fujitsu Ltd ノード
CN1941730A (zh) * 2005-09-26 2007-04-04 华为技术有限公司 实现rpr桥冗余保护的方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE68921373T2 (de) * 1988-06-27 1995-10-19 Digital Equipment Corp Transparente Lastteilung für parallele Netzwerke.
CN1266896C (zh) * 2002-08-29 2006-07-26 华为技术有限公司 弹性分组环网的快速倒换方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050002392A1 (en) * 2000-06-30 2005-01-06 Nader Vijeh Per-flow rate control for an asynchronous metro packet transport ring
JP2005130049A (ja) * 2003-10-21 2005-05-19 Fujitsu Ltd ノード
CN1941730A (zh) * 2005-09-26 2007-04-04 华为技术有限公司 实现rpr桥冗余保护的方法

Also Published As

Publication number Publication date
CN101136830A (zh) 2008-03-05
CN101136830B (zh) 2011-01-12

Similar Documents

Publication Publication Date Title
EP2194676B1 (fr) Système de réseau en anneau ethernet, noeud principal de celui-ci et procédé d'initialisation de ce noeud
JP5508289B2 (ja) 多重リンク障害からのネットワーク回復システム及び方法
JP4454516B2 (ja) 障害検出装置
US7440397B2 (en) Protection that automatic and speedily restore of Ethernet ring network
CN100409634C (zh) 快速环网保护方法及系统
US7940645B2 (en) Protection switching method based on change in link status in ethernet link aggregation sublayer
CN103843286B (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
EP2204947A1 (fr) Procédé et dispositif de n ud de détection de défaillance et de convergence ethernet
WO2008089701A1 (fr) Procédé, dispositif et système de protection d'anneau
WO2008046358A1 (fr) Procédé et dispositif destinés à réaliser une pénétration d'un statut de liaison de réseau point à multipoint
JP2005260927A (ja) イーサネット自動保護スイッチング
WO2012065435A1 (fr) Procédé et appareil pour rediriger des signaux vers une voie initiale dans un réseau de transmission
WO2011095101A1 (fr) Procédé, dispositif et système de protection 1 : n linéaire pour réseau de transport par paquets
WO2010031296A1 (fr) Procédé de contrôle pour une protection de reprise après une panne d’anneau ethernet et de nœuds d’anneau ethernet
WO2009046591A1 (fr) Procédé de traitement de traitement de panne de port esclave de nœud maître dans un système de réseau ethernet en anneau
CN101340346A (zh) 一种以太环网系统中环控制的方法及装置
WO2010031295A1 (fr) Procédé de contrôle pour reprise après une panne ethernet
WO2012171380A1 (fr) Procédé et dispositif de traitement de défaillance d'extrémité distante pour l'ethernet
WO2011017900A1 (fr) Procédé de protection de segment et système pour tunnel ethernet
CN102238067B (zh) 一种快速环网保护协议环上的切换方法和装置
CN110635940B (zh) 一种eaps以太环网的主备倒换方法
US8811157B2 (en) Protection switching method and system for ethernet dual-homed link
CN101883038A (zh) Eaps环网保护倒换的方法及eaps环网中的主节点
JP5012485B2 (ja) 冗長方法及びスイッチ装置

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: 07800680

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: 07800680

Country of ref document: EP

Kind code of ref document: A1