WO2016145839A1 - 虚拟网络的实现方法、装置及系统 - Google Patents

虚拟网络的实现方法、装置及系统 Download PDF

Info

Publication number
WO2016145839A1
WO2016145839A1 PCT/CN2015/092127 CN2015092127W WO2016145839A1 WO 2016145839 A1 WO2016145839 A1 WO 2016145839A1 CN 2015092127 W CN2015092127 W CN 2015092127W WO 2016145839 A1 WO2016145839 A1 WO 2016145839A1
Authority
WO
WIPO (PCT)
Prior art keywords
evb
vdp
virtual network
message
bridge
Prior art date
Application number
PCT/CN2015/092127
Other languages
English (en)
French (fr)
Inventor
顾忠禹
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016145839A1 publication Critical patent/WO2016145839A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • This application relates to, but is not limited to, the field of data center technology.
  • a data center is a globally coordinated, device-specific network that delivers, accelerates, displays, calculates, and stores data on the Internet infrastructure.
  • VN Virtual Network
  • Virtual network involves many aspects such as virtualization of the network, which has attracted the attention of equipment suppliers and operators.
  • IEEE introduced 802.1Qbg (edge virtual bridge) and supports VM (Virtual Machine) ⁇ (IEEE term is virtual) Station, need to distinguish the platform that provides the virtual station, called EBB (Edge Virtual Bridging) station, connect the VSI (Virtual Station Interface) to the switch (EVB bridge) outside the virtualization platform through the EVB station.
  • EBB Edge Virtual Bridging
  • FIG 1 is a schematic diagram of the architecture of the EVB.
  • VSI VSI discovery and configuration protocol
  • CDCP CDCP
  • ECP ECP
  • FIG. 1 Figure 1 is a schematic diagram of the architecture of the EVB.
  • VSI VSI discovery and configuration protocol
  • CDCP CDCP
  • ECP ECP
  • FIG. 1 Figure 1 is a schematic diagram of the architecture of the EVB.
  • VSI VSI discovery and configuration protocol
  • CDCP CDCP
  • ECP ECP
  • FIG. 1 is a schematic diagram of the architecture of the EVB.
  • NVO3 Network Virtualization Overlay Based-on L3Network
  • NVE Network Virtualization Edge
  • VRF Virtual Routing and Forwarding
  • VDP is to implement the VM-to-EVB bridge association work, which is added to the VM.
  • the VN of NVE is very similar because VDP is an L2
  • L3 address information and to support the transmission of VN-ID information.
  • EVB has its unique state machine processing mechanism, and it will encounter problems in the application. For example, in a typical NVO3 application environment, as shown in FIG.
  • TOR Top of Rack
  • VMM virtual machine monitor
  • This paper provides a method, device and system for implementing a virtual network, which aims to solve the problem that the related VDP technology does not support the NVO3 typical application environment of the EVB station/NVE-EVB bridge/NVE.
  • a method for implementing a virtual network comprising:
  • the EVB station receives an ER (Edge Relay) in the EVB station, and represents a VDP message sent by the VM to the virtual network VN, where the VDP message includes command type indication information;
  • ER Erge Relay
  • the EVB station processes the VDP message and accesses the VM to the VN;
  • the EVB station sends the VDP packet to the EVB bridge for processing to implement the VM accessing the VN in the EVB bridge.
  • the command type indication information is defined by a filtering information field of the VDP command message; or is defined by a reserved VDP type value.
  • the EVB station supports an EVB bridge and an NVE.
  • the step of the EVB station or the EVB bridge accessing the VM to the VN includes:
  • the context of the VN includes a virtual route forwarding function VRF forwarding table
  • the VRF forwarding table entry corresponding to the VM is generated in the VRF forwarding table.
  • a device for implementing a virtual network comprising:
  • the receiving module is configured to: receive, by the ER in the EVB station, a VDP message that is sent by the VM and join the virtual network VN, where the VDP message includes command type indication information;
  • the determining module is configured to: determine, according to the command type indication information included in the VDP message, whether the VDP message is processed by the EVB station;
  • the sending module is configured to: if the VDP packet is not processed by the EVB station, send the VDP packet to the EVB bridge for processing, to implement the VM accessing the VN in the EVB bridge;
  • a processing module configured to: if the VDP message is processed by the EVB station, process the VDP message and access the VN to the VN; and implement VN identity authentication for the VM; After the VM is authenticated by the VN, if the context of the VN does not exist, the context of the VN is generated; if the VM does not have a corresponding entry in the VRF forwarding table, the VRF is A corresponding VRF forwarding table entry of the VM is generated in the forwarding table.
  • the command type indication information is defined by a filtering information field of the VDP command message; or is defined by a reserved VDP type value.
  • the implementation device is an EVB station and supports both EVB bridge and NVE functions.
  • a virtual network implementation system including the virtual network implementation device and EVB as described above Bridge, where:
  • the virtual network implementation device is configured to: receive, by the ER in the EVB station, a VDP message that is sent by the VM and join the virtual network VN, where the VDP message includes command type indication information; according to the VDP message
  • the command type indication information includes: determining whether the VDP message is processed by the virtual network implementation device; if the VDP message is processed by the virtual network implementation device, accessing the VN to the VN; The virtual network implementation device processes the VDP packet, and sends the VDP packet to an EVB bridge for processing;
  • the EVB bridge is configured to: process the VDP packet, and implement the VM accessing the VN;
  • the virtual network implementation device is further configured to: implement VN identity authentication for the VM; after the VM passes the identity authentication of the VN, generate a context of the VN if the context of the VN does not exist If the VM does not have a corresponding entry in the VRF forwarding table, the corresponding entry of the VM is generated in the VRF forwarding table.
  • the command type indication information is defined by a filtering information field of the VDP command message; or is defined by a reserved VDP type value;
  • the virtual network implementation device is an EVB station, and supports the EVB bridge and the NVE.
  • a method for implementing a virtual network comprising:
  • the edge virtual bridge EVB station receives the virtual machine interface discovery and configuration protocol VDP message of the virtual network VN sent by the edge relay ER in the EVB station on behalf of the virtual machine VM;
  • the EVB station processes the VDP message and accesses the VM to the VN.
  • a method for implementing a virtual network comprising:
  • the edge virtual bridge EVB station receives the virtual machine interface discovery and configuration protocol VDP message of the virtual network VN sent by the edge relay ER in the EVB station on behalf of the virtual machine VM;
  • the EVB station sends the VDP packet to an EVB bridge for processing to implement the VM accessing the VN in an EVB bridge.
  • a computer readable storage medium storing computer executable instructions for performing the method of any of the above.
  • the embodiment of the present invention adds a VDP packet of the virtual network VN to the received virtual machine VM.
  • the command type indication information is added, and the command type indication information indicates that the EVB station processes the VDP message, or the EVB bridge processes the VDP message to access the VM to the virtual network. Effectively avoiding the current implementation of VDP-based VN, the implementation process is complicated, the operation is complicated, and the efficiency of VN implementation is poor.
  • the VDP message added to the VN with the command type indication information is an extension of the existing VDP message.
  • the EVB station supports EVB bridge and NVE functions. The embodiment of the invention expands the application range of the EVB and improves the implementation efficiency of the VN.
  • FIG. 1 is a schematic structural diagram of an EVB according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a virtual network provided according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a typical NVO3 application environment according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of an embodiment of a method for implementing a virtual network according to the present invention.
  • FIG. 5 is a schematic structural diagram of a network function according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of a format definition of a filtering information indicated by a command type according to a filtering information format according to an embodiment of the present invention
  • FIG. 7 is a schematic flowchart of an embodiment of processing the VDP packet according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of an implementation process of a virtual network according to the present invention.
  • FIG. 9 is a schematic flowchart of another embodiment of an implementation process of a virtual network according to the present invention.
  • FIG. 10 is a schematic diagram of functional modules of an implementation apparatus of a virtual network according to the present invention.
  • the EVB station receives the VDP message sent by the EV on the virtual network VN, and the VDP message includes the command type indication information, and the EVB station receives the VDP message according to the VDP message.
  • the command type indication information included in the message determines whether the VDP message is processed by the EVB station; if yes, the EVB station processes the VDP message and accesses the VM to the VN; if not, the The EVB station sends the VDP message to the EVB bridge. Row processing to enable the VM to access the VN in an EVB bridge.
  • the command type indication information indicates that the EVB station processes the VDP message, or the EVB bridge processes the VDP message,
  • the VM is connected to a virtual network. Effectively avoiding the current implementation of VDP-based VN, the implementation process is complicated, the operation is complicated, and the efficiency of VN implementation is poor.
  • the VDP message added to the VN with the command type indication information is an extension of the existing VDP message.
  • the EVB station supports EVB bridge and NVE functions. The embodiment of the invention expands the application range of the EVB and improves the implementation efficiency of the VN.
  • an embodiment of the present invention provides a method for implementing a virtual network.
  • FIG. 4 is a schematic flowchart diagram of an embodiment of a method for implementing a virtual network according to the present invention.
  • the implementation method of the virtual network includes:
  • step S10 the EVB station receives the VDP message that the ER in the EVB station sends to the virtual network VN, and the VDP message includes the command type indication information.
  • the embodiment of the invention is a method for implementing a virtual network based on VDP, and is applicable to a typical NVO3 application environment. However, it is not limited to the above application environment and the implementation of a VDP-based virtual network.
  • FIG. 5 it is a schematic diagram of a network function structure according to an embodiment of the present invention.
  • the VMM/EVB station and the EVB bridge all need to support the NVE function.
  • the NVA is a core control device that performs related functions such as user authentication and routing information exchange for VN deployment.
  • the VMM/Hypervisor prepares, generates the VM, and sets the initial parameters of the VM.
  • the generation of the VM triggers the start of the EVB station of the VNIC/VSI corresponding to the VM.
  • the EVB station After the EVB station starts running, it receives a VDP message that is added to the virtual network, and the VDP message includes command type indication information.
  • the VDP message added to the virtual network may be sent by the ER on behalf of the VM.
  • the virtual machine sends a packet: the packet encapsulation is optional using the virtual network ID, or is encapsulated by the L2 protocol. Installed, for example, including VLAN packaging, or Q-in-Q packaging.
  • the command type indication information is used to indicate processing information of the VDP message, and the indication information is used to indicate where the VDP command is processed, for example, may be processed in an EVB bridge or processed in an EVB station, that is,
  • the command type indication information carries a field indicating that the command is being processed at the EVB station or processed by the EVB bridge.
  • Step S20 the EVB station determines, according to the command type indication information included in the VDP message, whether to process the VDP message at the EVB station.
  • EVB EVB Hybrid or EVB station & bridge
  • the EVB station function (or, first of all, the EVB station), also needs to implement the EVB bridge function, and of course support the implementation of the NVE function.
  • the command indication bit is added.
  • the command type indication information is defined by a filtering information field of a VDP command message, or by a reserved VDP type value. 1.
  • the command indicator bit can be defined by the reserved value of the filter information format value in the existing command. For example, you can choose to reserve one of the values 0x00, 0x50through 0xFF. In the information format, you need to include the command indicator. 2.
  • a new command indication code can be defined using the reserved value: 0x66-0x7E. That is, the VDP information is processed by the EVB station or the EVB bridge by the code itself.
  • FIG. 6 is a schematic diagram of a format definition of a filtering information according to a command type indication of a filtering information format according to an embodiment of the present invention.
  • the indication bit (H bit in the figure, of course, may also be indicated by using an identifier different from H), is used to indicate whether it is a preferred VMM/Hypervisor for VDP message processing or an EVB bridge for VDP report.
  • the EVB station/mixed EVB is not processed, but is directly forwarded to the EVB bridge to process VDP packets through the EVB bridge.
  • VDP command extensions two types are involved, one is a join command, and the other is an instruction command.
  • one solution is that two different definitions can be defined in the filter information field.
  • the bits are used to indicate the addition of VN commands and command type indications. That is, the VDP message and the command type indication information are distinguished by defining different bits in the filter information field.
  • Step S30 if not, the EVB station sends the VDP packet to the EVB bridge for processing, to implement the VM accessing the VN in the EVB bridge;
  • Step S40 if yes, the EVB station processes the VDP message and accesses the VM to the VN.
  • the VDP message is processed by the front-end EVB station or the VDP message is processed by the back-end EVB bridge by determining whether the VDP message is processed by the EVB station.
  • the process of processing the VDP packet may be:
  • Step S31 the EVB station receives verification information of whether the VM passes the identity authentication of the VN.
  • Step S32 after the EVB station passes the verification of the VM, it is determined whether the context/VRF forwarding table of the VN exists.
  • Step S33 if the context/VRF forwarding table of the VN does not exist, the EVB station generates a VRF forwarding table of the VN;
  • Step S34 If the VRF entry corresponding to the VM does not exist in the VRF forwarding table, the EVB station generates a VRF forwarding table entry corresponding to the VM in the VRF forwarding table.
  • the EVB station During processing of the VDP message, the EVB station performs identity verification on the VM and obtains identity authentication result information of the VM. In the returned authentication result information, optional, including additional information, including but not limited to: virtual network ID (VN-ID), IP address information, establishing a virtual network context / VRF forwarding table (or collectively referred to as Virtual network instance VNI) information, etc.
  • VN-ID virtual network ID
  • IP address information establishing a virtual network context / VRF forwarding table (or collectively referred to as Virtual network instance VNI) information, etc.
  • VNI virtual network instance
  • the VRF forwarding table of the VN is generated; if the VRF is in the VRF If the VRF entry corresponding to the VM in the forwarding table does not exist, the EVB station generates a VRF forwarding table entry corresponding to the VM, and adds a VRF forwarding table entry corresponding to the VM to the VRF forwarding table. in.
  • the sending end takes the VM as an example. If the VM passes the identity authentication of the VN, and the VM is the first connected VM of the VN in the EVB station/NVE, the NVE creates a VN context/virtual network instance VNI, including VRF table. And for the VM, optional, assign the corresponding VLAN-ID The information, and the VLAN-ID and the corresponding physical interface information are used as the contents of the forwarding table entry, and the VN forwarding entry corresponding to the VM is formed in the VRF.
  • the corresponding VLAN-ID information is also assigned to the VM, and the VLAN-ID and the corresponding physical interface information are used as the contents of the entry.
  • a VN forwarding entry corresponding to the VM is formed in the VRF.
  • the processing may not be performed, or if the related parameter, for example, the assigned VLAN ID, is changed, the corresponding entry is modified accordingly.
  • VRF entries may include, but are not limited to, the IP/MAC address of the VM, the interface and/or sub-interface (eg, VLAN ID), and the virtual network number/identity (VN-ID).
  • VLAN ID the interface and/or sub-interface
  • VN-ID the virtual network number/identity
  • the NVE When the NVE generates a new VRF forwarding table, or the content in the VRF forwarding table changes, the NVE synchronizes the information of the virtual network through the NVE-NVA protocol.
  • the NVE can automatically synchronize the routing information of other NVEs of the virtual network through the protocol, that is, synchronize the local routing information or the newly updated routing information to all other NVEs in the virtual network through the NVA.
  • the release of different routing information is differentiated by the virtual network ID, so that routing updates between different virtual networks do not occur.
  • the NVE may also send a message to another NVE: the virtual network ID is generally encapsulated to distinguish different virtual networks, and the destination VNE sends a message to the virtual machine of the virtual network, which may also serve as a destination.
  • the NVE receives messages from other NVEs.
  • FIG. 8 and FIG. 9, are typical processing flows.
  • Step 700 Generate a VM and set initialization parameters.
  • Step 701 The generation of the VM triggers the EVB station corresponding to the VM to start running; here, the EVB station is an EVB station supporting a virtual network adapter (VNIC)/VSI corresponding to the VM and the VM.
  • VNIC virtual network adapter
  • Step 702 The VM sends an extended VDP command with the command indication information to the VN through the ER. If the indication information indicates the VDP command, and the local processing, the VDP command is processed.
  • Step 703 Perform identity authentication on the VM for accessing the VN.
  • Step 704 The NVA returns the result information of the identity authentication. If the certification is passed, feedback EVB bridge VN-ID, IP address (optionally, the IP address is a new IP address newly assigned to the VM, or an acknowledgment of the IP address of the VM), a VN context/VRF forwarding table generation command; if the authentication fails, The process ends.
  • Step 705 The EVB station generates a context/VRF forwarding table corresponding to the VN when the VN context/VRF forwarding table does not exist, and forms a corresponding VN forwarding entry for the VM.
  • the context in which the NVE automatically creates the VN includes the corresponding VRF table. This process can also be judged by the NVA, and the VN context/VRF forwarding table generation command is used to explicitly instruct the NVE to create the context/VRF forwarding table of the VN.
  • the forwarding table is not generated, and the forwarding entry corresponding to the VM is determined. If not, the corresponding forwarding entry is formed in the VRF table of the VN.
  • Step 707 The EVB station/NVE synchronizes the newly added forwarding table entry/forwarding table update information of the NVE to all other EVB bridges/NVEs in the NV via the network virtualization control device NVA.
  • the advertisement of the routing information of different VNs is distinguished by the VN-ID, so that the routing update between different VNs does not occur.
  • Step 708 The VM forwards the packet.
  • the IP packet encapsulation is performed by using the VN-ID; or the encapsulated IP packet is encapsulated by the pre-configured Layer 2 protocol L2.
  • Step 800 Generate a VM and set initialization parameters.
  • Step 801 The generation of the VM triggers the EVB station corresponding to the VM to start running; here, the EVB station is an EVB station supporting a virtual network adapter (VNIC)/VSI corresponding to the VM and the VM.
  • VNIC virtual network adapter
  • Step 802 The VM sends an extended VDP command with the command indication information to the VN through the ER. If the indication information indicates the VDP command and is not processed locally, the VDP command is forwarded to the EVB bridge.
  • Step 803 Perform identity authentication on the VM to access the VN.
  • Step 804 The NVA returns the result information of the identity authentication. If the authentication is passed, feedback the EVB bridge VN-ID, IP address (optional, the IP address is newly assigned to the VM's newly assigned IP address, or the confirmation of the VM's IP address), VN context/VRF forwarding table generation command If the authentication does not pass, the process ends.
  • Step 805 The EVB bridge generates a context/VRF forwarding table corresponding to the VN when the VN context/VRF forwarding table does not exist, and forms a corresponding VN forwarding entry for the VM.
  • the context in which the NVE automatically creates the VN includes the corresponding VRF table. This process can also be judged by the NVA, and the VN context/VRF forwarding table generation command is used to explicitly instruct the NVE to create the context/VRF forwarding table of the VN.
  • the forwarding table is not generated, and the forwarding entry corresponding to the VM is determined. If not, the corresponding forwarding entry is formed in the VRF table of the VN.
  • Step 806 The EVB bridge feedback processing acknowledgement information to the VM/ER/EVB station, including optional: VN-ID information, and IP address information.
  • Step 807 The EVB bridge/NVE synchronizes the newly added forwarding table entry/forwarding table update information of the NVE to all other EVB bridges/NVEs in the NV via the network virtualization control device NVA.
  • the advertisement of the routing information of different VNs is distinguished by the VN-ID, so that the routing update between different VNs does not occur.
  • Step 808 The VM forwards the packet. among them,
  • the IP packet encapsulation is performed by using the VN-ID; or the encapsulated IP packet is encapsulated by the pre-configured Layer 2 protocol L2.
  • the adaptability of the VDP in the typical application scenario of the VMM/NVE and the EVB bridge/NVE can be achieved, and the virtual network function based on the VDP can be successfully implemented.
  • the command type indication information is added to the VDP packet of the virtual machine VM that is added to the virtual network VN, and the command type indication information indicates that the EVB station processes the VDP message, or the EVB bridge processes the VDP message.
  • the command type indication information indicates that the EVB station processes the VDP message, or the EVB bridge processes the VDP message.
  • the VDP message added to the VN with the command type indication information is an extension of the existing VDP message.
  • the EVB station supports EVB bridge and NVE functions. The embodiment of the invention expands the application range of the EVB and improves the implementation efficiency of the VN.
  • the execution entities of the implementation method of the virtual network in the foregoing embodiment may all be terminals.
  • the implementation method of the virtual network may be implemented by an implementation program of a virtual network installed on the terminal (for example, implementation software of a virtual network, or an EVB station, etc.), wherein the terminal includes but is not limited to a mobile phone, a pad, a notebook computer, or the like.
  • Embodiments of the present invention provide an apparatus for implementing a virtual network.
  • FIG. 10 is a schematic diagram of functional modules of an embodiment of an apparatus according to an embodiment of the present invention.
  • the implementation device of the virtual network includes: a receiving module 10, a determining module 20, a sending module 30, and a processing module 40.
  • the implementation device is an EVB station that supports both EVB bridge and NVE functions.
  • the receiving module 10 is configured to: receive, by the ER in the EVB station, a VDP message that is sent by the VM and join the virtual network VN, where the VDP message includes command type indication information;
  • FIG. 5 it is a schematic diagram of a network function structure according to an embodiment of the present invention.
  • the VMM/EVB station and the EVB bridge all need to support the NVE function.
  • the NVA is a core control device that performs related functions such as user authentication and routing information exchange for VN deployment.
  • the VMM/Hypervisor prepares, generates the VM, and sets the initial parameters of the VM.
  • the generation of the VM triggers the start of the EVB station of the VNIC/VSI corresponding to the VM.
  • the EVB station After the EVB station starts running, it receives a VDP message that is added to the virtual network, and the VDP message includes command type indication information.
  • the VDP message added to the virtual network may be sent by the ER on behalf of the VM.
  • the virtual machine sends a packet: the packet encapsulation is optional using the virtual network ID, or is encapsulated by the L2 protocol. Installed, for example, including VLAN packaging, or Q-in-Q packaging.
  • the command type indication information is used to indicate processing information of the VDP message, and the indication information is used to indicate where the VDP command is processed, for example, may be processed in an EVB bridge or processed in an EVB station, that is,
  • the command type indication information carries a field indicating that the command is being processed at the EVB station or processed by the EVB bridge.
  • the determining module 20 is configured to: determine, according to the command type indication information included in the VDP message, whether the VDP message is processed by the EVB station;
  • EVB EVB Hybrid or EVB station & bridge
  • the EVB station function (or, first of all, the EVB station), also needs to implement the EVB bridge function, and of course support the implementation of the NVE function.
  • the command indication bit is added.
  • the command type indication information is defined by a filtering information field of a VDP command message, or by a reserved VDP type value. 1.
  • the command indicator bit can be defined by the reserved value of the filter information format value in the existing command. For example, you can choose to reserve one of the values 0x00, 0x50through 0xFF. In the information format, you need to include the command indicator. 2.
  • a new command indication code can be defined using the reserved value: 0x66-0x7E. That is, the VDP information is processed by the EVB station or the EVB bridge by the code itself.
  • FIG. 6 is a schematic diagram of a format definition of a filtering information according to a command type indication of a filtering information format according to an embodiment of the present invention.
  • the indication bit (H bit in the figure, of course, may also be indicated by using an identifier different from H), is used to indicate whether it is a preferred VMM/Hypervisor for VDP message processing or an EVB bridge for VDP report.
  • the EVB station/mixed EVB is not processed, but is directly forwarded to the EVB bridge to process VDP packets through the EVB bridge.
  • VDP command extensions two types are involved, one is a join command, and the other is an instruction command.
  • one solution is that two different definitions can be defined in the filter information field.
  • the bits are used to indicate the addition of VN commands and command type indications. That is, the VDP message and the command type indication information are distinguished by defining different bits in the filter information field.
  • the sending module 30 is configured to: if the VDP packet is not processed by the EVB station, send the VDP packet to an EVB bridge for processing, to implement the VM accessing the VN in an EVB bridge. ;
  • the processing module 40 processes the VDP message and accesses the VM to the VN if the VDP message is processed by the EVB station.
  • the VDP message is processed by the front-end EVB station or the VDP message is processed by the back-end EVB bridge by determining whether the VDP message is processed by the EVB station.
  • the processing module 40 is further configured to: implement VN identity authentication for the VM; after the VM passes the identity authentication of the VN, generate the VN if the context/VRF forwarding table of the VN does not exist Context/VRF forwarding table entry; if the VM does not have a corresponding entry in the VRF forwarding table, generate a corresponding VRF forwarding table entry of the VM in the VRF forwarding table.
  • the EVB During processing of the VDP message, the EVB needs to perform identity verification on the VM and obtain identity authentication result information of the VM. In the returned authentication result information, optional, including additional information, including but not limited to: virtual network ID (VN-ID), IP address information, establishing a virtual network context / VRF forwarding table (or collectively referred to as Virtual network instance VNI) information, etc.
  • VN-ID virtual network ID
  • IP address information IP address information
  • establishing a virtual network context / VRF forwarding table or collectively referred to as Virtual network instance VNI
  • the VRF forwarding table of the VN is generated; if the VRF is in the VRF If the VRF entry corresponding to the VM in the forwarding table does not exist, the EVB station generates a VRF forwarding table entry corresponding to the VM, and adds a VRF forwarding table entry corresponding to the VM to the VRF forwarding table. in.
  • the sending end takes the VM as an example. If the VM passes the identity authentication of the VN, and the VM is the first connected VM of the VN in the EVB station/NVE, the NVE creates a VN context/virtual network instance VNI, including VRF table. And for the VM, optionally, the corresponding VLAN-ID information is allocated, and the VLAN-ID and the corresponding physical interface information are used as the content of the forwarding table entry, and the VN forwarding entry corresponding to the VM is formed in the VRF.
  • the corresponding VLAN-ID information is also assigned to the VM, and the VLAN-ID and the corresponding physical interface information are used as the contents of the entry.
  • a VN forwarding entry corresponding to the VM is formed in the VRF.
  • the forwarding table entry corresponding to the VM is If it exists, it can be left unprocessed, or if the relevant parameters, such as the assigned VLAN-ID, change, the corresponding entries are modified accordingly.
  • VRF entries may include, but are not limited to, the IP/MAC address of the VM, the interface and/or sub-interface (eg, VLAN ID), and the virtual network number/identity (VN-ID).
  • VLAN ID the interface and/or sub-interface
  • VN-ID the virtual network number/identity
  • the NVE When the NVE generates a new VRF forwarding table, or the content in the VRF forwarding table changes, the NVE synchronizes the information of the virtual network through the NVE-NVA protocol.
  • the NVE can automatically synchronize the routing information of other NVEs of the virtual network through the protocol, that is, synchronize the local routing information or the newly updated routing information to all other NVEs in the virtual network through the NVA.
  • the release of different routing information is differentiated by the virtual network ID, so that routing updates between different virtual networks do not occur.
  • the NVE may also send a message to another NVE: the virtual network ID is generally encapsulated to distinguish different virtual networks, and the destination VNE sends a message to the virtual machine of the virtual network, which may also serve as a destination.
  • the NVE receives messages from other NVEs.
  • the first process flow generating a VM and setting initialization parameters; generating VMs, triggering the EVB station corresponding to the VM to start running; here, the EVB station is an EVB station supporting a virtual network adapter (VNIC)/VSI corresponding to the VM and the VM.
  • VNIC virtual network adapter
  • the VM sends an extended VDP command with the command indication information to the VN through the ER; if the indication information indicates the VDP command, the VDP command is processed locally, the VDP command is processed; the VM is authenticated to access the VN; and the NVA returns the result of the identity authentication. .
  • the EVB station If the authentication is passed, feedback the EVB bridge VN-ID, IP address (optional, the IP address is newly assigned to the VM's newly assigned IP address, or the confirmation of the VM's IP address), VN context/VRF forwarding table generation command If the authentication does not pass, the process ends.
  • the EVB station When the VN context/VRF forwarding table does not exist, the EVB station generates a context/VRF forwarding table corresponding to the VN, and forms a corresponding VN forwarding entry for the VM.
  • the context in which the NVE automatically creates the VN includes the corresponding VRF table. This process can also be judged by the NVA, and the VN context/VRF forwarding table generation command is used to explicitly instruct the NVE to create the context/VRF forwarding table of the VN.
  • the forwarding table is not generated, and the forwarding entry corresponding to the VM is determined. If not, the corresponding forwarding entry is formed in the VRF table of the VN.
  • the EVB station/NVE synchronizes the newly added forwarding table entry/forwarding table update information of the NVE to all other EVB bridges/NVEs in the NV via the network virtualization control device NVA.
  • the advertisement of the routing information of different VNs is distinguished by the VN-ID, so that the routing update between different VNs does not occur.
  • the VM forwards the packet. among them,
  • the IP packet encapsulation is performed by using the VN-ID; or the encapsulated IP packet is encapsulated by the pre-configured Layer 2 protocol L2.
  • the VM is generated and the initialization parameters are set; the generation of the VM triggers the EVB station corresponding to the VM to start running; here, the EVB station is an EVB station supporting the virtual network adapter (VNIC)/VSI corresponding to the VM and the VM.
  • the VM sends an extended VDP command to the VN with the command indication information through the ER; if the indication information indicates the VDP command, and is not processed locally, the VDP command is forwarded to the EVB bridge; the VM is authenticated to access the VN; and the NVA returns the identity authentication. Result information.
  • the EVB bridge If the authentication is passed, feedback the EVB bridge VN-ID, IP address (optional, the IP address is newly assigned to the VM's newly assigned IP address, or the confirmation of the VM's IP address), VN context/VRF forwarding table generation command If the authentication does not pass, the process ends.
  • the EVB bridge generates a context/VRF forwarding table corresponding to the VN when the VN context/VRF forwarding table does not exist, and forms a corresponding VN forwarding entry for the VM.
  • the context in which the NVE automatically creates the VN includes the corresponding VRF table. This process can also be judged by the NVA, and the VN context/VRF forwarding table generation command is used to explicitly instruct the NVE to create the context/VRF forwarding table of the VN.
  • the forwarding table is not generated, and the corresponding rotation of the VM is determined. If the publication item exists, if it does not exist, a corresponding forwarding entry is formed in the VRF table of the VN.
  • the EVB bridge feedback processing confirmation message to the VM/ER/EVB station including optional: VN-ID information, and IP address information.
  • the EVB Bridge/NVE synchronizes the newly added forwarding table entry/forwarding table update information of the NVE to all other EVB Bridges/NVEs in the NV via the Network Virtualization Control Device NVA.
  • the advertisement of the routing information of different VNs is distinguished by the VN-ID, so that the routing update between different VNs does not occur.
  • the VM forwards the packet. among them,
  • the IP packet encapsulation is performed by using the VN-ID; or the encapsulated IP packet is encapsulated by the pre-configured Layer 2 protocol L2.
  • the adaptability of the VDP in the typical application scenario of the VMM/NVE and the EVB bridge/NVE can be achieved, and the virtual network function based on the VDP can be successfully implemented.
  • the command type indication information is added to the VDP packet of the virtual machine VM that is added to the virtual network VN, and the command type indication information indicates that the EVB station processes the VDP message, or the EVB bridge processes the VDP message.
  • the command type indication information indicates that the EVB station processes the VDP message, or the EVB bridge processes the VDP message.
  • An embodiment of the present invention further provides a virtual network implementation system, including the virtual network implementation device and the EVB bridge as described above, where:
  • the virtual network implementation device is configured to: receive, by the ER in the EVB station, a VDP message that is sent by the VM and join the virtual network VN, where the VDP message includes command type indication information; according to the VDP message
  • the command type indication information includes: determining whether the VDP message is processed by the virtual network implementation device; if the VDP message is processed by the virtual network implementation device, accessing the VN to the VN;
  • the virtual network implements device processing Sending, by the VDP packet, the VDP packet to an EVB bridge for processing;
  • the EVB bridge is configured to: process the VDP packet, and implement the VM accessing the VN;
  • the virtual network implementation device is further configured to: implement VN identity authentication for the VM; after the VM passes the identity authentication of the VN, generate a context of the VN if the context of the VN does not exist If the VM does not have a corresponding entry in the VRF forwarding table, the corresponding entry of the VM is generated in the VRF forwarding table.
  • the command type indication information is defined by a filtering information field of the VDP command message; or, by a reserved VDP type value; the virtual network implementation device is an EVB station, and supports the EVB bridge and the NVE function.
  • the command type indication information is added to the VDP packet of the virtual machine VM that is added to the virtual network VN, and the command type indication information indicates that the EVB station processes the VDP message, or the EVB bridge processes the VDP message.
  • the VDP message added to the VN with the command type indication information is an extension of the existing VDP message.
  • the embodiment of the invention expands the application range of the EVB and improves the implementation efficiency of the VN. The scope of application of the EVB is extended, and the complexity of the implementation process of the VDP-based VN is reduced, thereby improving the efficiency of the VN implementation.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the device/function module/functional unit in the above embodiment can be implemented by using a general-purpose computing device. Now, they can be concentrated on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the embodiment of the present invention adds command type indication information to the VDP message of the virtual machine VM to join the virtual network VN, and the command type indication information indicates that the EVB station processes the VDP message, or the EVB bridge processes the VDP. A message to access the VM to the virtual network. Effectively avoiding the current implementation of VDP-based VN, the implementation process is complicated, the operation is complicated, and the efficiency of VN implementation is poor. The embodiment of the invention expands the application range of the EVB and improves the implementation efficiency of the VN.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本文公布一种虚拟网络的实现方法、装置及系统，所述方法包括：EVB站接收所述EVB站中的ER代表VM发出的加入虚拟网络VN的VDP报文，所述VDP报文包括命令类型指示信息；所述EVB站根据所述VDP报文中包括的命令类型指示信息判断是否在所述EVB站处理所述VDP报文；若是，则所述EVB站处理所述VDP报文并将所述VM接入所述VN；若否，则所述EVB站将所述VDP报文发送至EVB桥进行处理，以在EVB桥中实现所述VM接入所述VN。

Description

虚拟网络的实现方法、装置及系统 技术领域
本申请涉及但不限于数据中心技术领域。
背景技术
数据中心是全球协作的特定设备网络，用来在internet网络基础设施上传递、加速、展示、计算、存储数据信息。在数据中心中，如何通过虚拟化技术，例如，虚拟机提供VN(Virtual Network，虚拟网络)是一个热门的话题。虚拟网络涉及到网络的虚拟化等众多方面，引起设备供应商和运营商的多方关注，例如，IEEE推出802.1Qbg(边缘虚拟桥)，支持VM(Virtual Machine，虚拟机){(IEEE术语为虚拟站，需要区分提供虚拟站的平台，称为EVB(Edge Virtual Bridging，边缘虚拟桥)站，通过EVB站将VSI(Virtual Station Interface，虚拟机接口)连接到虚拟化平台外的交换机(EVB桥)}。图1，是EVB的体系结构示意图。通过VDP(VSI discovery and configuration protocol，虚拟机接口发现和配置协议)，CDCP和ECP等一系列协议，实现VSI到EVB桥的连接。另外，在IETF中也专门成立了一个工作组NVO3(Network Virtualization Overlay Based-on L3Network，基于层3的网络虚拟化)对虚拟网络进行研究。经过讨论，对如何实现VN的提供，有了一致的认识，即NVO3确定了虚拟网络提供的架构，如图2所示。
图2中，有一个集中的NVA(Network Virtualization Authority，网络虚拟化控制设备)，实现对业务提供的控制，VN中的多个VM连接到NVE(Network Virtualization Edge，网络虚拟化边缘设备)，并与NVE中的所述VN的VRF(Virtual Routing and Forwarding，虚拟路由转发功能)进行关联，多个不同NVE中同一VN的不同VRF，通过NVE直接的重叠网络隧道实现连接，从而实现VN。当然，VN可以通过NVE和互联网实现连接。
在实现过程中，特别是对VM如何接入NVE这一段的控制协议，一种观点认为，可以通过IEEE的VDP来承担，直观的，VDP是实现VM到EVB桥的关联工作，这和VM加入NVE的VN非常相似，因为VDP是一种L2 的协议，为了实现NVO3的虚拟网络，需要进行L3地址信息的支持，以及需要支持VN-ID信息的传递等。但是，仅仅有这些扩展，还是不够的，由于EVB本身应用场景和NVO3不完全相同，EVB具有其特有的状态机处理机制，在应用中，还会遇到问题。例如，在典型的NVO3应用环境中，如图3所示，TOR(Top of Rack，架顶交换机)和VMM(virtual machine monitor，服务器)都可以作为NVE使用，同时相互连接。为了满足那些对网络处理要求较高的用户，将他们接到架顶交换机的NVE中；对普通的用户而言，可以直接使用VMM/NVE进行处理。在这种情况下EVB会遇到困难，即如果将VDP的关联信息按照EVB体制都发送给EVB桥，即架顶交换机处理，则需要将处理后的信息关联到EVB站。这里在实现上，也比较困难；或者，可以将EVB桥的功能配置在EVB站中，可以实现。但是，对需要接入EVB桥用户的VDP请求，则不能直接到达架顶交换机的EVB桥。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本文提供一种虚拟网络的实现方法、装置及系统，旨在解决相关VDP技术不支持EVB站/NVE-EVB桥/NVE的NVO3典型应用环境的问题。
一种虚拟网络的实现方法，包括：
EVB站接收所述EVB站中的ER(边缘中继，Edge Relay)代表VM发出的加入虚拟网络VN的VDP报文，所述VDP报文包括命令类型指示信息；
所述EVB站根据所述VDP报文中包括的命令类型指示信息判断是否在所述EVB站处理所述VDP报文；
若是，则所述EVB站处理所述VDP报文并将所述VM接入所述VN；
若否，则所述EVB站将所述VDP报文发送至EVB桥进行处理，以在EVB桥中实现所述VM接入所述VN。
可选地，所述命令类型指示信息，通过VDP命令报文的过滤信息字段进行定义；或者，通过保留的VDP类型值进行定义。
可选地，所述EVB站，支持EVB桥和NVE。
可选地，所述EVB站或EVB桥将所述VM接入所述VN的步骤包括：
接收所述VM是否通过所述VN的身份认证的验证信息；
在所述VM验证通过后，判断所述VN的上下文是否存在；
若不存在，则生成所述VN的上下文；所述VN的上下文包括虚拟路由转发功能VRF转发表；
若在所述VRF转发表中所述VM对应的VRF表项不存在，则在所述VRF转发表中生成所述VM对应的VRF转发表表项。
一种虚拟网络的实现装置，包括：
接收模块，设置为：接收所述EVB站中的ER代表VM发出的加入虚拟网络VN的VDP报文，所述VDP报文包括命令类型指示信息；
判断模块，设置为：根据所述VDP报文中包括的命令类型指示信息判断是否在所述EVB站处理所述VDP报文；
发送模块，设置为：若不在所述EVB站处理所述VDP报文，则将所述VDP报文发送至EVB桥进行处理，以在EVB桥中实现所述VM接入所述VN；
处理模块，设置为：若在所述EVB站处理所述VDP报文，则处理所述VDP报文并将所述VM接入所述VN；以及，实现对所述VM的VN身份认证；在所述VM通过所述VN的身份认证后，若所述VN的上下文不存在则生成所述VN的上下文；若所述VM在所述VRF转发表中没有对应的表项，则在所述VRF转发表中生成所述VM的对应VRF转发表表项。
可选地，所述命令类型指示信息，通过VDP命令报文的过滤信息字段进行定义；或者，通过保留的VDP类型值进行定义。
可选地，所述实现装置是EVB站，同时支持EVB桥和NVE功能。
一种虚拟网络的实现系统，包括如上所述的虚拟网络实现装置及EVB 桥，其中：
所述的虚拟网络实现装置，设置为：接收所述EVB站中的ER代表VM发出的加入虚拟网络VN的VDP报文，所述VDP报文包括命令类型指示信息；根据所述VDP报文中包括的命令类型指示信息判断是否在所述虚拟网络实现装置处理所述VDP报文；若是在所述虚拟网络实现装置处理所述VDP报文，则将所述VM接入所述VN；若不在所述虚拟网络实现装置处理所述VDP报文，则将所述VDP报文发送至EVB桥进行处理；
所述EVB桥，设置为：对所述VDP报文进行处理，实现所述VM接入所述VN；
所述的虚拟网络实现装置，还设置为：实现对所述VM的VN身份认证；在所述VM通过所述VN的身份认证后，若所述VN的上下文不存在则生成所述VN的上下文；若所述VM在所述VRF转发表中没有对应的表项，则在所述VRF转发表中生成所述VM的对应表项。
可选地，所述命令类型指示信息，通过VDP命令报文的过滤信息字段进行定义；或者，通过保留的VDP类型值进行定义；所述虚拟网络实现装置为EVB站，同时支持EVB桥和NVE功能。
一种虚拟网络的实现方法，包括：
边缘虚拟桥EVB站接收所述EVB站中的边缘中继ER代表虚拟机VM发出的加入虚拟网络VN的虚拟机接口发现和配置协议VDP报文；
所述EVB站处理所述VDP报文并将所述VM接入所述VN。
一种虚拟网络的实现方法，包括：
边缘虚拟桥EVB站接收所述EVB站中的边缘中继ER代表虚拟机VM发出的加入虚拟网络VN的虚拟机接口发现和配置协议VDP报文；
所述EVB站将所述VDP报文发送至EVB桥进行处理，以在EVB桥中实现所述VM接入所述VN。一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项的方法。
本发明实施例通过在接收到的虚拟机VM加入虚拟网络VN的VDP报文 中添加命令类型指示信息，通过命令类型指示信息指示是EVB站处理所述VDP报文，或者EVB桥处理所述VDP报文，以将所述VM接入虚拟网络。有效避免目前在基于VDP的VN的实现过程中，实现过程复杂、操作繁杂，使得VN实现的效率差的问题。所述带命令类型指示信息的加入VN的VDP报文是对已有VDP报文的扩展。所述EVB站支持EVB桥和NVE功能。本发明实施例扩展了EVB的适用范围，并提高了VN的实现效率。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为本发明一实施例中EVB的体系结构示意图；
图2为本发明一实施例中虚拟网络提供的架构示意图；
图3为本发明一实施例中典型的NVO3应用环境的架构示意图；
图4为本发明虚拟网络的实现方法的实施例的流程示意图；
图5为本发明一实施例的网络功能结构示意图；
图6本发明一实施例中基于过滤信息格式的命令类型指示的过滤信息格式定义示意图；
图7为本发明实施例对所述VDP报文进行处理一实施例的流程示意图；
图8为本发明虚拟网络的实现过程一实施例的流程示意图；
图9为本发明虚拟网络的实现过程另一实施例的流程示意图；
图10为本发明虚拟网络的实现装置的实施例的功能模块示意图。
本发明的实施方式
本发明实施例中，EVB站接收所述EVB站中的ER代表VM发出的加入虚拟网络VN的VDP报文，所述VDP报文包括命令类型指示信息；所述EVB站根据所述VDP报文中包括的命令类型指示信息判断是否在所述EVB站处理所述VDP报文；若是，则所述EVB站处理所述VDP报文并将所述VM接入所述VN；若否，则所述EVB站将所述VDP报文发送至EVB桥进 行处理，以在EVB桥中实现所述VM接入所述VN。通过在接收到的虚拟机VM加入虚拟网络VN的VDP报文中添加命令类型指示信息，通过命令类型指示信息指示是EVB站处理所述VDP报文，或者EVB桥处理所述VDP报文，以将所述VM接入虚拟网络。有效避免目前在基于VDP的VN的实现过程中，实现过程复杂、操作繁杂，使得VN实现的效率差的问题。所述带命令类型指示信息的加入VN的VDP报文是对已有VDP报文的扩展。所述EVB站支持EVB桥和NVE功能。本发明实施例扩展了EVB的适用范围，并提高了VN的实现效率。
由于目前在基于VDP的VN的实现过程中，实现过程复杂、操作繁杂，使得VN实现的效率差。
基于上述问题，本发明实施例提供一种虚拟网络的实现方法。
参照图4，图4为本发明虚拟网络的实现方法的实施例的流程示意图。
在一实施例中，所述虚拟网络的实现方法包括：
步骤S10，EVB站接收所述EVB站中的ER代表VM发出的加入虚拟网络VN的VDP报文，所述VDP报文包括命令类型指示信息；
本发明实施例为基于VDP的虚拟网络的实现方法，且适用于典型的NVO3应用环境中。但也不限于上述的应用环境和基于VDP的虚拟网络的实现。
参考图5，为本发明实施例的网络功能结构示意图。其中VMM/EVB站和EVB桥都需要支持NVE的功能。NVA是核心控制设备，完成VN部署的用户认证和路由信息交互等相关功能。
VMM/Hypervisor准备、生成VM，并设置VM的初始参数。
VM的生成，触发VM对应的VNIC/VSI的EVB站开始运行。在EVB站开始运行后，接收加入虚拟网络的VDP报文，所述VDP报文包括命令类型指示信息。所述加入虚拟网络的VDP报文可以由ER代表VM发出。虚拟机发送报文：报文封装可选的使用虚拟网络ID，或者通过L2协议进行封 装，例如，包括VLAN封装，或者Q-in-Q封装等。
所述命令类型指示信息用以指示所述VDP报文的处理信息，通过该指示信息，指示VDP命令在哪里进行处理，例如，可以在EVB桥进行处理，或在EVB站进行处理，即所述命令类型指示信息携带指示命令在在EVB站处理或EVB桥处理的字段。
步骤S20，所述EVB站根据所述VDP报文中包括的命令类型指示信息判断是否在所述EVB站处理所述VDP报文；
为在VMM/NVE-TOR/NVE环境下实现通过VDP支持的VN的实现，需要扩展EVB架构功能，即新增加一种EVB角色，混合EVB(EVB Hybrid或者EVB站&桥)，它既需要实现EVB站功能(或者，首先是EVB站)，也需要实现EVB桥功能，当然也要支持NVE功能的实现。
在VDP关联TLV定义中，增加命令指示位。所述命令类型指示信息，通过VDP命令报文的过滤信息字段进行定义；或者通过保留的VDP类型值进行定义。1、可以通过已有命令中的过滤信息格式值的保留值，来进行命令指示位的定义。例如，可以选择保留值0x00，0x50through 0xFF中的一种加以定义。而信息格式中，需要包括命令指示位。2、可选的，可以利用保留值：0x66-0x7E，定义新的命令指示代码。即，通过代码本身来区分时EVB站还是EVB桥来对VDP信息进行处理。
图6为本发明实施例的基于过滤信息格式的命令类型指示的过滤信息格式定义示意图。该指示位(如图中的H位，当然，也可以使用不同于H其他的标识来进行指示)，用于指示：是优选VMM/Hypervisor来进行VDP报文处理，还是EVB桥来进行VDP报文处理；在接收到EVB桥优先处理的VDP报文，则EVB站/混合EVB不进行处理，而是直接转发给EVB桥，通过EVB桥处理VDP报文。
本发明实施例中，涉及到2种VDP命令扩展，一个是加入命令，另外一个是指示命令，从简化和高效定义VDP命令角度看，一种方案是，可以通过过滤信息字段中定义2个不同的位，分别用于指示加入VN命令和命令类型指示。即，通过过滤信息字段中定义不同的位来区分VDP报文和命令类型指示信息。
步骤S30，若否，则所述EVB站将所述VDP报文发送至EVB桥进行处理，以在EVB桥中实现所述VM接入所述VN；
步骤S40，若是，则所述EVB站处理所述VDP报文并将所述VM接入所述VN。
通过判断是否为所述EVB站处理所述VDP报文，实现在前端EVB站处理VDP报文，或者后端EVB桥处理VDP报文。
参考图7，以EVB站为例(EVB桥执行过程与EVB站相同)，所述对所述VDP报文进行处理的过程可以是：
步骤S31，所述EVB站接收所述VM是否通过所述VN的身份认证的验证信息；
步骤S32，所述EVB站在所述VM验证通过后，判断所述VN的上下文/VRF转发表是否存在；
步骤S33，若所述VN的上下文/VRF转发表不存在，则所述EVB站生成所述VN的VRF转发表；
步骤S34，若在所述VRF转发表中所述VM对应的VRF表项不存在，则所述EVB站在所述VRF转发表中生成所述VM对应的VRF转发表表项。
所述EVB站在处理所述VDP报文过程中，对所述VM进行身份验证，并获得所述VM的身份认证结果信息。在返回的认证结果信息中，可选的，包括附加信息，所述附加信息包括但不限于：虚拟网络ID(VN-ID)，IP地址信息，建立虚拟网络上下文/VRF转发表(或者统称为虚拟网络实例VNI)信息等。在认证通过后，所述EVB站判断所述VN的上下文/VRF转发表是否存在，若所述VN的上下文/VRF转发表不存在，则生成所述VN的VRF转发表；若在所述VRF转发表中所述VM对应的VRF表项不存在，则所述EVB站生成所述VM对应的VRF转发表表项，并将所述VM对应的VRF转发表表项增加到所述VRF转发表中。
所述发送端以VM为例，如果VM通过了VN的身份认证，且VM是所述VN在EVB站/NVE中的第一个连接VM，则NVE创建VN的上下文/虚拟网络实例VNI，包括VRF表。并针对VM，可选的，分配对应的VLAN-ID 信息，并将该VLAN-ID和对应的物理接口信息，作为转发表表项的内容，在VRF中形成VM对应的VN转发表项。如果VN的上下文已经存在但是VM的对应表项不存在，同样针对VM，可选的，分配对应的VLAN-ID信息，并将该VLAN-ID和对应的物理接口信息，作为表项的内容，在VRF中形成VM对应的VN转发表项。可选的，如果所述VM对应的转发表表项已经存在，则可以不做处理，或者如果有关的参数，例如分配的VLAN-ID有变化，则对对应的表项做相应的修改。
VRF表项可包括但不限于：VM的IP/MAC地址，接口和/或子接口(例如VLAN ID)，虚拟网络号/标识(VN-ID)。
在NVE生成新的VRF转发表，或者VRF转发表中的内容发生变化时，NVE通过NVE-NVA协议进行虚拟网络的信息同步。NVE可以通过协议自动地同步虚拟网络的其他NVE的路由信息，即，将本地的路由信息，或者是新更新的路由信息通过NVA同步到虚拟网络中的其他所有NVE中。而不同的路由信息的发布，通过虚拟网络ID来进行区分，从而不至于发生不同虚拟网络之间的路由更新发生错误。
在本发明其他实施例中也还可以是NVE发送报文到其他NVE：一般通过虚拟网络ID进行封装区分不同的虚拟网络，目的VNE发送报文给所述虚拟网络的虚拟机，也可以作为目的端NVE从其他NVE接收报文。
为了进一步说明本发明实施例技术方案，参考图8和图9，图8和图9是典型的处理流程。
第一个处理流程：
步骤700、生成VM并设置初始化参数；
步骤701、VM的生成，触发VM对应的EVB站开始运行；这里，EVB站为支持VM及VM所对应的虚拟网络适配器(VNIC)/VSI的EVB站。
步骤702、VM通过ER发送带命令指示信息的加入VN的扩展VDP命令；如果指示信息指示VDP命令，由本地处理，则处理该VDP命令；
步骤703、对VM进行接入VN的身份认证；
步骤704、NVA返回身份认证的结果信息。如果认证通过，反馈EVB桥 VN-ID、IP地址(可选的，该IP地址是新针对VM新分配的IP地址，或者是对VM的IP地址的确认)、VN上下文/VRF转发表生成命令；如果认证不通过，则处理过程结束。
步骤705、EVB站在VN上下文/VRF转发表不存在时，生成VN对应的上下文/VRF转发表；针对VM形成对应的VN转发表项。
这里，如果VM通过了VN的身份认证且VM是该VN在该NVE上的第一个连接VM，则NVE自动创建VN的上下文包括相应的VRF表。这个过程，也可以由NVA来实现判断，并通过VN上下文/VRF转发表生成命令来明确指示NVE进行该VN的上下文/VRF转发表的创建。
如果VRF转发表已经存在，则不用生成转发表，而判断VM所对应的转发表项是否存在，如果不存在，则在该VN的VRF表中形成对应的转发表项。
步骤707、EVB站/NVE经由网络虚拟化控制设备NVA实现将该NVE的新增加的转发表条目/转发表更新信息同步到该NV中的所有其他EVB桥/NVE中。
这里通过NVA同步到VN中的其他所有NVE中。而不同VN的路由信息的通告，通过VN-ID来进行区分，从而不至于发生不同VN之间的路由更新发生错误。
步骤708、VM进行报文转发。使用VN-ID进行IP报文封装；或，封装后的IP报文，通过预先设置的第二层协议L2进行报文的封装。
另外一个处理流程：
步骤800、生成VM并设置初始化参数；
步骤801、VM的生成，触发VM对应的EVB站开始运行；这里，EVB站为支持VM及VM所对应的虚拟网络适配器(VNIC)/VSI的EVB站。
步骤802、VM通过ER发送带命令指示信息的加入VN的扩展VDP命令；如果指示信息指示VDP命令，不由本地处理，则转发该VDP命令至EVB桥；
步骤803、对VM进行接入VN的身份认证；
步骤804、NVA返回身份认证的结果信息。如果认证通过，反馈EVB桥VN-ID、IP地址(可选的，该IP地址是新针对VM新分配的IP地址，或者是对VM的IP地址的确认)、VN上下文/VRF转发表生成命令；如果认证不通过，则处理过程结束。
步骤805、EVB桥在VN上下文/VRF转发表不存在时，生成VN对应的上下文/VRF转发表；针对VM形成对应的VN转发表项。
这里，如果VM通过了VN的身份认证且VM是该VN在该NVE上的第一个连接VM，则NVE自动创建VN的上下文包括相应的VRF表。这个过程，也可以由NVA来实现判断，并通过VN上下文/VRF转发表生成命令来明确指示NVE进行该VN的上下文/VRF转发表的创建。
如果VRF转发表已经存在，则不用生成转发表，而判断VM所对应的转发表项是否存在，如果不存在，则在该VN的VRF表中形成对应的转发表项。
步骤806、EVB桥反馈处理的确认信息至VM/ER/EVB站，包括可选的：VN-ID信息，及IP地址信息。
步骤807、EVB桥/NVE经由网络虚拟化控制设备NVA实现将该NVE的新增加的转发表条目/转发表更新信息同步到该NV中的所有其他EVB桥/NVE中。
这里通过NVA同步到VN中的其他所有NVE中。而不同VN的路由信息的通告，通过VN-ID来进行区分，从而不至于发生不同VN之间的路由更新发生错误。
步骤808、VM进行报文转发。其中，
使用VN-ID进行IP报文封装；或，封装后的IP报文，通过预先设置的第二层协议L2进行报文的封装。
通过本发明实施例的方案，可以实现VMM/NVE和EVB桥/NVE的典型应用场景下的VDP的适应性，保证了基于VDP的虚拟网络功能得以顺利实现。
本实施例通过在接收到的虚拟机VM加入虚拟网络VN的VDP报文中添加命令类型指示信息，通过命令类型指示信息指示是EVB站处理所述VDP报文，或者EVB桥处理所述VDP报文，以将所述VM接入虚拟网络。有效避免目前在基于VDP的VN的实现过程中，实现过程复杂、操作繁杂，使得VN实现的效率差的问题。所述带命令类型指示信息的加入VN的VDP报文是对已有VDP报文的扩展。所述EVB站支持EVB桥和NVE功能。本发明实施例扩展了EVB的适用范围，并提高了VN的实现效率。
上述实施例虚拟网络的实现方法的执行主体均可以为终端。该虚拟网络的实现方法可以由安装在终端上的虚拟网络的实现程序(例如，虚拟网络的实现软件，或EVB站等)实现，其中，该终端包括但不限于手机、pad、笔记本电脑等。
本发明实施例提供一种虚拟网络的实现装置。
参照图10，图10为本发明实施例装置的实施例的功能模块示意图。
在一实施例中，所述虚拟网络的实现装置包括：接收模块10、判断模块20、发送模块30和处理模块40。
所述实现装置是EVB站，同时支持EVB桥和NVE功能。
所述接收模块10，设置为：接收所述EVB站中的ER代表VM发出的加入虚拟网络VN的VDP报文，所述VDP报文包括命令类型指示信息；
参考图5，为本发明实施例的网络功能结构示意图。其中VMM/EVB站和EVB桥都需要支持NVE的功能。NVA是核心控制设备，完成VN部署的用户认证和路由信息交互等相关功能。
VMM/Hypervisor准备、生成VM，并设置VM的初始参数。
VM的生成，触发VM对应的VNIC/VSI的EVB站开始运行。在EVB站开始运行后，接收加入虚拟网络的VDP报文，所述VDP报文包括命令类型指示信息。所述加入虚拟网络的VDP报文可以由ER代表VM发出。虚拟机发送报文：报文封装可选的使用虚拟网络ID，或者通过L2协议进行封 装，例如，包括VLAN封装，或者Q-in-Q封装等。
所述命令类型指示信息用以指示所述VDP报文的处理信息，通过该指示信息，指示VDP命令在哪里进行处理，例如，可以在EVB桥进行处理，或在EVB站进行处理，即所述命令类型指示信息携带指示命令在在EVB站处理或EVB桥处理的字段。
所述判断模块20，设置为：根据所述VDP报文中包括的命令类型指示信息判断是否在所述EVB站处理所述VDP报文；
为在VMM/NVE-TOR/NVE环境下实现通过VDP支持的VN的实现，需要扩展EVB架构功能，即新增加一种EVB角色，混合EVB(EVB Hybrid或者EVB站&桥)，它既需要实现EVB站功能(或者，首先是EVB站)，也需要实现EVB桥功能，当然也要支持NVE功能的实现。
在VDP关联TLV定义中，增加命令指示位。所述命令类型指示信息，通过VDP命令报文的过滤信息字段进行定义；或者通过保留的VDP类型值进行定义。1、可以通过已有命令中的过滤信息格式值的保留值，来进行命令指示位的定义。例如，可以选择保留值0x00，0x50through 0xFF中的一种加以定义。而信息格式中，需要包括命令指示位。2、可选的，可以利用保留值：0x66-0x7E，定义新的命令指示代码。即，通过代码本身来区分时EVB站还是EVB桥来对VDP信息进行处理。
图6为本发明实施例的基于过滤信息格式的命令类型指示的过滤信息格式定义示意图。该指示位(如图中的H位，当然，也可以使用不同于H其他的标识来进行指示)，用于指示：是优选VMM/Hypervisor来进行VDP报文处理，还是EVB桥来进行VDP报文处理；在接收到EVB桥优先处理的VDP报文，则EVB站/混合EVB不进行处理，而是直接转发给EVB桥，通过EVB桥处理VDP报文。
本发明实施例中，涉及到2种VDP命令扩展，一个是加入命令，另外一个是指示命令，从简化和高效定义VDP命令角度看，一种方案是，可以通过过滤信息字段中定义2个不同的位，分别用于指示加入VN命令和命令类型指示。即，通过过滤信息字段中定义不同的位来区分VDP报文和命令类型指示信息。
所述发送模块30，设置为：若不在所述EVB站处理所述VDP报文，则将所述VDP报文发送至EVB桥进行处理，以在EVB桥中实现所述VM接入所述VN；
所述处理模块40，若在所述EVB站处理所述VDP报文，则处理所述VDP报文并将所述VM接入所述VN。
通过判断是否为所述EVB站处理所述VDP报文，实现在前端EVB站处理VDP报文，或者后端EVB桥处理VDP报文。
所述处理模块40，还设置为：实现对所述VM的VN身份认证；在所述VM通过所述VN的身份认证后，若所述VN的上下文/VRF转发表不存在则生成所述VN的上下文/VRF转发表；若所述VM在所述VRF转发表中没有对应的表项，则在所述VRF转发表中生成所述VM的对应VRF转发表表项。
所述EVB站在处理所述VDP报文过程中，需要对所述VM进行身份验证，并获得所述VM的身份认证结果信息。在返回的认证结果信息中，可选的，包括附加信息，所述附加信息包括但不限于：虚拟网络ID(VN-ID)，IP地址信息，建立虚拟网络上下文/VRF转发表(或者统称为虚拟网络实例VNI)信息等。在认证通过后，所述EVB站判断所述VN的上下文/VRF转发表是否存在，若所述VN的上下文/VRF转发表不存在，则生成所述VN的VRF转发表；若在所述VRF转发表中所述VM对应的VRF表项不存在，则所述EVB站生成所述VM对应的VRF转发表表项，并将所述VM对应的VRF转发表表项增加到所述VRF转发表中。
所述发送端以VM为例，如果VM通过了VN的身份认证，且VM是所述VN在EVB站/NVE中的第一个连接VM，则NVE创建VN的上下文/虚拟网络实例VNI，包括VRF表。并针对VM，可选的，分配对应的VLAN-ID信息，并将该VLAN-ID和对应的物理接口信息，作为转发表表项的内容，在VRF中形成VM对应的VN转发表项。如果VN的上下文已经存在但是VM的对应表项不存在，同样针对VM，可选的，分配对应的VLAN-ID信息，并将该VLAN-ID和对应的物理接口信息，作为表项的内容，在VRF中形成VM对应的VN转发表项。可选的，如果所述VM对应的转发表表项已 经存在，则可以不做处理，或者如果有关的参数，例如分配的VLAN-ID有变化，则对对应的表项做相应的修改。
VRF表项可包括但不限于：VM的IP/MAC地址，接口和/或子接口(例如VLAN ID)，虚拟网络号/标识(VN-ID)。
在NVE生成新的VRF转发表，或者VRF转发表中的内容发生变化时，NVE通过NVE-NVA协议进行虚拟网络的信息同步。NVE可以通过协议自动地同步虚拟网络的其他NVE的路由信息，即，将本地的路由信息，或者是新更新的路由信息通过NVA同步到虚拟网络中的其他所有NVE中。而不同的路由信息的发布，通过虚拟网络ID来进行区分，从而不至于发生不同虚拟网络之间的路由更新发生错误。
在本发明其他实施例中也还可以是NVE发送报文到其他NVE：一般通过虚拟网络ID进行封装区分不同的虚拟网络，目的VNE发送报文给所述虚拟网络的虚拟机，也可以作为目的端NVE从其他NVE接收报文。
本发明实施例方案的处理流程可包括：
第一个处理流程：生成VM并设置初始化参数；VM的生成，触发VM对应的EVB站开始运行；这里，EVB站为支持VM及VM所对应的虚拟网络适配器(VNIC)/VSI的EVB站。VM通过ER发送带命令指示信息的加入VN的扩展VDP命令；如果指示信息指示VDP命令，由本地处理，则处理该VDP命令；对VM进行接入VN的身份认证；NVA返回身份认证的结果信息。如果认证通过，反馈EVB桥VN-ID、IP地址(可选的，该IP地址是新针对VM新分配的IP地址，或者是对VM的IP地址的确认)、VN上下文/VRF转发表生成命令；如果认证不通过，则处理过程结束。EVB站在VN上下文/VRF转发表不存在时，生成VN对应的上下文/VRF转发表；针对VM形成对应的VN转发表项。
这里，如果VM通过了VN的身份认证且VM是该VN在该NVE上的第一个连接VM，则NVE自动创建VN的上下文包括相应的VRF表。这个过程，也可以由NVA来实现判断，并通过VN上下文/VRF转发表生成命令来明确指示NVE进行该VN的上下文/VRF转发表的创建。
如果VRF转发表已经存在，则不用生成转发表，而判断VM所对应的转发表项是否存在，如果不存在，则在该VN的VRF表中形成对应的转发表项。
EVB站/NVE经由网络虚拟化控制设备NVA实现将该NVE的新增加的转发表条目/转发表更新信息同步到该NV中的所有其他EVB桥/NVE中。
这里通过NVA同步到VN中的其他所有NVE中。而不同VN的路由信息的通告，通过VN-ID来进行区分，从而不至于发生不同VN之间的路由更新发生错误。
VM进行报文转发。其中，
使用VN-ID进行IP报文封装；或，封装后的IP报文，通过预先设置的第二层协议L2进行报文的封装。
另外一个处理流程：
生成VM并设置初始化参数；VM的生成，触发VM对应的EVB站开始运行；这里，EVB站为支持VM及VM所对应的虚拟网络适配器(VNIC)/VSI的EVB站。VM通过ER发送带命令指示信息的加入VN的扩展VDP命令；如果指示信息指示VDP命令，不由本地处理，则转发该VDP命令至EVB桥；对VM进行接入VN的身份认证；NVA返回身份认证的结果信息。如果认证通过，反馈EVB桥VN-ID、IP地址(可选的，该IP地址是新针对VM新分配的IP地址，或者是对VM的IP地址的确认)、VN上下文/VRF转发表生成命令；如果认证不通过，则处理过程结束。EVB桥在VN上下文/VRF转发表不存在时，生成VN对应的上下文/VRF转发表；针对VM形成对应的VN转发表项。
这里，如果VM通过了VN的身份认证且VM是该VN在该NVE上的第一个连接VM，则NVE自动创建VN的上下文包括相应的VRF表。这个过程，也可以由NVA来实现判断，并通过VN上下文/VRF转发表生成命令来明确指示NVE进行该VN的上下文/VRF转发表的创建。
如果VRF转发表已经存在，则不用生成转发表，而判断VM所对应的转 发表项是否存在，如果不存在，则在该VN的VRF表中形成对应的转发表项。
EVB桥反馈处理的确认信息至VM/ER/EVB站，包括可选的：VN-ID信息，及IP地址信息。EVB桥/NVE经由网络虚拟化控制设备NVA实现将该NVE的新增加的转发表条目/转发表更新信息同步到该NV中的所有其他EVB桥/NVE中。
这里，通过NVA同步到VN中的其他所有NVE中。而不同VN的路由信息的通告，通过VN-ID来进行区分，从而不至于发生不同VN之间的路由更新发生错误。VM进行报文转发。其中，
使用VN-ID进行IP报文封装；或，封装后的IP报文，通过预先设置的第二层协议L2进行报文的封装。
通过本发明实施例的方案，可以实现VMM/NVE和EVB桥/NVE的典型应用场景下的VDP的适应性，保证了基于VDP的虚拟网络功能得以顺利实现。
本实施例通过在接收到的虚拟机VM加入虚拟网络VN的VDP报文中添加命令类型指示信息，通过命令类型指示信息指示是EVB站处理所述VDP报文，或者EVB桥处理所述VDP报文，以将所述VM接入虚拟网络。有效避免目前在基于VDP的VN的实现过程中遇到的问题。扩展了EVB的适用范围，降低基于VDP的VN的实现过程的复杂度，进而提高VN实现的效率。
对应上述虚拟网络的实现装置的实施例，本发明实施例还提出一种虚拟网络的实现系统，包括如上所述的虚拟网络实现装置及EVB桥，其中：
所述的虚拟网络实现装置，设置为：接收所述EVB站中的ER代表VM发出的加入虚拟网络VN的VDP报文，所述VDP报文包括命令类型指示信息；根据所述VDP报文中包括的命令类型指示信息判断是否在所述虚拟网络实现装置处理所述VDP报文；若是在所述虚拟网络实现装置处理所述VDP报文，则将所述VM接入所述VN；若不在所述虚拟网络实现装置处理 所述VDP报文，则将所述VDP报文发送至EVB桥进行处理；
所述EVB桥，设置为：对所述VDP报文进行处理，实现所述VM接入所述VN；
所述的虚拟网络实现装置，还设置为：实现对所述VM的VN身份认证；在所述VM通过所述VN的身份认证后，若所述VN的上下文不存在则生成所述VN的上下文；若所述VM在所述VRF转发表中没有对应的表项，则在所述VRF转发表中生成所述VM的对应表项。所述命令类型指示信息，通过VDP命令报文的过滤信息字段进行定义；或者，通过保留的VDP类型值进行定义；所述虚拟网络实现装置为EVB站，同时支持EVB桥和NVE功能。
所述虚拟网络的实现装置的功能和实现过程如上所述，在此不再一一赘述。
本实施例通过在接收到的虚拟机VM加入虚拟网络VN的VDP报文中添加命令类型指示信息，通过命令类型指示信息指示是EVB站处理所述VDP报文，或者EVB桥处理所述VDP报文，以将所述VM接入虚拟网络。有效避免目前在基于VDP的VN的实现过程中遇到的问题。所述带命令类型指示信息的加入VN的VDP报文是对已有VDP报文的扩展。本发明实施例扩展了EVB的适用范围，并提高了VN的实现效率。扩展了EVB的适用范围，降低基于VDP的VN的实现过程的复杂度，进而提高VN实现的效率。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实 现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
本发明实施例通过在接收到的虚拟机VM加入虚拟网络VN的VDP报文中添加命令类型指示信息，通过命令类型指示信息指示是EVB站处理所述VDP报文，或者EVB桥处理所述VDP报文，以将所述VM接入虚拟网络。有效避免目前在基于VDP的VN的实现过程中，实现过程复杂、操作繁杂，使得VN实现的效率差的问题。本发明实施例扩展了EVB的适用范围，并提高了VN的实现效率。

Claims (12)

  1. 一种虚拟网络的实现方法，包括：
    边缘虚拟桥EVB站接收所述EVB站中的边缘中继ER代表虚拟机VM发出的加入虚拟网络VN的虚拟机接口发现和配置协议VDP报文，所述VDP报文包括命令类型指示信息；
    所述EVB站根据所述VDP报文中包括的命令类型指示信息判断是否在所述EVB站处理所述VDP报文；
    若是，则所述EVB站处理所述VDP报文并将所述VM接入所述VN；
    若否，则所述EVB站将所述VDP报文发送至EVB桥进行处理，以在EVB桥中实现所述VM接入所述VN。
  2. 如权利要求1所述的方法，其中，所述命令类型指示信息，通过VDP命令报文的过滤信息字段进行定义；或者，通过保留的VDP类型值进行定义。
  3. 如权利要求1所述的方法，其中，所述EVB站，支持EVB桥和网络虚拟化边缘设备NVE。
  4. 如权利要求1至3任一项所述的虚拟网络的实现方法，其中，所述EVB站或EVB桥将所述VM接入所述VN的步骤包括：
    接收所述VM是否通过所述VN的身份认证的验证信息；
    在所述VM验证通过后，判断所述VN的上下文是否存在；
    若不存在，则生成所述VN的上下文；所述VN的上下文包括虚拟路由转发功能VRF转发表；
    若在所述VRF转发表中所述VM对应的VRF表项不存在，则在所述VRF转发表中生成所述VM对应的VRF转发表表项。
  5. 一种虚拟网络的实现装置，包括：
    接收模块，设置为：接收所述EVB站中的ER代表VM发出的加入虚拟网络VN的VDP报文，所述VDP报文包括命令类型指示信息；
    判断模块，设置为：根据所述VDP报文中包括的命令类型指示信息判 断是否在所述EVB站处理所述VDP报文；
    发送模块，设置为：若不在所述EVB站处理所述VDP报文，则将所述VDP报文发送至EVB桥进行处理，以在EVB桥中实现所述VM接入所述VN；
    处理模块，设置为：若在所述EVB站处理所述VDP报文，则处理所述VDP报文并将所述VM接入所述VN；以及，实现对所述VM的VN身份认证；在所述VM通过所述VN的身份认证后，若所述VN的上下文不存在则生成所述VN的上下文；若所述VM在所述VRF转发表中没有对应的表项，则在所述VRF转发表中生成所述VM的对应VRF转发表表项。
  6. 如权利要求5所述的虚拟网络的实现装置，其中，所述命令类型指示信息，通过VDP命令报文的过滤信息字段进行定义；或者，通过保留的VDP类型值进行定义。
  7. 如权利要求5或6所述的虚拟网络的实现装置，其中，所述实现装置是EVB站，同时支持EVB桥和NVE功能。
  8. 一种虚拟网络的实现系统，包括如权利要求5至7任一项所述的虚拟网络实现装置及EVB桥，其中：
    所述的虚拟网络实现装置，设置为：接收所述EVB站中的ER代表VM发出的加入虚拟网络VN的VDP报文，所述VDP报文包括命令类型指示信息；根据所述VDP报文中包括的命令类型指示信息判断是否在所述虚拟网络实现装置处理所述VDP报文；若是在所述虚拟网络实现装置处理所述VDP报文，则将所述VM接入所述VN；若不在所述虚拟网络实现装置处理所述VDP报文，则将所述VDP报文发送至EVB桥进行处理；
    所述EVB桥，设置为：对所述VDP报文进行处理，实现所述VM接入所述VN；
    所述的虚拟网络实现装置，还设置为：实现对所述VM的VN身份认证；在所述VM通过所述VN的身份认证后，若所述VN的上下文不存在则生成所述VN的上下文；若所述VM在所述VRF转发表中没有对应的表项，则在所述VRF转发表中生成所述VM的对应表项。
  9. 如权利要求8所述的虚拟网络实现系统，其中，所述命令类型指示信息，通过VDP命令报文的过滤信息字段进行定义；或者，通过保留的VDP类型值进行定义；所述虚拟网络实现装置为EVB站，同时支持EVB桥和NVE功能。
  10. 一种虚拟网络的实现方法，包括：
    边缘虚拟桥EVB站接收所述EVB站中的边缘中继ER代表虚拟机VM发出的加入虚拟网络VN的虚拟机接口发现和配置协议VDP报文；
    所述EVB站处理所述VDP报文并将所述VM接入所述VN。
  11. 一种虚拟网络的实现方法，包括：
    边缘虚拟桥EVB站接收所述EVB站中的边缘中继ER代表虚拟机VM发出的加入虚拟网络VN的虚拟机接口发现和配置协议VDP报文；
    所述EVB站将所述VDP报文发送至EVB桥进行处理，以在EVB桥中实现所述VM接入所述VN。
  12. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-4，10-11任一项的方法。
PCT/CN2015/092127 2015-03-13 2015-10-16 虚拟网络的实现方法、装置及系统 WO2016145839A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510111334.0 2015-03-13
CN201510111334.0A CN106034115B (zh) 2015-03-13 2015-03-13 虚拟网络的实现方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2016145839A1 true WO2016145839A1 (zh) 2016-09-22

Family

ID=56919600

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/092127 WO2016145839A1 (zh) 2015-03-13 2015-10-16 虚拟网络的实现方法、装置及系统

Country Status (2)

Country Link
CN (1) CN106034115B (zh)
WO (1) WO2016145839A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102647288A (zh) * 2011-02-16 2012-08-22 中兴通讯股份有限公司 一种vm数据访问保护方法及系统
CN104202187A (zh) * 2014-08-28 2014-12-10 杭州华三通信技术有限公司 一种为交换机部署边缘虚拟桥接功能的方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8953621B2 (en) * 2010-09-10 2015-02-10 Futurewei Technologies, Inc. Specifying priority on a virtual station interface discovery and configuration protocol response
CN103428106B (zh) * 2012-05-16 2016-11-23 华为技术有限公司 虚拟机vm迁移后的报文处理的方法及其设备
CN103631652B (zh) * 2012-08-28 2018-09-28 中兴通讯股份有限公司 虚拟机迁移的实现方法及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102647288A (zh) * 2011-02-16 2012-08-22 中兴通讯股份有限公司 一种vm数据访问保护方法及系统
CN104202187A (zh) * 2014-08-28 2014-12-10 杭州华三通信技术有限公司 一种为交换机部署边缘虚拟桥接功能的方法和装置

Also Published As

Publication number Publication date
CN106034115A (zh) 2016-10-19
CN106034115B (zh) 2020-01-31

Similar Documents

Publication Publication Date Title
US9553846B2 (en) Method and system for realizing virtual network
CN103580980B (zh) 虚拟网络自动发现和自动配置的方法及其装置
JP6574304B2 (ja) 仮想ネットワーク管理
US10263808B2 (en) Deployment of virtual extensible local area network
WO2015117401A1 (zh) 信息的处理方法及装置
WO2018208295A1 (en) Iot device connectivity, discovery, and networking
EP3197107A1 (en) Message transmission method and apparatus
WO2017162089A1 (zh) 网络服务的业务配置方法和装置
EP3694157B1 (en) Vxlan configuration method, device and system
WO2014166247A1 (zh) 一种虚拟网络管理的实现方法和系统
WO2015143802A1 (zh) 业务功能链处理方法及装置
JP5679343B2 (ja) クラウドシステム、ゲートウェイ装置、通信制御方法、及び通信制御プログラム
EP3544241B1 (en) Method and apparatus for deploying service in virtualized network
CN103631652A (zh) 虚拟机迁移的实现方法及系统
WO2016090900A1 (zh) 流表更新方法及装置
JP2019519146A (ja) ルーティング確立、パケット送信
CN110855488A (zh) 一种虚拟机接入方法及装置
CN106911547B (zh) 一种报文转发方法及装置
WO2015081785A1 (zh) 一种虚拟化接入方法及设备
EP4132197A1 (en) Communication method and related device
CN115002029B (zh) 一种流量转发方法、装置、设备及存储介质
WO2016145839A1 (zh) 虚拟网络的实现方法、装置及系统
WO2016141715A1 (zh) 一种实现虚拟网络的方法及系统
WO2016180141A1 (zh) 虚拟机状态管理方法及装置
CN106878051B (zh) 一种多机备份实现方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15885209

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15885209

Country of ref document: EP

Kind code of ref document: A1