WO2013004124A1 - 一种分布式链路聚合***中业务流转发方法及节点 - Google Patents

一种分布式链路聚合***中业务流转发方法及节点 Download PDF

Info

Publication number
WO2013004124A1
WO2013004124A1 PCT/CN2012/077139 CN2012077139W WO2013004124A1 WO 2013004124 A1 WO2013004124 A1 WO 2013004124A1 CN 2012077139 W CN2012077139 W CN 2012077139W WO 2013004124 A1 WO2013004124 A1 WO 2013004124A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
gateway
service
service flow
flow forwarding
Prior art date
Application number
PCT/CN2012/077139
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 WO2013004124A1 publication Critical patent/WO2013004124A1/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/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • 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
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • the present invention relates to network communication technologies, and in particular, to a service flow forwarding method and a node based on a distributed link aggregation system.
  • NNI Network Node Interface
  • the distributed link aggregation system specifies a gateway (Gateway) based on each virtual local area network (VLAN) in the two sides of the NI network.
  • VLAN virtual local area network
  • the gateway of the network sends the traffic of the VLAN to the NNI network.
  • the NI network forwards the traffic of this VLAN to the gateway of the VLAN of the peer network.
  • the gateway of the VLAN of the peer network forwards the service flow to the peer network, and implements a process of transferring the service from one network to the other through the NI.
  • how to ensure that the traffic of a VLAN in the network enters from the gateway and how the traffic flow retransmits after the gateway node fails is not yet defined.
  • network A and network B are interconnected by multiple links and multiple nodes, wherein a network composed of nodes S1, S2, S4, and S3 constitutes an NNI network, and in network A, node S1 is designated as NI.
  • the gateway of VLAN 1 above, in network B, specifies that node S2 is the gateway of VLAN 1 on the NI.
  • the traffic of the VLAN 1 is forwarded to the node SI. Since the node SI is the gateway of the VLAN 1, the node S1 forwards the service flow to the NNI network.
  • the node S2 When the node S2 receives the service flow, since the node S2 is the gateway of the VLAN 1, the node S2 forwards the service flow to the network B, and implements the VLAN.
  • the traffic flow of 1 is forwarded by the network A through the NNI to the network B.
  • the service flow of the VLAN of the gateway will neither be sent nor received, causing the service flow to be interrupted.
  • the node S1 fails, the service flow of the VLAN 1 is sent to the node S1, the node S1 discards the service flow, and cannot forward the service flow to the NNI network, so the network B cannot receive the VLAN 1
  • the business flow causes the business flow to be interrupted.
  • the dual-homing technology in the network can be used to solve the problem of service flow switching.
  • the transmitted NI node after the service flow switching is not the gateway of the service, the service flow cannot be caused. Forwarding to form an interrupt.
  • the dual-homing technique specifies two ports on the node, which are the first port and the second port. When the first port and the second port are both normal, the service flow of the node is forwarded on the first port, when the first port is used. When a failure occurs, the node's traffic is forwarded on the second port.
  • This technique solves the problem that the internal nodes of the network cannot send traffic to the NI network node after the failure of the NI network node, but in the distributed aggregation link system, even after the gateway node fails, even if the service flow is sent to the NI Network, but because the receiving node is not the gateway node of the service VLAN, the traffic cannot be forwarded to the NI network.
  • the dual-homing technique is enabled on the node S5, and the ports 5 and 6 are the first port and the second port respectively.
  • the service flow of the VLAN 1 in the network A passes through the dual-homing node S5.
  • the first port 5 is forwarded to the node S1, and the service flow can be normally transmitted.
  • the dual-homing node S5 detects the link failure between S5 and S1, and then switches the traffic of the VLAN 1 through the first
  • the second port 6 is forwarded to the node S3, and the node S3 receives the service flow of the VLAN 1.
  • the node S3 is not the gateway of the VLAN 1.
  • the node S3 can only be discarded or cannot be forwarded to the NI network. Therefore, the related technology cannot solve the service caused by the gateway failure of the distributed link aggregation system. Flow interruption problem.
  • the technical problem to be solved by the embodiments of the present invention is to provide a service flow forwarding method and a node in a distributed link aggregation system, which avoids the service flow interruption problem caused by the path failure.
  • a service flow forwarding method in a distributed link aggregation system includes:
  • the service is separately set as the primary gateway.
  • the first node and the second node as the backup gateway, when the second node detects that the path with the first node fails, the second node switches to the primary gateway, and the received service is The data is forwarded.
  • the method further includes:
  • the first node as the primary gateway periodically sends the service flow forwarding policy of the first node to the second node that is the backup gateway;
  • the service flow forwarding policy of the local node is configured according to the service flow forwarding policy sent by the first node, and the service data of the local node is used to receive the service data. Forward.
  • the step of detecting, by the second node, that the path with the first node fails:
  • the second node detects that the first node is faulty
  • the second node detects a link failure between the local node and the first node.
  • the method further includes:
  • the second node When the second node detects that the link between the local node and the first node is faulty, the second node switches to the primary gateway, and the first node continues to perform the received service data as the primary gateway. Forward.
  • other nodes than the first node and the second node use dual-homing technology and/or ring network technology.
  • a node in a distributed link aggregation system includes a detecting unit, a switching unit, and a forwarding unit, where:
  • the detecting unit is configured to: when the node is a backup gateway of a service, detect a path of the node and a node that is the primary gateway of the service in the same network;
  • the switching unit is configured to: when the detecting unit detects that the path of the node and the node that is the primary gateway of the service in the same network fails, switch the local node to the primary gateway; When the node is used as the primary gateway, the received service is received. The data is forwarded.
  • the node further includes a service flow forwarding policy update unit and a service flow forwarding policy configuration unit, where:
  • the service flow forwarding policy update unit is configured to: when the node is the primary gateway, periodically send the service flow forwarding policy of the node to the node that serves as the backup gateway of the service in the same network;
  • the unit is configured to: after the node switches from the standby gateway to the active gateway, configure the service flow forwarding policy of the node according to the service flow forwarding policy sent by the node that is the primary gateway of the service;
  • the data is forwarded in the following manner: The received service data is forwarded by using the service flow forwarding policy of the node.
  • the fault of the path includes:
  • the node that is the primary gateway of the service is faulty; or,
  • the link between the node that is the backup gateway of the service and the node that is the primary gateway of the service in the same network is faulty.
  • the gateway node when the gateway node is not faulty, the gateway node performs the forwarding of the VLAN service flow.
  • the backup gateway automatically switches to the gateway of the VLAN service, and performs the service flow forwarding of the service VLAN service. Service flow interruption due to gateway failure is prevented.
  • FIG. 1 is a schematic diagram of service flow forwarding of a distributed link aggregation system
  • FIG. 2 is a schematic diagram of a service flow interruption caused by a gateway failure in a distributed link aggregation system
  • FIG. 3 is a schematic diagram of a dual-homing node performing service flow switching
  • FIG. 5 is a schematic diagram of a gateway switching of a distributed link aggregation system according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of an intermediate link failover of a distributed link aggregation system according to an embodiment of the present invention.
  • a first node as an active gateway and a second node as a backup gateway are respectively set for the service, and the second node serving as the backup gateway detects the same as the primary network in the same network.
  • the second node that is the backup gateway switches to the primary gateway, and forwards the received data of the service.
  • the first node that is the primary gateway periodically updates the service flow forwarding policy of the first node to the second node that is the backup gateway; after the second node that serves as the backup gateway switches to the primary gateway, according to the
  • the service flow forwarding policy sent by a node configures the service flow forwarding policy of the node, and uses the service flow forwarding policy of the node to forward the received service data.
  • the service flow forwarding policy of the primary gateway includes the following: Which port in the aggregation port group is forwarded by the traffic flow received by the network, and which service port received by the aggregation port group is forwarded from the port.
  • Step 401 In a distributed link aggregation system, setting a first node as a primary gateway node of a certain service in each network;
  • Step 402 In the same network, setting the second node as the backup gateway node of the service; Step 403: The second node detects the path status of the first node;
  • Step 404 When the second node detects that the path with the first node fails, the second node switches to the primary gateway node of the service.
  • the detected path failure with the first node includes the following: detecting the first node failure, or detecting that the link between the local node and the first node is faulty.
  • Step 405 The second node performs service flow forwarding of the foregoing service.
  • the first node that is the primary gateway periodically sends its own service flow forwarding policy to the second node that is the backup gateway, and when the second node switches to the primary gateway node, according to the service flow forwarding policy of the first node.
  • the service flow forwarding policy of the local node is set, and the received service data is forwarded according to the service flow forwarding policy of the node.
  • the node that implements the foregoing method includes a detecting unit, a switching unit, and a forwarding unit, where: the detecting unit is configured to: when the node acts as a backup gateway for a service, detecting that the node and the service in the same network are used as the primary service a path of the node of the gateway; the switching unit is configured to: when the detecting unit detects that the path of the node and the node serving as the active gateway in the same network fails, the local node is switched to the primary gateway;
  • the forwarding unit is configured to: when the node is used as the primary gateway, forward the received data of the service.
  • the node further includes a service flow forwarding policy update unit and a service flow forwarding policy configuration unit, where:
  • the service flow forwarding policy update unit is configured to: when the node is used as the primary gateway, periodically update the service flow forwarding policy of the node to the node serving as the backup gateway for the same service in the same network;
  • the service flow forwarding policy configuration unit is configured to: after the node switches from the standby gateway to the primary gateway, configure the service flow forwarding policy of the node according to the service flow forwarding policy sent by the node that is the primary gateway;
  • the forwarding unit is configured to forward the received data of the service in the following manner: Forward the received service data by using the service flow forwarding policy of the node.
  • FIG. 5 is a schematic diagram of a gateway forwarding service flow in a distributed link aggregation system according to the example, including the following steps:
  • Step 501 In the network A, the designated node S1 is the primary gateway of the VLAN 1 on the NNI, and the node S3 is the backup gateway of the VLAN 1 on the N1;
  • Node S5 is the dual-homed node of network A.
  • the dual-homing technique is enabled on the node S5, and ports 5 and 6 are the first port and the second port, respectively.
  • Step 502 In the network B, the designated node S2 is the primary gateway of the VLAN 1 on the N1, and the node S4 is the backup gateway of the VLAN 1 on the N1;
  • steps 501 and 502 are not limited in the order of execution.
  • Step 503 the node S1 does not fail, the service flow of the VLAN 1 in the network A is forwarded to the node S1 through the first port 5 of the dual-homing node S5, the node S1 is the gateway node of the VLAN 1, and the service flow can be normally transmitted; and the node S1 Regularly update the service flow forwarding policy to the node S3;
  • Step 504 the node S3 detects the path status of the node S1;
  • steps 503 and 504 are not limited in order and can be performed simultaneously.
  • Step 505 When the node S1 fails, the node S3 detects the path failure with the S1, and the node S3 sets itself as the gateway node of the VLAN 1 service, and sets the service flow forwarding policy of the node according to the service flow forwarding policy sent by the node S1. ;
  • the dual-homing node S5 detects the link failure between the S5 and the S1
  • the service flow of the VLAN 1 is forwarded to the node S3 through the second port 6, and the node S3 receives the service flow of the VLAN 1.
  • Step 506 After receiving the service flow of the VLAN 1, the node S3 forwards the received service flow to the NI network according to the service flow forwarding policy of the node, and transmits the data flow to the gateway node of the other end network through the NI network, thereby forwarding the The other end of the network.
  • FIG. 6 is a schematic diagram of the intermediate link failover of the distributed link aggregation system in the present example, including: Step 601: In the network A, the designated node S1 is the primary gateway of VLAN 1 on the NNI, and node S3 is the backup gateway of VLAN 1 on the NI;
  • the node S5 is a dual-homed node or a ring network node of the network A.
  • the dual-homing technology or the ring network technology is enabled on the node S5, and the ports 5 and 6 are the first port and the second port, respectively.
  • Step 602 in the network B, the designated node S2 is the primary gateway of the VLAN 1 on the NNI, and the node S4 is the backup gateway of the VLAN 1 on the NNI;
  • steps 501 and 502 are not limited in the order of execution.
  • Step 603 When the link between the nodes S1 and S3 does not fail, the service flow of the VLAN 1 in the network A is forwarded to the node S1 through the first port 5 of the node S5, because the node S1 is the gateway node of the VLAN 1, the service flow Normally transmitting; and node S1 periodically updates the service flow forwarding policy to node S3;
  • Step 604 the node S3 detects the path status of the node S1;
  • steps 603 and 604 are not limited in order and can be performed simultaneously.
  • Step 605 When the link between the nodes S1 and S3 fails, the node S3 detects the path failure with the S1, and the node S3 sets itself as the gateway node of the VLAN 1 service, according to the service flow forwarding policy sent by the node S1.
  • the service flow forwarding policy of the node
  • Step 606 At this time, the nodes S1 and S3 are the gateway nodes of the VLAN 1 service. After receiving the service flows of the VLAN 1, the nodes S1 and S3 respectively forward the service flows according to the respective service flow forwarding policies.
  • the node S5 If the node S5 enables the dual-homing technique, the node S5 does not detect the link failure between S5 and S1, and does not perform the handover.
  • the service flow sent by the node S5 to the NI is still sent from the port 5, because the node S1 is still in the VLAN 1 At the gateway node, the traffic is still able to transmit normally.
  • node S5 may switch, and node S5 sends to NNI.
  • the service flow will be forwarded from the port 6 to the node S3, and the node S3 will receive the traffic of the VLAN 1. Since the node S3 has become the gateway node of the VLAN 1, the node S3 can normally forward the traffic after receiving the traffic of the VLAN 1.
  • the gateway node that transmits to the other end network through the NI network is forwarded to the other end of the network without interruption of service flow.
  • Node S1 and node S3 each maintain their own service flow forwarding policy.
  • the above method is used to implement the switching of the gateway node when the gateway fails, and enable the backup gateway to forward the service flow, thereby preventing the service flow interruption caused by the gateway failure.
  • the gateway node when the gateway node is not faulty, the gateway node performs the forwarding of the VLAN service flow.
  • the backup gateway automatically switches to the gateway of the VLAN service, and performs the service flow forwarding of the service VLAN service. Service flow interruption due to gateway failure is prevented. Therefore, the present invention has strong industrial applicability.

Landscapes

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

Abstract

一种分布式链路聚合***中业务流转发方法及节点，避免由于通路故障导致的业务流中断问题。所述方法包括：在分布式链路聚合***的每个网络中，针对业务分别设置作为主用网关的第一节点和作为备用网关的第二节点，所述第二节点检测到与第一节点的通路出现故障时，该第二节点切换为主用网关，对接收到的所述业务的数据进行转发。所述节点包括检测单元、切换单元和转发单元。根据上述方法，当网关节点没有故障时，由网关节点进行VLAN业务流的转发，当网关节点发生故障时，备用网关自动切换为该VLAN业务的网关，进行该业务VLAN业务的业务流转发，防止了由于网关的故障导致的业务流中断。

Description

一种分布式链路聚合***中业务流转发方法及节点
技术领域
本发明涉及网络通信技术， 尤其涉及一种基于分布式链路聚合***中业 务流转发方法及节点。
背景技术
在 IEEE 中定义的分布式链路聚合***中， 两个网络之间的通信需要将 多条物理链路的聚合起来形成一条链路， 这两个网络之间的互连节点分别可 能有多个。 为了降低网络的复杂度， 减少网络之间的耦合关系， 将网络和网 络之间的接口定义为网络节点接口 （ NNI, Network Node Interface ) , 当 NNI 的链路发生故障切换时， 只需要进行 NNI上的业务流进行切换， 对于 N I 两侧的网络，并不需要感知到 NNI的保护切换，也不需要进行业务流的切换。 为了便于这一思想的实施， 分布式链路聚合***在 N I的两侧网络中， 分别 基于每个虚拟局域网 （ VLAN, Virtual Local Area Network )指定了一个网关 ( Gateway ) , 当某个 VLAN的业务流从网络一侧进入 N I网络时 , 必须从 网关进入， 接着这个网络的网关将该 VLAN的业务流发送到 NNI网络中， N I网络将这个 VLAN的业务流转发到对端网络的该 VLAN的网关， 然后 对端网络的该 VLAN的网关再将这个业务流转发到对端网络内部， 实现了业 务从一个网络经过 N I, 传输到另外一个网络的流程。 但是， 如何保证网络 中某个 VLAN的业务流从该网关进入， 以及该网关节点故障后， 该业务流如 何重新传输等问题， 目前还没有定义。
如图 1所示， 网络 A和网络 B通过多条链路和多个节点互联， 其中节点 Sl、 S2、 S4和 S3组成的网络构成了 NNI网络， 在网络 A中， 指定了节点 S1为 N I上 VLAN 1的网关，在网络 B中，指定了节点 S2为 N I上 VLAN 1的网关。根据分布式链路聚合***的业务流转发流程，在网络 A中， VLAN 为 1的业务流将转发给节点 SI , 由于节点 SI为 VLAN 1的网关， 因此节点 S1将该业务流转发到 NNI网络上， 当节点 S2收到该业务流后， 由于节点 S2 为 VLAN 1的网关，因此节点 S2将该业务流转发到网络 B中，实现了 VLAN 1的业务流由网络 A经过 NNI向网络 B的转发流程。
然而， 当网关发生故障时， 该网关的 VLAN的业务流将既不能发送， 也 不能接收，导致该业务流中断。例如图 2所示，当节点 S1发生故障时， VLAN 1的业务流发送给节点 S1后， 节点 S1会丟弃该业务流， 不能将业务流转发 给 NNI网络， 因此网络 B无法收到 VLAN 1的业务流， 导致业务流中断。
在相关技术中， 当 N I节点故障后， 可以用网络内部的双归技术解决业 务流切换的问题，但是由于业务流切换后的发送的 N I节点并不是该业务的 网关， 仍然会导致业务流无法转发从而形成中断。 双归技术是在节点上指定 两个端口，分别为第一端口和第二端口，当第一端口和第二端口均为正常时， 节点的业务流在第一端口上转发， 当第一端口发生故障时， 节点的业务流在 第二端口上转发。 这种技术解决了当 N I网络节点故障后， 网络内部节点无 法将业务流发送给 N I网络节点的问题， 但是在分布式聚合链路***中， 当 网关节点发生故障后， 即使业务流发送到了 N I网络， 但是由于接收节点并 不是该业务 VLAN的网关节点， 业务流无法转发到 N I网络。 例如图 3所 示， 在节点 S5上启用双归技术， 端口 5和 6分别为第一端口和第二端口， 当节点 S1没有发生故障时，网络 A中 VLAN 1的业务流通过双归节点 S5的 第一端口 5转发给节点 S1 , 业务流能够正常传输， 当节点 S1发生故障时， 双归节点 S5检测到 S5和 S1之间的链路故障后进行切换， 将 VLAN 1的业 务流通过第二端口 6转发给节点 S3 , 节点 S3收到 VLAN 1的业务流。 但是 节点 S3并不是 VLAN 1的网关， 在节点 S3收到 VLAN 1的业务流后只能丟 弃， 还是无法转发到 N I网络， 因此相关技术并不能解决分布式链路聚合系 统网关故障导致的业务流中断问题。
发明内容
本发明实施例要解决的技术问题是提供一种分布式链路聚合***中业务 流转发方法及节点， 避免由于通路故障导致的业务流中断问题。
为解决上述技术问题， 本发明实施例釆用如下技术方案：
一种分布式链路聚合***中的业务流转发方法， 包括：
在分布式链路聚合***的每个网络中， 针对业务分别设置作为主用网关 的第一节点和作为备用网关的第二节点， 所述第二节点检测到与所述第一节 点的通路出现故障时， 该第二节点切换为主用网关， 对接收到的所述业务的 数据进行转发。
可选地， 所述方法还包括：
作为主用网关的所述第一节点定期向作为备用网关的所述第二节点发送 所述第一节点的业务流转发策略；
当所述第二节点切换为主用网关后， 根据所述第一节点发送的所述业务 流转发策略配置本节点的业务流转发策略， 使用本节点的业务流转发策略对 接收到的业务数据进行转发。
可选地， 所述第二节点检测到与所述第一节点的通路出现故障的步骤包 括：
所述第二节点检测到所述第一节点故障； 或者，
所述第二节点检测到本节点与所述第一节点间的链路故障。
可选地， 所述方法还包括：
所述第二节点检测到本节点与所述第一节点间的链路故障时， 所述第二 节点切换为主用网关， 所述第一节点继续作为主用网关对接收到的业务数据 进行转发。
可选地， 所述网络中， 除所述第一节点和所述第二节点之外的其他节点 釆用双归技术和 /或环网技术。
一种分布式链路聚合***中的节点， 包括检测单元、 切换单元和转发单 元， 其中：
所述检测单元设置成： 在本节点作为某业务的备用网关时， 检测本节点 与同一网络中作为所述业务的主用网关的节点的通路；
所述切换单元设置成： 在所述检测单元检测出本节点与同一网络中作为 所述业务的主用网关的节点的通路出现故障时， 将本节点切换为主用网关； 所述转发单元设置成： 在本节点作为主用网关时， 对接收到的所述业务 的数据进行转发。
可选地， 所述节点还包括业务流转发策略更新单元和业务流转发策略配 置单元， 其中：
所述业务流转发策略更新单元设置成： 在本节点作为主用网关时， 定期 向同一网络中作为所述业务的备用网关的节点发送本节点的业务流转发策略; 所述业务流转发策略配置单元设置成： 在本节点从备用网关切换为主用 网关后， 根据上次作为所述业务的主用网关的节点发送的业务流转发策略配 置本节点的业务流转发策略； 所述转发单元设置成釆用以下方式对接收到的所述业务的数据进行转发: 使用本节点的业务流转发策略对接收到的业务数据进行转发。
可选地， 所述通路出现故障包括：
所述作为所述业务的主用网关的节点故障； 或者，
作为所述业务的备用网关的节点与同一网络中作为所述业务的主用网关 的节点间的链路故障。
根据上述技术方案， 当网关节点没有故障时， 由网关节点进行 VLAN业 务流的转发， 当网关节点发生故障时， 备用网关自动切换为该 VLAN业务的 网关， 进行该业务 VLAN业务的业务流转发， 防止了由于网关的故障导致的 业务流中断。
附图概述
图 1为分布式链路聚合***的业务流转发示意图；
图 2为分布式链路聚合***中网关故障导致业务流中断的示意图； 图 3为双归节点进行业务流切换的示意图；
图 4为本发明实施例的实施流程的示意图；
图 5为本发明的实施例中分布式链路聚合***网关切换的示意图； 图 6为本发明的实施例中分布式链路聚合***中间链路故障切换示意图。 本发明的较佳实施方式
为使本发明的目的、 技术方案和优点更加清楚明白， 下文中将结合附图 对本发明的实施例进行详细说明。 需要说明的是， 在不冲突的情况下， 本申 请中的实施例及实施例中的特征可以相互任意组合。 本发明实施例提供的选择网关的方案如下：
在分布式链路聚合***的每个网络中， 针对业务分别设置作为主用网关 的第一节点和作为备用网关的第二节点， 该作为备用网关的第二节点检测到 同一网络中作为主用网关的第一网关节点的通路出现故障时， 该作为备用网 关的第二节点切换为主用网关， 对接收到的该业务的数据进行转发。
通过设置备用网关节点， 当主用网关节点发生故障时业务流能够从另外 一个节点传输， 保障了业务流不会中断。
可选地， 该作为主用网关的第一节点定期向作为备用网关的第二节点更 新该第一节点的业务流转发策略； 当作为备用网关的第二节点切换为主用网 关后， 根据第一节点发送的业务流转发策略配置本节点的业务流转发策略， 使用本节点的业务流转发策略对接收到的业务数据进行转发。 主用网关的业务流转发策略包括以下内容： 本网络接收到的业务流从聚 合端口组中的哪个端口转发出去， 以及聚合端口组接收到的业务流从本网络 哪个端口转发出去。 本发明的实施例如图 4所示， 包括以下步骤：
步骤 401 : 在分布式链路聚合***中， 在每个网络中设置第一节点为某 个业务的主用网关节点；
不同的业务会有不同的主备网关， 业务由 VLAN来区分。
步骤 402: 在同一个网络中， 设置第二节点为该业务的备用网关节点； 步骤 403: 第二节点检测与第一节点的通路状态；
当两节点之间的链路完好时，第一节点作为上述 VLAN业务的主用网关 节点。 步骤 404: 当第二节点检测到与第一节点的通路出现故障， 第二节点切 换为上述业务的主用网关节点；
对于第二节点而言， 其检测到的与第一节点的通路故障包括以下情况： 检测到第一节点故障 , 或检测到本节点与第一节点间的链路发生故障。
步骤 405: 第二节点进行上述业务的业务流转发。
可选地， 作为主用网关的第一节点定期向作为备用网关的第二节点发送 自己的业务流转发策略， 当第二节点切换为主用网关节点时， 根据第一节点 的业务流转发策略， 设置本节点的业务流转发策略， 并根据本节点的业务流 转发策略对接收到的业务数据进行转发。
实现上述方法的节点包括检测单元、 切换单元和转发单元， 其中： 该检测单元设置成： 在本节点作为针对某业务的备用网关时， 检测本节 点与同一网络中针对所述业务的作为主用网关的节点的通路； 该切换单元设置成： 在所述检测单元检测出本节点与同一网络中的作为 主用网关的节点的通路出现故障时， 将本节点切换为主用网关；
该转发单元设置成： 在本节点作为主用网关时， 对接收到的所述业务的 数据进行转发。
可选地， 该节点还包括业务流转发策略更新单元和业务流转发策略配置 单元， 其中：
该业务流转发策略更新单元设置成： 在本节点作为主用网关时， 定期向 同一网络中针对同一业务的作为备用网关的节点更新本节点的业务流转发策 略；
该业务流转发策略配置单元设置成： 在本节点从备用网关切换为主用网 关后， 根据上次作为主用网关的节点发送的业务流转发策略配置本节点的业 务流转发策略；
该转发单元设置成釆用以下方式对接收到的所述业务的数据进行转发： 使用本节点的业务流转发策略对接收到的业务数据进行转发。 下面结合具体实例对本发明的技术方案作进一步的详细描述。
示例一：
图 5为本示例的分布式链路聚合***中网关转发业务流的示意图， 包括 以下步骤：
步骤 501 , 在网络 A中， 指定节点 S1为 NNI上 VLAN 1的主用网关， 节点 S3为 N I上 VLAN 1的备用网关；
节点 S5为网络 A的双归节点， 在该节点 S5上启用双归技术， 端口 5和 6分别为第一端口和第二端口。
步骤 502, 在网络 B中， 指定节点 S2为 N I上 VLAN 1的主用网关， 节点 S4为 N I上 VLAN 1的备用网关；
上述步骤 501和 502执行顺序不限。
步骤 503 , 节点 S1没有发生故障， 网络 A中 VLAN 1的业务流通过双 归节点 S5的第一端口 5转发给节点 S1 ,节点 S1为 VLAN 1的网关节点， 业 务流能够正常传输； 且节点 S1定期向节点 S3更新业务流转发策略；
步骤 504, 节点 S3检测与节点 S1的通路状态；
上述步骤 503和 504顺序不限， 可同时执行。
步骤 505, 当节点 S1发生故障时， 节点 S3检测到与 S1的通路故障， 节 点 S3将自己设置为 VLAN 1业务的网关节点， 根据节点 S1发送的业务流转 发策略设置本节点的业务流转发策略；
当双归节点 S5检测到 S5和 S1之间的链路故障后进行切换，将 VLAN 1 的业务流通过第二端口 6转发给节点 S3 , 节点 S3收到 VLAN 1的业务流。
步骤 506, 节点 S3收到 VLAN 1的业务流后， 根据本节点的业务流转发 策略将接收到的业务流正常转发到 N I网络上， 通过 N I网络传输给另一 端网络的网关节点， 从而转发到另一端网络内部。
由于节点 S3在节点 S1发生故障时切换为 VLAN 1的网关节点， 因此不 会产生业务流中断。 示例二：
上述方法还可以应用于分布式链路聚合***中间链路故障的场景， 图 6 为本示例的分布式链路聚合***中间链路故障切换示意图， 包括： 步骤 601 , 在网络 A中， 指定节点 S1为 NNI上 VLAN 1的主用网关， 节点 S3为 N I上 VLAN 1的备用网关；
节点 S5为网络 A的双归节点或者环网节点，在节点 S5上启用双归技术 或者环网技术， 端口 5和 6分别为第一端口和第二端口。
步骤 602, 在网络 B中， 指定节点 S2为 NNI上 VLAN 1的主用网关， 节点 S4为 NNI上 VLAN 1的备用网关；
上述步骤 501和 502执行顺序不限。
步骤 603 , 当节点 S1和 S3之间链路没有发生故障时， 网络 A中 VLAN 1的业务流通过节点 S5的第一端口 5转发给节点 S1 , 由于节点 S1为 VLAN 1的网关节点， 业务流能够正常传输； 且节点 S1定期向节点 S3更新业务流 转发策略；
步骤 604, 节点 S3检测与节点 S1的通路状态；
上述步骤 603和 604顺序不限， 可同时执行。
步骤 605, 当节点 S1和 S3之间链路发生故障时， 节点 S3检测到与 S1 的通路故障， 节点 S3将自己设置为 VLAN 1业务的网关节点， 根据节点 S1 发送的业务流转发策略设置本节点的业务流转发策略；
步骤 606, 此时， 节点 S1和 S3都是 VLAN 1业务的网关节点， 节点 S1 和节点 S3各自收到 VLAN 1的业务流后， 分别按照各自的业务流转发策略 进行业务流转发。
如果节点 S5启用双归技术，则节点 S5没有检测到 S5和 S1之间的链路 故障， 不会进行切换， 节点 S5发给 N I的业务流仍然从端口 5发出， 由于 节点 S1还是 VLAN 1的网关节点， 业务流仍然能够正常传输。
如果节点 S5启用环网技术，则节点 S5可能进行切换，节点 S5发给 NNI 的业务流将从端口 6转发给节点 S3 , 节点 S3将会收到 VLAN 1的业务流， 由于节点 S3已经成为 VLAN 1的网关节点， 因此在节点 S3收到 VLAN 1的 业务流后能够正常转发到 N I网络上， 通过 N I网络传输给另一端网络的 网关节点， 从而转发到另一端网络内部， 不会产生业务流中断。
不论网络中其他节点釆用何种技术， 均可釆用方法实现业务流不中断。 节点 S1和节点 S3各自维护自己的业务流转发策略。
综上所述， 釆用上述方法， 实现了在网关发生故障时进行网关节点的切 换， 并启用备用网关进行业务流的转发， 防止了由于网关故障导致的业务流 中断。
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序 来指令相关硬件完成， 所述程序可以存储于计算机可读存储介质中， 如只读 存储器、 磁盘或光盘等。 可选地， 上述实施例的全部或部分步骤也可以使用 一个或多个集成电路来实现。 相应地， 上述实施例中的各模块 /单元可以釆用 硬件的形式实现， 也可以釆用软件功能模块的形式实现。 本发明不限制于任 何特定形式的硬件和软件的结合。
当然， 本发明还可有其他多种实施例， 在不背离本发明精神及其实质的 但这些相应的改变和变形都应属于本发明所附的权利要求的保护范围。
工业实用性
根据上述技术方案， 当网关节点没有故障时， 由网关节点进行 VLAN业 务流的转发， 当网关节点发生故障时， 备用网关自动切换为该 VLAN业务的 网关， 进行该业务 VLAN业务的业务流转发， 防止了由于网关的故障导致的 业务流中断。 因此本发明具有很强的工业实用性。

Claims

权 利 要 求 书
1、 一种分布式链路聚合***中的业务流转发方法， 包括：
在分布式链路聚合***的每个网络中， 针对业务分别设置作为主用网关 的第一节点和作为备用网关的第二节点， 所述第二节点检测到与所述第一节 点的通路出现故障时， 该第二节点切换为主用网关， 对接收到的所述业务的 数据进行转发。
2、 如权利要求 1所述的业务流转发方法， 所述方法还包括：
作为主用网关的所述第一节点定期向作为备用网关的所述第二节点发送 所述第一节点的业务流转发策略；
当所述第二节点切换为主用网关后， 根据所述第一节点发送的所述业务 流转发策略配置本节点的业务流转发策略， 使用本节点的业务流转发策略对 接收到的业务数据进行转发。
3、如权利要求 1或 2所述的业务流转发方法， 其中， 所述第二节点检测 到与所述第一节点的通路出现故障的步骤包括：
所述第二节点检测到所述第一节点故障； 或者，
所述第二节点检测到本节点与所述第一节点间的链路故障。
4、 如权利要求 3所述的业务流转发方法， 所述方法还包括：
所述第二节点检测到本节点与所述第一节点间的链路故障时， 所述第二 节点切换为主用网关， 所述第一节点继续作为主用网关对接收到的业务数据 进行转发。
5、 如权利要求 1所述的业务流转发方法， 其中：
所述网络中， 除所述第一节点和所述第二节点之外的其他节点釆用双归 技术和 /或环网技术。
6、 一种分布式链路聚合***中的节点， 包括检测单元、切换单元和转发 单元， 其中：
所述检测单元设置成： 在本节点作为某业务的备用网关时， 检测本节点 与同一网络中作为所述业务的主用网关的节点的通路； 所述切换单元设置成： 在所述检测单元检测出本节点与同一网络中作为 所述业务的主用网关的节点的通路出现故障时， 将本节点切换为主用网关； 所述转发单元设置成： 在本节点作为主用网关时， 对接收到的所述业务 的数据进行转发。
7、如权利要求 6所述的节点，所述节点还包括业务流转发策略更新单元 和业务流转发策略配置单元， 其中：
所述业务流转发策略更新单元设置成： 在本节点作为主用网关时， 定期 向同一网络中作为所述业务的备用网关的节点发送本节点的业务流转发策略; 所述业务流转发策略配置单元设置成： 在本节点从备用网关切换为主用 网关后， 根据上次作为所述业务的主用网关的节点发送的业务流转发策略配 置本节点的业务流转发策略； 所述转发单元设置成釆用以下方式对接收到的所述业务的数据进行转发: 使用本节点的业务流转发策略对接收到的业务数据进行转发。
8、 如权利要求 6所述的节点， 其中： 所述通路出现故障包括：
所述作为所述业务的主用网关的节点故障； 或者，
作为所述业务的备用网关的节点与同一网络中作为所述业务的主用网关 的节点间的链路故障。
PCT/CN2012/077139 2011-07-01 2012-06-19 一种分布式链路聚合***中业务流转发方法及节点 WO2013004124A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110184347.2 2011-07-01
CN2011101843472A CN102857423A (zh) 2011-07-01 2011-07-01 一种分布式链路聚合***中业务流转发方法及节点

Publications (1)

Publication Number Publication Date
WO2013004124A1 true WO2013004124A1 (zh) 2013-01-10

Family

ID=47403627

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/077139 WO2013004124A1 (zh) 2011-07-01 2012-06-19 一种分布式链路聚合***中业务流转发方法及节点

Country Status (2)

Country Link
CN (1) CN102857423A (zh)
WO (1) WO2013004124A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107666402B (zh) * 2016-07-27 2020-07-07 新华三技术有限公司 网络服务控制方法和装置
EP3493488B1 (en) 2016-07-27 2020-12-30 New H3C Technologies Co., Ltd. Processing of data stream
CN108667640B (zh) * 2017-03-29 2021-09-07 北京华为数字技术有限公司 通信方法及设备、网络接入***
CN108737260A (zh) * 2017-04-13 2018-11-02 ***通信集团上海有限公司 一种行业短信发送方法、控制器、交换机及***

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1553628A (zh) * 2003-06-04 2004-12-08 深圳市中兴通讯股份有限公司南京分公 基于策略路由实现链路聚合功能的方法
CN101257490A (zh) * 2008-02-03 2008-09-03 杭州华三通信技术有限公司 一种防火墙旁路模式下的报文处理方法和***
CN101841408A (zh) * 2010-05-07 2010-09-22 北京星网锐捷网络技术有限公司 主备路由设备切换方法及路由设备
CN102088400A (zh) * 2009-12-03 2011-06-08 华为技术有限公司 虚拟专用网络中运营商边界设备及切换方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4757719B2 (ja) * 2006-06-21 2011-08-24 Ｎｅｃインフロンティア株式会社 ネットワークシステム、ｉｐ電話端末及びそれらに用いるネットワーク機器切替え方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1553628A (zh) * 2003-06-04 2004-12-08 深圳市中兴通讯股份有限公司南京分公 基于策略路由实现链路聚合功能的方法
CN101257490A (zh) * 2008-02-03 2008-09-03 杭州华三通信技术有限公司 一种防火墙旁路模式下的报文处理方法和***
CN102088400A (zh) * 2009-12-03 2011-06-08 华为技术有限公司 虚拟专用网络中运营商边界设备及切换方法
CN101841408A (zh) * 2010-05-07 2010-09-22 北京星网锐捷网络技术有限公司 主备路由设备切换方法及路由设备

Also Published As

Publication number Publication date
CN102857423A (zh) 2013-01-02

Similar Documents

Publication Publication Date Title
US8724452B2 (en) Technique for protecting communication traffic in a connection having redundancy
EP2518954B1 (en) Redundant ethernet automatic protection switching access to virtual private lan services.
JP4848254B2 (ja) リングネットワークを構成する装置
US10708081B2 (en) Failure protection method based on ring protection link, device, and system
JP4628945B2 (ja) レイヤ２ネットワーク
EP1958364B1 (en) Vpls remote failure indication
WO2012028029A1 (zh) 一种切换方法及***
CN103051536A (zh) 一种二层冗余链路的快速组播切换方法
JP2013519268A (ja) データ転送方法、データ転送装置及びデータ転送システム
WO2010022576A1 (zh) 基于以太多环网的控制报文的传输方法和装置
WO2009111969A1 (zh) 以太环网中边缘端口阻塞的方法、以太环网***和设备
WO2012171378A1 (zh) 解决vpls接入l3故障切换导致断流的方法及路由器
WO2010031295A1 (zh) 一种以太网故障恢复的控制方法
WO2014063571A1 (zh) 一种分布式链路聚合组业务切换方法和装置
US9716639B2 (en) Protection switching method and system
WO2013004124A1 (zh) 一种分布式链路聚合***中业务流转发方法及节点
WO2009111955A1 (zh) 以太环网节点地址表更新方法
JP2013239909A (ja) 通信システムおよび通信制御方法
EP3462681B1 (en) Apparatus and method for transmitting multicast service
WO2011011934A1 (zh) 一种以太网隧道分段保护方法和装置
WO2009146580A1 (zh) 一种地址转发表更新方法
WO2008110086A1 (fr) Procédé de protection contre la redondance et système pour anneaux résilients de paquets en mode pont
WO2010031211A1 (zh) 一种以太多环网的控制信道配置及其报文传输方法
WO2013064027A1 (zh) 一种跨环业务的保护方法及装置
JP2009004854A (ja) 通信システム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12807313

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

Country of ref document: EP

Kind code of ref document: A1