Network migration method and device, electronic equipment and storage medium

Abstract

The invention provides a network migration method and device, electronic equipment and a storage medium. The method comprises the following steps: acquiring network configuration information of a traditional network from gateway equipment, converting the configuration of the traditional network into a network architecture of an SDN (Software Defined Network), keeping the stability and performance of the network through connection of each layer, gradually migrating a virtual machine under a to-be-migrated sub-network of the traditional network to a corresponding virtual sub-network in the SDN, and transferring the virtual machine under the to-be-migrated sub-network to the SDN. And finally, the new gateway and the old gateway are switched in a one-key mode, automatic network migration is stably completed on the premise that service operation is not affected, the service flow interruption time in the network migration process is shortened to the maximum extent, meanwhile, the dependence of the network migration process on artificial experience is reduced, and the network migration efficiency and accuracy are improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a network migration method, device, electronic device and storage medium. Background Art

[0002] Traditional network refers to the traditional network architecture. In traditional networks, the control plane and data plane of network devices are coupled together, network configuration and management are cumbersome, and it is difficult to quickly adapt to business changes. In addition, the network management of traditional networks is usually decentralized and lacks a unified management view, resulting in low management efficiency and high operation and maintenance costs.

[0003] In contrast, the Software Defined Network (SDN) architecture has obvious advantages. SDN separates the control plane and data plane of the network, and implements unified management and control of the network through a centralized controller, making the network more flexible and programmable, and able to quickly adapt to different business needs and environmental changes. Secondly, SDN provides a unified network management view and management interface, simplifies the network management process, and improves management efficiency. In addition, SDN has the advantages of low operation and maintenance costs and strong security. Therefore, more and more companies tend to use SDN network architecture to replace traditional network architecture to meet business needs and improve network management efficiency.

[0004] However, in the process of migrating services from traditional networks to SDN networks, due to the problems of old network equipment, chaotic architecture, and complex services in traditional networks, the network migration project is extremely large, the time span may be as long as several months, and there is an unavoidable risk of business interruption. Summary of the invention

[0005] In order to overcome the problems existing in the related art, the present application provides a network migration method, device, electronic device and storage medium.

[0006] According to a first aspect of an embodiment of the present application, a network migration method is provided, the method being applied to an SDN controller, the SDN controller being connected to a gateway device of a traditional network and an edge device of the SDN network, the method comprising:

[0007] Acquire network configuration information of the traditional network from the gateway device, wherein the network configuration information includes information of the subnet to be migrated, information of the target VLAN to which the subnet to be migrated belongs, and information of the VPN instance associated with the target VLAN;

[0008] Creating a virtual network architecture of the SDN network according to the network configuration information, wherein the virtual network architecture includes a virtual routing device generated according to the associated VPN instance, a virtual network generated according to the target VLAN, and a virtual subnet generated according to the subnet to be migrated;

[0009] Creating a Layer 3 VPN instance that enables Layer 3 traffic between the gateway device and the edge device;

[0010] Creating a VXLAN tunnel for connecting Layer 2 traffic between the gateway device and the edge device;

[0011] Migrating the virtual machines in the subnet to be migrated to the virtual subnet;

[0012] After all virtual machines in the subnet to be migrated are migrated to the virtual subnet, the gateway of the subnet to be migrated is shut down, the gateway of the virtual subnet is associated with the layer 3 VPN instance, and the gateway of the virtual subnet is started.

[0013] According to a second aspect of an embodiment of the present application, a network migration device is provided, the device being applied to an SDN controller, the SDN controller being connected to a gateway device of a traditional network and an edge device of an SDN network, the device comprising:

[0014] A configuration parsing module, used to obtain network configuration information of the traditional network from the gateway device, wherein the network configuration information includes information of the subnet to be migrated, information of the target VLAN to which the subnet to be migrated belongs, and information of the VPN instance associated with the target VLAN;

[0015] A generation module, configured to create a virtual network architecture of the SDN network according to the network configuration information, wherein the virtual network architecture includes a virtual routing device generated according to the associated VPN instance, a virtual network generated according to the target VLAN, and a virtual subnet generated according to the subnet to be migrated;

[0016] A layer 3 opening module, used to create a layer 3 VPN instance for opening up layer 3 traffic between the gateway device and the edge device;

[0017] A layer 2 connection module, used to create a VXLAN tunnel that connects the layer 2 traffic between the gateway device and the edge device;

[0018] A migration module, used to migrate the virtual machines in the subnet to be migrated to the virtual subnet;

[0019] The gateway start-stop module is used to shut down the gateway of the subnet to be migrated, associate the gateway of the virtual subnet with the three-layer VPN instance and start the gateway of the virtual subnet after all virtual machines in the subnet to be migrated are migrated to the virtual subnet.

[0020] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising a processor and a machine-readable storage medium, wherein the machine-readable storage medium stores machine-executable instructions that can be executed by the processor, and the processor is prompted by the machine-executable instructions to implement the steps of the network migration method described above.

[0021] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the network migration method described above are implemented.

[0022] The technical solution provided by the embodiments of the present application may have the following beneficial effects:

[0023] In an embodiment of the present application, a one-stop automated network migration solution is implemented by integrating a network migration service in an SDN controller. First, the gateway device configuration of the traditional network is intelligently analyzed, and the traditional network configuration is converted into the network architecture of the SDN network. Then, the stability and performance of the network are maintained through connections at each layer, and network services are gradually migrated from the traditional network to the SDN network. Finally, the new and old gateways are switched with one click, and the network migration is smoothly completed without affecting business operations, thereby minimizing the business traffic interruption time during the migration process. At the same time, the dependence of the network migration process on manual experience is reduced, thereby improving migration efficiency and accuracy.

[0024] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings, which are incorporated in the specification and constitute a part of this application, illustrate embodiments consistent with the application and, together with the description, serve to explain the principles of the application.

[0026] Figure 1 A flowchart of a network migration method provided in an embodiment of the present application;

[0027] Figure 2 A schematic diagram of a configuration analysis of a network migration method provided in an embodiment of the present application;

[0028] Figure 3 A schematic diagram of a three-layer network connection method for a network migration method provided in an embodiment of the present application;

[0029] Figure 4 A schematic diagram of connecting a layer 2 network of a network migration method provided in an embodiment of the present application;

[0030] Figure 5 A schematic diagram of gateway migration of a network migration method provided in an embodiment of the present application;

[0031] Figure 6 A schematic diagram of a network migration device provided in an embodiment of the present application;

[0032] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0033] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0034] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms of "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0035] It should be understood that, although the terms first, second, third, etc. may be used in the present application to describe various information, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" or "if" as used herein may be interpreted as "at the time of" or "when...".

[0036] First, the concepts involved in the embodiments of the present application are explained:

[0037] Software-Defined Networking (SDN) is an emerging network architecture that separates the network control plane from the forwarding plane, allowing network administrators to manage and configure network devices through centralized software control.

[0038] Virtual Local Area Network (VLAN) is a technology that divides a physical network into multiple independent virtual networks through logical division. VLAN can create multiple independent broadcast domains on a single physical network device (such as a switch), thereby improving the flexibility, security and efficiency of network management.

[0039] A Virtual Private Network (VPN) is a technology that allows devices to establish a secure, encrypted connection through a public network (such as the Internet) to achieve confidentiality, integrity and verification of data, thereby providing users with a private and secure communication channel.

[0040] VXLAN (Virtual Extensible LAN) is a network virtualization technology used to expand the scale of virtual local area networks in large data center environments. VXLAN tunnel is its core mechanism, which creates a virtual layer 2 network on the existing network infrastructure to transcend physical network limitations.

[0041] The Data Link Layer (L2) mainly handles data communication within the LAN, ensuring frame transmission between different devices in the same broadcast domain. The switch is a key L2 device that forwards data through MAC addresses.

[0042] The Network Layer (L3) handles data communication across networks and is responsible for IP address planning and routing selection. Routers are key L3 devices that forward data packets using IP addresses to ensure data transmission between different networks.

[0043] Virtual Switch Instance (VSI): A virtual switch instance that provides Layer 2 switching services for a VXLAN. It can be regarded as a virtual switch that performs Layer 2 forwarding based on VXLAN. VSI corresponds to VXLAN one by one.

[0044] Next, the embodiments of the present application are described in detail.

[0045] The present application embodiment provides a network migration method, which is applied to an SDN controller, such as Figure 1 As shown, the method comprises the following steps:

[0046] Step 110: Obtain network configuration information of the traditional network from the gateway device;

[0047] Step 120: Create a virtual network architecture of the SDN network according to the network configuration information;

[0048] Step 130: Create a Layer 3 VPN instance to connect Layer 3 traffic between the gateway device and the edge device.

[0049] Step 140: Create a VXLAN tunnel to connect the Layer 2 traffic between the gateway device and the edge device.

[0050] Step 150: Migrate the virtual machine in the subnet to be migrated to the virtual subnet;

[0051] Step 160: After all virtual machines in the subnet to be migrated are migrated to the virtual subnet, the gateway of the subnet to be migrated is shut down, the gateway of the virtual subnet is associated with the Layer 3 VPN instance, and the gateway of the virtual subnet is started.

[0052] In the embodiment of the present application, the SDN network divides the network devices into functional groups, including edge devices, and may further include load balancers, firewalls, core switches, leaf switches, layer 2 / layer 3 switches, etc. Among them, the edge devices are connected to the external network and are responsible for managing inbound and outbound traffic. In the embodiment of the present application, the SDN controller connects the gateway device of the traditional network and the edge device of the SDN network.

[0053] Specifically, the embodiment of the present application integrates a network migration service in an SDN controller, adds and manages a gateway device of a traditional network in the network migration service, obtains the device configuration of the gateway device of the traditional network through a netconf or cli command line, and obtains the network configuration information described in step 110. The network configuration information specifically includes information about the subnet to be migrated, information about the target VLAN to which the subnet to be migrated belongs, and information about the VPN instance associated with the target VLAN.

[0054] It is worth mentioning that in actual applications, the number of subnets to be migrated can be one or more, but each subnet to be migrated belongs to only one VLAN. In the embodiment of the present application, the VLAN to which the subnet to be migrated belongs is referred to as the target VLAN. The associated VPN instance is used to connect different subnets to be migrated, and the embodiment of the present application does not limit the number of associated VPN instances.

[0055] The virtual network architecture described in step 120 specifically includes a virtual routing device generated according to the associated VPN instance, a virtual network generated according to the target VLAN, and a virtual subnet generated according to the subnet to be migrated. There is a one-to-one correspondence between the associated VPN instance and the virtual routing device.

[0056] During the network migration process, the embodiment of the present application performs migration in units of subnets to be migrated. In the process of successively migrating virtual machines under the same subnet to be migrated to the virtual subnet corresponding to the subnet to be migrated, the virtual machines under the subnet to be migrated that remain in the traditional network can communicate with the virtual machines that have been migrated to the SDN network through VXLAN tunnels. After all virtual machines under the subnet to be migrated are migrated to the virtual subnet corresponding to the subnet to be migrated, gateway migration can be performed, that is, shutting down the gateway of the subnet to be migrated in the traditional network, and starting the gateway of the virtual network corresponding to the subnet to be migrated in the SDN network.

[0057] As mentioned above, each subnet to be migrated belongs to only one VLAN, but there may be multiple subnets to be migrated under one VLAN. For each target VLAN, the embodiment of the present application creates a VXLAN tunnel between the gateway device and the edge device. After all virtual machines under a subnet to be migrated are migrated to the virtual subnet corresponding to the subnet to be migrated, the gateway migration can be performed, and then it is determined whether there is a subnet to be migrated that has not been migrated under the current target VLAN. If the judgment result is yes, continue to migrate other subnets to be migrated under the current target VLAN until all subnets to be migrated under the current target VLAN are migrated.

[0058] As a specific implementation method, a VXLAN tunnel that opens up the Layer 2 traffic between the gateway device and the edge device can be created in the following manner: for the current target VLAN, interconnection ports that only allow traffic from the target VLAN to pass through are set on the gateway device and the edge device respectively, a service instance associated with the target VLAN is created on the edge device, and the service instance is associated with the virtual network generated based on the target VLAN.

[0059] As described above, the number of associated VPN instances may be multiple. Specifically, in the embodiment of the present application, for each associated VPN instance, a three-layer VPN instance that opens up the three-layer traffic between the gateway device and the edge device will be created. Correspondingly, after all the subnets to be migrated under a target VLAN are migrated to the SDN network, it is determined whether the current associated VPN instance has other related target VLANs that need to be migrated. If the judgment result is yes, other target VLANs related to the current associated VPN instance will continue to be migrated until all target VLANs related to the current associated VPN instance are migrated.

[0060] Specifically, a three-layer VPN instance that opens up three-layer traffic between a gateway device and an edge device can be created in the following manner: create a three-layer VPN instance; configure the three-layer traffic address of the gateway device as a first address, and configure the three-layer traffic address of the edge device as a second address; configure the next-hop address of the three-layer VPN instance leading to the subnet to be migrated on the edge device as the first address, and configure the next-hop address of the three-layer VPN instance leading to the subnet to be migrated on the gateway device as the second address.

[0061] As a specific implementation method, the gateway of the virtual subnet can be associated with the Layer 3 VPN instance in the following manner: for the current target VLAN, create a virtualized interface; associate the virtualized interface with the Layer 3 VPN instance; for the current subnet to be migrated, configure the IP address and subnet mask of the virtualized interface as the IP address and subnet mask of the subnet to be migrated; configure the MAC address of the virtualized interface. Specifically, the gateway of the virtual subnet can be started in the following manner: issue a distributed gateway function start command to start the gateway of the virtual subnet.

[0062] Combine the following Figure 2 , Figure 3 , Figure 4 and Figure 5 , the implementation process of the embodiment of the present application is described by taking a specific application as an example. The following specific application is only a possible scenario and should not be understood as a limitation of the present application.

[0063] In the embodiment of the present application, the SDN controller obtains the following information from the gateway device of the traditional network: Figure 2 The network configuration information shown on the left is then converted into Figure 2 The network service configuration information shown in the middle table is then automatically modeled based on the network service configuration information. Figure 2 The topology on the right shows the virtual network architecture of the SDN network. Finally, the virtual router, virtual network, and virtual subnet are created through the SDN controller RestAPI, and the configuration is sent to the network devices of the SDN network.

[0064] Specifically, a request is made to create a virtual network and corresponding subnets through the northbound interface (such as REST API) of the SDN controller. After receiving the request, the SDN controller distributes configuration instructions to the underlying network devices through the southbound interface (such as OpenFlow, NetConf) to create virtual networks and subnets.

[0065] Below Figure 2 Explain the meaning of:

[0066] Figure 2The code on the left illustrates the network configuration information of the traditional network. Specifically, the traditional network defines two VLANs, namely VLAN 10 and VLAN 20; VLAN 10 is named user_vlan (user VLAN) and VLAN 20 is named server_vlan (server VLAN). The traditional network also defines a VPN instance named vrf-eng (equivalent to the associated VPN instance mentioned above). The traditional network creates logical interfaces corresponding to VLAN 10 and VLAN 20, namely Vlanif10 and Vlanif20, respectively, and configures IP addresses 10.1.1.254 / 24 and 10.1.2.254 / 24 for Vlanif10 and Vlanif20 respectively, and binds the two logical interfaces to the VPN instance vrf-eng.

[0067] Figure 2 The middle table illustrates the network service configuration information generated based on the network configuration information of the traditional network, and specifically includes the following fields:

[0068] Subnet: This field is used to describe the network prefix of the subnet, including the network address and subnet mask; the traditional network in the embodiment of the present application includes two subnets, namely 10.1.1.0 / 24 and 10.1.2.0 / 24.

[0069] Subnet Gateway: This field is used to describe the gateway IP address of the subnet; in the embodiment of the present application, the gateways of the two subnets are 10.1.1.254 and 10.1.2.254 respectively.

[0070] VLAN: This field is used to describe which VLAN the subnet belongs to, that is, the VLAN number; in the embodiment of the present application, the VLAN numbers corresponding to the two subnets are 10 and 20 respectively.

[0071] VRF: This field is used to describe the name of the VPN instance associated with the VLAN interface; the two VLAN interfaces in the embodiment of the present application are bound to the VPN instance vrf-eng.

[0072] Interface name: This field is used to describe the name of the logical interface specified for the VLAN. The names of the two VLAN interfaces in the embodiment of the present application are Vlanif10 and Vlanif20 respectively.

[0073] Interface IP: This field is used to describe the IP address of the VLAN interface. The addresses of the two VLAN interfaces in the embodiment of the present application are 10.1.1.254 and 10.1.2.254 respectively.

[0074] Figure 2The topology on the right illustrates the virtual network architecture of the SDN network, including a virtual router, two virtual networks, and two virtual subnets. The following is a detailed explanation of the components and their relationships in the virtual network architecture:

[0075] Virtual router (vRouter): Responsible for routing and forwarding traffic between different virtual networks, enabling devices in different virtual networks to communicate.

[0076] vNetwork 1 and vNetwork 2: Two independent network areas connected by a virtual router. Each virtual network contains a virtual subnet to divide the IP address range.

[0077] Virtual subnet 1 (subnet 1) and virtual subnet 2 (subnet 2): Virtual subnet 1 belongs to vNetwork1, and the network prefix is ​​10.1.1.254 / 24; virtual subnet 2 belongs to vNetwork2, and the network prefix is ​​10.1.2.254 / 24.

[0078] The embodiment of the present application configures the traditional network and the SDN network to ensure that the three-layer traffic is not interrupted during the network migration process. Specifically, the interconnection route between the new and old networks is opened to achieve the L3 service connection between the new and old networks, and reduce the L3 service traffic interruption time during the gateway migration process. Assuming that the current subnets to be migrated are 10.1.1.0 / 24 and 10.1.2.0 / 24, Figure 3 This is the static route of the subnet to be migrated issued by the embodiment of this application. After the subnet gateway is migrated to the SDN network, the traffic accessed by the SDN network is forwarded from the gateway to the interconnection device of the traditional network, thereby achieving three-layer traffic interconnection with the traditional network subnet. Figure 3 For detailed explanation:

[0079] like Figure 3 As shown in the code on the upper left, static routes are defined on the gateway device of the traditional network from the VPN instance named app_oa_net (equivalent to the three-layer VPN instance mentioned above) to the target networks 10.1.1.0 / 24 and 10.1.2.0 / 24. The next-hop addresses of these static routes are all 50.1.1.2 (equivalent to the second address mentioned above). Specifically, the target network of the first static route configured for this VPN instance is 10.1.1.0 / 24, and the next-hop address is 50.1.1.2. The target network of the second static route is 10.1.2.0 / 24, and the next-hop address is 50.1.1.2.

[0080] like Figure 3As shown in the code on the upper right, static routes from the VPN instance named app_oa_net to the target networks 10.1.1.0 / 24 and 10.1.2.0 / 24 are defined on the edge device of the SDN network. The next hop addresses of these static routes are all 50.1.1.1 (equivalent to the first address mentioned above). Specifically, the target network of the first static route configured for the VPN instance is 10.1.1.0 / 24, and the next hop address is 50.1.1.1. The target network of the second static route is 10.1.2.0 / 24, and the next hop address is 50.1.1.1.

[0081] After the L3 service is connected, the embodiment of the present application sends the Layer 2 intercommunication configuration to the interconnection devices of the traditional network and the SDN network to ensure that the Layer 2 traffic is not interrupted during the migration process. Assuming that the current subnet to be migrated is 1.0.0.0 / 24 and the gateway is 1.0.0.254, the L2 intercommunication configuration is as follows: Figure 4 As shown in the figure. After the virtual machines in the subnet are migrated to the SDN network, the virtual machines migrated to the SDN network can directly communicate with the virtual machines in the traditional network at Layer 2 through the VXLAN tunnel. Figure 4 For detailed explanation:

[0082] Figure 4 The figure shows the process of L2 service connection. Connection of L2 service means connecting the traffic of the same VLAN between different network devices. Figure 4 As shown, the embodiment of the present application sets the interfaces of the gateway device and the edge device to Trunk mode, and sets to allow traffic from VLAN 10 to pass. Create service instance 10 on the edge device, set its encapsulation type to VLAN 10, and connect service instance 10 to the virtual switching instance named SDN_VSI_100. Figure 4 The meaning of the code is explained:

[0083] Figure 4 The codes and meanings on the left are as follows:

[0084] port trunk permit vlan 10: The gateway device in the traditional network is configured with an interconnection port to allow traffic from VLAN 10 to pass through.

[0085] Figure 4 The codes and meanings on the right are as follows:

[0086] port trunk permit vlan 10: Configures the interconnection port to allow traffic from VLAN 10 to pass through.

[0087] service-instance 10: Creates a service instance numbered 10.

[0088] encapsulation s-vid 10: Specifies the encapsulation type of the service instance as VLAN 10, that is, the s-vid ID (service VLAN identifier) ​​used by the service instance is 10.

[0089] connect vsi SDN_VSI_10: connects the service instance to the virtual switching instance named SDN_VSI_10.

[0090] After the L2 service is connected, the virtual machine can be migrated from the traditional network to the SDN network. After all the virtual machines under a subnet to be migrated are migrated to the SDN network, the gateway of the subnet to be migrated can be migrated.

[0091] The gateway migration function automatically switches between the old and new gateways by disabling the traditional network gateway and starting the SDN network gateway. Assuming that the current subnet to be migrated is 1.0.0.0 / 24 and the gateway is 1.0.0.254, the gateway migration configuration is as follows: Figure 5 shown. Figure 5 The configuration shown ensures the interconnection between the traditional network and the SDN network. Specifically, the traditional network is configured with an interface of VLAN 10, an IP address is assigned and the interface is temporarily closed; the SDN network is configured with a virtualized interface and bound to a VPN instance named app_oa_net, an IP address and a MAC address are assigned, and a distributed gateway is enabled. This configuration ensures that traffic can be effectively managed and routed between the traditional network and the SDN network, ensuring network connectivity and security. Figure 5 The meaning of the code is explained:

[0092] Figure 5 The meanings of the codes on the left are as follows:

[0093] vlan-interface 10: creates an interface for VLAN 10.

[0094] ip address 10.1.1.0 255.255.255.0: The IP address configured for the interface of VLAN 10 is 10.1.1.0 / 24, that is, the network address is 10.1.1.0 and the subnet mask is 255.255.255.0.

[0095] shutdown: Shut down the VLAN interface.

[0096] Figure 5 The meaning of the code on the right is as follows:

[0097] interface Vsi-interface10: defines and configures the interface named Vsi-interface10.

[0098] description SDN_VSI_Interface_10: adds the description information of the interface, specifically SDN_VSI_Interface_10.

[0099] ip binding vpn-instance app_oa_net: Binds this interface to the VPN instance app_oa_net. This VPN instance can be used for traffic isolation and management.

[0100] ip address 10.1.1.0 255.255.255.0sub: Assigns an IP address and subnet mask to the interface, indicating that this interface is in subnet 10.1.1.0 / 24.

[0101] mac-address 6805-2c21-de65: Assigns the specified MAC address to this interface. 6805-2c41-de65 is the actual assigned MAC address used for network communication.

[0102] distributed-gateway local: Enables the distributed gateway function to share the gateway IP address between different network nodes in the SDN network to achieve more efficient traffic forwarding and management.

[0103] It can be seen from the above technical solutions that the network migration method provided by the embodiment of the present application can realize the automatic conversion and modeling from the traditional network configuration to the SDN network architecture, automatically migrate the subnet, and switch the gateway with one click through the SDN controller, effectively reducing the migration interruption time, and realizing the wizard-style batch migration of services to the SDN network. In short, this method has at least the following advantages:

[0104] Improve migration efficiency: Automating the network migration process can reduce manual operations, reduce reliance on manual experience, save time and costs, and improve operational efficiency.

[0105] Reduce error rate: Automated network migration can avoid human errors and improve system stability and reliability;

[0106] Improve resource utilization: Intelligently allocate and manage network resources to improve resource utilization.

[0107] Based on the same inventive concept, the present application also provides a network migration device, which is applied to an SDN controller, wherein the SDN controller connects a gateway device of a traditional network and an edge device of an SDN network, such as Figure 6 As shown, the device comprises:

[0108] A configuration parsing module 610 is used to obtain network configuration information of the traditional network from the gateway device, wherein the network configuration information includes information of the subnet to be migrated, information of the target VLAN to which the subnet to be migrated belongs, and information of the VPN instance associated with the target VLAN;

[0109] A generating module 620, configured to create a virtual network architecture of the SDN network according to the network configuration information, wherein the virtual network architecture includes a virtual routing device generated according to the associated VPN instance, a virtual network generated according to the target VLAN, and a virtual subnet generated according to the subnet to be migrated;

[0110] A layer 3 opening module 630, used to create a layer 3 VPN instance for opening up layer 3 traffic between the gateway device and the edge device;

[0111] A layer 2 connection module 640, used to create a VXLAN tunnel for connecting layer 2 traffic between the gateway device and the edge device;

[0112] A migration module 650, configured to migrate the virtual machine in the subnet to be migrated to the virtual subnet;

[0113] The gateway start-stop module 660 is used to shut down the gateway of the subnet to be migrated, associate the gateway of the virtual subnet with the three-layer VPN instance and start the gateway of the virtual subnet after all virtual machines in the subnet to be migrated are migrated to the virtual subnet.

[0114] As a specific implementation manner, the three-layer opening module 630 specifically creates a three-layer VPN instance for opening up the three-layer traffic between the gateway device and the edge device in the following manner:

[0115] Create a three-layer VPN instance; configure the three-layer traffic address of the gateway device as the first address, and configure the three-layer traffic address of the edge device as the second address; configure the next hop address of the three-layer VPN instance leading to the subnet to be migrated on the edge device as the first address, and configure the next hop address of the three-layer VPN instance leading to the subnet to be migrated on the gateway device as the second address.

[0116] As a specific implementation manner, the layer 2 opening module 640 specifically creates a VXLAN tunnel for opening the layer 2 traffic between the gateway device and the edge device in the following manner:

[0117] For the current target VLAN, interconnection ports that only allow traffic from the target VLAN to pass are set on the gateway device and the edge device respectively, a service instance associated with the target VLAN is created on the edge device, and the service instance is associated with a virtual network generated based on the target VLAN.

[0118] As a specific implementation, the gateway start / stop module 660 associates the gateway of the virtual subnet with the Layer 3 VPN instance in the following manner:

[0119] For the current target VLAN, create a virtualized interface; associate the virtualized interface to the three-layer VPN instance; for the current subnet to be migrated, configure the IP address and subnet mask of the virtualized interface to the IP address and subnet mask of the subnet to be migrated; configure the MAC address of the virtualized interface.

[0120] As a specific implementation, the gateway start-stop module 660 specifically starts the gateway of the virtual subnet in the following manner:

[0121] A distributed gateway function start command is issued to start the gateway of the virtual subnet.

[0122] As a specific implementation, the device further includes:

[0123] The loop module is used to determine whether there is a subnet to be migrated that has not completed migration under the current target VLAN; if the determination result is yes, the virtual machine under the subnet to be migrated is migrated to a virtual subnet generated according to the subnet to be migrated.

[0124] The present application also provides an electronic device, such as Figure 7 As shown, it includes a processor 710 and a machine-readable storage medium 720, wherein the machine-readable storage medium 720 stores machine-executable instructions that can be executed by the processor 710, and the processor 710 is prompted by the machine-executable instructions to implement the steps of any of the above-mentioned network migration methods.

[0125] The machine-readable storage medium may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk storage. Optionally, the machine-readable storage medium may also be at least one storage device located away from the processor.

[0126] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0127] In another embodiment provided in the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above network migration methods are implemented.

[0128] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A network migration method, characterized in that: The method is applied to an SDN controller, wherein the SDN controller is connected to a gateway device of a traditional network and an edge device of the SDN network, and the method includes: Acquire network configuration information of the traditional network from the gateway device, wherein the network configuration information includes information of the subnet to be migrated, information of the target VLAN to which the subnet to be migrated belongs, and information of the VPN instance associated with the target VLAN; Creating a virtual network architecture of the SDN network according to the network configuration information, wherein the virtual network architecture includes a virtual routing device generated according to the associated VPN instance, a virtual network generated according to the target VLAN, and a virtual subnet generated according to the subnet to be migrated; Creating a Layer 3 VPN instance that enables Layer 3 traffic between the gateway device and the edge device; Creating a VXLAN tunnel for connecting Layer 2 traffic between the gateway device and the edge device; Migrating the virtual machines in the subnet to be migrated to the virtual subnet; After all virtual machines in the subnet to be migrated are migrated to the virtual subnet, the gateway of the subnet to be migrated is shut down, the gateway of the virtual subnet is associated with the layer 3 VPN instance, and the gateway of the virtual subnet is started.

2. The method according to claim 1, characterized in that Creating a Layer 3 VPN instance that enables Layer 3 traffic between the gateway device and the edge device, specifically including: Create a Layer 3 VPN instance; Configure the layer 3 traffic address of the gateway device as a first address, and configure the layer 3 traffic address of the edge device as a second address; The next hop address of the layer 3 VPN instance leading to the subnet to be migrated is configured on the edge device as the first address, and the next hop address of the layer 3 VPN instance leading to the subnet to be migrated is configured on the gateway device as the second address.

3. The method according to claim 1, characterized in that Creating a VXLAN tunnel for Layer 2 traffic between the gateway device and the edge device, specifically including: For the current target VLAN, interconnection ports that only allow traffic from the target VLAN to pass are set on the gateway device and the edge device respectively, a service instance associated with the target VLAN is created on the edge device, and the service instance is associated with a virtual network generated based on the target VLAN.

4. The method according to claim 1, characterized in that: Associating the gateway of the virtual subnet with the layer 3 VPN instance specifically includes: Create a virtualized interface for the current target VLAN; Associating the virtualized interface to the layer 3 VPN instance; For the current subnet to be migrated, the IP address and subnet mask of the virtualized interface are configured as the IP address and subnet mask of the subnet to be migrated; Configure the MAC address of the virtualized interface.

5. The method according to claim 1, characterized in that Starting the gateway of the virtual subnet includes: A distributed gateway function start command is issued to start the gateway of the virtual subnet.

6. The method according to claim 1, characterized in that After shutting down the gateway of the subnet to be migrated, associating the gateway of the virtual subnet with the layer 3 VPN instance and starting the gateway of the virtual subnet, the method further includes: Determine whether there is a subnet to be migrated that has not been migrated yet under the current target VLAN; If the judgment result is yes, the virtual machine under the subnet to be migrated is migrated to a virtual subnet generated according to the subnet to be migrated.

7. A network migration device, characterized in that: The device is applied to an SDN controller, the SDN controller connects a gateway device of a traditional network and an edge device of the SDN network, and the device includes: A configuration parsing module, used to obtain network configuration information of the traditional network from the gateway device, wherein the network configuration information includes information of the subnet to be migrated, information of the target VLAN to which the subnet to be migrated belongs, and information of the VPN instance associated with the target VLAN; A generation module, configured to create a virtual network architecture of the SDN network according to the network configuration information, wherein the virtual network architecture includes a virtual routing device generated according to the associated VPN instance, a virtual network generated according to the target VLAN, and a virtual subnet generated according to the subnet to be migrated; A layer 3 opening module, used to create a layer 3 VPN instance for opening up layer 3 traffic between the gateway device and the edge device; A layer 2 connection module, used to create a VXLAN tunnel that connects the layer 2 traffic between the gateway device and the edge device; A migration module, used to migrate the virtual machines in the subnet to be migrated to the virtual subnet; The gateway start-stop module is used to shut down the gateway of the subnet to be migrated, associate the gateway of the virtual subnet with the three-layer VPN instance and start the gateway of the virtual subnet after all virtual machines in the subnet to be migrated are migrated to the virtual subnet.

8. The device according to claim 7, characterized in that The three-layer opening module specifically creates a three-layer VPN instance for opening up the three-layer traffic between the gateway device and the edge device in the following manner: Create a three-layer VPN instance; configure the three-layer traffic address of the gateway device as the first address, and configure the three-layer traffic address of the edge device as the second address; configure the next hop address of the three-layer VPN instance leading to the subnet to be migrated on the edge device as the first address, and configure the next hop address of the three-layer VPN instance leading to the subnet to be migrated on the gateway device as the second address.

9. The device according to claim 7, characterized in that The layer 2 connection module specifically creates a VXLAN tunnel for connecting layer 2 traffic between the gateway device and the edge device in the following manner: For the current target VLAN, interconnection ports that only allow traffic from the target VLAN to pass are set on the gateway device and the edge device respectively, a service instance associated with the target VLAN is created on the edge device, and the service instance is associated with a virtual network generated based on the target VLAN.

10. An electronic device, characterized in that: The method comprises a processor and a machine-readable storage medium, wherein the machine-readable storage medium stores machine-executable instructions that can be executed by the processor, and the processor is prompted by the machine-executable instructions to implement the method steps described in any one of claims 1 to 6.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps of any one of claims 1 to 6 are implemented.

Images