CN108718278B - Message transmission method and device - Google Patents

Message transmission method and device Download PDF

Info

Publication number
CN108718278B
CN108718278B CN201810329141.6A CN201810329141A CN108718278B CN 108718278 B CN108718278 B CN 108718278B CN 201810329141 A CN201810329141 A CN 201810329141A CN 108718278 B CN108718278 B CN 108718278B
Authority
CN
China
Prior art keywords
address
group
tunnel
device group
destination
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
CN201810329141.6A
Other languages
Chinese (zh)
Other versions
CN108718278A (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.)
Hangzhou H3C Technologies Co Ltd
Original Assignee
Hangzhou 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 Hangzhou H3C Technologies Co Ltd filed Critical Hangzhou H3C Technologies Co Ltd
Priority to CN201810329141.6A priority Critical patent/CN108718278B/en
Publication of CN108718278A publication Critical patent/CN108718278A/en
Application granted granted Critical
Publication of CN108718278B publication Critical patent/CN108718278B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • H04L45/745Address table lookup; Address filtering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/28Routing or path finding of packets in data switching networks using route fault recovery
    • 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
    • H04L47/00Traffic control in data switching networks
    • H04L47/70Admission control; Resource allocation
    • H04L47/82Miscellaneous aspects
    • H04L47/825Involving tunnels, e.g. MPLS
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4633Interconnection of networks using encapsulation techniques, e.g. tunneling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4641Virtual LANs, VLANs, e.g. virtual private networks [VPN]

Abstract

The application provides a message transmission method and a device, and the method comprises the following steps: inquiring a forwarding table through a destination address of the received data message to obtain a corresponding outgoing interface; if the output interface is a first tunnel, inquiring a routing table through a destination address of the first tunnel to obtain at least two corresponding routes; wherein the source address of the first tunnel is a group address of a first device group, and the destination address of the first tunnel is a group address of a second device group; and selecting one route from the at least two routes, and sending the data message to a second ED corresponding to the selected route, so that the second ED sends the data message to a target host. Through the technical scheme of this application, can realize the load sharing of flow at two at least ED, realize flow balance, alleviate every ED's processing pressure, improve the reliability that ED handled.

Description

Message transmission method and device
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for transmitting a packet.
Background
An EVPN (Ethernet Virtual Private Network) is a two-layer VPN (Virtual Private Network) technology, where a control plane uses MP-BGP (Multi Protocol-Border Gateway Protocol) to announce routing information, and a data plane uses VXLAN (Virtual eXtensible Local Area Network) encapsulation to forward a packet. VXLAN is a two-layer VPN technology based on an IP network and adopting a "MAC (Media Access Control) in UDP (User Datagram Protocol)" encapsulation form, and VXLAN may provide two-layer interconnection for distributed sites and may provide service isolation for different tenants based on an existing service provider or an existing enterprise IP network.
In an EVPN network, multiple data centers may be included, and different data centers may be interconnected by an ED (Edge Device), i.e., an Edge Device of the data center. For example, the ED1 of the data center 1 is connected to the ED2 of the data center 2, so that all messages of the data center 1 need to be sent to the ED2 through the ED1 and sent to each device of the data center 2 through the ED2, and similarly, all messages of the data center 2 need to be sent to the ED1 through the ED2 and sent to each device of the data center 1 through the ED 1.
In the above manner, all messages of the data center need to be processed by the ED of the data center, the processing pressure of the ED is high, and once the ED fails, the data centers cannot be interconnected directly.
Disclosure of Invention
The application provides a message transmission method, a first device group of a first data center comprises at least two first Edge Devices (ED), the method is applied to any first ED, and the method comprises the following steps:
inquiring a forwarding table through a destination address of the received data message to obtain a corresponding outgoing interface;
if the output interface is a first tunnel, inquiring a routing table through a destination address of the first tunnel to obtain at least two corresponding routes; wherein at least two second EDs are included in a second device group of a second data center connected with the first data center, a source address of the first tunnel is a group address of the first device group, and a destination address of the first tunnel is a group address of the second device group;
selecting one route from the at least two routes, and sending the data message to a second ED corresponding to the selected route, so that the second ED sends the data message to a target host; wherein each of the at least two routes corresponds to a second ED within the second device group.
The application provides a message transmission device, include two at least first edge devices ED in the first equipment group of first data center, the device is applied to arbitrary first ED, the device includes:
the obtaining module is used for inquiring a forwarding table through a destination address of the received data message to obtain a corresponding output interface; if the output interface is a first tunnel, inquiring a routing table through a destination address of the first tunnel to obtain at least two corresponding routes; wherein at least two second EDs are included in a second device group of a second data center connected with the first data center, a source address of the first tunnel is a group address of the first device group, and a destination address of the first tunnel is a group address of the second device group;
a selection module for selecting a route from the at least two routes;
a sending module, configured to send the data packet to a second ED corresponding to the route selected by the selection module, so that the second ED sends the data packet to a destination host; wherein each of the at least two routes corresponds to a second ED within the second device group.
Based on the above technical solution, in the embodiment of the present application, a device group including at least two EDs is configured in a data center, and the at least two EDs use the same group IP address, so that when a forwarding table is queried by a destination address of a received data packet, an obtained outgoing interface is a first tunnel, and the destination address of the first tunnel corresponds to at least two routes, and therefore, one route can be selected from the at least two routes, thereby implementing load sharing of traffic at the at least two EDs, implementing traffic balancing, and reducing processing pressure of each ED. When one ED fails, other EDs can provide services, and the reliability of ED processing is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present application or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present application.
FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present application;
fig. 2 is a flowchart of a message transmission method according to an embodiment of the present application;
fig. 3 is a block diagram of a message transmission apparatus according to an embodiment of the present application;
fig. 4 is a hardware configuration diagram of an edge device according to an embodiment of the present application.
Detailed Description
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. Furthermore, as used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein is meant to encompass any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Depending on the context, moreover, the word "if" is used may be interpreted as "at … …," or "when … …," or "in response to a determination.
The embodiment of the application provides a message transmission method, which can be applied to an EVPN network, each data center of the EVPN network can comprise a device group, the device group can comprise at least two EDs, and different data centers can be interconnected through the EDs. Referring to fig. 1, which is a schematic view of an application scenario of the embodiment of the present application, in a device group 110 of a data center 11, an ED111 and an ED112 may be included, and in a device group 120 of a data center 12, an ED121 and an ED122 may be included. Of course, two EDs are illustrated in fig. 1 as an example, and in practical applications, the number of EDs may be more, which is not limited.
Referring to FIG. 1, ED111 connects with each ED within device group 120 and establishes BGP neighbors. For example, the ED111 is connected with the ED121, and a BGP neighbor is established between the ED111 and the ED 121; the ED111 is connected with the ED122, and a BGP neighbor is established between the ED111 and the ED 122; similarly, the ED112 connects with each ED within the device group 120 and establishes BGP neighbors. For example, the ED112 is connected to the ED121, and a BGP neighbor is established between the ED112 and the ED 121; the ED112 is connected with the ED122, and BGP neighbors are established between the ED112 and the ED 122. The IP address of ED111 is 2.2.2.10, the IP address of ED112 is 2.2.2.11, the IP address of ED121 is 3.3.3.10, and the IP address of ED122 is 3.3.3.11.
VTEP113(VXLAN Tunnel End Point) and hosts 114 (e.g., virtual machines, etc.) may also be included in data center 11. VTEP113 is connected to host 114; VTEP113 is connected with ED111, and BGP neighbors are established between VTEP113 and ED 111; VTEP113 is connected to ED112, and BGP neighbors are established between VTEP113 and ED 112. The IP address of VTEP113 is 1.1.1.1, the IP address of host 114 is 11.1.1.2, and the MAC address of host 114 is a-a.
VTEP123 and host 124 may also be included in data center 12. VTEP123 is connected to host 124; the VTEP123 is connected with the ED121, and a BGP neighbor is established between the VTEP123 and the ED 121; VTEP123 is connected to ED122, and BGP neighbors are established between VTEP123 and ED 122. The IP address of VTEP123 is 4.4.4.4, the IP address of host 124 is 10.1.1.2, and the MAC address is B-B-B.
In this embodiment, a group IP address, such as 2.2.2.2, may also be configured for device group 110, that is, a same group IP address 2.2.2 is configured for ED111 and ED112, and a group IP address, such as 3.3.3.3, is configured for device group 120, that is, a same group IP address 3.3.3 is configured for ED121 and ED 122.
VXLAN tunnel a1 may be established on VTEP113 with the source IP address of VXLAN tunnel a1 being the IP address 1.1.1.1 of VTEP113 and the destination IP address being the group IP address 2.2.2.2 of device group 110. The VXLAN tunnel a1 is a VXLAN tunnel between VTEP113 and ED111, and is also a VXLAN tunnel between VTEP113 and ED 112. That is, VTEP113 may send messages to ED111 through VXLAN tunnel a1, and may also send messages to ED112 through VXLAN tunnel a 1.
And a VXLAN tunnel a2 corresponding to VXLAN tunnel a1 may be established at ED111, where the source IP address of VXLAN tunnel a2 is the group IP address 2.2.2.2 of device group 110, the destination IP address is the IP address 1.1.1.1 of VTEP113, and ED111 may send the message to VTEP113 through VXLAN tunnel a 2. A VXLAN tunnel a2 corresponding to VXLAN tunnel a1 may be established at ED112, where the source IP address of VXLAN tunnel a2 is the group IP address 2.2.2.2 of device group 110, and the destination IP address is the IP address 1.1.1.1 of VTEP113, and ED112 may send the message to VTEP113 through VXLAN tunnel a 2.
Based on the IP address 1.1.1.1 and the group IP address 2.2.2.2 of the VTEP113, a VXLAN tunnel a1 may be established on the VTEP113, for example, a VXLAN tunnel a1 may be established in a static manner, or a VXLAN tunnel a1 may be established in a dynamic manner, which is not limited to the establishment manner of the VXLAN tunnel a 1. For example, the user manually configures VXLAN tunnel a1 in VTEP113, or automatically establishes VXLAN tunnel a1 based on ENDP (Enhanced Neighbor Discovery Protocol).
Similarly, based on the IP address 1.1.1.1 and the group IP address 2.2.2.2 of VTEP113, VXLAN tunnel a2 corresponding to VXLAN tunnel a1 may be established at ED111 and ED112, for example, VXLAN tunnel a2 may be established in a static manner, or VXLAN tunnel a2 may be established in a dynamic manner.
VXLAN tunnel B1 may be established on ED111 with the source IP address of VXLAN tunnel B1 being group IP address 2.2.2.2 and the destination IP address being group IP address 3.3.3.3 of device group 120. VXLAN tunnel B1 is a VXLAN tunnel between ED111 and ED121, and is also a VXLAN tunnel between ED111 and ED 122. That is, ED111 may send messages to ED121 via VXLAN tunnel B1, or may send messages to ED122 via VXLAN tunnel B1. VXLAN tunnel B1 is established over ED112, VXLAN tunnel B1 is a VXLAN tunnel between ED112 and ED121, and is also a VXLAN tunnel between ED112 and ED 122. That is, ED112 may send messages to ED121 via VXLAN tunnel B1, or may send messages to ED122 via VXLAN tunnel B1.
In addition, VXLAN tunnel B2 corresponding to VXLAN tunnel B1 may be established on ED121, where the source IP address of VXLAN tunnel B2 is group IP address 3.3.3.3 and the destination IP address is group IP address 2.2.2.2. VXLAN tunnel B2 is a VXLAN tunnel between ED121 and ED111, and is also a VXLAN tunnel between ED121 and ED 112. That is, ED121 may send the message to ED111 through VXLAN tunnel B2, or may send the message to ED112 through VXLAN tunnel B2.
Further, VXLAN tunnel B2 corresponding to VXLAN tunnel B1 may be established on ED122, and VXLAN tunnel B2 is a VXLAN tunnel between ED122 and ED111, and also a VXLAN tunnel between ED122 and ED 112. That is, ED122 may send messages to ED111 via VXLAN tunnel B2, or may send messages to ED112 via VXLAN tunnel B2.
Based on the group IP address 3.3.3.3 and the group IP address 2.2.2.2, the VXLAN tunnel B1 may be established on the ED111 and the ED112, for example, the VXLAN tunnel B1 may be established in a static manner, or the VXLAN tunnel B1 may be established in a dynamic manner, which is not limited to the establishment manner of the VXLAN tunnel B1. For example, the user manually configures VXLAN tunnel B1 at ED111 and ED112, or automatically establishes VXLAN tunnel B1 based on ENDP. Similarly, based on the group IP address 3.3.3.3 and the group IP address 2.2.2.2, the VXLAN tunnel B2 may be established on the ED121 and the ED122, for example, the VXLAN tunnel B2 may be established in a static manner, or the VXLAN tunnel B2 may be established in a dynamic manner, which is not limited herein.
In the above process, the VXLAN tunnel B1 and the VXLAN tunnel B2 may be a Data Center Interconnection (Data Center Interconnection) type VXLAN tunnel (which may be referred to as a VXLAN-DCI tunnel), or may be other types of VXLAN tunnels, which is not limited.
A VXLAN tunnel C1 may be established on VTEP123, the source IP address of VXLAN tunnel C1 being IP address 4.4.4.4 of VTEP123 and the destination IP address being group IP address 3.3.3.3; the VXLAN tunnel C1 is a VXLAN tunnel between VTEP123 and ED121, and is also a VXLAN tunnel between VTEP123 and ED 122. That is, VTEP123 may send messages to ED121 through VXLAN tunnel C1, and may also send messages to ED122 through VXLAN tunnel C1. In addition, VXLAN tunnel C2 corresponding to VXLAN tunnel C1 may be established on ED121, where VXLAN tunnel C2 has a source IP address of 3.3.3.3 and a destination IP address of 4.4.4.4. ED121 may send the message to VTEP123 through VXLAN tunnel C2. A VXLAN tunnel C2 corresponding to VXLAN tunnel C1 may be established at ED122, and ED122 may send a message to VTEP123 through VXLAN tunnel C2.
For the establishment of the VXLAN tunnel C1 and the VXLAN tunnel C2, the VXLAN tunnel may be established in a static manner, or the VXLAN tunnel may be established in a dynamic manner, which is not limited herein.
Since VTEP113 establishes a BGP neighbor with ED111, ED111 may issue a BGP route to VTEP113 for group IP address 2.2.2.2, the next hop address of the BGP route being IP address 2.2.2.10 of ED111, and VTEP113 may learn the BGP route in a routing table after receiving the BGP route through interface 1131, as shown in table 1. Similarly, VTEP113 may learn the BGP routes published by ED112 in a routing table, see Table 1. As can be seen from table 1, the group IP address 2.2.2.2 corresponds to two BGP routes, which form an equivalent route to the group IP address 2.2.2.2.
TABLE 1
Destination IP address Next hop address Outlet interface
2.2.2.2 2.2.2.10 1131
2.2.2.2 2.2.2.11 1132
In the foregoing process, for example, ED111 publishes the BGP route to VTEP113, and ED112 publishes the BGP route to VTEP113, in practical applications, a Route Reflector (RR) may be further included, and the route reflector is not shown in fig. 1, so that ED111 may send the BGP route to the route reflector, and the route reflector sends the BGP route to VTEP113, so that VTEP113 learns the BGP route in the route table. Similarly, ED112 may send the BGP route to a route reflector, which sends the BGP route to VTEP113, so that VTEP113 learns the BGP route in a routing table.
Because ED111 and ED121 establish a BGP neighbor, ED121 may issue a BGP route for group IP address 3.3.3.3 to ED111, where the next hop address of the BGP route is IP address 3.3.3.10 of ED121, and ED111 may learn the BGP route in the routing table after receiving the BGP route through interface 1111, as shown in table 2. Similarly, the ED111 may also learn BGP routes published by the ED122 in the routing table, as shown in Table 2. As can be seen from table 2, the group IP address 3.3.3.3 corresponds to two BGP routes, which may form an equivalent route to the group IP address 3.3.3.3.
TABLE 2
Destination IP address Next hop address Outlet interface
3.3.3.3 3.3.3.10 1111
3.3.3.3 3.3.3.11 1112
Similarly, the routing table of ED112 can be seen in Table 3, the routing table of ED121 can be seen in Table 4, the routing table of ED122 can be seen in Table 5, and the routing table of VTEP123 can be seen in Table 6. Of course, the above routing tables are only an example, and the contents of the routing table are not limited.
TABLE 3
Destination IP address Next hop address Outlet interface
3.3.3.3 3.3.3.10 1121
3.3.3.3 3.3.3.11 1122
TABLE 4
Destination IP address Next hop address Outlet interface
2.2.2.2 2.2.2.10 1211
2.2.2.2 2.2.2.11 1212
TABLE 5
Destination IP address Next hop address Outlet interface
2.2.2.2 2.2.2.10 1221
2.2.2.2 2.2.2.11 1222
TABLE 6
Destination IP address Next hop address Outlet interface
3.3.3.3 3.3.3.10 1231
3.3.3.3 3.3.3.11 1232
In the above process, taking the example that ED121 publishes the BGP route to ED111 or ED112, and ED122 publishes the BGP route to ED111 or ED112, in practical applications, ED121 or ED122 may send the BGP route to the route reflector, and the route reflector sends the BGP route to ED111 or ED112, so that ED111 or ED112 learns the BGP route in the routing table. ED111 or ED112 may send BGP routes to route reflectors, which send BGP routes to ED121 or ED122, so that ED121 or ED122 learns the BGP routes in a routing table.
In the application scenario, the embodiment of the present application may further relate to a forwarding entry (for example, an MAC entry, an ARP entry, a routing entry, and the like, which is not limited thereto) learning process and a message transmission process, and the forwarding entry learning process and the message transmission process are described in detail below with reference to the application scenario.
Taking the forwarding table entry of the learning host 124 as an example, then: after the host 124 is online, a gratuitous ARP (Address Resolution Protocol) message may be sent, where the gratuitous ARP message carries the IP Address 10.1.1.2 and the MAC Address B-B of the host 124; VTEP123, upon receiving the gratuitous ARP message over interface 1233, adds a forwarding entry to the local forwarding table, see table 7.
TABLE 7
IP address MAC address Outlet interface
10.1.1.2 B-B-B 1233
VTEP123 may send a synchronization message (e.g., a BGP synchronization message) to ED121, where the synchronization message may carry IP address 10.1.1.2 of host 124, and the next hop address is IP address 4.4.4.4 of VTEP 123; in practical application, the synchronization message may also carry the MAC address B-B of the host 124, or may not carry the MAC address B-B, and the following description will take the example of not carrying the MAC address B-B as an example. After receiving the synchronization message, the ED121 may add a forwarding table entry in a local forwarding table, as shown in table 8; in table 8, since the next hop address 4.4.4.4 is the destination IP address of VXLAN tunnel C2, the egress interface is VXLAN tunnel C2. Similarly, VTEP123 may also send a synchronization message to ED122, and ED122 may also add a forwarding table entry in a local forwarding table after receiving the synchronization message, as shown in table 8.
TABLE 8
IP address Outlet interface
10.1.1.2 VXLAN tunnel C2
ED121 may send a synchronization message to ED111, which may carry IP address 10.1.1.2 of host 124 and a next hop address, which is group IP address 3.3.3.3, instead of IP address 3.3.3.10 of ED 121; ED122 may also send a synchronization message to ED111 that carries a next hop address that is also group IP address 3.3.3.3 instead of IP address 3.3.3.11 of ED 122; after receiving any synchronization message, ED111 may add a forwarding table entry in a local forwarding table, as shown in table 9; in table 9, since the next hop address 3.3.3.3 is the destination IP address of VXLAN tunnel B1, the egress interface is VXLAN tunnel B1. Similarly, ED121 and ED122 may also send synchronization messages to ED112, and ED112 adds a forwarding table entry in a local forwarding table after receiving any synchronization message, as shown in table 9.
TABLE 9
IP address Outlet interface
10.1.1.2 VXLAN tunnel B1
ED111 may send a synchronization message to VTEP113 that may carry host 124's IP address 10.1.1.2 and a next hop address, and the next hop address is group IP address 2.2.2.2 instead of ED 111's IP address 2.2.2.10; ED112 also sends a synchronization message to VTEP113 that carries host 124's IP address 10.1.1.2 and the next hop address, which is also group IP address 2.2.2.2 instead of ED 112's IP address 2.2.2.11; after receiving any synchronization message, VTEP113 may add a forwarding table entry in a local forwarding table, as shown in table 10; in table 10, since the next hop address 2.2.2.2 is the destination IP address of VXLAN tunnel a1, the egress interface is VXLAN tunnel a 1.
Watch 10
IP address Outlet interface
10.1.1.2 VXLAN tunnel A1
To this end, the learning process of the forwarding table entry of the host 124 may be completed, and then, the message transmission process may be implemented based on the forwarding table entry. Specifically, during the message transmission process, based on the forwarding table entries shown in table 7-table 10, the process of sending a message (e.g., a data message) from the host 114 to the host 124 may include:
host 114 sends datagram 1 to host 124 with the destination IP address of datagram 1 being the IP address 10.1.1.2 of host 124. After receiving the data packet 1, the VTEP113 queries the local forwarding table shown in the table 10 by using the IP address 10.1.1.2, and obtains an egress interface as a VXLAN tunnel a 1. Then, VTEP113 may perform VXLAN encapsulation on data packet 1, without limiting the VXLAN encapsulation process, obtain VXLAN-encapsulated data packet 2, and send data packet 2 through VXLAN tunnel a 1.
When sending data message 2 through VXLAN tunnel a1, since the destination IP address of VXLAN tunnel a1 is 2.2.2.2, VTEP113 can also obtain two routes for IP address 2.2.2.2 by looking up the routing table shown in table 1 through IP address 2.2.2.2, and these two routes are equivalent routes.
Therefore, VTEP113 may also select one route from the two routes, and if the first route is selected, send datagram 2 through interface 1131, that is, send datagram 2 to ED 111; if the second route is selected, data packet 2 is sent over interface 1132, i.e., data packet 2 is sent to ED 112.
When selecting one route from the two routes, VTEP113 may select one route by using a load balancing algorithm (e.g., a hash algorithm, a polling algorithm, etc., without limitation), so as to share traffic load to ED111 and ED112, that is, balance traffic is implemented on ED111 and ED 112.
If the link between VTEP113 and ED111 fails or ED111 fails, VTEP113 may sense the failure, and VTEP113 selects the second route instead of the first route when selecting one route from the two routes, thereby avoiding sending data packet 2 to the failed link or ED111, avoiding loss of data packet 2, and improving reliability of transmission.
Assuming that ED111 receives data message 2, ED111 decapsulates VXLAN from data message 2 to obtain data message 1, and does not limit the process of decapsulating VXLAN. Then, ED111 may query the local forwarding table shown in table 9 by using destination IP address 10.1.1.2 of data message 1, and obtain that the egress interface is VXLAN tunnel B1. Then, ED111 may perform VXLAN encapsulation on data packet 1 to obtain VXLAN-encapsulated data packet 3, and send data packet 3 through VXLAN tunnel B1.
When sending data message 3 through VXLAN tunnel B1, because the destination IP address of VXLAN tunnel B1 is 3.3.3.3, ED111 may also look up the routing table shown in table 2 through IP address 3.3.3.3, thereby obtaining two routes for IP address 3.3.3.3, and these two routes are equivalent routes.
Therefore, the ED111 may also select one route from the two routes, and if the first route is selected, send the data packet 3 through the interface 1111, that is, send the data packet 3 to the ED 121; if the second route is selected, data packet 3 is sent over interface 1112, i.e., data packet 3 is sent to ED 122.
When selecting one route from the two routes, the ED111 may select one route by using a load balancing algorithm (such as a hash algorithm, a polling algorithm, and the like, without limitation), so that traffic load may be shared between the ED121 and the ED122, that is, traffic balancing is implemented on the ED121 and the ED 122.
If the link between ED111 and ED121 fails or ED121 fails, ED111 may sense the failure, and ED111 selects the second route instead of the first route when selecting one route from the two routes, so as to avoid sending data packet 3 to the failed link or ED121, avoid loss of data packet 3, and improve reliability of transmission.
Assuming that ED121 receives data packet 3, ED121 decapsulates data packet 3 by VXLAN to obtain data packet 1, and queries the local forwarding table shown in table 8 by using destination IP address 10.1.1.2 of data packet 1 to obtain an egress interface as VXLAN tunnel C2. The ED121 performs VXLAN encapsulation on the data packet 1 to obtain a data packet 4 after VXLAN encapsulation, and sends the data packet 4 through a VXLAN tunnel C2. When sending the data message 4 through the VXLAN tunnel C2, because the destination IP address of the VXLAN tunnel C2 is 4.4.4.4, the ED121 may also query the routing table shown in table 4 through the IP address 4.4.4.4 to obtain the interface 1213, and in table 4, the corresponding relationship between the IP address 4.4.4.4 and the interface 1213 is not recorded. Data message 4 is then sent over interface 1213, i.e., data message 4 is sent to VTEP 123.
After receiving the data message 4, the VTEP123 decapsulates the data message 4 by VXLAN to obtain a data message 1, and queries the local forwarding table shown in table 7 by using the destination IP address 10.1.1.2 of the data message 1 to obtain an output interface as an interface 1233, so that the data message 1 is sent through the interface 1233. In this way, datagram 1 may be sent to the host 124, where the datagram transmission process may be completed.
In summary, in the embodiment of the present application, a device group including at least two EDs is configured in a data center, and the at least two EDs use the same group IP address, so that load sharing of traffic can be achieved on the at least two EDs, the traffic is balanced, and processing pressure of each ED is relieved. Moreover, when one ED fails, other EDs can provide services, and the reliability of ED processing is improved.
Based on the same application concept as the method, the message transmission method provided by the embodiment of the application can be applied to an EVPN network, the EVPN network can include a plurality of data centers, and two data centers are taken as an example in the following, so that in practical application, the number of the data centers can be more. For ease of distinction, these two data centers will be referred to as a first data center (e.g., data center 11) and a second data center (e.g., data center 12).
At least two first EDs are included in a first device group (e.g., device group 110) of a first data center, e.g., first EDs are ED111 and ED112 in fig. 1, and at least two second EDs are included in a second device group (e.g., device group 120) of a second data center, e.g., second EDs are ED121 and ED122 in fig. 1. The group address of the first device group is IP address 2.2.2.2 and the group address of the second device group is IP address 3.3.3.3. For any first ED in the first device group, the first ED may connect with each second ED in the second device group and establish a BGP neighbor. Similarly, for any second ED in the second device group, the second ED may connect with each first ED in the first device group and establish a BGP neighbor.
Referring to fig. 2, a flowchart of a message transmission method proposed in the embodiment of the present application is shown, where the method may be applied to any first ED (e.g., the ED111 or the ED112), and the method may include:
step 201, after receiving the data packet, querying a forwarding table (such as an MAC table, an ARP table, a routing table, etc.) through a destination address (such as a destination IP address) of the data packet to obtain a corresponding egress interface.
Step 202, if the egress interface is a first tunnel, querying a routing table through a destination address (e.g., a destination IP address) of the first tunnel to obtain at least two corresponding routes; wherein the source address of the first tunnel is a group address of a first device group and the destination address of the first tunnel is a group address of a second device group.
Step 203, selecting one route from the at least two routes, and sending the data message to a second ED corresponding to the selected route, so that the second ED sends the data message to a destination host; wherein each of the at least two routes corresponds to a second ED within the second device group.
Referring to the foregoing embodiment, assuming that the first ED is the ED111, the ED111 may query the local forwarding table shown in the table 9 through the destination IP address 10.1.1.2 of the data packet to obtain a corresponding outgoing interface.
Since the egress interface is VXLAN tunnel B1 (i.e., the first tunnel), the source address of VXLAN tunnel B1 is the group address 2.2.2.2 of device group 110, and the destination address of VXLAN tunnel B1 is the group address 3.3.3.3.3 of device group 120, two routes for destination address 3.3.3.3 are obtained by querying the routing table shown in table 2 for the destination address 3.3.3.3 of VXLAN tunnel B1, and these two routes are equivalent routes.
Then, ED111 selects one route from the two routes, and if the first route is selected, sends the data packet to ED121 corresponding to the route through interface 1111, and ED121 sends the data packet to the destination host, which is not described again; if the second route is selected, the ED121 sends the data packet to the destination host via the interface 1112 to send the data packet to the ED122 corresponding to the route.
Before querying a forwarding table through a destination address of the data message to obtain a corresponding outgoing interface, the first ED may further receive a first synchronization message sent by the second ED, where the first synchronization message may carry an address of a destination host and a next hop address, and the next hop address is a group address of a second device group to which the second ED belongs; then, the first ED determines a first tunnel whose destination address is a group address of the second device group; the first ED may then record the correspondence of the address of the destination host to the first tunnel in a forwarding table.
After receiving the first synchronization message sent by the second ED, the first ED may further send a second synchronization message to the VTEP device of the first data center, where the second synchronization message may carry an address of the destination host and a next hop address, and the next hop address may be a group address of a first device group to which the first ED belongs.
Further, after receiving the second synchronization message, the VTEP device may further record a correspondence relationship between the address of the destination host and a second tunnel in a local forwarding table, where a source address of the second tunnel is an address of the VTEP device, and a destination address of the second tunnel is a group address of the first device group.
Referring to the above embodiments, assuming that the first ED is ED111, ED121 and ED122 may both send a synchronization message to ED111, and ED111 may receive the synchronization message, the synchronization message may carry address 10.1.1.2 of the destination host and the next hop address, and the next hop address is group address 3.3.3.3 of device group 123, instead of the IP address of ED121 or ED 122. ED111 then determines the first tunnel whose destination address is group address 3.3.3.3, VXLAN tunnel B1. ED111 may then record the correspondence of destination host address 10.1.1.2 and VXLAN tunnel B1 in a forwarding table, see table 9.
ED111, upon receiving the above-mentioned synchronization message, may also send a synchronization message to VTEP113 of first data 11, which may carry address 10.1.1.2 of the destination host and the next hop address, and which is group address 2.2.2.2 of device group 110 to which ED111 belongs, instead of IP address 2.2.2.10 of ED 111. VTEP113, upon receiving the synchronization message, may also record in a forwarding table a correspondence between address 10.1.1.2 of the destination host and the second tunnel (i.e., VXLAN tunnel a1), where the source address of VXLAN tunnel a1 is the address of VTEP113 and the destination address is group address 2.2.2.2, as shown in table 10.
Before querying a forwarding table through a destination address of the data packet to obtain a corresponding egress interface, the first ED may further receive a routing message sent by the second ED, where a destination address carried in the routing message may be a group address of a second device group to which the second ED belongs, and a next hop address carried in the routing message may be an address of the second ED. Then, the first ED may determine a receiving interface of the routing message, and record a corresponding relationship among the group address of the second device group, the address of the second ED, and the receiving interface in a routing table.
Referring to the above embodiments, assuming that the first ED is ED111, ED121 and ED122 both send routing messages to ED 111. When ED121 sends a routing message to ED111, a destination address carried by the routing message may be a group address 3.3.3.3 of device group 120, and a next hop address carried by the routing message may be IP address 3.3.3.10 of ED 121; after receiving the routing message through interface 1111, ED111 determines that the receiving interface of the routing message is interface 1111, and records the corresponding relationship between group address 3.3.3.3, IP address 3.3.3.10 of ED121 and interface 1111 in the routing table, as shown in table 2. When ED122 sends a routing message to ED111, the destination address carried by the routing message is group address 3.3.3.3 of device group 120, and the next hop address carried by the routing message may be IP address 3.3.3.11 of ED 122; after receiving the routing message through interface 1112, ED111 determines that the receiving interface of the routing message is interface 1112, and records a correspondence relationship between group address 3.3.3.3, IP address 3.3.3.11 of ED122 and interface 1112 in a routing table, as shown in table 2.
Wherein a first tunnel is established between the first ED and each second ED within the second device group using the group address of the first device group and the group address of the second device group; and/or establishing a second tunnel between the first ED and the VTEP device by using the group address of the first device group and the address of the VTEP device of the first data center. For example, assuming that the first ED is ED111, VXLAN tunnel a2 is established on ED111, the source IP address of VXLAN tunnel a2 is the group IP address 2.2.2.2 of device group 110, and the destination IP address is the IP address 1.1.1.1 of VTEP 113; correspondingly, VXLAN tunnel a1 may be established on VTEP113, where the source IP address of VXLAN tunnel a1 is IP address 1.1.1.1 of VTEP113, and the destination IP address is group IP address 2.2.2.2 of device group 110. In addition, VXLAN tunnel B1 may be established on ED111, the source IP address of VXLAN tunnel B1 being group IP address 2.2.2.2 and the destination IP address being group IP address 3.3.3.3 of device group 120; correspondingly, VXLAN tunnel B2 may be established on ED121 and ED122, respectively, where the source IP address of VXLAN tunnel B2 is group IP address 3.3.3.3, and the destination IP address is group IP address 2.2.2.2.
When the first ED selects one route from the at least two routes, a load balancing algorithm (such as a hash algorithm, a polling algorithm, etc.) may be used to select one route from the at least two routes; alternatively, a route corresponding to a link that has not failed may be selected from the at least two routes, that is, the link corresponding to the route has not failed, and the second ED corresponding to the route has not failed.
Based on the above technical solution, in the embodiment of the present application, a device group including at least two EDs is configured in a data center, and the at least two EDs use the same group IP address, so that when a forwarding table is queried by a destination address of a received data packet, an obtained outgoing interface is a first tunnel, and the destination address of the first tunnel corresponds to at least two routes, and therefore, one route can be selected from the at least two routes, thereby implementing load sharing of traffic at the at least two EDs, implementing traffic balancing, and reducing processing pressure of each ED. When one ED fails, other EDs can provide services, and the reliability of ED processing is improved.
Based on the same application concept as the method described above, an embodiment of the present application further provides a message transmission apparatus, where a first device group of a first data center includes at least two first edge devices ED, and the message transmission apparatus is applied to any first ED, and as shown in fig. 3, the message transmission apparatus includes:
an obtaining module 301, configured to query a forwarding table through a destination address of the received data packet, so as to obtain a corresponding egress interface; if the output interface is a first tunnel, inquiring a routing table through a destination address of the first tunnel to obtain at least two corresponding routes; wherein at least two second EDs are included in a second device group of a second data center connected with the first data center, a source address of the first tunnel is a group address of the first device group, and a destination address of the first tunnel is a group address of the second device group;
a selecting module 302, configured to select one route from the at least two routes;
a sending module 303, configured to send the data packet to a second ED corresponding to the route selected by the selecting module 302, so that the second ED sends the data packet to a destination host; wherein each of the at least two routes corresponds to a second ED within the second device group.
In one example, the message transmission device may further include (not shown in the figure):
a receiving module, configured to receive a first synchronization message sent by a second ED, where the first synchronization message carries an address of a destination host and a next hop address, and the next hop address is a group address of a second device group to which the second ED belongs;
a determining module for determining a first tunnel whose destination address is a group address of the second device group;
and the recording module is used for recording the corresponding relation between the address of the destination host and the first tunnel in the forwarding table.
The sending module 303 is further configured to send a second synchronization message to a VTEP device of a first data center, where the second synchronization message carries an address of the destination host and a next hop address, and the next hop address is a group address of a first device group to which the first ED belongs; so that the VTEP device records a corresponding relationship between the address of the destination host and a second tunnel in a forwarding table, where a source address of the second tunnel is the address of the VTEP device, and a destination address of the second tunnel is a group address of the first device group.
In an example, the receiving module is further configured to receive a routing message sent by a second ED, where a destination address carried in the routing message is a group address of a second device group to which the second ED belongs, and a next hop address is an address of the second ED; the determining module is further configured to determine a receiving interface of the routing message; the recording module is further configured to record, in a routing table, a corresponding relationship between a group address of the second device group, an address of the second ED, and the receiving interface.
In one example, the message transmission device may further include (not shown in the figure):
an establishing module configured to establish a first tunnel between the first ED and each second ED within the second device group using the group address of the first device group and the group address of the second device group; and/or the presence of a gas in the gas,
establishing a second tunnel between the first ED and the VTEP device using the group address of the first device group and the address of the VTEP device of the first data center.
The selecting module 302 is specifically configured to select a route from the at least two routes by using a load balancing algorithm; or selecting a route corresponding to the link which does not have the fault from the at least two routes.
In terms of hardware, the hardware architecture diagram of the edge device provided in the embodiment of the present application may specifically refer to fig. 4, where the hardware structure may include: a machine-readable storage medium and a processor, wherein:
a machine-readable storage medium: the instruction code is stored.
A processor: the message transmission operation of the above-mentioned example application of the present application is realized by communicating with a machine-readable storage medium, reading and executing the instruction codes stored in the machine-readable storage medium.
Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and so forth. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims (10)

1. A message transmission method is characterized in that a first device group of a first data center comprises at least two first Edge Devices (EDs), and the method is applied to any first ED and comprises the following steps:
inquiring a forwarding table through a destination address of the received data message to obtain a corresponding outgoing interface;
if the output interface is a first tunnel, inquiring a routing table through a destination address of the first tunnel to obtain at least two corresponding routes; wherein at least two second EDs are included in a second device group of a second data center connected with the first data center, a source address of the first tunnel is a group address of the first device group, and a destination address of the first tunnel is a group address of the second device group;
selecting one route from the at least two routes, and sending the data message to a second ED corresponding to the selected route, so that the second ED sends the data message to a target host; wherein each of the at least two routes corresponds to a second ED within the second device group;
before querying a forwarding table through a destination address of the received data packet and obtaining a corresponding egress interface, the method further includes: receiving a first synchronization message sent by a second ED, wherein the first synchronization message carries an address of a destination host and a next hop address, and the next hop address is a group address of a second device group to which the second ED belongs; determining a first tunnel whose destination address is a group address of the second device group; and recording the corresponding relation between the address of the destination host and the first tunnel in a forwarding table.
2. The method of claim 1,
after receiving the first synchronization message sent by the second ED, the method further includes:
sending a second synchronization message to an extensible virtual local area network tunnel endpoint (VTEP) device of a first data center, wherein the second synchronization message carries an address of the destination host and a next hop address, and the next hop address is a group address of a first device group to which the first ED belongs; so that the VTEP device records the corresponding relation between the address of the destination host and a second tunnel in a forwarding table, wherein the source address of the second tunnel is the address of the VTEP device, and the destination address of the second tunnel is the group address of the first device group.
3. The method of claim 1, wherein before querying a forwarding table through a destination address of the received data packet to obtain a corresponding egress interface, the method further comprises:
receiving a routing message sent by a second ED, wherein a destination address carried by the routing message is a group address of a second device group to which the second ED belongs, and a next hop address is an address of the second ED;
and determining a receiving interface of the routing message, and recording the corresponding relation among the group address of the second device group, the address of the second ED and the receiving interface in a routing table.
4. The method according to claim 1 or 2, characterized in that the method further comprises:
establishing a first tunnel between the first ED and each second ED within the second device group using the group address of the first device group and the group address of the second device group; and/or the presence of a gas in the gas,
establishing a second tunnel between the first ED and the VTEP device using the group address of the first device group and the address of the VTEP device of the first data center.
5. The method of claim 1,
the selecting one route from the at least two routes includes:
selecting a route from the at least two routes by adopting a load balancing algorithm; alternatively, the first and second electrodes may be,
and selecting a route corresponding to the link which does not fail from the at least two routes.
6. A message transmission apparatus, wherein a first device group of a first data center includes at least two first edge devices ED, and the apparatus is applied to any first ED, and the apparatus includes:
the obtaining module is used for inquiring a forwarding table through a destination address of the received data message to obtain a corresponding output interface; if the output interface is a first tunnel, inquiring a routing table through a destination address of the first tunnel to obtain at least two corresponding routes; wherein at least two second EDs are included in a second device group of a second data center connected with the first data center, a source address of the first tunnel is a group address of the first device group, and a destination address of the first tunnel is a group address of the second device group;
a selection module for selecting a route from the at least two routes;
a sending module, configured to send the data packet to a second ED corresponding to the route selected by the selection module, so that the second ED sends the data packet to a destination host; wherein each of the at least two routes corresponds to a second ED within the second device group;
further comprising: a receiving module, configured to receive a first synchronization message sent by a second ED, where the first synchronization message carries an address of a destination host and a next hop address, and the next hop address is a group address of a second device group to which the second ED belongs; a determining module for determining a first tunnel whose destination address is a group address of the second device group; and the recording module is used for recording the corresponding relation between the address of the destination host and the first tunnel in the forwarding table.
7. The apparatus according to claim 6, wherein the sending module is further configured to send a second synchronization message to an extensible virtual local area network tunnel endpoint, VTEP, device in the first data center, where the second synchronization message carries an address of the destination host and a next hop address, and the next hop address is a group address of a first device group to which the first ED belongs; so that the VTEP device records a corresponding relationship between the address of the destination host and a second tunnel in a forwarding table, where a source address of the second tunnel is the address of the VTEP device, and a destination address of the second tunnel is a group address of the first device group.
8. The apparatus of claim 6, further comprising:
a receiving module, configured to receive a routing message sent by a second ED, where a destination address carried in the routing message is a group address of a second device group to which the second ED belongs, and a next hop address is an address of the second ED;
a determining module, configured to determine a receiving interface of the routing message;
and the recording module is used for recording the corresponding relation among the group address of the second equipment group, the address of the second ED and the receiving interface in a routing table.
9. The apparatus of claim 6 or 7, further comprising:
an establishing module configured to establish a first tunnel between the first ED and each second ED within the second device group using the group address of the first device group and the group address of the second device group; and/or the presence of a gas in the gas,
establishing a second tunnel between the first ED and the VTEP device using the group address of the first device group and the address of the VTEP device of the first data center.
10. The apparatus of claim 6,
the selection module is specifically configured to select one route from the at least two routes by using a load balancing algorithm; or selecting a route corresponding to the link which does not have the fault from the at least two routes.
CN201810329141.6A 2018-04-13 2018-04-13 Message transmission method and device Active CN108718278B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810329141.6A CN108718278B (en) 2018-04-13 2018-04-13 Message transmission method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810329141.6A CN108718278B (en) 2018-04-13 2018-04-13 Message transmission method and device

Publications (2)

Publication Number Publication Date
CN108718278A CN108718278A (en) 2018-10-30
CN108718278B true CN108718278B (en) 2021-04-27

Family

ID=63898997

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810329141.6A Active CN108718278B (en) 2018-04-13 2018-04-13 Message transmission method and device

Country Status (1)

Country Link
CN (1) CN108718278B (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111147381B (en) * 2018-11-02 2022-01-18 华为技术有限公司 Flow balancing method and device
CN109921992B (en) * 2019-03-26 2021-07-23 新华三技术有限公司 Path selection method and device, network equipment and ED equipment
CN112019417B (en) * 2019-05-30 2021-11-19 华为技术有限公司 Method and equipment for transmitting message
CN110391984B (en) * 2019-07-26 2022-01-25 新华三大数据技术有限公司 Message forwarding method and device
CN112769966B (en) * 2019-10-21 2023-08-25 阿里巴巴集团控股有限公司 Address information distribution method and device and electronic equipment
CN112751766B (en) * 2019-10-30 2023-07-11 华为技术有限公司 Message forwarding method and system, related equipment and chip
CN111884904B (en) * 2020-07-23 2021-09-24 中盈优创资讯科技有限公司 Method and device for dynamically managing vxlan tunnel based on equipment configuration
CN111988221B (en) * 2020-08-31 2022-09-13 网易(杭州)网络有限公司 Data transmission method, data transmission device, storage medium and electronic equipment
CN115150323B (en) * 2022-07-04 2023-06-02 中国联合网络通信集团有限公司 Route implementation method, VTEP, first edge equipment and system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105591924A (en) * 2014-11-10 2016-05-18 瞻博网络公司 Signaling aliasing capability in data centers
CN107135133A (en) * 2016-02-26 2017-09-05 丛林网络公司 Horizontal segmentation packet forwarding in many family PBB EVPN networks
CN107612809A (en) * 2017-10-31 2018-01-19 新华三技术有限公司 A kind of multicast list synchronous method and equipment
CN107733793A (en) * 2017-11-28 2018-02-23 新华三技术有限公司 A kind of forwarding-table item maintaining method and device
WO2018065813A1 (en) * 2016-10-05 2018-04-12 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for distribution of virtual layer 2 traffic towards multiple access network devices

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8867367B2 (en) * 2012-05-10 2014-10-21 Telefonaktiebolaget L M Ericsson (Publ) 802.1aq support over IETF EVPN

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105591924A (en) * 2014-11-10 2016-05-18 瞻博网络公司 Signaling aliasing capability in data centers
CN107135133A (en) * 2016-02-26 2017-09-05 丛林网络公司 Horizontal segmentation packet forwarding in many family PBB EVPN networks
WO2018065813A1 (en) * 2016-10-05 2018-04-12 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for distribution of virtual layer 2 traffic towards multiple access network devices
CN107612809A (en) * 2017-10-31 2018-01-19 新华三技术有限公司 A kind of multicast list synchronous method and equipment
CN107733793A (en) * 2017-11-28 2018-02-23 新华三技术有限公司 A kind of forwarding-table item maintaining method and device

Also Published As

Publication number Publication date
CN108718278A (en) 2018-10-30

Similar Documents

Publication Publication Date Title
CN108718278B (en) Message transmission method and device
US10404788B2 (en) Express route transmissions between virtual machines and cloud service computing devices
CN108259299B (en) Forwarding table item generating method and device and machine-readable storage medium
CN108259347B (en) Message transmission method and device
CN107547391B (en) Message transmission method and device
CN109104364B (en) Designated forwarder election method and device
CN108600074B (en) Method and device for forwarding multicast data message
CN108600109B (en) Message forwarding method and device
US10142223B2 (en) Symmetric intersubnet traffic load balancing in multihomed networks
CN107317752B (en) Method and device for forwarding data message
CN109412949B (en) Data message transmission method and device
CN103139075B (en) A kind of message transmitting method and equipment
CN102792651B (en) At the device of MAC layer application service path Route Selection
CN109412926B (en) Tunnel establishment method and device
US11296979B2 (en) Method and system for symmetric integrated routing and bridging
US20140040477A1 (en) Connection mesh in mirroring asymmetric clustered multiprocessor systems
CN106209557A (en) Message forwarding method and device
CN108718276B (en) Message forwarding method and device
CN107682261B (en) Flow forwarding method and device
CN111130978B (en) Network traffic forwarding method and device, electronic equipment and machine-readable storage medium
CN108259205B (en) Route publishing method and network equipment
CN113364660A (en) Data packet processing method and device in LVS load balancing
CN108768845B (en) Multi-homing host routing synchronization method and device
US20230412503A1 (en) Determining unicast addresses of gateway network devices associated with an anycast address in vxlan-evpn dci environments
CN108632125B (en) Multicast table item management method, device, equipment and machine readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant