CN115242708A - Multicast table item processing method and device, electronic equipment and storage medium - Google Patents
Multicast table item processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115242708A CN115242708A CN202210864634.6A CN202210864634A CN115242708A CN 115242708 A CN115242708 A CN 115242708A CN 202210864634 A CN202210864634 A CN 202210864634A CN 115242708 A CN115242708 A CN 115242708A
- Authority
- CN
- China
- Prior art keywords
- multicast
- virtual machine
- management module
- target virtual
- server
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/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/58—Association of routers
- H04L45/586—Association of routers of virtual routers
-
- 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)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a multicast table item processing method, a multicast table item processing device, electronic equipment and a storage medium, and relates to the technical field of communication. The address resolution module sends an address deletion event to the multicast management module to inform the target virtual machine that the address information of the target virtual machine is deleted from the host table. Therefore, the multicast management module is informed of the deletion of the address information of the target virtual machine from the host table through the address resolution module, so that the multicast management module can find the corresponding multicast table entry in time, when it is determined that no other virtual machine monitors the multicast group added by the target virtual machine in the server, that is, the other virtual machine in the server does not need to receive the multicast flow of the multicast group, the multicast table entry can be deleted in time, and the problem that the multicast table entry and the EVPN 6-type route are left under the migration or fault of the target virtual machine, so that the multicast flow impacts other virtual machines in the server after entering the edge switch, the waste of the bandwidth of the public network and the increase of the pressure of CPUs (central processing units) on the other virtual machines are avoided.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a multicast table entry processing method and apparatus, an electronic device, and a storage medium.
Background
A data center (DataCenter, abbreviated as DC), that is, a building site for providing an operating environment for the electronic information devices placed in a centralized manner, includes a main computer room, an auxiliary area, a support area, an administrative management area, and the like. As an important component of the computing infrastructure, the data center is a data center and a computing carrier that promote the development of 5G (5 th Generation Mobile Communication Technology ), artificial intelligence, cloud computing, and other new-Generation digital technologies.
To achieve high reliability and redundant deployment, most current enterprise data center networks contain physical sites that span multiple different physical locations and deploy similar services at these sites. In order to integrate the data center resources and reduce the management cost, the resources of the data center are usually virtualized. The virtualization technology of the data center mainly comprises three aspects of network virtualization, storage virtualization and server virtualization. The server virtualization refers to that multiple Virtual Machines (VMs) are virtualized on one physical server through dedicated virtualization software, and each VM runs independently and has its own operating system, application program, and Virtual hardware environment.
In order to implement dynamic allocation and management of resources among different physical sites, a requirement for dynamic migration of a virtual machine is generated, and the dynamic migration of the virtual machine refers to a process of moving one virtual machine from one physical server to another physical server while ensuring normal operation of the virtual machine. In order to ensure that the service is not interrupted during migration, it is required that, during virtual machine migration, not only the IP address of the virtual machine is not changed, but also the running state of the virtual machine must be kept unchanged (for example, TCP session state), so that the dynamic migration of the virtual machine can only be performed in the same two-layer domain, and cannot be migrated across the two-layer domain. This limits the networks before and after the virtual machine migration to be in the same two-layer network, so two-layer network interconnection must be implemented between sites distributed in different places.
To achieve a large-scale, even cross-domain live migration of virtual machines, it is desirable to include all servers that may be involved in a VM migration into the same two-layer network domain. Thus, VXLAN (Virtual eXtensible Local Area Network), which is a Network virtualization technology, has been introduced.
In the prior art, multicast services also exist in the data center network. When a virtual machine migrates or fails, the host table of the virtual machine is updated in time, but the multicast table entry corresponding to the virtual machine is not deleted in time, which may cause multicast traffic to impact all the suspended virtual machines (which belong to the same server as the virtual machine), thereby increasing the pressure of the CPU on the virtual machine.
Disclosure of Invention
The present invention provides a multicast table entry processing method, apparatus, electronic device and storage medium, so as to solve the problems in the prior art.
Embodiments of the invention may be implemented as follows:
in a first aspect, the present invention provides a multicast table entry processing method, which is applied to an edge switch, where the edge switch is connected to a server, the server is deployed with at least one virtual machine, the edge switch includes a multicast management module and an address resolution module, the address resolution module maintains a host table, and the host table includes address information of each virtual machine; the method comprises the following steps:
when the address resolution module determines that a target virtual machine is in a fault state or has been migrated, deleting the address information of the target virtual machine from the host table, and sending the address deletion event to the multicast management module; the target virtual machine is any one of the virtual machines;
the multicast management module searches a multicast table item corresponding to the target virtual machine;
the multicast management module judges whether other virtual machines exist in the server to monitor a multicast group added by the target virtual machine;
and when the multicast management module determines that no other virtual machine monitors the multicast group added by the target virtual machine in the server, deleting the multicast list item.
In an alternative embodiment, the method further comprises:
the multicast management module judges whether other virtual machines exist in the server to monitor a multicast group added by the target virtual machine;
and when the multicast management module determines that other virtual machines exist in the server to monitor the multicast group, the multicast list item is reserved.
In an optional implementation manner, the step of determining, by the multicast management module, whether there is a multicast group in which another virtual machine monitors the target virtual machine, includes:
the multicast management module sends a specified group query message to a multicast group added by the target virtual machine;
if the multicast management module receives response messages returned by other virtual machines of the server within preset response time, judging that other virtual machines exist in the server to monitor the multicast group;
and if the multicast management module does not receive the response message within the preset response time, the multicast management module resends the specified group query message to the multicast group, and determines that no other virtual machine monitors the multicast group when the response message is not received within preset times.
In an alternative embodiment, the edge switch further comprises a route management module, the edge switch and each of the virtual machines are in a VXLAN network, the VXLAN network further comprising at least one other edge switch communicatively connected to the edge switch; the method further comprises the following steps:
the routing management module receives an entry deletion event sent by the multicast management module, wherein the entry deletion event represents that the multicast entry corresponding to the target virtual machine is deleted;
the route management module deletes the route information corresponding to the target virtual machine;
and the route management module generates an item deletion notification and sends the item deletion notification to each of the other edge switches, so that each of the other edge switches deletes the multicast item and the route information related to the target virtual machine.
In an alternative embodiment, the edge switch further comprises a route management module, the edge switch and each of the virtual machines are in a VXLAN network, the VXLAN network further comprising at least one other edge switch communicatively connected to the edge switch; the method further comprises the following steps:
the multicast management module subscribes the host table to the address resolution module;
the step of determining that the target virtual machine is in a fault state or has been migrated by the address resolution module includes:
the address resolution module detects whether each virtual machine is in the fault state within a timeout period;
or, when the routing management module receives second-type routing information sent by any one of other edge switches, it is determined that the target virtual machine has been migrated to a server connected to the other edge switch, where address information included in the second-type routing information is the same as address information of the target virtual machine in the host table.
In an optional embodiment, the step of detecting, by the address resolution module, whether each of the virtual machines is in the failure state within a timeout period includes:
the address resolution module sends an ARP request to each virtual machine every fixed time within the timeout period;
and if the address analysis module does not receive the APR response message returned by the target virtual machine within the preset times of the overtime, confirming that the target virtual machine is in the fault state.
In an optional embodiment, the step of the edge switch connecting to the server through its access port, and the step of the multicast management module searching for the multicast entry corresponding to the target virtual machine includes:
the multicast management module acquires a multicast table entry corresponding to each port of the edge switch, wherein the multicast table entry comprises a port number;
and the multicast management module searches the multicast table entry with the port number consistent with the port number of the access side port from all the multicast table entries to obtain the multicast table entry corresponding to the target virtual machine.
In a second aspect, the present invention provides a multicast table entry processing apparatus, which is applied to an edge switch, where the edge switch is connected to a server, the server is deployed with at least one virtual machine, the multicast table entry processing apparatus includes a multicast management module and an address resolution module, the address resolution module maintains a host table, and the host table includes address information of each virtual machine;
the address resolution module is used for: when the target virtual machine is determined to be in a fault state or migrated, deleting the address information of the target virtual machine from the host table, and sending the address deletion event to the multicast management module; the target virtual machine is any one of the virtual machines;
the multicast management module is used for:
searching a multicast table item corresponding to the target virtual machine;
and deleting the multicast list item when determining that no other virtual machine monitors the multicast group added by the target virtual machine in the server.
In a third aspect, the present invention provides an edge switch, comprising: a memory and a processor, the memory storing machine readable instructions executable by the processor, the processor executing the machine readable instructions when the edge switch is running to implement the multicast entry processing method according to any one of the preceding embodiments.
In a fourth aspect, the present invention provides a computer-readable storage medium, which stores a computer program, where the computer program is executed by a processor to implement the multicast entry processing method according to any one of the foregoing embodiments.
Compared with the prior art, the embodiment of the invention provides a multicast table item processing method, a multicast table item processing device, electronic equipment and a storage medium. The edge switch is connected with a server with a plurality of virtual machines, the edge switch comprises a multicast management module and an address resolution module, the address resolution module maintains a host table, and the host table comprises address information of each virtual machine. The address resolution module sends an address deletion event to the multicast management module to inform the target virtual machine that the address information of the target virtual machine is deleted from the host table. Therefore, the address analysis module informs the multicast management module that the address information of the target virtual machine is deleted from the host table, so that the multicast management module can find the corresponding multicast table item in time and judge whether the server has a multicast group which is monitored by other virtual machines and is added in the target virtual machine. When it is determined that no other virtual machine monitors the multicast group added by the target virtual machine, that is, the other virtual machine in the server does not need to receive the multicast traffic of the multicast group, the multicast management module can delete the multicast entry in time, so as to avoid that the multicast entry is left by the target virtual machine due to migration or failure of the target virtual machine, which causes the multicast traffic to impact the other virtual machine in the server and increases the pressure of the CPU on the other virtual machine.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a schematic diagram of a partial architecture of a virtual extensible local area network according to an embodiment of the present invention.
Fig. 2 is a flowchart of a multicast entry processing method according to an embodiment of the present invention.
Fig. 3 is a schematic view of a virtual machine migration scenario according to an embodiment of the present invention.
Fig. 4 is a second flowchart illustrating a multicast entry processing method according to an embodiment of the present invention.
Fig. 5 is a third flowchart illustrating a multicast entry processing method according to an embodiment of the present invention.
Fig. 6 is a schematic structural diagram of a multicast entry processing apparatus according to an embodiment of the present invention.
Fig. 7 is a schematic structural diagram of an edge switch according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present invention, as presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
It should be noted that the features of the embodiments of the present invention may be combined with each other without conflict.
In a virtual extensible local area network (VXLAN), a Spine-Leaf architecture is involved, and the architecture is a data center network topology structure consisting of two exchange layers, namely a Spine layer and a Leaf layer. The Leaf layer is composed of edge switches, aggregates the traffic from each virtual machine in the server, and is directly connected to the Spine layer. Spine switches may interconnect all Leaf switches in a full mesh topology.
Referring to fig. 1, fig. 1 is a schematic diagram of a partial architecture of a virtual extensible local area network according to an embodiment of the present invention. Three edge switches (Leaf 1 node, leaf2 node and Leaf3 node) of a Leaf layer are connected under the Spine node to form a network basic framework. Wherein, a server S1 and a server S2 are accessed under the Leaf1 node; a server S3 is accessed under the Leaf2 node; the server S4 is accessed under the Leaf3 node. By using a server virtualization technology, virtual machines VM1 and VM2 may be deployed in the server S1, and virtual machines VM3, VM4, and VM5 may be deployed in the servers S2, S3, and S4, respectively.
Virtual tunnels are constructed between every two Leaf1 nodes, leaf2 nodes and Leaf3 nodes, so that any two virtual machines in a network can communicate with each other, each Leaf node can be an edge switch, has a VTEP (VXLAN Tunnel Endpoints) function and can be responsible for encapsulation and decapsulation of VXLAN messages.
It should be noted that fig. 1 is only an illustration, and in practical applications, the network topology of the VXLAN may be more complex, and the number of servers accessed under each Leaf node and the number of virtual machines deployed in each server are not limited according to practical application situations.
In the VXLAN Network, multicast service also exists, and the VXLAN Network is required to support IGMP Snooping (Internet Group Management Protocol Snooping) technology, and in the VXLAN Network, multicast table entries are advertised and learned through a type 6route of an EVPN (Ethernet Virtual Private Network).
Based on the service requirement, the virtual machine can actively apply for joining the multicast group and receive the multicast flow. With reference to fig. 1, it is assumed that VM1 needs to join a certain multicast group, and an ARP (Address Resolution protocol) request may be sent to the Leaf1 node, where the ARP request includes information such as a network identifier (VNI) of a VXLAN to which VM1 belongs, a port number of a port (VXLAN port, abbreviated as vx port) to which server S1 and Leaf1 node to which VM1 belongs are connected, and a multicast Address of the multicast group to which VM1 needs to join.
After receiving the ARP request of VM1, the Leaf1 node establishes a multicast entry of VM1, where the multicast entry includes information such as a network identifier, a port number, and a multicast Address of VM1, and adds a mapping relationship between VM1 and its IP Address and MAC (Media Access Control Address) Address in a host table maintained by the Leaf1 node itself. Then, based on the established multicast entry, the Leaf1 node will generate EVPN Type 6route (Border Gateway Protocol Ethernet Virtual Private Network Type 6 Router), and notify the EVPN Type 6route to the Leaf2 node and the Leaf3 node through the Virtual tunnel. After receiving the EVPN type 6route, the Leaf2 node and the Leaf3 node may obtain information such as a network identifier, a port number, a multicast address, and the like of the VM1, and generate a multicast entry.
In the prior art, with reference to fig. 1, when it is determined that a virtual machine VM1 migrates or fails, a Leaf1 node deletes a mapping relationship between an IP address and an MAC address belonging to VM1 in a host table in time, and a multicast entry corresponding to the Leaf1 node is deleted when time elapses, and when the multicast entry is deleted, a corresponding EVPN type 6route is deleted. However, the default timeout time of the multicast table entry is 260S, if VM2 does not join the multicast group to which VM1 belongs before migration, in this case, in the default timeout time, there is no receiver of multicast traffic in server S1 under Leaf1 node actually, but because EVPN class 6 routing is not deleted, the multicast traffic will be transmitted to Leaf1 node all the time, which will cause waste of public network bandwidth, and meanwhile, the multicast table entry is not deleted, the multicast traffic will go out from port p1 corresponding to VM1 in the multicast table entry, and impact the CPU of the suspended virtual machine VM 2.
In view of this, an embodiment of the present invention provides a multicast entry processing method, where after an address resolution module determines that a target virtual machine is in a failure state or has migrated, the address resolution module may notify a multicast management module that address information of the target virtual machine has been deleted from a host table, so that the multicast management module may find a corresponding multicast entry in time, and when it is determined that there is no multicast group that is added by another virtual machine monitoring the target virtual machine in a server, that is, when it is determined that the other virtual machine in the server does not need to receive multicast traffic of the multicast group, the multicast entry may be deleted in time, so as to avoid that the multicast traffic impacts other virtual machines in the server, which causes an increase in pressure of CPUs in the other virtual machines due to the multicast entry being migrated or left by a failure of the target virtual machine. The following detailed description is given by way of example with reference to the accompanying drawings.
Referring to fig. 2, fig. 2 is a flowchart illustrating a multicast entry processing method according to an embodiment of the present invention, where an execution main body of the method may be the edge switch, where the edge switch is connected to a server, the server is deployed with at least one virtual machine, the edge switch includes a multicast management module and an address resolution module, the address resolution module maintains a host table, and the host table includes address information of each virtual machine. The method comprises the following steps:
s110, when the address analysis module determines that the target virtual machine is in a fault state or has been migrated, the address information of the target virtual machine is deleted from the host table, and an address deletion event is sent to the multicast management module.
In this embodiment, the host table stores the correspondence between the IP address and the MAC address of each virtual machine under the edge switch. When the address resolution module determines that the target virtual machine is in a fault state or has been migrated, the IP address and the MAC address of the target virtual machine are deleted from the host table, and the multicast management module is notified that the address information of the target virtual machine has been deleted from the host table by an address deletion event.
S120, the multicast management module searches a multicast table item corresponding to the target virtual machine.
In this embodiment, the target virtual machine may be any one of the virtual machines in the server. The multicast management module may manage and maintain a plurality of multicast entries, and a multicast entry corresponding to a target virtual machine may represent that the target virtual machine has joined a multicast group before migration or before a failure occurs, and may receive multicast traffic of the multicast group.
S130, the multicast management module judges whether a multicast group which is added by other virtual machines to monitor the target virtual machine exists in the server.
In this embodiment, after the multicast management module finds the multicast entry of the target virtual machine, it needs to determine whether there is a multicast group in the server, where other virtual machines monitor the addition of the target virtual machine, so as to determine whether to delete the multicast entry corresponding to the target virtual machine.
It can be understood that when the multicast management module determines that there is a multicast group in the server, where other virtual machines monitor the joining of the target virtual machine, step S140 may be executed; when the multicast management module determines that there is no multicast group in the server for other virtual machines to listen to the joining of the target virtual machine, step S150 may be executed. S150, when the multicast management module determines that the multicast group added by the other virtual machine monitoring target virtual machine does not exist in the server, deleting the multicast list item.
In this embodiment, when it is determined that there is no multicast group to which the target virtual machine joins monitored by another virtual machine on the server to which the target virtual machine belongs, the multicast management module deletes the multicast entry corresponding to the target virtual machine. That is, when other virtual machines in the server do not join the multicast group joined by the target virtual machine, that is, it is proved that there is no multicast group that other virtual machines monitor joined by the target virtual machine on the server, so there is no receiver of the multicast traffic of the multicast group on the server, and the multicast entry of the target virtual machine can be deleted.
In the multicast table entry processing method provided by the embodiment of the present invention, an edge switch is connected to a server in which a plurality of virtual machines are deployed, the edge switch includes a multicast management module and an address resolution module, the address resolution module maintains a host table, and the host table includes address information of each virtual machine. The address resolution module sends an address deletion event to the multicast management module to inform the target virtual machine that the address information of the target virtual machine is deleted from the host table. Therefore, the address analysis module informs the multicast management module that the address information of the target virtual machine is deleted from the host table, so that the multicast management module can find the corresponding multicast table entry in time, and when it is determined that no other virtual machine monitors the multicast group added by the target virtual machine in the server, that is, the other virtual machine in the server does not need to receive the multicast flow of the multicast group, the multicast table entry can be deleted in time, thereby avoiding the problem that the multicast table entry is migrated or left by the target virtual machine due to a fault, so that the multicast flow impacts other virtual machines in the server, and the pressure of a CPU on other virtual machines is increased.
It should be noted that, with reference to fig. 6, in the embodiment of the present invention, an edge switch may include a multicast management module, an address resolution module, and a routing management module. It can be understood that the multicast management module may be an IGMP Snooping module of the edge switch, the address resolution module may be an ARP module of the edge switch, and the routing management module may be a BGP (Border Gateway Protocol) module of the edge switch. The following describes, with reference to a specific example, a process of processing, in an edge switch, a multicast entry and an EVPN sixth-type route corresponding to a target virtual machine in cooperation between three modules after the target virtual machine is migrated or fails.
Optionally, referring to fig. 4, correspondingly, before step S150, the method may further include S140:
s140, when the multicast management module determines that the multicast group added by the other virtual machines monitoring the target virtual machine exists in the server, the multicast list item is reserved.
It can be understood that, when there is a multicast group in the server where other virtual machines monitor the joining of the target virtual machine, the multicast management module may retain the multicast entry corresponding to the target virtual machine, so as to avoid that other virtual machines cannot receive the multicast traffic.
In an optional implementation manner, the multicast management module needs to subscribe to the host table from the address resolution module, so as to ensure that the multicast management module is notified when the address resolution module updates the host table. With reference to fig. 4, correspondingly, the method may further include step S100:
s100, the multicast management module subscribes the host list to the address resolution module.
In this embodiment, the multicast management module may generate a subscription event and issue the subscription event to the address resolution module, where the subscription event may be used to subscribe to the host table from the address resolution module.
Optionally, in step S110, the process of determining that the target virtual machine is in a failure state or has migrated by the address resolution module may include the sub-steps S111 or S112:
s111, the address resolution module detects whether each virtual machine is in a fault state within the overtime.
It is to be understood that, when detecting the operating state of the virtual machine, the address resolution module may detect whether each virtual machine in the server is in a failure state within a timeout period, where the number of detections within the timeout period may be a predetermined number.
Optionally, step S111 may include the sub-steps of:
s111-1, the address resolution module sends ARP requests to each virtual machine every fixed time interval within the overtime.
It will be appreciated that the number of detections within the timeout period is related to the fixed duration, i.e. the predetermined number depends on the size of the fixed duration and the size of the timeout period. For example, the timeout period may be configured to be 60s, the fixed duration may be configured to be 15s, and the predetermined number of times within the timeout period is 4 times. It should be noted that this example is only an example, and the configuration values of the timeout time, the predetermined number of times, and the fixed duration may be flexibly considered, which is determined by the practical application of the edge switch, and are not limited herein.
S111-2, if the address analysis module does not receive the APR response message returned by the target virtual machine within the preset times of the overtime, determining that the target virtual machine is in a fault state.
In this embodiment, the address resolution module detects every other fixed duration within the timeout period, and in each detection process, issues the ARP request to each virtual machine in the server. That is, within the timeout period, the address resolution module will send a predetermined number of ARP requests to each virtual machine. For any one virtual machine: if the address resolution module receives at least one APR response message returned by the virtual machine within the overtime, the virtual machine is confirmed to be in a normal working state; and if the address resolution module does not receive the APR response message returned by the virtual machine within the preset times within the overtime, confirming that the virtual machine is in a fault state, wherein the virtual machine is the target virtual machine.
It is to be understood that steps S111-1 and S111-2 are processes representing the address resolution module determining whether the target virtual machine is in a failed state. In another case, the target virtual machine is migrated to another server. The following describes a process in which an edge switch discovers migration of a target virtual machine to a server to which another edge switch is connected.
And S112, when the routing management module receives the second-class routing information sent by any other edge switch, confirming that the target virtual machine is migrated to the server connected with the other edge switch.
In this embodiment, the second type of routing information includes address information that is the same as the address information of the target virtual machine in the host table. The second type of routing information is EVPN type 2 routing, which may include the IP address and MAC address of the target virtual machine.
Referring to fig. 3, fig. 3 is a schematic view of a virtual machine migration scenario according to an embodiment of the present invention. Assuming that the VM1 is migrated from the server S1 to the server S4, when the VM1 completes the migration and starts working in the server S4, the VM1 reports an ARP packet to an edge switch (Leaf 3 node) connected to the server S4, so as to notify the MAC address and the IP address of the VM1 itself to the network. And the Leaf3 node receives the ARP message sent by the newly started VM1, generates an EVPN 2 type route, and sends the EVPN 2 type route to the Leaf1 node and the Leaf2 node through the virtual tunnel.
Therefore, for the edge switch corresponding to the Leaf1 node, which is the execution subject in the embodiment of the present invention, when receiving the EVPN type 2 route sent by the edge switch corresponding to the Leaf2 node, the Leaf1 node will compare the address information included in the EVPN type 2 route with the address information in the maintenance host table of the Leaf1 node, and determine whether there is a coincidence. During comparison, the Leaf1 node finds that the address information of the VM1 contained in the EVPN 2 type route is overlapped with the address information of the VM1 in the host table, the Leaf1 node confirms that the VM1 is migrated to a server under the Leaf3 node, and the VM1 is the target virtual machine at the moment.
It should be noted that the above example is only an exemplary illustration of a scenario shown for ease of understanding, and is not limited herein.
In an alternative embodiment, the edge switch is connected to the server through its access side port, and the sub-step of step S120 may include:
s121, the multicast management module obtains a multicast table entry corresponding to each port of the edge switch.
In this embodiment, the multicast entry may include, but is not limited to, a network identifier, a port number, a multicast address, and other information.
Optionally, in the multicast management module, all multicast table entries may exist in the multicast table. Referring to fig. 1, the Leaf1 node is connected to the server S1, the server S2, the Leaf3 node, the Leaf2 node, and the Spine node through five ports, i.e., p1, p2, p3, p4, and p 5. Wherein, p1 and p2 belong to the access side interface of the Leaf1 node, and p3, p4 and p5 belong to the network side interface of the Leaf1 node.
Assuming that VM2 is the multicast source, VM1, VM4, and VM5 all join the same multicast group, and VM2 joins another multicast group, the multicast table of the Leaf1 node may be as shown in table 1.1 below:
TABLE 1.1
| Number | VXLAN ID | Interface Name | Group Address | last report |
| 1 | 1001 | p1 | 225.0.0.1 | VM1 address |
| 2 | 1001 | p1 | 225.0.0.2 | |
| 3 | 1001 | p2 | 225.0.0.1 | VM3 address |
| 4 | 1001 | Leaf2 Tunnel Source | 225.0.0.1 | Leaf2 Tunnel Source |
| 5 | 1001 | Leaf3 Tunnel Source | 225.0.0.1 | Leaf3 Tunnel Source |
In the table, except the row where the table head is located, each of the other rows is a multicast table entry. Wherein, number is only one serial Number, VXLAN ID represents a network identifier, interface Name represents a port Number, group Address represents a multicast Address, and last report represents a source of a multicast entry.
In the table, the port number of the row with the sequence number 3 being Leaf2 Tunnel Source indicates that the multicast table entry corresponds to the Leaf2 node, and the last report of the row with the sequence number 3 being Leaf2 Tunnel Source indicates that the multicast table entry provides a virtual Tunnel report for the Leaf2 node.
And S122, the multicast management module searches the multicast table entries with the port numbers consistent with those of the access side ports from all the multicast table entries to obtain the multicast table entries corresponding to the target virtual machines.
With reference to fig. 3, it is assumed that VM1 migrates from server S1 to server S4, then for the Leaf1 node, it may search the multicast entry whose port number is consistent with the port number of the access side port corresponding to the target virtual machine from table 1.1, that is, the multicast entry corresponding to sequence number 1 is the multicast entry of the target virtual machine.
It should be noted that, the foregoing examples are only examples, and in practical application, the storage manner of the multicast table entry on the edge switch is not limited.
Optionally, step S130 may include sub-steps S131 to S133:
s131, the multicast management module sends the specified group query message to the multicast group.
In this embodiment, the Query packet for the specified Group may be a Group-Specific Query instruction.
And S132, if the multicast management module receives response messages returned by other virtual machines of the server within the preset response time, judging that other virtual machines monitor the multicast group in the server.
S133, if the multicast management module does not receive the response message within the preset response time, the multicast management module resends the specified group query message to the multicast group, and when the response message is not received within the preset times, the server is judged that no other virtual machine monitors the multicast group.
It can be understood that, after the multicast management module sends the specified group query message to the multicast group for the first time, if the response messages returned by other virtual machines in the server are not received within the preset response time, the multicast management module sends the specified group query message to the multicast group again, and if the response messages returned by other virtual machines in the server are not received within the preset response time within the preset times, it can be determined that there is no multicast group in which other virtual machines monitor the joining of the target virtual machine in the server.
With reference to fig. 3, it is assumed that VM1 is a migrated target virtual machine, a multicast address of a multicast group added thereto is 225.0.0.1, a multicast management module sends a specified group query message to the multicast group, and all virtual machines added to the multicast group with the multicast address of 225.0.0.1 need to reply a response message within a preset response time when receiving the specified group query message.
If the multicast group added by VM2 is also 225.0.0.1, in combination with the above example, if the multicast management module receives the response packet returned by VM2 within the preset response time, it may be determined that there is a multicast group added by VM1 that is monitored by VM2 in the server S1.
If the multicast group added by VM2 is different from VM1, and is 225.0.0.2, in combination with the above example, if the multicast management module does not receive the response packet returned by VM2 within the preset response time within the preset number of times, it may be determined that there is no multicast group added by VM1 monitored by other virtual machines in the server S1.
Note that the preset response time may be set in advance, for example, may be set to 1 second or 1.5 seconds. The preset number of times may be preset, and may be set to 3 times or 2 times, for example.
In an optional implementation manner, after the multicast management module deletes the multicast entry corresponding to the target virtual machine, it is further required to delete the EVPN class 6route corresponding to the multicast entry, so as to avoid that the EVPN class 6route is left behind by the target virtual machine, which causes the multicast traffic of the target virtual machine joining the multicast group is transmitted to the edge switch, and causes the waste of the public network bandwidth. Accordingly, referring to fig. 5, after step S150, the method may further include steps S160 to S180:
and S160, the routing management module receives the entry deletion event sent by the multicast management module.
S170, the route management module deletes the route information corresponding to the target virtual machine.
In this embodiment, after deleting the multicast entry corresponding to the target virtual machine, the multicast management module may generate an entry deletion event, where the entry deletion event may indicate that the multicast entry corresponding to the target virtual machine is deleted. When the routing management module receives the entry deletion event, the routing information corresponding to the target virtual machine is deleted.
It can be understood that the routing information is EVPN class 6 routing. Before migration or before a fault occurs, if a target virtual machine needs to join a multicast group, a group adding application is sent to an edge switch to request to join the multicast group, the edge switch generates a multicast entry corresponding to the target virtual machine based on the group adding application, and generates an EVPN type 6route based on the multicast entry. And the edge switch sends the EVPN 6 type route to other edge switches connected in the network, so that the other edge switches generate multicast entries corresponding to the target virtual machine based on the EVPN 6 type route. Thus, the target virtual machine can receive the multicast traffic of the multicast group after joining the multicast group.
S180, the route management module generates an item deleting notice and sends the item deleting notice to each other edge switch, so that each other edge switch deletes the multicast items and the route information related to the target virtual machine.
It can be understood that, when the multicast entry and the EVPN type 6route corresponding to the target virtual machine are deleted in the edge switch, the route management module generates an entry deletion notification, and sends the entry deletion notification to each of the other edge switches, so that each of the other edge switches deletes the multicast entry and the EVPN type 6route related to the target virtual machine.
Therefore, other edge switches in the VXLAN network are informed to delete the multicast list items and the routing information of the target virtual machine through the routing management module, so that the multicast flow cannot be sent to the original edge switch when the virtual machines in the multicast group multicast messages, and the waste of storage space on other virtual machines is avoided.
It should be noted that, the execution sequence of each step in the foregoing method embodiments is not limited to that shown in the drawings, and the execution sequence of each step is subject to the practical application.
Compared with the prior art, the embodiment of the invention has the following beneficial effects:
the multicast management module can delete the address information of the target virtual machine from the host table and send an address deletion event to the multicast management module when the address resolution module determines that the target virtual machine is in a fault state or has migrated by subscribing the host table of the address resolution module. The multicast management module can timely search the corresponding multicast entry, and when it is determined that no multicast group added by the target virtual machine is monitored by other virtual machines in the server, that is, other virtual machines in the server do not need to receive the multicast traffic of the multicast group, the multicast entry and the EVPN 6-type route corresponding to the target virtual machine can be timely deleted, so that the problem that the multicast traffic of the multicast group is transmitted to the edge switch to cause the waste of public network bandwidth under the condition that the multicast entry and the EVPN 6-type route are left under the migration or fault of the target virtual machine is avoided, and the problem that the pressure of a CPU (Central processing Unit) on other virtual machines is increased because the multicast traffic flows into other virtual machines in the server from the edge switch is also avoided;
meanwhile, other edge switches in the VXLAN network are informed to delete the multicast table items and the routing information related to the target virtual machine through the routing management module, so that the multicast flow cannot be sent to the original edge switch when the virtual machines in the multicast group multicast the message, and the waste of storage space on other virtual machines is avoided.
In order to perform the corresponding steps in the above method embodiments and various possible embodiments, an implementation manner of a multicast entry processing apparatus is given below.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a multicast entry processing apparatus according to an embodiment of the present invention. The multicast table item processing apparatus 200 is applied to an edge switch, the edge switch is connected to a server, the server is deployed with at least one virtual machine, the multicast table item processing apparatus 200 includes an address resolution module 210 and a multicast management module 220, the address resolution module 210 maintains a host table, and the host table includes address information of each virtual machine.
And the address resolution module 210 is configured to delete the address information of the target virtual machine from the host table and send an address deletion event to the multicast management module when it is determined that the target virtual machine is in a failure state or has migrated. The target virtual machine is any one of the virtual machines.
A multicast management module 220, configured to:
searching a multicast table item corresponding to the target virtual machine;
judging whether a multicast group which is monitored by other virtual machines and added by a target virtual machine exists in the server; and deleting the multicast list item when determining that the multicast group added by the target virtual machine monitored by other virtual machines does not exist in the server.
In an optional embodiment, the multicast management module 220 may be further configured to:
and when determining that the multicast group added by the target virtual machine is monitored by other virtual machines in the server, reserving the multicast list item.
In an optional embodiment, the multicast management module 220 may be specifically configured to:
sending a specified group query message to a multicast group added by a target virtual machine;
if response messages returned by other virtual machines of the server are received within the preset response time, judging that other virtual machines exist in the server to monitor the multicast group;
if the response message is not received within the preset response time, the specified group query message is sent to the multicast group again, and when the response message is not received within the preset times, it is determined that no other virtual machine monitoring multicast group exists in the server.
In an alternative embodiment, the edge switch and each virtual machine are in a VXLAN network that further includes at least one other edge switch communicatively connected to the edge switch. The edge switch also includes a route management module 230, and the route management module 230 may be configured to:
receiving a table item deleting event sent by a multicast management module, wherein the table item deleting event represents that a multicast table item corresponding to a target virtual machine is deleted;
deleting the routing information corresponding to the target virtual machine;
and generating an entry deletion notification and sending the entry deletion notification to each other edge switch so that each other edge switch deletes the multicast entry and the routing information related to the target virtual machine.
In an alternative embodiment, the edge switch and each virtual machine are in a VXLAN network that further includes at least one other edge switch communicatively connected to the edge switch. The multicast management module 220 may be further configured to:
subscribing to a host table from the address resolution module 210;
optionally, the address resolution module 210 may be configured to detect whether each virtual machine is in a failure state within a timeout period.
The routing management module 230 may be configured to, when receiving second-type routing information sent by any one of the other edge switches, confirm that the target virtual machine has migrated to the server connected to the other edge switch, where the second-type routing information includes address information that is the same as the address information of the target virtual machine in the host table.
In an optional embodiment, the address resolution module 210 may be specifically configured to:
sending an address resolution request to each virtual machine every fixed time within the overtime;
and if the feedback message returned by the target virtual machine is not received within the preset times of the overtime time, determining that the target virtual machine is in a fault state.
In an optional embodiment, the edge switch is connected to the server through an access side port thereof, and the multicast management module 220 may specifically be configured to:
acquiring a multicast table entry corresponding to each port of an edge switch, wherein the multicast table entry comprises port numbers;
and searching the multicast table entry with the port number consistent with that of the port at the access side from all the multicast table entries to obtain the multicast table entry corresponding to the target virtual machine.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the multicast entry processing apparatus 200 described above may refer to the corresponding process in the foregoing method embodiment, and is not described herein again.
Referring to fig. 7, fig. 7 is a schematic structural diagram of an edge switch according to an embodiment of the present invention. The edge switch 300 includes a processor 310, a memory 320, and a bus 330, the processor 310 being coupled to the memory 320 via the bus 330.
The memory 320 may be used to store a software program, such as the multicast entry processing device shown in FIG. 6. The Memory 320 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Flash Memory (Flash), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like. The processor 310 may be an integrated circuit chip having signal processing capabilities. The Processor 310 may be a general-purpose Processor including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
It will be appreciated that the architecture shown in fig. 7 is merely illustrative and that edge switch 300 may include more or fewer components than shown in fig. 7 or have a different configuration than shown in fig. 7. The components shown in fig. 7 may be implemented in hardware, software, or a combination thereof.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the multicast table entry processing method disclosed in the foregoing embodiment. The computer readable storage medium may be, but is not limited to: various media capable of storing program code, such as a U disk, a removable hard disk, a ROM, a RAM, a PROM, an EPROM, an EEPROM, a FLASH disk, or an optical disk.
To sum up, embodiments of the present invention provide a method and an apparatus for processing multicast table entries, an electronic device, and a storage medium, where an edge switch is connected to a server deployed with multiple virtual machines, the edge switch includes a multicast management module and an address resolution module, the address resolution module maintains a host table, and the host table includes address information of each virtual machine. The address resolution module sends an address deletion event to the multicast management module to inform the target virtual machine that the address information of the target virtual machine is deleted from the host table. Therefore, the multicast management module is informed of the deletion of the address information of the target virtual machine from the host table through the address resolution module, so that the multicast management module can find the corresponding multicast table entry in time, when it is determined that no other virtual machine monitors the multicast group added by the target virtual machine in the server, that is, the other virtual machine in the server does not need to receive the multicast flow of the multicast group, the multicast table entry can be deleted in time, and the problem that the multicast table entry and the EVPN 6-type route are left under the migration or fault of the target virtual machine, so that the multicast flow impacts the other virtual machine in the server after entering the edge switch, the waste of the bandwidth of the public network and the increase of the pressure of CPUs (central processing units) on the other virtual machines are avoided. The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are also within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. The multicast table item processing method is applied to an edge switch, the edge switch is connected with a server, the server is deployed with at least one virtual machine, the edge switch comprises a multicast management module and an address resolution module, the address resolution module maintains a host table, and the host table comprises address information of each virtual machine; the method comprises the following steps:
when the address resolution module determines that a target virtual machine is in a fault state or has migrated, deleting the address information of the target virtual machine from the host table, and sending the address deletion event to the multicast management module; the target virtual machine is any one of the virtual machines;
the multicast management module searches a multicast table item corresponding to the target virtual machine;
the multicast management module judges whether other virtual machines exist in the server to monitor a multicast group added by the target virtual machine;
and when the multicast management module determines that no other virtual machine monitors the multicast group added by the target virtual machine in the server, deleting the multicast list item.
2. The method of claim 1, further comprising:
and when the multicast management module determines that the multicast group which is monitored by other virtual machines and added by the target virtual machine exists in the server, the multicast list item is reserved.
3. The method according to claim 1, wherein the step of the multicast management module determining whether there is another virtual machine in the server to listen to the multicast group joined by the target virtual machine includes:
the multicast management module sends a specified group query message to a multicast group added by the target virtual machine;
if the multicast management module receives response messages returned by other virtual machines of the server within preset response time, judging that other virtual machines exist in the server to monitor the multicast group;
if the multicast management module does not receive the response message within the preset response time, the multicast management module resends the specified group query message to the multicast group, and determines that no other virtual machine in the server monitors the multicast group when the response message is not received within preset times.
4. The method of claim 1, wherein the edge switch further comprises a route management module, wherein the edge switch and each of the virtual machines are in a VXLAN network, wherein the VXLAN network further comprises at least one other edge switch communicatively connected to the edge switch; the method further comprises the following steps:
the routing management module receives an entry deletion event sent by the multicast management module, wherein the entry deletion event represents that the multicast entry corresponding to the target virtual machine is deleted;
the routing management module deletes the routing information corresponding to the target virtual machine;
and the route management module generates an item deletion notification and sends the item deletion notification to each of the other edge switches, so that each of the other edge switches deletes the multicast item and the route information related to the target virtual machine.
5. The method of claim 1, wherein the edge switch further comprises a route management module, wherein the edge switch and each of the virtual machines are in a VXLAN network, wherein the VXLAN network further comprises at least one other edge switch communicatively connected to the edge switch; the method further comprises the following steps:
the multicast management module subscribes the host table to the address resolution module;
the step of determining that the target virtual machine is in a fault state or has been migrated by the address resolution module includes:
the address resolution module detects whether each virtual machine is in the fault state within a timeout period;
or, when the routing management module receives second-type routing information sent by any one of other edge switches, it is determined that the target virtual machine has been migrated to a server connected to the other edge switch, where address information included in the second-type routing information is the same as address information of the target virtual machine in the host table.
6. The method of claim 5, wherein the step of the address resolution module detecting whether each of the virtual machines is in the fault state within a timeout period comprises:
the address resolution module sends an ARP request to each virtual machine every fixed time within the overtime;
and if the address analysis module does not receive the APR response message returned by the target virtual machine within the preset times of the overtime, confirming that the target virtual machine is in the fault state.
7. The method of claim 1, wherein the edge switch is connected to the server through an access-side port of the edge switch, and the step of the multicast management module searching for the multicast table entry corresponding to the target virtual machine includes:
the multicast management module acquires a multicast table entry corresponding to each port of the edge switch, wherein the multicast table entry comprises a port number;
and the multicast management module searches the multicast table items with the port numbers consistent with the port numbers of the access side ports from all the multicast table items to obtain the multicast table items corresponding to the target virtual machine.
8. The multicast table item processing device is applied to an edge switch, the edge switch is connected with a server, the server is deployed with at least one virtual machine, the multicast table item processing device comprises a multicast management module and an address resolution module, the address resolution module maintains a host table, and the host table comprises address information of each virtual machine;
the address resolution module is used for: when determining that the target virtual machine is in a fault state or has been migrated, deleting the address information of the target virtual machine from the host table, and sending the address deletion event to the multicast management module; the target virtual machine is any one of the virtual machines;
the multicast management module is used for:
searching a multicast table item corresponding to the target virtual machine;
and deleting the multicast table entry when determining that no other virtual machine in the server monitors the multicast group added by the target virtual machine.
9. An edge switch, comprising: a memory and a processor, the memory storing machine readable instructions executable by the processor, the processor executing the machine readable instructions when the edge switch is running to implement the multicast entry processing method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, which is executed by a processor to implement the multicast entry processing method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210864634.6A CN115242708B (en) | 2022-07-21 | 2022-07-21 | Multicast table item processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210864634.6A CN115242708B (en) | 2022-07-21 | 2022-07-21 | Multicast table item processing method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115242708A true CN115242708A (en) | 2022-10-25 |
| CN115242708B CN115242708B (en) | 2023-10-20 |
Family
ID=83675343
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210864634.6A Active CN115242708B (en) | 2022-07-21 | 2022-07-21 | Multicast table item processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115242708B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101242419A (en) * | 2008-03-19 | 2008-08-13 | 中兴通讯股份有限公司 | Fast multicast processing method |
| US20130242995A1 (en) * | 2012-03-15 | 2013-09-19 | Fujitsu Limited | Multicast technique managing multicast address |
| US20140098815A1 (en) * | 2012-10-10 | 2014-04-10 | Telefonaktiebolaget L M Ericsson (Publ) | Ip multicast service leave process for mpls-based virtual private cloud networking |
| US20140348164A1 (en) * | 2012-01-18 | 2014-11-27 | Hangzhou H3C Technologies Co., Ltd. | Maintaining a multicast forwarding table and a pim router |
| CN104348737A (en) * | 2013-08-02 | 2015-02-11 | 华为技术有限公司 | Multicast message transmission method and switches |
| CN104601476A (en) * | 2013-10-31 | 2015-05-06 | 华为技术有限公司 | Multicast data message forwarding method and device and switch |
| CN106161259A (en) * | 2015-03-27 | 2016-11-23 | 杭州华三通信技术有限公司 | The multicast data packet forwarding method and apparatus of virtual extended LAN VXLAN |
| CN107612809A (en) * | 2017-10-31 | 2018-01-19 | 新华三技术有限公司 | A kind of multicast list synchronous method and equipment |
| CN109194559A (en) * | 2018-08-29 | 2019-01-11 | 迈普通信技术股份有限公司 | Method of multicasting and VTEP equipment |
| US20210149702A1 (en) * | 2019-11-20 | 2021-05-20 | Red Hat, Inc. | Virtual machine migration downtime reduction using a multicast address |
| CN113507425A (en) * | 2021-06-22 | 2021-10-15 | 新华三大数据技术有限公司 | Overlay multicast method, device and equipment |
-
2022
- 2022-07-21 CN CN202210864634.6A patent/CN115242708B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101242419A (en) * | 2008-03-19 | 2008-08-13 | 中兴通讯股份有限公司 | Fast multicast processing method |
| US20140348164A1 (en) * | 2012-01-18 | 2014-11-27 | Hangzhou H3C Technologies Co., Ltd. | Maintaining a multicast forwarding table and a pim router |
| US20130242995A1 (en) * | 2012-03-15 | 2013-09-19 | Fujitsu Limited | Multicast technique managing multicast address |
| US20140098815A1 (en) * | 2012-10-10 | 2014-04-10 | Telefonaktiebolaget L M Ericsson (Publ) | Ip multicast service leave process for mpls-based virtual private cloud networking |
| CN104348737A (en) * | 2013-08-02 | 2015-02-11 | 华为技术有限公司 | Multicast message transmission method and switches |
| CN104601476A (en) * | 2013-10-31 | 2015-05-06 | 华为技术有限公司 | Multicast data message forwarding method and device and switch |
| CN106161259A (en) * | 2015-03-27 | 2016-11-23 | 杭州华三通信技术有限公司 | The multicast data packet forwarding method and apparatus of virtual extended LAN VXLAN |
| CN107612809A (en) * | 2017-10-31 | 2018-01-19 | 新华三技术有限公司 | A kind of multicast list synchronous method and equipment |
| CN109194559A (en) * | 2018-08-29 | 2019-01-11 | 迈普通信技术股份有限公司 | Method of multicasting and VTEP equipment |
| US20210149702A1 (en) * | 2019-11-20 | 2021-05-20 | Red Hat, Inc. | Virtual machine migration downtime reduction using a multicast address |
| CN113507425A (en) * | 2021-06-22 | 2021-10-15 | 新华三大数据技术有限公司 | Overlay multicast method, device and equipment |
Non-Patent Citations (3)
| Title |
|---|
| N. BANERJEE; S.K. DAS: "Analysis of mobile multicasting in IP-based wireless cellular networks", 《2002 IEEE INTERNATIONAL CONFERENCE ON COMMUNICATIONS. CONFERENCE PROCEEDINGS. ICC 2002 (CAT. NO.02CH37333)》 * |
| 惠作奎: "VDSL系统设计实现与应用研究", 《CNKI》 * |
| 王建文;王政锋;: "三层交换机基于vlan的组播实现", 计算机系统应用, no. 11 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115242708B (en) | 2023-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3229405B1 (en) | Software defined data center and scheduling and traffic-monitoring method for service cluster therein | |
| EP3261290B1 (en) | Software defined data center and method for deploying service cluster therein | |
| US10241820B2 (en) | Determining the realization status of logical entities in logical networks | |
| US10089123B2 (en) | Virtual cable modem termination system redundancy in a cable modem network environment | |
| US6507863B2 (en) | Dynamic multicast routing facility for a distributed computing environment | |
| US8213336B2 (en) | Distributed data center access switch | |
| CN114697252B (en) | Computer network method, software defined network controller and storage medium | |
| CN112235122B (en) | Automatic selection of software images for network devices | |
| US10880158B2 (en) | Identifying the realization status of logical entities based on a global realization number | |
| CN106664216B (en) | VNF switching method and device | |
| US11665088B2 (en) | Assisted replication in software defined network | |
| US9960964B2 (en) | System, method and apparatus to manage services in a network | |
| US10999195B1 (en) | Multicast VPN support in data centers using edge replication tree | |
| WO2018137520A1 (en) | Service recovery method and apparatus | |
| WO2020057445A1 (en) | Communication system, method, and device | |
| US20240187479A1 (en) | Efficient virtual ip address management for service clusters | |
| AU2017233504B2 (en) | Identifying the realization status of logical entities based on a global realization number | |
| US10608869B2 (en) | Handling control-plane connectivity loss in virtualized computing environments | |
| CN110958151A (en) | Keep-alive detection method, device, node, storage medium and communication system | |
| CN115242708B (en) | Multicast table item processing method and device, electronic equipment and storage medium | |
| CN114553707B (en) | Method and device for generating topology information of network and delimiting network faults | |
| CN113805788B (en) | Distributed storage system and exception handling method and related device thereof | |
| US11281451B2 (en) | Distributed backup and restoration in virtualized computing environments | |
| CN116033000A (en) | Cloud platform and cloud platform service calling method |
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 |