WO2015117465A1 - 环形网络中fdb刷新方法、装置、节点及*** - Google Patents

环形网络中fdb刷新方法、装置、节点及*** Download PDF

Info

Publication number
WO2015117465A1
WO2015117465A1 PCT/CN2014/091921 CN2014091921W WO2015117465A1 WO 2015117465 A1 WO2015117465 A1 WO 2015117465A1 CN 2014091921 W CN2014091921 W CN 2014091921W WO 2015117465 A1 WO2015117465 A1 WO 2015117465A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
fdb
ring network
address information
link
Prior art date
Application number
PCT/CN2014/091921
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 中兴通讯股份有限公司
Publication of WO2015117465A1 publication Critical patent/WO2015117465A1/zh

Links

Images

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 communications, and in particular to a FDB refresh method, device, node and system in a ring network.
  • the ring network protection protocol (for example, the ERPS protocol described in G.8032) blocks the Ring Protection Link (RPL) when the network is normal. After detecting a link fault, the faulty link is blocked. RPL link for business protection and fast switching.
  • RPL Ring Protection Link
  • FIG. 1 is a schematic diagram of service flow switching before and after ring network switching in the related art.
  • the ring network protocol status is switched (when the network is faulty or the fault is rectified)
  • the Spanning Tree Protocol (STP) status (STP status) of the ring port is re-set according to the protocol.
  • refreshing the MAC address forwarding table Formwarding DateBase, FDB for short
  • the current mechanism for refreshing the FDB is such that when the ring network is switched, the FDB action of the unnecessary and redundant refresh nodes is performed, and in the live network environment, due to the large number of FDB table entries, the performance of the switch chip may be limited.
  • the situation where the service switching interruption time exceeds the standard affects the user experience.
  • the invention provides a FDB refreshing method, device, node and system in a ring network, so as to solve at least the problem that the nodes existing in the related technology perform unnecessary FDB refreshing actions, affect the ring network switching performance, and reduce the user experience.
  • a method for refreshing an address forwarding table FDB in a ring network including: determining whether the first pair is based on address information of a node on a faulty link on a ring network or address information of a node on a backup link
  • the FDB of the node is refreshed, wherein the first node is a node other than the uplink node in the ring network, and the uplink node is a node connected to the upstream device by the ring network; In case, the FDB of the first node is refreshed.
  • the method further includes: determining If the result is no, the refresh operation of the FDB of the first node is abandoned.
  • determining whether to refresh the FDB of the first node according to the address information of the node on the faulty link on the ring network or the address information of the node on the backup link includes: occurring on the ring network link In the event of a failure, determining whether the path information of the node on the failed link is included in the path information of the first node in the normal state, wherein the path information includes the first
  • the purpose of starting the node is the address information of each node except the first node sequentially included on the path of the uplink node; if the determination result is yes, determining the FDB for the first node Refresh.
  • determining whether to refresh the FDB of the first node according to the address information of the node on the faulty link on the ring network or the address information of the node on the backup link includes: determining, when the link fault is eliminated, determining Whether the path information of the node on the backup link is included in the path information including the address information of the uplink node in the fault state of the first node, where the path information includes the destination from the first node And determining address information of each node except the first node sequentially included in the path of the uplink node; if the determination result is yes, determining to refresh the FDB of the first node.
  • an address forwarding table FDB refreshing apparatus in a ring network comprising: a determining module configured to: according to address information of a node on a faulty link on a ring network or a node on a backup link The address information is used to determine whether the FDB of the first node is refreshed, where the first node is a node other than the uplink node in the ring network, and the uplink node is a node connected to the upstream device by the ring network. And a refreshing module configured to refresh the FDB of the first node if the determination result of the determining module is YES.
  • the FDB refreshing device further includes: a discarding module, configured to abandon a refresh operation of the FDB of the first node if the determining result of the determining module is negative.
  • a discarding module configured to abandon a refresh operation of the FDB of the first node if the determining result of the determining module is negative.
  • the determining module includes: a first determining unit, configured to determine, when the ring network link is faulty, whether the path information including the uplink node address information in the normal state of the first node is included The address information of the node on the faulty link, where the path information includes each node except the first node sequentially included on the path of the uplink node starting from the first node
  • the first determining unit is configured to determine to refresh the FDB of the first node if the first determining unit determines that the result is yes.
  • the determining module includes: a second determining unit, configured to determine, when the link fault is eliminated, whether the path information including the uplink node address information in the fault state of the first node includes the backup chain The address information of the node on the road, wherein the path information includes address information of each node except the first node that is sequentially included on the path of the uplink node from the first node;
  • the second determining unit is configured to determine to refresh the FDB of the first node if the determination result of the second determining unit is YES.
  • a node comprising the apparatus of any of the above.
  • an address forwarding table FDB refresh system in a ring network comprising one or more of the nodes described above.
  • the present invention it is determined whether to refresh the FDB of the first node according to the address information of the node on the faulty link on the ring network or the address information of the node on the backup link, wherein the first node is the ring a node other than the uplink node in the network, the uplink node is a node connected to the upstream device by the ring network; and if the determination result is yes, the method for refreshing the FDB of the first node.
  • FIG. 1 is a schematic diagram of service flow switching before and after ring network switching in the related art
  • FIG. 2 is a flowchart of an FDB refresh method in a ring network according to an embodiment of the present invention
  • FIG. 3 is a structural block diagram of an FDB refresh apparatus in a ring network according to an embodiment of the present invention
  • FIG. 4 is a block diagram showing a preferred structure of an FDB refreshing apparatus in a ring network according to an embodiment of the present invention
  • FIG. 5 is a structural block diagram 1 of a determining module 32 in an FDB refreshing apparatus in a ring network according to an embodiment of the present invention
  • FIG. 6 is a block diagram 2 of a structure of a determining module 32 in an FDB refreshing apparatus in a ring network according to an embodiment of the present invention
  • FIG. 7 is a structural block diagram of a node according to an embodiment of the present invention.
  • FIG. 8 is a structural block diagram of an FDB refresh system in a ring network according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a trace in a normal working state according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a trace in a fault state according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of an FDB refreshing method in a ring network according to an embodiment of the present invention. As shown in FIG. 2, the process includes the following steps:
  • Step S202 determining whether to refresh the FDB of the first node according to the address information of the node on the faulty link on the ring network or the address information of the node on the backup link, where the first node is in addition to the uplink in the ring network.
  • step S204 if the determination result is YES, the FDB of the first node is refreshed.
  • the uplink node is a node connected to the upstream device by the ring network; if the determination result is yes, the method for refreshing the FDB of the first node is implemented according to the faulty link.
  • the address information of the node or the address information of the node on the backup link determines whether the FDB of the first node needs to be refreshed, and the node existing in the related art performs an unnecessary FDB refresh operation, affecting the ring network switching performance and reducing The user experience problem, and then achieve the optimization of the FDB refresh mechanism, reduce unnecessary refresh processing, and improve the performance of ring network switching performance.
  • the The refresh operation of the FDB of one node can further realize the FDB of the node refreshed only when the node FDB needs to be refreshed.
  • the method of determining whether to refresh the FDB of the first node according to the address information of the node on the faulty link on the ring network or the address information of the node on the backup link may be as follows: when the ring network link fails, it is determined. Whether the path information of the node on the faulty link includes the path information of the node on the faulty link in the normal state of the first node, wherein the path information includes the destination node starting from the first node. The address information of each node except the first node is sequentially included in the path; if the determination result is YES, it is determined that the FDB of the first node is refreshed. That is, when each link of the ring network is normal, each node can store its own path information. When a link failure occurs in the ring network, it can be determined whether the path information in the normal state stored by the node includes the faulty link. The address information of the node involved, in the case of inclusion, refreshes the FDB of the node.
  • the following method may be used to determine whether to refresh the FDB of the first node according to the address information of the node on the faulty link on the ring network or the address information of the node on the backup link: when the link fault is eliminated, the first node is determined. Whether the path information of the node on the backup link is included in the path information of the address information of the uplink node in the fault state, wherein the path information includes the order sequentially included on the path of the uplink node starting from the first node. The address information of each node except the first node; if the determination result is YES, it is determined to refresh the FDB of the first node.
  • each node when the network fails, the backup link is connected, and each node can store the node path information in the fault state.
  • the fault of the ring network When the fault of the ring network is eliminated, it can be determined that the node includes the uplink node in the fault state. Whether the address information of the node involved in the backup link is included in the path information of the address information, and if it is included, the FDB of the node is refreshed.
  • an address forwarding table FDB refreshing device is also provided in the ring network, and the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term “module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 3 is a structural block diagram of an FDB refreshing apparatus in a ring network according to an embodiment of the present invention. As shown in FIG. 3, the apparatus includes a judging module 32 and a refreshing module 34. The device is described below:
  • the determining module 32 is configured to determine, according to the address information of the node on the faulty link on the ring network or the address information of the node on the backup link, whether to refresh the FDB of the first node, where the first node is in the ring network
  • the node is connected to the upstream device, and the refreshing module 34 is connected to the determining module 32.
  • the FDB of the node is refreshed.
  • FIG. 4 is a block diagram showing a preferred structure of an FDB refreshing apparatus in a ring network according to an embodiment of the present invention. As shown in FIG. 4, the apparatus includes a discarding module 42 in addition to all the modules shown in FIG. Be explained:
  • the abandonment module 42 is connected to the above-mentioned judging module 32, and is set to abandon the refresh operation of the FDB of the first node if the judgment result of the judging module 32 is NO.
  • FIG. 5 is a block diagram showing the structure of the determining module 32 in the FDB refreshing apparatus in the ring network according to the embodiment of the present invention.
  • the determining module 32 includes a first determining unit 52 and a first determining unit 54, and the following This determination module 32 will be described.
  • the first determining unit 52 is configured to determine, when the ring network link is faulty, whether the path information including the uplink node address information in the normal state of the first node includes the address information of the node on the faulty link, where The path information includes address information of each node except the first node sequentially included on the path of the uplink node starting from the first node; the first determining unit 54 is connected to the first determining unit 52, and is set to When the determination result of the first determination unit 52 is YES, it is determined that the FDB of the first node is refreshed.
  • FIG. 6 is a block diagram 2 of the structure of the determining module 32 in the FDB refreshing apparatus in the ring network according to the embodiment of the present invention.
  • the determining module 32 includes a second determining unit 62 and a second determining unit 64. This determination module 32 will be described.
  • the second determining unit 62 is configured to determine, when the link fault is eliminated, whether the path information including the uplink node address information in the fault state of the first node includes address information of a node on the backup link, where the path information And including an address letter of each node except the first node sequentially included in the path of the uplink node starting from the first node; the second determining unit 64 is connected to the second determining unit 62, and is set to be in the second When the determination result of the determination unit 62 is YES, it is determined that the FDB of the first node is refreshed.
  • FIG. 7 is a structural block diagram of a node according to an embodiment of the present invention. As shown in FIG. 7, the node 70 includes the FDB refreshing device 72 of any of the above.
  • FIG. 8 is a structural block diagram of an FDB refresh system in a ring network according to an embodiment of the present invention. As shown in FIG. 8, the FDB refresh system 80 includes one or more nodes 70.
  • the present invention provides a processing method for refreshing the FDB under the ring network protection. The invention will now be described in connection with preferred embodiments.
  • the invention provides a processing method for refreshing the FDB under the ring network protection, so as to optimize the mechanism for refreshing the FDB during the protection switching process, reduce the service interruption time, and improve the ring network switching performance.
  • the node connected to the upstream device in the ring network is the uplink node.
  • other ring network nodes periodically send protocol packets from the two ring ports to perform trace operation, and obtain media access control of other ring nodes on the path between the two nodes and the uplink node (Medium/MediaAccess). Control, referred to as MAC address information (MAC address), is stored in the path information table under the corresponding port in order.
  • MAC address information MAC address
  • the faulty node When the ring network fails, the faulty node sends a fault packet (signal failure, Signal Fail, referred to as SF, according to the ERPS protocol).
  • SF Signal Fail
  • Other ring network nodes except for the upper link
  • the node After receiving the packet, the node searches for the source MAC address of the packet in the path information table of the uplink node address information of each port. If it is retrieved, the FDB needs to be refreshed when the ring network is switched; If you don't, you don't need to refresh the FDB.
  • the path information table containing the address information of the uplink node under a certain node port includes the node of the backup link (that is, the ring network protection link, the RPL link), then The FDB needs to be refreshed when the ring network resumes switching.
  • the method optimizes the mechanism for refreshing the FDB during the ring network switching process, reduces the redundant refresh FDB processing, and improves the network switching performance.
  • the present invention can solve the problem that the nodes existing in the related art perform unnecessary FDB refresh actions, affect the ring network switching performance, and reduce the user experience by the following technical solutions:
  • the device connected to the upstream switching device is configured as an uplink node, and the other ring network nodes configure the MAC address of the uplink node, and periodically send protocol packets (ERPS Trace packets) to the two ring ports to perform the trace operation target.
  • protocol packets ERPS Trace packets
  • For the uplink node since multiple logical rings (configured with multiple ERPS instances) may be configured on the same physical ring network, the uplink nodes of each logical ring may be different devices in the ring network, and all operations in the present invention are directed to a single logical ring.
  • the ERPS trace packet can be obtained by extending the ERPS protocol packet.
  • the extension field in the Request/State flag of the 4 bit packet represents the ERPS Trace packet.
  • the destination MAC address and the time-to-live (TTL) are added to the packet payload.
  • the packet is forwarded on the non-blocking port in the ring network and the TTL is decreased by 1 (the TTL is 0).
  • the blocked port is discarded.
  • the transmission path is the same as the service flow.
  • the TTL value ranges from 0 to 255. Can take 255.
  • the ERPS Trace packet is extended from the ERPS protocol packet and carries the information of the corresponding logical ring to distinguish different logical rings.
  • the processing flow is similar to the original ERPS protocol packet, and only needs to increase the parsing and processing of the packet, so it is a better choice for the ERPS ring network.
  • the node on the path After receiving the ERPS Trace message, the node on the path forwards the packet to another ring network port and replies with a trace response trace message carrying its own information. If the target is the local node, only one Trace Reply message is replied.
  • the ERPS Trace Reply message is similar to the Trace message and is obtained by extending the Request/State flag. Add the destination MAC address to the packet payload, and record the TTL value of the Trace packet received by the node as the label. The forwarding behavior is the same as that of the Trace packet.
  • a timeout timer can be started. After the timer expires, the received Trace Reply packet is not processed. This timer is reset the next time a Trace message is sent. After receiving the Reply packet, the ERPS Trace packet sends the source MAC address of the Reply packet to the path information table of the sending port according to the TTL value. The timer expires or the uplink node is received. After the Reply message A complete path information table for the uplink node can be obtained, where the order includes the MAC address of each node.
  • the faulty node sends an ERPS protocol packet (Signal Fail packet, ERPS protocol definition) carrying its own MAC address.
  • the trace path to the uplink node is the actual path of the service flow. If the source MAC address of the fault packet is in the path information table of the uplink node address information of a certain port, the path between the uplink node and the uplink node is faulty. If the service source needs to be switched, the FDB needs to be refreshed. If the source MAC address of the fault packet is not in the path information table containing the address information of the uplink node, the path between the uplink node and the uplink node does not fail. There is no need to refresh the FDB. The refresh FDB mechanism of the uplink node, the faulty node, and the RPL backup link node is consistent with the ERPS protocol definition (not within the scope of this embodiment).
  • each node immediately triggers the Trace process when the ring network is switched or a new fault packet is received.
  • the invention obtains the path information of the uplink node by periodically sending the trace message to each node in the ring network, and compares the fault information, the RPL information and the path information including the address information of the uplink node to determine the ring network switching time. Whether to refresh the FDB, optimize the refresh FDB mechanism, less unnecessary refresh processing, improve the ring network switching performance.
  • FIG. 9 is a schematic diagram of a trace in a normal working state according to an embodiment of the present invention.
  • a plurality of devices form a ring network and operate an ERPS ring network protection protocol, wherein the RPL link is as shown in FIG. 9.
  • the uplink node connected to the upstream device in the ring network may be any one of the devices.
  • the node connected to the upstream device is designated as the uplink node.
  • the other ring network device configures the MAC address of the uplink node, and periodically sends a trace packet from the two ring ports.
  • the destination is the uplink node to obtain the device information on the path between the uplink node and the trace packet payload. Contains the MAC address of the Trace target.
  • the source MAC address is the node.
  • the MAC address of the packet contains the MAC address of the node 4 and the TTL value of the received Trace packet.
  • Node 2 processing is the same as Node 3.
  • the node 1 After receiving the trace packet, the node 1 finds that the destination is the local node, and then responds to the Reply packet.
  • the packet payload contains the MAC address of the node 4 and contains the TTL value of the received trace packet.
  • the node on the path receives the Reply packet and checks that the destination MAC is not the local node and forwards it to another ring network port.
  • the port 0 of the node 4 After receiving the Reply packet replied by each node, the port 0 of the node 4 checks that the target is the local node, and stores the MAC addresses of the nodes according to the TTL values recorded in the Reply packets. After receiving the Reply packet of the uplink node or the timeout timer expires, the path information table under the Reply packet update port is not processed.
  • the processing in the Port1 direction is the same.
  • the trace packet cannot be forwarded because the RPL link of the node 6 is blocked.
  • the path information table of port 0 of node 4 is: MAC3 (MAC address of node 3) - MAC2 (MAC address of node 2) - MAC1 (MAC address of node 1); path information table of port 1 is: MAC5-MAC6.
  • the path information table of each node in the ring network is obtained. As shown in Table 1, Table 1 identifies the normal state path information table. Port0 is the port at the front end of the ring clockwise direction, and the other port is port1.
  • FIG. 10 is a schematic diagram of a trace in a fault state according to an embodiment of the present invention.
  • nodes 2, 3 detect a fault and block the faulty port according to the ERPS protocol.
  • the standard needs to refresh the FDB (not within the scope of this embodiment) and immediately send a failure message (Signal Fail message) to the ring port.
  • the uplink node 1 needs to refresh the FDB when receiving the SF message (same as the ERPS protocol standard, which is not within the scope of this embodiment).
  • Nodes 4, 5, and 6 will immediately receive the source MAC address as MAC3 at port0.
  • the SF message includes MAC3 according to the path information table of MAC1 including the address information of the uplink of each node port0. Therefore, the nodes 4, 5, and 6 need to refresh the FDB.
  • Node 7 receives the SF packet whose source MAC address is MAC2 in port1, and is not in the path information table of port1. Therefore, node 7 does not need to refresh the FDB.
  • the RPL link is opened and becomes the forwarding state.
  • the port 1 of the nodes 4, 5, and 6 also receives the SF packet whose source MAC address is MAC2. Because it is not in the path information table, there is no need to refresh the FDB.
  • Port 0 of node 7 receives the SF packet whose source MAC address is MAC3. Since it is not in the path information table, there is no need to refresh the FDB.
  • the path information table is updated in real time, after the fault state is stabilized, the path information table of each node is as shown in Table 2.
  • the table 2 is a fault state path information table.
  • the port path information table of the node 2 does not include the two nodes of the RPL link, so the FDB is not refreshed; the nodes 3, 4,
  • the port 1 of port 5 contains the address information of the uplink node.
  • the path information table contains two nodes 6 and 7 of the RPL. Therefore, you need to refresh the FDB. For nodes 6 and 7, you need to block the RPL port. Therefore, you need to refresh the FDB.
  • each node immediately initiates the operation of the Trace uplink node.
  • the port path information table receives the Reply packet, it is updated in real time. It is determined whether the FDB needs to be refreshed. The port path information table is also queried immediately. There is no need to wait for receiving the Reply message of the uplink node or the timeout timer expires.
  • the multi-link failure may be handled in the above single link failure. That is, whether to refresh the FDB is determined by querying whether the failed node is in the port path information table including the uplink node address information. For multi-link failure recovery, it can be decomposed into single The faults are gradually recovered. If the fault state is still after the recovery, there is no need to refresh the FDB; until the last one becomes the single link fault recovery, it is consistent with the above described processing.
  • each node in the ring network periodically sends a Trace packet to obtain the port path information of the uplink node, and compares the fault information, the RPL information, and the port path information including the address information of the uplink node to determine the ring.
  • the FDB mechanism is optimized to be refreshed, less unnecessary refresh processing is performed, and ring network switching performance is improved.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above embodiments and preferred embodiments solve the problem that the nodes existing in the related art perform unnecessary FDB refresh actions, affect the ring network switching performance, and reduce the user experience, thereby achieving an optimized FDB refresh mechanism. Reduce unnecessary refresh processing and improve the performance of ring network switching performance.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

本发明提供了一种环形网络中FDB刷新方法、装置、节点及***，其中，该方法包括依据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的FDB进行刷新，其中，该第一节点为环形网络中除上联节点外的节点，该上联节点为环形网络与上游设备相连的节点；在判断结果为是的情况下，对第一节点的FDB进行刷新。解决了相关技术中存在的节点会执行不必要的FDB刷新动作，影响环网切换性能，降低用户体验的问题，进而达到了优化FDB刷新机制，减少不必要的刷新处理，提高环网切换性能的效果。

Description

环形网络中FDB刷新方法、装置、节点及*** 技术领域
本发明涉及通信领域，具体而言，涉及一种环形网络中FDB刷新方法、装置、节点及***。
背景技术
环网保护协议(以G.8032描述的ERPS协议为例)在网络正常时阻塞环网保护链路(Ring Protection Link，简称为RPL)，在检测到链路故障后会阻塞故障链路，打开RPL链路，以实现业务保护和快速切换的功能。
图1是相关技术中的环网切换前后业务流切换示意图。如图1所示，在环网协议状态发生切换时(网络故障或故障恢复时)，一般会根据协议重新设置环网端口的生成树协议(Spanning Tree Protocol，简称为STP)状态(STP状态)，并且刷新MAC地址转发表(Forwarding DateBase，简称为FDB)使业务流在主用链路和备用链路间切换。目前的刷新FDB的机制使得在环网切换时，会执行不必要、多余的刷新节点的FDB的动作，并且，在现网环境下由于FDB表条目数量很大，受交换芯片性能限制，可能出现业务切换中断时间超标的情况，影响用户体验。
因此，在相关技术中存在着节点会执行不必要的FDB刷新动作，影响环网切换性能，降低用户体验的问题。
发明内容
本发明提供了一种环形网络中FDB刷新方法、装置、节点及***，以至少解决相关技术中存在的节点会执行不必要的FDB刷新动作，影响环网切换性能，降低用户体验的问题。
根据本发明的一方面，提供了一种环形网络中地址转发表FDB刷新方法，包括：依据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的FDB进行刷新，其中，所述第一节点为所述环形网络中除上联节点外的节点，所述上联节点为所述环形网络与上游设备相连的节点；在判断结果为是的情况下，对所述第一节点的所述FDB进行刷新。
优选的，在依据所述环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对所述第一节点的所述FDB进行刷新之后，还包括：在判断结果为否的情况下，放弃对所述第一节点的所述FDB的刷新操作。
优选的，依据所述环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的所述FDB进行刷新包括：在所述环形网络链路发生故障时，判断所述第一节点的正常状态下的包含上联节点地址信息的路径信息中是否包含所述故障链路上的节点的地址信息，其中，所述路径信息包括从所述第一节点开始的目的为所述上联节点的路径上顺序包含的除所述第一节点外的各个节点的地址信息；在判断结果为是的情况下，确定对所述第一节点的所述FDB进行刷新。
优选的，依据所述环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的所述FDB进行刷新包括：在链路故障消除时，判断所述第一节点的故障状态下的包含上联节点地址信息的路径信息中是否包含所述备份链路上的节点的地址信息，其中，所述路径信息包括从所述第一节点开始的目的为所述上联节点的路径上顺序包含的除所述第一节点外的各个节点的地址信息；在判断结果为是的情况下，确定对所述第一节点的所述FDB进行刷新。
根据本发明的另一方面，提供了一种环形网络中地址转发表FDB刷新装置，包括：判断模块，设置为依据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的FDB进行刷新，其中，所述第一节点为所述环形网络中除上联节点外的节点，所述上联节点为所述环形网络与上游设备相连的节点；刷新模块，设置为在所述判断模块的判断结果为是的情况下，对所述第一节点的所述FDB进行刷新。
优选的，所述FDB刷新装置还包括：放弃模块，设置为在所述判断模块的判断结果为否的情况下，放弃对所述第一节点的所述FDB的刷新操作。
优选的，所述判断模块包括：第一判断单元，设置为在所述环形网络链路发生故障时，判断所述第一节点的正常状态下的包含上联节点地址信息的路径信息中是否包含所述故障链路上的节点的地址信息，其中，所述路径信息包括从所述第一节点开始的目的为所述上联节点的路径上顺序包含的除所述第一节点外的各个节点的地址信息；第一确定单元，设置为在所述第一判断单元判断结果为是的情况下，确定对所述第一节点的所述FDB进行刷新。
优选的，所述判断模块包括：第二判断单元，设置为在链路故障消除时，判断所述第一节点的故障状态下的包含上联节点地址信息的路径信息中是否包含所述备份链 路上的节点的地址信息，其中，所述路径信息包括从所述第一节点开始的目的为所述上联节点的路径上顺序包含的除所述第一节点外的各个节点的地址信息；第二确定单元，设置为在所述第二判断单元的判断结果为是的情况下，确定对所述第一节点的所述FDB进行刷新。
根据本发明的又一方面，提供了一种节点，包括上述任一项所述的装置。
根据本发明的再一方面，提供了一种环形网络中地址转发表FDB刷新***，包括一个或多个上述所述的节点。
通过本发明，采用依据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的FDB进行刷新，其中，所述第一节点为所述环形网络中除上联节点外的节点，所述上联节点为所述环形网络与上游设备相连的节点；在判断结果为是的情况下，对所述第一节点的所述FDB进行刷新的方法，解决了相关技术中存在的节点会执行不必要的FDB刷新动作，影响环网切换性能，降低用户体验的问题，进而达到了优化FDB刷新机制，减少不必要的刷新处理，提高了环网切换性能的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是相关技术中的环网切换前后业务流切换示意图；
图2是根据本发明实施例的环形网络中FDB刷新方法的流程图；
图3是根据本发明实施例的环形网络中FDB刷新装置的结构框图；
图4是根据本发明实施例的环形网络中FDB刷新装置的优选结构框图；
图5是根据本发明实施例的环形网络中FDB刷新装置中判断模块32的结构框图一；
图6是根据本发明实施例的环形网络中FDB刷新装置中判断模块32的结构框图二；
图7是根据本发明实施例的节点的结构框图；
图8是根据本发明实施例的环形网络中FDB刷新***的结构框图；
图9是根据本发明实施例正常工作状态时的Trace示意图；
图10是根据本发明实施例故障状态下的Trace示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
在本实施例中提供了一种环形网络中FDB刷新方法，图2是根据本发明实施例的环形网络中FDB刷新方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，依据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的FDB进行刷新，其中，该第一节点为环形网络中除上联节点外的节点，该上联节点为环形网络与上游设备相连的节点；
步骤S204，在判断结果为是的情况下，对第一节点的FDB进行刷新。
通过上述步骤，采用依据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的FDB进行刷新，其中，该第一节点为环形网络中除上联节点外的节点，该上联节点为环形网络与上游设备相连的节点；在判断结果为是的情况下，对第一节点的FDB进行刷新的方法，实现了可以根据故障链路上的节点的地址信息或者是备份链路上的节点的地址信息来决定是否需要刷新第一节点的FDB，解决了相关技术中存在的节点会执行不必要的FDB刷新动作，影响环网切换性能，降低用户体验的问题，进而达到了优化FDB刷新机制，减少不必要的刷新处理，提高环网切换性能的效果。
在一个可选的实施例中，当根据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断不需要对第一节点的FDB进行刷新时，可以放弃对第一节点的FDB的刷新操作，进而可以实现仅在需要刷新节点FDB的时候再刷新节点的FDB。
其中，依据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的FDB进行刷新可以采用如下方法：在环形网络链路发生故障时，判断第一节点的正常状态下的包含上联节点地址信息的路径信息中是否包含故障链路上的节点的地址信息其中，该路径信息包括从第一节点开始的目的为上联节点 的路径上顺序包含的除第一节点外的各个节点的地址信息；在判断结果为是的情况下，确定对第一节点的FDB进行刷新。即，在环形网络各链路均正常时，每个节点可以存储自己的路径信息，在环形网络发生链路故障时，可以判断节点所存储的正常状态下的路径信息中是否包含故障链路所涉及的节点的地址信息，在包含的情况下，再刷新该节点的FDB。
依据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的FDB进行刷新还可以采用如下方法：在链路故障消除时，判断第一节点的故障状态下的包含上联节点地址信息的路径信息中是否包含备份链路上的节点的地址信息，其中，该路径信息包括从第一节点开始的目的为上联节点的路径上顺序包含的除第一节点外的各个节点的地址信息；在判断结果为是的情况下，确定对第一节点的FDB进行刷新。即，在网络发生故障时，会连通备份链路，每个节点可以存储该故障状态下的节点路径信息，当环形网络的故障消除时，可以判断节点所存储的故障状态下的包含上联节点地址信息的路径信息中是否包括备份链路所涉及的节点的地址信息，在包含的情况下，再刷新该节点的FDB。
在本实施例中还提供了一种环形网络中地址转发表FDB刷新装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的环形网络中FDB刷新装置的结构框图，如图3所示，该装置包括判断模块32和刷新模块34。下面对该装置进行说明：
判断模块32，设置为依据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的FDB进行刷新，其中，该第一节点为环形网络中除上联节点外的节点，上联节点为环形网络与上游设备相连的节点；刷新模块34，连接至上述判断模块32，用于在判断模块32的判断结果为是的情况下，对第一节点的FDB进行刷新。
图4是根据本发明实施例的环形网络中FDB刷新装置的优选结构框图，如图4所示，该装置除包括图3所示的所有模块外，还包括放弃模块42，下面对该装置进行说明：
放弃模块42，连接至上述判断模块32，设置为在判断模块32的判断结果为否的情况下，放弃对第一节点的FDB的刷新操作。
图5是根据本发明实施例的环形网络中FDB刷新装置中判断模块32的结构框图一，如图5所示，该判断模块32包括第一判断单元52和第一确定单元54，下面对该判断模块32进行说明。
第一判断单元52，设置为在环形网络链路发生故障时，判断第一节点的正常状态下的包含上联节点地址信息的路径信息是否包含故障链路上的节点的地址信息，其中，该路径信息包括从第一节点开始的目的为上联节点的路径上顺序包含的除第一节点外的各个节点的地址信息；第一确定单元54，连接至上述第一判断单元52，设置为在第一判断单元52的判断结果为是的情况下，确定对第一节点的FDB进行刷新。
图6是根据本发明实施例的环形网络中FDB刷新装置中判断模块32的结构框图二，如图6所示，该判断模块32包括第二判断单元62和第二确定单元64，下面对该判断模块32进行说明。
第二判断单元62，设置为在链路故障消除时，判断第一节点的故障状态下的包含上联节点地址信息的路径信息是否包含备份链路上的节点的地址信息，其中，该路径信息包括从第一节点开始的目的为上联节点的路径上顺序包含的除第一节点外的各个节点的地址信；第二确定单元64，连接至上述第二判断单元62，设置为在第二判断单元62的判断结果为是的情况下，确定对第一节点的FDB进行刷新。
图7是根据本发明实施例的节点的结构框图，如图7所示，该节点70包括上述任一项的FDB刷新装置72。
图8是根据本发明实施例的环形网络中FDB刷新***的结构框图，如图8所示，该FDB刷新***80包括一个或多个节点70。
为了解决相关技术中存在的节点会执行不必要的FDB刷新动作，影响环网切换性能，降低用户体验的问题，本发明提供了一种环网保护下刷新FDB的处理方法。下面结合优选实施例对本发明进行说明。
本发明提供了一种环网保护下刷新FDB的处理方法，以优化保护切换过程中刷新FDB的机制，减少业务中断时间，提高环网切换性能。环网内与上游设备相连的节点为上联节点。除上联节点外其他环网节点定时分别从两个环网端口发送协议包执行跟踪trace操作，获取该节点两侧与上联节点间路径上的其他环网节点的介质访问控制(Medium/MediaAccess Control，简称为MAC)地址信息(MAC地址)，并按顺序保存在对应端口下的路径信息表中。在环网发生故障时，故障节点会发送故障报文(信号失败报文，Signal Fail，简称为SF，根据ERPS协议定义)。其他环网节点(除上联 节点)收到该报文后，会将该报文源MAC地址在各个端口的包含上联节点地址信息的路径信息表中查找，如果检索到，则需要在环网切换时刷新FDB；如果检索不到，则可以无需刷新FDB。在故障消失，环网恢复到正常状态时，如果某节点端口下的包含上联节点地址信息的路径信息表中包含备份链路(即环网保护链路，RPL链路)的节点，则在环网恢复切换时需要刷新FDB。该方法优化了环网切换过程中刷新FDB的机制，减少了多余的刷新FDB处理，提高网络切换性能。
本发明可以通过如下技术方案来解决相关技术中存在的节点会执行不必要的FDB刷新动作，影响环网切换性能，降低用户体验的问题：
1、与上游交换设备相连的设备被配置为上联节点，其他环网节点配置该上联节点的MAC地址，定时向两个环网端口发送协议包(ERPS Trace报文)，执行trace操作目标为上联节点。由于同一个物理环网上可能配置多个逻辑环(配置多个ERPS实例)，每个逻辑环的上联节点可以是环网内不同设备，本发明中所有操作都是针对单个逻辑环。
2、ERPS Trace报文可通过扩展ERPS协议报文来获得，如：在报文4bit的Request/State标志位中扩展字段代表ERPS Trace报文。并在报文载荷中增加目标MAC地址，生存时间字段(time-to-live，简称为TTL)。该报文在环网中非阻塞端口转发并TTL减1(TTL为0则丢弃)，阻塞端口丢弃，保证传输路径与业务流相同，其中，TTL取值范围可以使0-255，一般情况下可以取255。ERPS Trace报文由于从ERPS协议报文扩展而来，也会携带对应逻辑环的信息用以区分不同的逻辑环。处理流程与原ERPS协议报文类似，只需增加对该报文的解析处理即可，因此对于ERPS环网是较好的选择。
3、路径上的节点收到ERPS Trace报文后，如果目标节点不是本节点，将该报文转发到另一个环网端口，并回复一份携带自身信息的跟踪回复Trace Reply报文。如果目标是本节点，则只回复一份Trace Reply报文。
4、ERPS Trace Reply报文与Trace报文类似，通过扩展Request/State标志位获得。在报文载荷中增加目标MAC地址，并记录节点收到Trace报文的TTL值作为标签。转发行为与Trace报文相同。
5、ERPS Trace报文发送后可以启动一个超时定时器，该定时器超时后不再处理收到的Trace Reply报文。该定时器在下次发送Trace报文时重置。ERPS Trace报文发送节点端收到Reply报文后，根据包含的TTL值的大小将Reply报文的源MAC地址保存在发送端口下的路径信息表中，在定时器超时或收到上联节点的Reply报文后即 可获取到一份完整的目标为上联节点的路径信息表，其中顺序包含各个节点的MAC地址。
6、环网故障发生时，故障节点会发送携带自身MAC地址的ERPS协议报文(Signal Fail报文，ERPS协议定义)。由于Trace报文与业务流转发状态一致，Trace至上联节点的路径即是业务流的实际路径。对于接收到该故障报文的环网节点，如果该故障报文的源MAC地址在某一个端口的包含上联节点地址信息的路径信息表中，则说明与上联节点间路径发生故障，此时业务需要切换，需要刷新FDB；如果该故障报文的源MAC地址不在包含上联节点地址信息的路径信息表中，则说明与上联节点间的路径没有发生故障，此时业务不会切换，无需刷新FDB。而上联节点、故障节点及RPL备份链路节点刷新FDB机制与ERPS协议定义保持一致(不在本实施例讨论范围内)。
7、环网故障消失，恢复到正常工作状态时，由于此时环网RPL链路将被阻塞，因此各节点任意端口包含上联节点地址信息的路径信息表中如果包含RPL备份链路的节点，则恢复后业务会发生切换，需要刷新FDB。
8、为保证切换性能和可靠性，在环网状态切换或收到新的故障报文时，各节点会立刻触发Trace过程。
本发明通过环网内各节点定时发送Trace报文获取到上联节点的路径信息，并通过将故障信息、RPL信息等与包含上联节点地址信息的路径信息进行比较，来决策环网切换时是否刷新FDB，优化了刷新FDB机制，较少不必要的刷新处理，提高环网切换性能。
下面结合附图对本发明实施例中的技术方案进行进一步的描述。本发明对专业技术人员熟知的部分未进行表述或者未进行详细描述，各种操作将按照顺序使用多个分离的步骤进行描述。
图9是根据本发明实施例正常工作状态时的Trace示意图，如图9所示，若干台设备组成环网并运行ERPS环网保护协议，其中RPL链路如图9中所示。环网内与上游设备相连的上联节点可以是其中任意一台设备。
正常工作时如图9，与上游设备相连的节点被指定为上联节点。其他环网设备配置该上联节点的MAC地址，定时分别从两个环网端口发送Trace报文，目的为上联节点，以获取与上联节点之间路径上的设备信息，Trace报文载荷中包含Trace目标的MAC地址。
下面以节点4为例进行说明。定时向环网端口port0、port1发送Trace报文，并启用超时定时器。超时定时器超时时间小于定时发送Trace报文的时间间隔。节点3收到Trace报文，发现目标不是本节点，则将报文TTL字段的值减1并向另一个环网端口转发Trace报文，并从接收端口回复Reply报文，源MAC地址为节点3的MAC地址，报文载荷中包含目标MAC地址为节点4的MAC，并包含收到的Trace报文的TTL值。节点2处理与节点3相同。节点1收到Trace报文后，发现目的就是本节点，则回复Reply报文，报文载荷中包含目标MAC地址为节点4的MAC，并包含收到的Trace报文的TTL值。路径上的节点收到Reply报文，检查目标MAC不是本节点则会向另一个环网端口转发。节点4的port0收到各节点回复的Reply报文后，检查发现目标是本节点，则根据Reply报文中记录的TTL值的从大到小排序保存各个节点的MAC地址。在Trace报文的一个发送周期内收到上联节点的Reply报文或超时定时器超时后不再处理Reply报文更新端口下的路径信息表。Port1方向上的处理相同，只是由于节点6的RPL链路为阻塞，Trace报文无法转发。此时节点4的port0的路径信息表为：MAC3(节点3的MAC地址)-MAC2(节点2的MAC地址)-MAC1(节点1的MAC地址)；port1的路径信息表为：MAC5-MAC6。
与上面的方法相同，得到环网内各节点的路径信息表，如表1所示，表1标识正常状态路径信息表。其中port0为环顺时针方向前端的端口，另一个端口为port1。
Figure PCTCN2014091921-appb-000001
表1
图10是根据本发明实施例故障状态下的Trace示意图，如图10所示，当节点2和节点3之间发生链路故障时，节点2、3检测到故障，阻塞故障端口，根据ERPS协议标准需要刷新FDB(不在本实施例讨论范围内)，并立刻向环网端口发送故障报文(Signal Fail报文)。上联节点1收到SF报文需要刷新FDB(与ERPS协议标准相同，不在本实施例讨论范围内)。节点4、5、6会立即在port0收到源MAC地址为MAC3 的SF报文，根据各节点port0的包含上联节点地址信息的MAC1的路径信息表，都包含MAC3，因此节点4、5、6需要刷新FDB。节点7在port1收到源MAC地址为MAC2的SF报文，不在port1的路径信息表中，因此节点7无需刷新FDB。故障发生后RPL链路打开，变为转发状态，此时节点4、5、6的port1也会收到源MAC地址为MAC2的SF报文，由于不在路径信息表中，无需刷新FDB。节点7的port0收到源MAC地址为MAC3的SF报文，由于不在路径信息表中，无需刷新FDB。
由于路径信息表是实时更新的，故障状态稳定后，各节点的路径信息表如表2，该表2是故障状态路径信息表。
Figure PCTCN2014091921-appb-000002
表2
当2、3节点间故障消失，环网恢复正常工作状态，阻塞RPL链路时，节点2的端口路径信息表中不包含RPL链路的两个节点，因此不用刷新FDB；节点3、4、5的port1端口包含上联节点地址信息的路径信息表中包含RPL两路的两个节点6、7，因此需要刷新FDB；对于节点6、7，由于需要阻塞RPL端口，因此需要刷新FDB(不在本实施例讨论范围内)。
为保证切换性能和可靠性，环网状态变化时，各个节点会立刻发起Trace上联节点的操作。并且端口路径信息表收到Reply报文后实时更新，判断是否需要刷新FDB也是立即查询端口路径信息表，无需等待收到上联节点Reply报文或者超时定时器超时。
在一个优选的实施例中，对于多链路故障，无论是同时发生还是先后发生都可以采用上面单链路故障的处理方式。即，通过查询故障节点是否在包含上联节点地址信息的端口路径信息表中来决策是否刷新FDB。对于多链路故障的恢复，可以分解为单 个故障逐步恢复，如果恢复后仍为故障状态则无需刷新FDB；直到最后变为单链路故障恢复的情形，与前面描述的处理一致。
经过以上处理，环网内各节点定时发送Trace报文获取到上联节点的端口路径信息，并通过将故障信息、RPL信息等与包含上联节点地址信息的端口路径信息进行比较，来决策环网切换时是否刷新FDB，优化了刷新FDB机制，较少不必要的刷新处理，提高环网切换性能。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，通过上述实施例及优选实施方式，解决了相关技术中存在的节点会执行不必要的FDB刷新动作，影响环网切换性能，降低用户体验的问题，进而达到了优化FDB刷新机制，减少不必要的刷新处理，提高了环网切换性能的效果。

Claims (10)

  1. 一种环形网络中地址转发表FDB刷新方法，包括：
    依据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的FDB进行刷新，其中，所述第一节点为所述环形网络中除上联节点外的节点，所述上联节点为所述环形网络与上游设备相连的节点；
    在判断结果为是的情况下，对所述第一节点的所述FDB进行刷新。
  2. 根据权利要求1所述的方法，其中，在依据所述环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对所述第一节点的所述FDB进行刷新之后，还包括：
    在判断结果为否的情况下，放弃对所述第一节点的所述FDB的刷新操作。
  3. 根据权利要求1所述的方法，其中，依据所述环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的所述FDB进行刷新包括：
    在所述环形网络链路发生故障时，判断所述第一节点的正常状态下的包含上联节点地址信息的路径信息中是否包含所述故障链路上的节点的地址信息，其中，所述路径信息包括从所述第一节点开始的目的为所述上联节点的路径上顺序包含的除所述第一节点外的各个节点的地址信息；
    在判断结果为是的情况下，确定对所述第一节点的所述FDB进行刷新。
  4. 根据权利要求1所述的方法，其中，依据所述环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的所述FDB进行刷新包括：
    在链路故障消除时，判断所述第一节点的故障状态下的包含上联节点地址信息的路径信息是否包含所述备份链路上的节点的地址信息，其中，所述路径信息包括从所述第一节点开始的目的为所述上联节点的路径上顺序包含的除所述第一节点外的各个节点的地址信息；
    在判断结果为是的情况下，确定对所述第一节点的所述FDB进行刷新。
  5. 一种环形网络中地址转发表FDB刷新装置，包括：
    判断模块，设置为依据环形网络上故障链路上的节点的地址信息或备份链路上的节点的地址信息判断是否对第一节点的FDB进行刷新，其中，所述第一节点为所述环形网络中除上联节点外的节点，所述上联节点为所述环形网络与上游设备相连的节点；
    刷新模块，设置为在所述判断模块的判断结果为是的情况下，对所述第一节点的所述FDB进行刷新。
  6. 根据权利要求5所述的装置，其中，还包括：
    放弃模块，设置为在所述判断模块的判断结果为否的情况下，放弃对所述第一节点的所述FDB的刷新操作。
  7. 根据权利要求5所述的装置，其中，所述判断模块包括：
    第一判断单元，设置为在所述环形网络链路发生故障时，判断所述第一节点的正常状态下的包含上联节点地址信息的路径信息中是否包含所述故障链路上的节点的地址信息，其中，所述路径信息包括从所述第一节点开始的目的为所述上联节点的路径上顺序包含的除所述第一节点外的各个节点的地址信息；
    第一确定单元，设置为在所述第一判断单元判断结果为是的情况下，确定对所述第一节点的所述FDB进行刷新。
  8. 根据权利要求5所述的装置，其中，所述判断模块包括：
    第二判断单元，设置为在链路故障消除时，判断所述第一节点的故障状态下的包含上联节点地址信息的路径信息中是否包含所述备份链路上的节点的地址信息，其中，所述路径信息包括从所述第一节点开始的目的为所述上联节点的路径上顺序包含的除所述第一节点外的各个节点的地址信息；
    第二确定单元，设置为在所述第二判断单元的判断结果为是的情况下，确定对所述第一节点的所述FDB进行刷新。
  9. 一种节点，包括权利要求5至8中任一项所述的装置。
  10. 一种环形网络中地址转发表FDB刷新***，包括一个或多个如权利要求9所述的节点。
PCT/CN2014/091921 2014-08-22 2014-11-21 环形网络中fdb刷新方法、装置、节点及*** WO2015117465A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410417790.3 2014-08-22
CN201410417790.3A CN105357131B (zh) 2014-08-22 2014-08-22 环形网络中fdb刷新方法、装置、节点及***

Publications (1)

Publication Number Publication Date
WO2015117465A1 true WO2015117465A1 (zh) 2015-08-13

Family

ID=53777274

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/091921 WO2015117465A1 (zh) 2014-08-22 2014-11-21 环形网络中fdb刷新方法、装置、节点及***

Country Status (2)

Country Link
CN (1) CN105357131B (zh)
WO (1) WO2015117465A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113518024A (zh) * 2021-07-12 2021-10-19 普联技术有限公司 一种节点的地址表刷新方法、装置、终端和存储介质
CN113645312A (zh) * 2021-08-25 2021-11-12 烽火通信科技股份有限公司 一种基于erps协议的子环网链路保护方法与装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102025561A (zh) * 2010-11-24 2011-04-20 中兴通讯股份有限公司 一种以太环网中刷新mac的方法及***
CN102075361A (zh) * 2011-01-19 2011-05-25 中兴通讯股份有限公司 一种恢复环网业务的方法及节点设备
US20130250753A1 (en) * 2012-03-26 2013-09-26 Dong-Chel Shin Method for protection switching in ethernet ring network

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101834774A (zh) * 2009-03-11 2010-09-15 中兴通讯股份有限公司 以太环网中交换节点端口的地址刷新方法及交换节点

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102025561A (zh) * 2010-11-24 2011-04-20 中兴通讯股份有限公司 一种以太环网中刷新mac的方法及***
CN102075361A (zh) * 2011-01-19 2011-05-25 中兴通讯股份有限公司 一种恢复环网业务的方法及节点设备
US20130250753A1 (en) * 2012-03-26 2013-09-26 Dong-Chel Shin Method for protection switching in ethernet ring network

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113518024A (zh) * 2021-07-12 2021-10-19 普联技术有限公司 一种节点的地址表刷新方法、装置、终端和存储介质
CN113518024B (zh) * 2021-07-12 2022-07-05 普联技术有限公司 一种节点的地址表刷新方法、装置、终端和存储介质
CN113645312A (zh) * 2021-08-25 2021-11-12 烽火通信科技股份有限公司 一种基于erps协议的子环网链路保护方法与装置
CN113645312B (zh) * 2021-08-25 2023-07-18 烽火通信科技股份有限公司 一种基于erps协议的子环网链路保护方法与装置

Also Published As

Publication number Publication date
CN105357131A (zh) 2016-02-24
CN105357131B (zh) 2018-10-09

Similar Documents

Publication Publication Date Title
US10686749B2 (en) Packet sending method and network device
US7688716B2 (en) Method, apparatus, and system for improving ethernet ring convergence time
US10110482B2 (en) Technique for network service availability
JP5369228B2 (ja) ユニキャストトラフィックを復元する方法及び装置
CN107547243B (zh) 一种报文转发方法及装置
US10277418B2 (en) Method and device for clearing media access control forwarding entry
US20140233369A1 (en) Ethernet virtual private network system for providing fast protection for access rings
US20150334057A1 (en) Packet forwarding
US20100027543A1 (en) Layer two mac flushing/re-routing
WO2016086713A1 (zh) 一种等价多路径的出接口更新方法及装置
US8451842B2 (en) Media access control bridging in a mesh network
JP7053901B2 (ja) ループ回避通信方法、ループ回避通信デバイスおよびループ回避通信システム
US10476774B2 (en) Selective transmission of bidirectional forwarding detection (BFD) messages for verifying multicast connectivity
WO2022077972A1 (zh) Mlag链路故障切换方法和装置
US10063675B2 (en) Performing duplicate address detection for an integrated routing and bridging device
WO2015117465A1 (zh) 环形网络中fdb刷新方法、装置、节点及***
WO2017219868A1 (zh) Arp条目的处理方法及装置
WO2018040940A1 (zh) 一种二层网络及二层网络的环回检测方法
WO2018120228A1 (zh) 一种环路故障恢复方法、装置及节点设备
US9634927B1 (en) Post-routed VLAN flooding
CN114710440A (zh) 环网收敛的处理方法及装置
US9647924B2 (en) Propagating LDP MAC flush as TCN
JP2012191534A (ja) レイヤ３スイッチの切替方法
US10075369B2 (en) Systems and methods for improved switch performance by preventing flooding
US10642702B1 (en) Mechanism for faster control plane switchover

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

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

Country of ref document: EP

Kind code of ref document: A1