A network migration method and device, electronic equipment and storage medium

Abstract

The application provides a network migration method and device, electronic equipment and storage medium. The method comprises the following steps: obtaining network configuration information of a traditional network from a gateway device, converting the traditional network configuration into a network architecture of an SDN network, then keeping the stability and performance of the network through each layer connection, gradually migrating virtual machines under a subnet to be migrated of the traditional network to corresponding virtual subnets in the SDN network, and finally switching the new and old gateways at one key, so that the network automatic migration is smoothly completed without affecting the business operation, the business traffic interruption time in the network migration process is minimized, the dependence on manual experience in the network migration process is reduced, and the network migration efficiency and accuracy are improved.

Description

TECHNICAL FIELD

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

[0002] The traditional network refers to a traditional network architecture. In the traditional network, the control plane and the data plane of a network device are coupled together, network configuration and management are relatively cumbersome, and it is difficult to quickly adapt to changes in business. In addition, network management of the traditional network is usually decentralized, lacking 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. The SDN separates the control plane and the data plane of the network, and realizes unified management and control of the network through a centralized controller, making the network more flexible and programmable, and enabling it to quickly adapt to different business requirements and environmental changes. Secondly, the SDN provides a unified network management view and management interface, simplifying the network management process and improving management efficiency. In addition, the SDN has the advantages of low operation and maintenance cost, strong security, etc. Therefore, more and more enterprises tend to use the SDN network architecture to replace the traditional network architecture to meet business requirements and improve network management efficiency.

[0004] However, in the process of migrating business from the traditional network to the SDN network, due to the problems of old network devices, chaotic architecture, and complex business in the traditional network, the engineering quantity of network migration is extremely large, the time span may be several months, and there is an unavoidable risk of business interruption. SUMMARY

[0005] To overcome the problems in the related art, the present application provides a network migration method and device, electronic equipment and storage medium.

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

[0007] obtaining network configuration information of the traditional network from the gateway device, the network configuration information comprising information of a subnet to be migrated, information of a target VLAN to which the subnet to be migrated belongs, and information of an associated VPN instance of the target VLAN;

[0008] Creating a virtual network architecture of the SDN network according to the network configuration information, the virtual network architecture including 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 for enabling Layer 3 traffic between the gateway device and the edge device;

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

[0011] Migrating the virtual machine 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 is applied to an SDN controller, wherein the SDN controller connects a gateway device of a traditional network and an edge device of the SDN network. The device includes:

[0014] A configuration parsing module, configured 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 is used 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 VPN module is used to create a layer 3 VPN instance that connects the layer 3 traffic between the gateway device and the edge device;

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

[0018] A migration module, configured 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. When the computer program is executed by a processor, the steps of the network migration method described above are implemented.

[0022] The technical solutions 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 the network migration service into the 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 the network services are gradually migrated from the traditional network to the SDN network. Finally, the old and new gateways are switched with one click, and the network migration is smoothly completed without affecting the business operation, thereby minimizing the business traffic interruption time during the migration process, and reducing the dependence of the network migration process on manual experience, thereby improving the 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 and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present 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 method for 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 provided in an embodiment of the present application;

[0029] Figure 4 A schematic diagram of a Layer 2 network connection method for 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, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

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

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

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

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

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

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

[0040] VXLAN (Virtual Extensible LAN) is a network virtualization technology used to scale virtual local area networks (VLANs) in large data center environments. VXLAN tunnels are its core mechanism, creating a virtual Layer 2 network on top of existing network infrastructure to transcend physical network limitations.

[0041] The Data Link Layer (L2) primarily handles data communications within a local area network (LAN), ensuring frame transmission between different devices within the same broadcast domain. Switches are key L2 devices, forwarding data based on MAC addresses.

[0042] The Network Layer (L3) handles data communication across networks and is responsible for IP address planning and routing. Routers are key L3 devices, forwarding 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 considered a virtual switch that performs Layer 2 forwarding based on the VXLAN. A VSI corresponds one-to-one with a VXLAN.

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

[0045] The embodiment of the present application provides a network migration method, which is applied to an SDN controller, such as Figure 1 As shown, the method includes 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 facilitate Layer 3 traffic between the gateway device and the edge device.

[0049] Step 140: Create a VXLAN tunnel to facilitate 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 this embodiment of the present application, the SDN network divides network devices into functional groups, specifically edge devices, and may further include load balancers, firewalls, core switches, leaf switches, and Layer 2 / Layer 3 switches. The edge devices connect to the external network and are responsible for managing inbound and outbound traffic. In this embodiment of the present application, the SDN controller connects the gateway devices of the traditional network with the edge devices of the SDN network.

[0053] Specifically, in the embodiment of the present application, a network migration service is integrated into the SDN controller, a gateway device of the traditional network is added and managed in the network migration service, and the device configuration of the gateway device of the traditional network is obtained through the netconf or cli command line to obtain 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's worth noting that in practice, there can be one or more subnets to be migrated, but each subnet to be migrated belongs to only one VLAN. In this embodiment, the VLAN to which the subnet to be migrated belongs is referred to as the target VLAN. Associated VPN instances are used to connect different subnets to be migrated, and this embodiment 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 based on the associated VPN instance, a virtual network generated based on the target VLAN, and a virtual subnet generated based on 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 on a per-subnet basis. As virtual machines in the same subnet are gradually migrated to the virtual subnet corresponding to the subnet, virtual machines in the subnet remaining in the traditional network can communicate with virtual machines already migrated to the SDN network via VXLAN tunnels. After all virtual machines in the subnet are migrated to the virtual subnet corresponding to the subnet, gateway migration can be performed, i.e., shutting down the gateway of the subnet in the traditional network and starting up the gateway of the virtual network corresponding to the subnet 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. Then, it is determined whether there are subnets to be migrated that have not been migrated under the current target VLAN. If the judgment result is yes, the migration of other subnets to be migrated under the current target VLAN will continue 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 Layer 2 traffic between a gateway device and an 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, 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, there may be multiple associated VPN instances. Specifically, in the embodiments of the present application, a Layer 3 VPN instance is created for each associated VPN instance to facilitate Layer 3 traffic between the gateway device and the edge device. Accordingly, after all subnets to be migrated under a target VLAN are migrated to the SDN network, a determination is made as to whether the currently associated VPN instance has other associated target VLANs that need to be migrated. If so, migration of other target VLANs associated with the currently associated VPN instance continues until all target VLANs associated with the currently associated VPN instance are fully migrated.

[0060] Specifically, a three-layer VPN instance that opens up three-layer traffic between the gateway device and the 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 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.

[0061] As a specific implementation, the virtual subnet's gateway can be associated with a Layer 3 VPN instance by creating a virtualized interface for the current target VLAN; associating the virtualized interface with the Layer 3 VPN instance; configuring the IP address and subnet mask of the virtualized interface to match the IP address and subnet mask of the subnet to be migrated; and configuring the MAC address of the virtualized interface. Specifically, the virtual subnet's gateway can be started by issuing a distributed gateway function start command to start the virtual subnet's gateway.

[0062] The following combination Figure 2 、 Figure 3 、 Figure 4 and Figure 5 The following specific application is only a possible scenario and should not be understood as a limitation of this 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 the following 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 SDN controller uses the RestAPI to create virtual routers, virtual networks, and virtual subnets, and then sends configurations to the network devices of the SDN network.

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

[0065] Below Figure 2 Explain the meaning of:

[0066] Figure 2The code on the left illustrates the network configuration of a traditional network. Specifically, the traditional network defines two VLANs: VLAN 10 and VLAN 20. VLAN 10 is named user_vlan, and VLAN 20 is named server_vlan. The traditional network also defines a VPN instance named vrf-eng (equivalent to the associated VPN instance described above). Logical interfaces, Vlanif10 and Vlanif20, corresponding to VLAN 10 and VLAN 20, are created. IP addresses 10.1.1.254 / 24 and 10.1.2.254 / 24 are configured for Vlanif10 and Vlanif20, respectively. Both logical interfaces are bound to the VPN instance vrf-eng.

[0067] Figure 2 The middle table shows the network service configuration information generated based on the network configuration information of the traditional network, including 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 this 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; in the embodiment of the present application, both VLAN interfaces 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, which includes a virtual router, two virtual networks, and two virtual subnets. The following is a detailed explanation of the components and their relationships in this 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, which is used to divide the IP address range.

[0077] Virtual subnet 1 (subnet 1) and virtual subnet 2 (subnet 2): Virtual subnet 1 belongs to vNetwork 1 and has a network prefix of 10.1.1.254 / 24; virtual subnet 2 belongs to vNetwork 2 and has a network prefix of 10.1.2.254 / 24.

[0078] The embodiment of the present application ensures that the three-layer traffic is not interrupted during the network migration process by configuring the traditional network and the SDN network. Specifically, the interconnection route between the old and new networks is opened to achieve the L3 service connection between the old and new 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 interconnected device of the traditional network, thereby achieving three-layer traffic intercommunication with the traditional network subnet. Figure 3 For detailed explanation:

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

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

[0081] After the L3 service is connected, the embodiment of the present application issues the Layer 2 intercommunication configuration to the interconnection equipment of the traditional network and the SDN network, thereby ensuring 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 This diagram illustrates the L2 service connection process. Connection of L2 services refers to connecting 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 the traffic of VLAN 10 to be allowed to pass. Create a service instance 10 on the edge device, set its encapsulation type to VLAN 10, and connect the 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 on 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 interconnected port to permit traffic from VLAN 10.

[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 in 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 activating the SDN network gateway. Assuming that the 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 in VLAN 10, an IP address is assigned, and the interface is temporarily shut down. The SDN network is configured with a virtualized interface, bound to a VPN instance named app_oa_net, and an IP address and MAC address are assigned, with a distributed gateway enabled. This configuration ensures that traffic can be effectively managed and routed between the traditional and SDN networks, ensuring network connectivity and security. Figure 5 The meaning of the code is explained:

[0092] Figure 5 The meaning 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 in 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: Shuts 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: Description information of the added interface, specifically described as SDN_VSI_Interface_10.

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

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

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

[0102] distributed-gateway local: Enable distributed gateway function to facilitate sharing of gateway IP addresses between different network nodes in the SDN network, achieving more efficient traffic forwarding and management.

[0103] As can be seen from the above technical solutions, the network migration method provided by the embodiments of the present application can realize automatic conversion and modeling from traditional network configuration to SDN network architecture, automatically migrate subnets, and switch gateways through the SDN controller, effectively reducing the migration outage time, and realizing guided batch migration of services to the SDN network. In summary, the method at least has the following advantages:

[0104] Improve migration efficiency: Automatic network migration process can reduce manual operation, reduce dependence on human experience, save time and cost, and improve operation efficiency;

[0105] Reduce error rate: Automated network migration can avoid human error, 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 connected to a gateway device of a traditional network and a border device of an SDN network, as shown in Figure 6 The device comprises:

[0108] A configuration parsing module 610 is configured 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 is 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 VPN module 630 is configured to create a Layer 3 VPN instance for connecting Layer 3 traffic between the gateway device and the edge device.

[0111] A Layer 2 connection module 640 is configured to create a VXLAN tunnel for connecting Layer 2 traffic between the gateway device and the edge device;

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

[0113] The gateway start-stop module 660 is configured to shut down the gateway of the subnet to be migrated, associate the gateway of the virtual subnet with the Layer 3 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, the Layer 3 VPN module 630 creates a Layer 3 VPN instance for connecting Layer 3 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 connection module 640 specifically creates a VXLAN tunnel for connecting 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 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 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] Create a virtualized interface for the current target VLAN; associate the virtualized interface with 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 starts the gateway of the virtual subnet in the following manner:

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

[0122] As a specific embodiment, 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 based on 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 random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Alternatively, the machine-readable storage medium may be at least one storage device located remote from the processor.

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

[0127] In a further embodiment provided in the present application, a computer readable storage medium is also provided, and the computer readable storage medium stores a computer program. The computer program is executed by a processor to implement the steps of any of the network migration methods described above.

[0128] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle 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 connects a gateway device of a traditional network and an edge device of the SDN network. 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 a VPN instance associated with the target VLAN; Creating a virtual network architecture of the SDN network according to the network configuration information, the virtual network architecture including 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 for enabling Layer 3 traffic between the gateway device and the edge device; Creating a VXLAN tunnel for Layer 2 traffic between the gateway device and the edge device; Migrating the virtual machine 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 to facilitate Layer 3 traffic between the gateway device and the edge device includes: Create a Layer 3 VPN instance; Configuring the layer 3 traffic address of the gateway device as a first address and configuring 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 to facilitate Layer 2 traffic between the gateway device and the edge device includes: 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 a virtual network generated based on the target VLAN.

4. The method according to claim 1, wherein 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 with the Layer 3 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.

5. The method according to claim 1, wherein Starting the gateway of the virtual subnet includes: A distributed gateway function startup 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 are any subnets to be migrated that have not yet been completed under the current target VLAN; If the judgment result is yes, the virtual machine in 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, which connects a gateway device of a traditional network and an edge device of the SDN network. The device includes: a configuration parsing module, configured 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 is used 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 VPN module is used to create a layer 3 VPN instance that connects the layer 3 traffic between the gateway device and the edge device; A layer 2 connection module is used to create a VXLAN tunnel for connecting layer 2 traffic between the gateway device and the edge device; A migration module, configured 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 that opens 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 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 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 according to 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 according to any one of claims 1 to 6 are implemented.

Images