[go: up one dir, main page]

CN106059946B - Message forwarding method and device - Google Patents

Message forwarding method and device Download PDF

Info

Publication number
CN106059946B
CN106059946B CN201610351755.5A CN201610351755A CN106059946B CN 106059946 B CN106059946 B CN 106059946B CN 201610351755 A CN201610351755 A CN 201610351755A CN 106059946 B CN106059946 B CN 106059946B
Authority
CN
China
Prior art keywords
address
target
message
forwarding
virtual
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
CN201610351755.5A
Other languages
Chinese (zh)
Other versions
CN106059946A (en
Inventor
郑敏
杨小朋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Technologies Co Ltd
Original Assignee
New H3C Technologies Co Ltd
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 New H3C Technologies Co Ltd filed Critical New H3C Technologies Co Ltd
Priority to CN201610351755.5A priority Critical patent/CN106059946B/en
Publication of CN106059946A publication Critical patent/CN106059946A/en
Application granted granted Critical
Publication of CN106059946B publication Critical patent/CN106059946B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/12Avoiding congestion; Recovering from congestion
    • H04L47/125Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/74Address processing for routing

Landscapes

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

Abstract

the application provides a message forwarding method and a message forwarding device, wherein the method comprises the following steps: when a target message is received, a destination address included in the target message is obtained, wherein the destination address is used for representing an access equipment address connected with target equipment; if the destination address is a virtual address of a pre-configured virtual access device, decapsulating the target packet to obtain an address of the target device included in the target packet; and sending the target message to the target equipment from the forwarding port according to the corresponding relation between the address of the target equipment and the forwarding port in the local forwarding table. The method and the device realize load sharing among devices in cross-device link aggregation under the condition of not occupying device port interconnection.

Description

Message forwarding method and device
Technical Field
The present application relates to network technologies, and in particular, to a method and an apparatus for forwarding a packet.
Background
with the rapid development of network technology, higher network bandwidth is required for the operation of network services, and if a service board supporting high bandwidth is purchased and replaced, the service cost is greatly increased; the link aggregation technique can achieve the above-mentioned purpose of increasing the bandwidth at a lower cost. The total bandwidth after link aggregation is the sum of the bandwidths of all the member links, so that the network bandwidth requirement can be met, and link backups can be formed among all the member links. In the cross-device link aggregation, in order to perform load sharing of service traffic between links of each member device, the member devices need to be interconnected through the links, so that the service traffic can be shared among the member devices through the interconnected links. However, in this way, device interconnection will occupy device port resources, and further, the requirement for port resources in other business aspects cannot be met, for example, the number of servers or hosts accessing the network through the device will be reduced.
disclosure of Invention
In view of this, the present application provides a method and an apparatus for forwarding a packet, so as to implement load sharing between devices in cross-device link aggregation without occupying device port interconnection.
specifically, the method is realized through the following technical scheme:
In a first aspect, a method for forwarding a target packet sent to a target device is provided, where the target device is connected to multiple access devices, and the multiple access devices are configured as a link aggregation group, and configured with a virtual access device as a connection broker for the target device and each access device in the link aggregation group; the method is performed by the access device and comprises:
When the target message is received, a destination address included in the target message is obtained, wherein the destination address is used for representing an access equipment address connected with target equipment;
if the destination address is a virtual address of the virtual access device which is pre-configured, decapsulating the target packet to obtain an address of the target device included in the target packet;
and sending the target message to the target equipment from the forwarding port according to the corresponding relation between the address of the target equipment and the forwarding port in the local forwarding table.
in a second aspect, a message forwarding apparatus is provided, where the apparatus is applied to an access device, so that the access device forwards a target message sent to a target device; the target device is respectively connected with a plurality of access devices, and the access devices are configured to be a link aggregation group; virtual access equipment is also configured to serve as a connection medium between the target equipment and each access equipment in the link aggregation group; the device comprises:
The target determining module is used for acquiring a destination address included in the target message when the target message is received, wherein the destination address is used for representing an access equipment address connected with target equipment;
An address obtaining module, configured to decapsulate the target packet to obtain an address of the target device included in the target packet when the destination address is a virtual address of the virtual access device that is preconfigured;
And the message forwarding module is used for sending the target message to the target equipment from the forwarding port according to the corresponding relation between the address of the target equipment and the forwarding port in the local forwarding table.
According to the message forwarding method and device, the virtual access equipment is configured to serve as the connection intermediary between the target equipment and each access equipment, so that the destination VTEP for sending the message can be set as the virtual access equipment during message forwarding, flow can be shared by links corresponding to each access equipment, and load sharing among equipment in cross-equipment link aggregation is achieved under the condition that interconnection of equipment ports is not occupied.
drawings
FIG. 1 is a schematic diagram of a forwarding network shown in an exemplary embodiment of the present application;
Fig. 2 is a schematic diagram illustrating a connection relationship between a virtual access device and an access device according to an exemplary embodiment of the present application;
Fig. 3 is a flow chart of an access device issuing a route according to an exemplary embodiment of the present application;
fig. 4 is a flow chart of a message forwarding process according to an exemplary embodiment of the present application;
Fig. 5 is a flow of route reissuing in the event of a link failure according to an exemplary embodiment of the present application;
Fig. 6 is a structural diagram of a message forwarding apparatus according to an exemplary embodiment of the present application;
Fig. 7 is a block diagram of another message forwarding apparatus according to an exemplary embodiment of the present application;
Fig. 8 is a structural diagram of a message forwarding device according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
fig. 1 illustrates a forwarding network 100, where the forwarding network 100 may be used to forward messages between network devices. For example, the network devices a to e shown in fig. 1 may be hosts, servers, and other devices, and when the network device e sends a message to the network device b, the message may be forwarded through the forwarding network 100. In this application, the forwarding network 100 may be a VXLAN network.
An access device and a forwarding device may be included in a forwarding network. The access device may be configured to connect to network devices such as a host and a server, for example, leaf1 to leaf4 in fig. 1 are all access devices, and network devices a to e are connected under these leaves; in addition, each leaf device in the disclosure does not need to occupy a device port for link interconnection, and the devices can transmit control information through an underlay IP. The forwarding device may include spine5 and spine6 in fig. 1, and the forwarding device is interconnected with each access device through links, and cooperates with the access device to complete message forwarding. The above leaf1 to leaf4, or spine5 and spine6 are located at the edge of the VXLAN network, and correspond to a VTEP (VXLAN Tunneling End Point) in the VXLAN network. In addition, fig. 1 illustrates some of the access devices, forwarding devices, and network devices, which may be more numerous in an actual networking environment.
Continuing with fig. 1, taking the network device as an example, the host b is connected to the Leaf1 and the Leaf2, respectively, and two links connecting the host b to the Leaf1 and the Leaf2 may be configured as a link aggregation group across the devices, so as to implement load sharing of traffic corresponding to the host b through the link aggregation group. For example, when there is network traffic (e.g., host e sends a message to host b) to be sent to host b, the network traffic may be transmitted to host b through the link between host b and Leaf1, or may be transmitted to host b through the link between host b and Leaf2, so as to implement load sharing of the traffic.
The message forwarding method in the embodiment of the present disclosure will describe how to implement traffic sharing of a cross-device link aggregation group when forwarding a message when each device in the link aggregation group does not perform port interconnection. In the following description, a forwarding process of sending a message to host b by host e is described by taking a link aggregation group formed by links connected between host b and Leaf1 and Leaf2 as an example.
as shown in fig. 1, a virtual access device Leaf7 may be configured for the link aggregation group corresponding to the host b, and the connection relationship between the Leaf7 and the hosts b, Leaf1, and Leaf2 may be as shown in fig. 2. Leaf7 is an intermediary for connections between host b and Leaf1, Leaf2, e.g., an actual physical connection, host b is directly connected to Leaf1 and Leaf2, but may be virtualized as: host b is connected with Leaf7, and Leaf7 is respectively connected with Leaf1 and Leaf2, i.e. the message can be transmitted from Leaf1 to Leaf7, and then forwarded to host b by Leaf 7. This is, of course, a virtual transport process corresponding to the virtual architecture of fig. 2, in effect the message is sent directly from Leaf1 to host b.
through the configuration of the virtual access device Leaf7 shown in fig. 2, when publishing routing information to a forwarding network, such as a VXLAN network, the Lea1 and the Leaf2 will publish a route instead of the Leaf7, so that other devices in the network consider the Leaf7 as being a real VTEP and the Leaf7 as being a real VTEP; moreover, when the Lea1 and the Leaf2 issue the routes, the virtual connection relationship illustrated in fig. 2 is also issued, so that other network devices consider that the Leaf7 is a connection intermediary between the host b and the Leaf1 or the Leaf2, and encapsulate the packet and determine the packet forwarding path according to the connection relationship.
Before performing the message forwarding of the present application, an access device, such as a Leaf1 or a Leaf2, may issue routing information into the VXLAN network for subsequent message forwarding procedures according to the routing information. Fig. 3 illustrates a process of issuing a route by an access device, but the execution order of the steps is not limited in fig. 3:
In step 301, Lea1 and Leaf2 publish first routing information.
the first routing information in this step, wherein "first" is only used for distinguishing from the subsequently described routing, and has no other limiting meaning. In this example, the first routing information is used to indicate a relationship between the access device and the virtual access device, and may indicate a neighbor relationship between the Leaf1 and the Leaf7, for example. The issuing of the first routing information may enable automatic discovery and recording of neighbor relations between each Leaf or spine as a VTEP in the VXLAN network shown in fig. 1, so as to be used for subsequent message forwarding.
The first routing information may include: a destination address and a corresponding next hop address. The destination address is the address of the access device that issues the first routing information, and the next hop address is the address of the virtual access device Leaf7, in this example, the address of Leaf7 may be referred to as a virtual address.
For example, taking leaf1 as an example, the first routing information published by leaf1 may include: the destination address is the IP address of leaf7 and the next hop address is the IP address of leaf 1. In addition, the Leaf2 also issues the first route information, and the destination address in the route issued by the Leaf2 is still the address of the Leaf7, except that the corresponding next hop address is the address of the Leaf 2.
the route distribution in this step is not limited to the used route distribution Protocol, and for example, BGP (Border Gateway Protocol) may be used to distribute the route information; the routing information may include other information not listed.
In step 302, other devices in the forwarding network receive and store the first routing information.
for example, after receiving the first routing information issued by the leaf1 in step 301, the leaf4 in fig. 1 stores the first routing information; the address of Leaf1, the address of Leaf7, and the neighbor relationship of Leaf7 and Leaf1 may be recorded.
Through the above-mentioned route distribution, other devices in the forwarding network, such as Leaf4, spine5, etc., will all consider Leaf7 as a real existing device, similar to Leaf1 and Leaf2, as VTEPs in the network, and also obtain the neighbor relationship between Leaf7 and Leaf1 and Leaf2, knowing that if Leaf7 is reached, Leaf7 can be reached through Leaf1 or Leaf 2. Through the release route, the addresses of the Leaf in the VXLAN network and the neighbor relation between the leaves are synchronized in the network, and can be used for path search in the VXLAN network for subsequent message forwarding.
in step 303, Lea1 and Leaf2 receive address information for host b.
For example, after host b comes online, it may send a host address to Leaf1, which includes the IP address and MAC address of host b. Leaf2 may also receive the address.
In addition, assuming that the port of the Leaf1 receiving the address of the host b is P2, it means that the host b is connected to the port P2 of the Leaf1, and then if there is a message to be sent to the host b, the Leaf1 will send the message to the host b through the port P2, and the port P2 may be referred to as a forwarding port of the corresponding host b.
leaf1 may store the address of host b for subsequent message forwarding to host b. Leaf1 may store host b related information in local IP and MAC tables, as shown in tables 1 and 2 below, which illustrate the MAC and IP tables, respectively, of Leaf1, and the records of the MAC and IP tables of Leaf2 are similar to Leaf1 and will not be described in detail.
TABLE 1 MAC TABLE for Leaf1
MAC VXLAN Port/VTEP IP
MAC a P1
MAC b P2
MAC c P3
MAC d IP2
MAC e IP4
as shown in table 1, leaf1 records host b corresponding to MAC b, and the corresponding port is local port P2, that is, the message sent by local port P2 can reach host b; as can be seen from fig. 1, the VTEP where the host e is located is Leaf4, so the MAC address of the host e, i.e., the IP address of the VTEP corresponding to the MAC e, is the IP address "IP 4" of Leaf 4.
In table 1 and the following tables, MAC addresses corresponding to hosts a to e are denoted by MAC a to MAC e, IP addresses corresponding to hosts a to e are denoted by IP a to IP e, IP addresses corresponding to hosts a to host e are denoted by IP1 to IP7, and MAC addresses corresponding to VTEPs (including Leaf and spine) of the VXLAN network in fig. 1 are denoted by MAC1 to MAC7, respectively.
TABLE 2 IP TABLE of Leaf1
IP VRF Port/VTEP IP Next Hop
IP a P1 MAC a
IP b P2 MAC b
IP c P3 MAC c
IP d IP2 MAC 2
IP e IP4 MAC 4
In step 304, Lea1 and Leaf2 issue a second routing message to inform host b to connect under the virtual access device Leaf 7.
For example, in this step, Lea1 and Leaf2 may issue second routing information, where the second routing information is used to indicate a relationship between a target device and a virtual access device, for example, the target device is host b, and when host e sends a packet to host b, host b is the target device to which the packet is forwarded; through this step, the relationship between leaf7 and host b can be published, indicating that the VTEP connected to host b is leaf 7.
The second routing information includes: a destination address and a corresponding next hop address, wherein the destination address is the address of the target device, i.e. host b, and the next hop address is the virtual address of the virtual access device. For example, the address of host b may include the IP address and MAC address of host b, and the virtual address of the virtual access device may be the IP address and MAC address of Leaf 7.
The protocol used for route distribution is not limited in this example, and MP-BGP may be used, for example.
In step 305, other devices in the forwarding network receive and store the second routing information.
For example, after receiving the second routing information in step 304, leaf4 may record the information in a local IP table and MAC table, and may record that the VTEP connected to host b is leaf 7.
Table 3 MAC table of Leaf4
As shown in table 3, leaf4 may record that the VTEP IP corresponding to MAC b of host b is IP7 in the local MAC table, i.e., the VTEP where host b is located is leaf 7. In addition, the VTEP corresponding to the host c is also a Leaf7, and with reference to fig. 1, link aggregation may be configured for links connecting the host c to Leaf1 and Leaf2, respectively, and the Leaf7 is also configured to serve as a connection intermediary between the host c and the Leaf1 and Leaf 2.
The Leaf4 may also record the corresponding relationship between the IP address of the host b, the IP address of the Leaf7, and the MAC address in its local IP table, as shown in the following table 4:
Table 4Leaf 4 IP table
IP VRF Port/VTEP IP Next Hop
IP a IP1 MAC 1
IP b IP7 MAC 7
IP c IP7 MAC 7
IP d IP2 MAC 2
IP e P1 MAC 4
Through the distribution of the second routing information of the first routing information shown in fig. 3, each device in the VXLAN network already stores and records the information of each VTEP and the neighbor relation, and also records the address information of the host connected under the leaf and the corresponding relation between the host and the VTEP where the host is located, and these information will be used for message forwarding.
Fig. 4 describes a process of forwarding a message by taking the example that the host e sends a message to the host b, and by the message forwarding process, load sharing of the link aggregation group corresponding to the host b is realized. In this example, the forwarded packet may be referred to as a target packet, and the host b receiving the target packet may be referred to as a target device. As shown in fig. 4, the following processes may be included:
In step 401, when receiving the message from host e to host b, Leaf4 encapsulates the message as a VXLAN message.
for example, Leaf4 may obtain that the destination MAC address to which host e is addressed is MAC b when receiving a message addressed to host b by host e. The Leaf4 can look up the local MAC table, and the VTEP IP corresponding to MAC b is IP7, i.e. the VTEP where host b is located is Leaf 7; leaf4 may also look up the local IP table to get MAC 7. The Leaf4 may encapsulate the VXLAN message, i.e. the target message, according to the address information obtained by the table lookup, where the target message may include: the MAC address of host b, the IP address and MAC address of Leaf 7.
in step 402, Leaf4 sends the target message to the VXLAN network for forwarding.
In this step, the forwarding device in the VXLAN network may forward the target packet according to the routing information recorded in the flow shown in fig. 3. For the message sent to the host b, two paths may be available according to the routing information, where one path is to send the message to the Leaf1, forward the message to the Leaf7 by the Leaf1, and send the message to the host b by the Leaf7 (regarding to other devices except for Leaf1 and Leaf2, it is considered that the Leaf7 is a VTEP device connected to the host b that exists really); the other path is to send the message to Leaf2, forward the message to Leaf7 by Leaf2, and send the message to host b by Leaf 7. Then, the forwarding device may select one of the two paths to send the message, the algorithm of the path selection is not limited in this example, and the following steps are described by taking the path selected to send the message to the leaf1 as an example.
in step 403, when receiving the target packet, the leaf1 acquires a destination address in the target packet, where the destination address is used to indicate an address of an access device to which the target device is connected.
In this step, the destination address included in the target packet is the IP address of the VTEP connected to the host b, i.e. the IP address IP7 of Leaf7 in this example.
In step 404, when determining that the destination address is the virtual address of the preconfigured virtual access device, leaf1 decapsulates the target packet to obtain the address of the target device in the packet.
For example, after the leaf1 obtains the IP7 in step 403, knowing that this is the virtual address of the preconfigured virtual access device, i.e. the IP address of the leaf7, the message is terminated locally, and VXLAN decapsulation is performed on the message to obtain the address MAC b of the target device host b included in the message.
in step 405, leaf1 looks up the local forwarding table and forwards the packet to host b.
For example, Leaf1 searches the MAC table of the local forwarding table, obtains that the local forwarding port corresponding to MAC b is P2, and sends the destination packet to host b through port P2.
in addition, in the above flow, taking the example that the packet is forwarded to the host b through the Leaf1, during the actual packet forwarding process, the traffic sent to the host b may be shared on the links corresponding to the Leaf1 and the Leaf2, where a part of the packet is sent to the Leaf1 and reaches the host b, and another part of the packet is sent to the Leaf2 and reaches the host b.
In the message forwarding method of the present disclosure, by virtualizing a virtual access device serving as a connection intermediary between a target device and an access device, so that when the message is forwarded, the destination address of the message will be the virtual address of the virtual access device, and multiple paths corresponding to each access device in the link aggregation group exist for reaching the virtual access device, when the message is forwarded by the route, the flow sent to the target equipment can be shared on the plurality of paths, therefore, the load balance of a plurality of paths is realized through the routing, the load sharing mode is realized through the routing in the message forwarding process, therefore, the interconnection of devices in the link aggregation group is not needed, for example, the Leaf1 and the Leaf2 shown in fig. 1 do not need to occupy ports for link connection, therefore, the port resource of the access equipment is saved, and the equipment port can be more effectively and fully utilized.
In another example, in a link aggregation group across devices, there may be partial link failure, for example, in the link aggregation where host b connects Leaf1 and Leaf2, in case of link failure between host b and Leaf2, host b may notify the link failure of Leaf1 itself and Leaf2 to trigger Leaf1 to update address information of host b to the forwarding network, so as to ensure normal forwarding of traffic.
Fig. 5 illustrates a route reissue flow when a link in an aggregation group fails:
in step 501, the Leaf1 receives a failure notification sent by the target device, where the failure notification is used to notify a partial link failure in the link aggregation group.
For example, when a link between host b and Leaf2 fails, host b may send a failure notification to Leaf1, notifying Leaf1 that the link between host b and Leaf2 failed.
In step 502, the Leaf1 issues the updated second routing information, including the next hop address as the access device itself.
for example, Leaf1, after obtaining a link failure between host b and Leaf2, may change the VTEP that host b is connected to be Leaf1 itself, which will involve updating the second routing information, i.e., the information used to indicate under which VTEP the target device is connected.
The Leaf1 issues updated second routing information, which may include: a destination address and a corresponding next hop address, wherein the destination address is the address of the target device host b and the next hop address is the address of the Leaf 1. In this way, other devices in the network may be enabled to determine that the VTEP where host b is located is Leaf1 (before being updated, other devices consider the VTEP where host b is connected to be Leaf 7).
In step 503, the other devices of the forwarding network store the updated second routing information.
For example, after receiving the updated second routing information issued by the Leaf1, the Leaf4 may modify the local MAC table and IP table, and change the VTEP where the host b is located from the Leaf7 to the Leaf1, where the following two tables illustrate the modifications made by the Leaf4 to the local IP table and MAC table according to the updated second routing information. In addition, it should be noted that other devices such as spine5 and spine6 also modify their local IP tables and MAC tables.
TABLE 5 MAC TABLE for Leaf4
MAC VXLAN Port/VTEP IP
MAC b IP1
TABLE 6 IP TABLE of Leaf4
IP VRF Port/VTEP IP Next Hop
IP b IP1 MAC 1
After the above modification, if the host e under the Leaf4 sends a message to the host b again, the Leaf4 will use the Leaf1 as the VTEP connected to the host b when looking up the local MAC table, and encapsulate the information such as the IP address of the Leaf1 into the target message. And when forwarding the target message according to the routing information, the forwarding device in the VXLAN network has only Leaf1 path to reach the host b, because the host b is only connected under Leaf1 according to the updated route, the message will not be forwarded to Leaf2, and it is ensured that the message will not be sent to the failed link.
through the fault processing, when the link in the link aggregation group has a fault, the virtual machine access equipment can be released and the access equipment which is actually connected with the host can be informed by re-issuing the routing information, so that the flow can be ensured not to be sent to the fault link, and the message forwarding is safe and reliable.
In addition, compared with the cross-device link aggregation in the conventional manner, the link aggregation group in the example of the present disclosure does not need to occupy port link interconnection between devices, so that port resources are saved, and a traffic path can be switched timely when a link fails, so as to ensure that traffic is not sent to a failed link, and in the link aggregation in the conventional manner, traffic may still be sent to the failed link when the link fails, for example, to the Leaf2 corresponding to the failed link, and the inter-device interconnection link needs to be relied on to detour traffic to the Leaf1 corresponding to the normal link.
Corresponding to the embodiment of the message forwarding method, the application also provides an embodiment of a message forwarding device. Fig. 6 illustrates a structure of a message forwarding apparatus, which is applied to an access device, so that the access device forwards a target message sent to a target device; the target equipment is respectively connected with the plurality of access equipment, and the plurality of access equipment are configured into a link aggregation group; the target device and each access device in the link aggregation group are further configured to be respectively connected with a virtual access device, so that the connection between the target device and the access device is virtualized to be through the virtual access device as a connection medium; the device comprises: a target determining module 61, an address obtaining module 62 and a message forwarding module 63.
A target determining module 61, configured to, when receiving the target packet, obtain a destination address included in the target packet, where the destination address is used to indicate an address of an access device to which a target device is connected;
An address obtaining module 62, configured to decapsulate the target packet to obtain an address of the target device included in the target packet when the destination address is a virtual address of the virtual access device that is preconfigured;
And a message forwarding module 63, configured to send the target message to the target device through the forwarding port according to a correspondence between an address of the target device in the local forwarding table and the forwarding port.
Fig. 7 illustrates another structure of a message forwarding apparatus, which may further include, on the basis of the structure shown in fig. 6: a first route publishing module 64, configured to publish first route information, where the first route information includes: and the destination address is the virtual address of the virtual access equipment, and the next hop address is the address of the access equipment.
in another example, the apparatus may further include: a second route issuing module 65, configured to issue second route information, where the second route information includes: and the destination address is the address of the target equipment, and the next hop address is the virtual address of the virtual access equipment.
In an example, the second route issuing module 65 is further configured to issue, when receiving a failure notification sent by the target device, updated second route information, where the updated second route information includes: a destination address and a corresponding next hop address, wherein the destination address is an address of the target device, and the next hop address is an address of the access device; the failure notification is used for notifying the failure of the part of the links in the link aggregation group.
The embodiment of the message forwarding apparatus in the present application may be applied to a message forwarding device, for example, the message forwarding device may be a Leaf in a VXLAN network shown in fig. 1. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a device in a logical sense, the device is formed by reading a corresponding computer program instruction in a nonvolatile memory into an internal memory through a processor of a message forwarding device where the device is located to operate. In terms of hardware, as shown in fig. 8, the present application is a hardware structure diagram of a message forwarding device where a message forwarding apparatus is located, except for the processor 81, the memory 82, the network interface 83, and the nonvolatile memory 84 shown in fig. 8, the message forwarding device where the apparatus is located in the embodiment may also include other hardware according to the actual function of the message forwarding device, which is not described again.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims (4)

1. A message forwarding method is used for forwarding a target message sent to a target device, the target device is respectively connected with a plurality of access devices, and links connected with the target device and the plurality of access devices are configured as a link aggregation group, and is characterized in that a virtual access device is configured to serve as a connection intermediary between the target device and each access device in the link aggregation group; the method is performed by any one of the plurality of access devices, and comprises: when the target message is received, a first destination address included in the target message is obtained, wherein the first destination address is used for representing an access equipment address connected with target equipment;
If the first destination address is a virtual address of the virtual access device which is pre-configured, decapsulating the target packet to obtain an address of the target device included in the target packet;
Sending the target message to the target equipment from a forwarding port according to the corresponding relation between the address of the target equipment and the forwarding port in a local forwarding table;
Before receiving the target message, issuing second routing information, where the second routing information includes: a second destination address and a corresponding next hop address, wherein the second destination address is an address of the target device, and the next hop address is a virtual address of the virtual access device;
receiving a failure notification sent by the target device, where the failure notification is used to characterize a link failure of the other access devices in the link aggregation group connected to the target device, and issue updated second routing information, where the updated second routing information includes: the second destination address and the corresponding next hop address, where the second destination address is the address of the target device, and the next hop address is the address of the local access device.
2. The method of claim 1, wherein prior to receiving the target packet, the method further comprises:
Issuing first routing information, the first routing information comprising: and a third destination address and a corresponding next hop address, where the third destination address is a virtual address of the virtual access device, and the next hop address is an address of the local access device.
3. A message forwarding device is characterized in that the device is applied to any one of a plurality of access devices, so that the access device forwards a target message sent to a target device; the target device is respectively connected with the plurality of access devices, and links connected with the target device and the plurality of access devices are configured as a link aggregation group; configuring a virtual access device as a connection intermediary between the target device and each access device in the link aggregation group; the device comprises:
The target determining module is used for acquiring a first destination address included in the target message when the target message is received, wherein the first destination address is used for representing an access equipment address connected with target equipment;
An address obtaining module, configured to decapsulate the target packet to obtain an address of the target device included in the target packet when the first destination address is a virtual address of the virtual access device that is preconfigured;
The message forwarding module is used for sending the target message to the target equipment from the forwarding port according to the corresponding relation between the address of the target equipment and the forwarding port in the local forwarding table;
A second route issuing module, configured to issue second route information, where the second route information includes: a second destination address and a corresponding next hop address, wherein the second destination address is an address of the target device, and the next hop address is a virtual address of the virtual access device;
the second route issuing module is further configured to issue updated second route information when receiving the fault notification sent by the target device, where the updated second route information includes: and a second destination address and a corresponding next hop address, where the second destination address is an address of the target device, the next hop address is an address of the local access device, and the failure notification is used to characterize a link failure of another access device in the link aggregation group connected to the target device.
4. The apparatus of claim 3, further comprising:
A first route issuing module, configured to issue first route information, where the first route information includes: and a third destination address and a corresponding next hop address, where the third destination address is a virtual address of the virtual access device, and the next hop address is an address of the local access device.
CN201610351755.5A 2016-05-23 2016-05-23 Message forwarding method and device Active CN106059946B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610351755.5A CN106059946B (en) 2016-05-23 2016-05-23 Message forwarding method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610351755.5A CN106059946B (en) 2016-05-23 2016-05-23 Message forwarding method and device

Publications (2)

Publication Number Publication Date
CN106059946A CN106059946A (en) 2016-10-26
CN106059946B true CN106059946B (en) 2019-12-06

Family

ID=57175170

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610351755.5A Active CN106059946B (en) 2016-05-23 2016-05-23 Message forwarding method and device

Country Status (1)

Country Link
CN (1) CN106059946B (en)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108234305B (en) * 2016-12-22 2021-08-31 上海诺基亚贝尔股份有限公司 Control method and equipment for cross-machine frame link redundancy protection
CN108322376B (en) 2017-06-26 2020-02-11 新华三技术有限公司 Route synchronization method, device and machine-readable storage medium
CN107547402B (en) * 2017-07-19 2020-04-03 新华三技术有限公司 Forwarding table generation method and device
CN107612808B (en) * 2017-09-13 2020-09-08 新华三技术有限公司 Tunnel establishment method and device
CN109768909B (en) * 2019-03-26 2021-04-27 杭州迪普科技股份有限公司 Message forwarding method and device
CN112333098B (en) * 2020-10-29 2022-11-25 杭州迪普科技股份有限公司 Message forwarding method and device between service board cards
CN114500007B (en) * 2022-01-07 2023-12-22 成都市联洲国际技术有限公司 Method, device, medium and equipment for realizing MACsec in M-LAG system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103841028A (en) * 2014-03-24 2014-06-04 杭州华三通信技术有限公司 Method and device for forwarding messages
CN104378297A (en) * 2013-08-15 2015-02-25 杭州华三通信技术有限公司 Message forwarding method and device
CN105490957A (en) * 2014-10-11 2016-04-13 华为技术有限公司 A load sharing method and device
WO2016101591A1 (en) * 2014-12-22 2016-06-30 华为技术有限公司 Packet response method and apparatus

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104660508B (en) * 2013-11-25 2018-03-16 华为技术有限公司 A kind of message forwarding method and device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104378297A (en) * 2013-08-15 2015-02-25 杭州华三通信技术有限公司 Message forwarding method and device
CN103841028A (en) * 2014-03-24 2014-06-04 杭州华三通信技术有限公司 Method and device for forwarding messages
CN105490957A (en) * 2014-10-11 2016-04-13 华为技术有限公司 A load sharing method and device
WO2016101591A1 (en) * 2014-12-22 2016-06-30 华为技术有限公司 Packet response method and apparatus

Also Published As

Publication number Publication date
CN106059946A (en) 2016-10-26

Similar Documents

Publication Publication Date Title
CN106059946B (en) Message forwarding method and device
US11863625B2 (en) Routing messages between cloud service providers
CN116158063B (en) Multi-edge Ethernet channel (MEEC) creation and management
CN107431642B (en) System and method for controlling a switch to capture and monitor network traffic
US10250553B2 (en) ARP offloading for managed hardware forwarding elements
US10454809B2 (en) Automatic network topology detection for merging two isolated networks
US20110261827A1 (en) Distributed Link Aggregation
US11811561B2 (en) Packet transmission method, device, and system
EP4020904B1 (en) Packet transmission method, device, and system
US11671345B2 (en) Self-expansion of a layer 3 network fabric
US11121969B2 (en) Routing between software defined networks and physical networks
JP2015211374A (en) Information processing system, control method for information processing system, and control program for management device
US10033646B2 (en) Resilient active-active data link layer gateway cluster
US20160205033A1 (en) Pool element status information synchronization method, pool register, and pool element
CN110011941B (en) Message forwarding method and device
JP6036506B2 (en) Program and information processing apparatus for specifying fault influence range
JP2016144142A (en) Communication system and communication method
CN117596284B (en) Method, device, computer equipment and storage medium for data transmission
US12273267B2 (en) Symmetric networking for orphan workloads in cloud networks
US20230239273A1 (en) Managing exchanges between edge gateways and hosts in a cloud environment to support a private network connection

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
CB02 Change of applicant information

Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No.

Applicant after: Xinhua three Technology Co., Ltd.

Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No.

Applicant before: Huasan Communication Technology Co., Ltd.

CB02 Change of applicant information
GR01 Patent grant
GR01 Patent grant