WO2019214560A1 - 一种dhcp报文处理方法及装置 - Google Patents

一种dhcp报文处理方法及装置 Download PDF

Info

Publication number
WO2019214560A1
WO2019214560A1 PCT/CN2019/085602 CN2019085602W WO2019214560A1 WO 2019214560 A1 WO2019214560 A1 WO 2019214560A1 CN 2019085602 W CN2019085602 W CN 2019085602W WO 2019214560 A1 WO2019214560 A1 WO 2019214560A1
Authority
WO
WIPO (PCT)
Prior art keywords
dhcp
network
address
node
request
Prior art date
Application number
PCT/CN2019/085602
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 WO2019214560A1 publication Critical patent/WO2019214560A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0876—Aspects of the degree of configuration automation
    • H04L41/0886—Fully automatic configuration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/562—Brokering proxy services

Definitions

  • the present application relates to the field of network communication technologies, and in particular, to a DHCP message processing method and apparatus.
  • At least one independent business area and one centralized operation and maintenance management area are usually set.
  • the service area is used to deploy various types of service systems
  • the operation and maintenance management area is used to deploy management and operation and maintenance platforms of various software and hardware systems, and is isolated from the service network.
  • management nodes are deployed in the operation and maintenance management area, and virtual machines or physical machines for various service systems are deployed in each service area.
  • Each management node deployed in the operation and maintenance management area is used to provide a management and operation and maintenance platform for the virtual machine or the physical machine in the service area.
  • a Dynamic Host Configuration Protocol (DHCP) service node for assigning an IP address is usually deployed.
  • Dimension management area When an administrator issues a virtual machine or a physical machine in a certain service area, the virtual machine or physical machine needs to send a DHCP request through the service network to obtain an IP address.
  • the DHCP is a Layer 2 network protocol.
  • the service network in the service area and the management network in the operation and maintenance management area cannot be connected to each other. As a result, DHCP broadcasts cannot be sent from the virtual machine or physical machine in the service area to the DHCP service in the operation and maintenance management area. Nodes, which in turn cause virtual machines or physical machines to fail to automatically configure IP addresses using DHCP broadcasts.
  • the present application solves the problem of isolation of the service network and the management network by deploying a DHCP proxy node, so that the DHCP proxy node can forward the DHCP broadcast obtained from the service network to the DHCP service node located on the management node through the management network.
  • the resulting virtual machine or physical machine cannot implement the problem of automatic IP address configuration.
  • the present application provides a dynamic host configuration protocol DHCP packet processing method, where the method includes: a DHCP proxy node receives a request from a service network, where the request is used to indicate that an IP address is allocated to a virtual machine or a physical machine; The DHCP proxy node sends the request to a DHCP service node, obtains an IP address from the DHCP service node according to the request in the management network, and sends the IP address to the virtual machine or the physical machine.
  • the request includes a DHCP Discover broadcast message in the DHCP protocol.
  • the IP address can be carried by a DHCP Offer message in the DHCP protocol.
  • DHCP proxy node by configuring a DHCP proxy node, message forwarding between the management network and the service network can be implemented, thereby automatically assigning an IP address to the virtual machine or the physical machine.
  • the receiving, by the DHCP proxy node, the request from the service network includes: the DHCP proxy node receiving the request from the virtual machine or the physical machine by using the first network card
  • the first network card is used to access the service network to implement receiving and sending the request in a service network.
  • the DHCP proxy node obtains an IP address from the DHCP service node according to the request in the management network, including: the DHCP proxy node receives the second network card
  • the DHCP service node is configured to access the management network according to the IP address allocated by the request, to implement receiving and sending the IP address in the management network.
  • the first network card is located on a host where the second network card is located, and the DHCP proxy node is deployed on a host where the second network card is located.
  • the present application further provides a DHCP proxy node, including a receiving module and a sending module, wherein the receiving module is configured to receive a request from a service network, and obtain a request from a DHCP service node according to the request in a management network. Obtaining an IP address, the request is used to indicate that an IP address is assigned to a virtual machine or a physical machine; and the sending module is configured to send the IP address to the virtual machine or a physical machine.
  • a DHCP proxy node including a receiving module and a sending module, wherein the receiving module is configured to receive a request from a service network, and obtain a request from a DHCP service node according to the request in a management network. Obtaining an IP address, the request is used to indicate that an IP address is assigned to a virtual machine or a physical machine; and the sending module is configured to send the IP address to the virtual machine or a physical machine.
  • the receiving module is specifically configured to receive, by using a first network card, the request from the virtual machine or a physical machine, where the first network card is used for accessing The service network.
  • the receiving module is specifically configured to receive, by using a second network card, the IP address that is allocated by the DHCP service node according to the request, the second network card Used to access the management network.
  • the first network card is located on a host where the second network card is located, and the DHCP proxy node is deployed on a host where the second network card is located.
  • the present application further provides a data center, the data center including at least one computing device, each of the computing devices including a processor and a memory, the at least one processor executing to control a DHCP proxy node, DHCP service node and virtual machine,
  • the DHCP proxy node is configured to receive a request from a service network, obtain an IP address from a DHCP service node according to the request in a management network, and send the IP address to a virtual machine or a physical machine, where the request is used to indicate Assign an IP address to the virtual machine or physical machine.
  • the processor is specifically configured to control, by the DHCP proxy node, the request from the virtual machine or a physical machine by using a first network card, where A network card is used to access the service network.
  • the processor is specifically configured to: control, by the second network card, the DHCP proxy node to receive, by using a second network card, the IP address that is allocated by the DHCP service node according to the request.
  • the second network card is used to access the management network.
  • the first network card is located on a host where the second network card is located, and the DHCP proxy node is deployed on a host where the second network card is located.
  • the present application further provides a computer storage medium, where the computer storage medium can store instructions that, when executed, can implement the first aspect provided by the present application and the various implementation manners in the first aspect. Part or all of the steps of the DHCP message processing method.
  • the storage medium comprises a memory in the computing device of the third aspect.
  • the present application also provides a computer program product comprising instructions for performing the DHCP message processing method of the above aspects when the instructions are run on a computer.
  • the method provided by the present application deploys a DHCP proxy node in a data center, and the DHCP proxy node has a function of freely forwarding a message or a message between a service network and a management network, for example, implementing a service network message through the first network card.
  • the second network card is used to implement the messaging of the management network, thereby solving the problem that the virtual machine or the physical machine cannot realize the automatic configuration of the IP address due to the isolation of the service network and the management network in the cloud platform, and the method implements the IP address.
  • Automatic configuration saves management costs and avoids the administrator's manual configuration of IP addresses to improve connection efficiency.
  • FIG. 1 is a schematic structural diagram of a data center provided by the present application.
  • FIG. 3 is a schematic diagram of a DHCP lease process provided by the present application.
  • FIG. 5 is a schematic diagram of DHCP packet forwarding according to the present application.
  • FIG. 6 is a schematic structural diagram of a DHCP proxy node provided by the present application.
  • FIG. 7 is a schematic structural diagram of a computing device provided by the present application.
  • the data center may be a cloud management platform or a cloud data center, where the data center deploys at least one host (ie, a computing device).
  • a virtual machine or a management node may be deployed on any host of at least one host, and any host of at least one host may not be virtualized, and provided as a physical machine to the user to provide services for the user.
  • a virtual machine and a management node are simultaneously deployed on a host.
  • a virtual machine can be deployed on a host, and no management node is deployed. limit.
  • an area composed of nodes related to each management node and a management node may be referred to as an operation and maintenance management area, and the formed network is a management network; and virtual machines and physical machines related to services are all related to services.
  • the inter-area area may be referred to as a service area, and the formed network is a service network.
  • the management node is used for creation and configuration of a virtual machine and configuration of a physical machine, and the management node includes a computing node and a network node.
  • the management node in this application may include a DHCP service node, configured to allocate an IP address and other parameters to the virtual machine or the physical machine.
  • the management node may not include the DHCP service node, which is not limited in this application.
  • the service area may also include only a virtual machine, that is, only the virtual machine is used to provide services for the user.
  • the host and the physical machine where the virtual machine is located are connected to the service network through the first network card, so that each virtual machine or physical machine communicates through other virtual machines or physical machines in the service network.
  • the host and the physical machine where the virtual machine resides access the management network through the second network card, so that the management node configures the physical machine, creates and configures the virtual machine through the management network.
  • the first network card and the second network card configured on the host implement isolation between the service network and the management network.
  • the isolation means that the management node in the management network can only create and configure virtual machines, and cannot interfere with services. For example, when a virtual machine in a service network performs a service transmission, the management node cannot acquire data transmitted by the service.
  • each virtual machine communicates with each other, and establishes a service network through the first network card, for example, the virtual machine 1 in the host 1, the virtual machine 2 in the host 2, and the physical machine 3 respectively pass
  • the respective first network cards access the service network and implement different service functions in the service network.
  • a DHCP proxy node is also deployed on the host where the virtual machine is located.
  • the DHCP proxy node is a process on the host, and can respectively monitor the first network card and the second network card on the host to communicate with the virtual machine or the physical machine of the service network and the management node in the management network.
  • the DHCP proxy node forwards the packet from the DHCP service node that is monitored by the second network card to the first network card, and forwards the packet to the virtual machine or the physical machine through the first network card, thereby solving the service network and The problem of automatic IP address configuration cannot be achieved by the virtual machine or physical machine caused by the isolation of the management network.
  • the DHCP proxy node only listens to DHCP packets, and other packets are discarded, so that the isolation between the service network and the virtual network is not affected.
  • the listening port of the DHCP proxy node may be adjusted to the port 67, 68 defined by the non-native DHCP protocol.
  • the DHCP proxy node deployed on the host where the virtual machine is located is exemplarily drawn. Further, since the physical machine also has the first network card and the second network card, the DHCP proxy node can also be deployed on the physical machine. This is not a limitation.
  • OpenStack is a free open source software cloud computing platform.
  • OpenStack network services are standard services and typically involve the deployment of several programs across multiple network nodes.
  • the main program of the OpenStack network service is the so-called Neutron server, which is a Python daemon that provides the OpenStack network application programming interface (API) to the tenants of the network service and passes the tenant request to one.
  • the series plugin is processed.
  • the Neutron server (formerly known as Quantum) runs on the processor node to service the networking API and its extensions.
  • the Neutron server can also be used to perform network models and IP addressing for each port.
  • the Neutron server usually includes at least one Neutron plugin.
  • the Neutron plugin runs on the compute nodes to manage and configure the local virtual switch.
  • the function of the network management node may be implemented by using a Neutron server in the OpenStack cloud platform, or may be implemented by other computer programs, which is not limited in this embodiment.
  • the DHCP protocol is used to assign IP addresses and some TCP/IP configuration information or network configuration parameters to network devices.
  • DHCP adopts the client/server communication mode, and the client requests configuration from the server.
  • the server returns the corresponding configuration information such as the IP address assigned by the client to implement dynamic configuration of the IP address and other information.
  • DHCP improves the security, reliability, and simplicity of TCP/IP network settings, avoiding address conflicts in TCP/IP networks, and greatly reducing the burden of managing IP address settings.
  • the client includes a virtual machine or a physical machine in a service area, which is not limited in this application.
  • the service node In the case of the isolation of the service network and the management network, the service node automatically allocates an IP address to the virtual machine or the physical machine.
  • This embodiment provides a method for processing a DHCP message, and the method is applied to a data center.
  • the center includes at least one computing device, each computing device including a processor and a memory, the at least one computing device for operating a DHCP proxy node, a DHCP service node, and a virtual machine,
  • the DHCP proxy node is deployed on a virtual machine or a physical machine in the service area, and the host where the virtual machine is located includes two network cards, a first network card and a second network card, where the first network card is used to access the service network to implement services.
  • the message is sent and received by the network; the second network card is used to access the management network to implement message transmission and reception of the management network, and the DHCP agent node is used to monitor the processes of the first network card and the second network card.
  • the method includes the following steps:
  • Step 201 The DHCP proxy node receives a request from the service network, where the request is used to indicate that an IP address is allocated to the virtual machine or the physical machine.
  • the DHCP proxy node receives the request from a virtual machine or a physical machine by using a first network card, where the first network card is used to access the service network.
  • the request includes a DHCP Discover broadcast message.
  • Step 202 The DHCP proxy node sends the request to the DHCP service node, and obtains an IP address from the DHCP service node according to the request in the management network.
  • the DHCP proxy node sends the request to the DHCP service node by using the second network card, and the DHCP proxy node receives, by using the second network card, the IP address that is allocated by the DHCP service node according to the request.
  • the second network card is used to access the management network.
  • the DHCP service node and the DHCP proxy node have established a communication connection before acquiring the request.
  • Step 203 The DHCP proxy node sends the IP address to the virtual machine or the physical machine.
  • the DHCP proxy node sends the IP address to the virtual machine or the physical machine through the first network card.
  • the first network card is located on a host where the second network card is located, and the DHCP proxy node is deployed on a host where the second network card is located.
  • the IP address can be sent to the virtual machine in the manner of the DHCP Offer message.
  • the DHCP proxy node accesses the service network through the first network card, obtains the request sent by the virtual machine from the service network, and then forwards the request to the DHCP service node through the management network, where the DHCP proxy node passes the
  • the second network card accesses the management network to implement forwarding of request packets from the service network to the management network.
  • the DHCP service node allocates an IP address and sends it to the DHCP proxy node through the management network, after the DHCP proxy node receives the IP address through the second network card, and then The IP address is translated to the service network, and the IP address is forwarded to the virtual machine or the physical machine by using the first network card, thereby realizing forwarding of the IP address from the management network to the service network.
  • a DHCP proxy node is deployed in the data center, and the DHCP proxy node has a free forwarding function between the service network and the management network, for example, the first network card is used to implement the service network.
  • the second network card is used to implement the messaging of the management network, thereby solving the problem that the virtual machine or the physical machine cannot realize the automatic configuration of the IP address due to the isolation of the service network and the management network in the cloud platform.
  • the method implements automatic configuration of an IP address, saves management costs, and avoids an administrator manually configuring an IP address to improve IP address binding efficiency.
  • the physical machine or virtual machine in the service area can obtain the IP address from the DHCP service node (that is, the DHCP server), and can also obtain the subnet mask, the default gateway address, the DNS server address, etc.
  • the above process is called DHCP. Lease process. Because when the virtual machine or physical machine receives the provided IP address, the DHCP service node will lease the IP address to the virtual machine or physical machine for a specified period of time.
  • the DHCP lease process overview can be divided into four steps. Referring to FIG. 3, respectively, the virtual machine or the physical machine requests an IP address—the server response—the virtual machine or the physical machine selects an IP address—the server determines the lease. .
  • a DHCP packet processing method provided in this embodiment is described in detail. The method can be applied to the data center shown in FIG.
  • the data center includes: a network management node deployed in the operation and maintenance management area, at least one DHCP service node, a DHCP proxy node, and a virtual machine or a physical machine.
  • the method includes the following steps:
  • Step 1 The user (administrator or tenant) creates a network, and the network management node receives a request for network creation from the user.
  • Step 2 The network management node creates/starts a DHCP service node on the operation and maintenance management area for the newly created network, and the DHCP service node can automatically allocate the IP address of the network, for example, provide an IP address for the requested VM/PM. .
  • Step 3 The network management node obtains the IP address information of the newly created DHCP service node.
  • Step 4 The network management node creates a DHCP proxy node for the PM/VM in the newly created network.
  • the network management node creates a DHCP proxy node on a physical machine of the service area or a host where the virtual machine of the service area is located.
  • the DHCP proxy node can also be deployed in multiple hosts in the service area in the form of active/standby or cluster. This embodiment does not limit this.
  • Step 5 The network management node configures the DHCP service node, and sends information such as the IP address and port of the newly created DHCP service node to the newly created DHCP proxy node in step 4 or the original node in the service area, so that the DHCP is enabled.
  • the proxy node establishes a communication connection with the IP address assigned by the DHCP service node.
  • the method further includes:
  • Step 6 After receiving the IP address of the DHCP service node, the DHCP proxy node establishes a communication connection with the DHCP service node and tests connectivity with the DHCP service node. If the network connection fails, the process ends, and the data center is terminated. Sends an error alarm message so that the operation and maintenance personnel can intervene to diagnose the fault point.
  • the data center is used to select a DHCP service node and a DHCP proxy node for the virtual machine or the physical machine, and establish a communication connection between the DHCP service node and the DHCP proxy node by using the IP address of the DHCP service node, so that the DHCP proxy is enabled.
  • the node can automatically forward the request to the DHCP service node, and receive the IP address fed back by the DHCP service node, thereby automatically establishing a connection relationship between the DHCP service node and the VM/PM.
  • automatic allocation of IP addresses is achieved, while avoiding modifying the content of the message and populating the IP address of the DHCP service node corresponding to the DHCP proxy section.
  • Step 7 The DHCP proxy node starts DHCP broadcast monitoring on the service network, and is used to listen to all the clients in the range, such as a virtual machine or a physical machine, and broadcast the request message.
  • Step 8 When the user issues a virtual machine or a physical machine, or the IP address of the virtual machine or the physical machine needs to be refreshed, you need to obtain and bind an IP address, that is, broadcast a DHCP Discover request message to the network.
  • the virtual machine or physical machine broadcasts a DHCP Discover packet in the data center to request an IP address.
  • This process is also called DHCP Discover.
  • the source IP address of the DHCP Discover packet is 0.0.0.0; the destination IP address is 255.255.255.255, and the DHCP Discover packet may further include a MAC address and a computer name of the virtual machine or the physical machine to enable the DHCP service node. It is possible to determine which request message is sent by which virtual machine or physical machine.
  • Step 9 After receiving the DHCP Discover request message, the DHCP proxy node copies the packet for forwarding, and converts the packet from the service network to the management network, and does not modify the packet content, and does not fill the DHCP relay field.
  • Step 10 The DHCP proxy node sends the copied DHCP Discover request message to the DHCP service node through the management network.
  • the DHCP proxy node sends the request packet to the DHCP service node in a unicast manner through the management network.
  • Step 11 The DHCP service node receives the DHCP Discover request packet sent by the DHCP proxy node, and then processes the request packet. Specifically, the DHCP request packet is selected from the IP address resource pool according to the information contained in the DHCP Discover request packet. The IP address is fed back to the DHCP proxy node in the form of a DHCP response packet, such as a DHCP Offer message.
  • the DHCP service node when it receives the information of the IP address requested by the client, it searches the IP address pool for a valid IP address to provide to the client. If so, the DHCP service node does the IP address. Mark it and then unicast to send a DHCP Offer packet to the DHCP proxy node (this process is also called DHCP Offer).
  • Step 12 After receiving the DHCP response packet (such as a DHCP Offer message) from the DHCP service node, the DHCP proxy node transfers the packet from the management network to the service network.
  • the DHCP response packet such as a DHCP Offer message
  • Step 13 The DHCP proxy node sends the DHCP Offer message to the physical machine or the virtual machine through the service network.
  • Step 14 The physical machine or the virtual machine extracts an IP address from the DHCP Offer message, and sends a DHCP response message (for example, a DHCP Requst message) to the DHCP proxy node if it is confirmed that the IP address is not occupied; If the IP address is occupied, you need to go back to step 8 to restart the transmission of the DHCP request message.
  • a DHCP response message for example, a DHCP Requst message
  • the physical machine or the virtual machine selects an IP address from the first DHCP Offer message received, and generates a DHCP response message, where the DHCP response message indicates that the IP address in the DHCP response message is available.
  • the DHCP response packet is a DHCP Request message, and the process is also called a DHCP Request.
  • Step 15 The DHCP proxy node receives the DHCP Request message from the physical machine or the virtual machine through the service network, copies the packet for forwarding, and does not modify the content of the packet, nor does it fill the DHCP relay field.
  • Step 16 The DHCP proxy node sends the DHCP Request message to the DHCP service node through the management network.
  • Step 17 The DHCP service node receives the DHCP Request message from the DHCP proxy node, and sends a DHCP ACK message to the DHCP proxy node through the management network.
  • the last step in the DHCP lease process is to confirm the IP lease, also known as DHCP ACK, for the server.
  • the DHCP service node After receiving the DHCP Request, the DHCP service node feeds back to the physical machine or virtual machine in the form of a DHCP ACK (DHCP Acknowledge) message, indicating successful acknowledgment.
  • the DHCP ACK message contains the effective lease of the IP address and other possible configuration information.
  • a physical or virtual machine receives a DHCP ACK, it configures the IP address and completes the TCP/IP initialization so that it can communicate over the TCP/IP network.
  • the DHCP service node that assigns the IP address will mark and retain the IP address, so that the IP address can no longer be provided. Used by other DHCP clients.
  • Step 18 The DHCP proxy node receives the DHCP ACK packet from the DHCP serving node through the management network, and transfers the DHCP ACK packet to the service network after processing.
  • Step 19 The DHCP proxy node sends the DHCP ACK packet to the client through the service network.
  • Step 20 After receiving the DHCP ACK packet, the physical machine or the virtual machine binds the requested IP address.
  • FIG. 5 is a schematic structural diagram of a DHCP proxy node forwarding a DHCP packet according to an embodiment of the present disclosure.
  • DHCP Discover broadcast packet the DHCP Offer packet, the DHCP Request packet, and the DHCP ACK packet are all in the DHCP protocol, and all have clear definitions.
  • the role of each message in the DHCP protocol is defined as follows:
  • DHCP Discover message/package The DHCP client (client) broadcasts this type of packet to the local network when it needs to obtain an IP address.
  • DHCP Offer message/package The DHCP service node (server) replies to the DHCP Discover message sent by the DHCP client, and the DHCP Offer packet contains some configuration parameters, such as an IP address, that the DHCP service node will provide to the client.
  • DHCP Request message/package A packet sent by the DHCP client to the DHCP server under the following conditions:
  • the client requests the configuration information provided in the DHCP Offer sent by a specific service node, and implicitly rejects the DHCP Offer packets of all other servers.
  • the client confirms the correctness of the configuration information previously assigned to itself at some point, such as after a short-lived physical failure of the client's operating system.
  • DHCP ACK message The DHCP service node replies to the DHCP Request packet or DHCP Inform packet sent by the DHCP client, which contains the configuration information assigned by the DHCP service node to the client.
  • the technical solution provided by the application provides a DHCP proxy node on the host, so that the DHCP proxy node can forward the DHCP broadcast obtained from the service network to the DHCP service node through the management network, thereby solving the isolation of the service network and the management network.
  • the resulting virtual machine or physical machine cannot implement the problem of automatic IP address configuration.
  • the method utilizes a DHCP service node to implement centralized allocation of IP addresses requested by the virtual machine, so that the cloud computing platform or the virtualization platform meets the requirements of the current data center, and the requirements of the operation and maintenance management are centralized, thereby enabling the network management node to be managed.
  • the entire data center avoids the deployment of a management platform in each business area, which saves management costs, thereby improving the efficiency of leases, and automating the configuration through IP addresses also allows platform administrators to avoid the pressure of manual operations.
  • FIG. 6 is a schematic structural diagram of a DHCP proxy node according to the present application.
  • the DHCP proxy node is deployed on a server or a computing node or a computing device, and is configured to execute the DHCP packet processing method corresponding to FIG. 2 or FIG. 4 .
  • the DHCP proxy node includes: a receiving module 601, a processing module 602, and a sending module 603.
  • the DHCP proxy node may further include other functional modules or components, such as a storage module.
  • the receiving module 601 is configured to receive a request from a service network, where the request is a DHCP Discover broadcast message.
  • the processing module 602 is configured to convert the request from the service network to the management network.
  • the sending module 603 is configured to send the request to the DHCP service node in a unicast manner.
  • the receiving module 601 is further configured to obtain an IP address from the DHCP service node according to the request in the management network, where the request is used to indicate that the virtual machine or the physical machine is assigned an IP address.
  • the IP address can be obtained by using a DHCP Offer message.
  • the sending module 603 is configured to send the IP address to the virtual machine or the physical machine.
  • the receiving module 601 is specifically configured to receive, by using a first network card, the request from a virtual machine or a physical machine, where the first network card is used for receiving Enter the business network.
  • the receiving module 601 is specifically configured to receive, by using a second network card, the IP address that is allocated by the DHCP service node according to the request, The second network card is used to access the management network.
  • the first network card is located on a host where the second network card is located, and the DHCP proxy node is deployed on a host where the second network card is located.
  • the processing module 602 is specifically configured to transfer the DHCP Offer message from the management network to the service network, and the sending module 603 is specifically configured to pass the first network card. Send the DHCP Offer message to the virtual machine or physical machine.
  • the receiving module 601 is further configured to obtain a DHCP Request message from the virtual machine or a physical machine by using a service network, where the DHCP Request message indicates DHCP.
  • the IP address of the offer packet is available;
  • the processing module 602 is further configured to transfer the DHCP Request message from the service network to the management network;
  • the sending module 603 is further configured to use the second network card to send the DHCP The Request message is sent to the DHCP service node.
  • the receiving module 601 is further configured to receive, by using the management network, a DHCP ACK packet from the DHCP serving node, where the processing module 602 is further configured to: Transmitting the DHCP ACK message from the management network to the service network; the sending module 603 is further configured to send the DHCP ACK message to the virtual machine or the physical machine by using the first network card, so that the The virtual machine or the physical machine binds the IP address after acquiring the DHCP ACK message.
  • the receiving module 601 is further configured to acquire an IP address of the DHCP service node before acquiring the request packet
  • the processing module 602 is further configured to: Establishing a connection with the DHCP service node based on the IP address and testing connectivity with the DHCP service node.
  • the embodiment of the present application further provides a network management node, such as a Neutron component deployed in an OpenStack cloud computing platform.
  • a network management node such as a Neutron component deployed in an OpenStack cloud computing platform.
  • the structure of the network management node may be the same as that of the DHCP proxy node shown in FIG. 6, for example, including: a receiving module. , processing modules and sending modules.
  • the receiving module is configured to acquire a request for network creation from a virtual machine or a physical machine; the processing module is configured to create a DHCP service node for the virtual machine or the physical machine, and determine a DHCP proxy for the virtual machine or the physical machine a node, wherein the DHCP service node is configured to provide an IP address, and the DHCP proxy node is configured to send the IP address to the virtual machine or a physical machine through a management network.
  • the sending module is further configured to send the IP address corresponding to the DHCP service node to the DHCP proxy node, so that the DHCP proxy node establishes a communication connection with the DHCP service node by using the IP address of the DHCP service node.
  • the embodiment of the present application further provides a DHCP service node, which is used to implement automatic allocation of an IP address.
  • the structure of the DHCP service node may be the same as that of the DHCP proxy node shown in FIG. 6, and includes, for example, a receiving module, a processing module, and a sending module.
  • the receiving module is configured to receive a DHCP request from the DHCP proxy node; the processing module is configured to determine an IP address of the virtual machine or the physical machine according to the DHCP request, and the sending module is configured to send the IP address to the DHCP through the management network. Proxy node.
  • the receiving module is further configured to receive a DHCP Request message from a DHCP proxy node, where the DHCP Request message indicates that the DHCP service node allocates The IP address is available; the processing module is further configured to generate an ACK packet and send the ACK packet to the DHCP proxy node by using a sending module.
  • the DHCP proxy node in the embodiments of the present application may also be referred to as a DHCP relay proxy, a DHCP forwarding proxy, a DHCP relay, or a DHCP forwarding node, and may also be other proxy modules for implementing physical Messaging between the on-board business network and the management network.
  • FIG. 7 is a schematic structural diagram of a computing device according to an embodiment of the present disclosure.
  • the computing device includes: a network interface 701, a processor 702, and a memory 703.
  • the processor 702 executes the code in the memory 703 to implement the DHCP proxy node shown in FIG. 6 through the network interface 701, including communication transmission between the DHCP proxy node and the DHCP server, virtual machine or physical machine.
  • the processor 702 may be composed of an integrated circuit (IC), for example, may be composed of a single packaged IC, or may be composed of a plurality of packaged ICs that have the same function or different functions.
  • the processor may include only a CPU, or may be a combination of a GPU, a digital signal processor (DSP), and a control chip (eg, a baseband chip) in the transceiver module.
  • the CPU may be a single computing core or may include multiple computing cores.
  • the memory 703 may include a volatile memory, such as a random access memory (RAM), and may also include a non-volatile memory, such as a flash memory.
  • RAM random access memory
  • non-volatile memory such as a flash memory.
  • the present application further provides a data center, where the data center includes at least one computing device or host, where each computing device or host includes a processor and a memory, and the at least one computing device or host is used for
  • the DHCP proxy node, the DHCP service node, and the virtual machine are executed to implement the DHCP packet processing method described in the foregoing embodiment.
  • the DHCP proxy node is configured to receive a request from a service network, obtain an IP address from a DHCP service node according to the request, and send the IP address to a virtual machine or a physical machine, where the request is The IP address is assigned to the virtual machine or the physical machine.
  • the processor is specifically configured to control, by the DHCP proxy node, the request from the virtual machine by using a first network card, where the first network card is Used to access the service network.
  • the processor is specifically configured to control, by the DHCP proxy node, the IP address that is allocated by the DHCP service node according to the request by using a second network card.
  • An address, the second network card is used to access the management network.
  • the first network card is located on a host where the second network card is located, and the DHCP proxy node is deployed on a host where the second network card is located.
  • the present application further provides a computer storage medium, where the computer storage medium may store a program, and the program may include some or all of the steps in the embodiments of the DHCP message processing method provided by the application.
  • the storage medium may be a magnetic disk, an optical disk, a ROM, a RAM, or the like.
  • the functions of the DHCP proxy node, the DHCP service node, and the virtual machine can be implemented by using a computer program.
  • a computer program product comprising one or more computer instructions, such as forwarding instructions.
  • the computer loads and executes the computer program, the processes or functions described in accordance with the above-described embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the DHCP proxy node receives a request from the service network, the request is for indicating an IP address is assigned to the virtual machine; the IP address is obtained from the DHCP service node according to the request in the management network; and the sending is performed to the virtual machine or the physical machine IP address.
  • the specific implementation includes: the DHCP proxy node receiving the request from the virtual machine or a physical machine by using a first network card, where the first network card is used to access the service network; and the DHCP proxy The node receives, by using the second network card, the IP address that is allocated by the DHCP service node according to the request, and the second network card is used to access the management network.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a network device, computer, server or data center Transfer to another device, computer, or server by wire or wirelessly.
  • the present application further provides a terminal, such as a user equipment, a physical machine, or a virtual machine, for implementing the method of sending a DHCP request message in the foregoing embodiment, and sending a DHCP request message and an ACK message.
  • a terminal such as a user equipment, a physical machine, or a virtual machine, for implementing the method of sending a DHCP request message in the foregoing embodiment, and sending a DHCP request message and an ACK message.
  • the terminal may include a control node, a processor, and a memory
  • the control node may include components such as a receiver, a transmitter, and an antenna.
  • the terminal may also include more or less components, or a combination of certain components, or different component arrangements, which is not limited in this application.
  • the control node is configured to broadcast a DHCP request message, such as a DHCP Discover broadcast message, for requesting an IP address from the server.
  • a DHCP request message such as a DHCP Discover broadcast message
  • the control node is further configured to receive a DHCP response message from the DHCP proxy node, where the DHCP response message may be a DHCP Offer message, and the DHCP Offer message carries an IP address;
  • the processor is configured to: Extracting an IP address from the DHCP response message, and sending a DHCP response message to the DHCP proxy node by using the control node, if the IP address is not occupied; wherein the DHCP response message may be DHCP Requst message.
  • the terminal needs to resend the DHCP Discover broadcast message to the DHCP proxy node to re-request to obtain a new IP address.
  • control node is further configured to receive a DHCP ACK sent by a DHCP proxy node, where the DHCP ACK is a DHCP service node according to the DHCP Requst report.
  • the IP address generated and sent to mark the IP address assigned to the client can no longer be used by other devices.
  • the processor is further configured to bind the IP address after receiving the DHCP ACK message.
  • a program instruction is stored in the memory, and when the program instruction is executed, the method for sending and receiving the respective DHCP messages by the client or the terminal, and binding the acquired IP address may be implemented.
  • the memory may include a volatile memory such as a RAM; and may further include a nonvolatile memory such as a flash memory, a hard disk HDD or an SSD; the memory may further include a combination of the above types of memories.
  • the processor may be a CPU, or a combination of a CPU and an NP.
  • the processor may further include a hardware chip.
  • the hardware chip may be an ASIC, a programmable logic device (PLD), or a combination thereof.
  • PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • the techniques in the embodiments of the present invention can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution in the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM. , a disk, an optical disk, etc., including instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention or portions of the embodiments.
  • a computer device which may be a personal computer, server, or network device, etc.

Abstract

发明公开了一种动态主机配置协议DHCP报文处理方法及装置，所述方法包括:DHCP代理节点从业务网络接收请求，所述请求用于为虚拟机或物理机分配IP地址；所述DHCP代理节点在管理网络中根据所述请求从DHCP服务节点获取IP地址；所述DHCP代理节点向所述虚拟机或物理机发送获取的所述IP地址。本方法通过在数据中心中部署DHCP代理节点，该DHCP代理节点具有将消息或报文在业务网络和管理网络之间的自由转发功能，从而实现了IP地址的自动配置，节约管理成本，并且还避免了管理员手工配置IP地址的操作，提高连接效率。

Description

一种DHCP报文处理方法及装置 技术领域
本申请涉及网络通信技术领域，尤其涉及一种DHCP报文处理方法及装置。
背景技术
在数据中心构建过程中，通常会设置至少一个独立的业务区和一个集中的运维管理区。其中，业务区用于部署各种类型的业务系统，而运维管理区用于部署各种软硬件系统的管理和运维平台，并且与业务网络隔离。
具体地，在运维管理区中部署有各种管理节点，在各个业务区部署有用于各类业务系统的虚拟机或者物理机。其中，部署在运维管理区中的各个管理节点用于为业务区的虚拟机或者物理机提供管理和运维平台。
为实现业务区中虚拟机或物理机的网络互联协议(Internet Protocol，IP)地址的统一管理，通常将用于分配IP地址的动态主机配置协议(Dynamic Host Configuration Protocol，DHCP)服务节点部署在运维管理区。当管理员在某个业务区发放一台虚拟机或物理机时，虚拟机或物理机需要通过业务网络发送DHCP请求来获取IP地址。所述DHCP是一种二层网络协议，业务区的业务网络和运维管理区的管理网络二层不通，导致DHCP广播不能从业务区的虚拟机或物理机发送到运维管理区的DHCP服务节点，进而导致虚拟机或物理机无法利用DHCP广播自动配置IP地址。
发明内容
本申请通过部署一个DHCP代理节点，使得该DHCP代理节点可以将从业务网络上获取的DHCP广播，通过管理网络转发到位于管理节点上的DHCP服务节点，以解决了因业务网络和管理网络的隔离导致的虚拟机或物理机无法实现IP地址自动配置的问题。
具体地，本申请公开了以下技术方案：
第一方面，本申请提供了一种动态主机配置协议DHCP报文处理方法，所述方法包括:DHCP代理节点从业务网络接收请求,所述请求用于指示为虚拟机或物理机分配IP地址；所述DHCP代理节点将所述请求发送给DHCP服务节点，在管理网络中根据所述请求从DHCP服务节点获取IP地址；以及向所述虚拟机或物理机发送所述IP地址。
可选的，所述请求包括DHCP协议中的DHCP Discover广播报文。
可选的，所述IP地址可以通过DHCP协议中的DHCP Offer报文承载。
本方面，通过配置DHCP代理节点可以实现管理网络和业务网络之间的消息转发，进而为虚拟机或物理机自动分配IP地址。
结合第一方面，在第一方面的一种实现方式中，所述DHCP代理节点从业务网络接收请求包括：所述DHCP代理节点通过第一网卡接收来自所述虚拟机或物理机的所述请求，所述第一网卡用于接入所述业务网络，以实现所述请求在业务网络中的接收和发送。
结合第一方面，在第一方面的另一种实现方式中，所述DHCP代理节点在管理网络中根据所述请求从DHCP服务节点获取IP地址，包括：所述DHCP代理节点通过第二网卡接收所述DHCP服务节点根据所述请求分配的所述IP地址，所述第二网卡用于接入所述管理网络，以实现所述IP地址在管理网络中的接收和发送。
结合第一方面，在第一方面的又一种实现方式中，所述第一网卡位于所述第二网卡所在的主机上，所述DHCP代理节点部署于所述第二网卡所在的主机。
第二方面，本申请还提供了一种DHCP代理节点，包括接收模块和发送模块，其中，所述接收模块，用于从业务网络接收请求,以及在管理网络中根据所述请求从DHCP服务节点获取IP地址，所述请求用于指示为虚拟机或物理机分配IP地址；所述发送模块，用于向所述虚拟机或物理机发送所述IP地址。
结合第二方面，在第二方面的一种实现方式中，所述接收模块具体用于通过第一网卡接收来自所述虚拟机或物理机的所述请求，所述第一网卡用于接入所述业务网络。
结合第二方面，在第二方面的另一种实现方式中，所述接收模块具体用于通过第二网卡接收所述DHCP服务节点根据所述请求分配的所述IP地址，所述第二网卡用于接入所述管理网络。
结合第二方面，在第二方面的又一种实现方式中，所述第一网卡位于所述第二网卡所在的主机上，所述DHCP代理节点部署于所述第二网卡所在的主机。
第三方面，本申请还提供了一种数据中心，所述数据中心包括至少一个计算设备，每个所述计算设备包括处理器和存储器，所述至少一个处理器执行用于控制DHCP代理节点、DHCP服务节点和虚拟机，
所述DHCP代理节点，用于从业务网络接收请求,在管理网络中根据所述请求从DHCP服务节点获取IP地址，以及向虚拟机或物理机发送所述IP地址，其中所述请求用于指示为所述虚拟机或物理机分配IP地址。
结合第三方面，在第三方面的一种实现方式中，所述处理器具体用于控制所述DHCP代理节点通过第一网卡接收来自所述虚拟机或物理机的所述请求，所述第一网卡用于接入所述业务网络。
结合第三方面，在第三方面的另一种实现方式中，所述处理器具体用于控制所述DHCP代理节点通过第二网卡接收所述DHCP服务节点根据所述请求分配的所述IP地址，所述第二网卡用于接入所述管理网络。
结合第三方面，在第三方面的又一种实现方式中，所述第一网卡位于所述第二网卡所在的主机上，所述DHCP代理节点部署于所述第二网卡所在的主机。
第四方面，本申请还提供了一种计算机存储介质，该计算机存储介质可存储有指令，该指令执行时可实现本申请提供的第一方面以及第一方面中的各种实现方式所述的DHCP报文处理方法的部分或全部步骤。
其中，所述存储介质包括第三方面中的所述计算设备中的存储器。
第五方面，本申请还提供了一种包含指令的计算机程序产品，当所述指令在计算机上运行时，所述计算机执行上述各个方面所述的DHCP报文处理方法。
本申请提供的方法，在数据中心中部署DHCP代理节点，该DHCP代理节点具有将消息或报文在业务网络和管理网络之间的自由转发功能，比如通过第一网卡实现业 务网络的消息收发，通过第二网卡实现管理网络的消息收发，从而解决了在云平台中，因业务网络和管理网络的隔离导致的虚拟机或物理机无法实现IP地址自动配置的问题，本方法实现了IP地址的自动配置，节约管理成本，并且还避免了管理员手工配置IP地址的操作，提高连接效率。
附图说明
为了更清楚地说明本申请的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，对于本领域普通技术人员而言，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本申请提供的一种数据中心的结构示意图；
图2为本申请提供的一种DHCP报文处理方法的流程图；
图3为本申请提供的一种DHCP租约过程的示意图；
图4为本申请提供的另一种DHCP报文处理方法的流程图；
图5为本申请提供的一种DHCP报文转发的示意图；
图6为本申请提供的一种DHCP代理节点的结构示意图；
图7为本申请提供的一种计算设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本申请实施例中的技术方案，并使本申请实施例的上述目的、特征和优点能够更加明显易懂，下面结合附图对本申请实施例中的技术方案作进一步详细的说明。
首先，对本申请的技术场景和系统下的各个功能实体，以及技术术语进行介绍和说明。
如图1所示，为本申请实施例提供的一种数据中心结构示意图，该数据中心可以是一种云管理平台或云数据中心，其中，所述数据中心部署至少一个主机(即计算设备)，至少一个主机的任一主机上可以部署虚拟机或管理节点，同时至少一个主机的任一主机也可以不进行虚拟化，作为物理机提供给用户，为用户提供服务。示例性地，图1中绘制出了一个主机上同时部署虚拟机和管理节点的情况，除此之外，一个主机上可以只部署虚拟机，不部署管理节点，本申请实施例对此不做限制。
如图1所示的数据中心，各个管理节点与管理节点相关的节点组成的区域可以称为运维管理区，其形成的网络为管理网络；将所有业务与业务相关的虚拟机及物理机之间组成的区域可以称为业务区，其形成的网络为业务网络。在运维管理区，管理节点用于虚拟机的创建和配置及物理机的配置，所述管理节点包括计算节点、网络节点。
可选的，本申请中的管理节点可以包括DHCP服务节点，用于为虚拟机或物理机分配IP地址以及其他参数。所述管理节点还可以不包括所述DHCP服务节点，本申请对此不予限制。
此外，业务区也可以只包含虚拟机，即只利用虚拟机为用户提供服务，本申请实施例对此不做限制。
虚拟机所在主机和物理机通过第一网卡接入业务网络，使得每个虚拟机或物理机通过业务网络其它虚拟机或物理机通信。同时，虚拟机所在主机和物理机通过第二网卡接入管理网络，使得管理节点通过管理网络配置物理机、创建和配置虚拟机。主机 上配置的第一网卡和第二网卡实现业务网络和管理网络的隔离。所述隔离是指管理网络中的管理节点只能对虚拟机进行创建和配置操作，不能对业务进行干预。例如在业务网络中的虚拟机在进行业务传输时，管理节点不能获取业务传输的数据。
如图1所示，在业务区，各个虚拟机之间相互通信，并通过第一网卡建立业务网络，例如主机1中的虚拟机1、主机2中的虚拟机2和物理机3中分别通过各自的第一网卡接入到业务网络，并在该业务网络中实现不同的业务功能。
虚拟机所在的主机上还部署有DHCP代理节点。该DHCP代理节点为主机上的一个进程，可以对主机上的第一网卡和第二网卡实现分别监听，从而与业务网络的虚拟机或物理机及管理网络中的管理节点通信。该DHCP代理节点将从第二网卡中监听到的来自DHCP服务节点的报文转发至第一网卡，又通过第一网卡将该报文转发至虚拟机或物理机，从而解决了因业务网络和管理网络的隔离导致的虚拟机或物理机无法实现IP地址自动配置的问题。DHCP代理节点只监听DHCP报文，其他报文丢弃，从而不影响业务网络和虚拟网络的隔离。
进一步地，为了避免与管理网络内部的DHCP请求相干扰，可将该DHCP代理节点的监听端口调整为非原生DHCP协议制定的67,68端口。图1中，示例性地绘制出部署在虚拟机所在主机的DHCP代理节点，进一步地，由于物理机同样具有第一网卡和第二网卡，所以DHCP代理节点也可以部署在物理机上，本申请对此不做限制。
可选的，本申请提供的技术方案可以应用于OpenStack云平台，其中，OpenStack是一个免费的开源软件云计算平台。OpenStack网络业务是标准业务，通常涉及若干个程序在多个网络节点中的部署。OpenStack网络业务的主要程序是所谓的Neutron服务器，所述Neutron服务器是一种Python后台程序，将OpenStack网络应用编程接口(application programming interface，API)提供给网络业务的租户，并将租户请求传递给一系列插件进行处理。
Neutron服务器(原来称为Quantum)在处理器节点上运行，以服务组网API及其拓展。Neutron服务器也可以用于执行网络模型以及每个端口的IP寻址。Neutron服务器通常包括至少一个Neutron插件。通常Neutron插件在计算节点上运行，以管理和配置本地虚拟交换机。
可选的，本实施例中，网络管理节点的功能可以通过OpenStack云平台中的Neutron服务器来实现，或者还可以通过其它计算机程序实现，本实施例对此不进行限制。
DHCP协议用于向网络设备分配IP地址及一些TCP/IP配置信息或网络配置参数。DHCP采用客户端/服务器通信模式，由客户端向服务器提出配置申请，服务器返回客户端分配的IP地址等相应的配置信息，以实现IP地址等信息的动态配置。DHCP提高安全、可靠且简单的TCP/IP网络设置，避免了TCP/IP网络中地址的冲突，同时也大大降低了管理IP地址设置的负担。
其中，本申请各实施例中，所述客户端包括业务区的虚拟机或者物理机，本申请对此不予限定。
为了实现在业务网络和管理网络的隔离的情况下，服务节点向虚拟机或物理机自动分配IP地址，本实施例提供了一种DHCP报文处理方法，该方法应用于数据中心，所述数据中心包括至少一个计算设备，每个计算设备包括处理器和存储器，所述至少 一个计算设备用于运行DHCP代理节点、DHCP服务节点和虚拟机，
其中，所述DHCP代理节点部署在业务区的虚拟机或物理机上，虚拟机所在的主机包括两个网卡，第一网卡和第二网卡，所述第一网卡用于接入业务网络，实现业务网络的消息收发；所述第二网卡用于接入管理网络，实现管理网络的消息收发，所述DHCP代理节点用于监听第一网卡和第二网卡的进程。
参加图2，所述方法包括以下步骤：
步骤201：DHCP代理节点从业务网络接收请求，所述请求用于指示为虚拟机或物理机分配IP地址；
具体地，所述DHCP代理节点通过第一网卡接收来自虚拟机或物理机的所述请求，所述第一网卡用于接入所述业务网络。
其中，所述请求包括DHCP Discover广播报文。
步骤202：DHCP代理节点将所述请求发送给DHCP服务节点，在管理网络中根据所述请求从DHCP服务节点获取IP地址；
具体地，所述DHCP代理节点通过第二网卡将所述请求发送给DHCP服务节点，以及所述DHCP代理节点通过第二网卡接收所述DHCP服务节点根据所述请求分配的所述IP地址，所述第二网卡用于接入所述管理网络。
所述DHCP服务节点与DHCP代理节点在获取请求之前已经建立了通信连接。
步骤203：DHCP代理节点向所述虚拟机或物理机发送所述IP地址。
具体地，所述DHCP代理节点通过第一网卡将所述IP地址发送给虚拟机或物理机。
其中，所述第一网卡位于所述第二网卡所在的主机上，所述DHCP代理节点部署于所述第二网卡所在的主机。
可选的，所述IP地址可以以DHCP Offer报文携带的方式发送给虚拟机。
本实施例中，DHCP代理节点通过第一网卡接入业务网络，从业务网络中获取虚拟机发送的请求，然后将该请求通过管理网络转发给DHCP服务节点，其中，所述DHCP代理节点通过第二网卡接入管理网络，实现请求报文从业务网络到管理网络之间的转发。
同理地，当DHCP服务节点接收到来自DHCP代理节点转发的请求之后，分配IP地址，并通过管理网络发送给DHCP代理节点，所述DHCP代理节点通过第二网卡接收该IP地址之后，再将该IP地址转换到业务网络，并通过第一网卡将该IP地址转发给所述虚拟机或物理机，从而实现了IP地址从管理网络到业务网络之间的转发。
本实施例提供的方法，在数据中心中部署DHCP代理节点，该DHCP代理节点具有将消息或报文在业务网络和管理网络之间的自由转发功能，比如通过第一网卡实现业务网络的消息收发，通过第二网卡实现管理网络的消息收发，从而解决了在云平台中，因业务网络和管理网络的隔离导致的虚拟机或物理机无法实现IP地址自动配置的问题。
本方法实现了IP地址的自动配置，节约管理成本，并且还避免了管理员手工配置IP地址的操作，提高了IP地址绑定效率。
此外，业务区的物理机或者虚拟机除了可以从DHCP服务节点(即DHCP Server)获得IP地址外，还可以获得子网掩码、默认网关地址、DNS服务器地址等信息，以上 这个过程称为DHCP租约过程。因为当虚拟机或者物理机接收提供的IP地址时，DHCP服务节点将会把IP地址租用给虚拟机或者物理机一段指定的时间。
进一步地，所述DHCP租约过程概况地可以分为4个步骤，参见图3分别为：虚拟机或者物理机请求IP地址——服务器响应——虚拟机或者物理机选择IP地址——服务器确定租约。
基于图3所示的DHCP租约过程，对本实施例提供的一种DHCP报文处理方法进行详细的介绍，该方法可以应用于图1所示的数据中心。
所述数据中心包括：部署在运维管理区的网络管理节点，至少一个DHCP服务节点，DHCP代理节点和虚拟机或物理机。
具体地，如图4所示，所述方法包括以下步骤：
步骤1：用户(管理员或者租户)创建一个网络，网络管理节点接收来自用户的网络创建的请求。
步骤2：网络管理节点为新创建的网络在运维管理区上创建/启动一个DHCP服务节点，该DHCP服务节点可服务于该网络的IP地址自动分配，例如为请求的VM/PM提供IP地址。
步骤3：网络管理节点获取新创建的DHCP服务节点的IP地址信息。
步骤4：网络管理节点在新创建的网络中为所述PM/VM创建一个DHCP代理节点。
具体地，若业务区不具有DHCP代理节点，则网络管理节点在该业务区的一个物理机或该业务区的虚拟机所在的主机上创建一个DHCP代理节点。DHCP代理节点还可以以主备或者集群的形式部署在业务区的多个主机，本实施例对此不做限制。
步骤5：网络管理节点配置DHCP服务节点，将新创建的DHCP服务节点的IP地址、端口等信息发送给步骤4中新创建的DHCP代理节点或该业务区原有的节点，以使所述DHCP代理节点利用所述DHCP服务节点分配的IP地址与其建立通信连接。
可选的，所述方法还包括：
步骤6：DHCP代理节点接收到所述DHCP服务节点的IP地址之后，与DHCP服务节点建立通信连接，并测试其与DHCP服务节点的连通性，如果网络连接不通，则流程结束，以及向数据中心发送出错的告警信息，以便运维人员可以介入诊断故障点。
本实施例中，利用数据中心为虚拟机或物理机选择服务的DHCP服务节点和DHCP代理节点，并通过DHCP服务节点的IP地址建立DHCP服务节点和DHCP代理节点之间的通信连接，使得DHCP代理节点在获取来自VM/PM的请求之后，就可以将该请求自动转发给DHCP服务节点，并接收所述DHCP服务节点反馈的IP地址，从而自动地建立起DHCP服务节点与VM/PM的连接关系，从而实现IP地址的自动分配，同时避免修改报文内容和填充DHCP代理节所对应的DHCP服务节点的IP地址。
步骤7：DHCP代理节点在业务网络启动DHCP广播监听，用于监听其所在范围内所有客户端，例如虚拟机或物理机，广播的请求报文。
步骤8：当用户发放一个虚拟机或者物理机，或虚拟机或者物理机的IP地址需要刷新时，则需要获取并绑定一个IP地址，即向网络广播DHCP Discover请求报文。
具体地，虚拟机或物理机在数据中心广播一个DHCP Discover包以请求IP地址， 此过程也称为DHCP Discover。可选的，所述DHCP Discover包的源IP地址为0.0.0.0；目的IP地址为255.255.255.255，该DHCP Discover包还可以包含虚拟机或物理机的MAC地址和计算机名，以使DHCP服务节点能够确定是由哪个虚拟机或物理机发送的请求报文。
步骤9：DHCP代理节点收到DHCP Discover请求报文后，拷贝该报文以备转发，将所述报文从业务网络转换为管理网络，并且不修改报文内容，也不填充DHCP relay字段。
步骤10：DHCP代理节点通过管理网络将所述拷贝的DHCP Discover请求报文发送给DHCP服务节点。
可选的，所述DHCP代理节点通过管理网络将所述请求报文以单播的形式发送给DHCP服务节点。
步骤11：DHCP服务节点接收来自DHCP代理节点发送的DHCP Discover请求报文，然后对该请求报文进行处理，具体地，根据DHCP Discover请求报文中包含的信息从IP地址资源池中选取合适的IP地址，并以DHCP响应报文，例如DHCP Offer报文的方式反馈给所述DHCP代理节点。
具体地，当DHCP服务节点接收到客户端请求IP地址的信息时，就在自己的IP地址库中查找是否有合法的IP地址提供给客户端，如果有，DHCP服务节点就将此IP地址做上标记，然后单播发送一个DHCP Offer包给DHCP代理节点(此过程又称DHCP Offer)。
步骤12：DHCP代理节点通过业务网络接收到来自DHCP服务节点的DHCP响应报文(比如DHCP Offer报文)后，将所述报文从管理网络转移到业务网络。
步骤13：DHCP代理节点通过业务网络将所述DHCP Offer报文发送给物理机或虚拟机。
步骤14：所述物理机或虚拟机从DHCP Offer报文中提取IP地址，并且在确认该IP地址没有被占用的情况下发送DHCP应答报文(例如DHCP Requst报文)到DHCP代理节点；如果该IP地址被占用，则需要回到步骤8重新开始DHCP请求报文的发送。
具体地，物理机或虚拟机从收到的第一个DHCP Offer报文中选择IP地址，并生成DHCP应答报文，所述DHCP应答报文表示所述DHCP响应报文中的IP地址可用。可选的，所述DHCP应答报文为DHCP Request报文，此过程也称为DHCP Request。
步骤15：DHCP代理节点通过业务网络接收来自物理机或虚拟机的DHCP Request报文，拷贝该报文以备转发，并且不修改该报文内容，也不填充DHCP relay字段。
步骤16：DHCP代理节点将DHCP Request报文通过管理网络发送到DHCP服务节点。
步骤17：DHCP服务节点接收来自DHCP代理节点的DHCP Request报文，并通过管理网络发送DHCP ACK报文给所述DHCP代理节点。
具体地，DHCP租约过程中的最后一步为服务器确认IP租约，也称为DHCP ACK。DHCP服务节点在接收到DHCP Request后，以DHCP ACK(DHCP Acknowledge)消息的形式反馈给物理机或虚拟机，表示成功确认，该DHCP ACK消息中包含IP地址的有效租约和其他可能配置的信息。当物理机或虚拟机收到DHCP ACK时，它就配置 了IP地址，完成了TCP/IP的初始化，从而可以在TCP/IP网络上通信了。
另外，如果物理机或虚拟机接受了DHCP服务节点分配的IP地址，发送了DHCP Request报文，则分配该IP地址的DHCP服务节点会将该IP地址标记和保留，使得该IP地址不能再提供给其它DHCP客户端使用。
步骤18：DHCP代理节点通过管理网络接收来自DHCP服务节点的DHCP ACK报文，处理后将该DHCP ACK报文转移到业务网络。
步骤19：DHCP代理节点将所述DHCP ACK报文通过业务网络发送给客户端。
步骤20：物理机或虚拟机接收到所述DHCP ACK报文后，对请求的IP地址进行绑定。
流程结束。
参见图5，为本实施例提供的一种DHCP代理节点转发DHCP报文的结构示意图。
需要说明的是，本实施例中所述的DHCP Discover广播报文、DHCP Offer报文、DHCP Request报文以及DHCP ACK报文均为在DHCP协议中的报文，且都具有明确的定义，具体地，DHCP协议中对各报文的作用定义如下：
DHCP Discover报文/包:DHCP客户端(client)在需要获取IP地址时，向本地网络广播此类型的包。
DHCP Offer报文/包:DHCP服务节点(server)回复DHCP客户端发出的DHCP Discover报文，且DHCP Offer包里包含了DHCP服务节点将要提供给客户端的一些配置参数，例如IP地址。
DHCP Request报文/包:DHCP客户端在以下情况下发送给DHCP服务器的包：
(a)客户端请求一个特定的服务节点发送的DHCP Offer中提供的配置信息，同时暗示的拒绝其他所有服务器的DHCP Offer包。
(b)客户端在某些时候确认之前分配给自己的配置信息的正确性，比如客户端的操作系统重启后，短暂的线路物理故障后。
(c)客户端延续其已经获得的明确的IP地址的租期。
DHCP ACK报文:DHCP服务节点回复DHCP客户端发送的DHCP Request包或者DHCP Inform包，里面包含了DHCP服务节点分配给客户端的配置信息。
本申请提供的技术方案，在主机上部署DHCP代理节点，使得该DHCP代理节点可以将从业务网络上获取的DHCP广播通过管理网络转发到DHCP服务节点，以解决了因业务网络和管理网络的隔离导致的虚拟机或物理机无法实现IP地址自动配置的问题。
此外，本方法利用DHCP服务节点实现了对虚拟机请求的IP地址进行集中分配，使得云计算平台或者虚拟化平台满足当前数据中心的要求，运维管理集中的要求，进而使得网络管理节点可以统管整个数据中心，避免了在每个业务区都部署一套管理平台，节约了管理成本，进而提高了租约效率，并且通过IP地址自动化配置也使得平台管理员避免了手工操作的压力。
参见图6，为本申请DHCP代理节点的结构示意图，所述DHCP代理节点部署在服务器或者计算节点或计算设备上，用于执行图2或图4对应的DHCP报文处理方法。
如图6所示，该DHCP代理节点包括：接收模块601、处理模块602和发送模块 603，此外，该DHCP代理节点还可以包括其它功能模块或部件，例如存储模块等。
其中，接收模块601，用于从业务网络接收请求，所述请求为DHCP Discover广播报文。
处理模块602，用于将所述请求从业务网络转换到管理网络。
发送模块603，用于将所述请求以单播的形式发送给DHCP服务节点。
接收模块601，还用于在管理网络中根据所述请求从DHCP服务节点获取IP地址，所述请求用于指示为虚拟机或物理机分配IP地址。其中，所述IP地址可以通过DHCP Offer报文的方式获得。
发送模块603，用于向所述虚拟机或物理机发送所述IP地址。
可选的，在本实施例的一种具体的实现方式中，所述接收模块601，具体用于通过第一网卡接收来自虚拟机或物理机的所述请求，所述第一网卡用于接入所述业务网络。
可选的，在本实施例的另一种具体的实现方式中，所述接收模块601，具体用于通过第二网卡接收所述DHCP服务节点根据所述请求分配的所述IP地址，所述第二网卡用于接入所述管理网络。
其中，所述第一网卡位于所述第二网卡所在的主机上，所述DHCP代理节点部署于所述第二网卡所在的主机。
可选的，在本实施例的一种具体的实现方式中，处理模块602，具体用于将所述DHCP Offer报文从管理网络转移到业务网络；发送模块603，具体用于通过第一网卡将DHCP Offer报文发送给虚拟机或物理机。
可选的，在本实施例的一种具体的实现方式中，接收模块601，还用于通过业务网络获取来自所述虚拟机或物理机的DHCP Request报文，所述DHCP Request报文表示DHCP Offer报文中的IP地址可用；处理模块602，还用于将所述DHCP Request报文从所述业务网络转移到所述管理网络；发送模块603，还用于通过第二网卡将所述DHCP Request报文发送给DHCP服务节点。
可选的，在本实施例的又一种具体的实现方式中，接收模块601，还用于通过所述管理网络接收来自所述DHCP服务节点的DHCP ACK报文；处理模块602，还用于将所述DHCP ACK报文从所述管理网络转移到所述业务网络；发送模块603，还用于通过第一网卡将所述DHCP ACK报文发送给所述虚拟机或物理机，以使所述虚拟机或物理机在获取所述DHCP ACK报文后绑定所述IP地址。
可选的，在本实施例的又一种具体的实现方式中，接收模块601，还用于在获取来请求报文之前，获取所述DHCP服务节点的IP地址；处理模块602，还用于根据所述IP地址与所述DHCP服务节点建立连接，并测试与所述DHCP服务节点之间的连通性。
此外，本申请实施例还提供一种网络管理节点，例如部署在OpenStack云计算平台中的Neutron组件，该网络管理节点的结构可以与图6所示的DHCP代理节点结构相同，例如包括：接收模块、处理模块和发送模块等。
所述接收模块用于获取来自虚拟机或物理机的网络创建的请求；处理模块用于为所述虚拟机或物理机创建一个DHCP服务节点，以及为所述虚拟机或物理机确定一个 DHCP代理节点，其中，所述DHCP服务节点用于提供IP地址，所述DHCP代理节点用于将所述IP地址通过管理网络发送给所述虚拟机或物理机。
可选的，所述发送模块还用于将所述DHCP服务节点对应的IP地址发送给DHCP代理节点，以使所述DHCP代理节点利用所述DHCP服务节点的IP地址与其建立通信连接。
另外，本申请实施例还提供一种DHCP服务节点，用于实现IP地址的自动分配。
可选的，该DHCP服务节点的结构可以与图6所示的DHCP代理节点结构相同，例如包括：接收模块、处理模块和发送模块等。
具体地，接收模块用于接收来自DHCP代理节点的DHCP请求；处理模块用于根据所述DHCP请求确定虚拟机或物理机的IP地址，发送模块用于将所述IP地址通过管理网络发送给DHCP代理节点。
可选的，在本实施例的又一种具体的实现方式中，所述接收模块还用于接收来自DHCP代理节点的DHCP Request报文，所述DHCP Request报文表示所述DHCP服务节点分配的IP地址可用；所述处理模块还用于生成ACK报文并通过发送模块将该ACK报文发送给DHCP代理节点。
需要说明的是，本申请各实施例中所述DHCP代理节点还可以称为DHCP中继代理，DHCP转发代理，DHCP中继，或DHCP转发节点等，还可以是其它代理模块，用于实现物理机上业务网络和管理网络之间的消息收发。
图7为本申请实施例提供的一种计算设备的结构示意图，该计算设备包括：网络接口701、处理器702和存储器703。处理器702执行存储器703中的代码，通过网络接口701来实现图6所示的DHCP代理节点，包括DHCP代理节点与DHCP服务器、虚拟机或物理机之间的通信传输。
进一步地，所述处理器702可以由集成电路(integrated circuit，IC)组成，例如可以由单颗封装的IC所组成，也可以由连接多颗相同功能或不同功能的封装IC而组成。举例来说，处理器可以仅包括CPU，也可以是GPU、数字信号处理器(digital signal processor，DSP)、及收发模块中的控制芯片(例如基带芯片)的组合。在本申请的各种实施方式中，CPU可以是单运算核心，也可以包括多运算核心。
所述存储器703可以包括易失性存储器(volatile memory)，例如随机存取内存(random access memory，RAM)；还可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；所述存储器还可以包括上述种类的存储器的组合。
在具体实现层面，本申请还提供了一种数据中心，所述数据中心包括至少一个计算设备或主机，每个计算设备或者主机中包括处理器和存储器，所述至少一个计算设备或者主机用于运行DHCP代理节点、DHCP服务节点和虚拟机，以实现前述实施例中所述的DHCP报文处理方法。
具体地，所述DHCP代理节点用于从业务网络接收请求,在管理网络中根据所述请求从DHCP服务节点获取IP地址，以及向虚拟机或物理机发送所述IP地址，其中所述请求用于指示为所述虚拟机或物理机分配IP地址。
可选的，在本实施例的一种具体的实现方式中，所述处理器具体用于控制所述 DHCP代理节点通过第一网卡接收来自所述虚拟机的所述请求，所述第一网卡用于接入所述业务网络。
可选的，在本实施例的又一种具体的实现方式中，所述处理器具体用于控制所述DHCP代理节点通过第二网卡接收所述DHCP服务节点根据所述请求分配的所述IP地址，所述第二网卡用于接入所述管理网络。
其中，所述第一网卡位于所述第二网卡所在的主机上，所述DHCP代理节点部署于所述第二网卡所在的主机。
具体实现中，本申请还提供一种计算机存储介质，其中，该计算机存储介质可存储有程序，该程序执行时可包括本申请提供的DHCP报文处理方法的各实施例中的部分或全部步骤。所述的存储介质可为磁碟、光盘、ROM或RAM等。
其中，所述DHCP代理节点、DHCP服务节点、虚拟机的所有功能都可以通过计算机程序来实现。
另外，本实施例中，还提供一种计算机程序产品，该计算机程序产品包括一个或多个计算机指令，例如转发指令等。在计算机加载和执行所述计算机程序时，全部或部分地产生按照本申请上述实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络或者其他可编程装置。
具体地，所述计算机执行所述计算机程序时，可实现以下功能：
DHCP代理节点从业务网络接收请求,所述请求用于指示为虚拟机分配IP地址；在管理网络中根据所述请求从DHCP服务节点获取IP地址；以及向所述虚拟机或物理机发送所述IP地址。
此外，具体地实现包括，所述DHCP代理节点通过第一网卡接收来自所述虚拟机或物理机的所述请求，所述第一网卡用于接入所述业务网络；以及，所述DHCP代理节点通过第二网卡接收所述DHCP服务节点根据所述请求分配的所述IP地址，所述第二网卡用于接入所述管理网络。
所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网络设备、计算机、服务器或数据中心通过有线或无线方式向另一个设备、计算机或服务器进行传输。
本申请还提供了一种终端，例如用户设备、物理机或者虚拟机，用于实现前述实施例中的DHCP请求报文的发送，以及DHCP request报文、ACK报文的发送等方法步骤。
具体地，所述终端可以包括控制节点、处理器和存储器，所述控制节点可以包括接收机、发射机与天线等部件。所述终端还可以包括更多或更少的部件，或者组合某些部件，或者不同的部件布置，本申请对此不进行限定。
其中，所述控制节点，用于向广播DHCP请求报文，例如DHCP Discover广播报文，用于向服务器请求IP地址；
所述控制节点，还用于接收来自DHCP代理节点的DHCP响应报文，所述DHCP响应报文可以是DHCP Offer报文，且该DHCP Offer报文中携带IP地址；所述处理器，用于从所述DHCP响应报文中提取IP地址，并且在确认该IP地址没有被占用的情况 下通过所述控制节点发送DHCP应答报文给DHCP代理节点；其中，所述DHCP应答报文可以是DHCP Requst报文。
可选的，如果该IP地址被占用，则终端需要重新向DHCP代理节点发送DHCP Discover广播报文，以便重新请求获取新的IP地址。
可选的，在本实施例的一种具体的实现方式中，所述控制节点，还用于接收到来自DHCP代理节点发送的DHCP ACK，所述DHCP ACK是DHCP服务节点根据所述DHCP Requst报文生成并发送的，用于标记该分配给客户端的IP地址不能再被其它设备使用。
所述处理器，还用于在接收到所述DHCP ACK报文后，对所述IP地址进行绑定。
另外，所述存储器中存储有程序指令，该程序指令执行时可实现上述客户端或终端对DHCP各自报文的发送和接收，以及对获取的IP地址进行绑定等方法流程。进一步地，所述存储器可以包括易失性存储器，例如RAM；还可以包括非易失性存储器，例如flash memory，硬盘HDD或SSD；所述存储器还可以包括上述种类的存储器的组合。
所述处理器可以是CPU，或者CPU和NP的组合。处理器还可以进一步包括硬件芯片。上述硬件芯片可以是ASIC，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic,GAL)或其任意组合。
本领域的技术人员可以清楚地了解到本发明实施例中的技术可借助软件加必需的通用硬件平台的方式来实现。基于这样的理解，本发明实施例中的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例或者实施例的某些部分所述的方法。
本说明书中各个实施例之间相同相似的部分互相参见即可。尤其，对于上述装置和硬件设备的实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例中的说明即可。
以上所述的本发明实施方式并不构成对本发明保护范围的限定。

Claims (10)

  1. 一种动态主机配置协议DHCP报文处理方法，其特征在于，所述方法包括:
    DHCP代理节点从业务网络接收请求，所述请求用于指示为虚拟机或物理机分配IP地址；
    所述DHCP代理节点在管理网络中根据所述请求从DHCP服务节点获取IP地址；
    所述DHCP代理节点向所述虚拟机或物理机发送所述IP地址。
  2. 根据权利要求1所述的方法，其特征在于，所述DHCP代理节点从业务网络接收请求包括：
    所述DHCP代理节点通过第一网卡接收来自所述虚拟机或物理机的所述请求，所述第一网卡用于接入所述业务网络。
  3. 根据权利要求1或2所述的方法，其特征在于，所述DHCP代理节点在管理网络中根据所述请求从DHCP服务节点获取IP地址，包括：
    所述DHCP代理节点通过第二网卡接收所述DHCP服务节点根据所述请求分配的所述IP地址，所述第二网卡用于接入所述管理网络。
  4. 根据权利要求3所述的方法，其特征在于，所述第一网卡位于所述第二网卡所在的主机上，所述DHCP代理节点部署于所述第二网卡所在的主机。
  5. 一种DHCP代理节点，其特征在于，包括接收模块和发送模块，其中，
    所述接收模块，用于从业务网络接收请求,以及在管理网络中根据所述请求从DHCP服务节点获取IP地址，所述请求用于指示为虚拟机或物理机分配IP地址；
    所述发送模块，用于向所述虚拟机或物理机发送所述IP地址。
  6. 根据权利要求5所述的代理节点，其特征在于，
    所述接收模块，具体用于通过第一网卡接收来自所述虚拟机或物理机的所述请求，所述第一网卡用于接入所述业务网络。
  7. 根据权利要求5或6所述的代理节点，其特征在于，
    所述接收模块，具体用于通过第二网卡接收所述DHCP服务节点根据所述请求分配的所述IP地址，所述第二网卡用于接入所述管理网络。
  8. 根据权利要求7所述的代理节点，其特征在于，
    所述第一网卡位于所述第二网卡所在的主机上，所述DHCP代理节点部署于所述第二网卡所在的主机。
  9. 一种计算设备，其特征在于，所述计算设备包括处理器和存储器，所述处理器执行所述存储器存储的计算机指令来实现动态主机配置协议DHCP代理节点，所述DHCP代理节点用于执行权利要求1至4任一项所述的方法。
  10. 一种数据中心，其特征在于，动态主机配置协议DHCP代理节点、DHCP服务节点和虚拟机分别部署在所述数据中心的一个或多个计算设备上，所述DHCP代理节点用于执行权利要求1至4任一项所述的方法。
PCT/CN2019/085602 2018-05-09 2019-05-06 一种dhcp报文处理方法及装置 WO2019214560A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810438541.0 2018-05-09
CN201810438541.0A CN108307002B (zh) 2018-05-09 2018-05-09 一种dhcp报文处理方法及装置

Publications (1)

Publication Number Publication Date
WO2019214560A1 true WO2019214560A1 (zh) 2019-11-14

Family

ID=62846409

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/085602 WO2019214560A1 (zh) 2018-05-09 2019-05-06 一种dhcp报文处理方法及装置

Country Status (2)

Country Link
CN (1) CN108307002B (zh)
WO (1) WO2019214560A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112491630A (zh) * 2020-12-07 2021-03-12 北京华胜天成科技股份有限公司 一种裸机自动部署方法、装置及云环境平台
CN113162944A (zh) * 2021-04-29 2021-07-23 杭州安恒信息安全技术有限公司 安全运营平台与安全组件的网络通信方法、装置及设备
CN113709207A (zh) * 2021-07-17 2021-11-26 济南浪潮数据技术有限公司 一种云资源中软件安装方法、系统、设备及介质
CN114944971A (zh) * 2022-05-11 2022-08-26 江苏安超云软件有限公司 Kubernetes部署网络的方法及装置、电子设备和存储介质
CN115174669A (zh) * 2022-05-25 2022-10-11 南京赛宁信息技术有限公司 一种靶场环境中虚拟机分布式代理接入方法与系统

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108307002B (zh) * 2018-05-09 2021-06-22 华为技术有限公司 一种dhcp报文处理方法及装置
CN110881143B (zh) * 2018-09-05 2022-07-19 中兴通讯股份有限公司 一种机顶盒管理方法、装置、设备及计算机可读存储介质
CN109343932A (zh) * 2018-09-13 2019-02-15 郑州云海信息技术有限公司 一种批量配置虚拟化系统计算节点的系统及方法
CN109862134B (zh) * 2019-03-18 2022-02-01 中国联合网络通信集团有限公司 一种ip地址的租约时间配置方法和系统及dhcp客户端
CN111225080B (zh) * 2020-01-06 2022-11-08 博为科技有限公司 一种网关下挂设备信息的获取方法
CN111586196B (zh) * 2020-04-07 2022-09-06 华云数据控股集团有限公司 一种虚拟机网络双栈的实现方法、装置及系统
CN114363294B (zh) * 2020-09-27 2024-03-15 华为云计算技术有限公司 一种租户服务器的管理方法、装置以及系统
CN112804368B (zh) * 2020-12-08 2021-12-17 中国电子科技集团公司第三十研究所 一种自动分配ip并批量测试的方法及系统
CN113406936A (zh) * 2021-06-28 2021-09-17 中国科学技术大学 一种大科学装置控制系统
CN114301875A (zh) * 2021-12-21 2022-04-08 锐捷网络股份有限公司 一种dhcp代理端的管控方法、装置及电子设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103944867A (zh) * 2013-01-23 2014-07-23 华为技术有限公司 动态主机配置协议报文的处理方法、装置和系统
CN104468574A (zh) * 2014-12-05 2015-03-25 中国联合网络通信集团有限公司 一种虚拟机动态获取ip地址的方法、系统及装置
CN105025067A (zh) * 2014-04-30 2015-11-04 中国银联股份有限公司 一种信息安全技术研究平台
CN105657081A (zh) * 2016-04-07 2016-06-08 华为技术有限公司 提供dhcp服务的方法、装置及系统
CN106797377A (zh) * 2014-09-05 2017-05-31 高通股份有限公司 经由邻居感知联网数据路径的基础设施访问
CN108307002A (zh) * 2018-05-09 2018-07-20 华为技术有限公司 一种dhcp报文处理方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020138614A1 (en) * 2001-03-20 2002-09-26 Hall Dennis W. Method and apparatus to manage network addresses
CN101075962B (zh) * 2007-06-26 2010-09-08 中兴通讯股份有限公司 在二层网络交换设备中实现dhcp中继的装置及其方法
CN101330531B (zh) * 2008-07-31 2011-01-19 杭州华三通信技术有限公司 Dhcp地址分配处理方法和dhcp中继
CN103458002B (zh) * 2013-08-15 2016-11-16 中电长城网际系统应用有限公司 云系统的一键部署方法和装置
CN103491203B (zh) * 2013-09-09 2016-08-31 北京三快在线科技有限公司 一种虚拟化dhcp服务的方法、装置、系统及服务器
CN103595772A (zh) * 2013-11-01 2014-02-19 浪潮电子信息产业股份有限公司 一种基于虚拟路由器的云数据中心网络部署方案

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103944867A (zh) * 2013-01-23 2014-07-23 华为技术有限公司 动态主机配置协议报文的处理方法、装置和系统
CN105025067A (zh) * 2014-04-30 2015-11-04 中国银联股份有限公司 一种信息安全技术研究平台
CN106797377A (zh) * 2014-09-05 2017-05-31 高通股份有限公司 经由邻居感知联网数据路径的基础设施访问
CN104468574A (zh) * 2014-12-05 2015-03-25 中国联合网络通信集团有限公司 一种虚拟机动态获取ip地址的方法、系统及装置
CN105657081A (zh) * 2016-04-07 2016-06-08 华为技术有限公司 提供dhcp服务的方法、装置及系统
CN108307002A (zh) * 2018-05-09 2018-07-20 华为技术有限公司 一种dhcp报文处理方法及装置

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112491630A (zh) * 2020-12-07 2021-03-12 北京华胜天成科技股份有限公司 一种裸机自动部署方法、装置及云环境平台
CN112491630B (zh) * 2020-12-07 2023-08-04 北京华胜天成科技股份有限公司 一种裸机自动部署方法、装置及云环境平台
CN113162944A (zh) * 2021-04-29 2021-07-23 杭州安恒信息安全技术有限公司 安全运营平台与安全组件的网络通信方法、装置及设备
CN113709207A (zh) * 2021-07-17 2021-11-26 济南浪潮数据技术有限公司 一种云资源中软件安装方法、系统、设备及介质
CN114944971A (zh) * 2022-05-11 2022-08-26 江苏安超云软件有限公司 Kubernetes部署网络的方法及装置、电子设备和存储介质
CN115174669A (zh) * 2022-05-25 2022-10-11 南京赛宁信息技术有限公司 一种靶场环境中虚拟机分布式代理接入方法与系统

Also Published As

Publication number Publication date
CN108307002A (zh) 2018-07-20
CN108307002B (zh) 2021-06-22

Similar Documents

Publication Publication Date Title
WO2019214560A1 (zh) 一种dhcp报文处理方法及装置
US10122679B2 (en) Method, relay agent, and system for acquiring internet protocol address in network
US9847967B2 (en) DHCP proxy in a subscriber environment
US8125993B2 (en) Network element having a DHCP lease timer
CN104283983B (zh) 一种软件定义网络中虚拟机ip地址分配方法及装置
US8631100B2 (en) Automatic assignment of hardware addresses within computer networks
US10594586B2 (en) Dialing test method, dialing test system, and computing node
US11888814B2 (en) Managing address spaces across network elements
US11539583B2 (en) Dynamic network discovery service for system deployment and validation
JP2016540448A (ja) 仮想拡張ｌａｎの通信方法、装置、及びシステム
US10361970B2 (en) Automated instantiation of wireless virtual private networks
US20180083968A1 (en) Method and system for authorizing service of user, and apparatus
CN114070723B (zh) 裸金属服务器的虚拟网络配置方法、系统及智能网卡
CN112654049B (zh) 用于配置无线通信覆盖扩展系统的方法、系统、节点和介质
CN114172905B (zh) 一种集群网络组网的方法、装置、计算机设备及存储介质
CN107769939B (zh) 数据通信网中网元管理方法、网管、网关网元及系统
US20150229523A1 (en) Virtual extensible local area network (vxlan) system of automatically configuring multicasting tunnel for segment of virtual extensible local area network according to life cycle of end system and operating method thereof
CN114144995B (zh) 一种用于配置物理服务器的虚拟端口的方法和系统
WO2015184853A1 (zh) 一种IPv6无状态自动配置的认证方法及装置
CN111669309B (zh) 一种建立VxLAN的方法及无线控制器、交换机
US20160241427A1 (en) Service Sending, Receiving Methods and Devices
WO2015085558A1 (zh) 一种动态分配ip地址的方法、装置和系统
CN110636146B (zh) 一种用户地址分配方法及设备
CN113079036A (zh) 一种接入点设备的管理vlan确定方法、装置及接入点设备
WO2022083610A1 (zh) 一种ip地址分配方法、装置及系统

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: 19799934

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: 19799934

Country of ref document: EP

Kind code of ref document: A1