WO2019201209A1 - Réacheminement de message - Google Patents

Réacheminement de message Download PDF

Info

Publication number
WO2019201209A1
WO2019201209A1 PCT/CN2019/082716 CN2019082716W WO2019201209A1 WO 2019201209 A1 WO2019201209 A1 WO 2019201209A1 CN 2019082716 W CN2019082716 W CN 2019082716W WO 2019201209 A1 WO2019201209 A1 WO 2019201209A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
leaf device
host
destination
route
Prior art date
Application number
PCT/CN2019/082716
Other languages
English (en)
Chinese (zh)
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 WO2019201209A1 publication Critical patent/WO2019201209A1/fr

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/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/18—Loop-free operations

Definitions

  • MLAG Multi-Chassis Link Aggregation Group
  • This mechanism improves the link reliability from the board level to the device level by combining two devices to implement cross-device link aggregation to form a MLAG active-active system.
  • a MLAG deployment scheme based on the Spine-Leaf (backbone-leaf) network is provided.
  • Host A is dual-homed to Leaf device 1 and Leaf device 2; host B is connected to Leaf device 3; Leaf device 1 and leaf device are provided. 2 and the leaf device 3 can communicate with the Spine device through the VXLAN tunnel.
  • the destination VTEP VXLAN Tunnel End Point
  • IP Internet Protocol
  • the Spine device receives the packet from the host B and distributes the packet to the Leaf device 1 or the Leaf device 2 based on the load sharing mechanism. If the link between the leaf device 1 and the host A is faulty, the leaf device 1 forwards the packet to the leaf device 2, and the leaf device 2 forwards the packet to the host A.
  • FIG. 1 is a schematic diagram of a MLAG deployment scheme in a Spine-Leaf networking according to an embodiment of the present disclosure.
  • 2A is a schematic diagram of a packet forwarding path before a link failure.
  • 2B is a schematic diagram of a message forwarding path after a link failure.
  • FIG. 3 is a flowchart of a packet forwarding method according to an embodiment of the present disclosure.
  • FIG. 4 is a flow chart showing interaction between devices when a link is faulty according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of a packet forwarding path after a link failure according to an embodiment of the present disclosure.
  • FIG. 6 is a flow chart of interaction between devices when the link shown in the embodiment of the present disclosure returns to normal.
  • FIG. 7 is a schematic diagram of a hardware structure of a Leaf device according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a Leaf device according to an embodiment of the present disclosure.
  • first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the embodiments of the present disclosure.
  • second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "when” or "when” or "in response to a determination.”
  • FIG. 1 is a schematic diagram of a MLAG deployment scheme in a Spine-Leaf networking according to an embodiment of the present disclosure.
  • the network includes one Spine device 100, three Leaf devices (Leaf device 101, Leaf device 102, Leaf device 103) and two hosts (Host 111 and Host 112).
  • the host 111 is dual-homed to the Leaf device 101 and the Leaf device 102 based on the MLAG mechanism.
  • the Leaf device 101 and the Leaf device 102 are called MLAG members, and have the same virtual IP address (MLAG group address), which is recorded as IP12; and the Leaf device 103 It does not belong to the MLAG to which the Leaf device 101 and the Leaf device 102 belong.
  • Each Leaf device is connected through a VXLAN tunnel.
  • the leaf device 103 When the forwarding device 112 accesses the packet of the host 111, the leaf device 103 performs VXLAN encapsulation on the packet, and the destination VTEP IP address of the encapsulated packet is the virtual IP address IP12.
  • the Spine device 100 receives the packet and distributes the packet to the Leaf device 101 or the Leaf device 102 based on the load sharing mechanism. If the message is distributed to the Leaf device 101, the message is forwarded by the Leaf device 101 to the host 111.
  • 2A is a schematic diagram of a path for forwarding a message by the Leaf device 101, where a dotted line indicates a forwarding path.
  • FIG. 2B it is a schematic diagram of a new packet forwarding path after a link failure. As shown in FIG. 2B, there is a round-trip of the packet forwarding path at the leaf device 101, which results in a low forwarding efficiency of the packet.
  • FIG. 3 is a flowchart of a packet forwarding method according to an embodiment of the present disclosure. The method describes a packet forwarding process from a first Leaf device side in the MLAG.
  • Step 301 The first Leaf device receives the first route revocation message sent by the second Leaf device.
  • the second Leaf device and the first Leaf device belong to the same MLAG and have the same virtual IP address.
  • Step 302 If the destination IP address included in the first route revocation message is the IP address of the local host, and the next hop information is the virtual IP address, the first leaf device sends a first route advertisement message.
  • the next hop information is a virtual IP address shared by the first leaf device and the second leaf device (referred to as a virtual IP address in the following description).
  • the link between the second Leaf device and the local host is faulty and cannot communicate properly.
  • the local host refers to a host that is dual-homed to the first Leaf device and the second Leaf device based on the MLAG mechanism.
  • the first leaf device sends a first route advertisement message, where the destination IP address included in the first route advertisement message is the IP address of the local host, and the next hop information is the real IP address of the first Leaf device (the IP address of the physical device) .
  • the Leaf device 101 and the Leaf device 102 in FIG. 1 have the same virtual IP address IP12 and have their own real IP addresses, which are respectively recorded as IP11 and IP22.
  • Both the route revocation message and the route advertisement message described in the examples of the present disclosure may be in the format of, for example, a BGP message.
  • Any device in the Spine-Leaf network can carry the updated route in a BGP message and send it to another device that has established a BGP neighbor relationship with the device.
  • the Spine-Leaf network further includes a third Leaf device (for example, the Leaf device 103 in FIG. 1) that does not belong to the first Leaf device and the MLAG to which the second Leaf device belongs.
  • the third leaf device When receiving the first route revocation message sent by the second leaf device, the third leaf device deletes the destination IP address and the next hop information included in the first route revocation message, and deletes the destination IP address of the local record as the IP address of the local host.
  • the next hop information is the routing entry of the virtual IP address.
  • the third leaf device When receiving the first route advertisement message sent by the first leaf device, the third leaf device generates the destination IP address as the IP address of the local host according to the destination IP address and the next hop information included in the first route advertisement message, and the next The hop information is the routing entry of the real IP address of the first Leaf device (recorded as the first routing entry). Therefore, the third Leaf device forwards the packet addressed to the local host based on the first routing entry. Specifically, before the third leaf device forwards the packet, the packet is VXLAN encapsulated, and the destination VTEP IP address of the encapsulated packet is the real IP address of the first Leaf device. The message is then forwarded to the first Leaf device.
  • the packet forwarding path is bypassed at the second Leaf device when the link between the second leaf device and the local host is faulty.
  • the packet is forwarded from the second Leaf device to the first Leaf device and then forwarded to the local device. Host. It can be seen that the packet forwarding method provided by the embodiment of the present disclosure can improve the packet forwarding efficiency.
  • the first leaf device when the first leaf device receives the second route advertisement message sent by the second leaf device, if the destination IP address included in the second route advertisement message is the IP address of the local host, the next hop information is The virtual IP address indicates that the link between the second Leaf device and the local host is normal and can communicate. At this time, the first leaf device sends a second route revocation message, where the destination IP address included in the second route revocation message is the IP address of the local host, and the next hop information is the real IP address of the first Leaf device.
  • the third leaf device when the third leaf device receives the second route revocation message sent by the first leaf device, deleting the first routing table of the local record according to the destination IP address and the next hop information included in the second route revocation message.
  • the entry is the IP address of the local host and the next hop information is the routing entry of the real IP address of the first leaf device.
  • the destination IP address is the IP address of the local host, and the destination IP address is generated according to the destination IP address and the next hop information included in the second route advertisement message.
  • the one-hop information is the routing entry of the virtual IP address (recorded as the second routing entry). The third Leaf device forwards the packet addressed to the local host based on the second routing entry.
  • the third leaf device performs VXLAN encapsulation on the packet before forwarding the packet, where the destination VTEP IP address of the encapsulated packet is a virtual IP address. Then, the Spine device redistributes the packet to the second Leaf device based on the load balancing mechanism, and the second Leaf device forwards the packet to the local host. That is, after the link between the second leaf device and the local host returns to normal, the packet forwarding path is restored.
  • the packet is sent to the local host based on the MLAG dual-homing access to the first Leaf device and the second Leaf device.
  • the first leaf device obtains the destination IP address carried in the packet, and the destination IP address is the IP address of the local host.
  • the media access control (address) table determines the port connected to the local host (also referred to as a distributed aggregation port); and determines the communication state of the first leaf device and the local host based on the state of the distributed aggregation port.
  • the communication state between the first leaf device and the local host is normal; if the state of the distributed aggregation interface is DOWN (the chain between the first leaf device and the local host) If the path is faulty, it is determined that the communication state of the first Leaf device and the local host is abnormal.
  • the first leaf device sends a third route revocation message, where the destination IP address included in the third route revocation message is the IP address of the local host, and the next hop information is Virtual IP address.
  • the third route device receives the third route revocation message, the second routing entry of the local record is deleted according to the destination IP address and the next hop information included in the third route revocation message, that is, the destination IP address is the local host.
  • the IP address and the next hop information are the routing entries of the virtual IP address.
  • the communication state of the first leaf device and the local host may be abnormal.
  • the second leaf device sends a third route advertisement message, where the destination IP address included in the third route advertisement message is the IP address of the local host, and the next hop information is the real IP address of the second leaf device.
  • the third leaf device When receiving the third route advertisement message, the third leaf device generates the destination IP address as the local host's IP address and the next hop information as the second, according to the destination IP address and the next hop information included in the third route advertisement message.
  • the routing entry of the real IP address of the leaf device (recorded as the third routing table entry). Therefore, the third Leaf device forwards the packet addressed to the local host based on the third routing entry.
  • the third leaf device performs VXLAN encapsulation on the packet before forwarding the packet, where the destination VTEP IP address of the encapsulated packet is the real IP address of the second Leaf device.
  • the message is then forwarded to the second Leaf device. Therefore, the packet forwarding path is bypassed at the first leaf device when the communication between the first leaf device and the local host is abnormal. For example, the packet is forwarded from the first leaf device to the second leaf device and then forwarded to the local host. It can be seen that the packet forwarding method provided by the embodiment of the present disclosure can improve packet forwarding efficiency.
  • the first leaf device sends a fourth route advertisement message, where the destination IP address included in the fourth route advertisement message is the IP address of the local host, and the next hop information is virtual. IP address.
  • the second leaf device may be configured to detect that the communication state of the first leaf device and the local host is normal, and send a fourth route revocation message, where the destination IP address included in the fourth route revocation message is IP address of the local host.
  • the next hop information is the real IP address of the second Leaf device.
  • the third leaf device When receiving the fourth route revocation message, the third leaf device deletes the third routing entry of the local record according to the destination IP address and the next hop information included in the fourth route revocation message, that is, the destination IP address is the local host.
  • the IP address and the next hop information are the routing entries of the real IP address of the second Leaf device.
  • the third leaf device receives the fourth route advertisement message, the second routing entry is generated according to the destination IP address and the next hop information included in the fourth route advertisement message, that is, the destination IP address is the IP address of the local host.
  • the next hop information is the routing entry of the virtual IP address.
  • the third Leaf device forwards the packet addressed to the local host based on the second routing entry.
  • the third leaf device performs VXLAN encapsulation on the packet before forwarding the packet, where the destination VTEP IP address of the encapsulated packet is a virtual IP address.
  • the Spine device redistributes the packet to the first leaf device based on the load balancing mechanism, and the first leaf device forwards the packet to the local host. In other words, after the communication between the first Leaf device and the local host returns to normal, the forwarding path of the packet is restored accordingly.
  • the packet forwarding method provided by the embodiment of the present disclosure only performs routing update for the host that is currently interacting with data, and the routes of other hosts that do not exchange data under the faulty distributed aggregation interface are not updated, thereby greatly reducing the number of routing updates.
  • the route of the host that is interacting with the data is also updated. Therefore, the route flapping caused by the large-scale routing update can be avoided.
  • the Spine-Leaf networking shown in Figure 1 is used as an example to describe the packet forwarding process in detail.
  • the host 112 accesses the host 111.
  • FIG. 4 it is a flow chart of interaction between devices when the link is faulty.
  • the leaf device 103 forwards the packet sent by the host 112 to the host 111 based on the routing entry R1 (the destination IP address is the IP address of the host 111 and the next hop information is the virtual IP address), and performs VXLAN encapsulation and encapsulation of the packet.
  • the destination VTEP IP address of the packet is IP12 (virtual IP address).
  • step 402 the leaf device 103 sends the encapsulated packet to the Spine device 100 through the outbound interface connected to the Spine device 100.
  • Step 403 After receiving the packet whose destination VTEP IP is IP12, the Spine device 100 distributes the packet to the leaf device 101 based on the load balancing mechanism.
  • Step 404 After receiving the packet whose destination VTEP IP is IP12, the leaf device 101 obtains the IP address of the host 111 carried by the packet, and determines the distributed aggregation interface connected to the host 111. If the distributed aggregation interface is normal (in the UP state) The status of the packet is sent to the host 111 through the distributed aggregation interface. The forwarding path is as shown by the dotted line in FIG. 2A. If the distributed aggregation interface is faulty (down state), go to step 405.
  • step 405 the leaf device 101 sends a route revocation message to the Spine device 100 (the route reflector).
  • the destination IP address included in the route revocation message is the IP address of the host 111, and the next hop information is a virtual IP address.
  • the Spine device 100 reflects the route revocation message to the Leaf device 102 and the Leaf device 103, respectively.
  • Step 407 After receiving the route revocation message, the leaf device 103 deletes the locally recorded routing entry R1 according to the destination IP address and the next hop information included in the route revocation message.
  • Step 408 After receiving the route revocation message, the leaf device 102 sends a route advertisement message to the Spine device 100.
  • the destination IP address included in the route advertisement message is the IP address of the host, and the next hop information is the real IP address of the Leaf device 102. (IP22).
  • step 409 the Spine device 100 reflects the route advertisement message to the Leaf device 103.
  • Step 410 After receiving the route advertisement message, the leaf device 103 generates a routing entry R2 according to the destination IP address and the next hop information included in the route advertisement message.
  • the destination IP address is the IP address of the host 111, and the next hop information. Is the real IP address of the Leaf device 102).
  • the leaf device 103 forwards the packet sent by the host 112 to the host 111 based on the routing entry R2, and performs VXLAN encapsulation on the packet.
  • the destination VTEP IP address of the encapsulated packet is IP22 (the real IP address of the Leaf device 102).
  • step 412 the leaf device 103 sends the encapsulated packet to the Spine device 100 through the outbound interface connected to the Spine device 100.
  • Step 413 After receiving the packet whose destination VTEP IP is IP22, the Spine device 100 forwards the packet directly to the Leaf device 102.
  • step 414 the leaf device 102 sends the packet to the host 111 through the distributed aggregation interface connected to the host 111 on the device.
  • the forwarding path is as shown by the dotted line in FIG.
  • FIG. 6 a flow chart of interaction between devices when the link is restored to normal.
  • Step 601 If the distributed aggregation interface of the leaf device 101 and the host 111 is restored to the UP state, the leaf device 101 sends a route advertisement message to the Spine device 100, where the destination IP address included in the route advertisement message is the IP address of the host 111.
  • the next hop information is a virtual IP address (IP12).
  • the Spine device 100 reflects the route advertisement message to the Leaf device 102 and the Leaf device 103.
  • Step 603 After receiving the route advertisement message, the leaf device 103 generates a routing entry R1 according to the destination IP address and the next hop information included in the route advertisement message.
  • the destination IP address is the IP address of the host 111, and the next hop information. Is a virtual IP address).
  • Step 604 After receiving the route advertisement message, the leaf device 102 sends a route revocation message to the Spine device 100.
  • the destination IP address included in the route revocation message is the IP address of the host 111, and the next hop information is the real IP address of the Leaf device 102. Address (IP22).
  • step 605 the Spine device 100 reflects the route revocation message to the Leaf device 103.
  • Step 606 after receiving the route revocation message, the leaf device 103 deletes the locally recorded routing entry R2 according to the destination IP address and the next hop information included in the route revocation message (the destination IP address is the IP address of the host 111, One hop information is the real IP address of the Leaf device 102).
  • the leaf device 103 forwards the packet sent by the host 112 to the host 111 based on the routing entry R1, and performs VXLAN encapsulation on the packet.
  • the destination VTEP IP address of the encapsulated packet is IP12 (virtual IP address).
  • step 608 the leaf device 103 sends the encapsulated packet to the Spine device 100 through the outbound interface connected to the Spine device 100.
  • Step 609 After receiving the packet with the destination VTEP IP being IP12, the Spine device 100 re-distributes the packet sent by the host 112 to the host 111 to the Leaf device 101 based on the load sharing mechanism.
  • step 610 the leaf device 101 sends the packet to the host 111 through the distributed aggregation port connected to the host 111 on the device, and the forwarding path is restored to the dotted line in FIG. 2A.
  • FIG. 7 is a schematic structural diagram of hardware of a Leaf device according to an embodiment of the present disclosure.
  • the Leaf device can include a processor 701, a machine readable storage medium 702 that stores machine executable instructions.
  • Processor 701 and machine readable storage medium 702 can communicate via system bus 703. And, by reading and executing machine executable instructions in the machine readable storage medium 702 corresponding to the message forwarding logic, the processor 701 can perform the message forwarding method described above.
  • the machine-readable storage medium 702 referred to herein can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like.
  • the machine-readable storage medium may be: RAM (Radom Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as a hard drive), solid state drive, any type of storage.
  • RAM Random Access Memory
  • volatile memory volatile memory
  • non-volatile memory such as a hard drive
  • solid state drive any type of storage.
  • a disk such as a compact disc, dvd, etc.
  • a similar storage medium or a combination thereof.
  • the receiving unit 801 is configured to receive a first route revocation message sent by the second Leaf device.
  • the sending unit 802 is configured to: if the destination IP address included in the first route revocation message is an IP address of the local host, and the next hop information is the virtual IP address, send a first route advertisement message, where the first The destination IP address included in the route advertisement message is the IP address of the local host, and the next hop information is the real IP address of the leaf device, so that the third leaf device that does not belong to the MLAG generates the first routing entry.
  • the destination IP address of the first routing entry is the IP address of the local host, and the next hop information is the real IP address of the Leaf device.
  • the receiving unit 801 is further configured to receive a second route advertisement message sent by the second leaf device, where the sending unit 802 is further configured to: if the destination IP address included in the second route advertisement message is included The address is the IP address of the local host, and the next hop information is the virtual IP address, the second route revocation message is sent, and the destination IP address included in the second route revocation message is the IP address of the local host.
  • the next hop information is the real IP address of the leaf device, so that the third leaf device deletes the first routing entry.
  • the device further includes: a determining unit, configured to determine a communication state of the Leaf device and the local host.
  • the sending unit 802 is further configured to: if the communication status of the Leaf device and the local host is abnormal, send a third route revocation message, and the destination IP address included in the third route revocation message
  • the address is the IP address of the local host, and the next hop information is the virtual IP address, so that the third leaf device deletes the second routing entry, and the destination IP address of the second routing entry is the local
  • the IP address of the host, the next hop information is the virtual IP address, and the second leaf device sends a third route advertisement message, where the destination IP address included in the third route advertisement message is the local host
  • the IP address, the next hop information is the real IP address of the second Leaf device.
  • the determining unit is configured to: obtain a destination IP address carried in the packet, where the destination IP address is the local IP address, if the packet with the destination VTEP IP address being the virtual IP address is received The IP address of the host is determined, and the distributed aggregation port connected to the local host is determined based on the destination IP address; and the communication state of the Leaf device and the local host is determined based on the state of the distributed aggregation interface.
  • the sending unit 802 is further configured to: if the communication status of the leaf device and the local host is normal, send a fourth route advertisement message, where the destination IP address included in the fourth route advertisement message is The IP address of the local host, the next hop information is the virtual IP address, so that the third Leaf device generates the second routing entry, and causes the second Leaf device to send a fourth route revocation message.
  • the destination IP address included in the fourth route revocation message is an IP address of the local host, and the next hop information is a real IP address of the second leaf device.
  • Embodiments of the present disclosure also provide a machine readable storage medium including machine executable instructions, such as machine readable storage medium 702 of FIG. 7, which may be processor 701 in a main control board of a network device Executed to implement the packet forwarding method described above.
  • machine executable instructions such as machine readable storage medium 702 of FIG. 7, which may be processor 701 in a main control board of a network device Executed to implement the packet forwarding method described above.

Landscapes

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

Abstract

Lorsqu'un premier dispositif de feuille et un second dispositif de sortie appartiennent au même MLAG, les dispositifs comportent la même adresse IP virtuelle. Le premier dispositif feuille reçoit un premier message de révocation de routage envoyé par le second dispositif feuille ; si une adresse IP de destination comprise dans le premier message de révocation de routage est l'adresse IP d'un hôte à double hébergement qui accède au premier dispositif feuille et au second dispositif feuille et que des informations de saut suivant sont une adresse IP virtuelle, envoie un premier message de distribution de routage, le premier message de distribution de routage comprenant l'adresse IP de destination en tant qu'adresse IP de l'hôte et les premières informations de saut en tant qu'adresse IP réelle du premier dispositif feuille de sorte qu'un troisième dispositif feuille qui n'appartient pas au MLAG génère un premier élément de table de routage, l'adresse IP de destination du premier élément de table de routage étant l'adresse IP de l'hôte et les informations de saut suivant étant l'adresse IP réelle du premier dispositif feuille.
PCT/CN2019/082716 2018-04-19 2019-04-15 Réacheminement de message WO2019201209A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810355459.1A CN108600099B (zh) 2018-04-19 2018-04-19 一种报文转发方法、装置及叶子设备
CN201810355459.1 2018-04-19

Publications (1)

Publication Number Publication Date
WO2019201209A1 true WO2019201209A1 (fr) 2019-10-24

Family

ID=63611233

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/082716 WO2019201209A1 (fr) 2018-04-19 2019-04-15 Réacheminement de message

Country Status (2)

Country Link
CN (1) CN108600099B (fr)
WO (1) WO2019201209A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113765823A (zh) * 2021-09-29 2021-12-07 新华三信息安全技术有限公司 一种报文转发方法及装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108600099B (zh) * 2018-04-19 2020-04-03 新华三技术有限公司 一种报文转发方法、装置及叶子设备
CN109495368B (zh) * 2018-12-19 2021-07-16 锐捷网络股份有限公司 Mac地址转发表的更新方法及网络设备
CN113381929B (zh) * 2020-03-10 2023-03-24 华为技术有限公司 一种路由处理方法、网关设备及计算机存储介质
CN111698154B (zh) * 2020-04-30 2023-04-07 新华三技术有限公司 一种主机路由频繁迁移的抑制方法及装置
CN115604174A (zh) * 2021-07-07 2023-01-13 中兴通讯股份有限公司（Cn） 跨设备链路聚合路由计算方法、交换机、系统及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140071810A1 (en) * 2012-09-11 2014-03-13 Hitachi Metals, Ltd. Communication system and processing method therefor
CN103986634A (zh) * 2013-02-13 2014-08-13 日立金属株式会社 通信系统及网络中继装置
CN104486124A (zh) * 2014-12-19 2015-04-01 盛科网络（苏州）有限公司 使用逻辑端口实现多系统链路聚合的装置及方法
CN107733793A (zh) * 2017-11-28 2018-02-23 新华三技术有限公司 一种转发表项维护方法及装置
CN108600099A (zh) * 2018-04-19 2018-09-28 新华三技术有限公司 一种报文转发方法、装置及Leaf设备

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102724126A (zh) * 2012-06-27 2012-10-10 福建星网锐捷网络有限公司 一种E-tree业务报文转发方法、装置和设备
CN103200089B (zh) * 2013-04-15 2016-10-19 杭州华三通信技术有限公司 虚拟专用局域网业务网络中的报文转发方法及设备
US10257043B2 (en) * 2016-01-11 2019-04-09 Lenovo Enterprise Solutions (Singapore) Pte. Ltd. Balancing utilization of infrastructure in a networked computing environment
CN106209643B (zh) * 2016-07-14 2019-08-06 新华三技术有限公司 报文转发方法及装置
CN106027352A (zh) * 2016-07-14 2016-10-12 瑞斯康达科技发展股份有限公司 一种业务报文转发方法和装置
CN106452992B (zh) * 2016-09-19 2020-02-11 新华三技术有限公司 一种远端多归属组网的实现方法及装置
CN107094110B (zh) * 2017-04-19 2020-01-03 新华三技术有限公司 一种dhcp报文转发方法及装置
CN106888166B (zh) * 2017-04-24 2020-04-24 新华三技术有限公司 一种报文转发方法和装置
CN107171964A (zh) * 2017-04-25 2017-09-15 中国联合网络通信集团有限公司 大规模组网中报文转发方法及装置
CN107547391B (zh) * 2017-06-08 2020-01-03 新华三技术有限公司 一种报文传输方法和装置
CN107547509B (zh) * 2017-06-27 2020-10-13 新华三技术有限公司 一种报文转发方法及装置
CN107547411B (zh) * 2017-06-30 2021-01-08 新华三技术有限公司 一种路由处理方法、装置、电子设备及机器可读存储介质
CN107547373B (zh) * 2017-07-17 2021-06-25 新华三技术有限公司 一种报文转发方法、装置、设备及机器可读存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140071810A1 (en) * 2012-09-11 2014-03-13 Hitachi Metals, Ltd. Communication system and processing method therefor
CN103986634A (zh) * 2013-02-13 2014-08-13 日立金属株式会社 通信系统及网络中继装置
CN104486124A (zh) * 2014-12-19 2015-04-01 盛科网络（苏州）有限公司 使用逻辑端口实现多系统链路聚合的装置及方法
CN107733793A (zh) * 2017-11-28 2018-02-23 新华三技术有限公司 一种转发表项维护方法及装置
CN108600099A (zh) * 2018-04-19 2018-09-28 新华三技术有限公司 一种报文转发方法、装置及Leaf设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113765823A (zh) * 2021-09-29 2021-12-07 新华三信息安全技术有限公司 一种报文转发方法及装置

Also Published As

Publication number Publication date
CN108600099A (zh) 2018-09-28
CN108600099B (zh) 2020-04-03

Similar Documents

Publication Publication Date Title
WO2019201209A1 (fr) Réacheminement de message
US10333836B2 (en) Convergence for EVPN multi-homed networks
US9019814B1 (en) Fast failover in multi-homed ethernet virtual private networks
US10135717B2 (en) Transferring data in a gateway
WO2018233588A1 (fr) Génération d'entrée de transfert
WO2019047855A1 (fr) Procédé et appareil de sauvegarde pour un bras ayant un plan de transfert et un plan de commande séparés
US20150016462A1 (en) Traffic forwarding in a layer 2 edge network
US11165693B2 (en) Packet forwarding
WO2018210094A1 (fr) Procédé de transmission de paquet, dispositif de périphérie et support de stockage lisible par machine
US9716687B2 (en) Distributed gateways for overlay networks
WO2018099394A1 (fr) Transmission de paquet
US20160248669A1 (en) Systems and methods of inter data center out-bound traffic management
WO2018090907A1 (fr) Transfert de message
US11497067B2 (en) Establishing a private network using multi-uplink capable network devices
WO2016086713A1 (fr) Procédé et appareil de mise à jour d'interface de sortie à trajets multiples à égalité de coût
WO2013078884A1 (fr) Procédé, dispositif et système pour le réacheminement d'un message
US11296979B2 (en) Method and system for symmetric integrated routing and bridging
JP2019521619A (ja) パケット転送
US20130343386A1 (en) First hop load balancing
JP6887523B2 (ja) Ｍａｃアドレス同期
WO2021082803A1 (fr) Procédé et appareil de transmission d'informations de routage et réseau d'interconnexion de centre de données
WO2019128612A1 (fr) Procédé et dispositif permettant de traiter un paquet de protocole de routage
JP2023544870A (ja) Ｍｌａｇリンク障害時切換え方法および装置
US10027589B1 (en) Apparatus, system, and method for achieving redundancy and load-balancing across communication layers within networks
CN108600075B (zh) 一种故障处理方法及装置

Legal Events

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

Ref document number: 19789253

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19789253

Country of ref document: EP

Kind code of ref document: A1