[go: up one dir, main page]

WO2012171380A1 - Procédé et dispositif de traitement de défaillance d'extrémité distante pour l'ethernet - Google Patents

Procédé et dispositif de traitement de défaillance d'extrémité distante pour l'ethernet Download PDF

Info

Publication number
WO2012171380A1
WO2012171380A1 PCT/CN2012/072829 CN2012072829W WO2012171380A1 WO 2012171380 A1 WO2012171380 A1 WO 2012171380A1 CN 2012072829 W CN2012072829 W CN 2012072829W WO 2012171380 A1 WO2012171380 A1 WO 2012171380A1
Authority
WO
WIPO (PCT)
Prior art keywords
edge device
associated port
port
message
fault
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/CN2012/072829
Other languages
English (en)
Chinese (zh)
Inventor
张付友
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2012171380A1 publication Critical patent/WO2012171380A1/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
    • 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 communications, and in particular to a method and apparatus for processing an Ethernet remote fault.
  • Ethernet technology has been widely used in local area networks, metropolitan area networks, and wide area networks due to its advantages of simplicity, ease of use, and low cost.
  • OAM operation, management, and maintenance
  • the Ethernet OAM mechanism mainly includes a link layer OAM mechanism and a service layer OAM mechanism (CFM, connectivity fault management).
  • the ETH-OAM is an OAM mechanism for the direct link. It is mainly configured to manage and maintain the local link. It can provide functions such as remote discovery, remote loopback, remote fault indication, and link monitoring.
  • Connection Fault Management (CFM) is mainly for carrier networks and uses a multi-domain network model. CFM enables end-to-end fault management.
  • the network administrator divides the network into several nestable maintenance domains based on management and maintenance purposes.
  • the network is defined by defining a series of maintenance points (MPs) on the maintenance domain. Management and maintenance. Through CFM, network administrators can effectively check, isolate, and report connectivity faults on virtual bridge LANs.
  • the main functions of CFM are: connectivity check, loopback detection, link tracking, and alarms.
  • a single CFM maintenance domain is shown in Figure 1.
  • the maintenance domain in the figure defines a series of maintenance points on the edge device and internal devices.
  • the W point indicates the maintenance end point (Maintenance End Point, ⁇ for short). Indicates the Maintenance Intermediate Point (MIP).
  • MIP Maintenance Intermediate Point
  • the service-based Ethernet OAM implements the management and maintenance functions through MEP and MIP.
  • the Ethernet OAM mechanism can diagnose faults in the management domain and use corresponding mechanisms (such as Spanning-Tree Protocol (ST:P), EAPS, etc.) to take corresponding switching measures.
  • ST:P Spanning-Tree Protocol
  • EAPS etc.
  • the fault detection and linkage mechanism for the uplink and downlink access links is lacking. For example, in some special application scenarios in the carrier network, when the uplink fails, the downlink becomes unavailable.
  • the uplink and downlink do not belong to the same network administrator, the uplink cannot be used.
  • the failure of the link is notified to the downlink, causing the downlink to fail to respond to the failure in a timely manner.
  • the network between E and F (including E and F) is the carrier network
  • A is the server
  • B is the user who uses the service of A. If the link between A and E fails, AEFB This link can't communicate normally, and B can't continue to use A. Service, but since B cannot sense the link failure between A and E, even user B uses high availability (High
  • a method for processing an Ethernet remote fault including: receiving, by a second edge device at one end of the access link, a first message sent by a first edge device at another end of the access link, The first message is sent by the first edge device when it detects that the associated first associated port is faulty, and the first message carries the fault information of the first associated port.
  • the second edge device is configured according to the first associated port.
  • the fault information and the physical state of the second associated port associated with the second edge device close the second associated port.
  • the method before the second edge device receives the message sent by the first edge device, the method further includes: the first edge device detecting that the first associated port associated with it fails, and sending the first message to the second edge device.
  • the method further comprises: the second edge device updating the physical state of the second associated port to a closed state.
  • the method includes: the second edge device generates fault alarm information.
  • the method further includes: the second edge device receiving the second message sent by the first edge device, where the second message is that the first edge device detects the first And the second message carries the fault recovery information of the first associated port; the second edge device opens according to the fault recovery information of the first associated port and the current physical state of the second associated port.
  • the second associated port Preferably, after the second edge device opens the second associated port, the method further comprises: the second edge device updating the physical state of the second associated port to an open state.
  • the method further includes: the second edge device generating fault recovery alarm information.
  • a device for processing an Ethernet remote fault including: a receiving module, configured to receive a first message sent by a first edge device at another end of the access link, where The message is sent by the first edge device when detecting that the associated first associated port is faulty, and is carried in the first message.
  • the fault information of the first associated port is configured to: close the second associated port according to the fault information of the first associated port and the physical state of the second associated port associated with the second edge device.
  • the receiving module is further configured to receive the second message sent by the first edge device, where the second message is sent by the first edge device when detecting the failure recovery of the first associated port, and the second message is carried in the second message.
  • the execution module is further configured to open the second associated port according to the fault recovery information of the first associated port and the physical state of the second associated port associated with the second edge device.
  • the foregoing apparatus further includes: an updating module, configured to update a physical state of the second associated port according to an operation performed by the execution module on the second associated port.
  • the foregoing apparatus further includes: an alarm module, configured to generate corresponding alarm information according to information carried in the message received by the receiving module.
  • FIG. 1 is a schematic diagram of a single CFM maintenance domain according to the related art
  • FIG. 2 is a schematic diagram of an application example when a link fails according to the related art
  • FIG. 3 is an Ethernet remote according to an embodiment of the present invention.
  • Figure 4 is a schematic illustration of a one-to-many designation in accordance with a preferred embodiment of the present invention
  • Figure 5 is a schematic illustration of a ring network designation in accordance with a preferred embodiment of the present invention
  • Figure 6 is a preferred embodiment in accordance with the present invention.
  • FIG. 10 Schematic diagram of the format of the Interface Status TLV field of the connectivity check message (CCM frame);
  • Figure 2 is a diagram showing the value of the Interface Status TLV field of a connectivity check message (CCM frame) in accordance with a preferred embodiment of the present invention;
  • Figure 8 is a process flow diagram of a port state change message in accordance with a preferred embodiment of the present invention;
  • Is a process flow diagram of a connectivity check message (CCM frame) in accordance with a preferred embodiment of the present invention;
  • FIG. 10 is a port state transition diagram in accordance with a preferred embodiment of the present invention;
  • FIG. 11 is an Ethernet remote fault in accordance with an embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of an apparatus for processing an Ethernet remote fault according to a preferred embodiment of the present invention
  • FIG. 13 is a schematic structural view of a preferred apparatus according to a preferred embodiment of the present invention.
  • the method mainly includes the following steps (step S302-step S304): Step S302, accessing one end of the link
  • the second edge device receives the first message sent by the first edge device at the other end of the access link, where the first message is sent by the first edge device when detecting that the associated first associated port is faulty, and A message carries the fault information of the first associated port.
  • the first edge device and the second edge device may be pre-arranged (where the first edge device is remote from the second edge device)
  • the second edge device is configured with a fault detection and isolation function relative to the first edge device. For example, in FIG.
  • the fault detection function can be configured on the edge device E, and the configured fault detection function is configured.
  • Associate with port 1 (port l) configure isolation on edge device F, and associate fault isolation with port 2 (port 2).
  • edge device E detects the associated port (that is, portl) associated with it.
  • a message is sent to the edge device F (the message carries the fault information of port1).
  • the second edge device may further generate fault alarm information. For example, in FIG.
  • the physical states of the associated ports port1 and port3 can be separately monitored on the edge device E (ie, the first edge device) and the F (ie, the second edge device) at both ends.
  • the network can be The end where the access link fails is called the designated end (that is, the edge device E of Figure 2), and the end (the opposite end) that needs to be fault-isolated is called the designated end (the edge device F of Figure 2).
  • the specified method is not limited. It can be specified for one-way or two-way. Of course, if the condition allows, it can also be specified in multiple directions. In the embodiment of the present invention, the specified manner includes but is not limited to the following forms:
  • FIG. 5 is a schematic diagram of a ring network application according to a preferred embodiment of the preferred embodiment of the present invention.
  • port1 is down
  • port 2 port 3
  • port4 are closed.
  • the specified end and the designated end are relative, and the specified role and the designated role are determined after the fault occurs.
  • the peer the first edge device
  • the peer end of the peer can be regarded as the designated end (the second edge device).
  • the message carrying the fault information is sent to the peer end (the designated end) (for example, in the embodiment of the present invention, the message is a protocol frame), so as to reach the port.
  • the failure notification of 1 is given to the designated end.
  • the designated end may also generate fault alarm information.
  • the second edge device closes the second associated port according to the fault information of the first associated port and the physical state of the second associated port associated with the second edge device.
  • the second edge device receives the message carrying the fault information from the first edge device (the designated end), according to the first associated port (for example, the port port1 associated with the designated end)
  • the fault information and the physical state of the second associated port close the second associated port (eg, port 2) for fault isolation purposes.
  • the second edge device may also update the physical state of the second associated port to a closed state. For example, in FIG. 2, the port may be updated (also referred to as migration). 2 (port 2)
  • the physical state is off.
  • the second edge device closes the second associated port, if the first edge device detects failure recovery of its associated first associated port, the first edge device And sending, by the second edge device, a second message that carries the fault recovery information of the first associated port, the second edge device receives the second message sent by the first edge device, and then the second edge device recovers the information according to the failure of the first associated port. And opening a second associated port with the current physical state of the second associated port. After the second edge device receives the second message (carrying the fault recovery information) sent by the first edge device, the second edge device may further generate the fault recovery alarm information.
  • the second edge device may also be the second
  • the physical status of the associated port is updated to the open state.
  • the physical state of port 2 can be updated (also referred to as migration).
  • Step 1 on the edge devices E and F in FIG.
  • the connectivity periodically sends a connectivity check message (CCM frame to the peer end, where the CCM frame includes
  • Interface Status TLV field The format of the TLV field is shown in Figure 6.
  • the Interface Status TLV field in the CCM frame carries the status of the associated port.
  • Step 2 for two-way The physical status of the associated port is monitored at the two ends.
  • the end is the designated end.
  • Corresponding values where the value of the Interface Status TLV field is as shown in Figure 7) are advertised to the designated end; for unidirectional designation, only the state of the associated port needs to be monitored at the designated end, in a preferred implementation of the present invention.
  • the Interface Status TIN field uses the values of isUp, isDown, and isDormant, which represent the three port states: the physical state of the port is up, the physical state of the port is down, and the port is artificial because it needs to isolate the remote fault. Close, where the local MEP processes the port status change message. The process is shown in Figure 8, which includes the following steps:
  • 5802 Determine the type of the message. If it is the shutdown command, go to S803. If it is physical up, go to S804. If it is physical down, go to S805.
  • the local port status is migrated to isDown, and the process ends.
  • Step 3 After receiving the CCM frame, the edge device of the designated end may first check the Interface Status TLV field information carried by the edge device, and close or open the associated port according to the value of the Interface Status TLV field and the physical state of the associated port of the local end. The action of the fault isolation or fault recovery, and the corresponding alarms are generated, and the state of the associated port of the local end can be migrated (updated).
  • the processing flow of the CCM frame is as shown in FIG. 9, and the process includes the following steps: S901. Receive, by the designated end, a CCM message.
  • FIG. 10 is a port state transition diagram according to a preferred embodiment of the present invention.
  • the event causing port state transition and its meaning are as follows: el: Receives a CCM frame carrying port status is isDown. E2: Received a CCM frame carrying the port status as isUp, or the CFM function fails for some reason, or the CCM continuity is lost. E3: Configure the shutdown command for the associated port. E4: Physical down of the associated port (including the shutdown command). E5: Associated port physical up (including the result of the no shutdown command).
  • the response when the port state is migrated is as follows: rl : Set the associated port state to isDormant to physically drop the associated port.
  • R2 Set the associated port status to isUp to physically raise the associated port.
  • R3 Set the port status to isDown.
  • R4 Set the associated port status to isUp.
  • events other than el-e5 do not respond.
  • the method for processing the remote fault of the Ethernet provided by the foregoing embodiment can detect the remote fault and isolate the fault at the local end. After the remote fault is eliminated, the local end can perform the recovery operation on the fault. You can notify the administrator to take appropriate action in time. In particular, if there is a backup link on the local end, you can quickly perform the switchover process to minimize data loss caused by remote faults.
  • FIG. 11 is a schematic structural diagram of a device for processing an Ethernet remote fault according to an embodiment of the present invention.
  • the device is located at a first edge device.
  • the device includes: a receiving module 10 and an executing module 20.
  • the receiving module 10 is configured to receive a first message sent by the first edge device at the other end of the access link, where the first message is sent by the first edge device when detecting that the associated first associated port is faulty. And the first message carries the fault information of the first associated port;
  • the executing module 20 is connected to the receiving module 10, and is configured to be configured according to the fault information of the first associated port and the second associated port associated with the second edge device. Physical state, close the second associated port.
  • the receiving module 10 is further configured to receive the second message sent by the first edge device, where the second message is sent by the first edge device when detecting the failure recovery of the first associated port, and the second message is carried in the second message.
  • FIG. 12 is a schematic structural diagram of a device for processing an Ethernet remote fault according to a preferred embodiment of the present invention.
  • the device is configured to implement the method for processing an Ethernet remote fault provided by the foregoing embodiment. As shown in FIG. 12, the device is further configured.
  • the method may include: an alarm module 30 and an update module 40.
  • FIG. 13 is a schematic structural diagram of a preferred apparatus according to a preferred embodiment of the present invention. As shown in FIG. 13, the preferred apparatus includes: a CFM unit 131, a driving unit 132, a transceiver unit 133, an interface management unit 134, an alarm unit 135, and Operation and maintenance unit 136.
  • the CFM unit 131 is configured to operate the protocol and maintain a port state state machine, and can notify the local end fault, and can also detect the remote fault, and notify the driving unit 132 to perform fault isolation and fault recovery operations;
  • the unit 132 is configured to close or open the port to implement fault isolation and fault recovery;
  • the transceiver packet unit 133 is configured to send and receive a fault notification message;
  • the interface management unit 134 is configured to periodically poll the associated port state, and The change information of the status of the associated port is notified to the CFM unit 131;
  • the alarm unit 135 is configured to generate an alarm when detecting the remote fault or the remote fault recovery, and notify the network administrator;
  • the operation and maintenance unit 136 is configured to receive the configuration command of the user. And issued to the relevant unit.
  • the remote end fault processing device provided by the foregoing embodiment can detect the remote fault and isolate the fault at the local end. After the remote fault is eliminated, the local end can perform the recovery operation on the fault. You can notify the administrator to take appropriate action in time. In particular, if there is a backup link on the local end, you can quickly perform the switchover process to minimize data loss caused by remote faults. From the above description, it can be seen that the present invention achieves the following technical effects:
  • the method and device for processing an Ethernet remote fault are used to solve the uplink or downlink failure in the prior art due to uplink
  • the edge device in the network can detect the link fault periodically, and notify the edge device of the peer end after detecting the fault, so that the edge device of the peer end closes the port associated with it according to the fault information, and opens the link after the link fault is recovered.
  • the port thus retransmits the data.

Landscapes

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

Abstract

L'invention concerne un procédé et un dispositif de traitement de défaillance d'extrémité distante pour l'Ethernet. Ledit procédé se déroule de la manière suivante : un second dispositif périphérique accède à une extrémité d'une liaison qui reçoit un premier message envoyé par un premier dispositif périphérique accédant à une autre extrémité de la liaison, ce premier message étant envoyé par le premier dispositif périphérique lorsqu'une détection indique qu'un premier port associé qui lui associé est défaillant, et ledit premier message contenant les informations de défaillance qui concernent le premier port associé ; et le second dispositif périphérique ferme un second port associé qui lui est associé en fonction des informations de défaillance qui concernent le premier port associé et de l'état physique du second port associé. Grâce à la présente invention, un dispositif périphérique d'un réseau peut détecter régulièrement la défaillance d'une liaison et informe rapidement un dispositif périphérique homologue après la détection d'une défaillance, ce qui permet au dispositif périphérique homologue de fermer un port qui lui est associé en fonction des informations de défaillance et d'ouvrir ce port pour retransmettre les données après la récupération de la liaison défaillante.
PCT/CN2012/072829 2011-06-17 2012-03-22 Procédé et dispositif de traitement de défaillance d'extrémité distante pour l'ethernet Ceased WO2012171380A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110163802.0 2011-06-17
CN2011101638020A CN102231674A (zh) 2011-06-17 2011-06-17 以太网远端故障的处理方法及装置

Publications (1)

Publication Number Publication Date
WO2012171380A1 true WO2012171380A1 (fr) 2012-12-20

Family

ID=44844214

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/072829 Ceased WO2012171380A1 (fr) 2011-06-17 2012-03-22 Procédé et dispositif de traitement de défaillance d'extrémité distante pour l'ethernet

Country Status (2)

Country Link
CN (1) CN102231674A (fr)
WO (1) WO2012171380A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102231674A (zh) * 2011-06-17 2011-11-02 中兴通讯股份有限公司 以太网远端故障的处理方法及装置
CN102404143B (zh) * 2011-11-17 2014-04-02 华为技术有限公司 基于lacp的端口故障处理方法和lacp终端
CN105591775B (zh) 2014-10-23 2019-10-25 华为技术有限公司 一种网络的操作管理维护oam方法、装置和系统
CN105703936B (zh) * 2014-11-28 2020-06-09 中兴通讯股份有限公司 一种控制方法、装置及主控板
CN106302146A (zh) * 2016-10-17 2017-01-04 杭州迪普科技有限公司 链路聚合的收敛方法及装置
US10193746B2 (en) * 2016-12-21 2019-01-29 Juniper Networks, Inc. Deadlock avoidance using modified ethernet connectivity fault management signaling
CN109547229A (zh) * 2017-09-21 2019-03-29 中兴通讯股份有限公司 一种以太网故障处理方法及装置
CN109981450B (zh) * 2017-12-28 2021-06-15 中国电信股份有限公司 路径连通维护方法、装置和系统
CN119232544A (zh) * 2024-09-30 2024-12-31 湖北安心智能科技有限公司 一种1+1冗余保护网络的告警联动方法及相关设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1968159A (zh) * 2006-11-16 2007-05-23 杭州华为三康技术有限公司 网络故障检测联动方法及网络运营商边缘设备
CN101212366A (zh) * 2007-12-21 2008-07-02 杭州华三通信技术有限公司 以太环网中的故障检测方法、系统及主节点
CN101247306A (zh) * 2008-03-13 2008-08-20 华为技术有限公司 以太环网中边缘端口阻塞的方法、以太环网系统和设备
CN102231674A (zh) * 2011-06-17 2011-11-02 中兴通讯股份有限公司 以太网远端故障的处理方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1968159A (zh) * 2006-11-16 2007-05-23 杭州华为三康技术有限公司 网络故障检测联动方法及网络运营商边缘设备
CN101212366A (zh) * 2007-12-21 2008-07-02 杭州华三通信技术有限公司 以太环网中的故障检测方法、系统及主节点
CN101247306A (zh) * 2008-03-13 2008-08-20 华为技术有限公司 以太环网中边缘端口阻塞的方法、以太环网系统和设备
CN102231674A (zh) * 2011-06-17 2011-11-02 中兴通讯股份有限公司 以太网远端故障的处理方法及装置

Also Published As

Publication number Publication date
CN102231674A (zh) 2011-11-02

Similar Documents

Publication Publication Date Title
WO2012171380A1 (fr) Procédé et dispositif de traitement de défaillance d'extrémité distante pour l'ethernet
JP5508289B2 (ja) 多重リンク障害からのネットワーク回復システム及び方法
US9509591B2 (en) Technique for dual homing interconnection between communication networks
CN102394787B (zh) 基于epa交换机的双链路冗余控制方法
CN103843286B (zh) 用于基于交换器连接性触发路由器状态更改的方法和装置
US9385944B2 (en) Communication system, path switching method and communication device
JP2009206891A (ja) レイヤ２リングネットワークシステムとその管理方法
CN101399737A (zh) 用于以太环网的链路聚合组的保护方法及装置
JP2005130049A (ja) ノード
WO2008046358A1 (fr) Procédé et dispositif destinés à réaliser une pénétration d'un statut de liaison de réseau point à multipoint
CN101436975B (zh) 一种在环网中实现快速收敛的方法、装置及系统
WO2010031295A1 (fr) Procédé de contrôle pour reprise après une panne ethernet
CN101127653B (zh) 设置有备份的以太网环网设备及其主设备备份的实现方法
JP2009303092A (ja) ネットワーク装置および回線切替方法
WO2012171378A1 (fr) Procédé et routeur pour prévenir une interruption de flux provoquée par basculement de vpls vers l3
CN101626335B (zh) 一种双归连接网络的数据保护方法
CN108668308A (zh) 一种lte　ptn传送网及其静态路由保护方法
CN102857316B (zh) 一种实现源环网保护的方法及系统
JP2012231223A (ja) アクセスシステムおよび冗長切替方法
CN102238067B (zh) 一种快速环网保护协议环上的切换方法和装置
JP2003258822A (ja) パケットリングネットワーク及びそれに用いるパケットリングネットワーク間の接続方法
CN102487348B (zh) 一种环网上行链路保护的实现方法和系统
CN102025561B (zh) 一种以太环网中刷新mac的方法及系统
CN101641915A (zh) 重构通信网络的方法
WO2007057884A2 (fr) Indication de defaillance a distance de service vpls

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

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

Country of ref document: EP

Kind code of ref document: A1