CN109194560B - Multicast method and VTEP - Google Patents
Multicast method and VTEP Download PDFInfo
- Publication number
- CN109194560B CN109194560B CN201810995123.1A CN201810995123A CN109194560B CN 109194560 B CN109194560 B CN 109194560B CN 201810995123 A CN201810995123 A CN 201810995123A CN 109194560 B CN109194560 B CN 109194560B
- Authority
- CN
- China
- Prior art keywords
- vtep
- multicast
- local
- route
- type
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/16—Multipoint routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/54—Organization of routing tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a multicast method and a VTEP, relates to the field of communication, and can improve multicast forwarding efficiency. The method comprises the following steps: the local end VTEP receives the 3 type route and the first 2 type route sent by the remote end VTEP, creates a BUM forwarding table and a multicast forwarding table, and adds the IP address of the remote end VTEP and the tunnel information corresponding to the copy table of the BUM forwarding table into the copy table of the multicast forwarding table. If the IP multicast message received by the local terminal VTEP carries the IP address of the appointed multicast group, the local terminal VTEP forwards the IP multicast message to the remote terminal VTEP according to the replication table of the multicast forwarding table. Wherein, the 3 kinds of routes include IP address of far-end VTEP, the first 2 kinds of routes include: the VNI, the local VLAN identification and the IP address of the designated multicast group of the remote VTEP, and the first type 2 route is used for the remote VTEP to request to join the designated multicast group.
Description
Technical Field
The present application relates to the field of communications, and in particular, to a multicast method and a VTEP.
Background
A Virtual eXtensible Local Area Network (VXLAN), such as an Ethernet Virtual Private Network (EVPN), is a widely applied Virtual Private Network (VPN) technology, and can achieve the purpose of enabling a layer 2 message to penetrate a layer 3 IP Network by using a manner of encapsulating a User Datagram Protocol (UDP) header and a VXLAN header from original data, such as Media Access Control (MAC) layer data.
The existing EVPN usually uses the same forwarding method to forward all traffic without distinction, such as Broadcast, Unknown unicast, and Multicast (BUM) traffic. Specifically, a BUM forwarding table is established on a network according to BUM members learned by 3 types of routes of a Border Gateway Protocol (BGP) EVPN, and BUM traffic is forwarded to all members in the BUM forwarding table. The BUM forwarding table may include at least one VXLAN Tunnel End Point (VTEP for short).
However, in practical applications, for a specified multicast group, only part of VTEPs generally need to receive multicast traffic, and if multicast forwarding is performed through the BUM forwarding table, a VTEP that does not need to receive the specified group traffic still receives the multicast traffic, which wastes network bandwidth and reduces network operating efficiency.
Disclosure of Invention
The application provides a multicast method and a VTEP, which can avoid forwarding the message to the VTEP which does not need to receive the message in the appointed multicast group, thereby improving the efficiency of forwarding the message in the appointed multicast group.
In order to achieve the purpose, the technical scheme is as follows:
in a first aspect, the present application provides a multicast method, which may include: a local virtual extensible local area network (VXLAN) tunnel termination end point VTEP receives a 3-type route sent by a remote VTEP, and creates a target broadcast, unknown unicast and multicast BUM forwarding table; wherein the class 3 route includes the IP address of the remote VTEP. The local VTEP receives the first type 2 route sent by the remote VTEP, creates a corresponding multicast forwarding table, and adds the IP address of the remote VTEP and the tunnel information corresponding to the copy table of the BUM forwarding table into the copy table of the multicast forwarding table; wherein, the first type 2 route is used for the remote VTEP to request to join the appointed multicast group, and the first type 2 route comprises: the VXLAN of the remote VTEP identifies the VNI, a local Virtual Local Area Network (VLAN) identification, and an IP address specifying a multicast group. If the IP multicast message received by the local terminal VTEP carries the IP address of the appointed multicast group, the local terminal VTEP forwards the IP multicast message to the remote terminal VTEP according to the replication table of the multicast forwarding table.
In a second aspect, the present application provides a VTEP, the apparatus comprising: the device comprises a receiving module and a forwarding module. The receiving module is used for receiving the 3 types of routes sent by the remote VTEP and creating a target broadcast, unknown unicast and multicast BUM forwarding table; wherein the class 3 route includes the IP address of the remote VTEP. The receiving module is further used for receiving the first type 2 route sent by the far-end VTEP, creating a corresponding multicast forwarding table, and adding the IP address of the far-end VTEP and tunnel information corresponding to the copy table of the BUM forwarding table into the copy table of the multicast forwarding table; wherein, the first type 2 route is used for the remote VTEP to request to join the appointed multicast group, and the first type 2 route comprises: the VXLAN of the remote VTEP identifies the VNI, the local virtual local area network VLAN identification, and the IP address specifying the multicast group. And the forwarding module is used for forwarding the IP multicast message to the remote VTEP according to the replication table of the multicast forwarding table if the IP multicast message received by the local VTEP carries the IP address of the specified multicast group.
In a third aspect, the present application provides a VTEP comprising: a processor, a transceiver, and a memory. Wherein the memory is used to store one or more programs. The one or more programs include computer executable instructions which, when executed by the processor, cause the VTEP to perform the multicast method of the first aspect and any of its various alternative implementations.
In a fourth aspect, the present application provides a computer-readable storage medium, in which instructions are stored, and when the instructions are executed by a computer, the computer executes the multicast method described in any one of the first aspect and various optional implementations thereof.
In a fifth aspect, the present application provides a communication system comprising a plurality of VTEPs according to the second aspect and any of its various alternative implementations, or a plurality of VTEPs according to the third aspect and any of its various alternative implementations.
According to the multicast method and the VTEP, a VXLAN multicast forwarding table containing the IP address of the remote VTEP and the IP address of the specified multicast group can be established according to the 3-type route and the first 2-type route sent by the remote VTEP, when the IP multicast message received by the local VTEP carries the IP address of the specified multicast group, the local VTEP can forward the IP multicast message to the remote VTEP instead of forwarding to all VTEPs except the local VTEP in the specified multicast group, the situation that the IP multicast message is forwarded to the VTEP which does not need to receive the IP multicast message is avoided, the number of invalid IP multicast messages forwarded in the multicast group can be reduced, the invalid occupation of network bandwidth is reduced, and the forwarding efficiency of the whole network is improved.
Drawings
Fig. 1 is a schematic structural diagram of a multicast method and a communication system to which a VTEP is applied according to an embodiment of the present application;
fig. 2 is a first flowchart of a multicast method according to an embodiment of the present application;
fig. 3 is a second flowchart of a multicast method according to an embodiment of the present application;
fig. 4 is a third schematic flowchart of a multicast method according to an embodiment of the present application;
fig. 5 is a fourth flowchart of a multicast method according to the embodiment of the present application;
fig. 6 is a fifth flowchart of a multicast method according to an embodiment of the present application;
FIG. 7 is a first schematic structural diagram of a VTEP provided in an embodiment of the present application;
FIG. 8 is a second schematic structural diagram of a VTEP provided in an embodiment of the present application;
fig. 9 is a schematic structural diagram three of a VTEP provided in an embodiment of the present application.
Detailed Description
The multicast method and VTEP provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone.
The terms "first" and "second" and the like in the description and drawings of the present application are used for distinguishing different objects or for distinguishing different processes for the same object, and are not used for describing a specific order of the objects.
Furthermore, the terms "including" and "having," and any variations thereof, as referred to in the description of the present application, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.
In the description of the present application, the meaning of "a plurality" means two or more unless otherwise specified.
The multicast method provided by the embodiment of the present application may be applied to the communication system shown in fig. 1. As shown in fig. 1, the communication system may include: a network cloud, and at least two VTEPs, such as VTEP1 and VTEP2, connected via the network cloud, such as via core devices (not shown in fig. 1) in the network cloud. Each VTEP is connected to a local Virtual Local Area Network (VLAN) (not shown in fig. 1). The VTEP1 may include a BGP module 11 and a multicast forwarding module 12, where the BGP module 11 is mainly configured to receive a 3-type route and a 2-type route sent by other VTEPs, or send a 3-type route and a 2-type route of its own to other VTEPs, for example, the 3-type route and the 2-type route are carried in an Internet Group Management Protocol (IGMP) message for transceiving. The multicast forwarding module 12 is mainly configured to forward an IP multicast packet received by the VTEP1, or receive an IP multicast packet forwarded by another VTEP, for example, forward the IP multicast packet between VTEP1 and another VTEP in the form of unicast, multicast, or unknown broadcast through a network cloud.
VTEP2 may include an IGMP module 13 and a BGP module 14. The IGMP module 13 is mainly used to transmit signaling between the VTEP2 and a terminal in the local VLAN network connected to the VTEP2, such as a personal computer and a smart phone, for example, to receive an IGMP message requesting to join a multicast group, which is sent by the terminal in the local VLAN network.
It should be noted that VTEP1 shown in fig. 1 may also include IGMP module 13 included in VTEP2, and VTEP2 may also include multicast forwarding module 12 included in VTEP1, which is not limited in this embodiment of the present application.
Furthermore, VTEP1 and VTEP2 shown in fig. 1 may belong to the same multicast group or may belong to different multicast groups, and the same VTEP may also belong to different multicast groups at the same time.
It is understood that the VTEP may apply for joining a multicast group or for exiting the multicast group.
It should be noted that the communication system shown in fig. 1 may include other VTEPs, such as VTEP3 shown in fig. 1, in addition to VTEP1 and VTEP 2.
As shown in fig. 1, it is assumed that VTEP1 (hereinafter referred to as a home VTEP) belongs to a specified multicast group, i.e., VTEP1 is a member VTEP of the specified multicast group. The multicast method provided by the embodiment of the present application is described in detail below by taking, as an example, VTEP2 and VTEP3 (hereinafter referred to as remote VTEP) applying for joining a specified multicast group.
As shown in fig. 2, the multicast method includes S201 to S203:
s201, the local VTEP receives the 3 types of routes sent by the remote VTEP, and creates a target broadcast, unknown unicast and multicast BUM forwarding table.
The 3 types of routes comprise internet IP addresses of the remote VTEP and are used for establishing BGP EVPN neighbor relations and BUM forwarding tables between the local VTEP and the remote VTEP.
As shown in fig. 1, the local VTEP may include a BGP module and a multicast forwarding module, the remote VTEP may include a BGP module and an IGMP module, and the local VTEP and the remote VTEP are connected through their respective BGP modules.
Illustratively, after the remote VTEP receives, through its IGMP module, IGMP information sent by a client in the local VLAN network connected to the remote VTEP, the remote VTEP forwards the IGMP information to the home VTEP through the BGP module. Accordingly, the local end VTEP receives the 3 types of routes through the BGP module of the local end VTEP so as to establish BGP EVPN neighbor relation and BUM forwarding table between the local end VTEP and the remote end VTEP. Wherein, the IGMP message carries the above-mentioned 3 types of routes.
For example, as shown in fig. 1, assume that the remote VTEP is VTEP2, whose IP address is: {2.2.2.2}, the local end VTEP establishes a BUM forwarding table with an egress address as the IP address according to the 3-type route: { egress IP address 2.2.2.2 }. The number of the egress IP addresses may be one or more. For example, the BUM forwarding table: { egress IP address 2.2.2.2; 3.3.3.3}. Wherein, the outlet IP address {3.3.3.3} can be other VTEP except the local VTEP and the remote VTEP, such as the IP address of VTEP3 in FIG. 1.
It can be understood that, when the remote VTEP receives the 3-type route, such as {1.1.1.1}, which is sent by the local VTEP and carries the IP address of the local VTEP, the remote VTEP may also locally establish a BUM forwarding table with the egress IP address as the IP address of the local VTEP, where the BUM forwarding table includes a copy table, the copy table includes tunnel information for forwarding a packet, and the establishment process of the copy table of the BUM forwarding table belongs to the prior art, and is not described in detail in this embodiment of the present application.
By the method, each VTEP in the multicast group can establish a BUM forwarding table with an exit IP address being the IP addresses of all other VTEPs except the VTEP in the multicast group locally.
Assume that the IP address of the multicast group is 224.1.1.1. In the prior art, when the local VTEP receives an IP multicast packet whose destination IP address is not {224.1.1.1} of the multicast group, the local VTEP forwards the IP multicast packet to all VTEPs except the local VTEP in the multicast group according to the exit IP address in the BUM forwarding table.
S202, the local VTEP receives the first type 2 route sent by the remote VTEP, creates a corresponding multicast forwarding table, and adds the IP address of the remote VTEP and the tunnel information corresponding to the copy table of the BUM forwarding table into the copy table of the multicast forwarding table.
The first type 2 route is used for the remote VTEP to request to join the designated multicast group, and may be carried in an IGMP join message. Wherein the first type 2 routing comprises: the VXLAN of the remote VTEP identifies the VNI and the local virtual local area network VLAN identification, as well as the IP address specifying the multicast group.
Illustratively, as shown in fig. 1, the home VTEP may receive, through its BGP module, an IGMP join packet sent by the remote VTEP. Wherein, the IGMP message carries the first type 2 route.
For example, assuming that the IGMP join packet sent by the remote VTEP carries a VXLAN network Identifier (VXLAN Identifier, abbreviated as VNI)100 to which the remote VTEP belongs, a local VLAN Identifier 1000 connected to the remote VTEP, an IP address { IP224.1.1.1} of a multicast group to which the remote VTEP requests to join, and a MAC address { MAC01005E010101} of the multicast group to which the remote VTEP requests to join, the local VTEP may generate a first type 2 route according to the information carried in the IGMP join packet: { VNI 100, VLAN ID 1000, IP 224.1.1.1/32, MAC01005E010101/48 }. Where 32 and 48 are mask lengths. Since the mask length is the prior art, the embodiments of the present application are not described in detail.
Then, the local VTEP can establish a VXLAN multicast forwarding table according to the received type 3 route and the first type 2 route. For example, the home VTEP may establish the following VXLAN multicast forwarding table: { { VNI 100; VLAN 1000; IP224.1.1.1 }; next hop 2.2.2.2 }. Wherein, { VNI 100; VLAN 1000; IP224.1.1.1 is a prefix of the VXLAN multicast forwarding table.
The VXLAN multicast forwarding table established by the embodiment of the invention comprises a replication table, the same establishment mechanism is adopted as the replication table of the BUM forwarding table, and the tunnel information corresponding to the replication table of the BUM forwarding table is added into the replication table of the VXLAN multicast forwarding table, wherein the tunnel information comprises a tunnel type and a tunnel identifier.
So far, the home VTEP has learned that: the remote VTEP has successfully joined the specified multicast group, and the local VTEP also establishes a VXLAN multicast forwarding table corresponding to the remote VTEP locally.
It can be understood that the local VTEP may also receive the type 3 routes and the first type 2 routes sent by other VTEPs except the remote VTEP mentioned in the embodiment of the present invention, and establish VXLAN multicast forwarding tables corresponding to the other VTEPs, such as { { VNI 100; VLAN 1000; IP224.1.1.1 }; next hop 2.2.2.2; 3.3.3.3}. Wherein, the next hop IP address {3.3.3.3} is the IP address of the other VTEP.
S203, if the IP multicast message received by the local terminal VTEP carries the IP address of the appointed multicast group, the local terminal VTEP forwards the IP multicast message to the remote terminal VTEP according to the copy table of the multicast forwarding table.
Wherein, VXLAN multicast forwarding table includes: the VNI of the remote VTEP, the local VLAN identification and the IP address, and the IP address of the designated multicast group.
Exemplarily, if the IP multicast packet carries the IP address { IP224.1.1.1} of the designated multicast group, the IP multicast packet may be forwarded to a remote VTEP, such as VTEP2 shown in fig. 1, according to { next hop 2.2.2} in the VXLAN multicast forwarding table generated in S202, or according to { next hop 2.2.2.2; 3.3.3.3}, forward the IP multicast packet to remote VTEPs, such as VTEP2 and VTEP3 shown in fig. 1.
The multicast method provided by the application can establish a VXLAN multicast forwarding table containing the IP address of the remote VTEP and the IP address of the specified multicast group according to the 3-type route and the first 2-type route sent by the remote VTEP, when the IP multicast message received by the local VTEP carries the IP address of the specified multicast group, the local VTEP can forward the IP multicast message to the remote VTEP instead of forwarding all the VTEPs except the local VTEP in the specified multicast group, thereby avoiding the situation of forwarding the IP multicast message to the VTEP which does not need to receive the IP multicast message, reducing the number of invalid IP multicast messages forwarded in the multicast group, reducing the invalid occupation of network bandwidth, and further improving the forwarding efficiency of the whole network.
Optionally, as shown in fig. 3, the method may further include S301:
s301, if the IP multicast message received by the local terminal VTEP does not carry the IP address of the appointed multicast group, the local terminal VTEP forwards the IP multicast message to all VTEPs in the copy table of the BUM forwarding table.
Specifically, the local VTEP may forward the IP multicast packet to all VTEPs except the local VTEP in the designated multicast group according to the existing BUM forwarding table. Since the forwarding method described in S301 is the same as the prior art, details are not described in this embodiment of the present application.
Optionally, corresponding to S202, a VTEP, such as a remote VTEP, that has joined the specified multicast group may also apply for leaving the specified multicast group. Specifically, as shown in fig. 4, the method may further include S401-S402:
s401, the local terminal VTEP receives the second type 2 route.
Wherein, the second type 2 route is used for the far-end VTEP to request to leave the appointed multicast group, and the second type 2 route comprises: the VNI of the remote VTEP, the local VLAN identification, and the IP address of the designated multicast group.
Specifically, the local VTEP receives the second type 2 route, which may be that the local VTEP receives an IGMP leave packet carrying the second type 2 route, and analyzes the IGMP leave packet to generate the second type 2 route.
S402, the local end VTEP deletes the IP address of the far end VTEP in the VXLAN multicast forwarding table according to the second type 2 route.
Exemplarily, if the VNI and the VLAN id of the remote VTEP carried in the IGMP leave packet and the IP address of the designated multicast group are respectively the same as the content in the prefix of the VXLAN multicast forwarding table, the local VTEP deletes the next-hop IP address corresponding to the prefix, that is, deletes the IP address {2.2.2.2} of the remote VTEP in the next-hop IP address.
It can be understood that if the VXLAN multicast forwarding table described in S202 is { { VNI 100; VLAN 1000; IP224.1.1.1 }; next hop 2.2.2.2; 3.3.3.3}, after the VTEP at the local end deletes 2.2.2 in the next hop IP address in the VXLAN multicast forwarding table, the VTEP at the local end forwards the IP multicast packet whose destination IP address is 224.1.1.1} to the VTEP3, but does not forward the IP multicast packet to the VTEP2 any more, so as to forward the IP multicast packet purposefully, reduce the number of times of forwarding the IP multicast packet in the designated multicast group, and improve the efficiency of forwarding the IP multicast packet.
In addition to forwarding messages between member VTEPs within a given multicast group, it may be desirable to forward messages between member VTEPs of the given multicast group and VTEPs not belonging to the given multicast group (hereinafter referred to as non-member VTEPs). Optionally, the first type 2 routing further includes: the MAC address of the multicast group is specified. Accordingly, as shown in fig. 5, the method may further include S501-S502:
s501, the local VTEP sends a third type 2 route to the remote VTEP.
Wherein the third type 2 routing comprises: a public Network Multicast Service Interface (PMSI) attribute, a MAC address for stipulating a Multicast tree and an IP address of a Multicast group, and the MAC address for stipulating the Multicast tree is different from the MAC address of the Multicast group. The PMSI attribute comprises a tunnel type and a tunnel identifier.
It should be noted that the MAC address used for the appointed multicast tree is different from the MAC address of the appointed multicast group, so as to distinguish the type 2 route added to the appointed multicast group from the type 2 route used for the appointed multicast tree. For example, the MAC address included in the type 2 route joining the specified multicast group may be the MAC address of the specified multicast group, and the MAC address used to provision the multicast tree may be 0. In practical application, the MAC address used for the appointed multicast tree may also be another value different from the MAC address of the designated multicast group, and the two values may be distinguished as long as they are different.
S502, the local VTEP modifies the multicast tree corresponding to the multicast forwarding table according to the PMSI attribute.
Specifically, as shown in fig. 6, the step S502 of modifying the multicast tree corresponding to the multicast forwarding table by the local VTEP according to the PMSI attribute may include the step S601:
s601, the local VTEP establishes a new multicast tree which takes the local VTEP as a tree root and takes the remote VTEP as a leaf according to the tunnel information corresponding to the PMSI attribute, and switches the known multicast forwarding table to the new multicast tree.
In the embodiment of the present application, the VTEP may be divided into the functional modules or the functional units according to the above method examples, for example, each functional module or functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a software functional module or a functional unit. The division of the modules or units in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
Fig. 7 shows a schematic diagram of a possible structure of the virtual extensible local area network VXLAN tunnel termination endpoint VTEP involved in the above embodiments. The VTEP includes a receiving module 701, a forwarding module 702, and a storing module 703.
The receiving module 701 is configured to receive a 3-type route sent by a remote VTEP, and create a target broadcast, unknown unicast, and multicast BUM forwarding table; wherein the class 3 route includes the IP address of the remote VTEP.
The receiving module 701 is further configured to receive a first type 2 route sent by the far-end VTEP, create a corresponding multicast forwarding table, and add an IP address of the far-end VTEP and tunnel information corresponding to the replication table of the BUM forwarding table to the replication table of the multicast forwarding table; wherein, the first type 2 route is used for the remote VTEP to request to join the appointed multicast group, and the first type 2 route comprises: the VXLAN of the remote VTEP identifies the VNI, the local virtual local area network VLAN identification, and the IP address specifying the multicast group.
A forwarding module 702, configured to forward the IP multicast packet to the remote VTEP according to the replication table of the multicast forwarding table if the IP multicast packet received by the local VTEP carries the IP address of the specified multicast group.
The memory module 703 is used for storing instructions and data.
Optionally, the forwarding module 702 is further configured to forward the IP multicast packet to all VTEPs in the replication table of the BUM forwarding table if the IP multicast packet received by the local VTEP does not carry the IP address of the designated multicast group.
Optionally, the receiving module 701 is further configured to receive a second type 2 route sent by the far-end VTEP; wherein, the second type 2 route is used for the far-end VTEP to request to leave the appointed multicast group, and the second type 2 route comprises: VNI, local VLAN identification and IP address of the designated multicast group;
accordingly, in conjunction with fig. 7, as shown in fig. 8, the VTEP may further include: a processing module 704;
the processing module 704 is further configured to delete the IP address of the remote VTEP in the replication table of the multicast forwarding table according to the second type 2 route.
Optionally, the forwarding module 702 is further configured to send a third type 2 route to the far-end VTEP; wherein the third type 2 routing comprises: the method comprises the steps that public network multicast service interface PMSI attributes, MAC addresses used for appointing a multicast tree and IP addresses of multicast groups are different, and the MAC addresses used for appointing the multicast tree are different from the MAC addresses of the multicast groups;
the processing module 704 is further configured to modify a multicast tree corresponding to the multicast forwarding table according to the PMSI attribute.
Optionally, the processing module 704 is further configured to establish a new multicast tree using the local VTEP as a tree root and using the remote VTEP as a leaf according to the tunnel information corresponding to the PMSI attribute, and switch the known multicast forwarding table to the new multicast tree.
The VTEP provided by the application can establish a VXLAN multicast forwarding table containing the IP address of the remote VTEP and the IP address of the appointed multicast group according to the 3-type route and the first 2-type route sent by the remote VTEP, when the IP multicast message received by the local VTEP carries the IP address of the appointed multicast group, the local VTEP can forward the IP multicast message to the remote VTEP instead of forwarding all VTEPs except the local VTEP in the appointed multicast group, thereby avoiding the situation of forwarding the IP multicast message to the VTEP which does not need to receive the IP multicast message, reducing the number of invalid IP multicast messages forwarded in the multicast group, reducing the invalid occupation of network bandwidth, and further improving the forwarding efficiency of the whole network.
Fig. 9 shows a schematic diagram of a further possible configuration of the VTEP involved in the above-described embodiment. The VTEP comprises: a processor 901 and a communication interface 902. The processor 901 is configured to control and manage the actions of the VTEP, for example, to perform the steps performed by the storage module 703, the processing module 704, and/or other processes for performing the techniques described herein. The communication interface 902 is used for supporting communication between the VTEP and other network entities, for example, the steps performed by the receiving module 701 and the forwarding module 702 are performed. The VTEP may also include a memory 903 and a bus 904, the memory 903 being used to store program codes and data for the VTEP.
The processor 901 may be, for example, a processor or controller in a VTEP that may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein. The processor or controller may be a central processing unit, general purpose processor, digital signal processor, application specific integrated circuit, field programmable gate array or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others.
The communication interface 902 may be a transceiver, transceiving circuitry, communication interface, input/output interface, etc. in a VTEP.
The memory 903 may be a memory in a VTEP, which may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, a hard disk, or a solid state disk; the memory may also comprise a combination of memories of the kind described above.
The bus 904 may be an Extended Industry Standard Architecture (EISA) bus or the like. The bus 904 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 9, but this does not indicate only one bus or one type of bus.
The embodiment of the application provides a communication system, which may include a VTEP, a user equipment, and a server, where the VTEP is configured to forward a data packet sent by the server to the user equipment, so as to execute the method for processing UDP traffic congestion in a mobile network provided in the embodiment of the application. For the descriptions of the VTEP, the user equipment, and the server, reference may be specifically made to the relevant descriptions in the foregoing method embodiment and apparatus embodiment, and details are not described here again.
Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.
The embodiment of the present application further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer executes the instructions, the computer may perform each step performed by the network device in the method flow shown in the foregoing method embodiment.
The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), a register, a hard disk, an optical fiber, a portable Compact Disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, any suitable combination of the above, or any other form of computer readable storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC). In embodiments of the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method of multicasting, comprising:
a local virtual extensible local area network (VXLAN) tunnel termination end point VTEP receives a 3-type route sent by a remote VTEP, and creates a target broadcast, unknown unicast and multicast BUM forwarding table; wherein the class 3 route includes an IP address of the remote VTEP;
the local end VTEP receives a first type 2 route sent by the remote end VTEP, creates a corresponding multicast forwarding table according to the type 3 route and the first type 2 route, and adds an IP address of the remote end VTEP and tunnel information corresponding to a copy table of the BUM forwarding table into the copy table of the multicast forwarding table; wherein the first type 2 route is used for the remote VTEP to request to join a specified multicast group, and the first type 2 route includes: the VXLAN identification VNI, the local virtual local area network VLAN identification and the IP address of the specified multicast group of the remote VTEP;
and if the IP multicast message received by the local VTEP carries the IP address of the specified multicast group, the local VTEP forwards the IP multicast message to the remote VTEP according to the copy table of the multicast forwarding table.
2. The multicast method according to claim 1, further comprising:
and if the IP multicast message received by the local VTEP does not carry the IP address of the specified multicast group, the local VTEP forwards the IP multicast message to all VTEPs in a replication table of the BUM forwarding table.
3. The multicast method according to claim 1, further comprising:
the local VTEP receives a second type 2 route sent by the remote VTEP; wherein the second type 2 route is used for the remote VTEP to request to leave the specified multicast group, and the second type 2 route comprises: the VNI, a local VLAN identification and an IP address of the designated multicast group;
and the local end VTEP deletes the IP address of the remote end VTEP in the replication table of the multicast forwarding table according to the second type 2 route.
4. The multicast method according to any one of claims 1 to 3, further comprising:
the local VTEP sends a third type 2 route to the remote VTEP; wherein the third type 2 routing comprises: the method comprises the steps that public network multicast service interface PMSI attributes, MAC addresses used for appointing multicast trees and IP addresses of multicast groups are different;
and the local VTEP modifies the multicast tree corresponding to the multicast forwarding table according to the PMSI attribute.
5. The multicast method according to claim 4, wherein the local VTEP modifies the multicast tree corresponding to the multicast forwarding table according to the PMSI attribute, which includes:
and the local VTEP establishes a new multicast tree which takes the local VTEP as a tree root and the remote VTEP as a leaf according to the tunnel information corresponding to the PMSI attribute, and switches the known multicast forwarding table to the new multicast tree.
6. A virtual extensible local area network, VXLAN, tunnel termination endpoint, VTEP, comprising: a receiving module and a forwarding module; wherein the content of the first and second substances,
the receiving module is used for receiving the 3 types of routes sent by the remote VTEP and creating a target broadcast, unknown unicast and multicast BUM forwarding table; wherein the class 3 route includes an IP address of the remote VTEP;
the receiving module is further configured to receive a first type 2 route sent by the remote VTEP, create a corresponding multicast forwarding table according to the type 3 route and the first type 2 route, and add an IP address of the remote VTEP and tunnel information corresponding to a copy table of the BUM forwarding table to a copy table of the multicast forwarding table; wherein the first type 2 route is used for the remote VTEP to request to join a specified multicast group, and the first type 2 route includes: the VXLAN identification VNI, the local virtual local area network VLAN identification and the IP address of the specified multicast group of the remote VTEP;
and the forwarding module is used for forwarding the IP multicast message to the far-end VTEP according to the copy table of the multicast forwarding table if the IP multicast message received by the local-end VTEP carries the IP address of the specified multicast group.
7. The VTEP according to claim 6,
and the forwarding module is further configured to forward the IP multicast packet to all VTEPs in a replication table of the BUM forwarding table if the IP multicast packet received by the local VTEP does not carry the IP address of the specified multicast group.
8. The VTEP according to claim 6, further comprising: a processing module; wherein the content of the first and second substances,
the receiving module is further configured to receive a second type 2 route sent by the remote VTEP; wherein the second type 2 route is used for the remote VTEP to request to leave the specified multicast group, and the second type 2 route comprises: the VNI, a local VLAN identification and an IP address of the designated multicast group;
and the processing module is configured to delete the IP address of the remote VTEP in the replication table of the multicast forwarding table according to the second type 2 route.
9. The VTEP according to any of claims 6 to 8,
the forwarding module is further configured to send a third type 2 route to the remote VTEP; wherein the third type 2 routing comprises: the method comprises the steps that public network multicast service interface PMSI attributes, MAC addresses used for appointing multicast trees and IP addresses of multicast groups are different;
and the processing module is also used for modifying the multicast tree corresponding to the multicast forwarding table according to the PMSI attribute.
10. The VTEP of claim 9, wherein the modifying, by the local VTEP, the multicast tree corresponding to the multicast forwarding table according to the PMSI attribute comprises:
the processing module is further configured to establish a new multicast tree using the local VTEP as a tree root and the remote VTEP as a leaf according to the tunnel information corresponding to the PMSI attribute, and switch the known multicast forwarding table to the new multicast tree.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810995123.1A CN109194560B (en) | 2018-08-29 | 2018-08-29 | Multicast method and VTEP |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810995123.1A CN109194560B (en) | 2018-08-29 | 2018-08-29 | Multicast method and VTEP |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109194560A CN109194560A (en) | 2019-01-11 |
| CN109194560B true CN109194560B (en) | 2021-06-22 |
Family
ID=64917071
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810995123.1A Active CN109194560B (en) | 2018-08-29 | 2018-08-29 | Multicast method and VTEP |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109194560B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110505152B (en) * | 2019-09-11 | 2022-02-22 | 迈普通信技术股份有限公司 | Route filtering method and device and electronic equipment |
| CN111371667A (en) * | 2019-10-23 | 2020-07-03 | 上海科技网络通信有限公司 | LTE VPDN networking method based on VxLAN technology under cloud computing environment |
| CN111083034B (en) * | 2019-12-24 | 2022-03-01 | 浪潮思科网络科技有限公司 | Method, equipment and medium for managing VXLAN tunnel under EVPN |
| CN111970201A (en) * | 2020-08-28 | 2020-11-20 | 迈普通信技术股份有限公司 | Multi-chip cascade forwarding system and forwarding control method |
| CN112688887B (en) * | 2020-12-23 | 2022-07-12 | 新华三技术有限公司 | Tunnel configuration method and node equipment |
| CN113472667B (en) * | 2021-06-29 | 2022-06-21 | 新华三信息安全技术有限公司 | Message forwarding method, device, node equipment and storage medium |
| CN117499299A (en) * | 2022-07-25 | 2024-02-02 | 中兴通讯股份有限公司 | Route forwarding method, electronic equipment and storage medium |
| CN115987912A (en) * | 2022-12-21 | 2023-04-18 | 迈普通信技术股份有限公司 | Message forwarding control method, device, equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104410560A (en) * | 2014-11-27 | 2015-03-11 | 盛科网络（苏州）有限公司 | Method for realizing BUM packet forwarding through NVGRE unicast |
| CN105262667A (en) * | 2015-09-17 | 2016-01-20 | 杭州数梦工场科技有限公司 | Method and device for controlling multicast transmission in Overlay network |
| CN105553848A (en) * | 2014-10-22 | 2016-05-04 | 瞻博网络公司 | Protocol independent multicast sparse mode (pim-sm) support for data center interconnect |
| JP2017034431A (en) * | 2015-07-31 | 2017-02-09 | 日本電信電話株式会社 | Communication system and communication method |
| CN106656722A (en) * | 2016-12-12 | 2017-05-10 | 杭州迪普科技股份有限公司 | VXLAN multicasting method and device |
| CN107612809A (en) * | 2017-10-31 | 2018-01-19 | 新华三技术有限公司 | A kind of multicast list synchronous method and equipment |
-
2018
- 2018-08-29 CN CN201810995123.1A patent/CN109194560B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105553848A (en) * | 2014-10-22 | 2016-05-04 | 瞻博网络公司 | Protocol independent multicast sparse mode (pim-sm) support for data center interconnect |
| CN104410560A (en) * | 2014-11-27 | 2015-03-11 | 盛科网络（苏州）有限公司 | Method for realizing BUM packet forwarding through NVGRE unicast |
| JP2017034431A (en) * | 2015-07-31 | 2017-02-09 | 日本電信電話株式会社 | Communication system and communication method |
| CN105262667A (en) * | 2015-09-17 | 2016-01-20 | 杭州数梦工场科技有限公司 | Method and device for controlling multicast transmission in Overlay network |
| CN106656722A (en) * | 2016-12-12 | 2017-05-10 | 杭州迪普科技股份有限公司 | VXLAN multicasting method and device |
| CN107612809A (en) * | 2017-10-31 | 2018-01-19 | 新华三技术有限公司 | A kind of multicast list synchronous method and equipment |
Non-Patent Citations (2)
| Title |
|---|
| A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN);A. Sajassi, Ed，等;《www.rfc-editor.org》;20180531;第23页 * |
| BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs;R. Aggarwal，等;《www.rfc-editor.org》;20120229;第10-11页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109194560A (en) | 2019-01-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109194560B (en) | Multicast method and VTEP | |
| JP7208386B2 (en) | Packet transfer method, packet transmitter, and packet receiver | |
| US9031069B2 (en) | Method, system, and apparatus for extranet networking of multicast virtual private network | |
| CN111669330B (en) | BIER message sending method and device | |
| US20180227135A1 (en) | Protocol independent multicast sparse mode (pim-sm) support for data center interconnect | |
| CN106656719B (en) | Inter-cloud communication method and related equipment, inter-cloud communication configuration method and related equipment | |
| CN109194559B (en) | Multicast method and VTEP device | |
| WO2018205982A1 (en) | Method and device for implementing broadcast and multicast in software-defined network and storage medium | |
| CN108429680B (en) | Route configuration method, system, medium and equipment based on virtual private cloud | |
| US8855118B2 (en) | Source discovery for non-flooding multicast using openflow | |
| CN104243269A (en) | Processing method and device of messages in VxLAN (virtual extensible local area network) | |
| EP3313031B1 (en) | Sdn-based arp realization method and apparatus | |
| CN110445702B (en) | Message forwarding method and device | |
| WO2018068588A1 (en) | Method and software-defined networking (sdn) controller for providing multicast service | |
| EP3151477B1 (en) | Fast path content delivery over metro access networks | |
| WO2021169235A1 (en) | Method and apparatus for processing routing message, and storage medium and electronic apparatus | |
| CN115442184A (en) | Access system and method, access server, system and storage medium | |
| US11323279B1 (en) | Internet group management protocol host mobility in ethernet virtual private network multicast networks | |
| CN103716244A (en) | Method and device enabling extra-VPN forwarding of multicasts to be achieved | |
| WO2017124712A1 (en) | Message generating method, message forwarding method and device | |
| CN110868307B (en) | Message processing method and device | |
| CN108011828B (en) | Multicast switching method, device, core layer switch and storage medium | |
| US20220094626A1 (en) | Method and Apparatus for Implementing Multicast | |
| WO2017173989A1 (en) | Method, device, and system for distribution processing on multicast and storage medium | |
| CN110324247B (en) | Multicast forwarding method, device and storage medium in three-layer multicast network |
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 |