Dynamic routing interface configuration method and device, and electronic equipment

Abstract

The application provides a dynamic routing docking configuration method and device and electronic equipment, the method is applied to a cloud management platform, the method comprises the following steps: creating a virtual router (vRouter) by calling a virtual infrastructure manager (VIM) and a software defined network (SDN) controller, and creating a virtual firewall (vFW) by calling a security controller; creating an interconnection logical link and a dynamic routing neighbor between the vRouter and the vFW by calling the VIM, the SDN controller and the security controller, realizing the configuration of dynamic routing docking between the vRouter and the vFW, so that the vRouter and the vFW can be dynamically routed and docked, the demand for dynamic routing docking between the vRouter and the vFW can be met, the method can be applied to a scene requiring dynamic routing docking, the applicable range is expanded, and the scene applicability is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a dynamic routing docking configuration method and device and electronic equipment. BACKGROUND

[0002] Neutron is an open source cloud computing management platform project (OpenStack) component responsible for providing network services. When a cloud data center gateway (Data Center-Gateway, DC-GW) and a firewall (Fire Wall, FW) are deployed in a hardware form, at least two hardware FWs are connected to the DC-GW, at least two hardware FWs are deployed in a mirror master-slave mode, and at least two hardware FWs present as one logical device to the cloud management platform / DC-GW to simplify implementation.

[0003] The current hardware FW master-slave mirror mode presents one logical device to the outside, only supports static routing docking, that is, static routing between the FW and the DC-GW, however, in some scenarios, static routing is not applicable, for example, there are two scenarios in the network edge cloud, one is a user plane function (User plane Function, UPF) host routing scenario, the host routing is scattered and cannot publish user equipment (User Equipment, UE) routing through static configuration, and the other is a UPF disaster recovery scenario, the master and standby UPFs publish different UE routes to the outside for distinguishing the master and standby and disaster recovery switching, both of which require dynamic publication of UE routing (which can be understood as dynamic publication of UE address). According to the edge cloud boundary security requirements, security access control needs to be performed, so the virtual router (vRouter) of the DC-GW and the vFW of the hardware FW need to be connected through dynamic routing. That is to say, the current static routing mode between the FW and the DC-GW has a limited scope of application, resulting in poor applicability in some scenarios. SUMMARY

[0004] The embodiments of the present application provide a dynamic routing docking configuration method, device and electronic equipment to solve the problem that the current static routing mode between the FW and the DC-GW has a limited scope of application, resulting in poor applicability in some scenarios.

[0005] To solve the above technical problems, the present application is implemented as follows:

[0006] In a first aspect, the embodiments of the present application provide a dynamic routing docking configuration method applied to a cloud management platform, and the configuration method comprises:

[0007] A virtual infrastructure manager (VIM) and a software-defined network (SDN) controller are called to create a virtual router (vRouter), and a security controller is called to create a virtual firewall (vFW).

[0008] create the interconnection logical link and the dynamic routing neighbor between the vRouter and the vFW by invoking the VIM, the SDN controller and the security controller.

[0009] In a second aspect, an embodiment of the present application provides a configuration device for dynamic routing docking, applied to a cloud management platform, the device comprising:

[0010] a first creating module configured to create a virtual router (vRouter) by invoking a virtual infrastructure manager (VIM) and a software defined network (SDN) controller, and create a virtual firewall (vFW) by invoking a security controller;

[0011] a second creating module configured to create an interconnection logical link and a dynamic routing neighbor between the vRouter and the vFW by invoking the VIM, the SDN controller and the security controller.

[0012] In a third aspect, an embodiment of the present application provides an electronic device comprising a transceiver and a processor, wherein the processor is configured to:

[0013] create a virtual router (vRouter) by invoking a virtual infrastructure manager (VIM) and a software defined network (SDN) controller, and create a virtual firewall (vFW) by invoking a security controller;

[0014] create an interconnection logical link and a dynamic routing neighbor between the vRouter and the vFW by invoking the VIM, the SDN controller and the security controller.

[0015] In a fourth aspect, an embodiment of the present application provides an electronic device comprising a processor, a memory and a program stored in the memory and executable in the processor, wherein the program, when executed by the processor, implements the steps of the dynamic routing docking configuration method of the first aspect.

[0016] In a fifth aspect, an embodiment of the present application provides a computer readable storage medium, having a computer program stored therein, wherein the computer program, when executed by a processor, implements the steps of the dynamic routing docking configuration method of the first aspect.

[0017] In the configuration method for dynamic routing docking provided in the embodiments of the present application, the cloud management platform can create a virtual router vRouter by invoking a VIM and an SDN controller, and the cloud management platform can create a virtual firewall vFW by invoking a security controller. Then, the cloud management platform can create a logical link for interconnection between the vRouter and the vFW and a dynamic routing neighbor by invoking the VIM, the SDN controller and the security controller. That is, the configuration method provided in the embodiments of the present application can realize the configuration of dynamic routing docking between the vRouter and the vFW. In this way, the vRouter and the vFW can be dynamically routed and docked, the requirement for dynamic routing docking between the vRouter and the vFW can be met, the method can be applied to scenarios requiring dynamic routing docking, the applicable range is expanded, and the scenario applicability is improved. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the description of the embodiments of the present application will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor on the basis of these drawings.

[0019] Figure 1 is an application scenario diagram;

[0020] Figure 2 is a vRouter and vFW connection diagram;

[0021] Figure 3 is a DC-GW and FW connection diagram;

[0022] Figure 4 is a dynamic UE routing release principle diagram;

[0023] Figure 5 is a flowchart of a dynamic routing docking configuration method provided by the embodiments of the present application;

[0024] Figure 6 is a structural diagram of a dynamic routing docking configuration system provided by the embodiments of the present application;

[0025] Figure 7 is a vRouter and vFW connection diagram provided by the embodiments of the present application;

[0026] Figure 8 is a DC-GW and FW connection diagram provided by the embodiments of the present application;

[0027] Figure 9 is a structural diagram of a dynamic routing docking configuration device provided by the embodiments of the present application;

[0028] Figure 10 is a structural schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0029] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0030] Description of Related Art

[0031] As shown in Figure 1 Neutron is an open source cloud computing management platform project (OpenStack) component responsible for providing network services, which provides network services through a plug-in (Plugin) and agent (Agent) mechanism. The plug-ins involved in the secure access control based on a virtual router (vRouter) include L3 plugin and firewall as a service (Fwaas) plugin. The L3 plugin is used to create a vRouter to provide routing services between Neutron subnets (Subnet) and external access floating Internet protocol (Floating IP) / network address translation (NAT) services. The Fwaas can be used to establish and manage a virtual firewall (vFW) and associate the vFW with the vRouter to filter layer 3 (layer 3) and layer 4 (layer 4) traffic on the Subnet boundary and provide network security protection, etc.

[0032] When the cloud DC-GW and FW are deployed in a hardware form, the L3 plugin can be used to interface a software defined network (SDN) controller to manage the DC-GW, a security controller (also referred to as a FW controller) or a Fwaas plug-in can be used to interface a hardware FW, and a private interface defined between the L3 plugin and the Fwaas plugin is used to complete the automatic deployment of Fwaas services and NAT / FloatingIP services in cooperation.

[0033] As shown in Figure 2 The security logic model in Openstack is that one vRouter corresponds to one vFW, as shown in Figure 3As shown, when the DC-GW and the FW in the cloud are deployed in a hardware form, two hardware FWs are connected with the DC-GW, in order to correspond to the model of one vFW in Neutron, the two hardware FWs are deployed in a mirror master-slave mode, that is, the two hardware FWs are configured identically, and the interfaces connected externally are also identical, the two hardware FWs are presented as one logical device to the cloud management platform / DC-GW, thereby simplifying the implementation, and static routing is used for flow diversion between the FW and the DC-GW.

[0034] As shown in the figure, Figure 4 There are two scenarios in the network edge cloud, one is a UPF host routing scenario, the host routing is scattered, and the host UE routing cannot be published through static configuration; the other is a UPF disaster recovery scenario, the master and standby UPFs publish different priority routes for distinguishing the master and standby and disaster recovery switching, both of the two scenarios need to dynamically publish UE routes, and the edge cloud boundary security requirement needs to do security access control, therefore, the DC-GW vRouter and the vFW need to be connected through dynamic routing, however, the current FW is in a mirror master-slave mode, only supports static routing connection, and the applicable range is limited, resulting in poor applicability or inapplicability in some scenarios, and the dynamic UE routing publishing business requirement of the network edge cloud in some scenarios cannot be met.

[0035] The embodiment of the application provides a kind of configuration method of dynamic routing docking, can realize the deployment of dynamic routing docking between vRouter and vFW, to carry out dynamic routing docking between vRouter and vFW, meet the demand of dynamic routing docking between vRouter and vFW, it can be applicable to the scene requiring dynamic routing docking, expand applicable range, improve scene applicability.

[0036] Referring to Figure 5 , Figure 5 It is a flow chart of the configuration method of dynamic routing docking provided by the embodiment of the application, the method of the embodiment can be applied to cloud management platform, and the cloud management platform can be deployed in electronic equipment (for example, it can be cloud server), it can be understood that the cloud management platform can be a software platform deployed in electronic equipment. As shown in the figure, Figure 5 The configuration method of dynamic routing docking provided by the embodiment includes the following steps:

[0037] Step 501: create a virtual router vRouter by calling a virtual infrastructure manager VIM and a software defined network SDN controller, and create a virtual firewall vFW by calling a security controller;

[0038] Step 502: create an interconnection logical link and a dynamic routing neighbor between the vRouter and the vFW by calling the VIM, the SDN controller and the security controller.

[0039] VIM is the abbreviation of Virtualised Infrastructure Manager, i.e. a virtual infrastructure manager. It should be noted that the VIM can be software deployed in the electronic device. The SDN controller and the security controller are different software deployed in the electronic device, i.e. the SDN controller and the security controller are deployed in the electronic device in the form of software. The VIM is between the cloud management platform and the SDN controller. The SDN controller is between the VIM and the hardware DC-GW. The security controller is between the cloud management platform and the hardware FW. In the configuration (deployment) process of the dynamic routing docking, the virtual router vRouter can be created by calling the VIM and the SDN controller. The virtual firewall vFW can be created by calling the security controller. It should be noted that in an example, the cloud management platform creates the virtual router vRouter on the hardware DC-GW by calling the VIM and the SDN controller. The virtual firewall vFW on the hardware FW can be created by calling the security controller. By calling the VIM, the SDN controller and the security controller, the interconnection logical link between the vRouter on the hardware DC-GW and the vFW on the hardware FW and the dynamic routing neighbor can be created.

[0040] After the vRouter is created and the vFW is created, the interconnection logical link between the vRouter and the vFW and the dynamic routing neighbor can be established. By calling the VIM, the SDN controller and the security controller, the interconnection logical link between the vRouter and the vFW and the dynamic routing neighbor can be created. The configuration of the dynamic routing docking between the M vRouters and the N vFWs is completed. In this way, the dynamic routing docking between the vRouter and the vFW can be performed.

[0041] In the dynamic routing docking configuration method of the embodiment of the present application, the cloud management platform can create the virtual router vRouter by calling the VIM and the SDN controller. The cloud management platform can create the virtual firewall vFW by calling the security controller. Then, the interconnection logical link between the vRouter and the vFW and the dynamic routing neighbor can be created by calling the VIM, the SDN controller and the security controller. That is, by using the method of the embodiment of the present application, the configuration of the dynamic routing docking between the vRouter and the vFW can be realized. In this way, the dynamic routing docking between the vRouter and the vFW can be realized, which meets the requirement of the dynamic routing docking between the vRouter and the vFW. The method can be applied to the scene requiring the dynamic routing docking, which expands the applicable range and improves the scene applicability.

[0042] In an embodiment, the cloud management platform can be configured to maintain a docking physical topology (also referred to as docking physical topology information) between the hardware data center gateways DC-GW and the hardware firewalls FW, i.e., the docking physical topology is maintained in the cloud management platform, and the docking physical topology can include M hardware data center gateways DC-GW, N hardware firewalls FW, and a physical connection relationship between the M hardware DC-GWs and the N hardware FWs, where M and N are integers greater than 1.

[0043] It should be noted that M and N can be the same or different, for example, in one example, M and N are the same, and can both be 2, and the docking physical topology represents the physical connection relationship between the M hardware DC-GWs and the N hardware FWs, i.e., represents the physical link, and a hardware DC-GW is physically connected to a hardware FW, i.e., indicates that there is a physical link between the two. It should be noted that the interconnection logical link between the M vRouters and the N vFWs can be established with reference to the physical connection relationship in the docking physical topology, and the interconnection logical link between the M vRouters and the N vFWs corresponds to the physical link between the M hardware DC-GWs and the N hardware FWs, for example, a hardware DC-GW is physically connected to a hardware FW, and a corresponding logical link between the vRouter of the hardware DC-GW and the vFW of the hardware FW can be established.

[0044] In an embodiment, the cloud management platform can be configured to maintain a docking physical topology (also referred to as docking physical topology information) between the hardware data center gateways DC-GW and the hardware firewalls FW, i.e., the docking physical topology is maintained in the cloud management platform, and the docking physical topology can include M hardware data center gateways DC-GW, N hardware firewalls FW, and a physical connection relationship between the M hardware DC-GWs and the N hardware FWs, where M and N are integers greater than 1.

[0045] In an embodiment, the cloud management platform also maintains the working mode of the N hardware FWs, where the working mode of the N hardware FWs is a master-slave mode, and the N hardware FWs are independent hardware FWs.

[0046] It can be understood that the cloud management platform can also maintain the working mode of N hardware FWs, that is, the cloud management platform also maintains the working mode of N hardware FWs. The working mode of N hardware FWs is a normal master-slave mode, that is, N hardware FWs are independent hardware FWs, have different interfaces connected to the outside, and present N different devices to the outside, which is different from the mirror master-slave mode in the related art. For the N hardware FWs in the normal master-slave mode of the embodiment, the configuration method of dynamic routing connection of the embodiment is used to realize the configuration of dynamic routing connection between the vRouter on the M hardware DC-GW and the vFW on the N hardware FW. In this way, the M vRouters and the N vFWs can be dynamically routed and connected, meet the demand of dynamic routing connection between the vRouter and the vFW, can be applied to the scene requiring dynamic routing connection, expand the application range, and improve the scene applicability.

[0047] In one embodiment, the interconnection logical link between the vRouter and the vFW corresponds to the interconnection logical link between the vRouter on the M hardware DC-GW and the vFW on the N hardware FW, wherein the interconnection logical link between the vRouter on one hardware DC-GW and the vFW on one hardware FW corresponds to one logical interface of the vRouter on one hardware DC-GW and one logical interface of the vFW on one hardware FW.

[0048] By calling the VIM, the SDN controller, and the security controller, the interconnection logical link between the vRouter and the vFW and the dynamic routing neighbor are created, including:

[0049] The network resources required for creating the interconnection logical link between the vRouter on the M hardware DC-GW and the vFW on the N hardware FW are determined;

[0050] According to the network resources, the third indication information for creating the logical interface is sent to the SDN controller by the VIM, the third indication information is used for the SDN controller to generate the third configuration information according to the third indication information, and the third configuration information is sent to the M hardware DC-GW to create the logical interface for connecting the vRouter on the M hardware DC-GW to the vFW on the N hardware FW;

[0051] According to the network resources, the fourth indication information for creating the logical interface is sent to the security controller, the fourth indication information is used for the security controller to generate the fourth configuration information according to the fourth indication information, and the fourth configuration information is sent to the N hardware FW to create the logical interface for connecting the vFW on the N hardware FW to the vRouter on the M hardware DC-GW.

[0052] It can be understood that the cloud management platform maintains a physical topology, and the physical topology can include M hardware DC-GWs and N hardware FWs. By calling the VIM, the SDN controller, and the security controller, the interconnection logical link between the vRouter on the M hardware DC-GWs and the vFW on the N hardware FWs and the dynamic routing neighbor can be created.

[0053] It can be understood that the third configuration information can include the logical interface configuration information of the vRouter on the M hardware DC-GWs, and the fourth configuration information can be the logical interface configuration information of the vFW on the N hardware FWs. It should be noted that one logical link corresponds to one logical interface of the vRouter on one hardware DC-GW and one logical interface of the vFW on one hardware FW. It can be understood that one logical link is a logical link between one logical interface of the vRouter on one hardware DC-GW and one logical interface of the vFW on one hardware FW. In addition, it should be noted that creating the logical interface of the vRouter on the M hardware DC-GWs to interface with the vFW on the N hardware FWs can be understood as creating the logical interface of the vRouter on the M hardware DC-GWs to interface with the vFW on the N hardware FWs. Creating the logical interface of the vRouter on the M hardware DC-GWs to interface with the vFW on the N hardware FWs can be understood as creating the logical interface of the vFW on the N hardware FWs to interface with the vRouter on the M hardware DC-GWs. In one example, the above-mentioned interfacing network resources can include but are not limited to IP addresses and VLAN resources, and the VLAN resource can be a VLAN identifier.

[0054] In this embodiment, in order to create the interconnection logical link between the vRouter on the M hardware DC-GWs and the vFW on the hardware FW, the interfacing network resources required for creating the interconnection logical link are first allocated, and then the cloud management platform can send third indication information to the VIM. The VIM can send the third indication information to the SDN controller. The SDN controller can generate third configuration information in response to the first indication information, and send the third configuration information to the M hardware DC-GWs to create the logical interface of the vRouter on the M hardware DC-GWs to interface with the vFW on the N hardware FWs, that is, to complete the creation of the logical interface of the vRouter on the M hardware DC-GWs. In addition, the cloud management platform can send fourth indication information to the security controller. The security controller generates fourth configuration information in response to the fourth indication information, and sends the fourth configuration information to the N hardware FWs to create the logical interface of the vFW on the N hardware FWs to interface with the vRouter on the M hardware DC-GWs, that is, to complete the creation of the logical interface of the vFW on the N hardware FWs. In this way, by calling the VIM and the SDN controller, and calling the security controller, the interconnection logical link between the vRouter and the vFW can be created.

[0055] In one embodiment, the dynamic routing neighbors between the vRouters and the vFWs correspond to the dynamic routing neighbors between the vRouters on the M hardware DC-GWs and the vFWs on the N hardware FWs.

[0056] By invoking the VIM, the SDN controller and the security controller, the interconnection logical links and the dynamic routing neighbors between the vRouters and the vFWs are created, which further include:

[0057] The fifth indication information for creating the dynamic routing neighbors between the vRouters and the vFWs is sent to the SDN controller by the VIM, and the fifth indication information is used for the SDN controller to generate the fifth configuration information according to the fifth indication information, and send the fifth configuration information to the M hardware DC-GWs, so as to create the dynamic routing neighbors between the vRouters on the M hardware DC-GWs and the vFWs on the N hardware FWs.

[0058] The sixth indication information for creating the dynamic routing neighbors between the vFWs and the vRouters is sent to the security controller, and the sixth indication information is used for the security controller to generate the sixth configuration information according to the sixth indication information, and send the sixth configuration information to the N hardware FWs, so as to create the dynamic routing neighbors between the vFWs on the N hardware FWs and the vRouters on the M hardware DC-GWs.

[0059] The cloud management platform can maintain the interfacing physical topology, and the interfacing physical topology can include the M hardware DC-GWs and the N hardware FWs, that is, the above-mentioned dynamic routing neighbors between the vRouters and the vFWs can include the dynamic routing neighbors between the vRouters on the M hardware DC-GWs and the vFWs on the N hardware FWs. It can be understood that the fifth configuration information can include the dynamic routing neighbor configuration information of the vRouters on the M hardware DC-GWs, and the sixth configuration information can be the dynamic routing neighbor configuration information of the vFWs on the N hardware FWs.

[0060] Since dynamic routing needs to know the neighbor, dynamic routing is performed through the neighbor, so in this embodiment, dynamic routing neighbors need to be created (established). In one example, the dynamic routing neighbor can be a dynamic routing protocol (for example, a Border Gateway Protocol (BGP) / Open Shortest Path First (OSPF) protocol) neighbor. The dynamic routing neighbors of the vRouters on the M hardware DC-GWs to the vFWs on the N hardware FWs can include the neighbor vFW (belonging to a vFW in the N vFWs) of the vRouter on each of the M hardware DC-GWs, and the dynamic routing neighbors of the vFWs on the N hardware FWs to the vRouters on the M hardware DC-GWs can include the neighbor vRouter (belonging to a vRouter in the M vRouters) of the vFW on each of the N hardware FWs. For example, a logical link can be established between a certain vRouter and a certain vFW, and the vFW can be set as the neighbor vFW of the vRouter, and the vRouter can be set as the neighbor vRouter of the vFW.

[0061] In this embodiment, the cloud management platform can send fifth indication information to the VIM, the VIM can send the fifth indication information to the SDN controller, the SDN controller can generate fifth configuration information in response to the fifth indication information, and send the fifth configuration information to the M hardware DC-GWs to create the dynamic routing neighbors of the vRouters on the M hardware DC-GWs to the vFWs on the N hardware FWs. In addition, the cloud management platform can send sixth indication information to the security controller, the security controller can generate sixth configuration information in response to the sixth indication information, and send the sixth configuration information to the N hardware FWs to create the dynamic routing neighbors of the vFWs on the N hardware FWs to the vRouters on the M hardware DC-GWs. In this way, by invoking the VIM and the SDN controller, and invoking the security controller, the dynamic routing neighbors between the vRouters and the vFWs can be created, the configuration of the dynamic routing between the vRouters and the vFWs can be achieved, in this way, the vRouters and the vFWs can be dynamically routed, the demand for dynamic routing between the vRouters and the vFWs can be met, the scenario can be applicable to the requirement for dynamic routing, the applicable range is expanded, the scenario applicability is improved, at the same time, the business demand for dynamic publishing of UE routing in some scenarios of network edge cloud can be met.

[0062] In one embodiment, a virtual router vRouter is created by invoking a virtual infrastructure manager VIM and a software defined network SDN controller, including:

[0063] The VIM sends first indication information to the SDN controller, wherein the first indication information is used by the SDN controller to generate first configuration information according to the first indication information, and send the first configuration information to the M hardware DC-GWs, so as to create a vRouter, and M is an integer greater than 1.

[0064] That is, the cloud management platform can send first indication information to the VIM, the VIM can send the first indication information to the SDN controller, the SDN controller can generate first configuration information according to the first indication information, and send the first configuration information to the M hardware DC-GWs, so as to create a virtual router vRouter, and realize the creation of the vRouter on the M hardware DC-GWs. The first configuration information can include virtual router configuration information, that is, in this embodiment, the SDN controller can convert the first indication information into hardware DC-GW virtual router configuration delivery, that is, deliver the first configuration information, and realize the deployment of the hardware DC-GW side virtual router configuration. It should be noted that in one example, the cloud management platform maintains a docking physical topology, and the docking physical topology can include M hardware DC-GWs and N hardware FWs, so that the creation of the virtual router vRouter on the hardware DC-GW can be the creation of the virtual router vRouter on each of the M hardware DC-GWs in the docking physical topology.

[0065] In one embodiment, the virtual firewall vFW is created by calling the security controller, including:

[0066] The second indication information is sent to the security controller, wherein the second indication information is used by the security controller to generate second configuration information according to the second indication information, and send the second configuration information to the N hardware FWs, so as to create a vFW, and N is an integer greater than 1.

[0067] That is, the cloud management platform can send second indication information to the security controller, the security controller can generate second configuration information according to the second indication information, and send the second configuration information to the N hardware FWs, so as to create a virtual firewall vFW, and realize the creation of the vRouter on the N hardware FWs. The second configuration information can include virtual firewall configuration information, that is, in this embodiment, the security controller can convert the second indication information into hardware FW virtual firewall configuration delivery, that is, deliver the second configuration information, and realize the deployment of the hardware FW side virtual firewall configuration.

[0068] It should be noted that the cloud management platform maintains a docking physical topology, and the docking physical topology can include M hardware DC-GWs and N hardware FWs, so that creating a virtual firewall vFW on the hardware FW can be to create a virtual firewall vFW on each of the N hardware FWs in the docking physical topology.

[0069] It should be noted that in the configuration method of the dynamic routing docking in the embodiment of the application, in the process of creating a vRouter on a hardware DC-GW and creating a vFW on a hardware FW, the cloud management platform can first create a vRouter object and a vFW object, and then the cloud management platform can call an SDN controller to create a vRouter instantiated by the vRouter object on the hardware DC-GW through first indication information, complete the creation of the vRouter on the hardware DC-GW, and call a security controller to create a vFW instantiated by the vFW object on the hardware FW through second indication information, complete the creation of the vFW on the hardware FW.

[0070] The process of the configuration method of the dynamic routing docking will be described in detail below with one specific embodiment.

[0071] As shown in Figure 6 , a configuration system structure diagram of the configuration method of the dynamic routing docking provided by the embodiment of the application, including a cloud management platform, a VIM, an SDN controller, a FW controller, a hardware DC-GW (i.e. a DC-GW in Figure 6 ) and a hardware FW (i.e. a FW in Figure 6 ), in the embodiment of the application, by introducing the cloud management platform, cooperating with the VIM, the SDN controller and the FW controller, realizing the automatic deployment of the dynamic routing docking between the DC-GW and the FW, meeting the edge cloud UPF security service requirements, supporting the rapid opening of the service. The specific process of the configuration method of the dynamic routing docking of the embodiment is as follows:

[0072] First, the cloud management platform maintains the docking physical topology of the hardware GW and the hardware FW and the working mode of the hardware FW, for example, M and N are both 2, the two hardware DC-GWs are hardware DC-GW 1-1-1 and hardware DC-GW 2-2-2, and the two hardware FWs are hardware FW 3-3-3 and hardware FW 4-4-4, and the logistics topology information is shown in Table 1.

[0073] Table 1 Topology information of hardware GW and hardware FW

[0074]

[0075] The hardware DC-GW 1-1-1 (i.e., DC-GW1) is physically connected with the eth-trunk 0 port of the hardware FW 3-3-3 (i.e., FW1) through the eth-trunk 0 port of the hardware DC-GW 1-1-1, the hardware DC-GW 1-1-1 is physically connected with the eth-trunk 0 port of the hardware FW 4-4-4 (i.e., FW2) through the eth-trunk 1 port of the hardware DC-GW 1-1-1, the hardware DC-GW 2-2-2 (i.e., DC-GW2) is physically connected with the eth-trunk 1 port of the hardware FW 3-3-3 through the eth-trunk 0 port of the hardware DC-GW 2-2-2, and the hardware DC-GW 2-2-2 is physically connected with the eth-trunk 1 port of the hardware FW 4-4-4 through the eth-trunk 1 port of the hardware DC-GW 2-2-2.

[0076] The cloud management platform creates a service vRouter object and a vFW object, and calls the VIM and the SDN controller to create corresponding instantiated vRouters on the hardware DC-GW and calls the security controller to create corresponding instantiated vFWs on the hardware FW, so as to realize the creation of the vRouters on the hardware DC-GW and the creation of the virtual firewalls vFWs on the hardware FW.

[0077] As shown in Figure 7 and Figure 8 , the cloud management platform creates an interconnection logical link between the vRouter and the vFW and dynamically routes to dock, specifically including:

[0078] The cloud management platform allocates IP and VLAN resources, and respectively calls the SDN controller and the security controller to create the interconnection logical links of DC-GW1-FW1, DC-GW2-FW1, DC-GW1-FW2 and DC-GW2-FW2.

[0079] The cloud management platform respectively calls the VIM and the security controller to create the BGP / OSPF route neighbors corresponding to the logical links of DC-GW1-FW1, DC-GW2-FW1, DC-GW1-FW2 and DC-GW2-FW2.

[0080] The cloud management platform arranges a routing policy, respectively calls the VIM and the security controller to create the routing policy, and applies the routing policy to the BGP / OSPF, which is used to control which external routes are introduced and which routes are received and published.

[0081] It should be noted that the functions of the management modules are summarized as follows:

[0082] Cloud management platform: the cloud management platform maintains the hardware GW and the hardware FW to dock the physical topology and the working mode; manages the IP, VLAN network resources docked by the interconnected logical link; creates the interconnected logical link and the BGP / OSPF neighbor between the GW-FW, and arranges the routing strategy to be applied to the BGP / OSPF, and cooperates the VIM / SDN controller and the security controller to deploy.

[0083] SDN controller: northwardly docking the cloud management platform, receiving the message of creating the vRouter, the interconnected interface (logical interface, interconnected logical link), the BGP / OSPF routing neighbor and the routing strategy, and southwardly docking the hardware DC-GW, converting the creation message into the DC-GW configuration to be issued, and realizing the configuration deployment of the network docking on the DC-GW side.

[0084] Security controller: northwardly facing the cloud management platform, receiving the message of creating the vFw, the interconnected interface, the BGP / OSPF routing neighbor and the routing strategy, and southwardly docking the hardware FW, converting the creation message into the hardware FW configuration to be issued, and realizing the configuration deployment of the network docking on the FW side.

[0085] The scheme provided by the embodiment of the application can orchestrate the vRouter and the vFW dynamic routing docking, cooperates the VIM / SDN controller and the security controller to complete the automatic deployment, the cloud management platform maintains the hardware GW and the hardware FW to dock the physical topology and the working mode; manages the IP, VLAN network resources docked by the interconnected logical link; creates the interconnected logical link and the BGP / OSPF neighbor between the GW-FW, and arranges the routing strategy to be applied to the BGP / OSPF, and cooperates the VIM / SDN controller and the security controller to deploy; the SDN controller and the security controller receive the message of creating the vRouter, the vFW, the interconnected interface and the BGP / OSPF neighbor and the routing strategy from the cloud platform in the north direction, convert the corresponding configuration of the hardware GW and the FW to be issued, and realize the automatic deployment of the GW and the FW dynamic routing docking.

[0086] As shown in Figure 9 , as shown in Figure 9 , it is a structure schematic diagram of a dynamic routing docking configuration device 900 provided by the embodiment of the application, and is applied to a cloud management platform, and the cloud management platform maintains the docking physical topology between the hardware data center gateway DC-GW and the hardware firewall FW, as shown in Figure 9 , the device 900 comprises:

[0087] A first creation module 901 is used for creating a virtual router vRouter by calling a virtual infrastructure manager VIM and a software defined network SDN controller, and creating a virtual firewall vFW by calling a security controller;

[0088] The second creating module 902 is configured to create the interconnection logical link between the vRouter and the vFW and the dynamic routing neighbor by invoking the VIM, the SDN controller and the security controller.

[0089] In one embodiment, a docking physical topology between the hardware data center gateway DC-GW and the hardware firewall FW is maintained in the cloud management platform, the docking physical topology comprising M hardware DC-GWs, N hardware FWs and a physical connection relationship between the M hardware DC-GWs and the N hardware FWs, M and N being integers greater than 1.

[0090] In one embodiment, the interconnection logical link between the vRouter and the vFW corresponds to interconnection logical links between the vRouter on the M hardware DC-GWs and the vFW on the N hardware FWs, wherein the interconnection logical link between the vRouter on one hardware DC-GW and the vFW on one hardware FW corresponds to one logical interface of the vRouter on the one hardware DC-GW and one logical interface of the vFW on the one hardware FW.

[0091] The second creating module 902 comprises:

[0092] The network resource determining unit is configured to determine docking network resources required for creating the interconnection logical link between the vRouter on the M hardware DC-GWs and the vFW on the N hardware FWs.

[0093] The first sending unit is configured to send, according to the docking network resources, third indication information for creating the logical interface to the SDN controller through the VIM, the third indication information being used for the SDN controller to generate third configuration information according to the third indication information and send the third configuration information to the M hardware DC-GWs, so as to create the logical interface between the vRouter on the M hardware DC-GWs and the vFW on the N hardware FWs.

[0094] The second sending unit is configured to send, according to the docking network resources, fourth indication information for creating the logical interface to the security controller, the fourth indication information being used for the security controller to generate fourth configuration information according to the fourth indication information and send the fourth configuration information to the N hardware FWs, so as to create the logical interface between the vFW on the N hardware FWs and the vRouter on the M hardware DC-GWs.

[0095] In one embodiment, the dynamic routing neighbor between the vRouter and the vFW corresponds to dynamic routing neighbors between the vRouter on the M hardware DC-GWs and the vFW on the N hardware FWs.

[0096] The second creating module 902 further comprises:

[0097] a third sending unit, configured to send, to the SDN controller through the VIM, fifth indication information for creating a dynamic routing neighbor of the vRouter interfacing the vFW, the fifth indication information being used for the SDN controller to generate fifth configuration information according to the fifth indication information, and send the fifth configuration information to the M hardware DC-GWs, so as to create a dynamic routing neighbor of the vRouter interfacing the vFW on the N hardware FWs on the M hardware DC-GWs;

[0098] a fourth sending unit, configured to send, to the security controller, sixth indication information for creating a dynamic routing neighbor of the vFW interfacing the vRouter, the sixth indication information being used for the security controller to generate sixth configuration information according to the sixth indication information, and send the sixth configuration information to the N hardware FWs, so as to create a dynamic routing neighbor of the vFW interfacing the vRouter on the M hardware DC-GWs on the N hardware FWs.

[0099] In one embodiment, the virtual router vRouter is created by invoking a virtual infrastructure manager VIM and a software defined network SDN controller, including:

[0100] the first indication information is used for the SDN controller to generate first configuration information according to the first indication information, and send the first configuration information to the M hardware DC-GWs, so as to create the vRouter, M being an integer greater than 1.

[0101] In one embodiment, the virtual firewall vFW is created on the hardware FW by invoking a security controller, including:

[0102] the second indication information is used for the security controller to generate second configuration information according to the second indication information, and send the second configuration information to the N hardware FWs, so as to create the vFW, N being an integer greater than 1.

[0103] In one embodiment, the cloud management platform further maintains working modes of the N hardware FWs, wherein the working modes of the N hardware FWs are master-slave modes, and the N hardware FWs are independent hardware FWs.

[0104] The configuration device for dynamic routing interfacing provided in this embodiment can implement each process of each embodiment of the configuration method for dynamic routing interfacing, the technical features are one-to-one correspondence, and the same technical effects can be achieved. To avoid repetition, no further description is given here.

[0105] The embodiment of the application further provides an electronic device, comprising a processor, a memory, and a program stored in the memory and executable on the processor, the program being executed by the processor to implement each process of the configuration method for dynamic routing docking and achieve the same technical effects. To avoid repetition, details are not described herein.

[0106] Specifically, referring to Figure 10 The embodiment of the application further provides an electronic device, comprising a bus 1001, a transceiver 1002, an antenna 1003, a bus interface 1004, a processor 1005, and a memory 1006.

[0107] The electronic device maintains a docking physical topology between a hardware data center gateway DC-GW and a hardware firewall FW;

[0108] The processor 1005 is configured to:

[0109] The virtual infrastructure manager VIM and the software defined network SDN controller are invoked to create a virtual router vRouter, and the security controller is invoked to create a virtual firewall vFW;

[0110] The VIM, the SDN controller, and the security controller are invoked to create an interconnection logical link between the vRouter and the vFW and a dynamic routing neighbor.

[0111] In one embodiment, the electronic device maintains a docking physical topology between a hardware data center gateway DC-GW and a hardware firewall FW; the docking physical topology comprises M hardware DC-GWs, N hardware FWs, and a physical connection relationship between the M hardware DC-GWs and the N hardware FWs, and M and N are integers greater than 1.

[0112] In one embodiment, the interconnection logical link between the vRouter and the vFW corresponds to an interconnection logical link between a vRouter on the M hardware DC-GWs and a vFW on the N hardware FWs, wherein the interconnection logical link between the vRouter on one hardware DC-GW and the vFW on one hardware FW corresponds to one logical interface of the vRouter on the one hardware DC-GW and one logical interface of the vFW on the one hardware FW.

[0113] The processor 1005 is specifically configured to:

[0114] Based on the docking physical topology, the docking network resources required for creating the interconnection logical link between the vRouter on the M hardware DC-GWs and the vFW on the N hardware FWs are determined;

[0115] According to the network resource, third indication information for creating a logical interface is sent to an SDN controller through a VIM, the third indication information is used for the SDN controller to generate third configuration information according to the third indication information, and the third configuration information is sent to M hardware DC-GWs, so as to create a logical interface in which the vRouter on the M hardware DC-GWs interfaces the vFW on the N hardware FWs;

[0116] According to the network resource, fourth indication information for creating a logical interface is sent to a security controller, the fourth indication information is used for the security controller to generate fourth configuration information according to the fourth indication information, and the fourth configuration information is sent to N hardware FWs, so as to create a logical interface in which the vFW on the N hardware FWs interfaces the vRouter on the M hardware DC-GWs.

[0117] In one embodiment, the dynamic routing neighbor between the vRouter and the vFW corresponds to a dynamic routing neighbor between the vRouter on the M hardware DC-GWs and the vFW on the N hardware FWs.

[0118] The processor 1005 is also specifically configured to:

[0119] Fifth indication information for creating a dynamic routing neighbor in which the vRouter interfaces the vFW is sent to an SDN controller through a VIM, the fifth indication information is used for the SDN controller to generate fifth configuration information according to the fifth indication information, and the fifth configuration information is sent to M hardware DC-GWs, so as to create a dynamic routing neighbor in which the vRouter on the M hardware DC-GWs interfaces the vFW on the N hardware FWs.

[0120] Sixth indication information for creating a dynamic routing neighbor in which the vFW interfaces the vRouter is sent to a security controller, the sixth indication information is used for the security controller to generate sixth configuration information according to the sixth indication information, and the sixth configuration information is sent to N hardware FWs, so as to create a dynamic routing neighbor in which the vFW on the N hardware FWs interfaces the vRouter on the M hardware DC-GWs.

[0121] In one embodiment, a virtual router vRouter is created by invoking a virtual infrastructure manager VIM and a software defined network SDN controller, including:

[0122] First indication information is sent to an SDN controller through a VIM, wherein the first indication information is used for the SDN controller to generate first configuration information according to the first indication information, and the first configuration information is sent to M hardware DC-GWs, so as to create a vRouter, and M is an integer greater than 1.

[0123] In one embodiment, a virtual firewall vFW is created by invoking a security controller, including:

[0124] The second indication information is used for the security controller to generate second configuration information according to the second indication information, and send the second configuration information to the N hardware FWs, to create the vFW, N is an integer greater than 1.

[0125] In one embodiment, the working mode of the N hardware FWs is also maintained in the cloud management platform, wherein the working mode of the N hardware FWs is a master-slave mode, and the N hardware FWs are independent hardware FWs.

[0126] In Figure 10 The bus architecture (represented by bus 1001) can include any number of interconnecting buses and bridges, and the bus 1001 links together various circuits such as the processor 1005 and the memory 1006 represented by one or more processors and the memory, respectively. The bus 1001 can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and thus, not further described herein. The bus interface 1004 provides an interface between the bus 1001 and the transceiver 1002. The transceiver 1002 can be one element or multiple elements, such as multiple receivers and transmitters, which provide a means for communicating with various other apparatuses over a transmission medium. Data processed by the processor 1005 is transmitted over a wireless medium via the antenna 1003, and further, the antenna 1003 also receives data and transmits the data to the processor 1005.

[0127] The processor 1005 is responsible for managing the bus 1001 and general processing, and can also provide various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. The memory 1006 can be used to store data used by the processor 1005 in performing operations.

[0128] Optionally, the processor 1005 can be a CPU, an ASIC, an FPGA, or a CPLD.

[0129] The computer readable storage medium stores a computer program, which is executed by the processor to implement each process of the configuration method for dynamic routing docking according to the embodiments of the application, and achieve the same technical effects. To avoid repetition, details are not described herein. The computer readable storage medium includes a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0130] It should be noted that, in the present document, the terms "comprises / comprising" or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element preceded by "comprises... a" does not, without more constraints, foreclose the existence of additional identical elements in the process, method, article, or apparatus that comprises the recited element.

[0131] Through the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be realized by means of software and necessary general hardware platforms, of course, they can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product in essence or in the form of a part of the prior art that makes a contribution. The computer software product is stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disk) and includes a plurality of instructions for causing a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods of various embodiments of the present application.

[0132] The embodiments of the present application are described above in combination with the accompanying drawings, but the present application is not limited to the above-described specific embodiments, and the above-described specific embodiments are merely illustrative and not restrictive. Those skilled in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the scope of protection of the claims.

Claims

1. A configuration method for dynamic routing, characterized in that, The configuration method, applied to a cloud management platform, includes: A virtual router (vRouter) is created by calling the Virtual Infrastructure Manager (VIM) and the Software Defined Networking (SDN) controller; a virtual firewall (vFW) is created by calling the Security Controller. By invoking the VIM, the SDN controller, and the security controller, logical interconnection links and dynamic routing neighbors between the vRouter and the vFW are created, including: Determine the network resources required to create logical interconnection links between M hardware DC-GW vRouters and N hardware FWs vFWs; Based on the network resources being connected, the third instruction information for creating a logical interface is sent to the SDN controller via VIM. The third instruction information is used by the SDN controller to generate third configuration information and send the third configuration information to M hardware DC-GWs to create a logical interface for vRouter on M hardware DC-GWs to connect to vFW on N hardware FWs. Based on the network resources being connected, a fourth instruction message for creating a logical interface is sent to the security controller. The security controller generates a fourth configuration message based on the fourth instruction message and sends the fourth configuration message to N hardware FWs to create a logical interface for the vFWs on the N hardware FWs to connect to the vRouters on the M hardware DC-GWs. The dynamic routing neighbors between the vRouter and the vFW correspond to M vRouters on the hardware DC-GW and N dynamic routing neighbors between the vFWs on the hardware FWs; The step of creating interconnection logical links and dynamic routing neighbors between the vRouter and the vFW by invoking the VIM, the SDN controller, and the security controller also includes: The VIM sends a fifth indication message to the SDN controller to create a dynamic routing neighbor for the vRouter to connect to the vFW. The fifth indication message is used by the SDN controller to generate a fifth configuration message and send the fifth configuration message to the M hardware DC-GWs to create a dynamic routing neighbor for the vRouter on the M hardware DC-GWs to connect to the vFW on the N hardware FWs. A sixth instruction message is sent to the security controller for creating dynamic routing neighbors for vFW to connect to vRouter. The sixth instruction message is used by the security controller to generate sixth configuration information and send the sixth configuration information to the N hardware FWs to create dynamic routing neighbors for vFW on the N hardware FWs to connect to vRouter on the M hardware DC-GWs.

2. The method according to claim 1, characterized in that, The cloud management platform maintains the physical topology between hardware data center gateways (DC-GW) and hardware firewalls (FW). The physical topology includes M hardware DC-GWs, N hardware FWs, and the physical connection relationships between the M hardware DC-GWs and the N hardware FWs, where M and N are integers greater than 1.

3. The method according to claim 1, characterized in that, The process of creating a virtual router (vRouter) by invoking the Virtual Infrastructure Manager (VIM) and the Software-Defined Networking (SDN) controller includes: The VIM sends a first indication message to the SDN controller, wherein the first indication message is used by the SDN controller to generate first configuration information based on the first indication message, and sends the first configuration information to M hardware DC-GWs to create vRouter, where M is an integer greater than 1.

4. The method according to claim 1, characterized in that, The process of creating a virtual firewall (vFW) by invoking the security controller includes: Send a second instruction to the security controller, wherein the second instruction is used by the security controller to generate second configuration information based on the second instruction and send the second configuration information to N hardware FWs to create vFWs, where N is an integer greater than 1.

5. The method according to claim 1, characterized in that, The interconnection logical links between the vRouter and the vFW correspond to M vRouters on hardware DC-GW and N vFW interconnection logical links on hardware FW. Among them, one vRouter on hardware DC-GW and one vFW interconnection logical link on hardware FW correspond to one logical interface of the vRouter on hardware DC-GW and one logical interface of the vFW on hardware FW.

6. A configuration device for dynamic routing, characterized in that, The device, applied to a cloud management platform, includes: The first creation module is used to create a virtual router (vRouter) by calling the Virtual Infrastructure Manager (VIM) and the Software Defined Network (SDN) controller, and to create a virtual firewall (vFW) by calling the Security Controller. The second creation module is used to create interconnection logical links and dynamic routing neighbors between the vRouter and the vFW by calling the VIM, the SDN controller and the security controller, including: determining the docking network resources required to create interconnection logical links between M hardware DC-GW vRouters and N hardware FWs; Based on the network resources being connected, the third instruction information for creating a logical interface is sent to the SDN controller via VIM. The third instruction information is used by the SDN controller to generate third configuration information and send the third configuration information to M hardware DC-GWs to create a logical interface for vRouter on M hardware DC-GWs to connect to vFW on N hardware FWs. Based on the network resources being connected, a fourth instruction message for creating a logical interface is sent to the security controller. The security controller generates a fourth configuration message based on the fourth instruction message and sends the fourth configuration message to N hardware FWs to create a logical interface for the vFWs on the N hardware FWs to connect to the vRouters on the M hardware DC-GWs. The dynamic routing neighbors between the vRouter and the vFW correspond to M vRouters on the hardware DC-GW and N dynamic routing neighbors between the vFWs on the hardware FWs; The step of creating interconnection logical links and dynamic routing neighbors between the vRouter and the vFW by invoking the VIM, the SDN controller, and the security controller also includes: The VIM sends a fifth indication message to the SDN controller to create a dynamic routing neighbor for the vRouter to connect to the vFW. The fifth indication message is used by the SDN controller to generate a fifth configuration message and send the fifth configuration message to the M hardware DC-GWs to create a dynamic routing neighbor for the vRouter on the M hardware DC-GWs to connect to the vFW on the N hardware FWs. A sixth instruction message is sent to the security controller for creating dynamic routing neighbors for vFW to connect to vRouter. The sixth instruction message is used by the security controller to generate sixth configuration information and send the sixth configuration information to the N hardware FWs to create dynamic routing neighbors for vFW on the N hardware FWs to connect to vRouter on the M hardware DC-GWs.

7. An electronic device, characterized in that, Includes a transceiver and a processor, wherein the processor is used for: A virtual router (vRouter) is created by calling the Virtual Infrastructure Manager (VIM) and the Software Defined Networking (SDN) controller; a virtual firewall (vFW) is created by calling the Security Controller. By invoking the VIM, the SDN controller, and the security controller, the interconnection logical links and dynamic routing neighbors between the vRouter and the vFW are created, including: determining the interfacing network resources required to create interconnection logical links between M hardware DC-GW vRouters and N hardware FWs; Based on the network resources being connected, the third instruction information for creating a logical interface is sent to the SDN controller via VIM. The third instruction information is used by the SDN controller to generate third configuration information and send the third configuration information to M hardware DC-GWs to create a logical interface for vRouter on M hardware DC-GWs to connect to vFW on N hardware FWs. Based on the network resources being connected, a fourth instruction message for creating a logical interface is sent to the security controller. The security controller generates a fourth configuration message based on the fourth instruction message and sends the fourth configuration message to N hardware FWs to create a logical interface for the vFWs on the N hardware FWs to connect to the vRouters on the M hardware DC-GWs. The dynamic routing neighbors between the vRouter and the vFW correspond to M vRouters on the hardware DC-GW and N dynamic routing neighbors between the vFWs on the hardware FWs; The step of creating interconnection logical links and dynamic routing neighbors between the vRouter and the vFW by invoking the VIM, the SDN controller, and the security controller also includes: The VIM sends a fifth indication message to the SDN controller to create a dynamic routing neighbor for the vRouter to connect to the vFW. The fifth indication message is used by the SDN controller to generate a fifth configuration message and send the fifth configuration message to the M hardware DC-GWs to create a dynamic routing neighbor for the vRouter on the M hardware DC-GWs to connect to the vFW on the N hardware FWs. A sixth instruction message is sent to the security controller for creating dynamic routing neighbors for vFW to connect to vRouter. The sixth instruction message is used by the security controller to generate sixth configuration information and send the sixth configuration information to the N hardware FWs to create dynamic routing neighbors for vFW on the N hardware FWs to connect to vRouter on the M hardware DC-GWs.

8. An electronic device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method as described in any one of claims 1 to 5.

9. A computer-readable storage medium having a computer program stored thereon, the computer program, when executed by a processor, implementing the steps of the method of any one of claims 1-5.

Images