[go: up one dir, main page]

WO2008089614A1 - Procédé, système et dispositif de protection d'une liaison en anneau - Google Patents

Procédé, système et dispositif de protection d'une liaison en anneau Download PDF

Info

Publication number
WO2008089614A1
WO2008089614A1 PCT/CN2007/002398 CN2007002398W WO2008089614A1 WO 2008089614 A1 WO2008089614 A1 WO 2008089614A1 CN 2007002398 W CN2007002398 W CN 2007002398W WO 2008089614 A1 WO2008089614 A1 WO 2008089614A1
Authority
WO
WIPO (PCT)
Prior art keywords
port
protocol packet
secondary port
sent
primary
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.)
Ceased
Application number
PCT/CN2007/002398
Other languages
English (en)
Chinese (zh)
Inventor
Haizhou Xiang
Binxuan Li
Chenggui Cai
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
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 WO2008089614A1 publication Critical patent/WO2008089614A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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 IP network technologies, and in particular, to a method, system and device for ring link protection. Background technique
  • the Rapid Ring Protection Protocol is a link layer protocol specifically applied to the Ethernet ring. It can quickly enable the backup link to recover the ring network when a link failure occurs on the Ethernet ring.
  • An Ethernet ring that uses the RRPP protocol is mainly composed of multiple nodes. One of them is the master node, and the other nodes are transit nodes.
  • the two ports on the ring of the master node are classified into the primary port and the secondary port.
  • the secondary port of the primary node is usually in the closed state. The secondary port in the closed state cannot send and receive service packets, but can send and receive protocol packets.
  • the master node In order to detect a link fault in the ring network, the master node periodically sends a ring protocol (HELLO) message from the master port. In the case of a complete ring, the master node receives the self-send on the secondary port within a certain period. The HELLO packet, so that the primary node considers that the ring network is in a complete state, keeps the secondary port in the closed state to ensure that there is no loop; if the primary node does not receive the HELLO packet sent by itself on the secondary port within a certain period, it is considered When the ring network is in the fault state, the primary node opens the secondary port to send and receive service packets, and sends a message to notify other transit nodes to update the forwarding table. After the transit node updates the forwarding table, the data flow is switched to the backup link.
  • HELLO ring protocol
  • the secondary port of the primary node receives the HELLO packet sent by the primary port, it considers that the ring network is restored to the complete state, immediately shuts down the secondary port, and sends a message to notify other nodes to refresh the forwarding table. After the transmission node updates the forwarding table, the data flow is restarted. Switch back to the original link.
  • a link between a node on a ring network or a directly connected node fails, a down event of the node port is triggered, and the node immediately sends a fault (link_down) message to the master node.
  • the master node receives the faulty packet, it also considers that the ring network is in the fault state, immediately opens the secondary port, and sends a message to notify other transmitting nodes to update the forwarding table. After the transmitting node updates the forwarding table, the data stream is switched to the backup link.
  • the port of the faulty node will be up.
  • the faulty node will temporarily block the port.
  • the port can also transparently transmit RRPP packets.
  • the HELLO packet sent by the master node from the master port can penetrate the temporary blocked port.
  • the secondary port of the primary node receives the HELLO packet sent by the primary port, it considers that the ring network is in a complete state, immediately shuts down the secondary port, and sends a message to notify other nodes to open the temporary blocked port and refresh the forwarding table. After the publication, the data stream is switched back to the original link.
  • the master node detects the ring network link according to the fact that the secondary port does not receive the protocol packet sent by the master port or receives the fault packet sent by the transit node in a certain period. malfunction.
  • a link of the transmitting node fails, for example, the forwarding chip of the transmitting node fails, causing a unidirectional path, that is, a communication disconnection, a reverse path, or a slave from the primary port of the primary node to the secondary port of the primary node.
  • the secondary port of the primary node is disconnected from the primary port of the primary node, and the reverse path.
  • the primary node detects a link failure, it opens the secondary port to enable it to send and receive service packets.
  • the path from the secondary port to the primary port or from the primary port to the secondary port is originally a path, a loop occurs when the secondary port is opened, which eventually causes serious consequences of the entire network.
  • node 1 in a normal ring network consisting of four switches: node 1, node 2, node 3, and node 4, RRPP is enabled for each switch, and node 1 is set as a master node.
  • S is the secondary port of the primary node, and the secondary port is closed to prevent loops;
  • the node 4 is faulty, such as a forwarding chip abnormality, etc., causing the link of node 3 to node 4 to be unreachable, and the link of node 4 to node 3 is a path, and the single pass of node 4 to node 3 occurs.
  • the master node detects that the ring network is in the fault state, it immediately opens the secondary port S. At this time, the secondary port S can send and receive service packets. Therefore, a loop from the secondary port to the primary port appears in the ring network, and the whole may appear. The serious consequences of the net. Summary of the invention
  • the embodiment of the invention provides a method, a system and a device for protecting a ring network link, which are used to solve the problem in the prior art.
  • the master node detects a link fault
  • the secondary port is opened, and the communication loop is caused. The problem.
  • An embodiment of the present invention provides a ring network link protection method, which is applied to an Ethernet ring network, where the ring network includes a primary node and one or more transit nodes, and the primary node includes a primary port and a secondary port, and the method includes the following Steps:
  • the master node sends a protocol packet from the primary port and the secondary port to the transit node;
  • the master port and the secondary port open the secondary port when the protocol sent by the transmitting node is not received within a certain period of time after the protocol is issued.
  • An embodiment of the present invention provides a ring network link protection system, where the system includes:
  • a master node device including a primary port and a secondary port, configured to send a protocol packet from the primary port and the secondary port to the transit node device; a certain time after the primary port and the secondary port send a protocol packet
  • the secondary port is opened; the transit node device is configured to receive the protocol packet sent by the primary port, and send the protocol packet to the secondary port; Receiving a protocol packet sent by the secondary port, and sending the protocol packet to the primary port.
  • the embodiment of the present invention provides a master node device, which is connected to a transit node device, where the master node device includes a primary port and a secondary port, and the device further includes:
  • a sending unit configured to send a protocol packet from the primary port and the secondary port to the transit node device
  • the fault detecting unit is configured to open the secondary port when the protocol packet sent by the transit node device is not received within a certain period of time after the sending unit sends the protocol packet from the primary port and the secondary port.
  • the primary node of the ring network sends a protocol packet from the primary port and the secondary port to the transit node, and the primary port and the secondary port are after the protocol packet is sent.
  • the master node opens the secondary port. Because the primary port and the secondary port do not receive the protocol on time, it means that the ring network has failed but is not single. If the fault occurs, the secondary port is opened, and no loop occurs in the ring network.
  • one of the primary port and the secondary port does not receive the protocol packet on time, and the other port receives the protocol packet on time, it means A single-pass fault occurs in the ring network.
  • the present invention solves the problem that the primary node opens the secondary node once the link fault is detected in the prior art, causing a communication loop.
  • 1A is a schematic diagram of a link failure in an Ethernet ring network in the prior art
  • FIG. 1B is a schematic diagram of the prior art in which the secondary port of the primary node is opened after a single-pass failure occurs in the Ethernet ring network;
  • FIG. 3A is a schematic diagram of a link failure of an Ethernet ring network in the first embodiment of the present invention
  • FIG. 3B is a schematic diagram of a single-pass failure of an Ethernet ring network according to Embodiment 1 of the present invention
  • FIG. 4B is a schematic diagram of a case where a non-single-pass fault occurs in an Ethernet ring network
  • FIG. 4B is a schematic diagram of a secondary port of a primary node after a non-single-link failure occurs in the Ethernet ring network according to Embodiment 2 of the present invention
  • FIG. 5A is a schematic structural diagram of a system according to an embodiment of the present invention.
  • 5B is a schematic structural diagram of a master node device in a system according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a device according to an embodiment of the present invention. detailed description
  • a method for protecting a ring network link in the method, the master node sends protocol packets from the primary port and the secondary port respectively, and the primary port and the secondary port send the protocol packet within a certain period of time.
  • the master node will open the secondary port. Otherwise, to avoid loops, keep the secondary port in the closed state.
  • the embodiment of the present invention provides a ring network link protection method, which is applied to an Ethernet ring network using the RRPP protocol, where the ring network is mainly composed of multiple nodes, one of which is a master node, and the other nodes are transit nodes, and the master node
  • the two ports on the ring are divided into a primary port and a secondary port.
  • the secondary port of the primary node is usually in the closed state.
  • the secondary port in the closed state cannot receive or send service packets, but can send and receive protocol packets.
  • Step 201 The master node issues an agreement from the primary port and the secondary port respectively.
  • the master node On the ring network that uses the RRPP protocol, the master node sends protocol packets from the primary port and the secondary port.
  • the master node sends protocol packets from the primary port and the secondary port at regular intervals.
  • the timer is started for the primary port and the secondary port.
  • the protocol packet sent from the primary port will reach the secondary port of the primary node through the transit nodes in the ring network when the ring network is complete. After the primary port sends the protocol packet, if it is within a certain period of time, If the secondary port does not receive the protocol packet, the primary node considers that the link is faulty.
  • the protocol packets sent from the secondary port will eventually reach the primary port of the primary node through the various transit nodes in the ring network. If the primary port does not receive the protocol within a certain period of time, In the case of the text, the master node also believes that the link has failed.
  • Step 202 The primary node opens the secondary port when the primary port and the secondary port do not receive the protocol packet within a certain period of time after the protocol is sent.
  • This step includes the following three situations:
  • the master node When the primary port does not receive the protocol packet within a certain period of time after the protocol packet is sent, the master node considers that the link is faulty, but does not immediately open the secondary port. The protocol packet is not received within a certain period of time. If yes, it means that there is no one-way path in the ring network. The link fault detected by the master node is not a single-pass fault. At this time, the master node opens the secondary port. It can send and receive service packets, and send messages to other transmitting nodes to update the forwarding table. After the transmitting node updates the forwarding table, the data flow is switched to the backup link; otherwise, it means that there is a direction from the primary port to the secondary port in the ring network. In a one-way path, the link fault detected by the master node is a one-way fault. In order to avoid loops, the secondary port is not opened, but the secondary port is kept closed. In the closed state, only the timer is cleared;
  • the master node When the secondary port does not receive the protocol packet within a certain period of time after the protocol packet is sent, the master node considers that the link is faulty but does not immediately open the secondary port. Instead, it first determines whether the primary port is also transmitting the protocol packet. The protocol packet is not received within a certain period of time. If yes, it means that there is no one-way path in the ring network. The link fault detected by the master node is not a single-pass fault. At this time, the master node opens the secondary port. The device can send and receive service packets, and send messages to other transmitting nodes to update the forwarding table.
  • the transmission node After the transmission node updates the forwarding table, the data flow is switched to the backup link; otherwise, the ring network has a direction from the secondary port to the primary port.
  • the link fault detected by the master node In a one-way path, the link fault detected by the master node is a one-way fault.
  • the secondary port In order to avoid loops, the secondary port is not opened, but the secondary port is kept closed, and only the timer is cleared.
  • the master node When receiving the link fault packet sent by the transit node, the master node does not immediately open the secondary port. Instead, it first determines whether the primary port and the secondary port have not received the protocol packet within a certain period of time after the protocol packet is sent. If yes, it means that there is no unidirectional path in the ring network. The link fault detected by the master node is not a single-pass fault. At this time, the master node opens the secondary port to enable it to send and receive service packets and send packets at the same time.
  • the link fault detected by the master node is a single-pass fault. In order to avoid loops, the secondary port is not opened, but the secondary port is kept closed, and only the timer is cleared.
  • the certain time can be set and changed.
  • a timer can be set for the primary port and the secondary port respectively in the primary node, and then the primary port can be returned when the timer of the primary port expires.
  • the protocol packet is not received, and the primary port does not receive the protocol packet within a certain period of time after the protocol packet is sent.
  • the secondary port has not received the protocol packet when the timer of the secondary port expires.
  • the secondary port does not receive the protocol packet within a certain period of time after the protocol packet is sent; of course, the primary port and the secondary port of the master node can share a timer, in this case, when the timer expires The master port has not received the protocol packet, and it is determined that the master port does not receive the protocol within a certain period of time after the protocol is issued. When the timer expires, the secondary port has not received the protocol packet to determine that the secondary port has not received the protocol packet within a certain period of time after the protocol packet is sent.
  • Step 203 After the secondary port is opened, when the primary port or the secondary port of the primary node receives the protocol sent by the transmission node, the secondary port is closed;
  • the secondary port After the secondary port is opened, when the primary port and the secondary port receive the protocol packet, the ring network is restored to the complete state. To prevent loops, the secondary port needs to be shut down, and a packet is sent to notify other transmitting nodes to refresh the forwarding table. After the transit node updates the forwarding table, the data stream is switched back to the original link.
  • the ring network When one port of the primary port or the secondary port receives the protocol packet, only one port receives the protocol packet. At this time, the ring network does not return to the complete state, but a communication loop occurs, in order to avoid loops. More serious consequences, such as broadcast storms, also require the secondary port to be closed and send a message to inform other transmitting nodes to refresh the forwarding table.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • a switch is composed of four switches: node 1, node 2, node 3, and node 4, and RRPP is enabled on each switch, and node 1 is set as the master.
  • Node P is the primary port of the master node, S is the secondary port of the master node, and the secondary port is closed to prevent loops;
  • the support node 4 fails, causing the link from node 3 to node 4 to be unreachable, and the link from node 4 to node 3 is the path.
  • the master node detects that the ring network is in the fault state, in order to distinguish whether the fault is a single-pass fault, it is first determined whether the master port and the secondary port have not received the protocol packet within a certain period of time. Since the link from node 4 to node 3 is the path, the unidirectional path of node 4-> node 3-> node 2-> node 1 appears in the ring network. At this time, the master port can receive the protocol packet sent by the slave port.
  • the link fault detected by the master node is a single-pass fault, and in order to avoid the communication loop in the direction of node 4->node 3->node 2->node 1->node 4, the secondary port is not opened, and Keep the secondary port off and only clear the timer.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • each switch is enabled with RRPP, and node 1 is set as the master node, P is the master port of the master node, and S is the secondary port of the master node. The secondary port is closed. To prevent loops;
  • Fig. 4A it is assumed that node 3 and node 4 fail, causing the link from node 3 to node 4 and node 4 to node 3 to fail.
  • the master node detects that the ring network is in the fault state, in order to distinguish whether the fault is a single-pass fault, it is first determined whether the master port and the secondary port have not received the protocol packet within a certain period of time. Since the link from node 3 to node 4 and node 4 to node 3 are unreachable, there is no unidirectional path in the ring network.
  • neither the primary port nor the secondary port can receive the protocol packet, so the link detected by the master node
  • the fault is not a single-pass fault, so the master node opens its secondary port to enable it to send and receive service packets, and sends a message to inform other transport nodes to update the forwarding table.
  • the transport node updates the forwarding table, the data flow is switched to the backup link. .
  • a communication path for service message transmission is established between the four nodes, as shown in Fig. 4B.
  • an embodiment of the present invention further provides a ring network link protection system, where the system includes: a master node device 501 including a primary port P and a secondary port S, respectively, for respectively from the primary port and the secondary
  • the port sends a protocol packet to the transit node device; when the primary port and the secondary port do not receive the protocol packet sent by the transit node device within a certain period of time after the protocol packet is sent, the secondary port is opened;
  • the node device 502 is configured to receive the protocol packet sent by the primary port, and send the protocol packet to the secondary port; receive the protocol packet sent by the secondary port, and send the protocol packet to the primary port. Text.
  • the master node device 501 further includes a sending unit 5011 and a fault detecting unit 5012, where the sending unit 5011 is configured to send a protocol packet from the primary port and the secondary port to the transmitting node device, respectively; 5012.
  • the method is: when the sending unit does not receive the protocol packet sent by the transit node device within a certain period of time after the sending unit sends the protocol packet from the primary port and the secondary port, the secondary port is opened.
  • the sending unit 5011 is configured to send a protocol packet from the primary port and the secondary port to the transmitting node device at regular intervals.
  • the fault detecting unit 5012 includes a first processing unit 50121, a second processing unit 50122, and a
  • the third processing unit 50123 is configured to: when the primary port does not receive the protocol packet sent by the transit node device within a certain period of time after the primary port sends the protocol packet, determine whether the secondary port is The protocol message sent by the transit node device is not received within a certain period of time after the protocol packet is sent, and if so, the secondary port is opened; the second processing unit 50122 is configured to send the protocol packet after the secondary port sends the protocol packet.
  • the third processing unit 50123 is configured to: when receiving the fault packet sent by the transit node device, determine whether the primary port and the secondary port are not within a certain period of time after sending the protocol packet Receiving a protocol packet sent by the transit node device, and if yes, opening the secondary port.
  • the master node device 501 further includes a fault recovery unit 5013, configured to close the secondary port when the primary port or/and the secondary port receives a protocol packet sent by the transit node device.
  • an embodiment of the present invention further provides a master node device, where the device includes a primary port P and a secondary port S, which can be applied to a ring link protection system, and is connected to a transmission node device, and the device further includes sending The unit 601 and the fault detecting unit 602, wherein the sending unit 601 is configured to send a protocol packet from the primary port and the secondary port to the transmitting node device, respectively; and the fault detecting unit 602 is configured to send the sending unit from the primary When the port and the secondary port do not receive the protocol packet sent by the transit node device within a certain period of time after the protocol packet is sent, the secondary port is opened.
  • the sending unit 601 is configured to send a protocol packet from the primary port and the secondary port to the transmitting node device at regular intervals.
  • the fault detection unit 602 includes a first processing unit, a second processing unit 6022, and a third processing unit 6023.
  • the first processing unit 6021 is configured to not receive the protocol packet after the primary port sends the protocol packet.
  • the protocol packet sent by the node device is transmitted, it is determined whether the secondary port does not receive the protocol packet sent by the transit node device within a certain period of time after the protocol packet is sent, and if yes, the secondary port is opened;
  • the second processing unit 6022 is configured to: when the protocol port sent by the transit node device is not received within a certain period of time after the slave port sends the protocol packet, determine whether the master port is certain after the protocol packet is sent. The protocol sent by the transit node device was not received within the time limit.
  • the third processing unit 6023 is configured to determine, when receiving the fault message sent by the transit node device, whether the primary port and the secondary port are in an agreement.
  • the protocol packet sent by the transit node device is not received within a certain period of time after the packet, and if so, the secondary port is opened.
  • the device further includes a fault recovery unit 603, configured to close the secondary port when the primary port or/and the secondary port receives a protocol packet sent by the transmitting node device.
  • the master node may not receive the protocol packet within a certain period of time after the protocol packet is sent by the primary port or the secondary port, or may detect the link fault by receiving the fault packet sent by the transit node.
  • a link failure from the primary port to the secondary port can be detected, and a link failure from the secondary port to the primary port can also be detected.
  • the backup link is enabled only when it is determined that the link failure is not a single-pass failure, and the secondary port is opened, because opening the secondary port in the single-pass failure causes communication on the ring network. Loops, while communication loops can cause serious adverse consequences such as broadcast storms.
  • the link fault is not a single-pass fault, and the secondary port can be opened; if the primary port And one of the ports on the secondary port does not receive the protocol packet sent by the transit node within a certain period of time after the protocol packet is sent, and the other port receives the protocol sent by the transit node within a certain period of time after the protocol packet is sent.
  • the packet indicates that the link fault is a single-pass fault and does not open the secondary port.
  • the primary node does not enable the backup link and opens the secondary port, thereby ensuring that communication does not occur in the ring network.
  • the loop avoids serious adverse consequences such as broadcast storms caused by communication loops.
  • the software corresponding to the invention can be stored in a computer readable storage medium, and the computer can implement the functions that the software can perform.

Landscapes

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

Abstract

Procédé de protection d'une liaison en anneau utilisée dans un anneau Ethernet. Cet anneau comprend un noeud maître et plus d'un noeud de transit. Ledit noeud maître comprend un premier port et un deuxième port. Selon le procédé, le noeud maître envoie un message d'accueil aux noeuds de transit par ledit premier port et ledit deuxième port, si le premier port et le deuxième port ne reçoivent pas ce message d'accueil qui est retransmis par les noeuds de transit, au bout d'un certain temps après l'envoi du message d'accueil, le noeud maître déverrouille le deuxième port. Ce procédé permet d'éviter la boucle de communication qui est créée lorsque le noeud maître utilise la liaison de sauvegarde.
PCT/CN2007/002398 2007-01-17 2007-08-10 Procédé, système et dispositif de protection d'une liaison en anneau Ceased WO2008089614A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007100009881A CN101001192B (zh) 2007-01-17 2007-01-17 一种环网链路保护的方法、系统及设备
CN200710000988.1 2007-01-17

Publications (1)

Publication Number Publication Date
WO2008089614A1 true WO2008089614A1 (fr) 2008-07-31

Family

ID=38693009

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/002398 Ceased WO2008089614A1 (fr) 2007-01-17 2007-08-10 Procédé, système et dispositif de protection d'une liaison en anneau

Country Status (2)

Country Link
CN (1) CN101001192B (fr)
WO (1) WO2008089614A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105429892A (zh) * 2015-10-29 2016-03-23 北京星网锐捷网络技术有限公司 一种轨道交通网络防止环路的方法及设备
CN110098967A (zh) * 2019-05-14 2019-08-06 浙江国利网安科技有限公司 一种通信方法、装置、设备及介质
CN113645312A (zh) * 2021-08-25 2021-11-12 烽火通信科技股份有限公司 一种基于erps协议的子环网链路保护方法与装置
CN115412424A (zh) * 2022-08-17 2022-11-29 浪潮思科网络科技有限公司 一种mlag环境下双主设备检测方法及设备

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001192B (zh) * 2007-01-17 2010-04-21 华为技术有限公司 一种环网链路保护的方法、系统及设备
CN101163038B (zh) * 2007-08-16 2010-06-02 中兴通讯股份有限公司 一种以太网设备链路保护的方法
CN101127674B (zh) * 2007-09-25 2011-11-30 中兴通讯股份有限公司 以太环网系统传输节点初始化方法
CN101141333A (zh) * 2007-10-12 2008-03-12 中兴通讯股份有限公司 一种以太环网系统主节点从端口故障处理方法
CN101262402B (zh) * 2007-11-08 2011-08-10 北京东土科技股份有限公司 一种环网间冗余备份的实现方法
CN101184013B (zh) * 2007-12-13 2011-04-13 杭州华三通信技术有限公司 一种避免产生环路的方法、主节点和系统
CN101212366B (zh) * 2007-12-21 2011-12-21 杭州华三通信技术有限公司 以太环网中的故障检测方法、系统及主节点
CN101227371B (zh) * 2008-02-18 2011-06-22 中兴通讯股份有限公司 同级交换机设备间的备份切换方法和装置
CN101237319B (zh) * 2008-02-20 2012-01-04 杭州华三通信技术有限公司 以太环网中的主节点、时间同步方法和以太环网系统
CN101227372B (zh) * 2008-02-21 2010-09-08 杭州华三通信技术有限公司 以太环网保护方法、传输节点和主节点
CN101989934B (zh) * 2009-08-06 2017-04-05 中兴通讯股份有限公司 一种数据环网故障检测及定位的方法和系统
CN101764731B (zh) * 2009-12-09 2011-11-30 熊伟 一种以太网环网算法切换方法
CN102111317B (zh) * 2009-12-25 2013-06-05 中兴通讯股份有限公司 以太环网中保护控制虚拟局域网的方法、系统及装置
CN101997724A (zh) * 2010-11-22 2011-03-30 中兴通讯股份有限公司 一种更新组播转发条目的方法及装置
CN102291290A (zh) * 2011-08-08 2011-12-21 浙江中控技术股份有限公司 以太环网故障检测、连接的方法和系统
CN102244600A (zh) * 2011-08-12 2011-11-16 华为技术有限公司 一种rrpp环网中链路故障检测及处理方法、装置
CN102710442B (zh) * 2012-06-01 2014-12-10 中兴通讯股份有限公司 网络管理业务口的管理方法、通信设备及通信系统
CN103220201B (zh) * 2013-04-24 2016-08-17 杭州华三通信技术有限公司 一种环网故障检测保护方法和设备
CN103973537B (zh) * 2014-05-09 2017-06-27 杭州同尊信息技术有限公司 一种具有故障保护功能的环网及用于环网的故障保护方法
CN105223931B (zh) * 2015-10-15 2018-02-09 固高科技(深圳)有限公司 柔性制造系统及其通信系统、通信方法
CN106357832B (zh) * 2016-08-24 2019-10-18 浙江宇视科技有限公司 环网地址表项更新机制方法及装置
CN108933732B (zh) * 2017-05-23 2021-10-15 中国电信股份有限公司 环路检测方法、装置和系统
JPWO2019167175A1 (ja) * 2018-02-28 2020-08-27 三菱電機株式会社 通信システム
CN110912815B (zh) * 2018-09-14 2022-07-05 中兴通讯股份有限公司 一种网元防成环方法、装置、设备及可读存储介质
CN111901216A (zh) * 2020-09-01 2020-11-06 昆山尚尼司电子科技有限公司 Rs485环状网路的备援处理方法与系统
CN115550106A (zh) * 2021-06-30 2022-12-30 中兴通讯股份有限公司 环网节点的控制方法、网络设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1412977A (zh) * 2001-10-10 2003-04-23 阿尔卡塔尔公司 在rpr网中传播故障信息的方法及相应rpr数据包
US6766482B1 (en) * 2001-10-31 2004-07-20 Extreme Networks Ethernet automatic protection switching
CN1812361A (zh) * 2006-01-23 2006-08-02 杭州华为三康技术有限公司 快速环网保护方法及系统
CN1859220A (zh) * 2006-06-07 2006-11-08 杭州华为三康技术有限公司 一种对主站点进行备份的方法和一种备用站点
CN101001192A (zh) * 2007-01-17 2007-07-18 华为技术有限公司 一种环网链路保护的方法、系统及设备
CN101030901A (zh) * 2007-04-27 2007-09-05 中控科技集团有限公司 分布式以太网系统及基于该系统的故障检测方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1412977A (zh) * 2001-10-10 2003-04-23 阿尔卡塔尔公司 在rpr网中传播故障信息的方法及相应rpr数据包
US6766482B1 (en) * 2001-10-31 2004-07-20 Extreme Networks Ethernet automatic protection switching
CN1812361A (zh) * 2006-01-23 2006-08-02 杭州华为三康技术有限公司 快速环网保护方法及系统
CN1859220A (zh) * 2006-06-07 2006-11-08 杭州华为三康技术有限公司 一种对主站点进行备份的方法和一种备用站点
CN101001192A (zh) * 2007-01-17 2007-07-18 华为技术有限公司 一种环网链路保护的方法、系统及设备
CN101030901A (zh) * 2007-04-27 2007-09-05 中控科技集团有限公司 分布式以太网系统及基于该系统的故障检测方法

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105429892A (zh) * 2015-10-29 2016-03-23 北京星网锐捷网络技术有限公司 一种轨道交通网络防止环路的方法及设备
CN105429892B (zh) * 2015-10-29 2018-10-12 北京星网锐捷网络技术有限公司 一种轨道交通网络防止环路的方法及设备
CN110098967A (zh) * 2019-05-14 2019-08-06 浙江国利网安科技有限公司 一种通信方法、装置、设备及介质
CN110098967B (zh) * 2019-05-14 2022-08-12 浙江国利网安科技有限公司 一种通信方法、装置、设备及介质
CN113645312A (zh) * 2021-08-25 2021-11-12 烽火通信科技股份有限公司 一种基于erps协议的子环网链路保护方法与装置
CN115412424A (zh) * 2022-08-17 2022-11-29 浪潮思科网络科技有限公司 一种mlag环境下双主设备检测方法及设备
CN115412424B (zh) * 2022-08-17 2024-03-26 浪潮思科网络科技有限公司 一种mlag环境下双主设备检测方法及设备

Also Published As

Publication number Publication date
CN101001192A (zh) 2007-07-18
CN101001192B (zh) 2010-04-21

Similar Documents

Publication Publication Date Title
WO2008089614A1 (fr) Procédé, système et dispositif de protection d'une liaison en anneau
CN100409634C (zh) 快速环网保护方法及系统
CN100571180C (zh) 保障以太环网在传输节点故障时可靠运行的方法及装置
CN101686158B (zh) 以太网环路保护故障恢复的控制方法及以太网环路节点
CN100521638C (zh) 相交以太环网及其自动保护方法、以及环网节点设备
CN103843286B (zh) 用于基于交换器连接性触发路由器状态更改的方法和装置
WO2009039698A1 (fr) Système de réseau en anneau ethernet, noeud principal de celui-ci et procédé d'initialisation de ce noeud
CN100493006C (zh) 一种环路故障检测方法、子环主节点以及子环
WO2008089701A1 (fr) Procédé, dispositif et système de protection d'anneau
WO2010045832A1 (fr) Procédé et appareil destinés à protéger un groupe d'agrégation de liaisons d'un réseau en anneau ethernet
WO2009039697A1 (fr) Système de réseau en anneau ethernet, noeud d'émission de réseau en anneau ethernet et procédé d'initialisation de celui-ci
US20090147672A1 (en) Protection switching method and apparatus for use in ring network
CN101247306A (zh) 以太环网中边缘端口阻塞的方法、以太环网系统和设备
WO2010031295A1 (fr) Procédé de contrôle pour reprise après une panne ethernet
CN101127653B (zh) 设置有备份的以太网环网设备及其主设备备份的实现方法
CN101677267B (zh) 一种跨环转发协议帧的方法及以太网多环中的共享节点
WO2011026347A1 (fr) Procédé de protection de réseau en boucle ethernet et nœud de transmission
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
CN101478469B (zh) Rrpp环链路切换的方法和系统
CN101039172B (zh) 以太环网系统及其保护方法和备用主节点
EP2533470B1 (fr) Procédé et équipement de prévention de rafraîchissement répété de table d'adresse de noeud d'anneau ethernet
CN110635940B (zh) 一种eaps以太环网的主备倒换方法
CN102487348B (zh) 一种环网上行链路保护的实现方法和系统
CN102238067A (zh) 一种快速环网保护协议环上的切换方法和装置
CN100550812C (zh) 提高快速环网可靠性的方法、系统和节点设备

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

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

Country of ref document: EP

Kind code of ref document: A1