WO2011094971A1 - 防止以太环网节点地址表重复刷新的方法和装置 - Google Patents

防止以太环网节点地址表重复刷新的方法和装置 Download PDF

Info

Publication number
WO2011094971A1
WO2011094971A1 PCT/CN2010/071700 CN2010071700W WO2011094971A1 WO 2011094971 A1 WO2011094971 A1 WO 2011094971A1 CN 2010071700 W CN2010071700 W CN 2010071700W WO 2011094971 A1 WO2011094971 A1 WO 2011094971A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
blocking
ring
protection link
ethernet ring
Prior art date
Application number
PCT/CN2010/071700
Other languages
English (en)
French (fr)
Inventor
吴少勇
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to JP2012551465A priority Critical patent/JP5491644B2/ja
Priority to KR1020127021429A priority patent/KR101402532B1/ko
Priority to US13/576,656 priority patent/US8948002B2/en
Priority to EP10845056.0A priority patent/EP2533470B1/en
Publication of WO2011094971A1 publication Critical patent/WO2011094971A1/zh

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
    • 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/40—Bus networks
    • H04L12/40006—Architecture of a communication node
    • H04L12/40013—Details regarding a bus controller

Definitions

  • the present invention relates to Ethernet technology, and in particular, to a method and apparatus for preventing repeated refreshing of an Ethernet ring node address table. Background technique
  • Ethernet is widely used in ring networking, which improves the reliability of the network.
  • fast protection switching is usually required to be within 50ms.
  • this fast protection switching technology can be implemented based on the International Telecommunication Union (ITU-T) G.8032v2 protocol.
  • an automatic protection switching protocol and mechanism is defined for the Ethernet layer of the ring topology Ethernet.
  • the network protection method is applicable to the ring topology Ethernet.
  • the main processes of the network protection are as follows: In the ring topology Ethernet, select a link as a Ring Protection Link (RPL), and a ring protection link.
  • the two adjacent nodes are used to control the blocking or opening of the ring protection link.
  • One node is called the RPL Owner Node and the other node is called the ring protection link neighbor node ( RPL Neighbour Node ), the adjacent port on the adjacent two nodes in the ring protection link relative to the ring protection link is called a ring protection link adjacent port (PRL Port).
  • PRL Port ring protection link adjacent port
  • the two adjacent nodes of the ring protection link block the adjacent ports of the link protection link to prevent the protected data from passing through the ring protection link; thus, any two of the Ethernet ring networks There is only a unique communication path between the nodes, so the closed loop of the communication path is not generated in the Ethernet ring network, preventing closed loop and network storm.
  • the link of the Ethernet ring network fails, such as If the faulty link is not a ring protection link, the node adjacent to the faulty link blocks the faulty port, and the two nodes adjacent to the ring protection link open the adjacent ports of the two ring protection link to protect the protected data. It can pass through the ring protection link, so a new communication path is generated between any two nodes on the ring protection link, which ensures the reconnection of the communication path and improves the reliability of the network.
  • the communication path of the data traffic needs to be changed. Since the address table information recorded by each node may not be applicable after the communication path of the data traffic changes, each node may need to be refreshed.
  • the address table the specific action is to delete the address entry of the port on the ring.
  • the Ethernet ring protection protocol frame sent by the node includes its own node number and blocked port index number; after receiving the protocol frame, other nodes extract the node number and blocked port index in the protocol frame. No., and compares the node number and the blocked port index number of the refresh record information saved for the receiving port.
  • the refresh record information corresponding to the receiving port is updated to the extracted node number and the blocked port index number. .
  • the node number and the blocked port index number in the protocol frame are different from the node number of the refresh record information corresponding to the peer port of the receiving port and the blocked port index number, the node may need to refresh the address table; When the node is blocking the port, delete the node number and blocked port index number of the refresh record information corresponding to the ports on the two rings.
  • the above refresh scheme of the Ethernet ring address table ensures that the Ethernet ring network can quickly delete the wrong address entry when switching, but also brings the problem of repeatedly refreshing the address table during handover.
  • the ring protection link blocking state (RPL Blocked, which is expressed as No Request) is sent.
  • NRRB NRRB Protocol frame.
  • the neighbor node updates the refresh record information corresponding to the receiving port to the received node number and the blocked port index number; and the node number and the blocked port index number and the receiving port in the received protocol frame
  • the node number of the refresh record corresponding to the peer port is different from the blocked port index. Therefore, the ring protection link neighbor node refreshes the address table according to the address refresh principle of the Ethernet ring network.
  • the neighboring node of the ring protection link also blocks the neighboring nodes of the ring protection link, and deletes the node number and the blocked port index number of the refresh record information corresponding to the ports on the two rings.
  • the node to which the ring protection link belongs will continue to send the ring protection link blocking state protocol frame. Therefore, after the ring protection link neighbor node receives the subsequent ring protection link blocking state protocol frame, it will not refresh the record because its two ports are not.
  • the address table is refreshed again, and the address table refresh operation is actually unnecessary, and the address table refresh operation is likely to cause an instantaneous burst of network traffic due to too many nodes or users involved, which is not conducive to network resources. Effective use and normal development of user services. Summary of the invention
  • the main object of the present invention is to provide a method and apparatus for preventing repeated refreshing of an Ethernet ring node address table, so as to solve the problem that the ring protection link neighbor node repeatedly refreshes the address table in the Ethernet ring backhaul scenario. .
  • the method includes:
  • the Ethernet ring network node determines whether the Ethernet ring network node is a ring protection link neighbor node, and whether the content that triggers the blocking is a ring protection link blocking state protocol frame. When the judgment result is yes, the Ethernet ring network node determines to save the two The refresh record information corresponding to the port on the ring.
  • the process of determining whether the Ethernet ring network node is a ring protection link neighbor node is implemented by querying a node attribute of the Ethernet ring network node.
  • the process of determining whether the content that triggers the blocking is a ring protection link blocking state protocol frame is implemented by parsing the content of the received data structure.
  • the method further includes: determining whether the Ethernet ring network node is a ring protection link neighbor node If the result is no, follow-up operations are performed according to the prior art.
  • the method further includes: determining whether the content that triggers the blocking is a ring protection link blocking state protocol frame, or not, performing a subsequent operation according to the prior art.
  • the refresh record information includes: a node number and a blocked port index number.
  • the device includes a connected blocking trigger detecting unit and a refresh record information maintaining unit. After the port state of the Ethernet ring node changes to a blocking state,
  • the blocking trigger detecting unit is configured to determine whether the Ethernet ring node to which the UE belongs is a ring protection link neighbor node, and whether the content that triggers the blocking is a ring protection link blocking state protocol frame, and notify the refreshing result of the determination result Record information maintenance unit;
  • the refresh record information maintenance unit is configured to: when the received judgment result is yes, determine to save the refresh record information corresponding to the two ring ports of the Ethernet ring network node to which the node belongs.
  • the blocking trigger detecting unit includes a node determining unit and a blocking cause determining unit.
  • the node determining unit is configured to determine whether the Ethernet ring network node to which the UE belongs is a ring protection link neighbor node, and generate a notification that can refresh the record information maintenance. The judgment result of the unit;
  • the blocking cause determining unit is configured to determine whether the blocking operation is caused by receiving the environmental protection link blocking state protocol frame, and generate a determination result that can notify the refresh record information maintenance unit.
  • the node judging unit and the blocking reason judging unit are respectively configured to notify the generated judgment result to the refresh record information maintenance unit;
  • the node judging unit and the blocking reason judging unit have a connection relationship, and are respectively used to notify the other party of the judgment result, so that the judgment result of the self is the trigger condition for the subsequent judgment of the other party.
  • the refresh record information includes: a node number and a blocked port index number.
  • the method and the device of the present invention can effectively solve the problem that the neighbor node of the ring protection link repeatedly refreshes the address table in the Ethernet ring backhaul scenario, and reduces the protection of the Ethernet ring network during protection switching. Traffic broadcasts improve switching efficiency.
  • Figure 1 is a schematic diagram of the operation of the Ethernet ring link without failure
  • FIG. 2 is a schematic diagram of operation when an Ethernet ring link fails
  • Figure 3 is a schematic diagram of the switchback operation of the Ethernet ring link failure recovery
  • FIG. 4 is a flowchart of preventing repeated refreshing of an Ethernet ring node address table according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram of a switchback operation of an Ethernet ring link failure recovery according to an embodiment of the present invention
  • FIG. The Ethernet ring node address table repeats the refresh device map. detailed description
  • FIG. 1 is a schematic diagram of the operation of the Ethernet ring link without failure.
  • nodes S1, S2, S3, and S4 form an Ethernet ring network.
  • the link between nodes S1 and S4 is a ring protection link
  • node S1 is the node to which the ring protection link belongs
  • node S4 is the ring protection link.
  • the node S1 blocks or opens the ring protection link through the blocking and opening of the control port 11.
  • the port blocking means that the blocked node port cannot complete the forwarding function of the protected data, but can still receive or send G. 8032v2 Ethernet ring protection protocol frame.
  • node S1 blocks port 11 to prevent protected data from passing through the ring protection link, that is, cannot be forwarded by node S1, and protected data between nodes S2 and S3.
  • the traffic communication path is only S2 ⁇ ->S3, and it is impossible to be S2 ⁇ ->S1 ⁇ ->S4 ⁇ ->S3. Therefore, the closed loop of the communication path is not generated in the ring network, and network storm is prevented.
  • the node to which the ring protection link belongs When there is no link fault in the Ethernet ring network, the node to which the ring protection link belongs periodically sends a ring protection link blocking protocol frame to notify other nodes that the ring protection link is in a blocked state, and the ring protection link blocking protocol frame includes sending Node node number, blocked port index number.
  • the other node After receiving the protocol frame, the other node extracts the node number and the blocked port index in the protocol frame, and compares the node number and the blocked port index number in the refresh record information corresponding to the receiving port saved by itself. If the two are different, the refresh record information corresponding to the receiving port is updated to the extracted node number and the blocked port index number.
  • the refresh record information corresponding to the port on each node ring stores the node number of the node to which the ring protection link belongs and the blocked port index number.
  • the node number of the refresh record information saved by the node S4 for the port 41 is 1 and the blocked port index number is 0; the node number of the refresh record information saved for the port 42 is 1 and the blocked port index number is 0.
  • Figure 2 is a schematic diagram of the operation when the Ethernet ring link fails.
  • nodes S2 and S3 detect a link failure.
  • the nodes S2 and S3 respectively block the port 22 and the port 31 connected to the faulty link, and send a link failure alarm (Signal Fail, SF) protocol frame to notify other nodes to perform protection switching.
  • the link failure alarm protocol frame is The node number of the sending node and the blocked port index number are included.
  • the node S1 to which the ring protection link belongs opens the blocked port 11 connected to the ring protection link after receiving the link failure alarm protocol frame.
  • the other nodes After receiving the link failure alarm protocol frame, the other nodes extract the node number and the blocked port index number in the protocol frame, and compare the node number of the refresh record information corresponding to the saved receiving port with the blocked port index number. If the two are not the same, the refresh record information corresponding to the receiving port is updated to the extracted node number and the blocked port index number, and the address table needs to be refreshed.
  • the node S4 when the node S4 receives the link failure alarm protocol frame sent by the S3 at the port 41 for the first time after the link failure, the node number included in the protocol frame is 3, and the blocked port index number is 0; It is found that the node number and the blocked port index number of the refresh record information originally saved for the port 41 are different, so the refresh record information of the port 41 is updated to the node number 3 and the blocked port index number 0, and the node S4 needs to refresh the address table. .
  • FIG 3 is a schematic diagram of the switchback operation of the Ethernet ring link failure recovery.
  • the nodes S2 and S3 detect the link recovery, the nodes S2 and S3 will send a No Request protocol frame, and after the node S1 to which the ring protection link belongs receives the No Request protocol frame, it starts to wait for recovery. Wait to Restore Timer (WTR Timer), after the WTR Timer expires, the node SI blocks the ring to protect the adjacent port 11 of the link, and sends a ring protection link blocking state protocol frame.
  • WTR Timer Restore Timer
  • the node SI blocks the ring to protect the adjacent port 11 of the link, and sends a ring protection link blocking state protocol frame.
  • the ring protection link neighbor node S4 refreshes the address table after receiving the ring protection link blocking state protocol frame, and blocks the ring protection link adjacent port 42, and deletes the refresh record information on port 41 and port 42; thus, when node S4 After receiving the subsequent ring protection link blocking state protocol frame, since there is no refresh record information on port 41 and port 42, node S4 needs to refresh the address table again.
  • FIG. 4 is a flowchart of preventing repeated refreshing of an Ethernet ring node address table according to an embodiment of the present invention, where the process includes the following steps:
  • Step 401 The Ethernet ring node changes the port state to a blocked state.
  • Step 402 Determine whether the own node is a ring protection link neighbor node, and if yes, proceed to step 403; otherwise, perform subsequent operations according to the prior art.
  • Step 403 Determine whether the content that triggers the blocking is a ring protection link blocking state protocol frame. If yes, go to step 404; otherwise, perform subsequent operations according to the prior art.
  • Step 404 The Ethernet ring network node determines to save the refresh record information corresponding to the ports on the two rings, and does not perform the action of deleting the refresh record information corresponding to the ports on the two rings.
  • the node in the Ethernet ring network changes the port to the blocking state, it needs to be judged if the node is a ring protection link neighbor node, and the blocking operation is due to the ring protection link neighbor node receiving the ring protection. If the link is blocked by the link protocol, the node saves the refresh record information corresponding to the ports on the two rings, but does not perform the action of deleting the refresh record information corresponding to the ports on the two rings. In this case, when the ring protection link neighbor node receives the subsequent ring protection link blocking state protocol frame, it is included in the ring protection link blocking state protocol frame that has been saved on the ring protection link neighbor node. The node number and the blocked port index number, so the address table will not be refreshed.
  • FIG. 4 can implement the situation shown in FIG. 5.
  • Figure 5 A schematic diagram of a switchback operation of an Ethernet ring link fault recovery according to an embodiment of the present invention.
  • the nodes S2 and S3 detect the link recovery, the nodes S2 and S3 will send a No Request protocol frame, and the node S1 to which the ring protection link belongs will start the WTR Timer after receiving the No Request protocol frame, after the WTR Timer expires.
  • the node S1 blocks the ring protection link adjacent port 11 and sends a ring protection link blocking state protocol frame.
  • the ring protection link neighbor node S4 refreshes the address table after receiving the ring protection link blocking state protocol frame, and the blocking ring protects the link adjacent port 42. After that, the node S4 determines that it is a neighboring node of the ring protection link by the judgment, and the blocking action is caused by receiving the ring protection link blocking state protocol frame, thus preserving the refresh record information on the port 41 and the port 42 without Delete it. After the ring protection link neighboring node S4 receives the subsequent ring protection link blocking state protocol frame, the node number, the blocked port index number, and the ring protection link blocking state corresponding to the refresh record information on the port 41 and the port 42 are blocked. The node number and the blocked port index number included in the protocol frame are the same. Therefore, the ring protection link neighbor node S4 does not refresh the address table, that is, the address table is repeatedly refreshed.
  • FIG. 6 is a diagram of a device for preventing an Ethernet ring node address table from being repeatedly refreshed according to an embodiment of the present invention.
  • the device includes a connected blocking trigger detecting unit and a refresh record information maintaining unit.
  • the blocking trigger detecting unit includes a connection that may exist. Node judgment unit of relationship, blocking cause judgment unit.
  • the node judging unit is configured to determine whether the node to which the node belongs is a ring protection link neighbor node when the node to which the node belongs changes to the blocking state, and notify the refresh record information maintenance unit when the judgment result is yes
  • the judgment may be implemented by querying the node attribute of the node to which the node belongs
  • the blocking cause determining unit is configured to determine whether the blocking operation is caused by receiving the ring protection link blocking state protocol frame, and notify the refresh when the determination result is yes.
  • the information maintenance unit is recorded, and the determination can be implemented by parsing the content of the data structure such as the received protocol frame.
  • the node judging unit and the blocking reason judging unit may also notify the refresh record information maintenance unit when the judgment result is no, as long as the refresh record information maintenance unit can be received according to the received The notification is normal for subsequent processing.
  • the node judging unit and the blocking reason judging unit may directly notify the refreshing record information maintenance unit of the judgment result of the self, or may separately notify the other party of the judgment result, so that the judgment result of the self becomes the counterpart for subsequent judgment.
  • the triggering condition for example, the node determining unit determines that the node to which the node belongs is a ring protection link neighboring node, and notifies the judgment result to the blocking reason judging unit; the blocking reason judging unit is triggered by the notification from the node judging unit, and then judges The content of the triggering blocking is determined to be the ring protection link blocking state protocol frame, and then the result of the determination and the judgment result from the node determining unit are sent to the refresh record information maintenance unit.
  • the unit After receiving the judgment result from the node judging unit and the blocking reason judging unit, if the judgment result is that the belonging node is a ring protection link neighbor node, and the content that triggers the blocking is a ring protection link blocking state protocol frame, refreshing the record information maintenance
  • the unit determines that it is necessary to save the refresh record information corresponding to the ports on the two rings, and then performs the save operation without performing the action of deleting the refresh record information corresponding to the ports on the two rings.
  • the method for preventing the Ethernet ring node address table from being repeatedly refreshed in the Ethernet ring network back-cut scenario can effectively solve the problem of repeatedly refreshing the address table of the ring protection link neighbor node in the Ethernet ring network back-cut scenario. , reducing the traffic broadcast of the Ethernet ring network during protection switching, improving the switching efficiency.

Landscapes

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

Description

防止以太环网节点地址表重复刷新的方法和装置 技术领域
本发明涉及以太网技术， 具体涉及防止以太环网节点地址表重复刷新 的方法和装置。 背景技术
随着以太网向着多业务承载方向的发展， 特别是一些业务对网络的可 靠性、 实时性要求越来越高， 以太网广泛釆用了环形的组网， 从而提高了 网络的可靠性。 并且在这种环形组网的保护方案中， 通常要求快速保护倒 换能达到 50ms以内。 目前， 这种快速保护倒换的技术可以基于国际电信联 盟 ( International Telecommunication Union, ITU-T ) 的 G.8032v2协议来实 现。
基于上述 G.8032v2协议， 为环形拓朴以太网的以太层定义了自动保护 切换协议与机制。 这种网络保护方法适用于环形拓朴的以太网， 其实现的 主要流程包括： 在环形拓朴以太网中， 选择一段链路为环保护链路 （Ring Protection Link, RPL ), 环保护链路上的两个相邻节点用于控制环保护链路 的阻塞或者打开， 其中一个节点称为环保护链路所属节点 （RPL Owner Node ), 另外一个节点称为环保护链路邻居节点 （ RPL Neighbour Node ), 环保护链路中相邻两个节点上相对于环保护链路而言的相邻端口称为环保 护链路相邻端口 （PRL Port )。
当以太环网的链路都无故障时， 环保护链路的两个相邻节点阻塞环保 护链路相邻端口， 防止被保护数据从环保护链路上通过； 这样， 以太环网 上任何两个节点之间只有惟一的通信路径， 因此以太环网中不会产生通信 路径的闭环， 防止了闭环和网络风暴。 当以太环网的链路出现故障时， 如 果该故障链路不是环保护链路， 则与故障链路相邻的节点阻塞故障端口， 与环保护链路相邻的两个节点打开两个环保护链路相邻端口， 使被保护数 据可以从环保护链路上通过， 因而环保护链路上任何两个节点之间产生了 新的通信路径， 保障了通信路径的重新连通， 提高了网络的可靠性。
在以太环网的切换过程中， 数据流量的通信路径需要发生变化， 由于 每个节点记录的地址表信息在数据流量的通信路径发生变化后都可能不再 适用， 因此每个节点有可能需要刷新地址表， 具体动作为删除环上端口的 地址条目。 在 G.8032v2协议中， 节点所发送的以太环网保护协议帧中包括 自身的节点号和阻塞端口索引号； 其他节点接收到该协议帧后， 提取出协 议帧中的节点号和阻塞端口索引号， 并与针对接收端口所保存的刷新记录 信息的节点号和阻塞端口索引号进行对比， 如果两者不相同则将接收端口 对应的刷新记录信息更新为提取出来的节点号和阻塞端口索引号。 另外， 如果协议帧中的节点号和阻塞端口索引号与接收端口的对端端口所对应的 刷新记录信息的节点号和阻塞端口索引号不同， 则该节点还有可能需要刷 新地址表； 再有， 节点在阻塞端口时， 还要将两个环上端口所对应的刷新 记录信息的节点号和阻塞端口索引号删除。
以上这种以太环网地址表的刷新方案虽然保障了以太环网在切换时能 够快速的删除错误的地址条目， 但是也带来了切换时重复刷新地址表的问 题。 例如， 在链路故障恢复的回切过程中， 环保护链路所属节点阻塞环保 护链路相邻端口后， 发送表现形式为无请求（ No Request )的环保护链路阻 塞状态 （RPL Blocked, NRRB )协议帧。 环保护链路邻居节点收到这个协 议帧后， 由于协议帧中包括的节点号和阻塞端口索引号与接收端口所对应 的刷新记录信息的节点号和阻塞端口索引号不相同， 因此环保护链路邻居 节点将接收端口所对应的刷新记录信息更新为收到的节点号和阻塞端口索 引号； 并且由于收到的协议帧中的节点号和阻塞端口索引号与接收端口的 对端端口所对应的刷新记录信息的节点号和阻塞端口索引号也不相同， 因 此环保护链路邻居节点根据以太环网的地址刷新原理刷新地址表。
接着， 环保护链路邻居节点还要阻塞环保护链路相邻节点， 并将自身 两个环上端口所对应的刷新记录信息的节点号和阻塞端口索引号删除。 由 于环保护链路所属节点会持续发送环保护链路阻塞状态协议帧， 因此环保 护链路邻居节点收到后续的环保护链路阻塞状态协议帧后， 会因为自身两 个端口都没有刷新记录信息而再刷新一次地址表， 而这次地址表刷新操作 实际上是不必要的， 并且该地址表刷新操作很有可能因涉及节点或用户过 多而导致网络通信量瞬间爆发， 不利于网络资源的有效利用以及用户业务 的正常开展。 发明内容
有鉴于此， 本发明的主要目的在于提供一种防止以太环网节点地址表 重复刷新的方法和装置， 以解决在以太环网回切场景下， 环保护链路邻居 节点重复刷新地址表的问题。
为达到上述目的， 本发明的技术方案是这样实现的：
防止以太环网节点地址表重复刷新的方法， 以太环网节点的端口状态 改变为阻塞状态后， 该方法包括：
判断所述以太环网节点是否为环保护链路邻居节点、 以及触发阻塞的 内容是否为环保护链路阻塞状态协议帧， 在判断结果为是时， 所述以太环 网节点确定保存自身两个环上端口所对应的刷新记录信息。
判断所述以太环网节点是否为环保护链路邻居节点的过程， 通过查询 所述以太环网节点的节点属性实现。
判断触发阻塞的内容是否为环保护链路阻塞状态协议帧的过程， 通过 解析收到的数据结构的内容实现。
进一步包括： 判断所述以太环网节点是否为环保护链路邻居节点的判 断结果为否， 按照现有技术执行后续操作。
进一步包括： 判断触发阻塞的内容是否为环保护链路阻塞状态协议帧 的判断结果为否， 按照现有技术执行后续操作。
所述刷新记录信息包括： 节点号和阻塞端口索引号。
该装置包括相连的阻塞触发检测单元、 刷新记录信息维护单元； 其中， 在以太环网节点的端口状态改变为阻塞状态后，
所述阻塞触发检测单元， 用于判断自身所属以太环网节点是否为环保 护链路邻居节点、 以及触发阻塞的内容是否为环保护链路阻塞状态协议帧， 并将判断结果通知给所述刷新记录信息维护单元；
所述刷新记录信息维护单元， 用于在收到的所述判断结果为是时， 确 定保存自身所属以太环网节点的两个环上端口所对应的刷新记录信息。
所述阻塞触发检测单元包括节点判断单元、 阻塞原因判断单元； 其中， 所述节点判断单元， 用于判断自身所属以太环网节点是否为环保护链 路邻居节点， 并生成能够通知刷新记录信息维护单元的判断结果；
所述阻塞原因判断单元， 用于判断所述阻塞操作是否是由于收到环保 护链路阻塞状态协议帧导致的， 并生成能够通知刷新记录信息维护单元的 判断结果。
所述节点判断单元、 阻塞原因判断单元， 分别用于将生成的判断结果 通知给刷新记录信息维护单元； 或者，
所述节点判断单元与阻塞原因判断单元之间存在连接关系， 分别用于 将判断结果通知给对方， 使得自身的判断结果成为对方进行后续判断的触 发条件。
所述刷新记录信息包括： 节点号和阻塞端口索引号。
可见， 本发明方法和装置， 均可有效解决在以太环网回切场景下环保 护链路邻居节点重复刷新地址表的问题， 减少了以太环网在保护倒换时的 流量广播， 提高了切换效率。 附图说明
图 1为以太环网链路无故障时的运行示意图；
图 2为以太环网链路出现故障时的运行示意图；
图 3为以太环网链路故障恢复的回切运行示意图；
图 4为本发明实施例的防止以太环网节点地址表重复刷新流程图； 图 5为本发明实施例的以太环网链路故障恢复的回切运行示意图； 图 6为本发明实施例的防止以太环网节点地址表重复刷新装置图。 具体实施方式
参见图 1 , 图 1为以太环网链路无故障时的运行示意图。 图 1中， 节点 Sl、 S2、 S3和 S4组成了以太环网， 节点 S1和 S4之间的链路为环保护链 路， 节点 S1为环保护链路所属节点， 节点 S4为环保护链路邻居节点， 节 点 S1通过控制端口 11 的阻塞和打开使环保护链路阻塞或者打开， 这里的 端口阻塞是指被阻塞的节点端口不能完成被保护数据的转发功能， 但是仍 然能够接收或者发送 G.8032v2的以太环网保护协议帧。
当图 1所示的以太环网链路无故障时， 节点 S1阻塞端口 11 , 防止被保 护数据从环保护链路上通过， 即不能被节点 S1转发， 节点 S2和 S3之间的 被保护数据流量通信路径仅为 S2<—>S3 , 而不可能是 S2<— >S1<— >S4< ->S3 , 因此环网中不会产生通信路径的闭环， 防止了网络风暴。
在以太环网中无链路故障时， 环保护链路所属节点周期性发送环保护 链路阻塞协议帧以通知其他节点环保护链路处于阻塞状态， 该环保护链路 阻塞协议帧中包括发送节点的节点号、 阻塞端口索引号。 其他节点收到该 协议帧后， 提取出协议帧中的节点号和阻塞端口索引， 和自身保存的接收 端口所对应的刷新记录信息中的节点号和阻塞端口索引号进行对比， 如果 两者不相同则将接收端口所对应的刷新记录信息更新为提取出来的所述节 点号和阻塞端口索引号。
在以太环网稳定时， 各个节点环上端口所对应的刷新记录信息都保存 了环保护链路所属节点的节点号和阻塞端口索引号。 例如， 节点 S4针对端 口 41所保存的刷新记录信息的节点号为 1 , 阻塞端口索引号为 0; 针对端 口 42所保存的刷新记录信息的节点号为 1 , 阻塞端口索引号为 0。
参见图 2, 图 2为以太环网链路出现故障时的运行示意图。 图 2中， 假 设节点 S2和 S3检测到链路故障。 那么， 首先节点 S2和 S3分别阻塞与故 障链路相连的端口 22和端口 31 , 并发送链路故障告警 （Signal Fail, SF ) 协议帧通知其他节点进行保护切换， 该链路故障告警协议帧中包括了发送 节点的节点号、 阻塞端口索引号； 接着， 环保护链路所属节点 S1在收到链 路故障告警协议帧后打开阻塞的与环保护链路相连的端口 11。
其他各个节点收到上述链路故障告警协议帧后， 提取出该协议帧中的 节点号和阻塞端口索引号， 与保存的接收端口所对应的刷新记录信息的节 点号和阻塞端口索引号进行对比， 如果两者不相同则将接收端口所对应的 刷新记录信息更新为提取出来的所述节点号和阻塞端口索引号， 并且还需 要刷新地址表。
例如， 节点 S4在链路故障后第一次在端口 41接收到 S3发送的链路故 障告警协议帧时， 该协议帧中包括的节点号为 3 , 阻塞端口索引号为 0; 节 点 S4通过对比发现与原来针对端口 41所保存的刷新记录信息的节点号和 阻塞端口索引号不同， 因此将端口 41的刷新记录信息更新为节点号 3和阻 塞端口索引号 0, 并且节点 S4还需要刷新地址表。
参见图 3 , 图 3为以太环网链路故障恢复的回切运行示意图。 图 3中， £设节点 S2和 S3检测到链路恢复， 则节点 S2和 S3会发送 No Request协 议帧， 环保护链路所属节点 S1收到 No Request协议帧后， 启动等待恢复定 时器（ Wait to Restore Timer, WTR Timer ), 在 WTR Timer超时后由节点 SI 阻塞环保护链路相邻端口 11 , 并发送环保护链路阻塞状态协议帧。 环保护 链路邻居节点 S4收到环保护链路阻塞状态协议帧后刷新地址表， 并且阻塞 环保护链路相邻端口 42, 删除端口 41和端口 42上的刷新记录信息； 这样， 当节点 S4收到后续的环保护链路阻塞状态协议帧后， 由于端口 41和端口 42上已不存在刷新记录信息， 因此节点 S4还需要再刷新一次地址表。
在实际应用中， 可以进行如图 4所示操作， 以避免上述的 S4再刷新一 次地址表的情况。 参见图 4, 图 4为本发明实施例的防止以太环网节点地址 表重复刷新流程图， 该流程包括以下步骤：
步骤 401： 以太环网节点将端口状态改变为阻塞状态。
步骤 402: 判断自身节点是否为环保护链路邻居节点， 如果是， 进入步 骤 403; 否则， 按照现有技术执行后续操作。
步骤 403: 判断触发阻塞的内容是否为环保护链路阻塞状态协议帧， 如 果是， 进入步骤 404; 否则， 按照现有技术执行后续操作。
步骤 404:所述以太环网节点确定保存自身两个环上端口所对应的刷新 记录信息， 而不执行删除两个环上端口对应的刷新记录信息的动作。
由图 4可见， 当以太环网中的节点将端口改变为阻塞状态时， 需要进 行判断， 如果该节点为环保护链路邻居节点， 且阻塞操作是由于环保护链 路邻居节点收到环保护链路阻塞状态协议帧导致的， 则该节点保存自身两 个环上端口所对应的刷新记录信息， 而不执行删除两个环上端口对应的刷 新记录信息的动作。 在这种情况下， 当环保护链路邻居节点收到后续的环 保护链路阻塞状态协议帧时， 由于在环保护链路邻居节点上已经保存了环 保护链路阻塞状态协议帧中所包括的节点号和阻塞端口索引号， 因此不会 重新刷新地址表。
在具体应用时， 图 4所示流程能够实现图 5所示情况。 参见图 5 , 图 5 为本发明实施例的以太环网链路故障恢复的回切运行示意图。 图 5 中， 假 设节点 S2和 S3检测到链路恢复， 则节点 S2和 S3会发送 No Request协议 帧，环保护链路所属节点 S1收到 No Request协议帧后启动 WTR Timer,在 WTR Timer超时后由节点 S1阻塞环保护链路相邻端口 11 ,并发送环保护链 路阻塞状态协议帧。
环保护链路邻居节点 S4 收到环保护链路阻塞状态协议帧后刷新地址 表， 并且阻塞环保护链路相邻端口 42。 之后， 节点 S4通过判断确定自身为 环保护链路相邻节点， 且阻塞动作是由于收到环保护链路阻塞状态协议帧 导致的， 因此保留端口 41和端口 42上的刷新记录信息， 而不予以删除。 当环保护链路邻居节点 S4收到后续的环保护链路阻塞状态协议帧后， 由于 端口 41、端口 42上所对应的刷新记录信息的节点号、 阻塞端口索引号与环 保护链路阻塞状态协议帧中所包括的节点号、 阻塞端口索引号相同， 因此 环保护链路邻居节点 S4不会重新刷新地址表，即防止了地址表的重复刷新。
为了顺利实现以上处理过程， 可以进行如图 6所示的设置。 参见图 6, 图 6为本发明实施例的防止以太环网节点地址表重复刷新装置图， 该装置 包括相连的阻塞触发检测单元、 刷新记录信息维护单元； 其中， 阻塞触发 检测单元包括可以存在相连关系的节点判断单元、 阻塞原因判断单元。
在具体应用时， 节点判断单元用于在自身所属节点将端口改变为阻塞 状态时， 判断自身所属节点是否为环保护链路邻居节点， 并在判断结果为 是时通知刷新记录信息维护单元， 该判断可以通过查询自身所属节点的节 点属性等信息实现； 阻塞原因判断单元用于判断所述阻塞操作是否是由于 收到环保护链路阻塞状态协议帧导致的， 并在判断结果为是时通知刷新记 录信息维护单元， 该判断可以通过解析收到的协议帧等数据结构的内容实 现。 当然， 节点判断单元、 阻塞原因判断单元同样可以在判断结果为否时 通知刷新记录信息维护单元， 只要刷新记录信息维护单元能够根据收到的 通知正常进行后续处理即可。
需要说明的是， 节点判断单元和阻塞原因判断单元可以分别将自身的 判断结果直接通知给刷新记录信息维护单元， 也可以分别将判断结果通知 给对方， 使得自身的判断结果成为对方进行后续判断的触发条件， 如： 节 点判断单元通过判断确定自身所属节点是环保护链路邻居节点， 并将该判 断结果通知给阻塞原因判断单元； 阻塞原因判断单元被来自节点判断单元 的通知触发， 进而通过判断确定触发阻塞的内容是环保护链路阻塞状态协 议帧， 之后将自身的判断结果以及来自节点判断单元的判断结果发送给刷 新记录信息维护单元。
收到来自节点判断单元和阻塞原因判断单元的判断结果后， 如果判断 结果分别为所属节点是环保护链路邻居节点、 以及触发阻塞的内容是环保 护链路阻塞状态协议帧， 刷新记录信息维护单元则确定需要保存自身两个 环上端口所对应的刷新记录信息， 进而执行该保存操作， 而不执行删除两 个环上端口对应的刷新记录信息的动作。
综上所述可见， 无论是方法还是装置， 本发明防止以太环网节点地址 表重复刷新的技术， 均可有效解决在以太环网回切场景下环保护链路邻居 节点重复刷新地址表的问题， 减少了以太环网在保护倒换时的流量广播， 提高了切换效率。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围， 凡在本发明的精神和原则之内所作的任何修改、 等同替换和改进 等， 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种防止以太环网节点地址表重复刷新的方法， 其特征在于， 该方 法包括：
以太环网节点的端口状态改变为阻塞状态后， 判断所述以太环网节点 是否为环保护链路邻居节点、 以及触发阻塞的内容是否为环保护链路阻塞 状态协议帧， 在判断结果均为是时， 所述以太环网节点确定保存自身两个 环上端口所对应的刷新记录信息。
2、 根据权利要求 1所述的方法， 其特征在于， 判断所述以太环网节点 是否为环保护链路邻居节点的过程， 通过查询所述以太环网节点的节点属 性实现。
3、 根据权利要求 1所述的方法， 其特征在于， 判断触发阻塞的内容是 否为环保护链路阻塞状态协议帧的过程， 通过解析收到的数据结构的内容 实现。
4、 根据权利要求 1至 3任一项所述的方法， 其特征在于， 该方法进一 步包括： 判断所述以太环网节点是否为环保护链路邻居节点的判断结果为 否， 按照现有技术执行后续操作。
5、 根据权利要求 1至 3任一项所述的方法， 其特征在于， 该方法进一 步包括： 判断触发阻塞的内容是否为环保护链路阻塞状态协议帧的判断结 果为否， 按照现有技术执行后续操作。
6、根据权利要求 1所述的方法，其特征在于， 所述刷新记录信息包括： 节点号和阻塞端口索引号。
7、 一种防止以太环网节点地址表重复刷新的装置， 其特征在于， 该装 置包括相连的阻塞触发检测单元、 刷新记录信息维护单元； 其中，
所述阻塞触发检测单元， 用于在以太环网节点的端口状态改变为阻塞 状态后， 判断自身所属以太环网节点是否为环保护链路邻居节点、 以及触 发阻塞的内容是否为环保护链路阻塞状态协议帧， 并将判断结果通知给所 述刷新记录信息维护单元；
所述刷新记录信息维护单元， 用于在收到的所述判断结果均为是时， 确定保存自身所属以太环网节点的两个环上端口所对应的刷新记录信息。
8、 根据权利要求 7所述的装置， 其特征在于， 所述阻塞触发检测单元 包括节点判断单元、 阻塞原因判断单元； 其中，
所述节点判断单元， 用于判断自身所属以太环网节点是否为环保护链 路邻居节点， 并生成能够通知刷新记录信息维护单元的判断结果；
所述阻塞原因判断单元， 用于判断所述阻塞操作是否是由于收到环保 护链路阻塞状态协议帧导致的， 并生成能够通知刷新记录信息维护单元的 判断结果。
9、 根据权利要求 8所述的装置， 其特征在于：
所述节点判断单元、 阻塞原因判断单元， 分别用于将生成的判断结果 通知给刷新记录信息维护单元； 或者，
所述节点判断单元与阻塞原因判断单元之间存在连接关系， 分别用于 将判断结果通知给对方， 使得自身的判断结果成为对方进行后续判断的触 发条件。
10、 根据权利要求 7所述的装置， 其特征在于， 所述刷新记录信息包 括： 节点号和阻塞端口索引号。
PCT/CN2010/071700 2010-02-05 2010-04-12 防止以太环网节点地址表重复刷新的方法和装置 WO2011094971A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2012551465A JP5491644B2 (ja) 2010-02-05 2010-04-12 イーサネットリングネットワークノードのアドレステーブルにおける反復リフレッシュの防止方法及び防止装置
KR1020127021429A KR101402532B1 (ko) 2010-02-05 2010-04-12 이더넷 링 네트워크 노드 주소 테이블이 반복 리프레시 되는 것을 방지하는 방법 및 장치
US13/576,656 US8948002B2 (en) 2010-02-05 2010-04-12 Method and device for preventing repeated refreshing of address table of Ethernet ring network node
EP10845056.0A EP2533470B1 (en) 2010-02-05 2010-04-12 Method and equipment for preventing repeated refreshing of ethernet ring node address table

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010107236.7 2010-02-05
CN201010107236.7A CN102148734B (zh) 2010-02-05 2010-02-05 防止以太环网节点地址表重复刷新的方法和装置

Publications (1)

Publication Number Publication Date
WO2011094971A1 true WO2011094971A1 (zh) 2011-08-11

Family

ID=44354906

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/071700 WO2011094971A1 (zh) 2010-02-05 2010-04-12 防止以太环网节点地址表重复刷新的方法和装置

Country Status (6)

Country Link
US (1) US8948002B2 (zh)
EP (1) EP2533470B1 (zh)
JP (1) JP5491644B2 (zh)
KR (1) KR101402532B1 (zh)
CN (1) CN102148734B (zh)
WO (1) WO2011094971A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104125148A (zh) * 2014-08-12 2014-10-29 烽火通信科技股份有限公司 三层以太网环的缺陷感知及路由条目刷新方法

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102546410A (zh) * 2011-12-30 2012-07-04 北京格林伟迪科技有限公司 一种以太环网的保护方法
CN104869057B (zh) * 2014-02-21 2019-03-01 中兴通讯股份有限公司 开放流交换机优雅重启处理方法、装置及开放流控制器
JP2016058883A (ja) 2014-09-09 2016-04-21 日立金属株式会社 中継システムおよび中継装置
CN108900403B (zh) * 2018-06-12 2021-02-26 瑞斯康达科技发展股份有限公司 一种以太环网保护配置的方法和装置
CN113518024B (zh) * 2021-07-12 2022-07-05 普联技术有限公司 一种节点的地址表刷新方法、装置、终端和存储介质
CN115714698B (zh) * 2022-09-26 2024-04-16 重庆长安汽车股份有限公司 车载以太网的环网通信方法、装置、车辆及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6496519B1 (en) * 1998-08-27 2002-12-17 Nortel Networks Limited Frame based data transmission over synchronous digital hierarchy network
CN101163079A (zh) * 2007-11-13 2008-04-16 中兴通讯股份有限公司 以太环网保护中转发数据库刷新的方法
CN101217443A (zh) * 2008-01-21 2008-07-09 杭州华三通信技术有限公司 一种以太环网保护方法和传输节点

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6766482B1 (en) 2001-10-31 2004-07-20 Extreme Networks Ethernet automatic protection switching
JP4020753B2 (ja) 2002-10-25 2007-12-12 富士通株式会社 リング切替方法
JP2005269059A (ja) 2004-03-17 2005-09-29 Fujitsu Ltd データ中継装置、データ中継方法およびデータ中継プログラム
CN100341299C (zh) * 2004-09-28 2007-10-03 中兴通讯股份有限公司 一种在弹性分组环上提供端到端业务的方法
JP4848254B2 (ja) * 2006-11-29 2011-12-28 アラクサラネットワークス株式会社 リングネットワークを構成する装置
CN101068185B (zh) * 2007-06-19 2012-06-06 中兴通讯股份有限公司 以太环网报文处理方法及应用该方法的以太环网保护系统
CN101127675A (zh) * 2007-09-25 2008-02-20 中兴通讯股份有限公司 以太环网系统主节点初始化方法
KR101223716B1 (ko) * 2008-04-22 2013-01-18 한국전자통신연구원 이더넷 링 망에서의 강제 보호 절체 방법
US9042216B2 (en) * 2008-06-20 2015-05-26 Alcatel Lucent Loop prevention mechanism for ethernet ring protection
US8149692B2 (en) * 2008-12-31 2012-04-03 Ciena Corporation Ring topology discovery mechanism
US20100290340A1 (en) * 2009-05-15 2010-11-18 Electronics And Telecommunications Research Institute Method for protection switching
CN101640622B (zh) * 2009-09-07 2012-05-23 中兴通讯股份有限公司 一种以太环网保护方法及传输节点

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6496519B1 (en) * 1998-08-27 2002-12-17 Nortel Networks Limited Frame based data transmission over synchronous digital hierarchy network
CN101163079A (zh) * 2007-11-13 2008-04-16 中兴通讯股份有限公司 以太环网保护中转发数据库刷新的方法
CN101217443A (zh) * 2008-01-21 2008-07-09 杭州华三通信技术有限公司 一种以太环网保护方法和传输节点

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104125148A (zh) * 2014-08-12 2014-10-29 烽火通信科技股份有限公司 三层以太网环的缺陷感知及路由条目刷新方法
CN104125148B (zh) * 2014-08-12 2017-02-15 烽火通信科技股份有限公司 三层以太网环的缺陷感知及路由条目刷新方法

Also Published As

Publication number Publication date
US20130028076A1 (en) 2013-01-31
EP2533470A4 (en) 2014-12-24
CN102148734A (zh) 2011-08-10
JP2013519265A (ja) 2013-05-23
KR101402532B1 (ko) 2014-05-30
JP5491644B2 (ja) 2014-05-14
EP2533470B1 (en) 2017-12-06
US8948002B2 (en) 2015-02-03
KR20120106898A (ko) 2012-09-26
EP2533470A1 (en) 2012-12-12
CN102148734B (zh) 2015-10-21

Similar Documents

Publication Publication Date Title
US8208369B2 (en) Ethernet ring system and a master node and an initialization method thereof
US9270485B2 (en) Method for ethernet ring protection
US8483050B2 (en) Method and apparatus for ethernet ring protection
WO2011094971A1 (zh) 防止以太环网节点地址表重复刷新的方法和装置
CN107547383B (zh) 路径检测方法及装置
EP2117176B1 (en) Method for implementing intersecting ring network with arbitrary topology, node and intersecting ring network
EP2569904B1 (en) A ring node, an ethernet ring and methods for loop protection in an ethernet ring
WO2010045832A1 (zh) 用于以太环网的链路聚合组的保护方法及装置
WO2009111969A1 (zh) 以太环网中边缘端口阻塞的方法、以太环网系统和设备
US20100254257A1 (en) Method for processing failure of slave port of master node in ethernet ring network system
WO2013182116A1 (zh) 保护以太环网节点间连通性的控制方法、装置及第一节点
CN102238067B (zh) 一种快速环网保护协议环上的切换方法和装置
CN102035710B (zh) 一种阻塞端口信息更新的方法及系统
US8681604B2 (en) Address refresh method and system
US8811157B2 (en) Protection switching method and system for ethernet dual-homed link
CN101997748B (zh) 无虚拟通道的子环控制信道阻塞协议报文的方法和系统
WO2012068866A1 (zh) 一种以太环网中刷新mac的方法及系统
WO2015135280A1 (zh) 一种实现按需智能拨号的方法、系统和接入路由器
WO2010099685A1 (zh) 控制以太网地址表刷新次数的方法
CN101938395B (zh) 一种以太环网的单环地址刷新方法及系统
CN107547330B (zh) 一种传输业务数据的方法和节点设备
WO2011127736A1 (zh) 以太环网节点中保存信息的维护方法和装置
WO2011094970A1 (zh) 一种以太网保护中阻塞端口的方法和系统
CN112312497B (zh) 一种业务快速切换方法及装置
WO2011147176A1 (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: 10845056

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012551465

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 13576656

Country of ref document: US

ENP Entry into the national phase

Ref document number: 20127021429

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2010845056

Country of ref document: EP