WO2022068736A1 - 转发流量的方法及设备 - Google Patents

转发流量的方法及设备 Download PDF

Info

Publication number
WO2022068736A1
WO2022068736A1 PCT/CN2021/120741 CN2021120741W WO2022068736A1 WO 2022068736 A1 WO2022068736 A1 WO 2022068736A1 CN 2021120741 W CN2021120741 W CN 2021120741W WO 2022068736 A1 WO2022068736 A1 WO 2022068736A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
traffic
network
link
forwarding
Prior art date
Application number
PCT/CN2021/120741
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 WO2022068736A1 publication Critical patent/WO2022068736A1/zh

Links

Images

Classifications

    • 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/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • 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
    • 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
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • 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/74—Address processing for routing

Definitions

  • the present invention relates to the field of communication technologies, and in particular, to a method and device for forwarding traffic.
  • Ethernet virtual private network (EVPN) replacing virtual private LAN service (VPLS)
  • EVPN interworking is deployed between provider edge devices (PEs) in EVPN.
  • PEs provider edge devices
  • user-side devices such as customer edge devices (customedge, CE) are multi-homed to multiple PEs, or
  • CE customer edge devices
  • the CE is multi-homed to the multiple PEs through the switch, and the Ethernet segment identifiers (ESIs) of the links between the user-side equipment and the multiple PEs need to be configured differently.
  • ESA Ethernet segment identifiers
  • the ring network attached to the EVPN fails, the Ethernet ring protection switching (ERPS) protocol of the ring network can be triggered, so that the PE can clear the stored data of the devices in the network topology.
  • ERPS Ethernet ring protection switching
  • the present application provides a method and device for forwarding traffic, which can solve the problem of user-side equipment in the case that the user-side equipment is multi-homed to multiple PEs, and the ESI configurations of the links between the user-side equipment and the multiple PEs are different.
  • the problem of long-term packet loss after the link between the side device and the PE is faulty.
  • the present application provides a method for forwarding traffic, the method comprising:
  • the first network device receives first traffic from the second network device, the destination address of the first traffic is the first device, and the first network device and the second network device are service provider edge PEs in the network devices, the first device is multi-homed to the first network device and the second network device through the first link and the second link respectively, and the Ethernet of the first link and the second link
  • the link identifiers ESI are different; the first network device sends the first traffic to the first device.
  • the above-mentioned network devices may be devices in an EVPN network
  • the above-mentioned first device may be a user-side device in a ring network connected to the EVPN network
  • the first device is a multi-homing access EVPN network.
  • the first network device and the second network device, and the ESIs of the first device accessing the first network device and the second network device are different.
  • the path such as access
  • the first traffic is forwarded to the first device through the second network device
  • the second network device In order to reduce traffic packet loss
  • the second network device receives the traffic sent from the third network device to the first device, that is, the above-mentioned first traffic, it can forward the traffic to the first network device, and the first network device forwards the traffic to the first network device. device, so that the first device can normally receive traffic and reduce the probability of service interruption.
  • the method before the first network device sends the first traffic to the first device, the method further includes: the first network device determines, by the first network device, all data in the local traffic feature table
  • the mapping device of the first traffic is not a third network device, the third network device is a PE device in the network, and the third network device is connected to the first network device and the second network device respectively.
  • the above-mentioned first network device determines that the source device of the first traffic described in the local traffic feature table is not the third network device, including the following two situations:
  • the first network device determines that the mapping device of the first traffic in the local traffic feature table is the second network device
  • the first network device determines that the local traffic characteristic table does not indicate a mapping device for the first traffic; in this case, the first network device may set the first traffic in the local traffic characteristic table
  • the mapping device is the second network device.
  • the traffic feature table in this application is used in the first network device to record the information of the traffic sent from the second network device, and record the information that the corresponding traffic reaches the mapping device of the first network device, so as to know whether the traffic is For the traffic forwarded through the second network device.
  • the traffic characteristic table is used to monitor the traffic received by the first network device from the second network device after the above-mentioned fault occurs.
  • the method further includes:
  • the first network device receives the first traffic from the third network device
  • the first network device sets the mapping device for the first flow in the local flow characteristic table to for the third network device;
  • the first network device sends the first traffic from the third network device to the first device.
  • the first network device receives the first traffic from the second network device again;
  • the mapping device of the first traffic in the local traffic characteristic table is the third network device
  • the first network device discards the second received from the first network device. a flow.
  • the first network device can receive the first traffic from the third network device, indicating that the first traffic can be forwarded normally, and there will be no problem of packet loss.
  • the first network device can normally forward the first traffic from the third network device, and mark in the traffic feature table that the first traffic can be received from the third network device, so that when the first traffic from the second network device is received again. When there is one flow, it can be discarded, thereby avoiding the problem of multiple packets of the first flow.
  • the method further includes: receiving, by the first network device, second traffic from the third network device; not including the second traffic in the local traffic feature table information, the first network device sends the second traffic to the second device in the network.
  • the first network device can still normally forward the traffic that is not affected by the fault, and before forwarding the traffic, check whether there is information on the traffic in the traffic feature table, and forward the traffic normally if not, this is also to avoid traffic The problem of multiple packages.
  • the first traffic carries a label
  • the label indicates that the first traffic comes from the second network device.
  • the first traffic from the second network device is identified by the label, which can clearly distinguish which traffic is affected by the fault, so that these traffics can be monitored and forwarded.
  • the sending, by the first network device, the first traffic to the first device includes: when a timer is started and the preset time period is not reached, the first network device sends the first traffic to the first device.
  • the device sends the first traffic to the first device, wherein the timer is started after the first network device senses the failure of the communication link between the second network device and the first device of.
  • a timer can be set to monitor the time period during which the traffic affected by the fault cannot be forwarded normally, which can reduce the cause of the first network device still processing the traffic according to the operation when the traffic cannot be normally forwarded after the traffic affected by the fault can be normally forwarded. waste of resources.
  • the method further includes: receiving, by the first network device, a notification from the third network device, where the notification is used to indicate that the first network device does not need to forward the notification from the third network device. the first traffic of the second network device; the first network device receives the first traffic from the second network device again, and in response to the notification, discards the re-received traffic from the second network device the first traffic of the network device.
  • the first network device when the first network device receives the traffic from the second network device due to the above failure, it will generally forward it, but when the first network device receives the above notification from the third network device , indicating that the traffic affected by the fault can be forwarded normally. Therefore, the traffic from the second network device will not be forwarded, thereby solving the problem of multiple packets of these traffic.
  • the method further includes: the first network device receives the first traffic from the third network device; the first network device sends the first traffic to the first device the first traffic from the third network device.
  • the first network device can normally forward the traffic.
  • all packets in the first traffic have the same feature, and the feature includes a 2-tuple, a 4-tuple, a 5-tuple or a 7-tuple.
  • the destination MAC address of the first traffic is the MAC address of the first device.
  • the present application provides a method for forwarding traffic, the method comprising:
  • the first network device sends first traffic to the second network device, and the destination address of the first traffic is the first device; the first network device and the second network device are service provider edge PE devices in the network , the first device is multi-homed to the first network device and the second network device through the first link and the second link respectively, and the Ethernet of the first link and the second link
  • the network link identifier ESI is different.
  • the above-mentioned network devices may be devices in an EVPN network
  • the above-mentioned first device may be a user-side device in a ring network connected to the EVPN network
  • the first device is a multi-homing access EVPN network.
  • the first network device and the second network device, and the ESIs of the first device accessing the first network device and the second network device are different.
  • the path such as access
  • the first traffic is forwarded to the first device through the first network device
  • the first network device receives the traffic sent from the third network device to the first device, that is, the above-mentioned first traffic, it can forward the traffic to the second network device, and the second network device forwards the traffic to the first device. device, so that the first device can normally receive traffic and reduce the probability of service interruption.
  • the method further includes: the first network device broadcasts the first traffic through an AC interface of an access link.
  • the traffic from the third network device can also be broadcast to the user-side device connected to the first network device. If the traffic is not the traffic affected by the above fault, the traffic can be normally forwarded to the destination.
  • the first network device sending the first traffic to the second network device includes: a communication link between the first network device and the first device occurs In case of failure, the first network device sends the first traffic to the second network device.
  • the first network device sends a message to the second network device
  • Sending the first traffic includes: in the case that the MAC address of the first device cannot match an entry in the local media access control MAC address forwarding table of the first network device, sending the first network device to the The second network device sends the first traffic.
  • the traffic received by the first network device from the third network device after the failure may not be matched Forwarding table entry, then the traffic can be sent to the second network device for forwarding, thereby reducing traffic packet loss.
  • the sending, by the first network device, the first traffic to the second network device includes: when a timer is started and the preset duration is not reached, the first network device sends the first traffic to the second network device. Sending the first traffic to the second network device, wherein the timer is started after the first network device senses the failure of the communication link between the first network device and the first device of.
  • a timer can be set to monitor the time period during which the traffic affected by the fault cannot be forwarded normally, which can reduce the resources caused by the first network device continuing to send the traffic to the second network device after the traffic affected by the fault can be forwarded normally. waste.
  • the first traffic carries a label
  • the label indicates that the first traffic comes from the first network device.
  • the first traffic from the first network device is identified by the label, which can clearly distinguish which traffic is affected by the fault, so that these traffics can be monitored and forwarded.
  • the method further includes: the first network device receives the second traffic; the first network device sends the second traffic according to a local MAC address forwarding table.
  • the method further includes: the first network device receives third traffic through an AC interface of an access link; when the destination MAC address of the third traffic cannot match the third traffic In the case of an entry in a local MAC address forwarding table of a network device, the first network device broadcasts the third traffic to network devices in the network.
  • the above two embodiments both show that after the above fault occurs, the first network device can still normally forward traffic that is not affected by the fault.
  • the sending, by the first network device, the first traffic to the second network device includes: acquiring, by the first network device, a default route, where the default route is used in the first network device When the communication link between a network device and the first device fails, send the first traffic from the third network device to the second network device; the first network device according to the The default route sends the first traffic to the second network device.
  • the first network device can send the traffic from the third network device to the second network device because the default route configured in the first network device in advance can realize the above avoidance of traffic Packet loss operation.
  • the present application provides a method for forwarding traffic, the method comprising:
  • the first network device sends a notification to the second network device, and the notification is used to indicate that the second network device does not need to forward the first traffic from the third network device; the destination address of the first traffic is the first device, so the
  • the first network device, the second network device and the third network device are service provider edge PE devices in the network, and the first network device is respectively connected to the second network device and the third network equipment, the first equipment is multi-homing to the second network equipment and the third network equipment through the first link and the second link respectively, the first link and the second link Ethernet link identification ESI is different.
  • the above-mentioned network devices may be devices in an EVPN network
  • the above-mentioned first device may be a user-side device in a ring network connected to the EVPN network
  • the first device is a multi-homing access EVPN network.
  • the second network device and the third network device, and the ESIs of the first device accessing the second network device and the third network device are different.
  • the path such as access
  • the first traffic is forwarded to the first device through the third network device
  • the second network device receives the traffic sent from the third network device to the first device, that is, the above-mentioned first traffic (the third network device receives the first traffic from the first network device), it can forward the traffic to the first device, so that the first device can normally receive traffic and reduce the probability of service interruption.
  • the first network device can normally forward the first traffic to the second network device.
  • the second network device does not need to forward the first traffic from the third network device. Therefore, the first network device can send a notification to the second network device that there is no need to forward the first traffic from the third network device, thereby solving the problem of multiple packets of the first traffic.
  • the MAC route of the first device includes the MAC address of the first device and corresponding next hop information, where the next hop may be the address of the next hop device of the first device, or the first device goes to the next hop Jump the outbound interface of the device, etc.
  • the present application provides a method for forwarding traffic, the method comprising:
  • the second network device Broadcast the first traffic to network devices in the network, the destination address of the first traffic is the first device, the network devices in the network include a third network device, the first network device, the second network device The network device and the third network device are service provider edge PE devices in the network, the second network device is respectively connected to the first network device and the third network device, and the first device is respectively The first network device and the third network device are multihomed through a first link and a second link, where the Ethernet link identifiers ESI of the first link and the second link are different.
  • the above-mentioned network devices may be devices in an EVPN network
  • the above-mentioned first device may be a user-side device in a ring network connected to the EVPN network
  • the first device is a multi-homing access EVPN network.
  • the first network device and the third network device, and the ESIs of the first device accessing the first network device and the third network device are different.
  • the path such as access
  • the first traffic is forwarded to the first device through the first network device
  • the second network device In order to reduce traffic packet loss time, when the first network device sends a notification of clearing the MAC to the second network device due to the fault, the second network device uniformly broadcasts the received first traffic, and after the third network device receives the broadcasted first traffic, can be forwarded to the first device. After the second network device relearns the MAC route of the first traffic, it stops broadcasting the first traffic, and can forward traffic according to the new learned route, so that the first device can receive traffic normally and reduce service interruption. The probability.
  • the present application provides a method for forwarding traffic, the method comprising:
  • the first network device receives the first traffic broadcasted by the second network device, where the first traffic is after the communication link between the third network device and the first destination device fails by the first network device, and Broadcast by the second network device without clearing the MAC address of the first device based on the fault, and the first network device, the second network device, and the third network device are The service provider edge PE device, the second network device is respectively connected to the first network device and the third network device, and the first device is multi-homed to the network through the first link and the second link respectively. the first network device and the third network device, the Ethernet link identifiers ESI of the first link and the second link are different; the first network device sends the first device to the first flow.
  • the above-mentioned network devices may be devices in an EVPN network
  • the above-mentioned first device may be a user-side device in a ring network connected to the EVPN network
  • the first device is a multi-homing access EVPN network.
  • the first network device and the third network device, and the ESIs of the first device accessing the first network device and the third network device are different.
  • the path such as access
  • the first traffic is forwarded to the first device through the third network device
  • the second network device In order to reduce traffic packet loss
  • the third network device sends a notification of clearing the MAC to the second network device due to the fault, the second network device uniformly broadcasts the received first traffic, and the first network device receives the first traffic and forwards it to the first device, so that the first device can normally receive traffic and reduce the probability of service interruption.
  • the present application provides a device for forwarding traffic, the device comprising:
  • a receiving unit configured to receive first traffic from a second network device, the destination address of the first traffic is the first device, and the device forwarding traffic and the second network device are service provider edges in the network PE device, the first device is multi-homed to the device for forwarding traffic and the second network device through the first link and the second link respectively, the Ethernet of the first link and the second link
  • the network link identification ESI is different;
  • a sending unit configured to send the first traffic to the first device.
  • the device before the sending unit sends the first traffic to the first device, the device further includes:
  • a determining unit configured to determine that the mapping device of the first traffic in the local traffic characteristic table is not a third network device, the third network device is a PE device in the network, and the third network device is connected to the A device for forwarding traffic and the second network device.
  • the above determining unit determines that the source device of the first traffic in the local traffic feature table is not the third network device, including the following two situations:
  • the determining unit determines that the mapping device of the first traffic in the local traffic characteristic table is the second network device
  • the determining unit determines that the local traffic feature table does not indicate the mapping device of the first traffic; in this case, the device that forwards traffic may set the mapping of the first traffic in the local traffic feature table
  • the device is the second network device.
  • the above receiving unit is further configured to receive the first traffic from the third network device
  • the above-mentioned device for forwarding traffic further includes a setting unit, configured to set the first traffic in the local traffic feature table to the third network device when the mapping device for the first traffic in the local traffic feature table is not the third network device.
  • a traffic mapping device is set as the third network device;
  • the above sending unit is further configured to send the first traffic from the third network device to the first device.
  • the above receiving unit is further configured to receive the first traffic from the second network device again;
  • the device for forwarding traffic further includes a discarding unit, configured to discard the re-received traffic from the forwarding when the device for mapping the first traffic in the local traffic feature table is the third network device the first flow of the device.
  • the above receiving unit is further configured to receive the second traffic from the third network device
  • the above-mentioned sending unit is further configured to send the second flow to the second device in the network when the local flow characteristic table does not include the information of the second flow.
  • the first traffic carries a label
  • the label indicates that the first traffic comes from the second network device.
  • the above-mentioned sending unit is specifically configured to: send the first traffic to the first device when a timer is started and the preset duration does not reach, wherein the timer It is started for the device forwarding traffic after sensing the failure of the communication link between the second network device and the first device.
  • the receiving unit is further configured to receive a notification from the third network device, where the notification is used to indicate that the device forwarding traffic does not need to forward the data from the second network device the first flow;
  • the above receiving unit is further configured to receive the first traffic from the second network device again;
  • the above device for forwarding traffic further includes a discarding unit, configured to discard the first traffic received from the second network device again in response to the notification.
  • the above receiving unit is further configured to receive the first traffic from the third network device
  • the above sending unit is further configured to send the first traffic from the third network device to the first device.
  • all packets in the first traffic have the same feature, and the feature includes a 2-tuple, a 4-tuple, a 5-tuple or a 7-tuple.
  • the destination MAC address of the first traffic is the MAC address of the first device.
  • the present application provides a device for forwarding traffic, the device comprising:
  • a sending unit configured to send first traffic to a second network device, where the destination address of the first traffic is the first device; the device that forwards traffic and the second network device are service provider edge PEs in the network device, the first device is multihomed to the device for forwarding traffic and the second network device through the first link and the second link respectively, the first link and the second link Ethernet link identification ESI is different.
  • the device for forwarding traffic further includes a broadcasting unit, configured to broadcast the first traffic through the AC interface of the access link.
  • the sending unit is specifically configured to: in the case of a failure of the communication link between the traffic forwarding device and the first device, send a message to the second network device The first traffic is sent.
  • the sending unit is specifically configured to: when the MAC address of the first device cannot match an entry in the local media access control MAC address forwarding table of the device forwarding traffic In this case, the first traffic is sent to the second network device.
  • the sending unit is specifically configured to: when the timer is started and the preset time period is not reached, the device for forwarding traffic sends the first network device to the second network device. traffic, wherein the timer is started after the device forwarding traffic senses the failure of the communication link between the device forwarding traffic and the first device.
  • the first traffic carries a label
  • the label indicates that the first traffic comes from the device that forwards the traffic.
  • the above receiving unit is further configured to receive the second traffic
  • the above sending unit is further configured to send the second traffic according to the local MAC address forwarding table.
  • the above receiving unit is further configured to: receive the third traffic through the AC interface of the access link;
  • the above-mentioned sending unit is further configured to broadcast the information to the network devices in the network when the destination MAC address of the third traffic cannot match the entry in the local MAC address forwarding table of the device that forwards the traffic. the third flow.
  • the device for forwarding traffic further includes an obtaining unit: configured to obtain a default route, where the default route is used for the communication between the device for forwarding traffic and the first device sending the first traffic from the third network device to the second network device when the communication link fails;
  • the above sending unit is specifically configured to: send the first traffic to the second network device according to the default route.
  • the present application provides a device for forwarding traffic, the device comprising:
  • a sending unit configured to send a notification to the second network device, where the notification is used to indicate that the second network device does not need to forward the first traffic from the third network device; the destination address of the first traffic is the first device,
  • the device for forwarding traffic, the second network device, and the third network device are service provider edge PE devices in the network, and the device for forwarding traffic is respectively connected to the second network device and the third network device.
  • the Ethernet link identifies the ESI differently.
  • the present application provides a device for forwarding traffic, the device comprising:
  • the broadcasting unit is configured to, after the communication link between the first network device and the first device fails, and the device forwarding traffic does not clear the MAC address of the first device based on the failure, send the A network device in the network broadcasts the first traffic, the destination address of the first traffic is the first device, the network device in the network includes a third network device, the first network device, the forwarding traffic
  • the device and the third network device are service provider edge PE devices in the network, the device for forwarding traffic is connected to the first network device and the third network device respectively, and the first device passes through the The first link and the second link are multihomed to the first network device and the third network device, and the Ethernet link identifiers ESI of the first link and the second link are different.
  • the present application provides a device for forwarding traffic, the device comprising:
  • a receiving unit configured to receive the first traffic broadcast by the second network device, where the first traffic is the device that forwards the traffic after the communication link between the third network device and the first destination device fails, And if the second network device does not clear the MAC address of the first device based on the fault, the device that forwards traffic, the second network device, and the third network device are in the network.
  • the service provider edge PE device the second network device is respectively connected to the traffic forwarding device and the third network device, the first device is multi-homing access through the first link and the second link respectively
  • the device that forwards traffic and the third network device have different Ethernet link identifiers ESIs of the first link and the second link; the device that forwards traffic sends all information to the first device. the first flow.
  • the present application provides a device for forwarding traffic, including a processor, a communication interface and a memory, wherein the memory is used to store program instructions and/or data, and the processor is used to execute the memory stored in the memory
  • the program instructions of the device cause the device to execute the method described in any one of the above first aspects.
  • the present application provides a device for forwarding traffic, including a processor, a communication interface, and a memory, wherein the memory is used to store program instructions and/or data, and the processor is used to execute the memory stored in the memory
  • the program instructions make the device execute the method described in any one of the second aspect above.
  • the present application provides a device for forwarding traffic, including a processor, a communication interface and a memory, wherein the memory is used to store program instructions and/or data, and the processor is used to execute the memory stored in the memory
  • the program instructions of the device cause the device to execute the method described in any one of the above third aspects.
  • the present application provides a device for forwarding traffic, including a processor, a communication interface, and a memory, wherein the memory is used to store program instructions and/or data, and the processor is used to execute the memory stored in the memory
  • the program instructions of the device cause the device to execute the method described in any one of the fourth aspects above.
  • the present application provides a device for forwarding traffic, including a processor, a communication interface, and a memory, wherein the memory is used to store program instructions and/or data, and the processor is used to execute the memory stored in the memory
  • the program instructions of the device cause the device to execute the method described in any one of the fifth aspects above.
  • the present application provides a system for forwarding traffic, the system includes a first network device and a second network device, wherein the first network device is the device described in the sixth aspect, and the second network device is the device described in the seventh aspect; or, the first network device is the device described in the eleventh aspect, and the second network device is the device described in the twelfth aspect.
  • the present application provides a system for forwarding traffic, the system includes a first network device and a second network device, wherein the first network device is the device described in the sixth aspect, and the second network device is the device described in the eighth aspect; or, the first network device is the device described in the eleventh aspect, and the second network device is the device described in the thirteenth aspect.
  • the present application provides a system for forwarding traffic, the system includes a first network device and a second network device, wherein the first network device is the device described in the ninth aspect, and the second network device is the device described in the tenth aspect; or, the first network device is the device described in the fourteenth aspect, and the second network device is the device described in the fifteenth aspect.
  • the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement the method described in any one of the above-mentioned first aspect; Or, the computer program is executed by a processor to implement the method described in any one of the above second aspects; or, the computer program is executed by a processor to implement any one of the methods described in the third aspect above; or, The computer program is executed by the processor to implement the method described in any one of the above fourth aspects; or, the computer program is executed by the processor to realize the method described in any one of the above fifth aspects.
  • the present application provides a computer program product, when the above computer program product is read and executed by a computer, any one of the above methods in the above first aspect will be executed; or, when the above computer program product is read and executed by a computer When read and executed, any one of the above-mentioned methods in the above second aspect will be executed; or, when the above-mentioned computer program product is read and executed by a computer, any one of the above-mentioned methods in the above-mentioned third aspect will be executed; or , when the above-mentioned computer program product is read and executed by a computer, any one of the above-mentioned methods in the above-mentioned fourth aspect will be executed; or, when the above-mentioned computer program product is read and executed by a computer, any one of the above-mentioned fifth aspects will be executed.
  • the above method will be executed.
  • the present application can solve the problem between the user-side equipment and the PEs when the user-side equipment is multi-homed to multiple PEs, and the ESI configurations of the links between the user-side equipment and the multiple PEs are different.
  • the problem of packet loss for a long time after the link between them fails.
  • 1 to 3 are schematic diagrams of system scenarios to which a method for forwarding traffic provided by the present application is applicable;
  • FIG. 4 is a schematic flowchart of a method for forwarding traffic provided by an embodiment of the present application
  • FIG. 5 is a schematic flowchart of another method for forwarding traffic provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a logical structure of a device provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a logical structure of another device provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a logical structure of another device provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a logical structure of another device provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a logical structure of another device provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a hardware structure of a device provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a communication network architecture to which the method for forwarding traffic provided by an embodiment of the present invention is applicable.
  • the communication network architecture may include network equipment and user-side equipment. As shown in the figure, the network equipment establishes communication connections with each other, and the user-side equipment is multi-homed to the network equipment in a ring network networking manner. For example, the user in FIG. 1 The side equipment 111 , the user side equipment 112 , the user side equipment 113 and the user side equipment 114 are dual-homed to the network equipment 101 and the network equipment 102 by means of a ring network.
  • the network device may include a provider edge device (provider edge, PE), and the provider edge device PE may be a router or a switch, which is used to connect the user-side device and the operator's backbone network device. User traffic flows into the user network through the PE device, or flows to the backbone network through the PE device.
  • PE provider edge
  • the user-side equipment may include a customer edge device (customer edge, CE).
  • the CE is a router or switch on the user-side connected to the service provider, and the CE provides service access for users by connecting one or more PEs.
  • the user-side device may establish a communication connection with one or more user terminals, and the user terminals may include various electronic devices such as mobile phones, computers, wearable smart devices, and vehicle-mounted devices.
  • the above-mentioned communication network architecture shown in FIG. 1 is only an example, for example, one or more network devices may be included between the network device 101 and the network device 103 , the dual-homing access network device 101 and the network device 102
  • the user-side devices of the device are not limited to the form and number shown in FIG. 1 and so on.
  • the communication network architecture to which the traffic forwarding method provided by the embodiment of the present application is applicable is not limited to the above description. As long as it is applied to the scenario of the traffic forwarding method provided by the embodiment of the present application, it is the applicable scene of the embodiment of the present application. No longer.
  • the communication network architecture to which the traffic forwarding method provided in the embodiment of the present application is applicable may be a virtual private network (virtual private network, VPN), a virtual private local area network service (virtual private LAN service, VPLS), or an Ethernet virtual private network (Ethernet virtual private network).
  • network, EVPN) architecture, etc. in particular, it can be a dual-homing or multi-homing scenario in the network.
  • FIG. 2 is obtained by adding relevant information on the basis of FIG. 1 . Therefore, the above description of FIG. 1 applies to FIG. 2 .
  • the user-side equipment is dual-homed to the network equipment 101 and the network equipment 102 through the ring network.
  • a destruction protocol needs to be deployed in the ring network.
  • the above-mentioned traffic looping refers to the phenomenon that the device sends and receives traffic spontaneously.
  • an example is given below. Referring to Figure 2, assuming that no destruction protocol is deployed, then there is no destruction point in the ring network, and each link can communicate normally.
  • the traffic reaches the network device 101 through the user-side device 111, the network device 101 can send the traffic to the network devices 102 and 103, and after the network device 102 receives the traffic, it may pass the forwarding path:
  • the user-side device 114 - the user-side device 113 - the user-side device 112 forward the traffic back to the user-side device 112 , thereby causing the traffic to form a loop.
  • the destruction protocol may include multi spanning tree protocol (MSTP) and Ethernet ring protection switching (Ethernet ring protection switching, ERPS) protocol, etc.
  • MSTP multi spanning tree protocol
  • ERPS Ethernet ring protection switching
  • a breaking point can be formed in the ring network to avoid traffic looping.
  • the destruction point is generally set in the link between two devices, so that the link is blocked, thereby avoiding traffic looping.
  • FIG. 2 it is assumed that the damage point can be set in the link between the user-side device 112 and the user-side device 113, so that the traffic sent by the user-side device 112 can no longer be forwarded back to the user-side device 112, Avoid traffic looping problems.
  • the failure of the link caused by the failure point is because the link is configured not to forward traffic, not because of failures and other reasons. .
  • the link between the user-side device 112 and the user-side device 113 is the point of failure, which means that the link between the user-side device 112 and the user-side device 113 is unreachable.
  • the network device 101 can learn the media access control (Media Access Control, MAC) addresses from the user-side device 111 and the user-side device 112, but cannot learn the MAC address from the user-side device 113 and the user-side device 114. MAC address.
  • the network device 102 can learn the MAC addresses from the user-side device 113 and the user-side device 114 , but cannot learn the MAC addresses from the user-side device 111 and the user-side device 112 .
  • Media Access Control Media Access Control
  • the traffic sent from the network device 103 to the user-side device can take two paths: one is network device 103-network device 101-user-side device 111-user-side device 112; the other is network device 103-network device 102- User side equipment 114 - User side equipment 113 .
  • the user-side device is dual-homed to the network device 101 and the network device 102 through the ring network, but sometimes the user-side device is dual-homed to the Ethernet link identifiers (Ethernet link identifiers) of the two network devices.
  • segment identifier, ESI segment identifier
  • the link between the network device 101 and the network device 102 in the existing protocol is unreachable. Then, when a fault occurs in the ring network, the downlink The time of traffic packet loss cannot be guaranteed, which may lead to long-term packet loss.
  • link 3 is the damage point of the ring network.
  • the ESI of the dual-homed access network equipment of the user-side device is different, that is, the ESIs of link 1 and link 5 are different.
  • the ESI of link 1 can be called ESI1
  • the ESI of link 5 can be called ESI2.
  • the destruction protocol in the ring network will be triggered to perform route recalculation.
  • the broken point link 3 can communicate normally.
  • the user-side device 112 notifies the fault to other devices in the ring network, namely the user-side device 113, the user-side device 114 and the network device 102 after sensing the fault, and the user-side device 111 also reports the fault to other devices in the ring network after sensing the fault.
  • the device, the network device 101 advertises the failure. After other devices in the ring network perceive the failure, they will clear the MAC address in their own MAC address table, and then re-learn the MAC addresses of each device in the new network topology formed after the failure to form a new MAC route. .
  • the MAC route includes the MAC address of the device and the corresponding next-hop information, and the next-hop may be the address of the next-hop device, or the outgoing interface to the next-hop device, and the like.
  • the network device 101 and the network device 102 clear the MAC address, they will send a notification of clearing the MAC address to the network device 103, so that the network device 103 will also clear the MAC address in its own MAC address table after a failure, and then relearn the MAC address.
  • the network device 103 when the number of MAC addresses in the MAC address table in the network device 3 is large, it takes a long time to clear the MAC addresses, and after the above failure occurs, the network device 103 has not yet removed the MAC address of the user-side device 112 , then if the network device 103 receives the traffic destined for the user-side device 112 at this time, it will forward the traffic according to the original forwarding path of the traffic, that is, the network device 103 - the network device 101 - the user-side device 111 - the user-side device 112 , but due to a fault, the forwarding path has been blocked, resulting in packet loss of the traffic.
  • the present application provides a method for forwarding traffic.
  • the following describes the method for forwarding traffic provided by the present application through several embodiments.
  • the method for forwarding traffic provided in this embodiment can be seen in FIG. 4 .
  • This method can be applied to the scenario shown in FIG. 3 to solve the problem that the traffic packet loss time is too long after a fault occurs in the above-mentioned ring network.
  • the method may include but not Limited to the following steps:
  • the first network device sends first traffic to the second network device, where the destination address of the first traffic is the first device.
  • the first network device may be the network device 101 shown in FIG. 3 above
  • the second network device may be the network device 102 shown in FIG. 3
  • the first device may be the network device 102 shown in FIG. 3 .
  • the first device is multi-homed to access the first network device and the second network device through the networking mode of the ring network.
  • the ring network may be a ring network including a plurality of user-side devices as shown in FIG. 3 , and the user-side devices in the ring network are multi-homed to the first network device and the second network device through the first link and the second link respectively.
  • Two network devices, the ESI of the first link and the ESI of the second link are different.
  • the first link may be, for example, link 1 in FIG. 3
  • the second link may be, for example, link 5 in FIG. 3 .
  • the sending of the first traffic by the first network device to the second network device may be that in the case of a failure in the ring network, the first network device sends the first traffic to the second network device.
  • the failure may be a failure occurring on the communication link between the first network device and the first device, for example, may be the failure occurring in the link 2 shown in FIG. 3 above.
  • the downlink traffic to the first device can be forwarded through the first network device. Due to the existence of the destruction point in the ring network that destroys the protocol settings, the communication between the second network device and the first device The link is dead.
  • the first network device and the second network device will clear the stored MAC addresses of the devices in the network topology before the fault based on the fault.
  • the MAC address will send a notification of clearing the MAC address to the third network device, so that the third network device also clears the MAC address.
  • the first network device and the second network device respectively establish border gateway protocol (border gateway protocol, BGP) neighbors with the third network device, or establish open shortest path first (open shortest path first, OSPF) neighbors, or Establish a link state routing protocol neighbor from an intermediate system to an intermediate system (ISIS), etc., then, the first network device and the second network device can communicate with the third network device through the BGP protocol, the OSPF protocol, or the ISIS protocol, etc. Send a notification to clear this MAC address.
  • border gateway protocol border gateway protocol
  • OSPF open shortest path first
  • ISIS intermediate system
  • the third network device may be the network device 103 shown in FIG. 3 .
  • the third network device cannot directly perceive the above fault, so it can only be notified by the first network device and the second network device to clear the stored data.
  • MAC address of the device in the network topology before the fault occurs. Regardless of whether it is the first network device, the second network device, or the third network device, all of them can learn the changed network after the failure while clearing the MAC addresses of the devices in the network topology before the failure.
  • the first network device receives the first traffic from the third network device.
  • the first network device can send the traffic to the user in the ring network through an access link (AC) interface.
  • the side device broadcasts the first traffic; on the other hand, the first network device may also send the first traffic to the second network device.
  • the destination address of the first traffic is the first device, and the destination MAC address of the first traffic may be the MAC address of the first device.
  • the first traffic can be broadcast or unicast normally only after the third network device clears the MAC address of the first device.
  • the broadcast refers to that in the case that the third network device has cleared the MAC address of the first device but has not learned the MAC route of the first device in the network topology changed after the above fault, the third network device passes broadcast method to send the first traffic.
  • the unicast means that in the case that the third network device has re-learned the MAC route of the first device in the network topology changed after the above-mentioned fault, after receiving the first traffic, the third network device can The first traffic is unicast according to the MAC address forwarding table.
  • the MAC route of the first device includes the MAC address of the first device and corresponding next hop information, where the next hop may be the address of the next hop device of the first device, or the first device goes to the next hop Jump the outbound interface of the device, etc.
  • the first traffic will forward the first traffic according to the original forwarding path, that is, the third network device-first network device-first device. , but because the link between the first network device and the first device is faulty, the first traffic cannot be normally forwarded to the first device, resulting in packet loss of traffic and interruption of service flow.
  • the first network device receives the above-mentioned first traffic from the third network device, and can perform address matching in the MAC address table normally, but due to the occurrence of the above-mentioned first traffic After the failure, the first network device has cleared the MAC address in the MAC address table. Therefore, the source MAC address and destination MAC address of the first traffic cannot be found in the MAC address table of the first network device. Therefore, the first network device can The first traffic is broadcast to the user-side device through the AC interface, and in addition, the first network device also sends the first traffic to the second network device.
  • the first network device receives the above-mentioned first traffic from the third network device, and may directly broadcast the first traffic through the AC interface without querying the MAC address table to the user-side device, and send the first traffic to the second network device.
  • the first network device and the second network device do not communicate.
  • the first network device can send the above-mentioned first traffic to the second network.
  • the device performs forwarding, and the first network device is configured with a default route for sending the first traffic to the second network device.
  • the default route includes information such as the MAC address of the second network device.
  • the first network device may send the traffic received from the third network device, such as the above-mentioned first traffic, to the second network device according to the default route.
  • the second network device receives the first traffic from the first network device.
  • the second network device can receive the first traffic.
  • the second network device sends the first traffic to the first device.
  • the destruction protocol in the ring network will be triggered to perform route recalculation, and the destruction point can be eliminated, then the communication link between the second network device and the first device can communicate normally. Therefore, the second network device After the above-mentioned first traffic from the first network device is received, it can be normally forwarded to the first device, so that the traffic packet drop caused by the above-mentioned fault can be reduced.
  • first traffic from the first network device refers to the traffic that the first traffic passes through the first network device and is forwarded by the first network device to the second network device.
  • FIG. 3 is taken as an example for description.
  • the network device 101 receives the first traffic sent from the network device 103 to the user-side device 112, and the network device 101 broadcasts the first traffic to the user-side device in the ring network through the AC port.
  • the first traffic is also sent to the network device 102 . Since the broken point link 3 can resume normal communication after the failure, the network device 102 can forward the first a flow, so that the first flow reduces packet loss.
  • the second network device may monitor the traffic received from the first network device through the traffic characteristic table.
  • the traffic characteristics table may record characteristics of traffic received from the first network device after the failure, as well as record the identification of one or more devices that the traffic passed through before reaching the second network device.
  • the characteristics of the traffic can be the characteristics of the packets in the traffic. All packets included in a traffic have the same characteristics, and the characteristics include the two-tuple, four-tuple, five-tuple or seven-tuple of the packets in the traffic. .
  • the identifier of the device may include an internet protocol (Internet protocol, IP) address or a MAC address of the device, and the like.
  • IP Internet protocol
  • the identifiers of one or more devices that the traffic passes through before reaching the second network device may include the identifier of the first network device. In this application, one or more devices that the traffic passes through before reaching the second network device may be referred to as mapping devices for the traffic.
  • the two-tuple of the traffic includes the source MAC address and the destination MAC address of the traffic.
  • the four-tuple of traffic includes the source IP address, destination IP address, source port, and destination port of the traffic.
  • the five-tuple of traffic includes the source IP address, destination IP address, source port, destination port, and protocol number of the traffic.
  • the seven-tuple of traffic includes the source IP address, destination IP address, protocol number, source port, destination port, service type, and interface index of the traffic.
  • the second network device receives the above-mentioned first traffic sent from the first network device, and can process the first traffic in the following three situations:
  • the second network device determines that the information of the first traffic has not been recorded in the traffic characteristic table.
  • the second network device may parse the received packets in the first traffic, obtain features in the packets, and compare the obtained features with the features in the traffic feature table, and there is no correlation with the acquired features in the traffic feature table. If the characteristics of the first flow are the same, it indicates that the information of the first flow has not been recorded in the flow characteristic table. That is, it indicates that this is the first time that the second network device receives the first traffic from the first network device after the above-mentioned failure.
  • the second network device adds the information of the first flow in the flow characteristic table, including adding the characteristic of the first flow and the identification of the mapping device of the first flow, and the like. Then, the second network device sends the first traffic received from the first network device to the first device. See Table 1 for example.
  • Table 1 shows the information of the first traffic recorded in the traffic feature table by taking the traffic feature as a two-tuple as an example.
  • the traffic feature table may record the source MAC address (eg, may be 1.1.1.1), destination MAC address (eg, may be 2.2.2.2) of the first traffic and the mapping device of the first traffic.
  • the mapping device may be the above-mentioned first network device, and the mapping device may be identified by a MAC address, for example, the MAC address of the mapping device may be 3.3.3.3.
  • the second network device determines that the mapping device of the first traffic in the traffic characteristic table includes the above-mentioned first network device.
  • the second network device can parse the received packets in the first traffic, obtain the features in the packets, compare the obtained features with the features in the traffic feature table, and find in the traffic feature table that matches the acquired features. If the characteristics of the first flow are the same, it means that the information of the first flow is recorded in the flow characteristic table, and then the mapping device of the first flow is searched in the flow characteristic table. If the mapping device of the first flow is the above-mentioned first network The device indicates that this is the second network device that has received the first traffic from the first network device again after the above-mentioned failure.
  • mapping device for the first traffic in the traffic feature table is still the first network device, it indicates that the second network device has not received the first traffic from the third network device, because if it receives the first traffic from the third network device For a flow, the second network device will set the mapping device of the first flow in the flow characteristic table as the third network device.
  • the fact that the second network device has not received the first traffic from the third network device indicates that after the above fault occurs, the third network device has not cleared the MAC address of the first device in the MAC address table stored by itself, and still When the traffic is forwarded to the first network device, the first network device will continue to send the received first traffic to the second network device. Then, the second network device sends the first traffic received from the first network device to the first device.
  • first traffic from the third network device refers to the first traffic that is sent by the third network device to the second network device and does not need to be forwarded by the first network device.
  • the first traffic from the third network device namely network device 103
  • the path 6 may also include one or more other network devices.
  • the above-mentioned first traffic from the first network device refers to the first traffic that is sent from the network device 103, reaches the network device 101 through the path 7, and then reaches the network device 102 through the path 8. .
  • path 7 and path 8 may also include one or more other network devices.
  • the second network device determines that the mapping device of the first traffic in the traffic characteristic table includes the above-mentioned third network device.
  • the second network device can parse the received packets in the first traffic, obtain the features in the packets, compare the obtained features with the features in the traffic feature table, and find in the traffic feature table that matches the acquired features. If the features are the same, it indicates that the information of the first flow is recorded in the flow characteristic table, and then the mapping device of the first flow is searched in the flow characteristic table. If the mapping device for the first traffic is the third network device, it means that the second network device has received the first traffic from the third network device before receiving the first traffic from the first network device again. .
  • the third network device completes the clearing of the MAC address of the first device after receiving the notification sent from the first network device to clear the MAC address of the first device, and then when the third network device clears the MAC address of the first device
  • the third network device can broadcast the received first traffic. Both the first network device and the second network device can receive the first traffic. If the third network device has learned the MAC route of the first device in the new network topology after the failure, the third network device can unicast the first traffic to the second network device according to the MAC address table.
  • the second network device After the second network device receives the first traffic broadcast by the third network device, it can look up the information of the first traffic in the traffic feature table, if the mapping device of the first traffic in the traffic feature table is not the third network device, then the second network device will set the mapping device of the first traffic in the traffic characteristic table as the third network device. Specifically, the identifier of the mapping device of the first traffic in the traffic characteristic table may be replaced with the identifier of the third network device.
  • the second network device will not send the first traffic received from the first network device to the first device again, and can directly send the The re-received first traffic from the first network device is discarded.
  • the mapping device of the first traffic in the traffic characteristic table is the above-mentioned third network device
  • the second network device will send the first traffic from the third network device to the first device.
  • the mapping device of the received first traffic is monitored through the traffic feature table. As long as the mapping device of the first traffic in the traffic monitoring table is not the third network device, the second network device can continue to forward the traffic. The first traffic from the first network device. When the mapping device of the first traffic in the traffic monitoring table is the third network device, it indicates that the third network device can normally forward the first traffic after the above-mentioned fault occurs. Then, in order to avoid multiple packets, the second network device The first traffic received again from the first network device is discarded, and only the first traffic from the third network device is forwarded.
  • the second network device may also receive the second traffic from the third network device, and the second traffic is sent to the second network device. equipment.
  • the second device may be, for example, the user-side device 113 or the user-side device 114 in FIG. 3 .
  • the second network device can look up the feature of the second traffic in the traffic feature table, but since the traffic feature table is only used to record the information of the traffic from the first network device after the fault, the traffic feature table does not include the feature of the second traffic. Information about the second flow. Then, the second network device sends the second traffic to the second device.
  • the first network device may also receive third traffic, and the third traffic may come from other network devices such as a third network If the device can find the forwarding entry of the third traffic in its own MAC address table, the first network device can send the third traffic according to the forwarding entry.
  • the first network device can also receive the fourth traffic.
  • the fourth traffic is received through the AC interface, indicating that it is the traffic from the user-side device.
  • the first network device can send the fourth traffic according to the forwarding entry. If the forwarding entry for the fourth traffic is not found in its own MAC address table, the first network device may broadcast the fourth traffic to other network devices in the network.
  • the first traffic sent by the first network device to the second network device may carry a label, and the label may be used to indicate that the first traffic comes from the first network device.
  • the label may be added to the header of the packet included in the first flow, for example, a field may be added to the header of the packet of the first flow to carry the label, or it may be in the original carry the label in the field.
  • the second network device can identify the label, so as to know that the traffic carrying the label comes from the first network device.
  • the operations performed by the first network device and the second network device in each of the foregoing embodiments may be operations performed before the timer reaches the preset duration.
  • a timer is respectively set.
  • the timer of the first network device may be referred to as a first timer
  • the timer of the second network device may be referred to as a second timer.
  • the duration of the first timer may be the first preset duration
  • the duration of the second timer may be the second preset duration.
  • the first preset duration and the second preset duration are greater than the convergence time of the third network device, and the convergence time includes the time from when the fault occurs to when the third network device clears the device according to the notification from the first network device and the second network device.
  • the duration of the own MAC address table Exemplarily, the first preset duration and the second preset duration may be 60 seconds, or may also be 50 seconds or 70 seconds, and so on.
  • the third network device completes the first device's MAC address after receiving the notification sent from the first network device to clear the MAC address of the first device.
  • a notification is sent to the second network device, where the notification is used to indicate that the second network device does not need to forward the first traffic from the first network device.
  • the notification may be a notification that the third network device has been able to send the first traffic to the second network device, or the notification is the first time that the third network device clears the MAC address of the first device to broadcast the first traffic.
  • the first traffic is sent to the second network device in the manner of the first traffic, or the notification may be a pre-defined indication message or the like.
  • the third network device sends the above notification to the second network device after clearing the MAC address of the first device because, after clearing the MAC address of the first device, regardless of whether the third network device has relearned the fault after the failure
  • the MAC route of the first device in the network topology and the third network device can both send the first traffic to the second network device. That is, if the third network device does not relearn the MAC route of the first device after clearing the MAC address of the first device, the third network device will broadcast the first device to other network devices including the second network device.
  • a flow if the third network device relearns the MAC route of the first device after clearing the MAC address of the first device, then the third network device will unicast according to the learned MAC route of the first device The first traffic is sent to the second network device.
  • the second network device after receiving the notification, when the second network device receives the first traffic from the first network device again, it will not forward the first traffic from the first network device, and can discard it. At the same time, the second network device forwards the first traffic from the third network device to the first device. Thus, the problem of multiple packets of the first traffic is avoided.
  • the method for forwarding traffic described in FIG. 4 and its possible implementations are mainly by configuring a default route between the first network device and the second network device, so as to pass the second network in the case of the above-mentioned fault.
  • the device completes the forwarding of the above-mentioned first traffic, so as to reduce the packet loss of the traffic.
  • the problem of reducing traffic and packet drops after solving the above-mentioned faults can also be achieved by broadcasting traffic by a third network device.
  • broadcasting traffic by a third network device.
  • the second embodiment is another method for forwarding traffic provided by the present application.
  • the method for forwarding traffic provided in this embodiment reference may be made to FIG. 5 , and the method can be applied to the scenario shown in FIG.
  • the method may include but is not limited to the following steps:
  • the first network device senses a fault in the connected ring network, clears the MAC address in its own MAC address table based on the fault, and sends a notification of clearing the MAC address to the third network device at the same time.
  • the third network device receives the notification and clears the MAC address in its own MAC address table.
  • the third network device After receiving the above notification and before relearning the MAC route of the first device, the third network device broadcasts the received first traffic with the destination MAC address of the first device to other network devices.
  • the notification may be the first notification of clearing the MAC address sent by the first network device to the third network device after sensing the above-mentioned failure. After receiving the notification, the third network device starts to clear the corresponding MAC address, and at the same time can start to learn the MAC routes of the devices in the network topology after the failure.
  • the third network device can broadcast the first traffic sent to the first device, so that the second network device can receive the first flow.
  • the second network device receives the broadcasted first traffic, and broadcasts the first traffic to the user-side device, so that the first device can receive the first traffic.
  • the second network device After the second network device receives the first traffic broadcast from the third network device, if it receives the first traffic for the first time, it cannot find the forwarding information of the first traffic in its own MAC address table , then the second network device can broadcast the data from the AC interface to the user-side device, so that the first device can receive the first traffic. After receiving the first traffic, the first device will return a message to the second network device, indicating that the first traffic is sent to the first device. Then, after receiving the message, the second network device may add a forwarding table entry for the first traffic in the MAC address forwarding table, for example, record the characteristics of the first traffic such as the source MAC address and destination MAC address and the outgoing port number, etc. information. When the second network device receives the first traffic again, the forwarding table entry in the MAC address forwarding table may be unicast and sent to the first device.
  • the third network device can normally forward the first device's MAC route according to the MAC address forwarding table. first flow.
  • the method described in each of the above embodiments can also be used to solve the problem that the traffic packet loss time is too long.
  • the first network device may be the network device 102 in FIG. 3
  • the second network device may be the network device 101 in FIG. 3
  • the third network device may be the network device 103 in FIG. 3
  • the above-mentioned first device may be the user side device 113 in FIG. 3 .
  • the third network device uniformly broadcasts the received first traffic, and the second network device receives the broadcasted first traffic. After traffic, it can be forwarded to the first device.
  • the third network device relearns the MAC route of the first traffic, it stops broadcasting the first traffic, and can forward traffic according to the new learned route, so that the first device can receive traffic normally and reduce service interruption The probability.
  • each device includes corresponding hardware structures and/or software modules for performing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • the device may be divided into functional modules according to the foregoing method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules. It should be noted that the division of modules in the embodiments of the present application is schematic, and is only a logical function division, and other division manners may be used in actual implementation.
  • FIG. 6 shows a schematic diagram of a possible logical structure of a device, and the device may be the second network device in each of the foregoing embodiments. It should be noted that the second network device involved in the process of describing the device shown in FIG. 6 may be the first network device in each of the foregoing embodiments.
  • the device 600 shown in FIG. 6 includes a receiving unit 601 and a sending unit 602 . in:
  • the receiving unit 601 is configured to receive the first traffic from the second network device, the destination address of the first traffic is the first device, the device 600 and the second network device are service provider edge PE devices in the network, the first A device is multihomed to the device 600 and the second network device through the first link and the second link respectively, and the Ethernet link identifiers ESI of the first link and the second link are different; the receiving The unit 601 may perform the operations described in step 402 shown in FIG. 4 .
  • a sending unit 602 configured to send the first traffic to the first device.
  • the sending unit 602 may perform the operations described in step 403 shown in FIG. 4 .
  • the device before the sending unit 602 sends the first traffic to the first device, the device further includes:
  • a determination unit configured to determine that the mapping device of the first traffic in the local traffic characteristic table is not a third network device, the third network device is a PE device in the network, and the third network device is connected to the device 600 and the third network device respectively. 2. Network equipment.
  • the above determining unit determines that the source device of the first traffic in the local traffic feature table is not the third network device, including the following two situations:
  • the determining unit determines that the mapping device of the first traffic in the local traffic characteristic table is the second network device
  • the determining unit determines that the local traffic feature table does not indicate the mapping device of the first traffic; in this case, the device 600 may set the mapping device of the first traffic as the second network in the local traffic feature table equipment.
  • the above receiving unit 601 is further configured to receive the first traffic from the third network device;
  • the above-mentioned device 600 also includes a setting unit for setting the mapping device of the first flow in the local flow characteristic table to be the third network device when the mapping device of the first flow in the local flow characteristic table is not the third network device. the third network device;
  • the above sending unit 602 is further configured to send the first traffic from the third network device to the first device.
  • the above receiving unit 601 is further configured to receive the first traffic from the second network device again;
  • the above-mentioned device 600 further includes a discarding unit configured to discard the re-received first traffic from the device 600 when the mapping device of the first traffic in the local traffic characteristic table is the third network device.
  • the above receiving unit 601 is further configured to receive the second traffic from the third network device;
  • the above-mentioned sending unit 602 is further configured to send the second flow to the second device in the network when the local flow characteristic table does not include the information of the second flow.
  • the first traffic carries a label
  • the label indicates that the first traffic comes from the second network device.
  • the above-mentioned sending unit 602 is specifically configured to send the first traffic to the first device when the timer is started and the preset duration does not reach, wherein the timer is the The device 600 is started after sensing the failure of the communication link between the second network device and the first device.
  • the receiving unit 601 is further configured to receive a notification from the third network device, where the notification is used to indicate that the device 600 does not need to forward the first traffic from the second network device;
  • the above receiving unit 601 is further configured to receive the first traffic from the second network device again;
  • the above-mentioned device 600 further includes a discarding unit for discarding the re-received first traffic from the second network device in response to the notification.
  • the above receiving unit 601 is further configured to receive the first traffic from the third network device;
  • the above sending unit 602 is further configured to send the first traffic from the third network device to the first device.
  • FIG. 7 shows a schematic diagram of a possible logical structure of a device, and the device may be the first network device in each of the foregoing embodiments. It should be noted that, the second network device involved in the process of describing the device shown in FIG. 7 may be the second network device in each of the foregoing embodiments.
  • the device 700 shown in FIG. 7 includes a sending unit 701 . in:
  • a sending unit 701 is configured to send first traffic to a second network device, where the destination address of the first traffic is the first device; the device 700 and the second network device are service provider edge PE devices in the network, and the first traffic is the first device.
  • a device is multihomed to the device 700 and the second network device through the first link and the second link respectively, and the Ethernet link identifiers ESI of the first link and the second link are different.
  • the sending unit 701 may perform the operations described in step 401 shown in FIG. 4 .
  • the device 700 further includes a broadcasting unit, configured to broadcast the first traffic through the AC interface of the access link.
  • the sending unit 701 is specifically configured to send the first traffic to the second network device when the communication link between the device 700 and the first device fails .
  • the sending unit 701 is specifically configured to: in the case that the MAC address of the first device cannot match the entry in the local media access control MAC address forwarding table of the device 700, send The second network device sends the first traffic.
  • the sending unit 701 is specifically configured to: when the timer is started and the preset time period is not reached, the device 700 sends the first traffic to the second network device, wherein the The timer is started after the device 700 senses the failure of the communication link between the device 700 and the first device.
  • the first traffic carries a label, and the label indicates that the first traffic comes from the device 700 .
  • the above receiving unit is further configured to receive the second traffic
  • the foregoing sending unit 701 is further configured to send the second traffic according to the local MAC address forwarding table.
  • the above receiving unit is further configured to: receive the third traffic through the AC interface of the access link;
  • the above-mentioned sending unit 701 is further configured to broadcast the third traffic to network devices in the network when the destination MAC address of the third traffic cannot match an entry in the local MAC address forwarding table of the device 700 .
  • the above-mentioned device 700 further includes an obtaining unit: used to obtain a default route, where the default route is used to obtain a default route when the communication link between the device 700 and the first device fails. sending the first traffic from the third network device to the second network device;
  • the above-mentioned sending unit 701 is specifically configured to: send the first traffic to the second network device according to the default route.
  • FIG. 8 shows a schematic diagram of a possible logical structure of the device, and the device may be the third network device in each of the foregoing embodiments.
  • the second network device involved in the process of describing the device shown in FIG. 8 may be the second network device in each of the foregoing embodiments
  • the third network device involved in the process of describing the device shown in FIG. 8 It may be the first network device in each of the foregoing embodiments.
  • the device 800 shown in FIG. 8 includes a sending unit 801 . in:
  • a sending unit 801 configured to send a notification to the second network device, where the notification is used to indicate that the second network device does not need to forward the first traffic from the third network device; the destination address of the first traffic is the first device, the device 800.
  • the second network device and the third network device are service provider edge PE devices in the network, the device 800 is respectively connected to the second network device and the third network device, and the first device passes through the first link.
  • the channel and the second link are multi-homed to the second network device and the third network device, and the Ethernet link identifiers ESI of the first link and the second link are different.
  • each unit in the device 800 shown in FIG. 8 can be referred to the above-mentioned FIG. 4 and its possible implementations.
  • the description of the embodiment of the notification of the first traffic will not be repeated here.
  • FIG. 9 shows a schematic diagram of a possible logical structure of a device, and the device may be the third network device in each of the foregoing embodiments. It should be noted that the third network device involved in the process of describing the device shown in FIG. 9 may be the second network device in each of the foregoing embodiments.
  • the apparatus 900 described in FIG. 9 includes a broadcasting unit 901 . in:
  • the broadcasting unit 901 is configured to, after the communication link between the first network device and the first device fails, and the device 900 does not clear the MAC address of the first device based on the failure, broadcast to the network in the network
  • the device broadcasts first traffic, the destination address of the first traffic is the first device, the network devices in the network include a third network device, the first network device, the device 900 and the third network device are in the network
  • the service provider edge PE device the device 900 is respectively connected to the first network device and the third network device, and the first device is multihomed to the first network device and the third network device through the first link and the second link respectively.
  • the Ethernet link identifiers ESI of the first link and the second link are different.
  • the broadcasting unit 901 may perform the operations described in step 503 shown in FIG. 5 .
  • FIG. 10 shows a schematic diagram of a possible logical structure of a device, and the device may be the second network device in each of the foregoing embodiments.
  • the second network device involved in the process of describing the device shown in FIG. 10 may be the third network device in each of the foregoing embodiments, and the third network device involved in the process of describing the device shown in FIG. 10 It may be the first network device in each of the foregoing embodiments.
  • the device 1000 shown in FIG. 10 includes a receiving unit 1001 . in:
  • the receiving unit 1001 is configured to receive the first traffic broadcast by the second network device, where the first traffic is the device 1000 after the communication link between the third network device and the first destination device fails, and the second traffic Broadcasted by the network device without clearing the MAC address of the first device based on the fault, the device 1000, the second network device, and the third network device are service provider edge PE devices in the network, and the second network device
  • the devices are respectively connected to the device 1000 and the third network device, the first device is multihomed to the device 1000 and the third network device through the first link and the second link respectively, the first link and the third network device
  • the Ethernet link identifier ESIs of the two links are different; the device 1000 sends the first traffic to the first device.
  • the receiving unit 1001 may perform the receiving operation described in step 504 shown in FIG. 5 .
  • FIG. 11 shows a schematic diagram of a possible hardware structure of the device provided by the present application.
  • the device may be any network device in the methods described in the foregoing embodiments, for example, it may be a first network device, or may be a second network device device, or may be a third network device.
  • the device 1100 includes: a processor 1101 , a memory 1102 and a communication interface 1103 .
  • the processor 1101 , the communication interface 1103 , and the memory 1102 may be connected to each other or to each other through a bus 1104 .
  • the memory 1102 is used to store computer programs and data of the device 1100, and the memory 1102 may include, but is not limited to, random access memory (RAM), read-only memory (ROM), memory Erase programmable read only memory (erasable programmable read only memory, EPROM) or portable read only memory (compact disc read-only memory, CD-ROM), etc.
  • the communication interface 1103 is used to support the device 1100 to communicate, such as receiving or sending data or signals.
  • the processor 1101 can not only call the program codes in the memory 1102 to implement some functions, but also cooperate with Other components (eg, communication interface 1103 ) collectively perform other functions (eg, functions of receiving and sending data) described in either embodiment.
  • the processor 1101 may be a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • a processor may also be a combination that performs computing functions, such as a combination comprising one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like.
  • the processor 1101 may be configured to read the program stored in the foregoing memory 1102, and execute the operations performed by the first network device, the second network device, or the third network device in the methods described in the foregoing embodiments.
  • An embodiment of the present application further provides an apparatus, the apparatus includes a processor, a communication interface, and a memory, and the apparatus is configured to execute the method described in any one of the foregoing embodiments and possible embodiments thereof.
  • the device is a chip or a System on a Chip (SoC).
  • SoC System on a Chip
  • Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program is executed by a processor to implement any one of the foregoing embodiments and possible embodiments thereof. method described.
  • the embodiments of the present application also provide a computer program product, when the computer program product is read and executed by a computer, the method described in any one of the foregoing embodiments and its possible embodiments will be executed.
  • the embodiments of the present application further provide a computer program, which, when executed on a computer, enables the computer to implement the method described in any one of the foregoing embodiments and possible embodiments thereof.
  • the present application can solve the problem between the user-side equipment and the PEs when the user-side equipment is multi-homed to multiple PEs, and the ESI configurations of the links between the user-side equipment and the multiple PEs are different.
  • the problem of packet loss for a long time after the link between them fails.
  • first, second and other words are used to distinguish the same or similar items with basically the same function and function, and it should be understood that between “first”, “second” and “nth” There are no logical or timing dependencies, and no restrictions on the number and execution order. It will also be understood that, although the following description uses the terms first, second, etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first image may be referred to as a second image, and, similarly, a second image may be referred to as a first image, without departing from the scope of various described examples. Both the first image and the second image may be images, and in some cases, may be separate and distinct images.
  • the size of the sequence number of each process does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not be used in the embodiment of the present application. Implementation constitutes any limitation.
  • determining B according to A does not mean that B is only determined according to A, and B may also be determined according to A and/or other information.
  • references throughout the specification to "one embodiment,” “an embodiment,” and “one possible implementation” mean that a particular feature, structure, or characteristic associated with the embodiment or implementation is included herein. in at least one embodiment of the application. Thus, appearances of "in one embodiment” or “in an embodiment” or “one possible implementation” in various places throughout this specification are not necessarily necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.

Landscapes

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

Abstract

本申请实施例公开了一种转发流量的方法及设备，该方法包括：第一网络设备接收来自第二网络设备的第一流量，该第一流量的目的地址为第一设备，该第一网络设备和该第二网络设备为网络中的服务提供商边缘PE设备，第一设备分别通过第一链路和第二链路多归接入该第一网络设备和该第二网络设备，该第一链路和该第二链路的以太网链路标识ESI不同；该第一网络设备向该第一设备发送该第一流量。本申请能够减少流量丢包。

Description

转发流量的方法及设备
本申请要求于2020年9月29日提交中国专利局、申请号为202011050592X、申请名称为“转发流量的方法及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种转发流量的方法及设备。
背景技术
在以太虚拟专用网(Ethernet virtual private network,EVPN)取代虚拟专用局域网业务(virtual private LAN service,VPLS)的趋势下，EVPN下挂环网的场景会逐步增多。EVPN中的运营商边缘设备(provider edge,PE)之间部署了EVPN互通，在这种场景下，有时用户侧设备例如客户端边缘设备(customedge,CE)多归接入的多个PE，或者CE通过交换机多归接入该多个PE，且用户侧设备分别与该多个PE之间的链路的以太链路标识(Ethernet segment identifier,ESI)需要配置不同。在这种情况下，当EVPN下挂的环网发生故障时，可以触发环网的以太网环保护交换(Ethernet ring protection switching,ERPS)协议，使得PE清除已存储有的网络拓扑中的设备的媒体访问控制(media access control,MAC)地址，然后重新学习故障之后的网络拓扑中的设备的MAC路由，学习完成之后才可以实现流量的正常转发。但是，当MAC地址数量较多时，需要花费较长的时间才可以恢复流量的正常转发，导致流量丢包时间较长的问题。
综上所述，如何在用户侧设备多归接入多个PE，且用户侧设备分别与该多个PE之间的链路的ESI配置不同的情况下，避免出现故障后长时间丢包是本领域技术人员需要解决的技术问题。
发明内容
本申请提供一种转发流量的方法及设备，能够在用户侧设备多归接入多个PE，且用户侧设备分别与该多个PE之间的链路的ESI配置不同的情况下，解决用户侧设备与PE之间的链路出现故障后长时间丢包的问题。
第一方面，本申请提供一种转发流量的方法，该方法包括：
第一网络设备接收来自第二网络设备的第一流量，所述第一流量的目的地址为第一设备，所述第一网络设备和所述第二网络设备为网络中的服务提供商边缘PE设备，第一设备分别通过第一链路和第二链路多归接入所述第一网络设备和所述第二网络设备，所述第一链路和所述第二链路的以太网链路标识ESI不同；所述第一网络设备向所述第一设备发送所述第一流量。
在本申请中，上述各个网络设备可以是EVPN网络中的设备，上述第一设备可以是该EVPN网络中下挂的环网中的用户侧设备，第一设备是多归接入EVPN网络中的第一网络设备和第二网络设备，且该第一设备接入该第一网络设备和第二网络设备的ESI不同，在这种情况下，当第一设备接入EVPN网络的路径例如接入第二网络设备的路径中出现故障时(若无该故障，第一流量通过第二网络设备转发给第一设备)，需要花费较长的时间才可以恢复流量的正常转发，为了减少流量丢包的时间，当第二网络设备接收到来自第三网络设备发往第 一设备的流量即上述第一流量时，可以将该流量转发给第一网络设备，由该第一网络设备转发给第一设备，从而可以使得第一设备正常接收到流量，减少业务中断的概率。
在其中一种可能的实施方式中，在所述第一网络设备向所述第一设备发送所述第一流量之前，所述方法还包括：所述第一网络设备确定本地流量特征表中所述第一流量的映射设备不是第三网络设备，所述第三网络设备为所述网络中的PE设备，所述第三网络设备分别连接所述第一网络设备和所述第二网络设备。
其中，上述第一网络设备确定本地流量特征表中所述第一流量的来源设备不是第三网络设备，包括下面两种情况：
所述第一网络设备确定本地流量特征表中所述第一流量的映射设备为所述第二网络设备；
或者，所述第一网络设备确定本地流量特征表未指示所述第一流量的映射设备；在这种情况下，该第一网络设备可以在所述本地流量特征表中设置所述第一流量的映射设备为所述第二网络设备。
本申请中的流量特征表在第一网络设备中用于记录从第二网路设备发送过来的流量的信息，并记录对应流量到达该第一网络设备的映射设备的信息，从而获知该流量是否为经过第二网络设备转发的流量。该流量特征表用于监控出现上述故障后第一网络设备从第二网路设备接收的流量。
在其中一种可能的实施方式中，所述方法还包括：
所述第一网络设备接收来自所述第三网络设备的所述第一流量；
在所述本地流量特征表中所述第一流量的映射设备不是所述第三网络设备的情况下，所述第一网络设备将所述本地流量特征表中所述第一流量的映射设备设置为所述第三网络设备；
所述第一网络设备向所述第一设备发送来自所述第三网络设备的所述第一流量。
且，所述第一网络设备再次接收来自所述第二网络设备的所述第一流量；
在所述本地流量特征表中所述第一流量的映射设备为所述第三网络设备的情况下，所述第一网络设备丢弃所述再次接收的来自所述第一网络设备的所述第一流量。
在本申请中，在出现上述故障之后，第一网络设备可以接收到来自第三网络设备的第一流量，表明该第一流量已经可以正常转发，不会有丢包的问题了，在这种情况下，第一网络设备可以正常转发来自第三网络设备的第一流量，并且在流量特征表中标记第一流量可以从第三网络设备接收，这样当再次接收到来自第二网络设备的第一流量时，可以将其丢弃，从而避免了该第一流量多包的问题。
在其中一种可能的实施方式中，所述方法还包括：所述第一网络设备接收来自所述第三网络设备的第二流量；在所述本地流量特征表中不包括所述第二流量的信息时，所述第一网络设备向所述网络中的第二设备发送所述第二流量。
在本申请中，第一网络设备仍然可以正常转发没有受故障影响的流量，并且转发这些流量之前都在流量特征表中查看一下是否有这些流量的信息，没有则正常转发，这也是为了避免流量多包的问题。
在其中一种可能的实施方式中，所述第一流量携带标签，所述标签指示所述第一流量来自所述第二网络设备。
在本申请中，通过标签来标识来自第二网络设备的第一流量，能够清楚区分哪些是受故障影响的流量，从而对这些流量进行监控转发。
在其中一种可能的实施方式中，所述第一网络设备向所述第一设备发送所述第一流量，包括：在定时器启动且未达到预设时长的情况下，所述第一网络设备向所述第一设备发送所述第一流量，其中，所述定时器为所述第一网络设备感知到所述第二网络设备与所述第一设备之间的通信链路故障后启动的。
在本申请中，可以设置定时器来监控受故障影响的流量无法正常转发的时长，可以减少受故障影响的流量可以正常转发后第一网络设备仍然按照无法正常转发时的操作处理这些流量所造成的资源浪费。
在其中一种可能的实施方式中，所述方法还包括：所述第一网络设备接收来自所述第三网络设备的通知，所述通知用于指示所述第一网络设备无需转发来自所述第二网络设备的所述第一流量；所述第一网络设备再次接收来自所述第二网络设备的所述第一流量，响应于所述通知，丢弃所述再次接收的来自所述第二网络设备的所述第一流量。
在本申请中，当第一网络设备因上述故障接收到来自第二网络设备的流量后，一般情况下会进行转发，但是，当该第一网络设备接收到来自第三网络设备的上述通知后，表明受故障影响的流量已经可以正常转发了，因此，不会再转发来自第二网络设备的这些流量，从而解决的这些流量多包的问题。
在其中一种可能的实施方式中，所述方法还包括：所述第一网络设备接收来自所述第三网络设备的所述第一流量；所述第一网络设备向所述第一设备发送来自所述第三网络设备的所述第一流量。
在本申请中，在受故障影响的流量经第三网络设备正常送达第一网络设备以后，第一网络设备可以正常转发该流量。
在其中一种可能的实施方式中，所述第一流量中的所有报文具备相同的特征，所述特征包括二元组、四元组、五元组或者七元组。
在其中一种可能的实施方式中，所述第一流量的目的MAC地址为所述第一设备的MAC地址。
第二方面，本申请提供一种转发流量的方法，所述方法包括：
第一网络设备向第二网络设备发送第一流量，所述第一流量的目的地址为第一设备；所述第一网络设备和所述第二网络设备为网络中的服务提供商边缘PE设备，所述第一设备分别通过第一链路和第二链路多归接入所述第一网络设备和所述第二网络设备，所述第一链路和所述第二链路的以太网链路标识ESI不同。
在本申请中，上述各个网络设备可以是EVPN网络中的设备，上述第一设备可以是该EVPN网络中下挂的环网中的用户侧设备，第一设备是多归接入EVPN网络中的第一网络设备和第二网络设备，且该第一设备接入该第一网络设备和第二网络设备的ESI不同，在这种情况下，当第一设备接入EVPN网络的路径例如接入第一网络设备的路径中出现故障时(若无该故障，第一流量通过第一网络设备转发给第一设备)，需要花费较长的时间才可以恢复流量的正常转发，为了减少流量丢包的时间，当第一网络设备接收到来自第三网络设备发往第一设备的流量即上述第一流量时，可以将该流量转发给第二网络设备，由该第二网络设备转发给第一设备，从而可以使得第一设备正常接收到流量，减少业务中断的概率。
在其中一种可能的实施方式中，所述方法还包括：所述第一网络设备通过接入链路AC接口广播所述第一流量。
在本申请中，还可以将来自第三网络设备的流量广播给该第一网络设备连接的用户侧设备，若该流量不是受上述故障影响的流量，那么可以使得该流量正常转发到目的地。
在其中一种可能的实施方式中，所述第一网络设备向所述第二网络设备发送第一流量，包括：在所述第一网络设备与所述第一设备之间的通信链路出现故障的情况下，所述第一网络设备向所述第二网络设备发送所述第一流量。
在其中一种可能的实施方式中，所述在所述第一网络设备与所述第一设备之间的通信链路出现故障的情况下，所述第一网络设备向所述第二网络设备发送第一流量，包括：在所述第一设备的MAC地址无法匹配到所述第一网络设备的本地媒体访问控制MAC地址转发表中的表项的情况下，所述第一网络设备向所述第二网络设备发送第一流量。
在本申请中，由于出现上述故障之后第一网络设备会逐一清除自身的MAC地址转发表中的表项，因此，故障之后第一网络设备接收到的来自第三网络设备的流量可能无法匹配到转发表项，这时可以将该流量向第二网络设备发送以进行转发，从而减少流量丢包。
在其中一种可能的实施方式中，所述第一网络设备向所述第二网络设备发送第一流量，包括：在定时器启动且未达到预设时长的情况下，所述第一网络设备向所述第二网络设备发送所述第一流量，其中，所述定时器为所述第一网络设备感知到所述第一网络设备与所述第一设备之间的通信链路故障后启动的。
在本申请中，可以设置定时器来监控受故障影响的流量无法正常转发的时长，可以减少受故障影响的流量可以正常转发后第一网络设备继续向第二网络设备发送这些流量所造成的资源浪费。
在其中一种可能的实施方式中，所述第一流量携带标签，所述标签指示所述第一流量来自所述第一网络设备。
在本申请中，通过标签来标识来自第一网络设备的第一流量，能够清楚区分哪些是受故障影响的流量，从而对这些流量进行监控转发。
在其中一种可能的实施方式中，所述方法还包括：所述第一网络设备接收第二流量；所述第一网络设备根据本地MAC地址转发表发送所述第二流量。
在其中一种可能的实施方式中，所述方法还包括：所述第一网络设备通过接入链路AC接口接收第三流量；在所述第三流量的目的MAC地址无法匹配到所述第一网络设备的本地MAC地址转发表中的表项的情况下，所述第一网络设备向所述网络中的网络设备广播所述第三流量。
上述两个实施例均表明在出现上述故障后，第一网络设备仍然可以正常转发不受故障影响的流量。
在其中一种可能的实施方式中，所述第一网络设备向第二网络设备发送第一流量，包括：所述第一网络设备获取缺省路由，所述缺省路由用于在所述第一网络设备与所述第一设备之间的通信链路出现故障时，向所述第二网络设备发送来自所述第三网络设备的所述第一流量；所述第一网络设备根据所述缺省路由向所述第二网络设备发送所述第一流量。
在本申请中，出现上述故障之后，第一网络设备能够向第二网络设备发送来自第三网络设备的流量，是因为预先在第一网络设备中配置的缺省路由，从而可以实现上述避免流量丢包的操作。
第三方面，本申请提供一种转发流量的方法，该方法包括：
第一网络设备向第二网络设备发送通知，所述通知用于指示所述第二网络设备无需转发来自第三网络设备的第一流量；所述第一流量的目的地址为第一设备，所述第一网络设备、所述第二网络设备和所述第三网络设备为网络中的服务提供商边缘PE设备，所述第一网络设备分别连接所述第二网络设备和所述第三网络设备，所述第一设备分别通过第一链路和第 二链路多归接入所述第二网络设备和所述第三网络设备，所述第一链路和所述第二链路的以太网链路标识ESI不同。
在本申请中，上述各个网络设备可以是EVPN网络中的设备，上述第一设备可以是该EVPN网络中下挂的环网中的用户侧设备，第一设备是多归接入EVPN网络中的第二网络设备和第三网络设备，且该第一设备接入该第二网络设备和第三网络设备的ESI不同，在这种情况下，当第一设备接入EVPN网络的路径例如接入第三网络设备的路径中出现故障时(若无该故障，第一流量通过第三网络设备转发给第一设备)，需要花费较长的时间才可以恢复流量的正常转发，为了减少流量丢包的时间，当第二网络设备接收到来自第三网络设备发往第一设备的流量即上述第一流量时(第三网络设备从第一网络设备接收该第一流量)，可以将该流量转发给第一设备，从而可以使得第一设备正常接收到流量，减少业务中断的概率。
但是，当第一网络设备已经学习到该第一设备的MAC路由后，可以正常将第一流量转发给第二网络设备，这时第二网络设备无需转发来自第三网络设备的第一流量，因此，第一网络设备可以向第二网络设备发送无需转发来自第三网络设备的第一流量的通知，从而解决了该第一流量多包的问题。该第一设备的MAC路由包括第一设备的MAC地址和对应的下一跳信息，该下一跳可以是该第一设备的下一跳设备的地址，或者该第一设备去往该下一跳设备的出接口等。
第四方面，本申请提供一种转发流量的方法，该方法包括：
在第一网络设备与所述第一设备之间的通信链路出现故障后，且第二网络设备未基于所述故障清除所述第一设备的MAC地址的情况下，所述第二网络设备向网络中的网络设备广播第一流量，所述第一流量的目的地址为所述第一设备，所述网络中的网络设备包括第三网络设备，所述第一网络设备、所述第二网络设备和所述第三网络设备为所述网络中的服务提供商边缘PE设备，所述第二网络设备分别连接所述第一网络设备和所述第三网络设备，所述第一设备分别通过第一链路和第二链路多归接入所述第一网络设备和所述第三网络设备，所述第一链路和所述第二链路的以太网链路标识ESI不同。
在本申请中，上述各个网络设备可以是EVPN网络中的设备，上述第一设备可以是该EVPN网络中下挂的环网中的用户侧设备，第一设备是多归接入EVPN网络中的第一网络设备和第三网络设备，且该第一设备接入该第一网络设备和第三网络设备的ESI不同，在这种情况下，当第一设备接入EVPN网络的路径例如接入第一网络设备的路径中出现故障时(若无该故障，第一流量通过第一网络设备转发给第一设备)，需要花费较长的时间才可以恢复流量的正常转发，为了减少流量丢包的时间，当第一网络设备因该故障向第二网络设备发送清除MAC的通知后，第二网络设备统一广播接收到的上述第一流量，第三网络设备接收到广播的第一流量后，可以转发给第一设备。当第二网络设备重新学习到该第一流量的MAC路由后，则停止广播该第一流量，可以按照学习到的新的路由转发流量，从而可以使得第一设备正常接收到流量，减少业务中断的概率。
第五方面，本申请提供一种转发流量的方法，该方法包括：
第一网络设备接收第二网络设备广播的第一流量，所述第一流量为所述第一网络设备在第三网络设备与所述第一目的设备之间的通信链路出现故障后，且所述第二网络设备未基于所述故障清除所述第一设备的MAC地址的情况下广播的，所述第一网络设备、所述第二网络设备和所述第三网络设备为网络中的服务提供商边缘PE设备，所述第二网络设备分别连接所述第一网络设备和所述第三网络设备，所述第一设备分别通过第一链路和第二链路多归接入所述第一网络设备和所述第三网络设备，所述第一链路和所述第二链路的以太网链路标 识ESI不同；所述第一网络设备向所述第一设备发送所述第一流量。
在本申请中，上述各个网络设备可以是EVPN网络中的设备，上述第一设备可以是该EVPN网络中下挂的环网中的用户侧设备，第一设备是多归接入EVPN网络中的第一网络设备和第三网络设备，且该第一设备接入该第一网络设备和第三网络设备的ESI不同，在这种情况下，当第一设备接入EVPN网络的路径例如接入第三网络设备的路径中出现故障时(若无该故障，第一流量通过第三网络设备转发给第一设备)，需要花费较长的时间才可以恢复流量的正常转发，为了减少流量丢包的时间，当第三网络设备因该故障向第二网络设备发送清除MAC的通知后，第二网络设备统一广播接收到的上述第一流量，第一网络设备接收到该第一流量后转发给第一设备，从而可以使得第一设备正常接收到流量，减少业务中断的概率。
第六方面，本申请提供一种转发流量的设备，该设备包括：
接收单元，用于接收来自第二网络设备的第一流量，所述第一流量的目的地址为第一设备，所述转发流量的设备和所述第二网络设备为网络中的服务提供商边缘PE设备，第一设备分别通过第一链路和第二链路多归接入所述转发流量的设备和所述第二网络设备，所述第一链路和所述第二链路的以太网链路标识ESI不同；
发送单元，用于向所述第一设备发送所述第一流量。
在其中一种可能的实施方式中，在所述发送单元向所述第一设备发送所述第一流量之前，所述设备还包括：
确定单元，用于确定本地流量特征表中所述第一流量的映射设备不是第三网络设备，所述第三网络设备为所述网络中的PE设备，所述第三网络设备分别连接所述转发流量的设备和所述第二网络设备。
其中，上述确定单元确定本地流量特征表中所述第一流量的来源设备不是第三网络设备，包括下面两种情况：
所述确定单元确定本地流量特征表中所述第一流量的映射设备为所述第二网络设备；
或者，所述确定单元确定本地流量特征表未指示所述第一流量的映射设备；在这种情况下，该转发流量的设备可以在所述本地流量特征表中设置所述第一流量的映射设备为所述第二网络设备。
在其中一种可能的实施方式中，上述接收单元，还用于接收来自所述第三网络设备的所述第一流量；
上述转发流量的设备还包括设置单元，用于在所述本地流量特征表中所述第一流量的映射设备不是所述第三网络设备的情况下，将所述本地流量特征表中所述第一流量的映射设备设置为所述第三网络设备；
上述发送单元，还用于向所述第一设备发送来自所述第三网络设备的所述第一流量。
且，上述接收单元，还用于再次接收来自所述第二网络设备的所述第一流量；
上述转发流量的设备还包括丢弃单元，用于在所述本地流量特征表中所述第一流量的映射设备为所述第三网络设备的情况下，丢弃所述再次接收的来自所述转发流量的设备的所述第一流量。
在其中一种可能的实施方式中，上述接收单元，还用于接收来自所述第三网络设备的第二流量；
上述发送单元，还用于在所述本地流量特征表中不包括所述第二流量的信息时，向所述网络中的第二设备发送所述第二流量。
在其中一种可能的实施方式中，所述第一流量携带标签，所述标签指示所述第一流量来 自所述第二网络设备。
在其中一种可能的实施方式中，上述发送单元具体用于：在定时器启动且未达到预设时长的情况下，向所述第一设备发送所述第一流量，其中，所述定时器为所述转发流量的设备感知到所述第二网络设备与所述第一设备之间的通信链路故障后启动的。
在其中一种可能的实施方式中，上述接收单元，还用于接收来自所述第三网络设备的通知，所述通知用于指示所述转发流量的设备无需转发来自所述第二网络设备的所述第一流量；
上述接收单元，还用于再次接收来自所述第二网络设备的所述第一流量；
上述转发流量的设备还包括丢弃单元，用于响应于所述通知，丢弃所述再次接收的来自所述第二网络设备的所述第一流量。
在其中一种可能的实施方式中，上述接收单元，还用于接收来自所述第三网络设备的所述第一流量；
上述发送单元，还用于向所述第一设备发送来自所述第三网络设备的所述第一流量。
在其中一种可能的实施方式中，所述第一流量中的所有报文具备相同的特征，所述特征包括二元组、四元组、五元组或者七元组。
在其中一种可能的实施方式中，所述第一流量的目的MAC地址为所述第一设备的MAC地址。
第七方面，本申请提供一种转发流量的设备，所述设备包括：
发送单元，用于向第二网络设备发送第一流量，所述第一流量的目的地址为第一设备；所述转发流量的设备和所述第二网络设备为网络中的服务提供商边缘PE设备，所述第一设备分别通过第一链路和第二链路多归接入所述转发流量的设备和所述第二网络设备，所述第一链路和所述第二链路的以太网链路标识ESI不同。
在其中一种可能的实施方式中，所述转发流量的设备还包括广播单元，用于通过接入链路AC接口广播所述第一流量。
在其中一种可能的实施方式中，所述发送单元具体用于：在所述转发流量的设备与所述第一设备之间的通信链路出现故障的情况下，向所述第二网络设备发送所述第一流量。
在其中一种可能的实施方式中，所述发送单元具体用于：在所述第一设备的MAC地址无法匹配到所述转发流量的设备的本地媒体访问控制MAC地址转发表中的表项的情况下，向所述第二网络设备发送第一流量。
在其中一种可能的实施方式中，所述发送单元具体用于：在定时器启动且未达到预设时长的情况下，所述转发流量的设备向所述第二网络设备发送所述第一流量，其中，所述定时器为所述转发流量的设备感知到所述转发流量的设备与所述第一设备之间的通信链路故障后启动的。
在其中一种可能的实施方式中，所述第一流量携带标签，所述标签指示所述第一流量来自所述转发流量的设备。
在其中一种可能的实施方式中，上述接收单元，还用于接收第二流量；
上述发送单元，还用于根据本地MAC地址转发表发送所述第二流量。
在其中一种可能的实施方式中，上述接收单元还用于：通过接入链路AC接口接收第三流量；
上述发送单元，还用于在所述第三流量的目的MAC地址无法匹配到所述转发流量的设备的本地MAC地址转发表中的表项的情况下，向所述网络中的网络设备广播所述第三流量。
在其中一种可能的实施方式中，上述转发流量的设备还包括获取单元：用于获取缺省路 由，所述缺省路由用于在所述转发流量的设备与所述第一设备之间的通信链路出现故障时，向所述第二网络设备发送来自所述第三网络设备的所述第一流量；
上述发送单元具体用于：根据所述缺省路由向所述第二网络设备发送所述第一流量。
第八方面，本申请提供一种转发流量的设备，该设备包括：
发送单元，用于向第二网络设备发送通知，所述通知用于指示所述第二网络设备无需转发来自第三网络设备的第一流量；所述第一流量的目的地址为第一设备，所述转发流量的设备、所述第二网络设备和所述第三网络设备为网络中的服务提供商边缘PE设备，所述转发流量的设备分别连接所述第二网络设备和所述第三网络设备，所述第一设备分别通过第一链路和第二链路多归接入所述第二网络设备和所述第三网络设备，所述第一链路和所述第二链路的以太网链路标识ESI不同。
第九方面，本申请提供一种转发流量的设备，该设备包括：
广播单元，用于在第一网络设备与所述第一设备之间的通信链路出现故障后，且转发流量的设备未基于所述故障清除所述第一设备的MAC地址的情况下，向网络中的网络设备广播第一流量，所述第一流量的目的地址为所述第一设备，所述网络中的网络设备包括第三网络设备，所述第一网络设备、所述转发流量的设备和所述第三网络设备为所述网络中的服务提供商边缘PE设备，所述转发流量的设备分别连接所述第一网络设备和所述第三网络设备，所述第一设备分别通过第一链路和第二链路多归接入所述第一网络设备和所述第三网络设备，所述第一链路和所述第二链路的以太网链路标识ESI不同。
第十方面，本申请提供一种转发流量的设备，该设备包括：
接收单元，用于接收第二网络设备广播的第一流量，所述第一流量为所述转发流量的设备在第三网络设备与所述第一目的设备之间的通信链路出现故障后，且所述第二网络设备未基于所述故障清除所述第一设备的MAC地址的情况下广播的，所述转发流量的设备、所述第二网络设备和所述第三网络设备为网络中的服务提供商边缘PE设备，所述第二网络设备分别连接所述转发流量的设备和所述第三网络设备，所述第一设备分别通过第一链路和第二链路多归接入所述转发流量的设备和所述第三网络设备，所述第一链路和所述第二链路的以太网链路标识ESI不同；所述转发流量的设备向所述第一设备发送所述第一流量。
第十一方面，本申请提供一种转发流量的设备，包括处理器、通信接口和存储器，其中，所述存储器用于存储程序指令和/或数据，所述处理器用于执行所述存储器中存储的程序指令，使得所述设备执行上述第一方面任一项所述的方法。
第十二方面，本申请提供一种转发流量的设备，包括处理器、通信接口和存储器，其中，所述存储器用于存储程序指令和/或数据，所述处理器用于执行所述存储器中存储的程序指令，使得所述设备执行上述第二方面任一项所述的方法。
第十三方面，本申请提供一种转发流量的设备，包括处理器、通信接口和存储器，其中，所述存储器用于存储程序指令和/或数据，所述处理器用于执行所述存储器中存储的程序指令，使得所述设备执行上述第三方面任一项所述的方法。
第十四方面，本申请提供一种转发流量的设备，包括处理器、通信接口和存储器，其中，所述存储器用于存储程序指令和/或数据，所述处理器用于执行所述存储器中存储的程序指令，使得所述设备执行上述第四方面任一项所述的方法。
第十五方面，本申请提供一种转发流量的设备，包括处理器、通信接口和存储器，其中，所述存储器用于存储程序指令和/或数据，所述处理器用于执行所述存储器中存储的程序指令，使得所述设备执行上述第五方面任一项所述的方法。
第十六方面，本申请提供一种转发流量的系统，该系统包括第一网络设备和第二网络设备，其中，该第一网络设备为上述第六方面所述的设备，该第二网络设备为上述第七方面所述的设备；或者，该第一网络设备为上述第十一方面所述的设备，该第二网络设备为上述第十二方面所述的设备。
第十七方面，本申请提供一种转发流量的系统，该系统包括第一网络设备和第二网络设备，其中，该第一网络设备为上述第六方面所述的设备，该第二网络设备为上述第八方面所述的设备；或者，该第一网络设备为上述第十一方面所述的设备，该第二网络设备为上述第十三方面所述的设备。
第十八方面，本申请提供一种转发流量的系统，该系统包括第一网络设备和第二网络设备，其中，该第一网络设备为上述第九方面所述的设备，该第二网络设备为上述第十方面所述的设备；或者，该第一网络设备为上述第十四方面所述的设备，该第二网络设备为上述第十五方面所述的设备。
第十九方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行以实现上述第一方面任意一项所述的方法；或者，所述计算机程序被处理器执行以实现上述第二方面任意一项所述的方法；或者，所述计算机程序被处理器执行以实现上述第三方面任意一项所述的方法；或者，所述计算机程序被处理器执行以实现上述第四方面任意一项所述的方法；或者，所述计算机程序被处理器执行以实现上述第五方面任意一项所述的方法。
第二十方面，本申请提供一种计算机程序产品，当上述计算机程序产品被计算机读取并执行时，上述第一方面任意一项上述的方法将被执行；或者，当上述计算机程序产品被计算机读取并执行时，上述第二方面任意一项上述的方法将被执行；或者，当上述计算机程序产品被计算机读取并执行时，上述第三方面任意一项上述的方法将被执行；或者，当上述计算机程序产品被计算机读取并执行时，上述第四方面任意一项上述的方法将被执行；或者，当上述计算机程序产品被计算机读取并执行时，上述第五方面任意一项上述的方法将被执行。
综上所述，本申请能够在用户侧设备多归接入多个PE，且用户侧设备分别与该多个PE之间的链路的ESI配置不同的情况下，解决用户侧设备与PE之间的链路出现故障后长时间丢包的问题。
附图说明
下面将对本申请实施例中所需要使用的附图作介绍。
图1至图3所示为本申请提供的一种转发流量的方法适用的系统场景示意图；
图4所示为本申请实施例提供的一种转发流量的方法的流程示意图；
图5所示为本申请实施例提供的另一种转发流量的方法的流程示意图；
图6为本申请实施例提供的一个设备的逻辑结构示意图；
图7为本申请实施例提供的另一个设备的逻辑结构示意图；
图8为本申请实施例提供的另一个设备的逻辑结构示意图；
图9为本申请实施例提供的另一个设备的逻辑结构示意图；
图10为本申请实施例提供的另一个设备的逻辑结构示意图；
图11为本申请实施例提供的设备的硬件结构示意图。
具体实施方式
下面结合附图对本申请实施例中的技术方案进行描述。
为了更好的理解本发明实施例提供的一种转发流量的方法，下面先对本发明实施例适用的场景进行示例性地描述。参阅图1，图1是本发明实施例提供的转发流量的方法适用的通信网络架构示意图。
该通信网络架构可以包括网络设备和用户侧设备，如图所示，网络设备之间互相建立通信连接，用户侧设备以环网的组网方式多归接入网络设备，例如图1中的用户侧设备111、用户侧设备112、用户侧设备113和用户侧设备114通过环网的方式双归接入网络设备101和网络设备102。
其中，网络设备可以包括提供商边缘设备(provider edge，PE)，提供商边缘设备PE可以是路由器或者交换机，用于连接用户侧设备和运营商骨干网络设备。用户的流量通过PE设备流入用户网络，或者通过PE设备流到骨干网。
用户侧设备可以包括客户端边缘设备(customer edge，CE)，CE为服务供应商所连接的用户侧的路由器或者交换机，CE通过连接一个或多个PE为用户提供服务接入。用户侧设备可以与一个或多个用户终端建立通信连接，用户终端可以包括手机、电脑、可穿戴智能设备、车载设备等各种电子设备。
需要说明的是，上述如图1所示通信网络架构仅为一个示例，例如网络设备101与网络设备103之间还可以包括一个或多个网络设备，双归接入网络设备101和网络设备102的用户侧设备也不限于图1所示的形式和个数等等。本申请实施例提供的转发流量的方法适用的通信网络架构不限于上述的描述，只要是应用到本申请实施例提供的转发流量的方法的场景，都是本申请实施例适用的场景，此处不再赘述。
另外，本申请实施例提供的转发流量的方法适用的通信网络架构可以是虚拟专用网络(virtual private network，VPN)、虚拟专用局域网业务(virtual private LAN service，VPLS)或者以太虚拟专用网络(Ethernetvirtual private network，EVPN)的架构等，特别地，可以是网络中双归或者多归的场景。
在介绍本申请提供的转发流量的方法之前，先示例性介绍本申请需要解决的技术问题。
参见图2，图2为在图1的基础添加了相关的信息得到，因此，上述对图1的描述适用于图2。在图2中，用户侧设备通过环网的方式双归接入网络设备101和网络设备102，为了避免下行流量成环，需要在环网中部署破坏协议。
上述流量成环指的是设备自发自收流量的现象，为便于理解该流量成环，下面举例说明。参见图2，假设没有部署破坏协议，那么，环网中没有破坏点，每一条链路都可以进行正常通信。假设用户侧设备112发送一个流量，该流量经过用户侧设备111到达网络设备101，网络设备101可以将流量发送给网络设备102和103，而网络设备102接收到该流量后，可能通过转发路径：用户侧设备114-用户侧设备113-用户侧设备112，又将流量转发回用户侧设备112，从而导致流量成环。
破坏协议可以包括多生成树协议(multi spanning tree protocol，MSTP)和以太网环保护交换(Ethernet ring protection switching，ERPS)协议等。通过部署的破换协议可以在环网中形成破坏点，避免流量成环。破坏点一般设置在两个设备之间的链路中，以使得该链路不通，从而避免流量成环。例如，在图2中，假设破坏点可以设置在用户侧设备112和用户侧和设备113之间的链路中，从而使得上述用户侧设备112发出的流量无法再转发回到用户侧设备112，避免的流量成环的问题。
需要说明的是，破坏点导致的链路不通是因为配置该链路不转发流量，而不是因为故障 等原因导致不能转发流量，当需要的时候可以开放破坏点的链路使其可以继续转发流量。例如，参见图2，假设用户侧设备112和用户侧设备113之间的链路为破坏点，即表明用户侧设备112和用户侧设备113之间的链路是不通的。
形成上述破坏点之后，网络设备101可以学习到来自用户侧设备111和用户侧设备112的媒体访问控制(Media Access Control，MAC)地址，而不能学习到来自用户侧设备113和用户侧设备114的MAC地址。同样的，网络设备102可以学习到来自用户侧设备113和用户侧设备114的MAC地址，而不能学习到来自用户侧设备111和用户侧设备112的MAC地址。
那么，从网络设备103向用户侧设备发送的流量可以走两条路径：一条是网络设备103-网络设备101-用户侧设备111-用户侧设备112；另一条是网络设备103-网络设备102-用户侧设备114-用户侧设备113。
在上述所述的网络架构下，用户侧设备通过环网的方式双归接入网络设备101和网络设备102，但是有时用户侧设备双归接入该两个网络设备的以太链路标识(Ethernet segment identifier，ESI)需要配置为不同的ESI，在这种情况下，现有的协议中网络设备101与网络设备102之间的链路是不通的，那么，当环网中出现故障时，下行流量丢包的时间无法保障，可能会导致长时间丢包的问题。
示例性地，以图3为例说明，上述对图1和图2的描述适用于图3。为了便于描述，图3中给部分链路标示了链路标号，网络设备101与用户侧设备111之间的链路标号为①，用户侧设备111与用户侧设备112之间的链路标号为②，用户侧设备112和用户侧设备113之间的链路标号为③，用户侧设备113和用户侧设备114之间的链路标号为④，用户侧设备114和网络设备102之间的链路标号为⑤。基于前面的描述可知，链路③为环网的破坏点。
在图3中，用户侧设备双归接入网络设备的ESI不同，即链路①和链路⑤配置的ESI不同，可以称链路①的ESI为ESI1，称链路⑤的ESI为ESI2。在这种情况下，当环网中出现故障时，例如当链路②出现故障时，会触发环网中的破坏协议进行路由重计算。
具体的，当链路②出现故障时，破坏点链路③可以正常通信。那么，用户侧设备112感知到故障后向环网内的其它设备即用户侧设备113、用户侧设备114和网络设备102通告该故障，用户侧设备111感知到故障后同样向环网中的其它设备即网络设备101通告该故障。环网中的其它设备感知到该故障后，会将自身的MAC地址表中的MAC地址清除，然后重新学习出现故障之后形成的新的网络拓扑中各个设备的MAC地址，以形成新的MAC路由。该MAC路由包括设备的MAC地址和对应的下一跳信息，该下一跳可以是下一跳设备的地址，或者去往下一跳设备的出接口等。网络设备101和网络设备102在清除MAC地址之后，会向网络设备103发送清除MAC地址的通知，从而使得网络设备103也会在出现故障之后清除自身的MAC地址表中的MAC地址，然后重新学习故障之后形成的新的网络拓扑中各个设备的MAC地址，以形成新的MAC路由。
但是，当网络设备3中的MAC地址表中的MAC地址数量较多时，清除MAC地址的时间需要较长，且在出现上述故障之后，网络设备103中还没请除用户侧设备112的MAC地址，那么此时如果网络设备103接收到发往用户侧设备112的流量，会根据该流量原来的转发路径即网络设备103-网络设备101-用户侧设备111-用户侧设备112来进行流量的转发，但是由于出现了故障，该转发路径已经走不通，从而导致该流量丢包。又因为，网络设备3中的MAC地址表中的MAC地址数量较多，需要较长的时间才可以清除该用户侧设备112的MAC地址，那么会导致该流量的丢包时间过长，从而影响业务的正常运行，并影响用户体验。
需要说明的是，上述只是以链路②出现故障为例介绍，实际中也可以是链路①出现故障 或者用户侧设备111出现故障等。
为了解决上述问题，本申请提供了一种转发流量的方法，下面通过几个实施例对本申请提供的转发流量的方法进行介绍。
实施例一
本实施例提供的转发流量的方法可以参见图4，该方法可以适用于上述图3所示场景以解决上述环网中出现故障后导致流量丢包时间过长的问题，该方法可以包括但不限于如下步骤：
S401、第一网络设备向第二网络设备发送第一流量，该第一流量的目的地址为第一设备。
在具体实施例中，该第一网络设备可以是上述图3中所示的网络设备101，该第二网络设备可以是图3中所示的网络设备102，该第一设备可以是图3所示中的用户侧设备112。第一设备通过环网的组网方式多归接入第一网络设备和第二网络设备。该环网可以是图3中所示的包括多个用户侧设备的环网，该环网中的用户侧设备分别通过第一链路和第二链路多归接入第一网络设备和第二网络设备，该第一链路的ESI和该第二链路的ESI不同。其中，该第一链路例如可以是图3中链路①，该第二链路例如可以是图3中的链路⑤。
上述第一网络设备向第二网络设备发送第一流量可以是，在上述环网中出现故障的情况下，第一网络设备向第二网络设备发送该第一流量。该故障可以是第一网络设备和第一设备之间的通信链路上出现的故障，例如可以是上述图3中所示的链路②出现的故障等。在未出现该故障时，下行到该第一设备的流量可以通过该第一网络设备进行转发，由于环网中破坏协议设置的破坏点的存在，第二网络设备与第一设备之间的通信链路是不通的。
基于上述的描述可知，当第一网络设备和第二网络设备感知到上述故障之后，会基于该故障清除自身已存储有的未出现该故障前的网络拓扑中设备的MAC地址，并且每清除一个MAC地址都会向第三网络设备发送清除该MAC地址的通知，以使得第三网络设备也清除该MAC地址。
示例性地，第一网络设备和第二网络设备分别和第三网络设备建立了边界网关协议(border gateway protocol，BGP)邻居，或者建立开放最短路径优先(open shortest path first，OSPF)邻居，或者建立中间系统到中间系统(intermediate system to intermediate system，ISIS)的链接状态路由协议邻居等，那么，第一网络设备和第二网络设备可以通过BGP协议或者OSPF协议或者ISIS协议等向第三网络设备发送清除该MAC地址的通知。
该第三网络设备可以是图3中所示的网络设备103，该第三网络设备无法直接感知到上述故障，因此只能通过第一网络设备和第二网络设备告知来清除自身已存储有的未出现该故障前的网络拓扑中设备的MAC地址。不管是第一网络设备和第二网络设备，还是第三网络设备，都可以一边清除自身已存储有的未出现该故障前的网络拓扑中设备的MAC地址，一边学习出现故障后发生改变的网络拓扑中设备的MAC地址，以形成新的MAC路由。
在出现上述故障之后，该第一网络设备接收来自第三网络设备的第一流量，一方面，该第一网络设备可以通过接入链路(access link，AC)接口向该环网中的用户侧设备广播该第一流量；另一方面，该第一网络设备还可以向第二网络设备发送该第一流量。
该第一流量的目的地址为第一设备可以是该第一流量的目的MAC地址为该第一设备的MAC地址。
在具体实施例中，在出现上述故障之后，现有的技术方案中，只有等第三网络设备中清除了该第一设备的MAC地址之后才可以正常广播或单播该第一流量。该广播指的是在该第 三网络设备清除完该第一设备的MAC地址但还未学习到上述故障后发生改变的网络拓扑中该第一设备的MAC路由的情况下，第三网络设备通过广播的方法来发送该第一流量。该单播指的是在该第三网络设备已经重新学习到上述故障后发生改变的网络拓扑中该第一设备的MAC路由的情况下，第三网络设备在收到该第一流量之后，可以根据MAC地址转发表来单播该第一流量。该第一设备的MAC路由包括第一设备的MAC地址和对应的下一跳信息，该下一跳可以是该第一设备的下一跳设备的地址，或者该第一设备去往该下一跳设备的出接口等。
而在第三网络设备清除该第一设备的MAC地址之前，该第一流量会按照原来的转发路径即第三网路设备-第一网络设备-第一设备这一路径来转发该第一流量，但由于第一网络设备和第一设备之间的链路出现了故障，因此第一流量无法正常转发到该第一设备，导致流量丢包，造成业务断流。
为了解决该流量丢包的问题，在本申请实施例中，出现上述故障之后，第一网络设备从第三网络设备接收到上述第一流量，可以正常进行MAC地址表的地址匹配，但由于出现故障后第一网络设备已经将MAC地址表中的MAC地址清除，因此，第一网络设备的MAC地址表中无法查找到第一流量的源MAC地址和目的MAC地址，因此，第一网络设备可以将该第一流量通过AC接口广播给用户侧设备，另外，第一网络设备还将该第一流量发送给第二网络设备。
或者，在另一种可能的实施方式中，出现上述故障之后，第一网络设备从第三网络设备接收到上述第一流量，可以不查询MAC地址表，直接将该第一流量通过AC接口广播给用户侧设备，并将该第一流量发送给第二网络设备。
需要说明的是，现有技术中第一网络设备和第二网络设备是不进行通信的，本申请实施例为了在出现上述故障后，第一网络设备能够将上述第一流量发送到第二网络设备进行转发，第一网络设备中配置了将该第一流量发往该第二网络设备的缺省路由，该缺省路由包括该第二网络设备的MAC地址等信息，在出现上述故障后，第一网络设备可以根据该缺省路由将从第三网络设备接收到的流量例如上述第一流量发送给第二网络设备。
S402、第二网络设备接收该来自第一网络设备的第一流量。
上述第一网络设备通过缺省路由向第二网络设备发送第一流量后，第二网络设备可以接收到该第一流量。
S403、第二网络设备向该第一设备发送该第一流量。
在出现上述故障之后，会触发环网中的破坏协议进行路由重计算，破坏点可以消除，那么上述第二网络设备和第一设备之间的通信链路可以正常通信，因此，第二网络设备接收到来自第一网络设备的上述第一流量后，可以正常向第一设备转发，从而可以减少因上述故障导致的流量掉包。
需要说明的是，上述来自第一网络设备的第一流量指的是该第一流量经过该第一网络设备，并由该第一网络设备转发给该第二网络设备的流量。
为了便于理解，还是以图3为例介绍说明。在图3中，链路②出现故障后，网络设备101接收到来自网络设备103发往用户侧设备112的第一流量，网络设备101在通过AC口向环网的用户侧设备广播该第一流量的同时，还向网络设备102发送该第一流量。由于故障后破坏点链路③可以恢复正常通信，因此，网络设备102可以通过转发路径：网络设备102-用户侧设备114-用户侧设备113-用户侧设备112，向用户侧设备112转发该第一流量，从而使得该第一流量减少丢包。
在一种可能的实施方式中，基于上述图4所述的转发流量的方法，在出现上述故障之后，第二网络设备可以通过流量特征表来监控从第一网络设备接收到的流量。该流量特征表可以记录该故障之后从第一网络设备接收到的流量的特征，以及记录这些流量到达该第二网络设备之前经过的一个或多个设备的标识。
流量的特征可以是流量中的报文的特征，一个流量中包括的所有的报文的特征相同，该特征包括流量中的报文的二元组、四元组、五元组或者七元组。设备的标识可以包括设备的互联网协议(internet protocol，IP)地址或者MAC地址等。上述流量到达该第二网络设备之前经过的一个或多个设备的标识可以包括该第一网络设备的标识。在本申请中，该流量到达该第二网络设备之前经过的一个或多个设备可以称为该流量的映射设备。
其中，流量的二元组包括流量的源MAC地址和目的MAC地址。流量的四元组包括流量的源IP地址、目的IP地址、源端口和目的端口。流量的五元组包括流量的源IP地址、目的IP地址、源端口、目的端口和协议号。流量的七元组包括流量的源IP地址、目的IP地址、协议号、源端口、目的端口、服务类型以及接口索引。
在出现上述故障后，第二网络设备接收到从第一网络设备发送过来的上述第一流量，可以通过以下三种情况来处理该第一流量：
第一种情况、第二网络设备确定流量特征表中还没有记录有该第一流量的信息。
具体的，第二网络设备可以解析接收到的第一流量中的报文，获取报文中的特征，将获取的特征与流量特征表中的特征进行比较，在流量特征表中没有与该获取的特征相同的特征，则表明流量特征表中还没有记录有该第一流量的信息。即表明这是第二网络设备在上述故障后第一次接收到来自第一网络设备的第一流量。
在这种情况下，第二网络设备在流量特征表中添加该第一流量的信息，包括添加该第一流量的特征和该第一流量的映射设备的标识等。然后，第二网络设备将从第一网络设备接收的第一流量发送给第一设备。例如，可以参见表1。
表1
源MAC地址 目的MAC地址 映射设备
1.1.1.1 2.2.2.2 3.3.3.3
表1以流量的特征为二元组为例示出了流量特征表中记录的第一流量的信息。在表1中可以看到，流量特征表可以记录第一流量的源MAC地址(例如可以是1.1.1.1)、目的MAC地址(例如可以是2.2.2.2)和该第一流量的映射设备。该映射设备可以是上述第一网络设备，映射设备可以通过MAC地址来标识，例如该映射设备的MAC地址可以是3.3.3.3。
第二种情况、第二网络设备确定流量特征表中该第一流量的映射设备包括上述第一网络设备。
同样的，第二网络设备可以解析接收到的第一流量中的报文，获取报文中的特征，将获取的特征与流量特征表中的特征进行比较，在流量特征表中找到与该获取的特征相同的特征则表明流量特征表中记录有该第一流量的信息，然后，再在流量特征表中查找该第一流量的映射设备，若该第一流量的映射设备为上述第一网络设备即表明这是第二网络设备在上述故障后又一次接收到了来自第一网络设备的第一流量。
由于流量特征表中第一流量的映射设备仍然是上述第一网络设备，那么表明第二网络设备还没有接收到来自第三网络设备的第一流量，因为若接收到了来自第三网络设备的第一流量，第二网络设备会将流量特征表中第一流量的映射设备设置为第三网络设备。第二网络设 备还没有接收到来自第三网络设备的第一流量表明，在出现上述故障之后，第三网络设备还没有清除自身存储的MAC地址表中的第一设备的MAC地址，仍然将第一流量转发给第一网络设备，第一网络设备会继续将接收到的第一流量发送给第二网络设备。然后，第二网络设备将从第一网络设备接收的第一流量发送给第一设备。
需要说明的是，上述来自第三网络设备的第一流量指的是该第一流量由第三网络设备向第二网络设备发出，不需要经过上述第一网络设备转发的第一流量。为了便于理解，可以参见图3。对于第二网络设备即网络设备102来说，来自第三网络设备即网络设备103的第一流量指的是从网络设备103发出后经路径⑥到达网络设备102的第一流量。当然，路径⑥中还可以包括其它的一个或多个网络设备。而上述来自第一网络设备即网络设备101的第一流量则指的是该从网络设备103发出后，经路径⑦后到达网络设备101，然后再经路径⑧到达网路设备102的第一流量。当然，路径⑦和路径⑧中还可以包括其它的一个或多个网络设备。
第三种情况、第二网络设备确定流量特征表中该第一流量的映射设备包括上述第三网络设备。
同样的，第二网络设备可以解析接收到的第一流量中的报文，获取报文中的特征，将获取的特征与流量特征表中的特征进行比较，在流量特征表中找到与该获取的特征相同的特征则表明流量特征表中记录有该第一流量的信息，然后，再在流量特征表中查找该第一流量的映射设备。若该第一流量的映射设备为上述第三网络设备，即表明在又一次接收到上述来自第一网络设备的第一流量之前，第二网络设备已经接收到了来自第三网络设备的第一流量。
具体的，在出现上述故障之后，第三网络设备接收到来自第一网络设备发送的清除第一设备的MAC地址的通知后完成了该第一设备的MAC地址的清除，然后，当该第三网络设备再次接收到上述第一流量的时候，若还没有学习到故障后新的网络拓扑中第一设备的MAC路由，第三网络设备可以将该接收到的第一流量广播出去，那么此时第一网络设备和第二网络设备都可以接收到该第一流量。若该第三网络设备已经学习到故障后新的网络拓扑中第一设备的MAC路由，那么，第三网络设备可以根据MAC地址表向第二网络设备单播发送第一流量。
第二网络设备接收到该第三网络设备广播的第一流量后，可以在流量特征表中查找到该第一流量的信息，若流量特征表中的第一流量的映射设备不是该第三网络设备，那么，第二网络设备会将流量特征表中第一流量的映射设备设置为该第三网络设备。具体的，可以是将流量特征表中的第一流量的映射设备的标识替换为该第三网络设备的标识。
在流量特征表中第一流量的映射设备为上述第三网络设备的情况下，第二网络设备不会将再次接收到的来自第一网络设备的第一流量发送给第一设备，可以直接将该再次接收到的来自第一网络设备的第一流量丢弃。
在流量特征表中第一流量的映射设备为上述第三网络设备的情况下，第二网络设备会将来自第三网络设备的第一流量发送给第一设备。
在本申请实施例中，通过流量特征表来监控接收到的第一流量的映射设备，只要流量监控表中的第一流量的映射设备不是第三网络设备，那么第二网络设备就可以继续转发来自第一网络设备的第一流量。当流量监控表中的第一流量的映射设备为第三网络设备时，表明第三网络设备在出现上述故障后已经可以正常进行第一流量的转发，那么，为了避免多包，第二网络设备会丢弃再次接收到的来自第一网络设备的第一流量，只转发来自第三网络设备的第一流量。
在一种可能的实施方式中，结合上述实施例一和实施例二，在出现上述故障后，第二网 络设备还可以接收来自第三网络设备的第二流量，该第二流量发往第二设备。该第二设备例如可以是图3中的用户侧设备113或用户侧设备114。当然，第二网络设备可以在流量特征表中查找该第二流量的特征，但由于流量特征表只是用于记录故障后来自第一网络设备的流量的信息，因此，流量特征表中不包括该第二流量的信息。然后，第二网络设备向第二设备发送该第二流量。
在一种可能的实施方式中，结合上述实施例一和实施例二，在出现上述故障后，第一网络设备还可以接收第三流量，该第三流量可以是来自其他网络设备例如第三网络设备，若可以在自身的MAC地址表中找到该第三流量的转发表项，那么第一网络设备可以根据该转发表项发送该第三流量。
结合上述实施例一和实施例二，在出现上述故障后，第一网络设备还可以接收第四流量，该第四流量是通过AC接口接收到，表明是来自用户侧设备的流量，同样的，若可以在自身的MAC地址表中找到该第四流量的转发表项，那么第一网络设备可以根据该转发表项发送该第四流量。若没有在自身的MAC地址表中找到该第四流量的转发表项，那么，第一网络设备可以将该第四流量广播给网络中的其它网络设备。
在一种可能的实施方式中，在出现上述故障之后，第一网络设备向第二网络设备发送的第一流量可以携带标签，该标签可以用于指示该第一流量来自该第一网络设备。该标签可以添加在该第一流量包括的报文的头部，例如可以是在该第一流量的报文的头部中添加一个字段，通过该字段携带该标签，或者，可以是在原有的字段中携带该标签。第二网络设备接收到该携带标签的第一流量之后，可以识别该标签，从而获知该携带标签的流量来自第一网络设备。
在一种可能的实施方式中，上述各个实施例中第一网络设备和第二网络设备所做的操作都可以是在定时器未达到预设时长之前所做的操作。
在具体实施例中，第一网络设备和第二网络设备感知到上述故障之后，例如可以是清除完自身的MAC地址转发表之后，分别设置一个定时器。第一网络设备的定时器可以称为第一定时器，第二网络设备的定时器可以称为第二定时器。第一定时器定时的时长可以是第一预设时长，第二定时器定时的时长可以是第二预设时长。其中，第一预设时长和第二预设时长大于上述第三网络设备的收敛时间，该收敛时间包括从出现故障开始到第三网络设备根据第一网络设备和第二网络设备的通知清除完自身的MAC地址表的时长。示例性地，该第一预设时长和第二预设时长可以是60秒钟，或者，也可以是50秒或70秒等等。
在另一种可能的实施方式中，为了解决上述多包的问题，除了可以采用上述流量特征表监控的实施方式之外，还可以采用如下的实施方式：
结合上述图4所述的转发流量的方法，在具体实施例中，上述第三网络设备在接收到来自第一网络设备发送的清除第一设备的MAC地址的通知后完成了该第一设备的MAC地址的清除，然后，向第二网络设备发送通知，该通知用于指示所述第二网络设备无需转发来自所述第一网络设备的所述第一流量。示例性地，该通知可以是该第三网络设备已经可以向该第二网络设备发送第一流量的通知，或者，该通知为第三网络设备清除完该第一设备的MAC地址后首次以广播的方式向第二网络设备发送的第一流量，或者，该通知可以是预先定义的一个指示消息等。
第三网络设备清除完该第一设备的MAC地址后向第二网络设备发送上述通知是因为，清除完该第一设备的MAC地址后，不管该第三网络设备有没有重新学习到故障后的网络拓 扑中的第一设备的MAC路由，第三网络设备都可以将第一流量发送到第二网络设备。即，若清除第一设备的MAC地址后，第三网络设备没有重新学习到该第一设备的MAC路由，那么第三网络设备会通过广播的方式向其它网络设备包括第二网络设备发送该第一流量；若清除第一设备的MAC地址后，第三网络设备重新学习到了该第一设备的MAC路由，那么第三网络设备会根据学习到的该第一设备的MAC路由通过单播的方式向第二网络设备发送该第一流量。
因此，第二网络设备接收到该通知后，再次接收到来自第一网络设备的第一流量时，不会再转发该来自第一网络设备的第一流量，可以将其丢弃。同时，第二网络设备会将来自第三网络设备的第一流量转发给第一设备。从而避免了该第一流量多包的问题。
上述图4所述的转发流量的方法及其可能的实施方式主要是通过在第一网络设备和第二网设备之间配置缺省路由，以用于在出现上述故障的情况下通过第二网络设备来完成上述第一流量的转发，以减少流量的丢包。在本申请中，解决上述故障后减少流量掉包的问题还可以通过第三网络设备广播流量的方式来实现，具体参见实施例二的具体介绍。
实施例二
实施例二为本申请提供的另一种转发流量的方法，本实施例提供的转发流量的方法可以参见图5，该方法可以适用于上述图3所示场景以解决上述环网中出现故障后导致流量丢包时间过长的问题，该方法可以包括但不限于如下步骤：
S501、第一网络设备感知接入的环网中的故障，并基于该故障清除自身的MAC地址表中的MAC地址，同时向第三网络设备发送清除MAC地址的通知。
S502、第三网络设备接收到该通知，并清除自身的MAC地址表中的MAC地址。
本实施例中的第一网络设备、第二网络设备、第三网络设备和第一设备之间的关系，以及S501和S502的具体实现过程可以参见上述实施例一的S401中的对应描述，此处不再赘述。
S503、在接收到上述通知后，且在没有重新学习到第一设备的MAC路由之前，第三网络设备将接收到的目的MAC地址为第一设备的第一流量广播给其它网络设备。
在具体实施例中，该通知可以是第一网络设备感知到上述故障之后，向第三网络设备发送的第一个清除MAC地址的通知。第三网络设备接收到该通知之后，开始清除对应的MAC地址，同时可以开始学习故障后的网络拓扑中的设备的MAC路由。
如果接收到上述通知后，还没有重新学习到该第一设备的MAC路由，第三网络设备可以将发往该第一设备的第一流量广播出去，以使得第二网路设备可以接收到该第一流量。
S504、第二网络设备接收到该广播的第一流量，并将该第一流量向用户侧设备广播，使得第一设备能够接收到该第一流量。
第二网络设备接收到从第三网络设备广播的该第一流量后，若是第一次接收到该第一流量的，那么，无法在自身的MAC地址表中查找到该第一流量的转发信息，那么第二网络设备可以以广播的方式从AC接口发送给用户侧设备，从而使得第一设备可以接收到该第一流量。第一设备接收到该第一流量后会向第二网络设备返回一个消息，表明该第一流量是发给该第一设备的。那么，第二网络设备接收到该消息之后，可以在MAC地址转发表中添加该第一流量的转发表项，例如记录该第一流量的特征例如源MAC地址和目的MAC地址以及发出端口号等信息。当第二网络设备再次接收到该第一流量时，可以通过MAC地址转发表中的该转发表项进行单播发送给第一设备。
在一种可能的实施方式中，如果第三网络设备接收到上述通知之后，已经重新学习到该第一设备的MAC路由，那么第三网络设备可以根据MAC地址转发表正常转发该第一设备的第一流量。
在一种可能的实施方式中，当上述故障不是图3中链路②出现故障，而是链路④出现故障，那么也可以通过上述各个实施例所述的方法解决流量丢包时间过长的问题。在这种情况下，上述第一网络设备可以是图3中的网络设备102，上述第二网络设备可以是图3中的网络设备101，上述第三网路设备还是图3中的网络设备103，上述第一设备可以是图3中的用户侧设备113。
上述实施例二中，当第一网络设备因上述故障向第三网络设备发送清除MAC的通知后，第三网络设备统一广播接收到的上述第一流量，第二网络设备接收到广播的第一流量后，可以转发给第一设备。当第三网络设备重新学习到该第一流量的MAC路由后，则停止广播该第一流量，可以按照学习到的新的路由转发流量，从而可以使得第一设备正常接收到流量，减少业务中断的概率。
上述主要对本申请实施例提供的转发流量的方法进行了介绍。可以理解的是，各个设备为了实现上述对应的功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用使用不同方法来实现所描述的功能，但这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图6示出了设备的一种可能的逻辑结构示意图，该设备可以是上述各个实施例中的第二网络设备。需要说明的是，在描述图6所述设备的过程中涉及的第二网络设备可以是上述各个实施例中的第一网络设备。图6所述的设备600包括接收单元601和发送单元602。其中：
接收单元601，用于接收来自第二网络设备的第一流量，该第一流量的目的地址为第一设备，该设备600和该第二网络设备为网络中的服务提供商边缘PE设备，第一设备分别通过第一链路和第二链路多归接入该设备600和该第二网络设备，该第一链路和该第二链路的以太网链路标识ESI不同；所述接收单元601可以执行图4所示的步骤402所述的操作。
发送单元602，用于向该第一设备发送该第一流量。所述发送单元602可以执行图4所示的步骤403所述的操作。
在其中一种可能的实施方式中，在该发送单元602向该第一设备发送该第一流量之前，该设备还包括：
确定单元，用于确定本地流量特征表中该第一流量的映射设备不是第三网络设备，该第三网络设备为该网络中的PE设备，该第三网络设备分别连接该设备600和该第二网络设备。
其中，上述确定单元确定本地流量特征表中该第一流量的来源设备不是第三网络设备， 包括下面两种情况：
该确定单元确定本地流量特征表中该第一流量的映射设备为该第二网络设备；
或者，该确定单元确定本地流量特征表未指示该第一流量的映射设备；在这种情况下，该设备600可以在该本地流量特征表中设置该第一流量的映射设备为该第二网络设备。
在其中一种可能的实施方式中，上述接收单元601，还用于接收来自该第三网络设备的该第一流量；
上述设备600还包括设置单元，用于在该本地流量特征表中该第一流量的映射设备不是该第三网络设备的情况下，将该本地流量特征表中该第一流量的映射设备设置为该第三网络设备；
上述发送单元602，还用于向该第一设备发送来自该第三网络设备的该第一流量。
且，上述接收单元601，还用于再次接收来自该第二网络设备的该第一流量；
上述设备600还包括丢弃单元，用于在该本地流量特征表中该第一流量的映射设备为该第三网络设备的情况下，丢弃该再次接收的来自该设备600的该第一流量。
在其中一种可能的实施方式中，上述接收单元601，还用于接收来自该第三网络设备的第二流量；
上述发送单元602，还用于在该本地流量特征表中不包括该第二流量的信息时，向该网络中的第二设备发送该第二流量。
在其中一种可能的实施方式中，该第一流量携带标签，该标签指示该第一流量来自该第二网络设备。
在其中一种可能的实施方式中，上述发送单元602具体用于：在定时器启动且未达到预设时长的情况下，向该第一设备发送该第一流量，其中，该定时器为该设备600感知到该第二网络设备与该第一设备之间的通信链路故障后启动的。
在其中一种可能的实施方式中，上述接收单元601，还用于接收来自该第三网络设备的通知，该通知用于指示该设备600无需转发来自该第二网络设备的该第一流量；
上述接收单元601，还用于再次接收来自该第二网络设备的该第一流量；
上述设备600还包括丢弃单元，用于响应于该通知，丢弃该再次接收的来自该第二网络设备的该第一流量。
在其中一种可能的实施方式中，上述接收单元601，还用于接收来自该第三网络设备的该第一流量；
上述发送单元602，还用于向该第一设备发送来自该第三网络设备的该第一流量。
图6所示设备600中各个单元的具体操作以及有益效果可以参见上述图4所述方法及其可能的实施方式中的描述，此处不再赘述。
在采用对应各个功能划分各个功能模块的情况下，图7示出了设备的一种可能的逻辑结构示意图，该设备可以是上述各个实施例中的第一网络设备。需要说明的是，在描述图7所述设备的过程中涉及的第二网络设备可以是上述各个实施例中的第二网络设备。图7所述的设备700包括发送单元701。其中：
发送单元701，用于向第二网络设备发送第一流量，该第一流量的目的地址为第一设备；该设备700和该第二网络设备为网络中的服务提供商边缘PE设备，该第一设备分别通过第一链路和第二链路多归接入该设备700和该第二网络设备，该第一链路和该第二链路的以太网链路标识ESI不同。所述发送单元701可以执行图4所示的步骤401所述的操作。
在其中一种可能的实施方式中，该设备700还包括广播单元，用于通过接入链路AC接口广播该第一流量。
在其中一种可能的实施方式中，该发送单元701具体用于：在该设备700与该第一设备之间的通信链路出现故障的情况下，向该第二网络设备发送该第一流量。
在其中一种可能的实施方式中，该发送单元701具体用于：在该第一设备的MAC地址无法匹配到该设备700的本地媒体访问控制MAC地址转发表中的表项的情况下，向该第二网络设备发送第一流量。
在其中一种可能的实施方式中，该发送单元701具体用于：在定时器启动且未达到预设时长的情况下，该设备700向该第二网络设备发送该第一流量，其中，该定时器为该设备700感知到该设备700与该第一设备之间的通信链路故障后启动的。
在其中一种可能的实施方式中，该第一流量携带标签，该标签指示该第一流量来自该设备700。
在其中一种可能的实施方式中，上述接收单元，还用于接收第二流量；
上述发送单元701，还用于根据本地MAC地址转发表发送该第二流量。
在其中一种可能的实施方式中，上述接收单元还用于：通过接入链路AC接口接收第三流量；
上述发送单元701，还用于在该第三流量的目的MAC地址无法匹配到该设备700的本地MAC地址转发表中的表项的情况下，向该网络中的网络设备广播该第三流量。
在其中一种可能的实施方式中，上述设备700还包括获取单元：用于获取缺省路由，该缺省路由用于在该设备700与该第一设备之间的通信链路出现故障时，向该第二网络设备发送来自该第三网络设备的该第一流量；
上述发送单元701具体用于：根据该缺省路由向该第二网络设备发送该第一流量。
图7所示设备700中各个单元的具体操作以及有益效果可以参见上述图4所述方法及其可能的实施方式中的描述，此处不再赘述。
在采用对应各个功能划分各个功能模块的情况下，图8示出了设备的一种可能的逻辑结构示意图，该设备可以是上述各个实施例中的第三网络设备。需要说明的是，在描述图8所述设备的过程中涉及的第二网络设备可以是上述各个实施例中的第二网络设备，在描述图8所述设备的过程中涉及的第三网络设备可以是上述各个实施例中的第一网络设备。图8所述的设备800包括发送单元801。其中：
发送单元801，用于向第二网络设备发送通知，该通知用于指示该第二网络设备无需转发来自第三网络设备的第一流量；该第一流量的目的地址为第一设备，该设备800、该第二网络设备和该第三网络设备为网络中的服务提供商边缘PE设备，该设备800分别连接该第二网络设备和该第三网络设备，该第一设备分别通过第一链路和第二链路多归接入该第二网络设备和该第三网络设备，该第一链路和该第二链路的以太网链路标识ESI不同。
图8所示设备800中各个单元的具体操作以及有益效果可以参见上述图4及其可能的实施方式中，通过第三网络设备向第二网络设备发送无需转发来自所述第一网络设备的所述第一流量的通知的实施例的描述，此处不再赘述。
在采用对应各个功能划分各个功能模块的情况下，图9示出了设备的一种可能的逻辑结构示意图，该设备可以是上述各个实施例中的第三网络设备。需要说明的是，在描述图9所 述设备的过程中涉及的第三网络设备可以是上述各个实施例中的第二网络设备。图9所述的设备900包括广播单元901。其中：
广播单元901，用于在第一网络设备与该第一设备之间的通信链路出现故障后，且设备900未基于该故障清除该第一设备的MAC地址的情况下，向网络中的网络设备广播第一流量，该第一流量的目的地址为该第一设备，该网络中的网络设备包括第三网络设备，该第一网络设备、该设备900和该第三网络设备为该网络中的服务提供商边缘PE设备，该设备900分别连接该第一网络设备和该第三网络设备，该第一设备分别通过第一链路和第二链路多归接入该第一网络设备和该第三网络设备，该第一链路和该第二链路的以太网链路标识ESI不同。
所述广播单元901可以执行图5所示的步骤503所述的操作。
图9所示设备900中各个单元的具体操作以及有益效果可以参见上述实施例二及其可能的实施方式中的描述，此处不再赘述。
在采用对应各个功能划分各个功能模块的情况下，图10示出了设备的一种可能的逻辑结构示意图，该设备可以是上述各个实施例中的第二网络设备。需要说明的是，在描述图10所述设备的过程中涉及的第二网络设备可以是上述各个实施例中的第三网络设备，在描述图10所述设备的过程中涉及的第三网络设备可以是上述各个实施例中的第一网络设备。图10所述的设备1000包括接收单元1001。其中：
接收单元1001，用于接收第二网络设备广播的第一流量，该第一流量为该设备1000在第三网络设备与该第一目的设备之间的通信链路出现故障后，且该第二网络设备未基于该故障清除该第一设备的MAC地址的情况下广播的，该设备1000、该第二网络设备和该第三网络设备为网络中的服务提供商边缘PE设备，该第二网络设备分别连接该设备1000和该第三网络设备，该第一设备分别通过第一链路和第二链路多归接入该设备1000和该第三网络设备，该第一链路和该第二链路的以太网链路标识ESI不同；该设备1000向该第一设备发送该第一流量。
所述接收单元1001可以执行图5所示的步骤504所述的接收的操作。
图10所示设备1000中各个单元的具体操作以及有益效果可以参见上述实施例二及其可能的实施方式中的描述，此处不再赘述。
图11所示为本申请提供的设备的一种可能的硬件结构示意图，该设备可以是上述实施例所述方法中的任意一个网络设备，例如可以是第一网络设备，或者可以是第二网络设备，或者可以是第三网络设备。该设备1100包括：处理器1101、存储器1102和通信接口1103。处理器1101、通信接口1103以及存储器1102可以相互连接或者通过总线1104相互连接。
示例性的，存储器1102用于存储设备1100的计算机程序和数据，存储器1102可以包括但不限于是随机存储记忆体(random access memory，RAM)、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable read only memory，EPROM)或便携式只读存储器(compact disc read-only memory，CD-ROM)等。通信接口1103用于支持设备1100进行通信，例如接收或发送数据或信号等。
在实现实施例一及其可能的实施方式中，执行实施例一中的全部或部分单元的功能所需的软件或程序代码存储在存储器1102中。
在实现实施例二及其可能的实施方式中，执行实施例二中的全部或部分单元的功能所需的软件或程序代码存储在存储器1102中。
在实现上述任一个实施例的情况下，如果是部分单元的功能所需的软件或程序代码存储在存储器1102中，则处理器1101除了调用存储器1102中的程序代码实现部分功能外，还可以配合其他部件(如通信接口1103)共同完成该任一个实施例所描述的其他功能(如接收和发送数据的功能)。
示例性的，处理器1101可以是中央处理器单元、通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。处理器1101可以用于读取上述存储器1102中存储的程序，执行上述各个实施例所述的方法中第一网络设备、第二网络设备或者第三网络设备所做的操作。
图11所示设备1100所执行的具体操作以及有益效果可以参见上述各个方法实施例及其可能的实施方式中的描述，此处不再赘述。
本申请实施例还提供一种装置，该装置包括处理器、通信接口和存储器，该装置被配置为执行上述各个实施例及其可能的实施例中任意一个实施例所述的方法。
在其中一种可能的实施方式中，该装置为芯片或系统芯片(System on a Chip，SoC)。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，该计算机程序被处理器执行以实现上述各个实施例及其可能的实施例中任意一个实施例所述的方法。
本申请实施例还提供一种计算机程序产品，当该计算机程序产品被计算机读取并执行时，上述各个实施例及其可能的实施例中任意一个实施例所述的方法将被执行。
本申请实施例还提供一种计算机程序，当该计算机程序在计算机上执行时，将会使该计算机实现上述各个实施例及其可能的实施例中任意一个实施例所述的方法。
综上所述，本申请能够在用户侧设备多归接入多个PE，且用户侧设备分别与该多个PE之间的链路的ESI配置不同的情况下，解决用户侧设备与PE之间的链路出现故障后长时间丢包的问题。
本申请中术语“第一”“第二”等字样用于对作用和功能基本相同的相同项或相似项进行区分，应理解，“第一”、“第二”、“第n”之间不具有逻辑或时序上的依赖关系，也不对数量和执行顺序进行限定。还应理解，尽管以下描述使用术语第一、第二等来描述各种元素，但这些元素不应受术语的限制。这些术语只是用于将一元素与另一元素区别分开。例如，在不脱离各种所述示例的范围的情况下，第一图像可以被称为第二图像，并且类似地，第二图像可以被称为第一图像。第一图像和第二图像都可以是图像，并且在某些情况下，可以是单独且不同的图像。
还应理解，在本申请的各个实施例中，各个过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
还应理解，术语“包括”(也称“includes”、“including”、“comprises”和/或“comprising”)当在本说明书中使用时指定存在所陈述的特征、整数、步骤、操作、元素、和/或部件，但是并不排除存在或添加一个或多个其他特征、整数、步骤、操作、元素、部件、和/或其分组。
还应理解，说明书通篇中提到的“一个实施例”、“一实施例”、“一种可能的实现方式”意味着与实施例或实现方式有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”、“一种可能的实现方式”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
最后应说明的是：以上各实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述各实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (28)

  1. 一种转发流量的方法，其特征在于，所述方法包括：
    第一网络设备接收来自第二网络设备的第一流量，所述第一流量的目的地址为第一设备，所述第一网络设备和所述第二网络设备为网络中的服务提供商边缘PE设备，第一设备分别通过第一链路和第二链路多归接入所述第一网络设备和所述第二网络设备，所述第一链路和所述第二链路的以太网链路标识ESI不同；
    所述第一网络设备向所述第一设备发送所述第一流量。
  2. 根据权利要求1所述的方法，其特征在于，在所述第一网络设备向所述第一设备发送所述第一流量之前，所述方法还包括：
    所述第一网络设备确定本地流量特征表中所述第一流量的映射设备不是第三网络设备，所述第三网络设备为所述网络中的PE设备，所述第三网络设备分别连接所述第一网络设备和所述第二网络设备。
  3. 根据权利要求2所述的方法，其特征在于，所述第一网络设备确定本地流量特征表中所述第一流量的来源设备不是第三网络设备，包括：
    所述第一网络设备确定本地流量特征表中所述第一流量的映射设备为所述第二网络设备。
  4. 根据权利要求2所述的方法，其特征在于，所述第一网络设备确定本地流量特征表中所述第一流量的来源设备不是第三网络设备，包括：
    所述第一网络设备确定本地流量特征表未指示所述第一流量的映射设备；
    所述第一网络设备在所述本地流量特征表中设置所述第一流量的映射设备为所述第二网络设备。
  5. 根据权利要求2至4任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述第三网络设备的所述第一流量；
    在所述本地流量特征表中所述第一流量的映射设备不是所述第三网络设备的情况下，所述第一网络设备将所述本地流量特征表中所述第一流量的映射设备设置为所述第三网络设备；
    所述第一网络设备向所述第一设备发送来自所述第三网络设备的所述第一流量。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备再次接收来自所述第二网络设备的所述第一流量；
    在所述本地流量特征表中所述第一流量的映射设备为所述第三网络设备的情况下，所述第一网络设备丢弃所述再次接收的来自所述第一网络设备的所述第一流量。
  7. 根据权利要求2至6任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述第三网络设备的第二流量；
    在所述本地流量特征表中不包括所述第二流量的信息时，所述第一网络设备向所述网络中的第二设备发送所述第二流量。
  8. 根据权利要求1至7任一项所述的方法，其特征在于，所述第一流量携带标签，所述标签指示所述第一流量来自所述第二网络设备。
  9. 根据权利要求1至8任一项所述的方法，其特征在于，所述第一网络设备向所述第一设备发送所述第一流量，包括：
    在定时器启动且未达到预设时长的情况下，所述第一网络设备向所述第一设备发送所述 第一流量，其中，所述定时器为所述第一网络设备感知到所述第二网络设备与所述第一设备之间的通信链路故障后启动的。
  10. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述第三网络设备的通知，所述通知用于指示所述第一网络设备无需转发来自所述第二网络设备的所述第一流量；
    所述第一网络设备再次接收来自所述第二网络设备的所述第一流量，响应于所述通知，丢弃所述再次接收的来自所述第二网络设备的所述第一流量。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述第三网络设备的所述第一流量；
    所述第一网络设备向所述第一设备发送来自所述第三网络设备的所述第一流量。
  12. 根据权利要求1至11任一项所述的方法，其特征在于，所述第一流量中的所有报文具备相同的特征，所述特征包括二元组、四元组、五元组或者七元组。
  13. 根据权利要求1至12任一项所述的方法，其特征在于，所述第一流量的目的MAC地址为所述第一设备的MAC地址。
  14. 一种转发流量的方法，其特征在于，所述方法包括：
    第一网络设备向第二网络设备发送第一流量，所述第一流量的目的地址为第一设备；所述第一网络设备和所述第二网络设备为网络中的服务提供商边缘PE设备，所述第一设备分别通过第一链路和第二链路多归接入所述第一网络设备和所述第二网络设备，所述第一链路和所述第二链路的以太网链路标识ESI不同。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备通过接入链路AC接口广播所述第一流量。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第一网络设备向所述第二网络设备发送第一流量，包括：
    在所述第一网络设备与所述第一设备之间的通信链路出现故障的情况下，所述第一网络设备向所述第二网络设备发送所述第一流量。
  17. 根据权利要求16所述的方法，其特征在于，所述在所述第一网络设备与所述第一设备之间的通信链路出现故障的情况下，所述第一网络设备向所述第二网络设备发送第一流量，包括：
    在所述第一设备的MAC地址无法匹配到所述第一网络设备的本地媒体访问控制MAC地址转发表中的表项的情况下，所述第一网络设备向所述第二网络设备发送第一流量。
  18. 根据权利要求14至17任一项所述的方法，其特征在于，所述第一网络设备向所述第二网络设备发送第一流量，包括：
    在定时器启动且未达到预设时长的情况下，所述第一网络设备向所述第二网络设备发送所述第一流量，其中，所述定时器为所述第一网络设备感知到所述第一网络设备与所述第一设备之间的通信链路故障后启动的。
  19. 根据权利要求14至18任一项所述的方法，其特征在于，所述第一流量携带标签，所述标签指示所述第一流量来自所述第一网络设备。
  20. 根据权利要求14至19任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收第二流量；
    所述第一网络设备根据本地MAC地址转发表发送所述第二流量。
  21. 根据权利要求14至20任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备通过接入链路AC接口接收第三流量；
    在所述第三流量的目的MAC地址无法匹配到所述第一网络设备的本地MAC地址转发表中的表项的情况下，所述第一网络设备向所述网络中的网络设备广播所述第三流量。
  22. 根据权利要求14至21任一项所述的方法，其特征在于，所述第一网络设备向第二网络设备发送第一流量，包括：
    所述第一网络设备获取缺省路由，所述缺省路由用于在所述第一网络设备与所述第一设备之间的通信链路出现故障时，向所述第二网络设备发送来自所述第三网络设备的所述第一流量；
    所述第一网络设备根据所述缺省路由向所述第二网络设备发送所述第一流量。
  23. 一种转发流量的设备，其特征在于，包括用于执行如权利要求1至13任一项所述的方法的单元。
  24. 一种转发流量的设备，其特征在于，包括用于执行如权利要求14至22任一项所述的方法的单元。
  25. 一种转发流量的设备，其特征在于，包括处理器、通信接口和存储器，其中，所述存储器用于存储程序指令和/或数据，所述处理器用于执行所述存储器中存储的程序指令，使得所述设备执行如权利要求1至13任一项所述的方法。
  26. 一种转发流量的设备，其特征在于，包括处理器、通信接口和存储器，其中，所述存储器用于存储程序指令和/或数据，所述处理器用于执行所述存储器中存储的程序指令，使得所述设备执行如权利要求14至22任一项所述的方法。
  27. 一种转发流量的系统，其特征在于，包括第一网络设备和第二网络设备，其中，所述第一网络设备为权利要求23所述的设备，所述第二网络设备为权利要求24所述的设备；或者，所述第一网络设备为权利要求25所述的设备，所述第二网络设备为权利要求26所述的设备。
  28. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行以实现权利要求1至13任意一项所述的方法；或者，所述计算机程序被处理器执行以实现权利要求14至22任意一项所述的方法。
PCT/CN2021/120741 2020-09-29 2021-09-26 转发流量的方法及设备 WO2022068736A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011050592.X 2020-09-29
CN202011050592.XA CN114363114B (zh) 2020-09-29 2020-09-29 转发流量的方法及设备

Publications (1)

Publication Number Publication Date
WO2022068736A1 true WO2022068736A1 (zh) 2022-04-07

Family

ID=80951220

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/120741 WO2022068736A1 (zh) 2020-09-29 2021-09-26 转发流量的方法及设备

Country Status (2)

Country Link
CN (1) CN114363114B (zh)
WO (1) WO2022068736A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113132220B (zh) 2019-12-31 2022-12-06 华为技术有限公司 一种路由信息的处理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160127320A1 (en) * 2014-11-03 2016-05-05 Cisco Technology, Inc. Proxy Forwarding of Local Traffic by Edge Devices in a Multi-Homed Overlay Virtual Private Network
WO2018103099A1 (zh) * 2016-12-09 2018-06-14 华为技术有限公司 发送和接收消息的方法、设备和系统
CN109787797A (zh) * 2017-11-14 2019-05-21 华为技术有限公司 链路的故障检测方法、装置以及系统
CN110351772A (zh) * 2018-04-08 2019-10-18 慧与发展有限责任合伙企业 无线链路和虚拟局域网之间的映射

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100333250B1 (ko) * 1998-10-05 2002-05-17 가나이 쓰토무 패킷 중계 장치
JP4231766B2 (ja) * 2003-10-24 2009-03-04 株式会社日立コミュニケーションテクノロジー Ａｓ間の経路制御を行う通信装置および通信方法。
CN101035063A (zh) * 2006-03-07 2007-09-12 华为技术有限公司 组播流转发方法及其路由器和系统
CN101656679B (zh) * 2009-09-25 2012-04-04 华为技术有限公司 一种组播快速收敛方法、路由器和通信系统
US9787573B2 (en) * 2014-12-31 2017-10-10 Juniper Networks, Inc. Fast convergence on link failure in multi-homed Ethernet virtual private networks
CN109672619B (zh) * 2017-10-17 2021-08-20 华为技术有限公司 一种处理报文的方法、设备及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160127320A1 (en) * 2014-11-03 2016-05-05 Cisco Technology, Inc. Proxy Forwarding of Local Traffic by Edge Devices in a Multi-Homed Overlay Virtual Private Network
WO2018103099A1 (zh) * 2016-12-09 2018-06-14 华为技术有限公司 发送和接收消息的方法、设备和系统
CN109787797A (zh) * 2017-11-14 2019-05-21 华为技术有限公司 链路的故障检测方法、装置以及系统
CN110351772A (zh) * 2018-04-08 2019-10-18 慧与发展有限责任合伙企业 无线链路和虚拟局域网之间的映射

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
J. HE, ED. X. LI Z. ZHOU H. QU ERICSSON: "EVPN Egress Fast ReRoute; draft-jiang-bess-evpn-egress-frr-00.txt", EVPN EGRESS FAST REROUTE; DRAFT-JIANG-BESS-EVPN-EGRESS-FRR-00.TXT; INTERNET-DRAFT: BESS WORKING GROUP, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEVA, SWITZERLAND, no. 00, 29 June 2020 (2020-06-29), Internet Society (ISOC) 4, rue des Falaises CH- 1205 Geneva, Switzerland , pages 1 - 7, XP015140285 *

Also Published As

Publication number Publication date
CN114363114A (zh) 2022-04-15
CN114363114B (zh) 2023-07-07

Similar Documents

Publication Publication Date Title
US11533249B2 (en) Route processing method and apparatus, and data transmission method and apparatus
US11012355B2 (en) Route processing method, device, and system
US9100281B2 (en) Systems and methods for equal-cost multi-path virtual private LAN service
US8134919B2 (en) Method and device for protecting ethernet tree services
US8750314B2 (en) Method and device for link protection in virtual private local area network
US20080247324A1 (en) Detection of specific bfd path failures
US9007958B2 (en) External loop detection for an ethernet fabric switch
WO2016101646A1 (zh) 以太虚拟网络的接入方法及装置
US20070036161A1 (en) System and method of routing Ethernet MAC frames using Layer-2 MAC addresses
CN111064596B (zh) 对于用于多宿主节点故障的bum流量的节点保护
WO2020168854A1 (zh) 一种evpn组播方法、装置及系统
KR20040102177A (ko) 중복 접속들을 위한 다이내믹하게 변경된 메트릭들을이용한 트래픽 네트워크 흐름 제어
US11824779B2 (en) Traffic forwarding processing method and device
US20210119911A1 (en) Message sending and receiving method, apparatus, and system
US20240214243A1 (en) Designated forwarder df election method and device
WO2022068736A1 (zh) 转发流量的方法及设备
US20230164070A1 (en) Packet sending method, device, and system
EP4346181A1 (en) Loop detection method and apparatus
US20220294728A1 (en) Packet Transmission Path Switching Method, Device, and System
CN109981452B (zh) 一种pw链路的回切方法及装置
US20240235986A1 (en) Loop detection method and apparatus

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21874396

Country of ref document: EP

Kind code of ref document: A1