Highly available multicast traffic forwarding method and system based on cloud platform

Abstract

The application discloses a high-availability multicast traffic forwarding method and system based on a cloud platform, belongs to the technical field of cloud computing, and aims to solve the high availability of multicast traffic forwarding of the cloud platform. The method comprises the following steps: creating two multicast traffic forwarding virtual machines under a VPC virtual network of the cloud platform; releasing the security group of each multicast traffic forwarding virtual machine; taking one of the multicast traffic forwarding modules as a master virtual machine and the other as a standby virtual machine, and forwarding multicast traffic to a core switch of the cloud platform through the master virtual machine; when the running state of the master virtual machine is abnormal, switching the standby virtual machine to the master virtual machine, deleting the original master virtual machine, and re-creating a new multicast traffic forwarding virtual machine as the standby virtual machine.

Description

Technical Field

[0001] This invention relates to the field of cloud computing technology, specifically to a high-availability multicast traffic forwarding method and system based on a cloud platform. Background Technology

[0002] With the rapid development of network communication technology, people are using network technology for communication in more and more scenarios, and various applications are emerging one after another. Broadcast, multicast, and unicast are the three main transmission methods in network communication, each with its unique characteristics and applicable scenarios. Broadcast is a one-to-all communication method. In broadcast, a host sends data packets to all other hosts in the network, and each host receives these data packets regardless of whether it needs the data. This communication method is suitable for situations where information needs to be sent to all devices in the network, such as cable television networks. Unicast, on the other hand, is a one-to-one communication method. In unicast, data is sent from one host to another specific host. This communication method is the most common in network communication, such as web browsing and email.

[0003] Multicast is a one-to-many communication method where a sender can send data packets to a specific multicast group on the network. Only hosts that have joined this multicast group can receive these data packets. This communication method is increasingly used in network communication applications, such as live streaming and video conferencing. Multicast technology has unique advantages for one-to-many use cases. Compared to broadcast, multicast can bypass the Layer 2 broadcast domain and perform Layer 3 traffic forwarding. Compared to unicast, multicast can utilize network resources more efficiently because data packets only need to be transmitted once on each network link, and are only copied when the link forks.

[0004] Current cloud computing platforms based on OpenStack do not support multicast traffic forwarding within or outside the cloud via their Neutron component, let alone high availability. High availability is crucial for cloud-based network communication, especially in one-to-many multicast scenarios. When a multicast source is deployed within a cloud VPC and simultaneously sending multicast packets to external networks, an interruption in multicast traffic forwarding will prevent all members of that multicast group from receiving the packets. This not only causes user losses but also significantly degrades the cloud platform's user experience.

[0005] High availability of multicast traffic forwarding on cloud platforms is a technical problem that needs to be solved. Summary of the Invention

[0006] The technical objective of this invention is to address the above-mentioned shortcomings by providing a highly available multicast traffic forwarding method and system based on a cloud platform, thereby resolving the technical problem of high availability in multicast traffic forwarding on cloud platforms.

[0007] In a first aspect, the present invention provides a highly available multicast traffic forwarding method based on a cloud platform, comprising the following steps:

[0008] Create two multicast traffic forwarding virtual machines in the VPC virtual network of the cloud platform;

[0009] Open the security group of each multicast traffic forwarding virtual machine, and each multicast traffic forwarding virtual machine can forward or receive multicast traffic from the VPC virtual network and the VLAN physical network.

[0010] For two multicast traffic forwarding virtual machines, one multicast traffic forwarding module is used as the primary virtual machine and the other multicast traffic forwarding virtual machine is used as the backup virtual machine. Multicast traffic is forwarded to the cloud platform core switch through the primary virtual machine. The cloud platform core switch is configured with a VLAN physical network gateway and supports the configuration of PIM protocol and OSPF protocol.

[0011] Monitor the running status of two multicast traffic forwarding virtual machines. When the running status of the primary virtual machine is abnormal, issue a configuration for the backup virtual machine, switch the backup virtual machine to the primary virtual machine, forward multicast traffic to the cloud platform core switch through the new primary virtual machine, delete the original primary virtual machine, and recreate a new multicast traffic forwarding virtual machine as the backup virtual machine.

[0012] As a preferred option, when creating two multicast traffic forwarding virtual machines under the VPC of the cloud platform, three virtual network interfaces are configured on each multicast traffic forwarding virtual machine, namely the first virtual network interface, the second virtual machine network interface, and the third virtual network interface.

[0013] The first virtual network interface card belongs to the VPC virtual network and is used to forward or receive multicast traffic within the VPC virtual network.

[0014] The second virtual network interface card belongs to the VLAN physical network and is connected to the core switch of the cloud platform. It is used to forward or receive multicast traffic from the VLAN physical network.

[0015] The third virtual network interface card belongs to the control network and is used to interact with the multicast monitoring module configured on the cloud platform control side. It is used to send the status data of the multicast traffic forwarding virtual machine to the multicast monitoring module and to distribute the configuration of the multicast traffic forwarding virtual machine by the multicast monitoring module to the corresponding multicast traffic forwarding virtual machine.

[0016] As a preferred option, each multicast traffic forwarding virtual machine is configured with an OVS startup module. The OVS module is used to configure the primary virtual machine to provide multicast traffic forwarding functionality to forward multicast traffic to the cloud platform core switch, while the backup virtual machine is configured not to provide multicast traffic forwarding functionality.

[0017] As a preferred option, multicast traffic is UDP packets, which are unidirectional traffic with no return path.

[0018] Preferably, the method is applied to two scenarios: Scenario 1 is a VPC virtual network that is a VXLAN network and the multicast source is within the VPC virtual network; Scenario 2 is a VPC virtual network that is a VXLAN network and the multicast receiver is within the VPC virtual network. In both scenarios, there are multiple routing devices on the physical link from the multicast source to the multicast receiver, and each routing device is configured with PIM protocol and OSPF protocol.

[0019] In a second aspect, the present invention provides a high-availability multicast traffic forwarding system based on a cloud platform, used to realize multicast traffic forwarding through a high-availability multicast traffic forwarding method based on a cloud platform as described in any one of the first aspects, the system comprising a multicast traffic forwarding virtual machine, a cloud platform core switch, and a multicast monitoring module.

[0020] There are two multicast traffic forwarding virtual machines, both configured in the VPC virtual network of the cloud platform. Each multicast traffic forwarding virtual machine has its own security group open, and each multicast traffic forwarding virtual machine can forward or receive multicast traffic from the VPC virtual network and the VLAN physical network.

[0021] For the two multicast traffic forwarding virtual machines, one multicast traffic forwarding module is used as the primary virtual machine and the other multicast traffic forwarding virtual machine is used as the backup virtual machine. The primary virtual machine is used to forward multicast traffic to the cloud platform core switch. The cloud platform core switch is configured with a VLAN physical network gateway and supports the configuration of PIM protocol and OSPF protocol.

[0022] The multicast monitoring module is used to monitor the running status of two multicast traffic forwarding virtual machines. When the running status of the primary virtual machine is abnormal, it is used to issue configurations to the backup virtual machine, switch the backup virtual machine to the primary virtual machine, and the new primary virtual machine is used to forward multicast traffic to the cloud platform core switch. It is also used to delete the original primary virtual machine and recreate a new multicast traffic forwarding virtual machine as the backup virtual machine.

[0023] As a preferred option, each multicast traffic forwarding virtual machine is configured with three virtual network interfaces, namely the first virtual network interface, the second virtual network interface, and the third virtual network interface.

[0024] The first virtual network interface card belongs to the VPC virtual network and is used to forward or receive multicast traffic within the VPC virtual network.

[0025] The second virtual network interface card belongs to the VLAN physical network and is connected to the core switch of the cloud platform. It is used to forward or receive multicast traffic from the VLAN physical network.

[0026] The third virtual network interface card belongs to the control network and is used to interact with the multicast monitoring module configured on the cloud platform control side. It is used to send the status data of the multicast traffic forwarding virtual machine to the multicast monitoring module and to distribute the configuration of the multicast traffic forwarding virtual machine by the multicast monitoring module to the corresponding multicast traffic forwarding virtual machine.

[0027] Preferably, each multicast traffic forwarding virtual machine is configured with an OVS startup module. The OVS module is used to configure the primary virtual machine to provide multicast traffic forwarding function to forward multicast traffic to the cloud platform core switch, and to configure the backup virtual machine not to provide multicast traffic forwarding function.

[0028] As a preferred option, multicast traffic is UDP packets, which are unidirectional traffic with no return path.

[0029] Preferably, the system is applied to two scenarios: Scenario 1 is a VPC virtual network that is a VXLAN network and the multicast source is within the VPC virtual network; Scenario 2 is a VPC virtual network that is a VXLAN network and the multicast receiver is within the VPC virtual network. In both scenarios, there are multiple routing devices on the physical link from the multicast source to the multicast receiver, and each routing device is configured with PIM protocol and OSPF protocol.

[0030] The high-availability multicast traffic forwarding method and system based on cloud platform of the present invention has the following advantages:

[0031] 1. Provide multicast traffic forwarding functionality for cloud platforms, enabling multicast communication between inside and outside the cloud;

[0032] 2. Provide high availability for the multicast traffic forwarding function of the cloud platform and improve the reliability of multicast communication on the cloud platform. Attached Figure Description

[0033] To more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0034] The invention will be further described below with reference to the accompanying drawings.

[0035] Figure 1 This is a flowchart of a high-availability multicast traffic forwarding method based on a cloud platform, as shown in Example 1.

[0036] Figure 2 This is a flowchart of the multicast traffic forwarding process where the multicast source is located in the cloud center in Example 1, a high-availability multicast traffic forwarding method based on a cloud platform.

[0037] Figure 3 This is a flowchart illustrating the multicast traffic forwarding process where the multicast receiver is located within the cloud center in Example 1, a high-availability multicast traffic forwarding method based on a cloud platform.

[0038] Figure 4 This is a block diagram illustrating the principle of a high-availability multicast traffic forwarding system based on a cloud platform, as shown in Example 2. Detailed Implementation

[0039] The present invention will be further described below with reference to the accompanying drawings and specific embodiments, so that those skilled in the art can better understand and implement the present invention. However, the embodiments are not intended to limit the present invention. In the absence of conflict, the embodiments of the present invention and the technical features in the embodiments can be combined with each other.

[0040] This invention provides a high-availability multicast traffic forwarding method and system based on a cloud platform, which solves the technical problem of high availability of multicast traffic forwarding in cloud platforms.

[0041] Example 1:

[0042] This invention discloses a high-availability multicast traffic forwarding method based on a cloud platform, comprising the following steps:

[0043] S100. Create two multicast traffic forwarding virtual machines under the VPC virtual network of the cloud platform;

[0044] S200: Open the security group of each multicast traffic forwarding virtual machine, so that each multicast traffic forwarding virtual machine can forward or receive multicast traffic from the VPC virtual network and the VLAN physical network.

[0045] S300: For two multicast traffic forwarding virtual machines, one multicast traffic forwarding module is used as the primary virtual machine and the other multicast traffic forwarding virtual machine is used as the backup virtual machine. Multicast traffic is forwarded to the cloud platform core switch through the primary virtual machine. The cloud platform core switch is configured with a VLAN physical network gateway and supports the configuration of PIM protocol and OSPF protocol.

[0046] The S400 monitors the running status of two multicast traffic forwarding virtual machines. When the running status of the primary virtual machine is abnormal, it issues a configuration to the backup virtual machine, switches the backup virtual machine to the primary virtual machine, forwards multicast traffic to the cloud platform core switch through the new primary virtual machine, deletes the original primary virtual machine, and recreates a new multicast traffic forwarding virtual machine as the backup virtual machine.

[0047] In step S100 of this embodiment, when creating two multicast traffic forwarding virtual machines under the VPC of the cloud platform, three virtual network interfaces are configured on each multicast traffic forwarding virtual machine: a first virtual network interface, a second virtual network interface, and a third virtual network interface. The first virtual network interface belongs to the VPC virtual network and is used to forward or receive multicast traffic within the VPC virtual network. The second virtual network interface belongs to the VLAN physical network and is connected to the core switch of the cloud platform, and is used to forward or receive multicast traffic from the VLAN physical network. The third virtual network interface belongs to the control network and is used to interact with the multicast monitoring module configured on the control side of the cloud platform. It is used to send the status data of the multicast traffic forwarding virtual machine to the multicast monitoring module and to distribute the configuration of the multicast traffic forwarding virtual machine to the corresponding multicast traffic forwarding virtual machine by the multicast monitoring module.

[0048] In this embodiment, each multicast traffic forwarding virtual machine is configured with an OVS startup module. The OVS module configures the primary virtual machine to provide multicast traffic forwarding functionality to forward multicast traffic to the cloud platform core switch, and configures the backup virtual machine not to provide multicast traffic forwarding functionality.

[0049] In this embodiment, the multicast traffic is UDP packets, which is unidirectional and has no return path. This method is applied to two scenarios: Scenario 1 is where the VPC virtual network is a VXLAN network and the multicast source is within the VPC virtual network; Scenario 2 is where the VPC virtual network is a VXLAN network and the multicast receiver is within the VPC virtual network. In both scenarios, there are multiple routing devices on the physical link from the multicast source to the multicast receiver, and each routing device is configured with both PIM and OSPF protocols.

[0050] When a VPC is a VXLAN network and the multicast source is within the VPC, the prerequisites in this scenario are: the core switch (router) is configured with PIM and OSPF protocols to ensure unobstructed routing, normal reverse path checks, and normal PIM protocol operation; there may be multiple routing devices on the physical link from the multicast source to the multicast receiver, and all of them need to be configured with PIM and OSPF protocols to ensure route reachability.

[0051] The operation is as follows in the following scenario:

[0052] (1) Add two new gw virtual machines in the VPC to provide multicast traffic forwarding function, and open the security group of the gw virtual machines to ensure that multicast and cross-layer 2 packets can pass through without obstacles;

[0053] (2) Insert two virtual network cards into each GW virtual machine. One belongs to the VXLAN network where the multicast source is located, and the other belongs to the VLAN network and is connected to the core switch.

[0054] (3) Install an OVS module on each gw virtual machine. By configuring the OVS module, the Master-gw virtual machine is responsible for forwarding multicast traffic to the core switch, so that the Slave-gw virtual machine does not provide multicast traffic forwarding function.

[0055] (4) Insert a virtual network card of the control network into each GW virtual machine to interact with the VPC multicast monitoring module. The VPC multicast monitoring module provides the main and backup switching capability for the overall solution.

[0056] In Scenario 2, the VPC is a VxLAN network, and the multicast receiver is within the VPC. Prerequisites: the core switch (router) is configured with PIM and OSPF protocols to ensure routing connectivity, reverse path checks are normal, and PIM protocol functionality is achieved. The physical link from the multicast source to the multicast receiver may involve multiple routing devices, all of which must be configured with PIM and OSPF protocols to ensure route reachability. The operation in Scenario 2 is as follows:

[0057] (1) Add two new gw virtual machines in the VPC to provide multicast traffic forwarding function, and open the security group of the gw virtual machines to ensure that multicast and cross-layer 2 packets can pass through without obstacles;

[0058] (2) Two virtual network cards are inserted into each GW virtual machine. One belongs to the VXLAN network where the multicast receiver is located; the other belongs to the VLAN network and is connected to the core switch.

[0059] (3) Install the OVS module on each gw virtual machine. By configuring the OVS module, the Master-gw virtual machine forwards multicast traffic to the multicast receiver in the VPC, so that the Slave-gw virtual machine does not have the function of forwarding multicast traffic.

[0060] (4) Insert a virtual network card of the control network into each GW virtual machine to interact with the VPC multicast monitoring module. The VPC multicast monitoring module is responsible for switching and scheduling between primary and backup according to the actual situation.

[0061] In this implementation, the forwarding virtual machine provides multicast traffic forwarding functionality. It has three virtual network interfaces: eth0 belongs to the private VXLAN network created by the VPC, eth1 belongs to the VLAN network where the cloud platform's core switch resides, and eth2 belongs to the control network, interacting with the VPC multicast monitoring module to receive messages and configurations, ensuring high availability for the overall solution. The steps for creating the multicast forwarding virtual machine are as follows:

[0062] (1) Create two multicast forwarding virtual machines through the VPC control page;

[0063] (2) VPC creates three network cards inside each forwarding virtual machine: one belongs to the VPC's VXLAN network, one belongs to the VLAN network and is connected to the core switch, and one belongs to the control network, which is responsible for receiving messages and configurations issued by the VPC's primary and backup control model.

[0064] (3) VPC removes security group restrictions for two forwarding virtual machines;

[0065] (4) The VPC multicast monitoring module starts the monitoring program. After both multicast forwarding virtual machines are started, the VPC multicast monitoring module sends a running status (healthCheck interface) query message to the two virtual machines, then selects one of them as the Master-gw virtual machine and issues the relevant OVS configuration (distributeConfig interface). At this time, the virtual machine has the function of forwarding multicast traffic; at the same time, the other virtual machine is used as the Slave-gw virtual machine, and the OVS configuration is issued to disable its multicast traffic forwarding function.

[0066] (5) The VPC multicast monitoring module periodically obtains the running status (healthCheck interface) of the two virtual machines Master-gw and Slave-gw. If the Master-gw virtual machine fails and affects the forwarding of multicast traffic, the VPC multicast monitoring module will switch Slave-gw to the new Master-gw and issue OVS configuration to enable it to forward multicast traffic.

[0067] (6) The VPC master-slave monitoring module will delete the old Master-gw virtual machine that has failed, and then recreate a multicast forwarding virtual machine as the new Slave-gw and issue the corresponding OVS configuration.

[0068] In this embodiment, the multicast traffic forwarding virtual machine receives relevant OVS configurations through the control network to realize multicast traffic forwarding between VXLAN and VLAN networks. The interaction design between the multicast forwarding virtual machine and the VPC multicast monitoring module enables the VPC multicast monitoring module to obtain the virtual machine's running status (healthCheck interface), the virtual machine's primary / standby status (checkGatewayStatus interface), and to send multicast forwarding configurations to the virtual machine (distributeConfig interface), thereby achieving high availability of multicast traffic forwarding on the cloud platform.

[0069] Example 2:

[0070] This invention discloses a highly available multicast traffic forwarding system based on a cloud platform, such as... Figure 4 The system includes a multicast traffic forwarding virtual machine, a cloud platform core switch, and a multicast monitoring module. The system can execute the method disclosed in Example 1.

[0071] There are two multicast traffic forwarding virtual machines, both configured in the VPC virtual network of the cloud platform. Each multicast traffic forwarding virtual machine has its own security group open, and each multicast traffic forwarding virtual machine can forward or receive multicast traffic from the VPC virtual network and the VLAN physical network.

[0072] Each multicast traffic forwarding virtual machine is configured with three virtual network interface cards (NICs): a first virtual NIC, a second virtual NIC, and a third virtual NIC. The first virtual NIC belongs to the VPC virtual network and is used to forward or receive multicast traffic within the VPC virtual network. The second virtual NIC belongs to the VLAN physical network and is connected to the cloud platform's core switch, used to forward or receive multicast traffic from the VLAN physical network. The third virtual NIC belongs to the control network and is used to interact with the multicast monitoring module configured on the cloud platform's control side. It is used to send the status data of the multicast traffic forwarding virtual machine to the multicast monitoring module and to distribute the configuration settings of the multicast traffic forwarding virtual machine from the multicast monitoring module to the corresponding multicast traffic forwarding virtual machine.

[0073] Each multicast traffic forwarding virtual machine is configured with an OVS module. The OVS module is used to configure the primary virtual machine to provide multicast traffic forwarding function to forward multicast traffic to the cloud platform core switch, and to configure the backup virtual machine not to provide multicast traffic forwarding function.

[0074] For the two multicast traffic forwarding virtual machines, one multicast traffic forwarding module serves as the primary virtual machine and the other serves as the backup virtual machine. The primary virtual machine is used to forward multicast traffic to the cloud platform core switch. The cloud platform core switch is configured with a VLAN physical network gateway and supports the configuration of PIM and OSPF protocols.

[0075] The multicast monitoring module is used to monitor the running status of two multicast traffic forwarding virtual machines. When the running status of the primary virtual machine is abnormal, it is used to issue configurations to the backup virtual machine, switch the backup virtual machine to the primary virtual machine, and the new primary virtual machine is used to forward multicast traffic to the cloud platform core switch. It is also used to delete the original primary virtual machine and recreate a new multicast traffic forwarding virtual machine as the backup virtual machine.

[0076] In this embodiment, multicast traffic consists of UDP packets, which are unidirectional and have no return path. This system is applied to two scenarios: Scenario 1 involves a VPC virtual network (VXLAN) with the multicast source within the VPC; Scenario 2 involves a VPC virtual network (VXLAN) with the multicast receiver within the VPC. In both scenarios, multiple routing devices exist on the physical link from the multicast source to the multicast receiver, and each routing device is configured with both PIM and OSPF protocols.

[0077] When a VPC is a VXLAN network and the multicast source is within the VPC, the prerequisites in this scenario are: the core switch (router) is configured with PIM and OSPF protocols to ensure unobstructed routing, normal reverse path checks, and normal PIM protocol operation; there may be multiple routing devices on the physical link from the multicast source to the multicast receiver, and all of them need to be configured with PIM and OSPF protocols to ensure route reachability.

[0078] The operation is as follows in the following scenario:

[0079] (1) Add two new gw virtual machines in the VPC to provide multicast traffic forwarding function, and open the security group of the gw virtual machines to ensure that multicast and cross-layer 2 packets can pass through without obstacles;

[0080] (2) Insert two virtual network cards into each GW virtual machine. One belongs to the VXLAN network where the multicast source is located, and the other belongs to the VLAN network and is connected to the core switch.

[0081] (3) Install an OVS module on each gw virtual machine. By configuring the OVS module, the Master-gw virtual machine is responsible for forwarding multicast traffic to the core switch, so that the Slave-gw virtual machine does not provide multicast traffic forwarding function.

[0082] (4) Insert a virtual network card of the control network into each GW virtual machine to interact with the VPC multicast monitoring module. The VPC multicast monitoring module provides the main and backup switching capability for the overall solution.

[0083] In Scenario 2, the VPC is a VxLAN network, and the multicast receiver is within the VPC. Prerequisites: the core switch (router) is configured with PIM and OSPF protocols to ensure routing connectivity, reverse path checks are normal, and PIM protocol functionality is achieved. The physical link from the multicast source to the multicast receiver may involve multiple routing devices, all of which must be configured with PIM and OSPF protocols to ensure route reachability. The operation in Scenario 2 is as follows:

[0084] (1) Add two new gw virtual machines in the VPC to provide multicast traffic forwarding function, and open the security group of the gw virtual machines to ensure that multicast and cross-layer 2 packets can pass through without obstacles;

[0085] (2) Two virtual network cards are inserted into each GW virtual machine. One belongs to the VXLAN network where the multicast receiver is located; the other belongs to the VLAN network and is connected to the core switch.

[0086] (3) Install the OVS module on each gw virtual machine. By configuring the OVS module, the Master-gw virtual machine forwards multicast traffic to the multicast receiver in the VPC, so that the Slave-gw virtual machine does not have the function of forwarding multicast traffic.

[0087] (4) Insert a virtual network card of the control network into each GW virtual machine to interact with the VPC multicast monitoring module. The VPC multicast monitoring module is responsible for switching and scheduling between primary and backup according to the actual situation.

[0088] In this implementation, the forwarding virtual machine provides multicast traffic forwarding functionality. It has three virtual network interfaces: eth0 belongs to the private VXLAN network created by the VPC, eth1 belongs to the VLAN network where the cloud platform's core switch resides, and eth2 belongs to the control network, interacting with the VPC multicast monitoring module to receive messages and configurations, ensuring high availability for the overall solution. The steps for creating the multicast forwarding virtual machine are as follows:

[0089] (1) Create two multicast forwarding virtual machines through the VPC control page;

[0090] (2) VPC creates three network cards inside each forwarding virtual machine: one belongs to the VPC's VXLAN network, one belongs to the VLAN network and is connected to the core switch, and one belongs to the control network, which is responsible for receiving messages and configurations issued by the VPC's primary and backup control model.

[0091] (3) VPC removes security group restrictions for two forwarding virtual machines;

[0092] (4) The VPC multicast monitoring module starts the monitoring program. After both multicast forwarding virtual machines are started, the VPC multicast monitoring module sends a running status (healthCheck interface) query message to the two virtual machines, then selects one of them as the Master-gw virtual machine and issues the relevant OVS configuration (distributeConfig interface). At this time, the virtual machine has the function of forwarding multicast traffic; at the same time, the other virtual machine is used as the Slave-gw virtual machine, and the OVS configuration is issued to disable its multicast traffic forwarding function.

[0093] (5) The VPC multicast monitoring module periodically obtains the running status (healthCheck interface) of the two virtual machines Master-gw and Slave-gw. If the Master-gw virtual machine fails and affects the forwarding of multicast traffic, the VPC multicast monitoring module will switch Slave-gw to the new Master-gw and issue OVS configuration to enable it to forward multicast traffic.

[0094] (6) The VPC master-slave monitoring module will delete the old Master-gw virtual machine that has failed, and then recreate a multicast forwarding virtual machine as the new Slave-gw and issue the corresponding OVS configuration.

[0095] In this embodiment, the multicast traffic forwarding virtual machine receives relevant OVS configurations through the control network to realize multicast traffic forwarding between VXLAN and VLAN networks. The interaction design between the multicast forwarding virtual machine and the VPC multicast monitoring module enables the VPC multicast monitoring module to obtain the virtual machine's running status (healthCheck interface), the virtual machine's primary / standby status (checkGatewayStatus interface), and to send multicast forwarding configurations to the virtual machine (distributeConfig interface), thereby achieving high availability of multicast traffic forwarding on the cloud platform.

[0096] The present invention has been shown and described in detail above with reference to the accompanying drawings and preferred embodiments. However, the present invention is not limited to these disclosed embodiments. Based on the above embodiments, those skilled in the art will know that more embodiments of the present invention can be obtained by combining the means in the different embodiments described above, and these embodiments are also within the protection scope of the present invention.

Claims

1. A highly available multicast traffic forwarding method based on a cloud platform, characterized in that, Includes the following steps: Create two multicast traffic forwarding virtual machines in the VPC virtual network of the cloud platform; Open the security group of each multicast traffic forwarding virtual machine, and each multicast traffic forwarding virtual machine can forward or receive multicast traffic from the VPC virtual network and the VLAN physical network. For two multicast traffic forwarding virtual machines, one multicast traffic forwarding module is used as the primary virtual machine and the other multicast traffic forwarding virtual machine is used as the backup virtual machine. Multicast traffic is forwarded to the cloud platform core switch through the primary virtual machine. The cloud platform core switch is configured with a VLAN physical network gateway and supports the configuration of PIM protocol and OSPF protocol. Monitor the running status of two multicast traffic forwarding virtual machines. When the running status of the primary virtual machine is abnormal, issue the configuration to the backup virtual machine, switch the backup virtual machine to the primary virtual machine, forward multicast traffic to the cloud platform core switch through the new primary virtual machine, delete the original primary virtual machine, and recreate a new multicast traffic forwarding virtual machine as the backup virtual machine. When creating two multicast traffic forwarding virtual machines under the VPC of the cloud platform, three virtual network interfaces are configured on each multicast traffic forwarding virtual machine, namely the first virtual network interface, the second virtual machine network interface, and the third virtual network interface. The first virtual network interface card belongs to the VPC virtual network and is used to forward or receive multicast traffic within the VPC virtual network. The second virtual network interface card belongs to the VLAN physical network and is connected to the core switch of the cloud platform. It is used to forward or receive multicast traffic from the VLAN physical network. The third virtual network interface card belongs to the control network and is used to interact with the multicast monitoring module configured on the cloud platform control side. It is used to send the status data of the multicast traffic forwarding virtual machine to the multicast monitoring module and to distribute the configuration of the multicast traffic forwarding virtual machine by the multicast monitoring module to the corresponding multicast traffic forwarding virtual machine.

2. The high-availability multicast traffic forwarding method according to claim 1, characterized in that, Each multicast traffic forwarding virtual machine is configured with an OVS module. The OVS module configures the primary virtual machine to provide multicast traffic forwarding functionality to forward multicast traffic to the cloud platform core switch, and configures the backup virtual machine not to provide multicast traffic forwarding functionality.

3. The high-availability multicast traffic forwarding method according to any one of claims 1-2, characterized in that, Multicast traffic consists of UDP packets, which are unidirectional and have no return path.

4. The high-availability multicast traffic forwarding method according to any one of claims 1-2, characterized in that, The method is applied to two scenarios: Scenario 1 is a VPC virtual network that is a VXLAN network and the multicast source is within the VPC virtual network; Scenario 2 is a VPC virtual network that is a VXLAN network and the multicast receiver is within the VPC virtual network. In both scenarios, there are multiple routing devices on the physical link from the multicast source to the multicast receiver, and each routing device is configured with both PIM and OSPF protocols.

5. A high-availability multicast traffic forwarding system based on a cloud platform, characterized in that, The system includes a multicast traffic forwarding virtual machine, a cloud platform core switch, and a multicast monitoring module. There are two multicast traffic forwarding virtual machines, both configured in the VPC virtual network of the cloud platform. Each multicast traffic forwarding virtual machine has its own security group open, and each multicast traffic forwarding virtual machine can forward or receive multicast traffic from the VPC virtual network and the VLAN physical network. For the two multicast traffic forwarding virtual machines, one multicast traffic forwarding module is used as the primary virtual machine and the other multicast traffic forwarding virtual machine is used as the backup virtual machine. The primary virtual machine is used to forward multicast traffic to the cloud platform core switch. The cloud platform core switch is configured with a VLAN physical network gateway and supports the configuration of PIM protocol and OSPF protocol. The multicast monitoring module is used to monitor the running status of two multicast traffic forwarding virtual machines. When the running status of the primary virtual machine is abnormal, it is used to issue configurations to the backup virtual machine, switch the backup virtual machine to the primary virtual machine, and the new primary virtual machine is used to forward multicast traffic to the cloud platform core switch. It is also used to delete the original primary virtual machine and recreate a new multicast traffic forwarding virtual machine as the backup virtual machine. Each multicast traffic forwarding virtual machine is configured with three virtual network interfaces, namely the first virtual network interface, the second virtual network interface, and the third virtual network interface. The first virtual network interface card belongs to the VPC virtual network and is used to forward or receive multicast traffic within the VPC virtual network. The second virtual network interface card belongs to the VLAN physical network and is connected to the core switch of the cloud platform. It is used to forward or receive multicast traffic from the VLAN physical network. The third virtual network interface card belongs to the control network and is used to interact with the multicast monitoring module configured on the cloud platform control side. It is used to send the status data of the multicast traffic forwarding virtual machine to the multicast monitoring module and to distribute the configuration of the multicast traffic forwarding virtual machine by the multicast monitoring module to the corresponding multicast traffic forwarding virtual machine.

6. The high-availability multicast traffic forwarding system based on a cloud platform according to claim 5, characterized in that, Each multicast traffic forwarding virtual machine is configured with an OVS module. The OVS module is used to configure the primary virtual machine to provide multicast traffic forwarding function to forward multicast traffic to the cloud platform core switch, and to configure the backup virtual machine not to provide multicast traffic forwarding function.

7. The high-availability multicast traffic forwarding system based on a cloud platform according to any one of claims 5-6, characterized in that, Multicast traffic consists of UDP packets, which are unidirectional and have no return path.

8. The high-availability multicast traffic forwarding system based on a cloud platform according to any one of claims 5-6, characterized in that, The system is applied to two scenarios: Scenario 1 is a VPC virtual network that is a VXLAN network and the multicast source is within the VPC virtual network; Scenario 2 is a VPC virtual network that is a VXLAN network and the multicast receiver is within the VPC virtual network. In both scenarios, there are multiple routing devices on the physical link from the multicast source to the multicast receiver, and each routing device is configured with PIM protocol and OSPF protocol.

Images