WO2012171427A1 - Procédé de traitement et système de traitement centralisé pour application client/serveur - Google Patents

Procédé de traitement et système de traitement centralisé pour application client/serveur Download PDF

Info

Publication number
WO2012171427A1
WO2012171427A1 PCT/CN2012/075678 CN2012075678W WO2012171427A1 WO 2012171427 A1 WO2012171427 A1 WO 2012171427A1 CN 2012075678 W CN2012075678 W CN 2012075678W WO 2012171427 A1 WO2012171427 A1 WO 2012171427A1
Authority
WO
WIPO (PCT)
Prior art keywords
processing
application
network
different
centralized
Prior art date
Application number
PCT/CN2012/075678
Other languages
English (en)
Chinese (zh)
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 WO2012171427A1 publication Critical patent/WO2012171427A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network

Definitions

  • the present invention relates to the field of communications, and in particular to a processing method and a centralized processing system for a client/server application.
  • a DHCP Dynamic Host Configuration Protocol
  • DNS Domain Name System
  • a DHCP Dynamic Host Configuration Protocol
  • DNS Domain Name System
  • FIG. 1 is a schematic diagram of a typical DHCP and DNS server deployed in a network. In each network (the enterprise network in the figure), DHCP and DNS servers are deployed due to ease of use and management.
  • IP address allocation schemes in different networks and the servers in different enterprise networks may adopt different addressing/naming schemes, DHCP and DNS servers have different databases, although their processing functions are the same, that is, This can be achieved by using the same software system.
  • the user's network is realized through the service provision of the operator, that is, the enterprise user no longer needs the enterprise user to purchase, deploy and Manage relevant network facilities and perform related network application function deployments, and directly obtain relevant network and some basic network application functions from service providers.
  • the operator in addition to providing the basic network connection of the user network, it is also necessary to provide separate DHCP and separate for each user network (customer network).
  • DNS function because the IP address planning of each user, and the domain name planning of some internal systems are very different, it is unlikely to be implemented through a system, and there is still a need for network security, which needs to be isolated from the network. .
  • the present invention provides a processing method and a centralized processing system for a client/server application to at least solve the problem of resource waste and management cost in the above client/server application.
  • a processing method of a C/S (Client/Server, Client/Server) application including: a centralized processing system receives C/S application messages from different customer networks; The C/S application message is processed and the result is returned to the corresponding customer network.
  • the centralized processing system includes: a processing subsystem configured to process the C/S application message; and a gateway configured to receive the C/S application message and return the processing result of the C/S application message to the corresponding The customer network, where the gateway connects different customer networks and processing subsystems, and realizes isolation between different customer networks; the management subsystem is set to perform performance monitoring and configuration management of the centralized processing system.
  • the processing subsystem is one of the following: a PC, a PC server, a blade server, a cluster system consisting of a PC/PC server/blade server, and a distributed system consisting of a PC/PC server/blade server.
  • the processing subsystem includes: a C/S centralized processing function module, including multiple C/S application processing instances, and different C/S application processing instances respectively implementing processing of C/S application messages from different customer networks.
  • the client network and the C/S application processing instance are associated with each other through a gateway; wherein, the multiple C/S application processing instances are independent C/S application processing processes or threads.
  • the configuration management of the management subsystem comprises: IP address configuration of the C/S processing instance and initialization of the data.
  • the gateway receives the C/S application message of the different customer network through different external physical interfaces or sub-interfaces, and implements the correspondence to the C/S processing instance through the internal interface; the internal interface is the physical interface of the gateway connection centralized processing system. Or a sub-interface, a physical interface, or a sub-interface is identified and distinguished by one of the following: VLAN Q-in-Q.
  • the gateway has an L3 switching function and/or an ACL function, and the L3 switching function includes: supporting a VLAN function and implementing a routing function between different VLANs.
  • the processing subsystem is a plurality of virtualized virtual machines, each virtual machine is divided into different customer networks, and the C/S application processing program is installed in the virtual machine to C/ of different customer networks.
  • S applies the message for processing.
  • the centralized processing system is located in an external network outside the customer network and has a public IP address; the customer network forwards the C/S application message to the centralized processing system through the relay or the proxy; the C/S application message carries There is network identification information for identifying the customer network; a centralized processing system, which implements processing of C/S applications of different customer networks through C/S application processing instances.
  • the C/S application comprises: a DHCP and/or a DNS application
  • the centralized processing system comprises: a DHCP and/or a DNS server
  • the customer network is an enterprise network or a subnet.
  • a centralized processing system comprising: a transceiver subsystem and a processing subsystem, wherein a transceiver subsystem is configured to receive C/S application messages from different customer networks; , configured to process the C/S application message, and return the processing result to the corresponding customer network through the transceiver subsystem.
  • the transceiver subsystem is a gateway, and the gateway connects different customer networks and processing subsystems, and implements isolation between different customer networks.
  • the centralized processing system further comprises: a management subsystem, configured to perform performance monitoring and configuration management of the centralized processing system.
  • the processing subsystem is one of the following: a PC, a PC server, a blade server, a cluster system consisting of a PC/PC server/blade server, and a distributed system consisting of a PC/PC server/blade server.
  • the processing subsystem includes: a C/S centralized processing function module, including multiple C/S application processing instances, and different C/S application processing instances respectively implementing processing of C/S application messages from different customer networks.
  • the configuration management of the management subsystem comprises: IP address configuration of the C/S processing instance and initialization of the data.
  • the gateway receives the C/S application message of the different customer network through different external physical interfaces or sub-interfaces, and implements the correspondence to the C/S processing instance through the internal interface; the internal interface is the physical interface of the gateway connection centralized processing system. Or a sub-interface, a physical interface, or a sub-interface is identified and distinguished by one of the following:
  • the gateway has an L3 switching function and/or an ACL function, and the L3 switching function includes: supporting a VLAN function and implementing a routing function between different VLANs.
  • the processing subsystem is a plurality of virtualized virtual machines, each virtual machine is divided into different customer networks, and the C/S application processing program is installed in the virtual machine to C/ of different customer networks. S applies the message for processing.
  • the centralized processing system is located in an external network outside the customer network and has a public IP address; the customer network forwards the C/S application message to the centralized processing system through the relay or the proxy; the C/S application message carries There is network identification information for identifying the customer network; a centralized processing system, which implements processing of C/S applications of different customer networks through C/S application processing instances.
  • the centralized processing of C/S applications from various customer networks solves the problem of waste of resources of the C/S application server, thereby achieving the effects of reducing management costs and improving management efficiency.
  • FIG. 1 is a schematic diagram of a DHCP and DNS server deployed in a network according to the related art
  • FIG. 2 is a flowchart of DHCP processing according to the related art
  • FIG. 3 is a C/S application according to a first embodiment of the present invention.
  • FIG. 4A is a network structure diagram of a C/S application according to Embodiment 2 of the present invention
  • FIG. 4B is a flowchart of DHCP processing of a C/S application according to Embodiment 2 of the present invention
  • FIG. 5 is a network structure diagram of a C/S application according to Embodiment 3 of the present invention
  • FIG. 6 is a centralized diagram according to Embodiment 4 of the present invention.
  • FIG. 7 is a schematic structural diagram of a centralized processing system according to Embodiment 5 of the present invention.
  • Step S302 The centralized processing system receives C/S application messages from different customer networks.
  • Step S304 the centralized processing system processes the received C/S application message.
  • Step S306 the centralized processing system returns the processing result to the corresponding customer network.
  • the customer network may be an enterprise network, or a network that needs to perform the C/S application processing, or a subnet (later).
  • the centralized processing system is located on the external network and is specified by using a public IP address.
  • the service agent uniformly sends the message about the C/S application to the centralized processing system.
  • C/S applications such as DNS
  • it can be directly processed through the underlying IP network without special proxy or relay mechanism, ie when there is an IP network connection between the customer network and centralized processing, ie The relevant processing can be implemented.
  • the service relay or the proxy in the enterprise network carries the network identifier information about the enterprise network in the sent C/S application packet.
  • the centralized processing system combines the egress IP address of the enterprise network and related attribute categories, such as DHCP Option 82, or the port number of the protocol, to distinguish different networks to implement different processing.
  • the centralized processing system may be one, or multiple/a group of PCs or PC servers, or a blade server, or a specially designed computer system, which may be a cluster system or a distributed system.
  • the centralized processing system can implement multiple C/S processing instances to implement the processing and management of the C/S applications of the relevant customer networks, while ensuring high availability of the system.
  • FIG. 4A is a network structure diagram of a C/S application according to Embodiment 2 of the present invention. As shown in FIG.
  • the network structure includes an enterprise network 1 and an enterprise network 2, and the enterprise network 1 and the enterprise network 2 are accessible.
  • ISP/INTERNET network a DHCP relay or proxy is set in the enterprise network 1 and the enterprise network 2 respectively (for the DNS application, since the implementation mechanism is different, the proxy setting is not required, and the packet is directly implemented through the underlying IP network mechanism.
  • the DHCP agent is connected to a centralized processing system, which includes a DHCP server and a DNS server.
  • the DHCP server and the DNS server may be one, or multiple PCs or PC servers, or blade servers, or specially designed computer systems, which may form a cluster system or a distributed system. This needs to be determined based on processing power and the size of the database in question.
  • the public IP address is allocated to the processing server in the centralized processing system.
  • the DHCP server receives the DHCP discovery message and performs The processing returns a DHCP providing information, and the PC selects one of the DHCP providing information, and selects one of them to send the DHCP request information, and obtains an IP address from the DHCP server. Since this processing flow is prior art, it will not be described in detail herein. In general, DHCP and DNS do not require much processing power in small and medium-sized networks.
  • Step S402 Configure a DHCP relay or proxy in the enterprise network, by DHCP.
  • Step S404 the DHCP relay or the proxy forwards the DHCP discovery message to the DHCP server of the external network.
  • the DHCP relay agent or the proxy carries the related attribute category in the sent DHCP discovery packet, for example, the DHCP Option 82o.
  • the work to be completed in the step S402 and the step S404 further includes: configuring a DHCP relay or proxy, configuring DHCP
  • the server IP address allows the DHCP relay or proxy to communicate with the DHCP server.
  • Step S406 the DHCP server provides information related to the DHCP server.
  • Step S408, the DHCP relay or the proxy forwards the DHCP providing information to the corresponding inside the enterprise network.
  • Step S410 to step S414, the PC selects one of the plurality of DHCP providing information that may be returned, and sends the DHCP request information, obtains an IP address from the DHCP proxy, and performs a service connection (if the DHCP relay function is used, Then the relay needs to forward the relevant DHCP request to the relevant DHCP server to obtain the IP address allocation, so the flow is slightly different from FIG. 4B. Since this process is similar to the prior art, it will not be described in detail herein. In a specific implementation, different servers and networks can be distinguished by different IP addresses. And each IP address corresponds to a PC/server to implement the relevant processing functions.
  • this method is the same as the case of deploying DHCP and DNS servers in different enterprise networks in the prior art, or using a separate computer for C/S application processing, and does not solve the problem of resource waste and sharing.
  • it brings further problems, such as the need for a large number of IP addresses, especially in the case of a large number of corporate networks.
  • further optimization can be done on this basis:
  • the same IP address can be used to correspond to the centralized processing system. This is the same as current load balancing, corresponding to an IP address, but its processing can be distributed to multiple computers. But there is a problem here, how to distinguish between different networks, because it is different from ordinary load balancing, here need to implement different processing for different user networks.
  • DHCP Option 82 can also be used to carry customer-related information about DHCP relay or proxy information. The DHCP server determines which enterprise the DHCP request comes from through the DHCP relay or proxy of the enterprise network and the information of the additional DHCP Option 82, and sends it to the corresponding processing process for processing, and returns the processing result.
  • DHCP processing requires virtualization of the processing process for different user processing requirements. Specifically, there are multiple copies of the DHCP processed function in the centralized processing system, or processing instances. Or there is a DHCP processing context (CONTEXT) for each enterprise network, including information about the initial configuration and related processing status, mainly the allocation information of the IP address, and related time information.
  • CONTEXT DHCP processing context
  • the specific functions include: on the one hand, the processing of the application is required, which is an external operation; at the same time, the management operation is also completed, for example, the time is refreshed, and at some critical time points, notification or refresh is required.
  • the transmission of messages, etc. are all conventional operations of DHPC processing and are prior art and will not be further described in the present invention.
  • the association between the specific customer network and the processing instance, the Option 82 information sent by the DHCP relay or the proxy, and the related IP address information, and the subscription information, etc. first realize the identification of the customer network, and further process the processing instance of the relevant customer network.
  • the centralized processing system realizes the related function processing by realizing the connection with the customer network through the IP network.
  • Centralized processing system provides some configuration management, statistics and planning tools, supports function planning and statistics, and provides related management tools to support centralized processing and related management tasks, such as configuring IP address for DHCP processing instances. And initialization of data, etc.
  • FIG. 5 is a network structure diagram of a C/S application according to Embodiment 3 of the present invention.
  • the centralized processing system is a network system composed of one or more PCs, or a PC server, or a blade server, connected by an Ethernet switch (or a network composed of multiple switches), and can be Further forming a PC Or server clusters or distributed systems to improve system reliability.
  • the centralized processing system also includes a gateway, which is configured to connect different customer networks, and a management subsystem to implement management of the centralized processing system.
  • a method of implementing centralized DHCP processing is provided in the second embodiment.
  • this is somewhat inconsistent with the general network deployment experience, that is, the internal network's DNS and DHCP servers should be deployed inside the network, using internal network addresses instead of being exposed to external networks.
  • another processing method is provided, which is similar to the prior art in which the related server is separately deployed in each enterprise network, and meets the experience requirements of the user network deployment and the security requirements of the network isolation.
  • the specific implementation method is: by virtualizing the computing resources in the centralized processing system into multiple virtual machines (VMs), and depending on the processing capability, it may also be an independent host.
  • VMs virtual machines
  • independent IP address configuration can be performed, and further divided into different subnets (corresponding to different customer networks), possibly including multiple VMs or hosts in one subnet, and the IP address is The address in the corresponding customer network.
  • This allows the client's network administrator to independently install and manage DHCP, and/or DNS servers.
  • the gateway further uses Q-in-Q (multi-layer VLAN) technology by centrally processing tunnels in the system network, such as VLANs (referred to as internal VLANs), or when 12-bit VLAN identification is insufficient.
  • VLANs referred to as internal VLANs
  • external VLANs external VLANs
  • the network forms a network to handle the processing of C/S functions.
  • the security function of the network can be enhanced by opening an ACL (Access Control List) function through a gateway or a device on the client network side connected to the gateway.
  • the gateway has: L3 switching function and / or ACL function.
  • the L3 switching functions include but are not limited to: VLAN functions and routing functions between different VLANs.
  • the planning of the processing power of a specific VM can be realized by a management subsystem in the centralized processing system. Specifically, the management subsystem can accept the processing requirements of the client's C/S application, including the number of VMs, the capabilities of the VM, the specific C/S functions, and the like; further, the management subsystem can check according to requirements. Centralize the processing power in the system to meet the demand, and return the result to the customer if the demand is met. Further, the association between the VM and the customer network can be realized through an automatic or manual configuration.
  • a centralized processing system running a set of soft The system, including the main program and different instances of DHCP and DNS processing, is handled by different processes, or threads. Different instances of different DHCP and DNS servers include related address allocation table information, as well as DNS mapping information. Due to the real-time nature of DHCP and DNS, it may not be very strong, or it may require relatively timely processing.
  • the processing capability and setting related processing performance parameters, such as the processing response time, may be appropriately configured.
  • different processing instances need to be differentiated according to the customer network of the service. Specifically, it can be distinguished by the names of different instances.
  • the specific processing example, the association with the customer network can be achieved through a specific network connection.
  • the customer network is connected to the physical interface of a specific computer system of the centralized processing system through the gateway and the internal interface of the gateway, and is associated with the corresponding processing instance through the interface, or further, may be a sub-interface, The interface or the packet sent from the sub-interface is forwarded to the corresponding processing instance. Process the results, returning to the customer network from the same path.
  • the management subsystem accepts the client's processing request and names it.
  • the management subsystem provides an interface interface to the client, and the client can perform further configuration through the interface, such as an IP address, data initialization of the C/S application, and the like.
  • the customer network can connect two gateways through two networks, and centrally process the computers in the system, connect two switches through two links, and so on, to achieve high network reliability. Sex.
  • high reliability implementation can be supported by VRRP (Virtual Router Redundancy Protocol).
  • the high reliability of the C/S application processing can be realized, for example, by backup of the VM or by performing hot backup of the C/S application processing instance.
  • FIG. 6 is a schematic structural diagram of a four-concentration processing system according to an embodiment of the present invention. As shown in FIG.
  • the transceiver subsystem 10 and the processing subsystem 20 are included, and the transceiver subsystem 10 and the processing subsystem 20 are connected.
  • the transceiver subsystem 10 is configured to receive C/S application messages from different customer networks.
  • the processing subsystem 20 is configured to process the C/S application message and return the processing result to the corresponding customer network through the transceiver subsystem 10.
  • the centralized processing system centrally processes the C/S application from each customer network, and solves the problem of waste of C/S application server resources, thereby achieving the effects of reducing management costs and improving management efficiency.
  • the customer network may be an enterprise network, and a service agent, such as a DHCP relay or proxy, is set in the enterprise network; the centralized processing system is located on the external network, and is specified by using a public IP address.
  • the service agent uniformly sends the message about the C/S application to the centralized processing system.
  • the service proxy in the enterprise network carries the network identifier information about the enterprise network in the C/S application packet that is sent.
  • the centralized processing system combines the egress IP address of the enterprise network and related attribute categories, such as DHCP Option 82, to distinguish different networks to implement different processing.
  • the centralized processing system can be a cluster system or a distributed system.
  • FIG. 7 is a schematic structural diagram of a centralized processing system according to Embodiment 5 of the present invention. As shown in FIG. 7, the centralized processing system includes a management subsystem 30 in addition to the transceiver subsystem 10 and the processing subsystem 20.
  • the management subsystem 30 is configured to perform performance monitoring and configuration management of the centralized processing system.
  • the configuration management of the management subsystem 30 includes: IP address configuration of the C/S processing instance and initialization of the data.
  • the transceiver subsystem can be a gateway that connects different customer networks and processing subsystems and implements isolation between different customer networks.
  • the gateway has L3 switching and/or ACL functions.
  • the L3 switching function includes: Supports VLAN functions and implements routing between different VLANs.
  • the processing subsystem is at least one or more PCs, PC servers, blade servers connected through a network, or further, a cluster system composed of the PC, a PC server, or a blade server, or a distributed system. .
  • the centralized processing of the client server application saves the server resources of the application processing, thereby reducing the overall cost, improving the implementation efficiency, and ensuring security.
  • the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.

Landscapes

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

Abstract

L'invention porte sur un procédé de traitement et un système de traitement centralisé pour une application client/serveur. Le procédé de traitement comprend les opérations suivantes : un système de traitement centralisé reçoit des messages d'application client/serveur (C/S) en provenance de divers réseaux clients ; et le système de traitement centralisé traite les messages d'application C/S et renvoie un résultat à un réseau client correspondant. Selon la présente invention, le traitement d'une manière centralisée des applications C/S provenant de divers réseaux clients résout le problème de gaspillage de ressources de serveur d'application C/S, ce qui permet d'atteindre les effets de réduction des coûts de gestion et d'amélioration de l'efficacité de gestion.
PCT/CN2012/075678 2011-06-16 2012-05-17 Procédé de traitement et système de traitement centralisé pour application client/serveur WO2012171427A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110162603.8A CN102833217B (zh) 2011-06-16 2011-06-16 客户/服务器应用的处理方法及集中处理系统
CN201110162603.8 2011-06-16

Publications (1)

Publication Number Publication Date
WO2012171427A1 true WO2012171427A1 (fr) 2012-12-20

Family

ID=47336190

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/075678 WO2012171427A1 (fr) 2011-06-16 2012-05-17 Procédé de traitement et système de traitement centralisé pour application client/serveur

Country Status (2)

Country Link
CN (1) CN102833217B (fr)
WO (1) WO2012171427A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11233778B2 (en) * 2018-08-15 2022-01-25 Juniper Networks, Inc. Secure forwarding of tenant workloads in virtual networks
US11329966B2 (en) 2018-08-15 2022-05-10 Juniper Networks, Inc. System and method for transferring packets between kernel modules in different network stacks

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103475699A (zh) * 2013-08-27 2013-12-25 北京创毅讯联科技股份有限公司 一种企业网代理装置及企业网与公网通信的方法
CN104780017B (zh) * 2014-01-10 2018-07-24 中国移动通信集团公司 一种数据处理方法及装置
CN106354507A (zh) * 2016-08-30 2017-01-25 江苏车置宝信息科技股份有限公司 一种企业级应用管理系统及其运行方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1777156A (zh) * 2005-11-30 2006-05-24 北京邮电大学 用于下一代网络、可动态扩展、开放接口技术的网关
CN101227428A (zh) * 2008-01-30 2008-07-23 中兴通讯股份有限公司 一种应用服务器及其远程控制方法
CN101741850A (zh) * 2009-12-25 2010-06-16 北京邮电大学 面向混合网络服务的多任务并发执行系统及方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101527740B (zh) * 2009-05-05 2011-08-03 杭州华三通信技术有限公司 一种动态地址分配的方法、装置及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1777156A (zh) * 2005-11-30 2006-05-24 北京邮电大学 用于下一代网络、可动态扩展、开放接口技术的网关
CN101227428A (zh) * 2008-01-30 2008-07-23 中兴通讯股份有限公司 一种应用服务器及其远程控制方法
CN101741850A (zh) * 2009-12-25 2010-06-16 北京邮电大学 面向混合网络服务的多任务并发执行系统及方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11233778B2 (en) * 2018-08-15 2022-01-25 Juniper Networks, Inc. Secure forwarding of tenant workloads in virtual networks
US11329966B2 (en) 2018-08-15 2022-05-10 Juniper Networks, Inc. System and method for transferring packets between kernel modules in different network stacks

Also Published As

Publication number Publication date
CN102833217B (zh) 2017-09-15
CN102833217A (zh) 2012-12-19

Similar Documents

Publication Publication Date Title
US9614748B1 (en) Multitenant data center providing virtual computing services
US10148500B2 (en) User-configured on-demand virtual layer-2 network for Infrastructure-as-a-Service (IaaS) on a hybrid cloud network
US8331362B2 (en) Methods and apparatus for distributed dynamic network provisioning
US8565118B2 (en) Methods and apparatus for distributed dynamic network provisioning
US8335841B2 (en) Logical networks
US9485147B2 (en) Method and device thereof for automatically finding and configuring virtual network
JP5953421B2 (ja) 仮想サーバおよび非仮想サーバ混在環境におけるテナントネットワーク構成の管理方法
US8959185B2 (en) Multitenant server for virtual networks within datacenter
EP2725737B1 (fr) Procédé de configuration de politique de réseau, dispositif de gestion et centre de gestion de réseau
US20150172104A1 (en) Managing failure behavior for computing nodes of provided computer networks
US20150058463A1 (en) Proxy methods for suppressing broadcast traffic in a network
WO2015096737A1 (fr) Procédé, appareil, et système de contrôle d'auto-approvisionnement d'un dispositif de réseau
US20220200821A1 (en) Resilient zero touch provisioning
US10771309B1 (en) Border gateway protocol routing configuration
WO2010096155A1 (fr) Commutateur d'accès à un centre de données distribuées
WO2015150756A1 (fr) Réseaux de centre de données
EP3788772B1 (fr) Implementation dhcp sur-noeud pour des machines virtuelles
WO2012171427A1 (fr) Procédé de traitement et système de traitement centralisé pour application client/serveur
CN107547403B (zh) 报文转发方法、协助方法、装置、控制器及主机
Wolinsky et al. On the design of scalable, self-configuring virtual networks
US10924397B2 (en) Multi-VRF and multi-service insertion on edge gateway virtual machines
WO2012087263A1 (fr) Redirecteur dns pour plateformes multicœur
US20210352004A1 (en) Multi-vrf and multi-service insertion on edge gateway virtual machines
CA2736956C (fr) Systeme de gestion de reseau a adresses de gestion
JP2011239082A (ja) 通信装置及びアドレス変換方法

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

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

Country of ref document: EP

Kind code of ref document: A1