CN108123819B - Virtual-real network seamless fusion simulation method - Google Patents

Virtual-real network seamless fusion simulation method Download PDF

Info

Publication number
CN108123819B
CN108123819B CN201611077852.6A CN201611077852A CN108123819B CN 108123819 B CN108123819 B CN 108123819B CN 201611077852 A CN201611077852 A CN 201611077852A CN 108123819 B CN108123819 B CN 108123819B
Authority
CN
China
Prior art keywords
network
virtual
address
flow
ovs
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201611077852.6A
Other languages
Chinese (zh)
Other versions
CN108123819A (en
Inventor
王晓锋
邓博
蒋敏
刘渊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jiangnan University
Original Assignee
Jiangnan University
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jiangnan University filed Critical Jiangnan University
Priority to CN201611077852.6A priority Critical patent/CN108123819B/en
Publication of CN108123819A publication Critical patent/CN108123819A/en
Application granted granted Critical
Publication of CN108123819B publication Critical patent/CN108123819B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14Network analysis or design
    • H04L41/145Network analysis or design involving simulating, designing, planning or modelling of a network

Abstract

The invention discloses a simulation method for seamless fusion of virtual and real networks, which relates to the technical field of network simulation and solves the problem that the transmission of virtual and real fused network data packets based on an OpenStack platform is opaque, and the method comprises the following steps: building a basic environment of an OpenStack cloud computing platform; constructing a target virtual network, wherein an autonomously developed router is used in the virtual network; running a flow table configuration script to enable data packets between the virtual network and the real network to be transmitted transparently; and connecting the physical equipment with the virtual network to form a virtual-real fused network. The invention realizes the construction of a transparent virtual-real fused network environment by providing a virtual-real network seamless fused simulation method, and can be used for network security evaluation and computer system security evaluation.

Description

Virtual-real network seamless fusion simulation method
Technical Field
The invention relates to the technical field of network analog simulation, in particular to a simulation method for seamless fusion of virtual and real networks.
Background
Network research has been developed for a long time based on three main technologies, namely, network simulation and a physical test bed, but the network simulation technology is difficult to ensure the fidelity of network node reproduction, the network simulation technology has limitations on scale, and the physical test bed is difficult to support the research of large-scale network behaviors due to the defects of high cost, poor flexibility, poor experiment repeatability and the like, so that relevant experts propose a virtual-real fused network research environment, and the technology can support large-scale and high-fidelity network experiments by combining the advantages of the three technologies, and the technology is gradually becoming mainstream.
OpenStack, as a representative of a cloud computing platform, has powerful functions and can construct diversified virtual networks, but communication between virtual networks and real networks needs to be subjected to address conversion through router namespace, so that data packet transmission is opaque for scientific research, and network simulation is not vivid.
Open VSwitch (OVS) is a virtual switch that runs on a virtualized platform and provides a two-layer switching function for dynamically changing endpoints. And each bridge in the OVS operates the data packets flowing through according to the flow table rule of the bridge, and each port on the OVS receives and transmits the data packets according to the vlan tag. If a port on the OVS is configured with a vlan tag, the port can only receive a packet with the vlan tag, and for traffic flowing into the OVS through the port, the port can automatically mark the vlan tag carried by the port for the packet, and for traffic flowing out of the OVS through the port, the port can automatically delete the vlan tag carried by the packet. An OVS can be used as a virtual switch in OpenStack, a network is established in OpenStack, and the OVS can configure a unique vlan tag for the network, so that the purpose of isolating the network is achieved. The OVS can conveniently manage the flow table by using an OpenFlow protocol according to the characteristics of controlling and forwarding the data packet by the flow table and the vlan tag, thereby achieving the purposes of controlling the flow direction of the data packet, isolating the network, monitoring the flow and the like.
Disclosure of Invention
The invention aims to provide a virtual-real network seamless fusion simulation method, which can realize virtual-real network fusion by means of an OpenStack platform and ensure transparent transmission of data packets.
The technical scheme for solving the problems is as follows:
s1: building a basic environment of an OpenStack cloud computing platform, wherein an OVS is used as a virtual switch, Gre modes are adopted for communication among nodes, network nodes and control nodes are mutually independent, and the independent network nodes serve as virtual and real interconnection servers; the built environment comprises a control node, a network node and a plurality of computing nodes;
s2: constructing a target virtual network, wherein the virtual network comprises an OpenStack virtual cloud host, an Open vSwitch virtual switch and an autonomously developed virtual router, and abandoning the virtual router carried by the OpenStack;
s3: running a flow table configuration script written by python autonomously, wherein the script has the function of enabling a data packet to jump over a router namespace in a network node, thereby avoiding address conversion and realizing transparent transmission of the data packet, and the detailed configuration process is as follows:
(1) remotely querying a neutron database of the control node;
(2) if the flowInfo table exists in the database, directly entering the next step, otherwise, establishing the table on the control node, and adding the flow table on br-ex in the network node OVS, so that the flow entering all the virtual networks is sent to the physical network;
(3) using internal connection query to query the ports table and the subnet table of the database, comparing the port table and the subnet table with the data in the flowInfo table, searching the IP address and the id of the network which are not recorded in the flowInfo table and the name of the DHCP interface corresponding to the IP address and the id, if the IP address and the id are found, entering the next step, otherwise, directly entering (7);
(4) according to the interface name obtained in the last step, ovs-db of the network node is inquired, the interface is found, and a vlan tag of the network where the interface is located is obtained;
(5) storing the id, IP address, vlan tag and self-defined node name of the network into a flowInfo table;
(6) establishing two flow table rules for br-int in a network node OVS of each network according to the obtained information, wherein the two flow table rules correspond to an IP protocol and an ARP protocol, and the two flow table rules have the function of enabling all the flow coming from the physical network to modify a vlan tag of a data packet according to a source address of the data packet; the command format is' ovs-offset add-flow br-int table is 0, priority is 10, dl _ type is 0x0800, in _ port is x, vlan _ tci is 0x0000, nw _ src is y, actions is mod _ vlan _ vid: z, norm ", where x is the number of the interface where br-int connects br-ex, dl _ type refers to the protocol type, 0x0800 is the IP protocol, 0x0806 is the ARP protocol, nw _ src is the packet source address, y is changed to the network address of the current operation, and z is vlan tag;
(7) inquiring a subnet table in a database, and taking the IP address of the network as a keyword to acquire the network which exists in the flowInfo and does not exist in the subnet so as to obtain the IP addresses of the networks;
(8) deleting the row in which these IP addresses are located from the flowInfo table;
(9) deleting a corresponding flow table rule on the network node according to the network IP address obtained in (1), wherein the command format is "ovs-offset del-flow br-int table ═ 0, in _ port ═ x, IP, nw _ dst ═ y" and "ovs-offset del-flow br-int table ═ 0, in _ port ═ x, arp, arp _ spa ═ y", where x is the number of the interface br-int connecting br-ex, and y is the network IP address;
s4: and connecting the physical equipment with the virtual network to form a virtual-real fused network.
The OVS virtual switch is composed of bridges with different functions, wherein br-tun is responsible for tunnel communication, br-ex is responsible for physical network communication, and br-int is responsible for sending data packets to each virtual machine or bridge.
The autonomously developed virtual router refers to a virtual cloud host created by using a Linux system mirror image, and the virtual cloud host is not used as a source host and a destination host for receiving and transmitting data packets, but used as a router for forwarding the data packets so as to enable virtual machines in different virtual networks to communicate with each other.
The basic OpenStack architecture is an architecture which only has one network node and each network node only has one network card connected with an external network;
the network card connected with the external network is a network card connected with the network node and the physical network.
The invention has the following beneficial effects:
1. the virtual-real network fusion avoids the defects of the network simulation technology and the network simulation technology in fidelity and scale, and also avoids the defects of high cost and poor usability of a real object test bed;
2. the physical network can select any virtual network to connect as required, the physical machine can be connected to any virtual network only by changing the IP address of the physical machine, and the whole network environment can be flexibly configured;
3. when the constructed virtual-real network carries out communication, NAT address conversion is skipped, the whole communication process is transparent, and the reality of virtual-real network fusion simulation is improved.
Drawings
FIG. 1 is a flow chart of a simulation method for seamless fusion of virtual and real networks;
FIG. 2 is a flow chart of script auto-configuration flow table rules;
FIG. 3 is a diagram of a network topology used in an embodiment of the present invention;
FIG. 4 is a diagram illustrating the results of verifying transparency;
FIG. 5 is a packet flow diagram of a constructed virtual-real network;
fig. 6 is a topology diagram of a physical machine communicating with a virtual machine via a network node and a virtual router.
Detailed Description
The following describes the embodiments of the present invention with reference to the drawings and examples.
The flow chart of the embodiment is shown in fig. 1, and the technical scheme is as follows:
s1: the basic environment of the OpenStack cloud computing platform is built, wherein the virtual switch uses OVS, the communication among all nodes adopts an Gre mode, the network nodes are independent from the control nodes, the independent network nodes serve as virtual and real interconnection servers, and the built environment comprises one control node, one network node and a plurality of computing nodes;
s2: constructing a target virtual network, wherein the virtual network comprises an OpenStack virtual cloud host, an Open vSwitch virtual switch and an autonomously developed virtual router, and abandoning the virtual router carried by the OpenStack;
s3: a flow table configuration script written by python is run, the function of the script enables a data packet to jump over a router namespace in a network node, so that address conversion is avoided, transparent transmission of the data packet is realized, a flow chart of flow table configuration is shown in fig. 2, and the detailed configuration process is as follows:
(1) remotely querying a neutron database of the control node;
(2) if the flowInfo table exists in the database, directly entering the next step, otherwise, establishing the table, and adding a flow table to br-ex in the network node OVS to enable all flows entering the virtual network to be sent to the physical network;
(3) using internal connection query to query the ports table and the subnet table of the database, comparing the port table and the subnet table with the data in the flowInfo table, searching the IP address and the id of the network which are not recorded in the flowInfo table and the name of the DHCP interface corresponding to the IP address and the id, if the IP address and the id are found, entering the next step, otherwise, directly entering (7);
(4) according to the interface name obtained in the last step, ovs-db of the network node is inquired, the interface is found, and a vlan tag of the network where the interface is located is obtained;
(5) storing the id, IP address, vlan tag and self-defined node name of the network into a flowInfo table;
(6) establishing two flow table rules for br-int in a network node OVS of each network according to the obtained information, wherein the two flow table rules correspond to an IP protocol and an ARP protocol, and the two flow table rules have the function of enabling all the flow coming from the physical network to modify a vlan tag of a data packet according to a source address of the data packet; the command format is' ovs-offset add-flow br-int table is 0, priority is 10, dl _ type is 0x0800, in _ port is x, vlan _ tci is 0x0000, nw _ src is y, actions is mod _ vlan _ vid: z, norm ", where x is the number of the interface where br-int connects br-ex, dl _ type refers to the protocol type, 0x0800 is the IP protocol, 0x0806 is the ARP protocol, nw _ src is the packet source address, y is changed to the network address of the current operation, and z is vlan tag;
(7) inquiring a subnet table in a database, and taking the IP address of the network as a keyword to acquire the network which exists in the flowInfo and does not exist in the subnet so as to obtain the IP addresses of the networks;
(8) deleting the row in which these IP addresses are located from the flowInfo table;
(9) deleting a corresponding flow table rule on the network node according to the network IP address obtained in (1), wherein the command format is "ovs-offset del-flow br-int table ═ 0, in _ port ═ x, IP, nw _ dst ═ y" and "ovs-offset del-flow br-int table ═ 0, in _ port ═ x, arp, arp _ spa ═ y", where x is the number of the interface br-int connecting br-ex, and y is the network IP address;
s4: and connecting the physical equipment with the virtual network to form a virtual-real fused network.
In step S1, the basic environment established in this example includes a control node, a network node, and two computing nodes, where the IP address of the network card connected to the management network by the control node is 192.168.1.31, the IP addresses of the network cards connected to the management network by the network node and the tunnel network are 192.168.1.11 and 10.0.0.11, the IP addresses of the network cards connected to the management network by the computing node 1 and the tunnel network are 192.168.1.21 and 10.0.0.21, and the IP addresses of the network cards connected to the management network by the computing node 2 and the tunnel network are 192.168.1.22 and 10.0.0.22, respectively.
In the above technical solution, in step S2, taking establishing 3 networks as an example for explanation, the IP addresses are 192.168.100.0/24, 172.18.146.0/24 and 10.10.1.0/24, respectively, and 4 virtual cloud hosts VM1, VM2, VM3 and VM4 are established, and the IP addresses are 192.168.100.3, 192.168.100.4, 172.18.146.3 and 172.18.146.4, respectively.
In the above technical solution, in step S3, the environment established in this embodiment is combined to run a script at the network node, and the specific method is as follows:
because the script is run for the first time after the environment is built, a flowInfo table is newly built, and a flow table for releasing all flows is added to br-ex, and the command is as follows: ovs-ofctl add-flow br-ex priority is 9, in _ port is 2, actions is strip _ vlan, NORMAL means that all traffic entering from port No. 2 is removed from vlan tag and forwarded normally, in this embodiment, port No. 2 is a port where br-ex is connected to br-int; after the configuration, the data packet sent by the virtual network can reach the physical device through all the network nodes.
Then configuring a flow table on br-int, because no flowInfo table is added into any of 192.168.100.0/24, 172.18.146.0/24 and 10.10.1.0/24, an internal connection query obtains information of three networks, and then queries a local ovs-db to obtain vlan tags of the three networks, which are 2, 3 and 4 respectively; then, the obtained related information and the self-defined node name are stored into a flowInfo table, which is a Network node self-defined name "Network 1" in this embodiment; the specific command for the IP protocol to add a flow table to the network 192.168.100.0/24 is as follows: ovs-offset add-flow br-int table is 0, priority is 10, dl _ type is 0x0800, in _ port is 2, vlan _ tci is 0x0000, nw _ src is 192.168.100.0/24, actions is mod _ vlan _ vid:2, norm al, the bar flow table means that all IP packets entering from port No. 2 are executed with vlan tag being 2 and forwarded normally, where port No. 2 in this embodiment corresponds to br-int to which the interface of br-ex is connected; adding flow tables for other protocols and networks only needs to modify parameters including protocol types, data packet source addresses and vlan tags; after the configuration is completed, the flow entering the virtual network by the physical device can be sent to the target virtual machine.
The flow table rule of the deleted network is deleted by the script, and the script takes the IP address of the network as a keyword to acquire the network which exists in the flowInfo but does not exist in the subnet, namely the deleted network is searched; in this embodiment, the network 10.10.1.0/24 is deleted, after the script queries that the network is deleted, the row where the network is located is deleted from the flowInfo table, and then the corresponding flow table rule is deleted from the network node by using a command, "ovs-offset del-flow br-int table is 0, in _ port is 2, IP, nw _ dst is 10.10.1.0/24", the command deletes the flow table rule for the IP protocol for the network 10.10.1.0/24, and then the command for the ARP protocol is deleted by using a command "ovs-offset del-flow br-int table is 0, in _ port is 2, ARP, ARP _ spa is 10.10.1.0/24"; at this point, all flow table information related to the network 10.10.1.0/24 is deleted.
In the above technical solution, in step S4, 1 physical host is connected to the network card of the network node connected to the external network, the IP address of the physical host can be configured according to the experiment requirement, and the physical host needs to be connected to a virtual network, and only the IP address of the physical host needs to be configured to the IP of the network. In this embodiment, the physical machine is first connected to 192.168.100.0/24 with the IP address configured to 192.168.100.100.
The topology of the constructed virtual-real converged network is shown in fig. 3, and the virtual-real converged network constructed based on the steps can be used for carrying out various testing and research works.
Based on the present embodiment, the following test work can be deployed but not limited:
(1) the physical machine with the IP address of 192.168.100.100 and the virtual machine on the same network execute p-ing commands mutually, then the IP address of the physical machine is changed into 172.18.146.100, and the physical machine and the virtual machine on the same network execute ping commands mutually, and the result shows that the physical machine and the virtual machine on the same network can be communicated with each other;
(2) using traceroute command with VM1 as destination address on the physical machine, the result shows that its routing path really has only 1 hop, proving transparency, the result is shown in fig. 4, the data packet flow diagram is shown in fig. 5;
(3) after the virtual router is added, the physical machines and the virtual machines belonging to different networks can be communicated through the virtual router, the topology is shown in fig. 6, the number of routes is checked by using a traceroute command, and a result shows 3 hops, which is in line with expectation.
The experimental results show that the simulation method for seamless fusion of virtual and real networks can realize a transparent virtual and real fused network environment and solve the problem of opaque data packet transmission in the virtual and real interconnection environment based on the OpenStack platform.
The above-described embodiments are intended to be illustrative of the present invention, rather than limiting, and various changes may be made without departing from the spirit of the invention, which will be apparent to those skilled in the art from the teachings herein.

Claims (1)

1. A simulation method for seamless fusion of virtual and actual networks is characterized by comprising the following steps:
s1: the basic environment of the OpenStack cloud computing platform is built, wherein the virtual switch uses OVS, the communication among all nodes adopts an Gre mode, the network nodes are independent from the control nodes, the independent network nodes serve as virtual and real interconnection servers, and the built environment comprises one control node, one network node and a plurality of computing nodes;
s2: constructing a target virtual network, wherein the virtual network comprises an OpenStack virtual cloud host, an Open vSwitch virtual switch and a virtual router which is constructed based on a virtualization technology and supports RIP, OSPF and BGP protocols, and abandoning the virtual router of the OpenStack;
s3: running a flow table configuration script written by python autonomously, wherein the script has the function of enabling a data packet to jump over a router namespace in a network node, thereby avoiding address conversion and realizing transparent transmission of the data packet;
s4: connecting the physical equipment and the virtual network to form a virtual-real fused network;
the configuration steps of the flow table configuration script are as follows:
(1) remotely querying a neutron database of the control node;
(2) if the flowInfo table exists in the database, directly entering the next step, otherwise, establishing the table on the control node, and adding the flow table on br-ex in the network node OVS, so that the flow entering all the virtual networks is sent to the physical network;
(3) using internal connection query to query the ports table and the subnet table of the database, comparing the port table and the subnet table with the data in the flowInfo table, searching the IP address and the id of the network which are not recorded in the flowInfo table and the name of the DHCP interface corresponding to the IP address and the id, if the IP address and the id are found, entering the next step, otherwise, directly entering (7);
(4) according to the interface name obtained in the last step, ovs-db of the network node is inquired, the interface is found, and a vlan tag of the network where the interface is located is obtained;
(5) storing the id, IP address, vlan tag and self-defined node name of the network into a flowInfo table;
(6) establishing two flow table rules for br-int in a network node OVS of each network according to the obtained information, wherein the two flow table rules correspond to an IP protocol and an ARP protocol, and the two flow table rules have the function of enabling all the flow coming from the physical network to modify a vlan tag of a data packet according to a source address of the data packet; the command format is' ovs-offset add-flow br-int table is 0, priority is 10, dl _ type is 0x0800, in _ port is x, vlan _ tci is 0x0000, nw _ src is y, actions is mod _ vlan _ vid: z, norm ", where x is the number of the interface where br-int connects br-ex, dl _ type refers to the protocol type, 0x0800 is the IP protocol, 0x0806 is the ARP protocol, nw _ src is the packet source address, y is changed to the network address of the current operation, and z is vlan tag;
(7) inquiring a subnet table in a database, and taking the IP address of the network as a keyword to acquire the network which exists in the flowInfo and does not exist in the subnet so as to obtain the IP addresses of the networks;
(8) deleting the row in which these IP addresses are located from the flowInfo table;
(9) according to the network IP address obtained in (1), the corresponding flow table rule is deleted on the local network node, and the command format is "ovs-offset del-flow br-int table ═ 0, in _ port ═ x, IP, nw _ dst ═ y" and "ovs-offset flow br-int table ═ 0, in _ port ═ x, arp, arp _ spa ═ y", where x is the number of the interface connected to br-ex and y is the IP address of the network.
CN201611077852.6A 2016-11-30 2016-11-30 Virtual-real network seamless fusion simulation method Active CN108123819B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201611077852.6A CN108123819B (en) 2016-11-30 2016-11-30 Virtual-real network seamless fusion simulation method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201611077852.6A CN108123819B (en) 2016-11-30 2016-11-30 Virtual-real network seamless fusion simulation method

Publications (2)

Publication Number Publication Date
CN108123819A CN108123819A (en) 2018-06-05
CN108123819B true CN108123819B (en) 2020-10-16

Family

ID=62225945

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201611077852.6A Active CN108123819B (en) 2016-11-30 2016-11-30 Virtual-real network seamless fusion simulation method

Country Status (1)

Country Link
CN (1) CN108123819B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109981493B (en) * 2019-04-09 2020-05-01 苏州浪潮智能科技有限公司 Method and device for configuring virtual machine network
CN110635943B (en) * 2019-09-02 2020-11-06 北京航空航天大学 Spark computing framework-based network flow simulation system in network transmission process
CN111181861A (en) * 2020-01-13 2020-05-19 山东汇贸电子口岸有限公司 Policy routing implementation method and device
CN112866036B (en) * 2021-02-24 2022-03-01 鹏城实验室 Network flow simulation method and system of cloud computing platform and computer storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103152239A (en) * 2013-02-25 2013-06-12 汉柏科技有限公司 Open VSwitch-based virtual network implementation method and system
CN103401917A (en) * 2013-07-29 2013-11-20 华南理工大学 Hybrid cloud computing system based on cloud bus and realization method of hybrid cloud computing system
CN103780640A (en) * 2012-10-18 2014-05-07 中国科学院声学研究所 Multimedia cloud calculating simulation method
CN104468746A (en) * 2014-11-23 2015-03-25 国云科技股份有限公司 Method for realizing distributed virtual networks applicable to cloud platform
CN105827464A (en) * 2016-05-16 2016-08-03 江南大学 Automatically deployable virtual router establishment method

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9049115B2 (en) * 2012-12-13 2015-06-02 Cisco Technology, Inc. Enabling virtual workloads using overlay technologies to interoperate with physical network services

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103780640A (en) * 2012-10-18 2014-05-07 中国科学院声学研究所 Multimedia cloud calculating simulation method
CN103152239A (en) * 2013-02-25 2013-06-12 汉柏科技有限公司 Open VSwitch-based virtual network implementation method and system
CN103401917A (en) * 2013-07-29 2013-11-20 华南理工大学 Hybrid cloud computing system based on cloud bus and realization method of hybrid cloud computing system
CN104468746A (en) * 2014-11-23 2015-03-25 国云科技股份有限公司 Method for realizing distributed virtual networks applicable to cloud platform
CN105827464A (en) * 2016-05-16 2016-08-03 江南大学 Automatically deployable virtual router establishment method

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
EmuStack: An OpenStack-Based DTN Network Emulation Platform;Haifeng Li等;《IEEE》;20160912;全文 *
基于NS_3构建网络环境的虚实结合技术的研究;李广荣等;《高技术通讯》;20150715;全文 *

Also Published As

Publication number Publication date
CN108123819A (en) 2018-06-05

Similar Documents

Publication Publication Date Title
CN108123819B (en) Virtual-real network seamless fusion simulation method
JP5991424B2 (en) Packet rewriting device, control device, communication system, packet transmission method and program
CN105791463B (en) A kind of method and apparatus for realizing virtual machine communication
CN103997414B (en) Generate method and the network control unit of configuration information
CN109716717A (en) From software-defined network controller management virtual port channel switching equipment peer-to-peer
US9838462B2 (en) Method, apparatus, and system for data transmission
US20150163072A1 (en) Virtual Port Extender
CN108123818B (en) Simulation method for flexible and extensible fusion of virtual and actual networks
CN107948041B (en) Method and equipment for constructing VXLAN centralized multi-active gateway
EP3069471B1 (en) Optimized multicast routing in a clos-like network
US20180077048A1 (en) Controller, control method and program
CN105515802B (en) Network virtualization method and device
US11310080B2 (en) VXLAN configuration method, device, and system
CN107592216B (en) Virtual-real network fusion simulation method supporting multi-scene experimental isolation
CN106878136A (en) A kind of message forwarding method and device
Yamanaka et al. AutoVFlow: Autonomous virtualization for wide-area OpenFlow networks
CN111147372A (en) Downlink message sending and forwarding method and device
EP3605959B1 (en) Method, device and computer storage medium for implementing double control plane
KR20210093312A (en) Logic routers with segmented network elements
CN108512737B (en) Data center IP layer interconnection method and SDN controller
CN109728962B (en) Method and equipment for sending message
CN112511432B (en) Method and system for configuring and transmitting virtualization SFC (Small form factor) route of Overlay network
CN108965000B (en) Private cloud SDN drainage implementation method
CN110022263B (en) Data transmission method and related device
JP2020113836A (en) Information processing device, information processing system, and setting program

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant