CN110851238A - Implementation method of openstack fully-distributed dhcp service - Google Patents
Implementation method of openstack fully-distributed dhcp service Download PDFInfo
- Publication number
- CN110851238A CN110851238A CN201911105158.4A CN201911105158A CN110851238A CN 110851238 A CN110851238 A CN 110851238A CN 201911105158 A CN201911105158 A CN 201911105158A CN 110851238 A CN110851238 A CN 110851238A
- Authority
- CN
- China
- Prior art keywords
- virtual machine
- port
- dhcp service
- dhcp
- computing node
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/462—LAN interconnection over a bridge based backbone
-
- 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
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Abstract
The invention discloses a realization method of an openstack fully-distributed dhcp service, which relates to the field of cloud computing.A dhcp service is deployed on all computing nodes, a name space is created on the computing nodes, a trunk port is created on a virtual machine bridge, the trunk port is associated with the name space, a rule of a flow table is set, only network flow of the related port of a virtual machine is allowed to flow through the trunk port, a dhcp service process is created after the port of the virtual machine is bound with the computing nodes, and only the dhcp service of the computing nodes is allowed to run in the name space of the computing nodes; the method of the invention can greatly improve the performance of the system, simplify the configuration file of the dnsmasq only by configuring the information related to a single network card and reduce the complexity of the configuration file because the dhcp service is provided only by the process of the node and the network does not pass through the network card and is directly corresponding by the operating system.
Description
Technical Field
The invention discloses a realization method of an openstack fully-distributed dhcp service, and relates to the field of cloud computing.
Background
The dhcp service of openstack is implemented by launching a dnmasq process on a user-defined dhcp node, with a dedicated dnmasq process for each network responsible for providing IP and routing information for the network. There are some problems with this mode: the dhcp is distributed in a centralized way, so that the total number of the network is limited; the centralized dhcp service occupies a plurality of IP addresses for ensuring high availability of the service; the virtual machine and the dhcp server are not on the same host, so that the performance is influenced, and meanwhile, if a physical network fails, the normal service cannot be ensured; the broadcast messages of dhcp flood on two-layer or even three-layer networks, which affects the risk of the stability of the underlying network,
the invention discloses a realization method of an openstack fully distributed dhcp service, which can improve the performance and stability of the dhcp service,
disclosure of Invention
Aiming at the problems in the prior art, the invention provides a method for realizing the openstack fully-distributed dhcp service, which has the characteristics of strong universality, simple and convenient implementation and the like and has wide application prospect.
The specific scheme provided by the invention is as follows:
a realization method of an openstack fully distributed dhcp service, wherein the dhcp service is deployed on all computing nodes,
creating a namespace on the compute node, and creating a trunk port on the virtual machine bridge, associated with the namespace,
setting a rule of a flow table, only allowing network traffic of a relevant port of the virtual machine to flow through a trunk port, creating a dhcp service process after the port of the virtual machine is bound with a computing node, and only allowing the dhcp service of the computing node to run in a name space of the computing node.
In the implementation method, the dhcp service for the virtual machine of the computing node is provided through the dhcpagent.
In the implementation method, dhcpagent of a computing node receives a service request,
the dhcpagent judges whether a naming space and a dnsmasq process of the virtual machine are created on the computing node, if not, the naming space is created, a new trunk port is created in the virtual machine bridge and is moved to the naming space, otherwise, the dhcp service operation of the computing node is continued.
In the implementation method, the dhcpagent judges whether the port of the newly added virtual machine belongs to the same subnet, if not, the IP address of the dhcp of the subnet of the port of the newly added virtual machine is obtained and added to the port in the name space.
In the implementation method, the computing node creates a corresponding name space according to the id of the virtual machine or the name of the equipment.
In the implementation method, the port used for providing the dhcp service on the virtual machine bridge only provides the dhcp service of the specified virtual machine.
An implementation system of an openstack fully-distributed dhcp service comprises a computing cluster and a virtual machine,
the dhcp service is deployed on all the compute nodes of the compute cluster,
creating a namespace on the compute node, and creating a trunk port on the virtual machine bridge, associated with the namespace,
setting a rule of a flow table, only allowing network traffic of a relevant port of the virtual machine to flow through a trunk port, creating a dhcp service process after the port of the virtual machine is bound with a computing node, and only allowing the dhcp service of the computing node to run in a name space of the computing node.
In the implementation system, the dhcp service for the virtual machine of the computing node is provided by the dhcpagent in the computing node.
The dhcpagent of the computing node in the implementation system receives the service request,
the dhcpagent judges whether a naming space and a dnsmasq process of the virtual machine are created on the computing node, if not, the naming space is created, a new trunk port is created in the virtual machine bridge and is moved to the naming space, otherwise, the dhcp service operation of the computing node is continued.
And in the implementation system, the dhcpagent in the computing node judges whether the port of the newly added virtual machine belongs to the same subnet, if not, the IP address of the dhcp of the subnet of the port of the newly added virtual machine is obtained and added to the port in the name space.
The invention has the advantages that:
the invention provides a realization method of an openstack fully-distributed dhcp service, which comprises the steps that all computing nodes are provided with the dhcp service, a name space is created on the computing nodes, a trunk port is created on a virtual machine bridge and is associated with the name space, a rule of a flow table is set, only network flow of the related port of a virtual machine is allowed to flow through the trunk port, a dhcp service process is created after the port of the virtual machine is bound with the computing nodes, and only the dhcp service of the computing nodes is allowed to run in the name space of the computing nodes;
the method of the invention can greatly improve the performance of the system because the service of the dhcp is provided only by the process of the node and the network does not pass through the network card but directly corresponds by the operating system, simplifies the configuration file of the dnsmasq, only needs to configure the information related to a single network card, reduces the complexity of the configuration file, and each subnet of the fully-distributed dhcp service only needs to occupy one IP without using a plurality of IP addresses, greatly improves the upper limit of the network, and in the centralized dhcp design, the upper limit of the network is determined by vlan and the number of processes, and the number of the network can not basically break through 3000 taking three nodes dhcp as an example. However, under the full-subdivision dhcp architecture, the bottleneck of the number of the network is related to the virtual machine, and under the condition of ensuring the operation premise of the invention, the number of the network theoretically has no upper limit.
Drawings
FIG. 1 is a schematic diagram of a system computing node of the present invention;
FIG. 2 is a schematic flow chart of the method of the present invention.
Detailed Description
The invention provides a realization method of an openstack fully distributed dhcp service, which deploys the dhcp service on all computing nodes,
creating a namespace on the compute node, and creating a trunk port on the virtual machine bridge, associated with the namespace,
setting a rule of a flow table, only allowing network traffic of a relevant port of the virtual machine to flow through a trunk port, creating a dhcp service process after the port of the virtual machine is bound with a computing node, and only allowing the dhcp service of the computing node to run in a name space of the computing node.
In the implementation method, the dhcp service for the virtual machine of the computing node is provided through the dhcpagent.
Meanwhile, the implementation system of the openstack fully-distributed dhcp service corresponding to the method comprises a computing cluster and a virtual machine,
the dhcp service is deployed on all the compute nodes of the compute cluster,
creating a namespace on the compute node, and creating a trunk port on the virtual machine bridge, associated with the namespace,
setting a rule of a flow table, only allowing network traffic of a relevant port of the virtual machine to flow through a trunk port, creating a dhcp service process after the port of the virtual machine is bound with a computing node, and only allowing the dhcp service of the computing node to run in a name space of the computing node.
The present invention is further described below in conjunction with the following figures and specific examples so that those skilled in the art may better understand the present invention and practice it, but the examples are not intended to limit the present invention.
The dhcp service mainly functions to provide a dynamic IP address for the client, after the virtual machine is started, the operating system will generally obtain the IP address by default through a dhcp request, and through the dhcp service, the virtual machine can communicate with an external network.
When the method of the invention is used for realizing the openstack fully distributed dhcp service, the specific process is as follows:
the dhcp service is deployed on all the compute nodes,
creating a corresponding namespace on a computing node according to the id of a virtual machine or the name of equipment, creating a trunk port on a virtual machine bridge, namely creating a corresponding dhcp virtual port on the virtual bridge and setting the same vlan number, associating with the namespace, wherein each dhcp service runs in an independent namespace, the name of the namespace can be qdhcp- $ { instance-id }, the instance-id is the uuid identification number of the virtual machine, and the dnmasq is responsible for the configuration of the dhcps of all network cards under the namespace,
referring to fig. 1, a new trunk port is created in the br-int bridge, moved into the namespace, an IP address is assigned to a port in this namespace,
the dhcp services distributed on different nodes share the same one ip address,
setting a rule of a flow table, only allowing network traffic of a relevant port of the virtual machine to flow through a trunk port, creating a dhcp service process after the port of the virtual machine is bound with a computing node, only allowing the dhcp service of the computing node to run in a name space of the computing node, and providing the dhcp service for the virtual machine of the computing node through a dhcpagent.
In the above process, when a user accesses a subnet which creates dhcp, the user can create a port and bind the port to a specified computing node, an update request of the port is sent to the dhcpagent of the computing node, after the dhcpagent receives a service request, the dhcpagent judges whether a namespace and a dnsmasq process of a virtual machine are created on the computing node, if not, a namespace is created, a new trunk port is created on a virtual machine bridge and is moved to the namespace, otherwise, the dhcp service operation of the computing node is continued.
In the method, when the dhcpagent judges whether the port of the newly added virtual machine belongs to the same subnet, if not, the IP address of the dhcp of the subnet of the port of the newly added virtual machine is obtained, the IP address is added to the port in the name space, the information of the port needing to be added, such as an IP address, a mac address and the like, can be obtained according to the content of the message, and meanwhile, the related configuration file of the dnsmasq is updated,
and each port on a virtual machine bridge br-int that is used to provide a dhcp is only used to provide the dhcp service for the specified virtual machine.
By using the method of the invention, the dhcp message is allowed to be broadcast on a physical link, and the dhcpagent only provides the dhcp service for the virtual machine of the node, thereby reducing the risk of two-layer broadcast.
When the system is utilized to realize the openstack fully-distributed dhcp service, the method is similar to the method in process, and specifically comprises the following steps:
the dhcp service is deployed on all the compute nodes of the compute cluster,
creating a corresponding namespace on a computing node according to the id of a virtual machine or the name of equipment, creating a trunk port on a virtual machine bridge, namely creating a corresponding dhcp virtual port on the virtual bridge and setting the same vlan number, associating with the namespace, wherein each dhcp service runs in an independent namespace, the name of the namespace can be qdhcp- $ { instance-id }, the instance-id is the uuid identification number of the virtual machine, and the dnmasq is responsible for the configuration of the dhcps of all network cards under the namespace,
referring to fig. 1, a new trunk port is created in the br-int bridge, moved into the namespace, an IP address is assigned to a port in this namespace,
the dhcp services distributed on different nodes share the same one ip address,
setting a rule of a flow table, only allowing network traffic of a relevant port of the virtual machine to flow through a trunk port, creating a dhcp service process after the port of the virtual machine is bound with a computing node, only allowing the dhcp service of the computing node to run in a name space of the computing node, and providing the dhcp service for the virtual machine of the computing node through a dhcpagent.
In the above process, when a user accesses a subnet which creates dhcp, the user can create a port and bind the port to a specified computing node, an update request of the port is sent to the dhcpagent of the computing node, after the dhcpagent receives a service request, the dhcpagent judges whether a namespace and a dnsmasq process of a virtual machine are created on the computing node, if not, a namespace is created, a new trunk port is created on a virtual machine bridge and is moved to the namespace, otherwise, the dhcp service operation of the computing node is continued.
In the above process, when the dhcpagent judges whether the port of the newly added virtual machine belongs to the same subnet, if not, the IP address of the dhcp of the subnet of the port of the newly added virtual machine is obtained, and is added to the port in the name space, and the information of the port to be added, such as IP address, mac address and the like, can be obtained according to the content of the message, and meanwhile, the related configuration file of the dnsmasq is updated,
and each port on a virtual machine bridge br-int that is used to provide a dhcp is only used to provide the dhcp service for the specified virtual machine.
The invention also allows the dhcp message to be broadcast on the physical link, and the dhcpagent only provides the dhcp service for the virtual machine of the node, thereby reducing the risk of the two-layer broadcast.
The above-mentioned embodiments are merely preferred embodiments for fully illustrating the present invention, and the scope of the present invention is not limited thereto. The equivalent substitution or change made by the technical personnel in the technical field on the basis of the invention is all within the protection scope of the invention. The protection scope of the invention is subject to the claims.
Claims (10)
1. A realization method of an openstack fully distributed dhcp service is characterized in that the dhcp service is deployed on all computing nodes,
creating a namespace on the compute node, and creating a trunk port on the virtual machine bridge, associated with the namespace,
setting a rule of a flow table, only allowing network traffic of a relevant port of the virtual machine to flow through a trunk port, creating a dhcp service process after the port of the virtual machine is bound with a computing node, and only allowing the dhcp service of the computing node to run in a name space of the computing node.
2. The method of claim 1, wherein the dhcp service to the virtual machine of the compute node is provided via dhcpagent.
3. The implementation method as claimed in claim 2, wherein the dhcpagent of the compute node receives the service request,
the dhcpagent judges whether a naming space and a dnsmasq process of the virtual machine are created on the computing node, if not, the naming space is created, a new trunk port is created in the virtual machine bridge and is moved to the naming space, otherwise, the dhcp service operation of the computing node is continued.
4. The implementation method of claim 2 or 3, wherein the dhcpagent determines whether the port of the newly added virtual machine belongs to the same subnet, and if not, obtains the IP address of the dhcp of the subnet of the port of the newly added virtual machine and adds the IP address to the port in the namespace.
5. The implementation method as claimed in claim 4, wherein the compute node creates the corresponding namespace according to the id of the virtual machine or the name of the device.
6. The implementation of claim 5 wherein the port on the virtual machine bridge for providing the dhcp service provides only the dhcp service of the specified virtual machine.
7. An implementation system of openstack fully distributed dhcp service is characterized by comprising a computing cluster and a virtual machine,
the dhcp service is deployed on all the compute nodes of the compute cluster,
creating a namespace on the compute node, and creating a trunk port on the virtual machine bridge, associated with the namespace,
setting a rule of a flow table, only allowing network traffic of a relevant port of the virtual machine to flow through a trunk port, creating a dhcp service process after the port of the virtual machine is bound with a computing node, and only allowing the dhcp service of the computing node to run in a name space of the computing node.
8. The system of claim 7, wherein the dhcp service is provided to the virtual machine of the compute node within the compute node via a dhcp agent.
9. The implementation method as claimed in claim 8, wherein the dhcpagent of the compute node receives the service request,
the dhcpagent judges whether a naming space and a dnsmasq process of the virtual machine are created on the computing node, if not, the naming space is created, a new trunk port is created in the virtual machine bridge and is moved to the naming space, otherwise, the dhcp service operation of the computing node is continued.
10. The implementation method according to claim 8 or 9, wherein the dhcp pagent in the compute node determines whether the port of the newly added virtual machine belongs to the same subnet, and if not, obtains the IP address of the dhcp of the subnet of the port of the newly added virtual machine and adds the IP address to the port in the namespace.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911105158.4A CN110851238A (en) | 2019-11-13 | 2019-11-13 | Implementation method of openstack fully-distributed dhcp service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911105158.4A CN110851238A (en) | 2019-11-13 | 2019-11-13 | Implementation method of openstack fully-distributed dhcp service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110851238A true CN110851238A (en) | 2020-02-28 |
Family
ID=69601058
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911105158.4A Pending CN110851238A (en) | 2019-11-13 | 2019-11-13 | Implementation method of openstack fully-distributed dhcp service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110851238A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111970199A (en) * | 2020-08-24 | 2020-11-20 | 浪潮云信息技术股份公司 | Implementation method for improving virtual machine network performance in openstack dvr mode |
| CN114024772A (en) * | 2022-01-05 | 2022-02-08 | 北京赛宁网安科技有限公司 | Network attack and defense platform port mapping method and system |
| CN114915545A (en) * | 2022-05-20 | 2022-08-16 | 深圳市证通电子股份有限公司 | Application scheduling deployment management method based on DHCP network high-availability cluster |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101039234A (en) * | 2007-03-19 | 2007-09-19 | 中兴通讯股份有限公司 | Method for realizing distributed DHCP relay |
| CN105446797A (en) * | 2015-11-30 | 2016-03-30 | 国云科技股份有限公司 | Virtual machine access service method |
| CN106101301A (en) * | 2016-08-05 | 2016-11-09 | 汉柏科技有限公司 | Distributed virtual DHCP service provides system and method |
| CN108933844A (en) * | 2017-05-27 | 2018-12-04 | 华为技术有限公司 | The method and apparatus of DHCP service is provided |
-
2019
- 2019-11-13 CN CN201911105158.4A patent/CN110851238A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101039234A (en) * | 2007-03-19 | 2007-09-19 | 中兴通讯股份有限公司 | Method for realizing distributed DHCP relay |
| CN105446797A (en) * | 2015-11-30 | 2016-03-30 | 国云科技股份有限公司 | Virtual machine access service method |
| CN106101301A (en) * | 2016-08-05 | 2016-11-09 | 汉柏科技有限公司 | Distributed virtual DHCP service provides system and method |
| CN108933844A (en) * | 2017-05-27 | 2018-12-04 | 华为技术有限公司 | The method and apparatus of DHCP service is provided |
Non-Patent Citations (1)
| Title |
|---|
| ZHANGOIC: "Neutron dhcp实现", 《HTTPS://BLOG.CSDN.NET/ZHANGOIC/ARTICLE/DETAILS/79990699》 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111970199A (en) * | 2020-08-24 | 2020-11-20 | 浪潮云信息技术股份公司 | Implementation method for improving virtual machine network performance in openstack dvr mode |
| CN114024772A (en) * | 2022-01-05 | 2022-02-08 | 北京赛宁网安科技有限公司 | Network attack and defense platform port mapping method and system |
| CN114024772B (en) * | 2022-01-05 | 2022-04-26 | 北京赛宁网安科技有限公司 | Network attack and defense platform port mapping method and system |
| CN114915545A (en) * | 2022-05-20 | 2022-08-16 | 深圳市证通电子股份有限公司 | Application scheduling deployment management method based on DHCP network high-availability cluster |
| CN114915545B (en) * | 2022-05-20 | 2024-01-26 | 深圳市证通电子股份有限公司 | Application scheduling deployment management method based on DHCP network cluster |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11895154B2 (en) | Method and system for virtual machine aware policy management | |
| CN107733670B (en) | Forwarding strategy configuration method and device | |
| CN107070691B (en) | Cross-host communication method and system of Docker container | |
| US10742557B1 (en) | Extending scalable policy management to supporting network devices | |
| EP2866389B1 (en) | Method and device thereof for automatically finding and configuring virtual network | |
| CN102801599B (en) | A kind of communication means and system | |
| CN114500135B (en) | Access method, device and system of user terminal equipment | |
| JP2020512638A (en) | System and method for providing homogeneous fabric attributes to reduce the need for subnet administrator access in a high performance computing environment | |
| CN110505152B (en) | Route filtering method and device and electronic equipment | |
| CN110851238A (en) | Implementation method of openstack fully-distributed dhcp service | |
| WO2014032598A1 (en) | Forward packet with edge device | |
| EP2584742B1 (en) | Method and switch for sending packet | |
| CN107666419B (en) | Virtual broadband access method, controller and system | |
| CN113872845B (en) | Method for establishing VXLAN tunnel and related equipment | |
| CN111464454B (en) | Load sharing method and system for virtual BRAS (broadband remote Access Server) equipment in data center | |
| WO2011147342A1 (en) | Method, equipment and system for exchanging routing information | |
| CN108574613B (en) | Two-layer intercommunication method and device for SDN data center | |
| CN115296848B (en) | Multi-local area network environment-based fort system and fort access method | |
| CN112769965A (en) | IP address management and distribution method, device and system | |
| CN104734930B (en) | Method and device for realizing access of Virtual Local Area Network (VLAN) to Variable Frequency (VF) network and Fiber Channel Frequency (FCF) | |
| CN109688241A (en) | IPv4/IPv6 dual stack conversion method and system based on SDN | |
| CN115955456A (en) | IPv 6-based enterprise campus network and networking method | |
| CN113381936A (en) | Network information processing method and device and network equipment | |
| CN107911495B (en) | MAC address synchronization method and VTEP | |
| CN112583655B (en) | Data transmission method and device, electronic equipment and readable storage 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200228 |