CN109450696B - Network configuration method and device - Google Patents

Network configuration method and device Download PDF

Info

Publication number
CN109450696B
CN109450696B CN201811444058.XA CN201811444058A CN109450696B CN 109450696 B CN109450696 B CN 109450696B CN 201811444058 A CN201811444058 A CN 201811444058A CN 109450696 B CN109450696 B CN 109450696B
Authority
CN
China
Prior art keywords
target
interface
host
order network
network
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
CN201811444058.XA
Other languages
Chinese (zh)
Other versions
CN109450696A (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.)
New H3C Cloud Technologies Co Ltd
Original Assignee
New H3C Cloud Technologies Co Ltd
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 New H3C Cloud Technologies Co Ltd filed Critical New H3C Cloud Technologies Co Ltd
Priority to CN201811444058.XA priority Critical patent/CN109450696B/en
Publication of CN109450696A publication Critical patent/CN109450696A/en
Application granted granted Critical
Publication of CN109450696B publication Critical patent/CN109450696B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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/04Network management architectures or arrangements
    • H04L41/044Network management architectures or arrangements comprising hierarchical management structures
    • 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/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/35Switches specially adapted for specific applications
    • H04L49/354Switches specially adapted for specific applications for supporting virtual local area networks [VLAN]

Abstract

The disclosure provides a network configuration method and a network configuration device, which are applied to a controller in networking comprising a first-order network and a second-order network. The controller receives an operation instruction for indicating that a target virtual machine and a virtual port belonging to a target first-order network are bound, calls a configuration interface corresponding to the operation instruction, determines a target first interface connected with a target host where the target virtual machine is located on the switching equipment according to the stored topology information, and sends the corresponding relation between the target first-order network and a target second-order network allocated to the virtual port to the target first interface. The topology information includes a link connection relation sent by the switching device, and the link connection relation is obtained by the switching device according to a preset link discovery protocol message sent by the target host. Therefore, the automatic issuing of the corresponding relation between the target first-order network and the target second-order network can be realized.

Description

Network configuration method and device
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a network configuration method and apparatus.
Background
To scale up a traditional cloud computing network, networking with a hierarchical network topology is typically employed. Generally, first-order network communication is adopted between the switching equipment and the switching equipment in the networking, and second-order network communication is adopted between the switching equipment and the host. In this networking, a port connected to a host on a switching device is required to configure a mapping relationship between a first-order network and a second-order network to which a virtual machine running in the host belongs.
In the related art, for networking using the hierarchical network topology, a user needs to manually configure the connection relationship between the switching device and the host and manually issue the mapping relationship, and the configuration by a manual method is very prone to errors. In addition, when the number of hosts in the networking is large, a large amount of manual operation is required, which is very inconvenient.
Disclosure of Invention
In view of the above, an object of the present disclosure is to provide a network configuration method and apparatus to at least partially improve the above problem.
In a first aspect, the present disclosure provides a network configuration method, applied to a controller in a networking including a first-order network and a second-order network, where the networking further includes a host and an access switching device connected to each other, the host and the access switching device communicate through the second-order network, and two or more access switching devices communicate through the first-order network; a virtual machine runs on the host, and the access switching equipment is provided with a first interface; the method comprises the following steps:
receiving an operation instruction, wherein the operation instruction is used for indicating that a target virtual machine and a virtual port belonging to a pre-specified target first-order network are bound;
calling a configuration interface corresponding to the operation instruction, determining a target first interface connected with a target host where the target virtual machine is located on the access switching equipment according to the stored topology information, and sending a corresponding relation between the target first-order network and a target second-order network allocated to the virtual port to the target first interface;
the topology information includes a link connection relation sent by the access switching device, and the link connection relation is obtained by the access switching device according to a preset link protocol packet sent by the target host.
In a second aspect, the present disclosure further provides a network configuration apparatus, applied to a controller in a networking including a first-order network and a second-order network, where the networking further includes a host and an access switching device connected to each other, the host and the access switching device communicate through the second-order network, and two or more access switching devices communicate through the first-order network; the host runs a virtual machine, the access switching equipment has a first interface, and the apparatus includes:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving an operation instruction which is used for indicating that a target virtual machine and a virtual port belonging to a pre-specified target first-order network are bound;
a corresponding relationship issuing module, configured to invoke a configuration interface corresponding to the operation instruction, to determine, according to the stored topology information, a target first interface on the access switching device, which is connected to a target host where the target virtual machine is located, and to issue, to the target first interface, a corresponding relationship between the target first-order network and a target second-order network allocated to the virtual port;
the topology information includes a link connection relation sent by the access switching device, and the link connection relation is obtained by the access switching device according to a preset link protocol packet sent by the target host.
Compared with the prior art, the method has the following beneficial effects:
the disclosure provides a network configuration method and a network configuration device, which are applied to a controller in networking comprising a first-order network and a second-order network. The networking also comprises a host and a switching device which are connected with each other, the host and the switching device communicate through a second-order network, and the access switching device communicates with other switching devices in the networking through a first-order network. The host runs a virtual machine, and the switching device has a first interface. The controller receives an operation instruction for indicating that a target virtual machine and a virtual port belonging to a target first-order network are bound; and calling a configuration interface corresponding to the operation instruction to determine a target first interface connected with a target host where the target virtual machine is located on the switching equipment according to the stored topology information, and issuing a corresponding relation between a target first-order network and a target second-order network allocated to the virtual port to the target first interface. The topology information includes a link connection relation sent by the access switching device, and the link connection relation is obtained by the switching device according to a preset link discovery protocol message sent by the target host. Therefore, the automatic issuing of the corresponding relation between the corresponding target first-order network and the corresponding target second-order network can be realized.
Drawings
To more clearly illustrate the technical solutions of the present disclosure, the drawings needed for the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present disclosure, and therefore should not be considered as limiting the scope, and those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic diagram of a networking with a layered network topology provided by the present disclosure;
fig. 2 is a schematic flow chart of a network configuration method provided by the present disclosure;
FIG. 3 is a schematic diagram of the connection relationship between the hosts shown in FIG. 1;
fig. 4 is a schematic connection relationship diagram of a host having a plurality of second interfaces according to the present disclosure;
figure 5 is a schematic diagram of a networking with a hierarchical network topology in one particular example provided by the present disclosure;
FIG. 6 is a block schematic diagram of a controller provided by the present disclosure;
fig. 7 is a functional block diagram of a network configuration device provided in the present disclosure.
Detailed Description
To make the objects, technical solutions and advantages of the present disclosure clearer, the technical solutions of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the present disclosure, and it is apparent that the described embodiments are some, but not all embodiments of the present disclosure. The components of the present disclosure, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present disclosure, presented in the figures, is not intended to limit the scope of the claimed disclosure, but is merely representative of selected embodiments of the disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Referring to fig. 1, fig. 1 is a schematic diagram of a network 100 with a layered network topology according to the present disclosure. In some scenarios, networking with a hierarchical network topology is also referred to as hierarchical port-bound networking. The networking adopts an SDN (Software Defined Network) architecture, in the SDN architecture, a control plane and a forwarding plane are separated, and a controller is adopted to issue configuration to devices (or nodes) used for forwarding data in the networking so as to control the devices. This controller is commonly referred to as an SDN controller.
The network 100 includes a controller 150, hosts, such as the host 111, the host 112, and the host 113 shown in fig. 1, on which at least one virtual machine may run, and switching devices. The switching devices may be, for example, switching device 121, switching device 122, switching device 130, and switching device 140 shown in fig. 1, where switching device 121 and switching device 122 directly connected to a host are generally referred to as access switches, and switching device 130 may be a core switch.
Optionally, the networking 100 may further include a cloud management platform 160 for the user to perform corresponding management and configuration operations. The cloud management platform 160 may be, for example, an OpenStack dashboard. The cloud management platform 160 may issue instructions to the controller and corresponding devices in the network 100 according to user operations. Cloud management platform 160 and controller 150 may communicate with other devices in networking 100 through switching device 140, in which case switching device 140 may be a management switch and the communication network employed by cloud management platform 160 and controller 150 with other devices in networking 100 may be referred to as a management network.
The switch has a first interface, for example, the switch 121 has a first interface P1 and a first interface P2, and the switch 122 has a first interface P3. The host has a second interface, for example, the host 111 has a second interface eth1, the host 112 has a second interface eth2, and the host 113 has a second interface eth 3. The host is connected via its second interface to the corresponding first interface of the switching device. In the networking 100, a first interface on a switching device and a second interface on a host have a one-to-one correspondence.
Wherein the host and the switching device communicate via a second order network, e.g., host 111 and switching device 121 communicate via a second order network, host 112 and switching device 121 communicate via a second order network, and host 113 and switching device 122 communicate via a second order network. The switching devices communicate with each other via a first order network, for example, switching device 121, switching device 130, and switching device 122 communicate with each other via a first order network.
In the present disclosure, the first-order Network may be one of VXLAN (Virtual Extensible Local Area Network) and GRE (General Routing Encapsulation), and the second-order Network may be one of VLAN (Virtual Local Area Network), VXLAN, and GRE.
Taking the example that the first-order network is VXLAN and the second-order network is VLAN: in this case, the switching device 121 and the switching device 122 are usually VTEP (VXLAN Tunnel End Point) devices, and the VTEP devices may adopt VXLAN switches, which can convert the received VLAN packets into corresponding VXLAN packets and send the VXLAN packets to the opposite End device through the VXLAN Tunnel; or converting the received VXLAN message into a VLAN message and sending the VLAN message to the corresponding host. Switching device 130 may be a core switch.
In the above example, a virtual port belonging to a particular VXLAN segment (e.g., VXLAN 10001) is typically assigned a VLAN segment (e.g., VLAN 10) and bound to a virtual machine on the host, such that the virtual machine belongs to VXLAN 10001 and VLAN 10. In this case, there is a correspondence (also referred to as a mapping) between VXLAN 10001 and VLAN 10, which needs to be configured to the first interface of the switching device connected to the host where the virtual machine is located.
For example, assuming that the virtual machine is a virtual machine on the host 1, the corresponding relationship between VXLAN 10001 and VLAN 10 is configured on the first interface P1 of the switching device 121. In the implementation process, the host 1 encapsulates the message sent by the virtual machine into a VLAN message, and sends the VLAN message to the switching device 121, where a VLAN Tag (Tag) of the VLAN message is 10; the switching device 121 receives the VLAN packet through the first interface P1, searches for a hit corresponding relationship of the VLAN tag 10 of the VLAN packet on the first interface P1, and determines that VXLAN 10001 corresponds to VLAN 10 according to the hit corresponding relationship, so that the VLAN packet is converted into a VXLAN packet whose VXLAN network segment is identified as 10001, and is sent to a corresponding peer device (i.e., the switching device 122).
Accordingly, when the switching device 121 receives the VXLAN message whose VXLAN network segment identifier is 10001, the VXLAN message may be converted into a VLAN message whose VLAN tag is 10 according to the correspondence, and the VLAN message is sent to the host 111 through the first interface P1.
It should be noted that, when the first-order network is a GRE network, the specific implementation process is similar to that when the first-order network is a VXLAN network, and details thereof are not repeated herein.
Therefore, in the hierarchical port binding networking, a port connected with a host on the switching device is required to configure a corresponding relationship between a first-order network and a second-order network to which a virtual machine on the host belongs. In the related art, the connection relationship between the ports of the switching device and the hosts is usually configured to the controller manually by the user, which is prone to error on one hand, and on the other hand, when the number of hosts in the networking is large, the number of manual operations required is increased, which is very inconvenient.
In view of the above problems, the present disclosure provides a network configuration method and device, which can implement automatic issuing of a correspondence between a first-order network and a second-order network to which a virtual machine belongs. This will be described below.
Referring to fig. 2, fig. 2 is a flowchart of a network configuration method applied to the controller 150 in the networking 100 shown in fig. 1, and the method including various steps will be described in detail below.
Step S21, receiving an operation instruction, where the operation instruction is used to instruct to bind the target virtual machine and the virtual port belonging to the pre-specified target first-order network.
The method is described below by taking the host 111 in fig. 1 as an example. Referring to fig. 3, fig. 3 is a schematic diagram illustrating a partial connection relationship of the host 111 in the networking 100.
In a specific example, a user selects host 111 on a page of cloud management platform 160, creates virtual machine VM1 on host 111, and creates a virtual port vNIC associated with (i.e., belonging to) a particular first-order network. The virtual port may also be referred to as a virtual network card. This particular first order network may be, for example, a first order network having a segment identification of 10001, hereinafter referred to as first order network 10001 for ease of description. The first-order network 10001 is a target first-order network in the present disclosure, and may be created through the following processes: a first-order network is created on cloud management platform 160 by a user and a network segment identifier 10001 is set for the first-order network.
Of course, one of the created but unbound virtual ports on the cloud management platform 160 may be selected as the virtual port vNIC. The present disclosure is not so limited.
The user may perform an operation of binding the virtual port vNIC and the virtual machine VM1 on the cloud management platform 160, and in response to the operation, the cloud management platform 160 issues the operation instruction described in step S21 to the controller 150, so that the controller 150 calls the configuration interface corresponding to the operation instruction, and the binding of the virtual port vNIC and the virtual machine VM1 is implemented. The configuration Interface may be, for example, an Application Programming Interface (API), and the parameters passed to the API include a name of the virtual port vNIC, a name of the virtual machine VM1, and a name of the host 111 where the virtual machine VM1 is located.
In addition, a virtual switch (vSwitch) is included on the host 111 for enabling communication between the virtual machines on the host 111 and switching of the virtual machines with external traffic. When a vSwitch is newly created, one of the second interfaces of the host may be selected as the uplink interface of the vSwitch, so as to forward the uplink traffic of the vSwitch from the uplink interface. In addition, the vSwitch also includes a downstream interface for connecting to the virtual machine, and is configured to communicate with the virtual machine through the downstream interface. For example, fig. 3 shows a scenario in which a vSwitch has an upstream interface eth0 and a downstream interface vnet 0.
Step S22, invoking a configuration interface corresponding to the operation instruction, to determine a target first interface on the switch device connected to the target host where the target virtual machine is located according to the stored topology information, and sending a corresponding relationship between the target first-order network and a target second-order network allocated to the virtual port to the target first interface.
The topology information refers to network topology information of the networking 100 stored in the controller 150, and the topology information includes link connection relationships sent by each switching device, and the link connection relationships are obtained by each switching device according to a preset link protocol packet sent by a corresponding host.
In the present disclosure, the content of the configuration interface is expanded, and a first interface of the switching device that determines the connection of the target host is added, and an instruction for issuing the corresponding relationship between the target first-order network and the target second-order network to which the virtual port belongs is issued to the first interface. Thus, when the controller 150 calls the configuration interface, the corresponding relationship can be automatically issued.
The controller 150 may issue the determined identifier of the target first interface and the corresponding relationship between the target first-order network and the target second-order network to the switching device connected to the target host, and when receiving the identifier and the corresponding relationship, the switching device configures the corresponding relationship on the first interface indicated by the identifier (that is, the target first interface).
In this disclosure, each host and each switch device in the networking support the preset Link Discovery Protocol, for example, LLDP (Link Layer Discovery Protocol), but the preset Link Discovery Protocol may also be any other Protocol capable of discovering the connection relationship between the ports of the host and the switch device.
Taking the scenario shown in fig. 3 as an example, assuming that the preset link discovery protocol is LLDP, when the host 111 accesses the switch device 121, the host 111 sends an LLDP message to the switch device 121, where the LLDP message carries an identifier capable of uniquely representing the host 111, for example, a name of the host.
In the related art, a host in a networking with a hierarchical network topology usually has only one second interface (i.e., only one outgoing interface), and thus only the connection relationship between the host and the port of the switching device needs to be determined.
Under the condition that the second interfaces of the host are expanded to more than two, if the preset link discovery protocol message only carries the identifier of the host, the corresponding relation to be issued can be issued to more than two first interfaces respectively connected with the more than two second interfaces of the host, so that the messages sent from the second interfaces of the host can be forwarded. If the preset link discovery protocol message carries the identifier of the host and the identifier of the corresponding second interface, the topology information stored in the controller 150 includes the connection relationship between the second interface of the host and the first interface of the switching device, so that the specific first interface to be issued according to the correspondence relationship to be issued can be determined according to the topology information.
In the implementation process, the switching device 121 obtains a link connection relationship according to the LLDP packet sent by the host 111: the first interface P1 of the switching device 121 is connected to the host 111. The link connection is then sent to controller 150. In the present disclosure, there are various ways for the switching device 121 to send the link connection relationship to the controller 150, for example, an LLDP message sent by the host may be sent to the controller 150; as another example, the link connection relationship obtained from the received LLDP message may be uploaded to the controller 150 through another message. The present disclosure is not so limited.
With the above design, the controller 150 may find out the first interface of the switching device (i.e., the first interface P1 of the switching device 121) to which the host 111 (i.e., the target host) is connected as the target first interface from the topology information. After the controller 150 allocates a target second-order network to the virtual port vNIC, the corresponding relationship between the target second-order network and the target first-order network may be sent to the target first interface, that is, the first interface P1 of the switching device 121.
Therefore, the connection relation between the host and the first interface of the exchange equipment can be prevented from being manually configured by a user, the operation is more convenient, and configuration errors caused by misoperation can be avoided.
In addition, when the link connection relationship between the host and the switching device in the networking 100 changes, the corresponding LLDP packet is sent, so that the controller 150 updates the stored topology information in time according to the received LLDP packet, and configuration errors caused by the fact that the user cannot know the change of the link connection relationship in time can be avoided.
Optionally, in this disclosure, an instruction for allocating a target second-order network to a virtual port may be further provided in the configuration interface corresponding to the operation instruction, based on which the method may further include the following steps:
and calling a configuration interface corresponding to the operation instruction to determine a target second interface from second interfaces of the target host machine where the target virtual machine is located, searching a second-order network allocation range of the target second interface from a pre-stored configuration file, and selecting a target second-order network which is not used by the target host machine from the second-order network allocation range to allocate to the virtual port.
It should be understood that in the present disclosure, step S22 and the above steps may be implemented by calling the configuration interface once.
In the related art, the target host usually has only one second interface, and in this case, the second interface may be directly used as the target second interface. However, in the scenario of the host having more than two second interfaces described later, the target second interface may be determined according to a selection of a user. Details will be described later.
In the networking 100, for a second interface of each host, a second-order network allocation range of the second interface may be configured in a configuration file of the controller 150. Specifically, for any two second interfaces that need to forward messages of the same first-order network (for example, the first-order network 10001), the same name may be configured for the two second interfaces in the configuration file of the controller 150.
For example, in the scenario shown in fig. 1, assuming that the second interface eth1 and the second interface eth2 are both used for forwarding packets of the first-order network 10001, the same name (e.g., export1) may be configured for the second interfaces eth1 and eth2 in the configuration file of the controller 150. On this basis, assuming that the second interface eth2 and the second interface eth3 are both used for forwarding packets of the first-order network 10002, the same names may be configured for the second interfaces eth2 and eth3 in the configuration file of the controller 150, and the names of the second interfaces eth1, eth2, and eth3 in the configuration file of the controller 150 are the same and are all export 1.
For each second interface name in the configuration file, a corresponding second-order network allocation range (e.g., range of second-order network 1-second-order network 4094) is set for the name. The same names are used for the same ranges. Taking the name of export1 and the second-order network allocation range of 1-4094 as examples, the following contents are configured in the configuration file: second order network range: export1:1: 4094.
Taking the above-mentioned virtual port vNIC as an example, in the process of allocating a target second-order network to the virtual port vNIC, a target virtual machine (i.e., virtual machine VM1) that needs to be bound to the virtual port vNIC is determined, and a target host (i.e., host 111) where virtual machine VM1 is located is determined. And determining a target second interface associated with the virtual port vNIC from the second interfaces of the host 111, wherein the target second interface is used for forwarding the message from the virtual port vNIC. Assuming that the host 111 has only one second interface eth1, the second interface eth1 can be directly used as the target second interface. Accordingly, the target second-order network allocated for the virtual port vNIC may be selected from the second-order network allocation range of the second interface eth 1.
Specifically, the second interface eth1 has a name (e.g., export1) on the controller 150, and the controller 150 may search the configuration file for a second-order network allocation range corresponding to the export1, e.g., 1-4094, and may select a second-order network that is not used by the virtual ports of the other virtual machines on the host 111 as a target second-order network (e.g., second-order network 10) from the range, and allocate the second-order network 10 to the virtual port vNIC.
As described above, in the related art, it is common to set the same name for the second interface for forwarding the same first-order network in the controller, and set a second-order network allocation range for the name. Thus, the virtual ports associated with these second interfaces, which are set to the same name, can only allocate the same range of second-order networks, are very inflexible, and limit to some extent the number of second-order networks that can be used on each host. This is also the reason why each host is allowed to have only one first interface in the related art.
In view of the above, the present disclosure proposes a new way to name the second interface of the host. Correspondingly, the network configuration method provided by the present disclosure may further include the following steps:
and configuring a second interface of the host in the networking with a name with a prefix and a suffix and a second-order network distribution range corresponding to the name in the configuration file, wherein the names of different first interfaces for forwarding messages of the same first-order network have the same prefix.
Referring to the above example, in the scenario shown in fig. 1, the second interfaces eth1 and eth2 are both used for forwarding packets of the first-order network 10001, and the same prefixes, for example, export10001, may be configured for the second interfaces eth1 and eth2 in the configuration file of the controller 150, and then the prefixes thereof are customized according to requirements, for example, the name of the second interface eth1 may be export10001_1, and the name of the second interface eth2 may be export10001_ 2. As such, different second order network allocation ranges may be configured for a second interface using the same first order network.
With the above improvement, a plurality of second interfaces may be provided on each host. In some scenarios, a virtual machine on a host may have more than two second interfaces, which are respectively connected to a management (management) network, a business (business) network, a storage network, and the like.
The case where the host has more than two second interfaces will be described below with reference to the scenario shown in fig. 4. As shown in fig. 4, a host 1 and a host 2 are connected to the switching device 3, respectively, wherein the host 1 has second interfaces eth0 and eth1, and the host 2 has second interfaces eth2 and eth 3. The second interfaces eth0 and eth2 perform transmission of management data through the second-order network 10000, and the second interfaces eth1 and eth3 perform transmission of traffic data through the second-order network 20000.
Host 1 has virtual machine VM1 running thereon, host 2 has virtual machine VM2 running thereon, virtual machine VM1 has virtual ports vNIC0 and vNIC1, and virtual machine VM2 has virtual ports vNIC2 and vNIC 3. The virtual ports vNIC0 and vNIC2 belong to the second-order network 10000, and the virtual ports vNIC1 and vNIC3 belong to the second-order network 20000.
Host 1 and host 2 also run corresponding virtual switches, respectively, and since the virtual switches are used for two-layer forwarding of the packet, virtual switches accessed by virtual machines belonging to the same first-order network (e.g., VXLAN or GRE) may have the same name on a controller (not shown in fig. 4). For example, as shown in fig. 4, the virtual switch on host 1 communicatively connected to virtual port vNIC0 is vSwitch0-manage, and the virtual switch on host 2 communicatively connected to virtual port vNIC2 is vSwitch 0-manage; the virtual switch on host 1 communicatively coupled to virtual port vNIC1 is vSwitch1-business, and the virtual switch on host 2 communicatively coupled to virtual port vNIC3 is vSwitch 1-business.
Of course, the names of the virtual switches accessed by the virtual machines belonging to the same first-order network on the controller may also be different, and the disclosure does not limit this.
In the above scenario, the second interfaces eth0 and eth2 using the same first-order network 10000 may be configured with names having the same prefix in the configuration file of the controller, and suffixes may be set as needed, so that different second-order network allocation ranges may be set for the second interfaces eth0 and eth 2. For example, the name of the second interface eth0 is manageexport _1, and the corresponding second-order network allocation range is set to 1-2048; the second interface eth2 is named manageexport _2 and its corresponding second-order network allocation range is set to, for example, 2049-.
The second interfaces eth1 and eth3 using the same first-order network 20000 may be configured with names having the same prefix and suffixes of both may be set according to requirements, so that the second-order network allocation ranges of the second interfaces eth1 and eth3 may be set to be different. For example, the name of the second interface eth1 is businessexport _1, and the corresponding second-order network allocation range is set to 2049-; the name of the second interface eth3 is businessexport _2, and the second-order network allocation range corresponding to the second interface eth3 is set to 1-2048.
Based on the above configuration, in implementation, a prefix may be selected by a user as a target prefix, and then the target first-order network is established based on the target prefix, or the target prefix is associated with the established target first-order network. Then, a virtual port belonging to the target first-order network is created, and the created virtual port is bound with a specified virtual machine (namely, a target virtual machine); or binding the created virtual port belonging to the target first-order network with the target virtual machine.
In the case that the host has more than two second interfaces, in the process of allocating the target second-order network to the virtual port, the target second interface may be determined from the second interfaces of the target host where the target virtual machine is located according to the target prefix selected by the user:
and acquiring a target prefix selected by a user, and determining one of second interfaces of which the names on the target host comprise the target prefix as the target second interface.
When only one name on the target host includes the second interface of the target prefix, the second interface can be directly determined as the target second interface. When there are more than two second interfaces of which the names include the target prefix on the target host, one of the more than two second interfaces can be selected as the target second interface. In detail, one of the more than two second interfaces may be randomly selected as the target second interface, or a second interface with a smallest port number (or a largest port number) may be selected as the target second interface, which is not limited in this embodiment. Correspondingly, if the target host where the target virtual machine is located has more than two second interfaces, the number of the first interfaces connected to the target host where the target virtual machine is located on the switch device is more than two. For this situation, in a specific embodiment, if the preset link protocol message only carries the host identifier, two or more first interfaces connected to the target host on the switching device may be determined as the target first interfaces, and a corresponding relationship between the target first-order network and the target second-order network allocated to the virtual port is sent to the two or more determined target first interfaces.
In another embodiment, if the preset link protocol packet includes the host identifier and the identifier of the corresponding second interface, the first interface connected to the target second interface may be determined as the target first interface according to the topology information, and the corresponding relationship between the target first-order network and the target second-order network allocated to the virtual port is sent to the determined target first interface. For this situation, in the network configuration method provided by the present disclosure, step S22 may further include the following steps to determine, according to the stored topology information, a target first interface on the switch device connected to the target host where the target virtual machine is located:
and searching a first interface connected with the target second interface on the switching equipment from the topology information, and determining the searched first interface as the target first interface.
A specific example is given below in conjunction with the networking 200 shown in fig. 5 to further illustrate the network configuration method provided by the present disclosure. First, the architecture of the networking 200 will be briefly described.
In networking 200, the first order network is VXLAN and the second order network is VLAN. Networking 200 includes host 211, host 212, host 213, VTEP 221, VTEP 222, core switch 230, management switch 240, controller 250, and cloud management platform 260. VTEP 221 may act as switching device 121 in fig. 1, and VTEP 222 may act as switching device 122 in fig. 1, among other things.
Among them, the host 211 runs a virtual machine 2111 and a virtual machine 2112, the host 212 runs a virtual machine 2121, and the host 213 runs a virtual machine 2131 and a virtual machine 2132. The host 211 has second interfaces eth0 and eth1, the host 212 has second interfaces eth2 and eth3, and the host 213 has second interface eth 4. The virtual machines on the hosts may be communicatively connected through respective virtual switches (e.g., vSwitch0-vSwitch6 shown in fig. 5) and respective second interfaces (e.g., eth0-eth4 shown in fig. 5).
Suppose that: the names of the second interfaces eth0 and eth2 in the configuration file of the controller 250 each include a prefix export1, where the name of the second interface eth0 is export1_0, and the name of the second interface eth2 is export1_ 2; the names of the second interfaces eth1, eth3 and eth4 in the configuration file of the controller 250 each include a prefix export2, where the name of the second interface eth1 is export2_1, the name of the second interface eth3 is export2_3, and the name of the second interface eth4 is export2_ 4. Further, the following information is configured in the configuration file of the controller 250:
network_vlan_ranges:export1_0:1:4094;
network_vlan_ranges:export1_2:1:4094;
network_vlan_ranges:export2_1:1:4094;
network_vlan_ranges:export2_3:100:2048;
network_vlan_ranges:export2_4:1000:4094。
in addition, each host sends an LLDP message to the VTEP when accessing the corresponding VTEP, where the LLDP message includes an identifier of the host. For example, when accessing VTEP 221, host 211 sends an LLDP message to VTEP 221, where the LLDP message includes an identifier of host 211. The link connection relationship determined by VTEP 221 from the LLDP message is that host 211 is connected to first interfaces P0 and P1 of the device, and sends the link connection relationship to controller 250. As another example, host 213 sends an LLDP message to VTEP 222 when accessing VTEP 222, where the LLDP message includes an identification of host 213. The link connection relationship determined by the VTEP 222 according to the LLDP message is that the host 213 is connected to the first interface P4 of the present device, and sends the link connection relationship to the controller 250.
In a specific example, if the correspondence between the VLAN and the VXLAN to which the virtual machine 2111 belongs on the host 211 needs to be issued to a corresponding VTEP, the network configuration method provided by the present disclosure may include the following steps:
first, the cloud management platform 260 selects the prefix export1 as a target prefix according to a user operation, and associates the target prefix with the created VXLAN 10001.
Second, virtual port vNIC0 associated with VXLAN 10001 is created, and virtual port vNIC0 belongs to VXLAN 10001. Then VXLAN 10001 can act as the target first-order network in this disclosure.
Thirdly, the cloud management platform 260 issues an operation instruction t1 to the controller 250 according to the user operation, where the operation instruction is used to instruct: virtual port vNIC0 associated with VXLAN 10001 is bound to virtual machine 2111 on host 211.
Fourthly, the controller 250 receives the operation instruction t1 and calls the API corresponding to the operation instruction t1 to implement the following processes:
(1) and determining that the host where the virtual machine 2111 is located is the host 211, and taking a second interface eth0 with the name prefix of the host 211 as a target prefix export1 as a target second interface.
(2) The name of the second interface eth0 on the controller 250 is export1_0, so that the VLAN allocation range corresponding to export1_0 can be searched from the configuration file, and the range of 1 to 4094 is obtained; from which it is looked up that a VLAN not used by host 211 is assigned to virtual port vNIC 0.
Assuming that VLAN 20 is used for the virtual port bound to virtual machine 2112, one of VLANs 1-4094 other than VLAN 20 may be assigned to virtual port vNIC0, e.g., VLAN 10.
(3) It is determined from the topology information that host 211 is connected to first interfaces P0 and P1 of VTEP 221, then first interfaces P0 and P1 are both the target first interfaces in this disclosure.
(4) And issuing the corresponding relation between VXLAN 10001 and VLAN 10 to the first interfaces P0 and P1 of VTEP 221.
In another specific example, if the correspondence between the VLAN and the VXLAN to which the virtual machine 2131 on the host 213 belongs needs to be issued to a corresponding VTEP, the network configuration method provided by the present disclosure may include the following steps:
first, the cloud management platform 260 selects the prefix export2 as a target prefix according to a user operation, and associates the target prefix with the created VXLAN 10002.
Second, virtual port vNIC6 associated with VXLAN 10002 is created, and virtual port vNIC6 belongs to VXLAN 10002.
Thirdly, the cloud management platform 260 issues an operation instruction t2 to the controller 250 according to the user operation, where the operation instruction is used to instruct: virtual port vNIC6 associated with VXLAN 10002 is bound to virtual machine 2131 on host 213.
Fourthly, the controller 250 receives the operation instruction t2 and calls the API corresponding to the operation instruction t2 to implement the following processes:
(1) the host where the virtual machine 2131 is located is determined to be 213, and since only one second interface eth4 is located on the host 213, the second interface eth4 is determined to be the target second interface.
(2) The name of the second interface eth4 on the controller 250 is export2_4, so that the VLAN allocation range corresponding to export2_4 can be searched from the configuration file, and the allocation range of 1000-; from which a VLAN (e.g., VLAN 1000) not used by host 213 is looked up to virtual port vNIC 6.
(3) It is determined from the topology information that host 213 is connected to first interface P4 of VTEP 222, then first interface P4 is the target first interface in this disclosure.
(4) And issuing the corresponding relation between VXLAN 10002 and VLAN 1000 to the first interface P4.
The above steps one to eight may be all adopted for the other virtual machines shown in fig. 5, and the correspondence between the VLAN and VXLAN to which the other virtual machines belong is issued. Specifically, it is assumed that, through the above-described procedure, VTEP 221 and VTEP 222 are configured with the following correspondence relationships:
Figure GDA0003278007650000171
Figure GDA0003278007650000181
it should be noted that, as shown in the above table, the corresponding relationship of the configuration of each first interface is shown in the case that the preset link protocol message only carries the host identifier.
In the above case, taking the example that the virtual machine 2112 sends a message to the virtual machine 2131 through the virtual port vNIC1, a process of forwarding the message by the VTEP in the networking 200 based on the correspondence configured on the first interface is described.
The first virtual machine 2112 sends a message D1 through the virtual port vNIC1, and the host 211 encapsulates the message D1 into a VLAN message D2 with a VLAN tag of 20, and sends the VLAN message D2 to the VTEP 221.
Secondly, the VTEP 221 receives the VLAN message D2, recognizes that the VLAN tag carried by the VLAN message D2 is 20, and can determine that the corresponding relationship of the VLAN 20 is configured on the first interface P1 of the device, and then determines that the VLAN 20 corresponds to VXLAN 10002 according to the corresponding relationship configured on the first interface P1, so as to forward and encapsulate the VLAN message D2 into a VXLAN message D3 carrying a VXLAN identifier 10002, and send the VXLAN message D3 to an opposite device (VTEP 222).
Thirdly, the VTEP 222 receives the VXLAN message D3, recognizes that the VXLAN identifier carried by the VXLAN message D3 is 10002, converts the VXLAN message D3 into a VLAN message D4 carrying a VLAN identifier 1000 according to the corresponding relationship on the first interface P4, and sends a VLAN message D4 through the first interface P4.
Fourthly, the host 213 receives the VLAN packet D4, decapsulates the VLAN packet D4 to obtain a packet D1, and sends the packet D1 to the virtual machine 2131 according to the destination address.
Referring to fig. 6, fig. 6 is a schematic diagram of a hardware structure of a controller 150 according to the present embodiment. The controller 150 may include a processor 151 and a machine-readable storage medium 152. The processor 151 and the machine-readable storage medium 152 may communicate via a system bus. Also, the machine-readable storage medium 152 stores machine-executable instructions, and the processor 151 may perform the network configuration method described above by reading and executing the machine-executable instructions corresponding to the network configuration logic in the machine-readable storage medium 152.
The machine-readable storage medium 152 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
Referring to fig. 7, the present embodiment further provides a network configuration apparatus 700, where the network configuration apparatus 700 includes at least one functional module that can be stored in the machine-readable storage medium 152 in the form of software. Functionally, the network configuration apparatus 700 may include a receiving module 710 and a corresponding relationship issuing module 720.
The receiving module 710 is configured to receive an operation instruction, where the operation instruction is used to instruct to bind a target virtual machine and a virtual port belonging to a pre-specified target first-order network.
In the present disclosure, the receiving module 710 may perform step S21 shown in fig. 2, and the detailed description of step S21 may be referred to for the description of the receiving module 710.
The corresponding relationship issuing module 720 is configured to invoke a configuration interface corresponding to the operation instruction, determine a target first interface on the switching device, which is connected to a target host where the target virtual machine is located, according to the stored topology information, and issue a corresponding relationship between the target first-order network and a target second-order network allocated to the virtual port to the target first interface.
The topology information includes a link connection relation sent by the switching device, and the link connection relation is obtained by the switching device according to a preset link protocol packet sent by the target host.
In the present disclosure, the correspondence issuing module 720 may execute step S22 shown in fig. 2, and the detailed description of step S22 may be referred to for the description of the correspondence issuing module 720.
Optionally, the network configuration apparatus 700 may further include a second-order network allocation module 730.
The second-order network allocation module 730 is configured to invoke a configuration interface corresponding to the operation instruction, so as to determine a target second interface from second interfaces of the target host where the target virtual machine is located, search a second-order network allocation range of the target second interface from a pre-stored configuration file, and select a target second-order network that is not used by the target host from the second-order network allocation range to allocate to the virtual port.
Optionally, the network configuration apparatus 700 may further include a port name configuration module 740.
The port name configuration module 740 is configured to configure, in the configuration file, a name having a prefix and a suffix and a second-order network allocation range corresponding to the name for the second interface of the host in the networking, where names of different first interfaces for forwarding a message of the same first-order network have the same prefix.
In the present disclosure, the host may have more than two second interfaces. In this case, the specific way for the second-order network allocation module 730 to determine a target second interface from the second interfaces of the target host where the target virtual machine is located may be:
and acquiring a target prefix selected by a user, and determining one of second interfaces of which the names on the target host comprise the target prefix as the target second interface.
The specific manner of determining, by the correspondence issuing module 720 according to the stored topology information, the target first interface connected to the target host where the target virtual machine is located on the switch device may be:
and searching a first interface connected with the target second interface on the switching equipment from the topology information, and determining the searched first interface as the target first interface.
Alternatively, in the present disclosure, the first order network may be VXLAN or GRE and the second order network may be VXLAN, VLAN or GRE.
In summary, the present disclosure provides a network configuration method and apparatus, which are applied to a controller in a networking system including a first-order network and a second-order network. The networking also comprises a host and a switching device which are connected with each other, the host and the switching device communicate through a second-order network, and the access switching device communicates with other switching devices in the networking through a first-order network. The host runs a virtual machine, and the switching device has a first interface. The controller receives an operation instruction for indicating that a target virtual machine and a virtual port belonging to a target first-order network are bound, calls a configuration interface corresponding to the operation instruction, determines a target first interface connected with a target host where the target virtual machine is located on the switching equipment according to the stored topology information, and sends the corresponding relation between the target first-order network and a target second-order network allocated to the virtual port to the target first interface. The topology information includes a link connection relation sent by the access switching device, and the link connection relation is obtained by the switching device according to a preset link discovery protocol message sent by the target host. Therefore, the automatic issuing of the corresponding relation between the corresponding target first-order network and the corresponding target second-order network can be realized.
In the embodiments provided in the present disclosure, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present disclosure may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present disclosure. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only for the specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present disclosure, and all the changes or substitutions should be covered within the scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims (10)

1. A network configuration method is characterized in that the method is applied to a controller in networking comprising a first-order network and a second-order network, the networking further comprises a host and a switching device which are connected with each other, the host and the switching device communicate through the second-order network, and the switching device communicates with other switching devices in the networking through the first-order network; a virtual machine runs on the host, and the switching equipment is provided with a first interface; the method comprises the following steps:
receiving an operation instruction, wherein the operation instruction is used for indicating that a target virtual machine and a virtual port belonging to a pre-specified target first-order network are bound;
calling a configuration interface corresponding to the operation instruction, determining a target first interface connected with a target host where the target virtual machine is located on the switching equipment according to the stored topology information, and sending a corresponding relation between the target first-order network and a target second-order network allocated to the virtual port to the target first interface;
the topology information comprises a link connection relation sent by the switching equipment, and the link connection relation is obtained by the switching equipment according to a preset link protocol message sent by the target host;
and configuring a name with a prefix and a suffix and a second-order network distribution range corresponding to the name for a second interface of the host in the networking in a configuration file, wherein the names of different first interfaces for forwarding messages of the same first-order network have the same prefix.
2. The method of claim 1, further comprising:
and calling a configuration interface corresponding to the operation instruction to determine a target second interface from second interfaces of the target host machine where the target virtual machine is located, searching a second-order network allocation range of the target second interface from the configuration file, and selecting a target second-order network which is not used by the target host machine from the second-order network allocation range to allocate to the virtual port.
3. The method of claim 1, wherein the host has a plurality of second interfaces; determining a target second interface from second interfaces of a target host machine where the target virtual machine is located, including:
and acquiring a target prefix selected by a user, and determining one of second interfaces of which the names on the target host comprise the target prefix as the target second interface.
4. The method of claim 3, wherein determining the target first interface on the switch device connected to the target host where the target virtual machine is located according to the stored topology information comprises:
and searching a first interface connected with the target second interface on the switching equipment from the topology information, and determining the searched first interface as the target first interface.
5. The method of any of claims 1-4, wherein the first order network is a VXLAN or GRE network and the second order network is a VXLAN, VLAN, or GRE network.
6. A network configuration device is characterized in that the network configuration device is applied to a controller in networking comprising a first-order network and a second-order network, the networking further comprises a host and a switching device which are connected with each other, the host and the switching device communicate through the second-order network, and the switching device communicates with other switching devices in the networking through the first-order network; a virtual machine runs on the host, and the switching equipment is provided with a first interface; the device comprises:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving an operation instruction which is used for indicating that a target virtual machine and a virtual port belonging to a pre-specified target first-order network are bound;
a corresponding relationship issuing module, configured to invoke a configuration interface corresponding to the operation instruction, to determine, according to the stored topology information, a target first interface on the switching device, which is connected to a target host where the target virtual machine is located, and to issue a corresponding relationship between the target first-order network and a target second-order network allocated to the virtual port to the target first interface;
the topology information comprises a link connection relation sent by the switching equipment, and the link connection relation is obtained by the switching equipment according to a preset link protocol message sent by the target host;
and a port name configuration module, configured to configure, in a configuration file, a name having a prefix and a suffix and a second-order network allocation range corresponding to the name for a second interface of the host in the network, where names of different first interfaces for forwarding a message of the same first-order network have the same prefix.
7. The apparatus of claim 6, further comprising:
and the second-order network allocation module is used for calling the configuration interface corresponding to the operation instruction so as to determine a target second interface from the second interface of the target host where the target virtual machine is located, searching a second-order network allocation range of the target second interface from the configuration file, and selecting a target second-order network which is not used by the target host from the second-order network allocation range to allocate to the virtual port.
8. The apparatus of claim 6, wherein the host has a plurality of second interfaces; the specific way for the second-order network allocation module to determine a target second interface from the second interfaces of the target host where the target virtual machine is located is as follows:
and acquiring a target prefix selected by a user, and determining one of second interfaces of which the names on the target host comprise the target prefix as the target second interface.
9. The apparatus according to claim 8, wherein the specific manner for the correspondence issuing module to determine, according to the stored topology information, the target first interface on the switch device connected to the target host where the target virtual machine is located is as follows:
and searching a first interface connected with the target second interface on the switching equipment from the topology information, and determining the searched first interface as the target first interface.
10. The apparatus according to any of claims 6-9, wherein the first order network is a VXLAN or GRE network and the second order network is a VXLAN, VLAN or GRE network.
CN201811444058.XA 2018-11-29 2018-11-29 Network configuration method and device Active CN109450696B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811444058.XA CN109450696B (en) 2018-11-29 2018-11-29 Network configuration method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811444058.XA CN109450696B (en) 2018-11-29 2018-11-29 Network configuration method and device

Publications (2)

Publication Number Publication Date
CN109450696A CN109450696A (en) 2019-03-08
CN109450696B true CN109450696B (en) 2022-02-25

Family

ID=65555636

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811444058.XA Active CN109450696B (en) 2018-11-29 2018-11-29 Network configuration method and device

Country Status (1)

Country Link
CN (1) CN109450696B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113300984B (en) * 2020-04-08 2022-09-13 阿里巴巴集团控股有限公司 Communication method, device, system and storage medium

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101110745A (en) * 2007-08-14 2008-01-23 华为技术有限公司 Method, device and system for engaging second layer network and third layer network
CN103152256B (en) * 2013-02-22 2017-05-03 浪潮电子信息产业股份有限公司 Virtual routing network design method based on cloud computing data center
CN104468219B (en) * 2014-12-11 2019-01-08 新华三技术有限公司 Virtual networking method for discovering network topology and equipment
US9686176B2 (en) * 2014-12-19 2017-06-20 Ciena Corporation Constrained and viable path computation systems and methods
CN108768692B (en) * 2018-04-18 2020-07-28 华为技术有限公司 Network creation method, related equipment and system

Also Published As

Publication number Publication date
CN109450696A (en) 2019-03-08

Similar Documents

Publication Publication Date Title
CN111885075B (en) Container communication method, device, network equipment and storage medium
CN106789667B (en) Data forwarding method, related equipment and system
CN108293022B (en) Method, device and system for transmitting message
US10063470B2 (en) Data center network system based on software-defined network and packet forwarding method, address resolution method, routing controller thereof
CN107579900B (en) Method, device and system for accessing VX L AN network from V L AN network
CN107968749B (en) Method for realizing QinQ route termination, switching chip and switch
CN111800329B (en) Message forwarding method, device and medium based on SDN and OVN
CN108141416A (en) A kind of message processing method, computing device and message process device
WO2014176740A1 (en) Stream classifier, service routing trigger, and message processing method and system
CN105323136A (en) Information processing method and device
CN109245984A (en) A kind of message transmitting method, a kind of information processing method and its relevant device
CN104283806A (en) Service link processing method and device
WO2017113300A1 (en) Route determining method, network configuration method and related device
CN102857414A (en) Forwarding table writing method and device and message forwarding method and device
JP7190569B2 (en) Data center traffic sharing method, apparatus, device and storage medium
CN111010329B (en) Message transmission method and device
CN112688814B (en) Equipment access method, device, equipment and machine readable storage medium
CN104468401A (en) Message processing method and device
CN103259726A (en) Method, device and system for storing and sending MAC address table entries
CN109150638A (en) A kind of route management method and device
EP2965476A1 (en) Forwarding ethernet packets
JP2019521619A (en) Packet forwarding
CN106331206A (en) Domain name management method and device
CN107517129B (en) Method and device for configuring uplink interface of equipment based on OpenStack
CN112104499A (en) Container network model construction method, device, equipment and medium

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