CN108306806B - Message forwarding method and device - Google Patents

Message forwarding method and device Download PDF

Info

Publication number
CN108306806B
CN108306806B CN201810116549.5A CN201810116549A CN108306806B CN 108306806 B CN108306806 B CN 108306806B CN 201810116549 A CN201810116549 A CN 201810116549A CN 108306806 B CN108306806 B CN 108306806B
Authority
CN
China
Prior art keywords
port
vtep
message
unicast
forwarding
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
CN201810116549.5A
Other languages
Chinese (zh)
Other versions
CN108306806A (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 CN201810116549.5A priority Critical patent/CN108306806B/en
Publication of CN108306806A publication Critical patent/CN108306806A/en
Application granted granted Critical
Publication of CN108306806B publication Critical patent/CN108306806B/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
    • 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/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • 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]
    • 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

Landscapes

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

Abstract

The application provides a message forwarding method and a device, wherein the method is applied to any VTEP in a DR system, and comprises the following steps: acquiring the state of a DR port on an opposite-end VTEP which belongs to the same DR system as the VTEP; if the obtained state of the DR port on the VTEP at the opposite end is an UP state, searching a local DR port corresponding to the DR port on the VTEP at the opposite end; the DR port on the opposite end VTEP and the local DR port are connected with the same aggregation interface on the same user host; setting all AC ports configured on the local DR port to forbid to forward non-unicast messages; and after receiving the VXLAN message sent by the opposite-end VTEP, if the message after the decapsulation of the VXLAN message is a non-unicast message, forwarding the non-unicast message to other AC ports recorded in a broadcast list except the AC port which is set to prohibit the forwarding of the non-unicast message. Loops can be prevented using the methods provided herein.

Description

Message forwarding method and device
Technical Field
The present application relates to the field of computer communications, and in particular, to a method and an apparatus for forwarding a packet.
Background
EVPN (Ethernet Virtual Private Network) is a two-layer VPN technology, where BGP (Border Gateway Protocol) is used on the control plane to advertise routing information, and VXLAN (Virtual eXtensible local area Network) is used on the data plane to forward user packets.
In order to improve reliability, an EVPN networking manner of distributed aggregation as shown in fig. 1 may be adopted. In the networking shown in fig. 1, VTEP11(VXLAN Tunnel End Point) and VTEP13 may form a DR (Distributed aggregation) system, and VTEP11 and VTEP13 may be connected through an iplvllan Tunnel. A DR port 1(Distributed Relay interface) on VTEP11 and a DR port 2 on VTEP13 together form a DR group, VTEP11 is connected to an AGG 1(Virtual Machine) on VM11 through DR port 1, and VTEP13 is connected to an AGG 1(Virtual Machine) on VM11 through DR port 2.
Generally, when VTEP11 receives a non-unicast message sent by VM11 through DR port 1, VTEP11 may broadcast the non-unicast message. VTEP13 may receive the non-unicast message broadcast by VTEP11 through an IPL VXLAN tunnel. After receiving the non-unicast message, the VTEP13 also broadcasts the non-unicast message, so that the non-unicast message is forwarded back to the VM11 through the DR port 2, thereby creating a loop.
Disclosure of Invention
In view of this, the present application provides a message forwarding method and apparatus for preventing a loop.
Specifically, the method is realized through the following technical scheme:
according to a first aspect of the present application, a packet forwarding method is provided, where the method is applied to any one of the extensible virtual local area network tunnel endpoints VTEPs in a distributed aggregated DR system, and includes:
acquiring the state of a DR port on an opposite-end VTEP which belongs to the same DR system as the VTEP;
if the obtained state of the DR port on the VTEP at the opposite end is an UP state, searching a local DR port corresponding to the DR port on the VTEP at the opposite end; wherein, the DR port on the opposite terminal VTEP and the searched local DR port are connected with the same aggregation interface on the same user host;
setting all AC ports configured on the local DR port to forbid to forward non-unicast messages;
after receiving a VXLAN message sent by the opposite-end VTEP, if the message after the VXLAN message is de-encapsulated is a first non-unicast message, forwarding the first non-unicast message to other AC ports recorded in a first broadcast list except the AC port which is set to prohibit the forwarding of the non-unicast message; wherein the first broadcast list is a broadcast list corresponding to a VXLAN identifier of the VXLAN packet.
According to a second aspect of the present application, there is provided a packet forwarding apparatus, which is applied to any scalable virtual local area network tunnel endpoint VTEP in a distributed aggregated DR system, and includes:
the acquiring unit is used for acquiring the state of a DR port on an opposite-end VTEP which belongs to the same DR system as the VTEP;
a searching unit, configured to search a local DR port corresponding to the DR port on the VTEP at the opposite end if the obtained state of the DR port on the VTEP at the opposite end is an UP state; wherein, the DR port on the opposite terminal VTEP and the searched local DR port are connected with the same aggregation interface on the same user host;
a setting unit, configured to set all AC ports configured on the local DR port to prohibit forwarding a non-unicast message;
a first forwarding unit, configured to forward, after receiving the VXLAN packet sent by the VTEP at the opposite end, the first non-unicast packet to an AC port recorded in a first broadcast list except an AC port that is set to prohibit forwarding of the non-unicast packet if a packet decapsulated by the VXLAN packet is the first non-unicast packet; wherein the first broadcast list is a broadcast list corresponding to a VXLAN identifier of the VXLAN packet.
When a VTEP in a DR system determines that an opposite end DR port on the opposite end VTEP is in an UP state, the VTEP can search a local DR port which is connected with the opposite end DR port on the same VM through the same aggregation interface, and all AC ports configured on the local DR port are set to prohibit the forwarding of non-unicast messages.
When the opposite end VTEP receives the non-unicast message from the VM connected in common through the opposite end DR port and broadcasts the non-unicast message to the local end VTEP, and the local end VTEP broadcasts the non-unicast message, the local end VTEP does not forward the non-unicast message to the VM through the AC port on the local DR port associated with the opposite end DR port because the non-unicast message is not forwarded to the AC port which prohibits forwarding the non-unicast message, thereby preventing a loop.
Drawings
Fig. 1 is a schematic diagram of EVPN networking employing a distributed aggregation system according to an exemplary embodiment of the present application;
fig. 2a is a flowchart illustrating a message forwarding method according to an exemplary embodiment of the present application;
fig. 2b is a flowchart illustrating a message forwarding method according to another exemplary embodiment of the present application;
fig. 3 is a schematic diagram of another EVPN networking system using a distributed aggregation system according to an exemplary embodiment of the present application;
fig. 4 is a hardware architecture diagram of a VTEP where a message forwarding apparatus is located according to the present application;
fig. 5 is a block diagram of a message forwarding apparatus 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.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. 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 refers to and encompasses 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. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
Before introducing the message forwarding method of the present application, a DR port is first introduced.
The DR port refers to a two-layer aggregation interface connected to an external device. Typically the DR port is aggregated by physical ports on the VTEP in the DR system. In the DR system, DR ports connected to the same aggregation group on the external device belong to the same DR group. The VTEP records the correspondence between the DR port and the DR group to which the DR port belongs.
Taking fig. 1 as an example, it is assumed that physical ports port _101, port _102, and port _103 on VTEP11 are aggregated into a two-layer aggregation interface DR port 1, physical ports port _201, port _202, and port _203 on VTEP13 are aggregated into a two-layer aggregation interface DR port 2, and physical ports port _301, port _302, and port _303 on VM11 are aggregated into a common aggregation interface AGG 1.
VTEP11 is connected to AGG1 of VM11 through DR port 1, DR port 2 of VTEP13 is connected to AGG1 of VM11, and DR port 1 of VTEP11 and DR port 2 of VTEP13 form DR group 1.
In addition, an AC (access Circuit) port may be disposed in the DR port, and the AC port is associated with a VLAN and VXLAN.
For example, the configuration of the AC port may be as follows:
service-instance 10 (service instance 10);
encapsulation s-vid 10 (VLAN 10 associated with AC port 1);
xconnect VSI vpnb (VSI vpnb associated with AC Port 1, where vpnb is the identity of the VSI);
the AC port configuration indicates that, if the VLAN identifier carried by the message received from the DR port is VLAN10, the message will enter VSI vpnb for forwarding.
Referring to fig. 2a, fig. 2a is a flowchart illustrating a message forwarding method according to an exemplary embodiment of the present application. The method may be applied to any VTEP (herein referred to as the present VTEP for ease of description) in a DR system, and may include the steps described below.
Step 201: the VTEP acquires the state of a DR port on an opposite-end VTEP belonging to the same DR system as the VTEP.
The present VTEP may acquire the DR port state of one DR port on the opposite VTEP, or may acquire the DR port states of a plurality of DR ports, and is not particularly limited herein.
For convenience of description, the DR port on the peer VTEP will be referred to as a peer DR port hereinafter.
For convenience of description, an opposite-end VTEP belonging to the same DR system as the present VTEP will be referred to as an opposite-end VTEP.
The following description will take the DR port state of one peer DR port as an example, and the manner of obtaining the DR port states of multiple peers is similar, which is not described herein again.
The first method is as follows: the VTEP can receive the table item synchronization message sent by the opposite-end VTEP belonging to the same DR system with the VTEP through the IPL VXLAN tunnel, and acquire the state information of the opposite-end DR port carried in the table item synchronization message.
Specifically, the peer VTEP may periodically check whether the physical port bound to the peer DR port is normal, and when any one of the physical ports bound to the DR port is in the UP state, the DR port is in the UP state.
Generally, after learning forwarding entries such as MAC entries and ARP suppression entries of a message sent by a user host VM, an opposite VTEP may send a forwarding entry synchronization message to the VTEP to synchronize the forwarding entries learned by the opposite VTEP. At this time, the peer VTEP may carry the status of the peer DR port and the DR group identifier to which the peer DR port belongs in the forwarding table synchronization message, and then send the forwarding table synchronization message to the VTEP through the IPL VXLAN tunnel.
After receiving the forwarding table item synchronization message, the VTEP can obtain the state of the peer DR port carried by the forwarding table item synchronization message and the DR group identifier to which the peer DR port belongs through the IPL VXLAN tunnel.
The second method comprises the following steps: the VTEP and the opposite VTEP can periodically send DR port state notification messages to the opposite side to notify the DR port state of the VTEP.
Further, the present VTEP may periodically send a DR port status advertisement message for the local DR port to the peer VTEP. The peer VTEP may periodically send status advertisement messages for the peer DR port to the local VTEP. The VTEP receives a DR port state notification message sent by an opposite-end VTEP, and acquires the opposite-end DR port state carried by the DR port state notification message.
Specifically, the peer VTEP may periodically check whether the physical port bound to the peer DR port is normal, and when any one of the physical ports bound to the DR port is in the UP state, the DR port is in the UP state.
The peer VTEP may then send a DR port status advertisement message to the local VTEP via the IPL VXLAN tunnel. The status notification message of the DR port carries the status of the DR port of the opposite terminal and the DR group identification of the DR port of the opposite terminal.
After receiving the DR port state notification message, the VTEP can acquire the state of the opposite DR port carried by the DR port state notification message and the DR group identifier of the opposite DR port through the IPL VXLAN tunnel.
Similarly, the local VTEP may also periodically send a DR port status advertisement message for the local DR port to the peer VTEP.
Step 202: if the obtained DR port state is UP, the VTEP can search a local DR port corresponding to the DR port on the opposite-end VTEP; and the DR port on the opposite-end VTEP and the searched local DR port are connected with the same aggregation interface on the same user host.
Step 203: the VTEP sets all the searched AC ports configured on the local DR port to prohibit the forwarding of non-unicast messages.
When the data is realized, if the VTEP determines that the DR port of the opposite end is in an UP state according to the state of the DR port of the opposite end, the local DR port corresponding to the DR port of the opposite end is searched.
When searching for a local DR port corresponding to an opposite-end DR port, the VTEP may first obtain the entry synchronization message or a DR group identifier to which the opposite-end DR port belongs, which is carried in the DR port status notification message, and then search for the local DR port corresponding to the obtained DR group identifier according to a preset correspondence between the DR group identifier and the local DR port.
The VTEP can set all the AC ports configured on the searched local DR port to prohibit the forwarding of the non-unicast message.
Specifically, the VTEP may add a broadcast-prohibited forwarding flag to all AC ports configured on the found local DR port.
It should be noted that, when the VTEP obtains the state information of the plurality of peer DR ports and determines that the plurality of peer DR ports are all in the UP state, the VTEP may search for local DR ports corresponding to the plurality of peer DR ports, and add broadcast-prohibited forwarding flags to all AC ports configured on each of the searched local DR ports.
Step 204: after receiving a VXLAN message sent by the opposite-end VTEP, if the message after the VXLAN message is de-encapsulated is a first non-unicast message, forwarding the first non-unicast message to other AC ports recorded in a first broadcast list except the AC port which is set to prohibit the forwarding of the non-unicast message; wherein the first broadcast list is a broadcast list corresponding to a VXLAN identifier of the VXLAN packet.
The non-unicast message may include a Broadcast message, an unknown unicast message, or a multicast message, and these three types of messages may be collectively referred to as a BUM (Broadcast, unknown unicast, or multicast) message, and a protocol message that needs to be Broadcast, such as an ARP request message, and the like.
In implementation, after receiving the VXLAN message, the VTEP can first determine whether the VXLAN message is sent by an opposite VTEP in the same DR system.
The first method is as follows: the VTEP can determine whether the tunnel port receiving the VXLAN message is an IPL VXLAN tunnel port, and if so, the VTEP can determine that the VXLAN message is sent by an opposite end VTEP. And if not, determining that the VXLAN message is not sent by the opposite-end VTEP.
The second method comprises the following steps: the VTEP can determine that the VXLAN packet is sent by the VTEP at the opposite end if the source IP address is the IP address of the VTEP at the opposite end based on the source IP address of the VXLAN packet. And if the source IP address is not the IP address of the opposite-end VTEP, determining that the VXLAN message is not sent by the opposite-end VTEP.
In this embodiment, if the VXLAN packet is sent by a peer VTEP, and the decapsulated packet of the VXLAN packet is a non-unicast packet (herein, referred to as a first non-unicast packet), the VTEP may determine a broadcast list (herein, referred to as a first broadcast list) for broadcasting the first non-unicast packet.
When the VXLAN message is determined, the VTEP can read the VXLAN identification of the VXLAN message, and then the broadcast list associated with the VXLAN identification is used as a first broadcast list.
Then, the VTEP may forward the non-unicast packet to an AC port other than the AC port on which the forwarding of the non-unicast packet is prohibited, which is recorded in the first broadcast list.
And if the VXLAN message is not sent by the opposite-end VTEP and the message of the decapsulated VXLAN message is a non-unicast message, broadcasting according to a broadcast list corresponding to the VXLAN identifier of the VXLAN message.
In addition, in this embodiment of the present application, after receiving a non-unicast packet sent by a user host VM, the processing flow of the VTEP is as follows:
referring to fig. 2b, the packet forwarding process shown in fig. 2b includes the following steps.
Step 211: the VTEP may receive a second non-unicast message sent by the user host, and determine a second broadcast list corresponding to the second non-unicast message.
During implementation, the VTEP may search, on the DR port that receives the second non-unicast message from the user host, for an AC port corresponding to the VLAN id carried in the second non-unicast message, and use a broadcast list of the VSI associated with the AC port as a second broadcast list corresponding to the second non-unicast message.
Step 212: the VTEP can forward the non-unicast message through the VXLAN tunnel port, the iplvlxan tunnel port, and other AC ports except the AC port corresponding to the non-unicast message recorded in the second broadcast list.
And the AC port corresponding to the second non-unicast message is an AC port which is configured on the DR port for receiving the second non-unicast message and corresponds to the VLAN identifier of the second non-unicast message.
It should be noted that, when the VTEP at the opposite end receives the non-unicast packet sent by the user host VM, the processing flow is the same as in steps 211 to 212.
As can be seen from the above description, when the VTEP determines that the peer DR port on the peer VTEP is in an UP state, the VTEP may search for the local DR port corresponding to the peer DR port, and then set all the AC ports configured on the local DR port to prohibit broadcast forwarding, where the peer DR port and the searched local DR port are connected to the same aggregation interface on the same VM together.
When the opposite end VTEP receives the non-unicast message from the VM through the opposite end DR port and broadcasts the non-unicast message to the VTEP, the VTEP does not forward the non-unicast message to the AC port which is set with the prohibition of forwarding the non-unicast message when broadcasting the non-unicast message, so the VTEP does not forward the non-unicast message back to the VM through the AC port on the local DR port corresponding to the opposite end DR port, and a loop is prevented.
The following describes the message forwarding method in detail by taking the non-unicast message as an ARP request message as an example, and referring to fig. 3.
Referring to fig. 3, in the EVPN networking using the distributed aggregation system shown in fig. 3, VTEP31 and VTEP33 constitute a distributed aggregation system (DR system). VTEP31 and VTEP33 are connected by IPL VXLAN tunnels. VTEP31 and VTEP32 are connected by a VXLAN tunnel. VTEP33 and VTEP32 are connected by a VXLAN tunnel. VTEP32 is connected to VM32 through a user link.
It is assumed that VTEP31, VTEP32, and VTEP33 and their respective underlying VMs belong to the same VXLAN (i.e., VXLAN 100).
Assuming that the physical ports port _11, port _12, and port _13 on VTEP31 are aggregated into a two-layer aggregation interface DR port 1, the physical ports port _21, port _22, and port _23 on VTEP33 are aggregated into a two-layer aggregation interface DR port 2, and the physical ports port _31, port _32, and port _33 on VM31 are aggregated into a common aggregation interface AGG 1.
VTEP31 is connected to AGG1 of VM31 through DR port 1, DR port 2 of VTEP33 is connected to AGG1 of VM31, and DR port 1 of VTEP31 and DR port 2 of VTEP33 form DR group 1.
Further, it is assumed that AC port 1 and AC port 3 are also provided in DR port 1 of VTEP 31. At the same time, an AC port 2 corresponding to the AC port 1 and an AC port 4 corresponding to the AC port 3 are also disposed on the DR port 2 of the VTEP 33.
Where AC port 1 and AC port 2 associate VLAN10 with VSI vpnb. AC port 3 and AC port 4 associate VLAN11 with VSI vpnb. Meanwhile, VSI vpnb is configured to correspond to VXLAN 100.
At this point, there may be a record on VTEP31 as follows:
the corresponding relation between the DR port 1 and the DR group 1;
binding relationships between DR port 1 and physical ports port _11, port _12, and port _ 13.
The corresponding relation between the DR port 1 and the AC ports 1 and 3;
AC port 1:
service-instance 10 (service instance 10);
encapsulation s-vid 10 (VLAN 10 associated with AC port 1);
xconnect VSI vpnb (VSI vpnb associated with AC Port 1, where vpnb is the identity of the VSI);
AC port 3:
service-instance 11 (service instance 11);
encapsulation s-vid 11 (VLAN 11 associated with AC port 3);
xconnect VSI vpnb (VSI vpnb associated with AC port 3, where vpnb is the identity of the VSI);
VSI vpnb to VXLAN 100.
There may be records on VTEP2 as follows:
the corresponding relation between the DR port 2 and the DR group 1;
binding relationships between DR port 2 and physical ports port _21, port _22, and port _ 23.
The corresponding relation between the DR port 2 and the AC ports 2 and 4;
AC port 2:
service-instance 10 (service instance 10);
encapsulation s-vid 10 (VLAN 10 associated with AC port 2);
xconnect VSI vpnb (VSI vpnb associated with AC Port 2, where vpnb is the identity of the VSI);
AC port 4:
service-instance 11 (service instance 11);
encapsulation s-vid 11 (VLAN 11 associated with AC port 4);
xconnect VSI vpnb (VSI vpnb associated with AC port 4, where vpnb is the identity of the VSI);
VSI vpnb to VXLAN 100.
After the configurations on VTEP31 and VTEP33 are introduced, the message forwarding method proposed in the present application will be described in detail below in terms of both broadcast forwarding flag setting prohibition and forwarding of ARP request messages.
1) Prohibit broadcast forwarding flag setting
Step 301: VTEP33 may obtain status information for the DR port on VTEP 31.
The VTEP33 acquires the DR port state information on the VTEP31, and the information may be the DR port state information of one DR port or the DR port state information of a plurality of DR ports, and is not particularly limited herein.
Here, the description will be given taking an example in which the VTEP33 acquires status information of the DR port 1 on the VTEP 31. Certainly, in practical applications, there are other DR ports on VTEP31 and VTEP33, for example, there are DR port 3 on VTEP31 and DR port 4 on VTEP33, and DR port 3 and DR port 4 belong to DR group 2, so VTEP33 obtains status information of DR port 3, and the method of setting broadcast forwarding prohibition for the AC port under DR port 4 is also similar to the method using DR port 1 as an example, and is not described here again.
The first method is as follows: VTEP31 may notify VTEP33 of status information of DR port 1 via a forwarding table synchronization message.
Specifically, VTEP31 may periodically check whether physical ports port _11, port _12, and port _13 bound by DR port 1 are normal, and if any one of physical ports port _11, port _12, and port _13 is in the UP state, DR port 1 is in the UP state.
Generally, after VTEP31 learns forwarding entries such as MAC entries and ARP suppression entries of messages sent by the user host VM, VTEP31 may send a forwarding entry synchronization message to VTEP33 to synchronize the forwarding entries learned by VTEP 31. At this time, VTEP31 may carry the status of DR port 1 and the DR group identifier (DR group 1) to which DR port 1 belongs in the forwarding table synchronization message, and then send the forwarding table synchronization message to VTEP33 through the IPL VXLAN tunnel.
After receiving the forwarding table synchronization message, VTEP33 may obtain the status of DR port 1 carried by the forwarding table synchronization message and the DR group identifier (i.e., DR group 1) to which DR port 1 belongs.
The second method comprises the following steps: VTEP31 and VTEP33 may periodically advertise their own DR port status to each other.
Specifically, VTEP31 may periodically check whether physical ports port _11, port _12, and port _13 bound by DR port 1 are normal, and if any one of physical ports port _11, port _12, and port _13 is in the UP state, DR port 1 is in the UP state.
VTEP31 may then send a DR port status advertisement message for DR port 1 to VTEP 33. The status notification message carries the status of the DR port 1 and the DR group id (i.e. DR group 1) to which the DR port 1 belongs.
After receiving the DR port status notification message, the VTEP33 may obtain the status of the DR port 1 carried in the DR port status notification message and the DR group identifier (i.e., DR group 1) to which the DR port 1 belongs.
Similarly, VTEP33 may also periodically send a DR port status advertisement message for DR port 2 to VTEP 31.
Step 302: after determining that the DR port 1 is in an UP state according to the state of the DR port 1, the VTEP33 may search for a local DR port corresponding to the DR port 1, and set all AC ports configured on the searched local DR port to prohibit broadcast forwarding.
Specifically, the VTEP33 may search the local DR port (i.e., DR port 2) corresponding to the obtained DR group 1 according to the preset correspondence between the DR group identifier and the DR port.
VTEP33 may then add the prohibit broadcast forwarding flag for all AC ports configured on DR port 2 (i.e., AC port 2 and AC port 4).
It should be noted that, when the VTEP33 obtains the states of the plurality of peer DR ports and determines that the plurality of peer DR ports are all in the UP state, the VTEP33 may search local DR ports respectively associated with the plurality of peer DR ports, and add broadcast forwarding prohibition flags to all AC ports configured on each of the searched local DR ports.
For example, there is DR port 3 in VTEP31, DR port 4 in VTEP33, and DR port 3 and DR port 4 belong to DR group 2 (not shown in FIG. 3). VTEP31 also needs to add a no broadcast forwarding flag for all AC ports configured on DR port 3.
2) Forwarding of ARP request messages
The VM31 sends an ARP request message to the DR system via the AGG 1. Assume that the VLAN TAG carried by the ARP request message is TAG 10.
During the sending process, VM31 may hash one link among the links locally connected to VTEP31 and VTEP32 to forward the ARP request message. Assuming that the hashed link is a link between the local and VTEP31, VM31 sends the ARP request message to VTEP31 through the hashed link.
Step 401, after receiving the ARP request message, VTEP31 may determine the VSI to which the ARP request message belongs.
Specifically, assume that VTEP31 receives an ARP request message sent by VM31 through physical port _ 11. The VTEP31 may determine the DR port (i.e., DR port 1) bound by the physical ingress port _11 of the ARP request packet according to a preset binding relationship between the DR port and the physical port.
Then, VTEP31 may configure AC port 1 and AC port 2 on DR port 1, and search for the AC port (i.e., AC port 1) corresponding to the VLAN id (i.e., tag 10) carried in the ARP request packet. VTEP31 may then determine the VSI associated with AC port 1, i.e., VSI vpnb, based on the configuration of AC port 1.
Step 402: VTEP31 may search for an ARP suppression entry matching the determined VSIvpnb and the IP address requested by the ARP request message from the locally recorded ARP suppression entries.
The ARP suppression entry may be as shown in table 1:
IP address of request MAC address VSI AC port
TABLE 1
Step 403: if an ARP suppression entry matching the determined VSI vpnb and the IP address requested by the ARP request message is found, VTEP31 may return the MAC address in the ARP suppression entry to VM 31.
Step 404: if an ARP suppression entry matching the determined VSI vpnb and the IP address requested by the ARP request message is not found, VTEP31 may broadcast the ARP request message.
During broadcasting, the VTEP31 forwards the ARP request packet through the VXLAN tunnel port, IPL VXLAN tunnel port, and other AC ports except the AC port corresponding to the ARP request packet recorded in the broadcast list. And the broadcast list is the broadcast list associated with the determined VSI.
The AC corresponding to the ARP request message is the AC port (i.e., AC port 1) configured on the DR port (i.e., DR port 1) receiving the ARP request message and corresponding to the VLAN identifier (VLAN 10) of the ARP request message.
For example, in this example, it is assumed that the broadcast list associated with VSI vpnb is referred to as broadcast list 1, and ports recorded in broadcast list 1 include a VXLAN tunnel port and an IPL VXLAN tunnel port connected to VTEP31 from VTEP32, and AC port 1 and AC port 3 disposed in DR port 1.
1) VTEP31 does not forward the ARP request packet through AC port 1(AC port corresponding to ARP request packet), and VTEP31 forwards the ARP request packet through AC port 3 provided on DR port 1.
The other AC ports include an AC port provided in another DR port of VTEP31, an AC port connected to a VM suspended solely in VTEP31, and the like.
For example, a DR port 3 is present in VTEP31, a DR port 4 is present in VTEP33, and DR port 3 and DR port 4 belong to DR group 2 (not shown in FIG. 3). VTEP31 also needs to forward the ARP request message to all AC ports configured on DR port 3.
For another example, VM32 is hung on VTEP31, and an AC port 5 (not shown in fig. 3) is configured on an interface of VTEP31 connected to VM32, and then VTEP31 forwards the ARP request message through AC port 5.
2) VTEP31 forwards the ARP request message to VTEP32 through the VXLAN tunnel portal.
Specifically, VTEP31 may perform VXLAN encapsulation on the ARP packet to generate a VXLAN packet, and in this example, since the VSI corresponding to the ARP packet is VSI vpnb and VSI vpn corresponds to VXLAN100, the VXLAN of the VXLAN packet is identified as VXLAN 100.
Then, VTEP31 may send the VXLAN packet encapsulating the ARP packet to VTEP32 through a VXLAN tunnel portal.
3) VTEP31 forwards the ARP request message to VTEP33 through the IPL VXLAN tunnel portal.
Specifically, VTEP31 may perform VXLAN encapsulation on the ARP packet to generate a VXLAN packet. In this example, since the VSI corresponding to the ARP message is VSI vpnb and VSI vpn corresponds to VXLAN100, the VXLAN identifier of the VXLAN message is VXLAN 100.
Next, VTEP31 may send the VXLAN packet encapsulating the ARP packet to VTEP33 through the IPL VXLAN tunnel port.
Step 405: after receiving the VXLAN message, VTEP33 may determine whether the VXLAN message is sent by a peer VTEP (i.e., VTEP31) in the same DR system.
The first method is as follows: VTEP33 may determine whether the tunnel port receiving the VXLAN packet is an IPL VXLAN tunnel port, and if so, VTEP33 may determine that the VXLAN packet is sent by VTEP 31. If not, the VXLAN message is determined not to be sent by VTEP 31.
The second method comprises the following steps: the VTEP33 may determine that the VXLAN message was sent by VTEP31 if the source IP address is the IP address of VTEP31 based on the source IP address of the VXLAN message. And if the source IP address is not the IP address of the VTEP31, determining that the VXLAN message is not sent by the VTEP 31.
Step 406: if the VXLAN message is sent by VTEP31 and the ethernet message decapsulated by the VXLAN message is an ARP request message, VTEP33 may search whether an ARP suppression entry matching the ARP request message exists.
In implementation, VTEP33 may look up, in a local ARP suppression table, whether there is an ARP suppression entry matching the VSI (i.e., VSI vpnb) corresponding to the VXLAN identifier of the VXLAN message (i.e., VXLAN100) and the IP address requested by the ARP request message.
In this example, since VTEP31 and VTEP33 belong to the same DR system, the forwarding table entries configured on VTEP31 and VTEP33 are the same. No matching ARP suppression entry is found on VTEP31, so there is no matching ARP suppression entry on VTEP 33.
Step 407: and if the matched ARP suppression table entry does not exist, broadcasting the ARP request message.
In implementation, VTEP33 may obtain a broadcast list that broadcasts the ARP request message.
Specifically, VTEP33 may read the VXLAN identifier of the VXLAN message (i.e., VXLAN100), and then use the broadcast list corresponding to VXLAN100 as the broadcast list for broadcasting the ARP request message, which is referred to as broadcast list 2 here.
Then, VTEP33 may forward the ARP request message through the other AC ports recorded in broadcast list 2 except the AC port to which the broadcast prohibited forwarding flag is set.
For example, the ports recorded in the playlist 2 include a VXLAN tunnel port connected between VTEP33 and VTEP32, an IPL VXLAN tunnel port, an AC port 2 and an AC port 4 on DR port 2, and an AC port (not shown in fig. 3) for connecting a VM that is suspended locally.
Since the broadcast prohibit forwarding flags are added to AC port 2 and AC port 4, VTEP33 does not forward the ARP request message through AC port 2 and AC port 4.
VTEP33 may broadcast an AC port recorded in list 2 with a VM for connecting to a single local hook.
In the conventional EVPN networking, since there is horizontal division of VXLAN tunnels, that is, a message received from one VXLAN tunnel is not forwarded through another VXLAN tunnel, in this example, since VTEP33 receives a VXLAN message encapsulating an ARP request message from an IPL VXLAN tunnel, VTEP33 does not forward the ARP request message to a VXLAN tunnel port connected between VTEP33 and VTEP32 recorded in broadcast list 2. The ARP request message will not be forwarded to the source port that receives the ARP request message, i.e., the IPL VXLAN tunnel port.
In the embodiment of the present application, after determining that DR port 1 is in an UP state, VTEP33 sets all ACs configured on DR port 2 associated with DR port 1 to prohibit broadcast forwarding, so that VTEP31 forwards the received ARP request packet from VM31 to VTEP33, and when VTEP33 broadcasts the ARP request packet, since the ARP request packet is not forwarded through AC port 2, the ARP request packet is not sent back to VM31, so that a loop is not generated.
Referring to fig. 4, the present application further provides a hardware architecture diagram of a VTEP where a packet forwarding device is located, where the network device includes: a communication interface 401, a processor 402, a memory 403, and a bus 404; wherein, the communication interface 401, the processor 402 and the memory 403 complete the communication with each other through the bus 404.
The communication interface 401 is used for communicating with a peer VTEP, a far-end VTEP, and a VM in the same DR system. The processor 402 may be a CPU, the memory 403 may be a non-volatile memory (non-volatile memory), and the memory 403 stores logic instructions for message forwarding, and the processor 402 may execute the logic instructions for message forwarding stored in the memory 403 to implement the message forwarding function.
Up to this point, the description of the hardware configuration shown in fig. 4 is completed.
Referring to fig. 5, fig. 5 is a block diagram of a message forwarding apparatus according to an exemplary embodiment of the present application. The device can be applied to any VTEP in a DR system and can comprise the following units.
An obtaining unit 501, configured to obtain a status of a DR port on an opposite VTEP in the same DR system as the VTEP;
a searching unit 502, configured to search a local DR port corresponding to the DR port on the VTEP at the opposite end if the obtained state of the DR port on the VTEP at the opposite end is an UP state; wherein, the DR port on the opposite terminal VTEP and the searched local DR port are connected with the same aggregation interface on the same user host;
a setting unit 503, configured to set all AC ports configured on the local DR port to prohibit forwarding a non-unicast packet;
a first forwarding unit 504, configured to forward, after receiving the VXLAN packet sent by the VTEP at the opposite end, the first non-unicast packet to another AC port recorded in the first broadcast list except the AC port on which forwarding of the non-unicast packet is prohibited, if the packet decapsulated by the VXLAN packet is the first non-unicast packet; wherein the first broadcast list is a broadcast list corresponding to a VXLAN identifier of the VXLAN packet.
Optionally, the obtaining unit 501 is specifically configured to receive a table entry synchronization message sent by an opposite-end VTEP that belongs to the same DR system as the VTEP, and obtain a state of a DR port on the opposite-end VTEP carried in the table entry synchronization message; or, sending a DR port state notification message aiming at the local DR port state to an opposite end VTEP which belongs to the same DR system as the VTEP; and receiving a DR port state notification message sent by the opposite-end VTEP, and acquiring the state of the DR port on the opposite-end VTEP carried by the DR port state notification message.
Optionally, the table synchronization message and the DR port status notification message also carry a DR group identifier to which a DR port on the VTEP of the opposite end belongs;
the searching unit 502 is specifically configured to obtain a DR group identifier to which a DR port on the VTEP at the opposite end belongs, where the DR group identifier is carried in the table item synchronization message or the DR port status notification message; and searching a local DR port corresponding to the obtained DR group identification according to a preset corresponding relation between the DR group identification and the local DR port.
Optionally, the first non-unicast message is an ARP request message;
the first forwarding unit 504 is specifically configured to, when an ARP suppression entry matching the ARP request packet is not found, forward the ARP request packet to an AC port recorded in the first broadcast list, except an AC port that is set to prohibit forwarding a non-unicast packet.
Optionally, the apparatus further comprises:
a receiving unit 505, configured to receive a second non-unicast message sent by a subscriber host, and determine a second broadcast list for broadcasting the second non-unicast message;
a second forwarding unit 506, configured to forward the second non-unicast packet through the VXLAN tunnel port, the IPL VXLAN tunnel port, and other AC ports except the AC port corresponding to the second non-unicast packet recorded in the second broadcast list;
and the AC port corresponding to the second non-unicast message is an AC port which is configured on the DR port for receiving the second non-unicast message and corresponds to the VLAN identifier of the second non-unicast message.
Optionally, the receiving unit 505 is specifically configured to search, on the DR port that receives the second non-unicast packet, an AC port corresponding to the VLAN identifier carried in the second non-unicast packet; and taking the broadcast list of the VSI associated with the searched AC port as a second broadcast list.
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 (12)

1. A message forwarding method is applied to any extensible virtual local area network tunnel endpoint (VTEP) in a distributed aggregation DR system, and comprises the following steps:
acquiring the state of a DR port on an opposite-end VTEP which belongs to the same DR system as the VTEP;
if the obtained state of the DR port on the VTEP at the opposite end is an UP state, searching a local DR port corresponding to the DR port on the VTEP at the opposite end; wherein, the DR port on the opposite terminal VTEP and the searched local DR port are connected with the same aggregation interface on the same user host;
setting all AC ports configured on the local DR port to forbid to forward non-unicast messages;
after receiving a VXLAN message sent by the opposite-end VTEP, if the message after the VXLAN message is de-encapsulated is a first non-unicast message, forwarding the first non-unicast message to other AC ports recorded in a first broadcast list except the AC port which is set to prohibit the forwarding of the non-unicast message; the first broadcast list is a broadcast list corresponding to a VXLAN identifier of the VXLAN message;
the searching for the local DR port corresponding to the DR port on the VTEP of the opposite end comprises:
obtaining a DR group identifier of a DR port on the opposite-end VTEP;
and searching a local DR port corresponding to the obtained DR group identification according to a preset corresponding relation between the DR group identification and the local DR port.
2. The method according to claim 1, wherein the obtaining the status of the DR port on the VTEP at the opposite end belonging to the same DR system as the VTEP comprises:
receiving a table item synchronization message sent by an opposite-end VTEP belonging to the same DR system as the VTEP, and acquiring the state of a DR port on the opposite-end VTEP carried in the table item synchronization message;
alternatively, the first and second electrodes may be,
sending a DR port state notification message aiming at the local DR port state to an opposite end VTEP which belongs to the same DR system as the VTEP;
and receiving a DR port state notification message sent by the opposite-end VTEP, and acquiring the state of the DR port on the opposite-end VTEP carried by the DR port state notification message.
3. The method of claim 2, wherein the table entry synchronization message and the received DR port status advertisement message further carry a DR group id to which a DR port on the VTEP on the opposite end belongs;
the acquiring the DR group identifier to which the DR port belongs on the VTEP at the opposite end includes:
and acquiring the table item synchronization message or the DR port state notification message which is carried in the received DR port state notification message and to which the DR port on the opposite-end VTEP belongs.
4. The method of claim 1, wherein the first non-unicast message is an ARP request message;
the forwarding the first non-unicast message to other AC ports recorded in the first broadcast list except the AC port on which the forwarding of the non-unicast message is prohibited is performed, including:
and when the ARP suppression table entry matched with the ARP request message is not found, forwarding the ARP request message to other AC ports recorded in the first broadcast list except the AC port which is set to prohibit the forwarding of the non-unicast message.
5. The method of claim 1, further comprising:
receiving a second non-unicast message sent by a user host, and determining a second broadcast list for broadcasting the second non-unicast message;
forwarding the second non-unicast message through the VXLAN tunnel port, the IPL VXLAN tunnel port and other AC ports except the AC port corresponding to the second non-unicast message recorded in the second broadcast list;
and the AC port corresponding to the second non-unicast message is an AC port which is configured on the DR port for receiving the second non-unicast message and corresponds to the VLAN identifier of the second non-unicast message.
6. The method of claim 5, wherein determining the second broadcast list for broadcasting the second non-unicast message comprises:
searching an AC port corresponding to the VLAN identification carried by the second non-unicast message on the DR port receiving the second non-unicast message;
and taking the broadcast list of the VSI associated with the searched AC port as a second broadcast list.
7. A message forwarding apparatus applied to any extensible virtual local area network tunnel endpoint (VTEP) in a distributed aggregation DR system, comprising:
the acquiring unit is used for acquiring the state of a DR port on an opposite-end VTEP which belongs to the same DR system as the VTEP;
a searching unit, configured to search a local DR port corresponding to the DR port on the VTEP at the opposite end if the obtained state of the DR port on the VTEP at the opposite end is an UP state; wherein, the DR port on the opposite terminal VTEP and the searched local DR port are connected with the same aggregation interface on the same user host;
a setting unit, configured to set all AC ports configured on the local DR port to prohibit forwarding a non-unicast message;
a first forwarding unit, configured to forward, after receiving the VXLAN packet sent by the VTEP at the opposite end, the first non-unicast packet to an AC port recorded in a first broadcast list except an AC port that is set to prohibit forwarding of the non-unicast packet if a packet decapsulated by the VXLAN packet is the first non-unicast packet; the first broadcast list is a broadcast list corresponding to a VXLAN identifier of the VXLAN message;
the search unit is used for acquiring a DR group identifier to which a DR port on the opposite end VTEP belongs when searching a local DR port corresponding to the DR port on the opposite end VTEP; and searching a local DR port corresponding to the obtained DR group identification according to a preset corresponding relation between the DR group identification and the local DR port.
8. The apparatus according to claim 7, wherein the obtaining unit is specifically configured to receive an entry synchronization message sent by a VTEP that is a peer of the same DR system as the VTEP, and obtain a status of a DR port on the VTEP on the peer, which is carried in the entry synchronization message; or, sending a DR port state notification message aiming at the local DR port state to an opposite end VTEP which belongs to the same DR system as the VTEP; and receiving a DR port state notification message sent by the opposite-end VTEP, and acquiring the state of the DR port on the opposite-end VTEP carried by the DR port state notification message.
9. The apparatus of claim 8, wherein the table entry synchronization message and the received DR port status advertisement message further carry a DR group id to which a DR port belongs on the VTEP on the opposite end;
the search unit is specifically configured to obtain the table synchronization message or the DR group identifier to which the DR port on the VTEP at the opposite end belongs, which is carried in the received DR port status notification message.
10. The apparatus of claim 7, wherein the first non-unicast message is an ARP request message;
the first forwarding unit is specifically configured to, when an ARP suppression entry matching the ARP request packet is not found, forward the ARP request packet to an AC port recorded in the first broadcast list, except for an AC port that is set to prohibit forwarding of a non-unicast packet.
11. The apparatus of claim 7, further comprising:
a receiving unit, configured to receive a second non-unicast packet sent by a user host, and determine a second broadcast list for broadcasting the second non-unicast packet;
a second forwarding unit, configured to forward the second non-unicast packet through the VXLAN tunnel port, the IPL VXLAN tunnel port, and other AC ports except the AC port corresponding to the second non-unicast packet recorded in the second broadcast list;
and the AC port corresponding to the second non-unicast message is an AC port which is configured on the DR port for receiving the second non-unicast message and corresponds to the VLAN identifier of the second non-unicast message.
12. The apparatus according to claim 11, wherein the receiving unit is specifically configured to search, on a DR port that receives the second non-unicast packet, an AC port corresponding to a VLAN id carried in the second non-unicast packet; and taking the broadcast list of the VSI associated with the searched AC port as a second broadcast list.
CN201810116549.5A 2018-02-06 2018-02-06 Message forwarding method and device Active CN108306806B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810116549.5A CN108306806B (en) 2018-02-06 2018-02-06 Message forwarding method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810116549.5A CN108306806B (en) 2018-02-06 2018-02-06 Message forwarding method and device

Publications (2)

Publication Number Publication Date
CN108306806A CN108306806A (en) 2018-07-20
CN108306806B true CN108306806B (en) 2021-10-29

Family

ID=62864172

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810116549.5A Active CN108306806B (en) 2018-02-06 2018-02-06 Message forwarding method and device

Country Status (1)

Country Link
CN (1) CN108306806B (en)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109462515A (en) * 2018-09-11 2019-03-12 锐捷网络股份有限公司 Loop circuit processing method, the network equipment, MLAG networking and storage medium
CN109067634B (en) * 2018-09-28 2021-02-05 新华三技术有限公司 Forwarding table item creating method and device
CN111698156B (en) * 2020-04-30 2022-08-30 新华三技术有限公司 Data message forwarding method and device
CN113037565B (en) * 2021-03-29 2022-04-01 新华三信息安全技术有限公司 Message processing method and device
CN113364662B (en) * 2021-06-30 2023-03-24 北京天融信网络安全技术有限公司 Message processing method and device, storage medium and electronic equipment
CN114253979B (en) * 2021-12-23 2023-10-03 北京百度网讯科技有限公司 Message processing method and device and electronic equipment

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107547402A (en) * 2017-07-19 2018-01-05 新华三技术有限公司 A kind of forwarding table generation method and device

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10116464B2 (en) * 2015-03-18 2018-10-30 Juniper Networks, Inc. EVPN inter-subnet multicast forwarding
CN106059886B (en) * 2016-06-27 2020-10-13 新华三技术有限公司 Message forwarding method and device
CN106878065B (en) * 2017-01-18 2021-06-11 新华三技术有限公司 Configuration method and device of distributed aggregation system
CN107547398B (en) * 2017-05-23 2020-04-17 新华三技术有限公司 Message forwarding method, device and equipment
CN107547370B (en) * 2017-09-25 2020-05-12 新华三技术有限公司 Flow forwarding method, device and system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107547402A (en) * 2017-07-19 2018-01-05 新华三技术有限公司 A kind of forwarding table generation method and device

Also Published As

Publication number Publication date
CN108306806A (en) 2018-07-20

Similar Documents

Publication Publication Date Title
CN108306806B (en) Message forwarding method and device
US10693766B2 (en) Engines to prune overlay network traffic
CN107819677B (en) Message forwarding method and device
CN107547402B (en) Forwarding table generation method and device
US10333836B2 (en) Convergence for EVPN multi-homed networks
CN108259303B (en) Message forwarding method and device
EP2907265B1 (en) Ip multicast service join process for mpls-based virtual private cloud networking
US10193707B2 (en) Packet transmission method and apparatus
EP3065342A1 (en) Update of mac routes in evpn single-active topology
CN108259304B (en) Forwarding table item synchronization method and device
US9300524B2 (en) Message forwarding between geographically dispersed network sites
WO2016101646A1 (en) Access method and apparatus for ethernet virtual network
CN108964940B (en) Message sending method and device and storage medium
CN109729012B (en) Unicast message transmission method and device
WO2014057403A1 (en) Ip multicast service leave process for mpls-based virtual private cloud networking
WO2013029440A1 (en) Method and apparatus for implementing layer-2 interconnection of data centers
CN107645431B (en) Message forwarding method and device
US20190215191A1 (en) Deployment Of Virtual Extensible Local Area Network
CN105187311A (en) Message forwarding method and message forwarding device
CN114095460B (en) Message broadcasting method and device
CN106992918B (en) Message forwarding method and device
CN108306825B (en) Equivalent forwarding table item generation method and VTEP device
CN108183858B (en) Route introducing method and device
CN113938405B (en) Data processing method and device
CN107911495B (en) MAC address synchronization method and VTEP

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