CN109428824B - Host topology generation method and system - Google Patents
Host topology generation method and system Download PDFInfo
- Publication number
- CN109428824B CN109428824B CN201710747073.0A CN201710747073A CN109428824B CN 109428824 B CN109428824 B CN 109428824B CN 201710747073 A CN201710747073 A CN 201710747073A CN 109428824 B CN109428824 B CN 109428824B
- Authority
- CN
- China
- Prior art keywords
- host
- identity
- topology
- connection point
- controller
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- 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/12—Discovery or management of network topologies
Abstract
The invention provides a host topology generation method and a host topology generation system, and relates to the technical field of software defined networks. The host topology generation method of the invention comprises the following steps: the controller acquires connection point information through the switch, wherein the connection point information comprises a host identifier of a host where the connection point is located, and the host identifier is a unique and non-repeated identifier of the host; the controller determines the connection points located in the same host by matching the host identification; the controller generates a host topology from the host identity. By the method, the controller can obtain the host machine identification of the host machine where the connection points are located, so that which connection points are located in the same host machine can be determined, an accurate host machine topology can be generated, the problem of inaccurate host machine topology caused by the fact that a single host machine has multiple network cards, multiple containers or multiple virtual machines can be solved, and the accuracy of determining the host machine topology can be improved.
Description
Technical Field
The application relates to the technical field of software defined networking, in particular to a host topology generation method and a host topology generation system.
Background
Currently, in an SDN (Software Defined Network), a controller discovers a switch topology through Openflow and LLDP (Link Layer Discovery Protocol) and discovers a host topology through Openflow and ARP (Address Resolution Protocol).
The process of discovering the host topology by the SDN controller comprises the following steps: when the host machine carries out ARP analysis, an ARP request or a response is reported, and the switch reports the message to the controller through an Openflow message; the SDN controller analyzes the packet, obtains a Media Access Control (MAC) and an IP of the host and a connection port with the switch, and generates topology information of the host.
The host topology generated in such a way has a large deviation from the real topology, and cannot reflect the real host topology situation.
Disclosure of Invention
It is an object of the present application to improve the accuracy of host topology determination.
According to an aspect of the present application, a host topology generation method is provided, including: the controller acquires connection point information through the switch, wherein the connection point information comprises a host identifier of a host where the connection point is located, and the host identifier is a unique and non-repeated identifier of the host; the controller determines the connection points located in the same host by matching the host identification; the controller generates a host topology from the host identity.
Optionally, the connection point comprises a network card, a container, and/or a virtual machine.
Optionally, the obtaining, by the controller through the switch, the connection point information includes: the controller issues a host identity acquisition instruction to the switch; the switch acquires the host identity of the host where the connection point is located from the connected connection point; the switch feeds back connection point information including the host identity to the controller.
Optionally, the controller acquiring the connection point information through the switch further includes: when the host identity of the host is updated, the connection point located at the host reports the host identity to the connected switch.
Optionally, the method further comprises: a unique and non-repeating host identity is deployed for each host.
Optionally, the deploying of the unique and non-repeating host identifier for each host comprises: the host identity distribution module configured on each host distributes host identities for the hosts, wherein the host identity distribution module of one host has management function so as to ensure that the host identities of the hosts are not repeated; when the host identity distribution module with the management function fails, the host identity distribution module on each host selects a new host identity distribution module with the management function.
By the method, the controller can obtain the host machine identification of the host machine where the connection points are located, so that which connection points are located in the same host machine can be determined, an accurate host machine topology can be generated, the problem of inaccurate host machine topology caused by the fact that a single host machine has multiple network cards, multiple containers or multiple virtual machines can be solved, and the accuracy of determining the host machine topology can be improved.
According to another aspect of the present application, there is provided a host topology generation system, including a controller including: the connection point information acquisition unit is used for acquiring connection point information from the switch, wherein the connection point information comprises a host identifier of a host where the connection point is located, and the host identifier is a unique and non-repeated identifier of the host; the host internal topology determining unit is used for determining the connection points of the same host by matching the host identification; and the host topology determining unit is used for generating a host topology according to the host identifier.
Optionally, the connection point comprises a network card, a container, and/or a virtual machine.
Optionally, the connection point information obtaining unit is configured to: issuing a host identity acquisition instruction to a switch; acquiring connection point information from a switch; the system further comprises: and the switch is used for acquiring the host identity of the host where the connection point is located from the connected connection point and feeding back the connection point information including the host identity to the controller.
Optionally, when the host identifier of the host is updated, the connection point located at the host reports the host identifier to the connected switch.
Optionally, the system further comprises a host identifier distribution module located at the host, and configured to deploy a unique and non-duplicate host identifier for each host.
Optionally, each host is configured with a host identifier distribution module, where the host identifier distribution module of one host has a management function to ensure that the host identifiers of the hosts are not repeated; when the host identity distribution module with the management function fails, the host identity distribution module on each host selects a new host identity distribution module with the management function.
According to another aspect of the present application, a host topology generation system is provided, including: a memory; and a processor coupled to the memory, the processor configured to perform any of the host topology generation methods mentioned above based on instructions stored in the memory.
In the host topology generating system, the controller can obtain the host identity of the host where the connection points are located, so that which connection points are located in the same host are determined, an accurate host topology is generated, the problem of inaccurate host topology caused by the fact that a single host has multiple network cards, multiple containers or multiple virtual machines is avoided, and the accuracy of determining the host topology is improved.
According to yet another aspect of the present application, a computer-readable storage medium is proposed, on which computer program instructions are stored, which instructions are executed by a processor to perform the steps of any of the host topology generation methods mentioned above.
Therefore, the computer readable storage medium can acquire the host identity of the host where the connection points are located by executing the instruction on the computer readable storage medium, so that which connection points are located in the same host can be determined, an accurate host topology can be generated, the problem of inaccurate host topology confirmation caused by the fact that a single host has multiple network cards, multiple containers or multiple virtual machines can be avoided, and the accuracy of determining the host topology can be improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1A is a schematic diagram of a host topology generated by a controller in the prior art.
FIG. 1B is a schematic diagram of the real network topology of the network of FIG. 1A.
Fig. 2 is a flowchart of an embodiment of a host topology generation method of the present application.
Fig. 3 is a flowchart of another embodiment of a host topology generation method of the present application.
Fig. 4 is a schematic diagram of an embodiment of a controller in the host topology generating system according to the present application.
Fig. 5 is a schematic diagram of an embodiment of a host topology generation system of the present application.
Fig. 6 is a schematic diagram of an embodiment of a host topology generation system of the present application for host identity distribution.
Fig. 7 is a schematic diagram of an embodiment of the host topology generation system of the present application when a single host includes multiple network cards.
FIG. 8 is a diagram of one embodiment of the present application when a single host includes multiple containers or virtual machines.
Fig. 9 is a schematic diagram of another embodiment of a host topology generation system of the present application.
Fig. 10 is a schematic diagram of another embodiment of a host topology generation system of the present application.
Detailed Description
The technical solution of the present application is further described in detail by the accompanying drawings and examples.
The host topology generation method of the SDN controller in the industry at present has certain defects, including:
1. two network cards belonging to the same server cannot be correctly identified;
2. containers, hosts, and virtual machines cannot be correctly identified;
3. containers, network cards, virtual machines and switches belonging to the same server cannot be marked in the server.
Based on the above characteristics, when the SDN controller generates the topology shown in fig. 1A, its real host topology is shown in fig. 1B.
A flowchart of one embodiment of a host topology generation method of the present application is shown in fig. 2.
In step 201, the controller obtains connection point information through the switch, where the connection point information includes a host identifier of a host where the connection point is located, and the host identifier is a unique and non-duplicate identifier of the host. The connection points comprise network cards, containers, virtual machines and the like. In one embodiment, the host identity may be a host name unique to the host, generated and assigned to each host by a host identity distribution module deployed in a distributed manner on each host, and stored by a distributed host identity management system deployed in the host.
In step 202, the controller determines the connection points located on the same host by matching the host identity, i.e., the connection points with the same host identity are located on the same host.
In step 203, the controller generates a host topology from the host identity, in which the same host acts as a node.
By the method, the controller can obtain the host identity of the host where the connection points are located, so that which connection points are located in the same host can be determined, an accurate host topology can be generated, the problem of inaccurate host topology confirmation caused by the fact that a single host has multiple network cards, multiple containers or multiple virtual machines can be avoided, and the accuracy of determining the host topology can be improved.
In one embodiment, when the host identifier of the host changes, the host actively reports a new host identifier to the switch, so that the switch reports the new host identifier to the controller for updating, thereby ensuring the timeliness of the data of the controller.
In one embodiment, since the connection point information includes the type information of the connection point, the controller can identify the type of the connection point, so that the types of different internal connection points can be distinguished when the internal topology of the host is generated, so as to form more comprehensive host topology information.
A flow diagram of another embodiment of a host topology generation method of the present application is shown in fig. 3.
In step 301, a host identity distribution module configured on each host allocates a host identity to the host. In one embodiment, the hosts in the network are respectively deployed with a host identifier distribution module, wherein there is one host identifier distribution module with management function for ensuring that the host identifiers of the hosts are not duplicated. When the host identity distribution module with the management function fails, the host identity distribution module on each host selects a new host identity distribution module with the management function, so that the robustness of the network is improved.
In step 302, the controller issues a host identity acquisition command to the switch.
In step 303, the switch obtains the host identity of the host where the point of attachment is located from the attached point of attachment.
In step 304, the switch feeds back connection point information including the host identity to the controller.
In step 305, the controller determines the connection point located on the same host by matching the host identity.
In step 306, the controller generates a host topology from the host identity.
By the method, unique and non-repeated host identifiers can be distributed to each host, and the controller can request the hosts to report the identifiers through the switch, so that the controller can conveniently acquire and update the host identifiers of all the connection points according to the requirements, and the controllability of host topology acquisition is improved.
In one embodiment, the host can actively report the host identifier to the controller through the switch, thereby reducing signaling interaction and improving the efficiency of the controller for acquiring the host identifier.
A schematic diagram of one embodiment of a controller in the host topology generation system of the present application is shown in fig. 4. The connection point information obtaining unit 401 can obtain connection point information through the switch, where the connection point information includes a host identifier of a host where the connection point is located, and the host identifier is a unique and non-duplicate identifier of the host. The connection points comprise network cards, containers, virtual machines and the like. In one embodiment, the host identity may be a host name unique to the host, generated and assigned to each host by a host identity distribution module deployed in a distributed manner on each host, and stored by a distributed host identity management system deployed in the host. The intra-host topology determining unit 402 can determine that the connection points located at the same host, i.e., the connection points having the same host identity, are located in the same host by matching the host identity. The host topology determination unit 403 can generate a host topology from the host identity.
In the host topology generating system, the controller can obtain the host identity of the host where the connection points are located, so that which connection points are located in the same host are determined, an accurate host topology is generated, the problem of inaccurate host topology confirmation caused by the fact that a single host has multiple network cards, multiple containers or multiple virtual machines is avoided, and the accuracy of determining the host topology is improved.
A schematic diagram of one embodiment of a host topology generation system of the present application is shown in fig. 5. The structure and function of the controller 50 may be as shown in the embodiment of fig. 4. The host topology generating system can also include a plurality of switches 51 and a host 52 connected to the switches 51. The host 52 has a host identity distribution module 521 thereon, which can assign a host identity to the host. In one embodiment, there is a host identity distribution module with administrative functions to ensure that the host identities of the respective hosts are not duplicated. When the host identity distribution module with the management function fails, the host identity distribution module on each host selects a new host identity distribution module with the management function, so that the robustness of the network is improved. In one embodiment, a distributed host identity management module may be deployed on a host to implement storage, management, and reporting of host identities, so as to implement the above functions on an existing switch. In one embodiment, the host identity management module may be implemented in a manner that generates a dedicated container or virtual machine.
The switch 51 can acquire the host identifier acquisition instruction from the controller 50 and acquire the host identifier of the host 52 where the connection point is located from the connected connection point, and the switch 51 feeds back the connection point information including the host identifier to the controller 50. In one embodiment, a host identity proxy module may be deployed on switch 51 to implement the above-described functionality on an existing switch. In one embodiment, the host identity proxy module may be implemented in a manner that generates a dedicated container or virtual machine.
The system can distribute unique and non-repeated host identifiers for each host, and the controller can request the hosts to report the identifiers through the switch, so that the controller can conveniently acquire and update the host identifiers of all the connection points according to the requirements, and the controllability of host topology acquisition is improved.
In one embodiment, when the host identifier of the host changes, the host may actively report a new host identifier to the switch, so that the switch reports the new host identifier to the controller for updating, thereby ensuring the timeliness of the controller data.
In one embodiment, the host can actively report the host identifier to the controller through the switch, thereby reducing signaling interaction and improving the efficiency of the controller for acquiring the host identifier.
A schematic diagram of an embodiment of a host topology generation system for host identity distribution according to the present application is shown in fig. 6. The host 63 includes H1 to H3, and is connected to the core switch 61 through the access switch 62 and further connected to the SDN controller.
All the hosts in the whole network are provided with a distributed host identity management system and a host identity distribution system, and a host identity management module and a host identity distribution module are deployed on each host.
The host identifiers of all hosts are configured in the distributed host identifier distribution system, or all host identifiers are automatically generated by the host identifiers, so that all host identifiers are not repeated. The distributed host identity distribution system automatically elects a management node, keeps one management node in the whole network all the time, and elects a new management node again when the management node fails. And the host identity distribution module of each host acquires the host identity of the host from the management node. And the host identity management module of each host acquires and stores the host identity of the host from the host identity distribution module of the host.
The host can complete the distribution and management of the host identification under the coordination of the distributed host identification management system and the host identification distribution system, so that the host has unique and unrepeated identification, and the controller can distinguish the host to which the connection point belongs conveniently.
Fig. 7 is a schematic diagram of an embodiment of the host topology generation system according to the present application when a single host includes multiple network cards. The host topology generation system includes an SDN controller 71, a core switch 72, an access switch 73, and a host 74. The access switch 73 includes access switches S1 and S2, and the host H1 includes two network cards connected to the switch S1 and the switch S2, respectively. The hostname of host H1 is generated by user configuration or default when installing the system, or is obtained by the hostname distribution system of step 1.
The host H1 sends an ARP request or response message, and the access switch S1 encapsulates it into an Openflow message to report to the SDN controller. The controller analyzes the Openflow message, obtains the MAC and IP of the connection point and the port (port of network card 1) connected to S1, and generates a host topology.
The controller issues an Openflow message to the switch S1, and acquires the host id of the host H1. The switch S1 parses the Openflow message, and sends the message to the connection point through the host identity broker module deployed in the switch to obtain the host identity. The nexus, upon receiving the message, queries the local host identity and responds to switch S1. After receiving the response, the switch S1 responds to the SDN controller with an Openflow message. The controller displays the host identification into the connection point topology; if the host identities of a plurality of connection points exist in the network, the topology of the connection points (network cards) is merged into one host.
ARP messages sent by another network card of host H1 may reach the SDN controller through access switch S2. After repeating the above steps, the SDN controller can correctly display the dual network card topology of the host H1. When the host identity of the host H1 changes (a new host identity may be obtained through the distributed host identity distribution system), the distributed host identity management module of H1 reports to the switches S1 and S2 actively, and S1 and S2 report to the SDN controller through Openflow messages, and the controller refreshes the corresponding host topology.
In the host topology generation system, the SDN controller can actively inquire the host identifier after obtaining the MAC and IP of the host through the host ARP to generate the host topology, so that the unique identifier of the host is obtained, and the internal topology and the host topology of the host are conveniently determined.
A schematic diagram of one embodiment of the present application when a single host includes multiple containers or virtual machines is shown in fig. 8. The host topology generation system includes an SDN controller 81, a core switch 82, an access switch 83, and a host 84. The host name is generated by user configuration or default when the system is installed, or the distributed host identity distribution system is distributed and determined.
After a vSwitch (Virtual Switch) of the host H1 is started, the vSwitch registers with the SDN controller according to configuration, and after the controller processes a registration message successfully, the controller issues an Openflow message to query a host identifier of a host where the vSwitch is located.
The access switch S1 receives the Openflow message and issues the message through the host identity broker module. The host identity management module of host H1 returns the host identity of the native machine to switch S1. The switch S1 encapsulates the received message into Openflow message and reports the Openflow message to the controller; the controller receives the topology information of the post-refresh host H1. The container/virtual machine inside host H1 sends an ARP (request or response) which is encapsulated by vSwitch into an Openflow message reporting controller. The controller analyzes the Openflow message, obtains the MAC and IP addresses of the container/virtual machine and a link connected with the vSwitch, and generates a container/VM topology.
The controller issues an Openflow message to the vSwitch to acquire a host identifier of the container/virtual machine; the switch S1 receives the message and forwards it to the container/virtual machine via the host identity agent. After the container/virtual machine receives the message, the host identifier of the host and the identifier of the container/virtual machine are obtained by the host identifier management module of the local machine, and the obtained identifier is returned to the switch S1. After receiving the message, the switch S1 returns the message to the controller through an Openflow message; and after the controller obtains the host identity of the host of the container/virtual machine according to the Openflow message, displaying the vSwitch and the network card with the same host identity in the topology of the same host.
When the host identity of the host H1 changes, the host identity management module of the host H1 reports to the switches S1 and S2 actively, and the switches S1 and S2 report to the SDN controller through Openflow messages, and the controller refreshes the corresponding host topology.
In one embodiment, the host identity distribution system Etcd and the distributed host identity management system Flannel-hn can be configured on all hosts of the whole network. The Etcd configures the host identity of each host, or the Etcd automatically generates the host identity of each host, thereby ensuring that all the host identities are not repeated.
Etcd elects a manager node by a Raft algorithm, keeps a manager node in the whole network all the time, and elects a new manager node again when the manager node fails. Each host Etcd acquires the host identity of the host from the manager node. The Flannel-hn of each host acquires the host identity of the host from the host Etcd and configures the host identity into the host identity of the host name.
When the host has a dual network card:
1. the host obtains a host identity from a distributed host identity distribution system.
2. One connection point (a network card) of the host sends an ARP request message, and the access switch encapsulates the ARP request message into an Openflow message to be reported to the SDN controller.
3. The controller analyzes the Openflow message, obtains the MAC and the IP of the connection point and the port connected with the S1, and generates a host topology.
4. And the controller sends an Openflow message to the switch to acquire the host identity of the host where the connection point is located.
5. The switch analyzes the Openflow message, and acquires the host identity through the message sent to the connection point by the host identity agent.
6. After receiving the message, the host inquires the host identifier of the local machine and responds to the switch.
7. And after receiving the response, the switch responds to the SDN controller through Openflow.
8. The controller displays the host identification in the topology of its host. If the host identifiers of a plurality of connection points in the network are the same, the topology of the host identifiers is merged into the same host, and the host identifiers are marked as a plurality of network cards of the same host.
9. The ARP message sent by another network card of the host may be responded to by other access switches. After repeating the above steps, the SDN controller can correctly display the dual network card topology of the host H1.
The host topology generating system can allow a user to distribute host identifications to the server through configuration or a mechanism similar to an etcd/Flannel host name storage and distribution system, so that the uniqueness of the whole network is ensured, and further, the host identifications of all the connection points can be obtained, so that network cards, virtual machines, containers and the like included in the host corresponding to the host identifications are determined, the internal topology of the host is determined, the real host topology can be obtained, and the accuracy of determining the host topology is improved.
Fig. 9 is a schematic structural diagram of an embodiment of the host topology generation system of the present application. The host topology generation system includes a memory 910 and a processor 920. Wherein: the memory 910 may be a magnetic disk, flash memory, or any other non-volatile storage medium. The memory is for storing instructions in the following corresponding embodiments of the host topology generation method. Coupled to memory 910, processor 920 may be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. The processor 920 is configured to execute instructions stored in the memory, which can improve the accuracy of the host topology determination.
In one embodiment, as also shown in FIG. 10, the host topology generation system 1000 includes a memory 1010 and a processor 1020. Processor 1020 is coupled to memory 1010 by a BUS 1030. The host topology generation system 1000 can also be connected to an external storage device 1050 through a storage interface 1040 for calling external data, and can also be connected to a network or another computer system (not shown) through a network interface 1060. And will not be described in detail herein.
In this embodiment, the accuracy of the host topology determination can be improved by storing the data instructions in the memory and processing the instructions by the processor.
In another embodiment, a computer readable storage medium has stored thereon computer program instructions which, when executed by a processor, implement the steps of the method in the corresponding embodiment of the host topology generation method. As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The present application has been described in detail so far. Some details well known in the art have not been described in order to avoid obscuring the concepts of the present application. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.
The methods and apparatus of the present application may be implemented in a number of ways. For example, the methods and apparatus of the present application may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present application are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present application may also be embodied as a program recorded in a recording medium, the program including machine-readable instructions for implementing a method according to the present application. Thus, the present application also covers a recording medium storing a program for executing the method according to the present application.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solutions of the present application and not to limit them; although the present application has been described in detail with reference to preferred embodiments, those of ordinary skill in the art will understand that: modifications to the specific embodiments of the application or equivalent replacements of some of the technical features may still be made; all of which are intended to be encompassed within the scope of the claims appended hereto without departing from the spirit and scope of the present disclosure.
Claims (12)
1. A host topology generation method, comprising:
the method comprises the steps that a controller acquires connection point information through a switch, wherein the connection point information comprises a host identifier of a host where the connection point is located, and the host identifier is a unique and non-repeated identifier of the host;
the controller determines connection points located in the same host by matching the host identification, wherein the connection points comprise network cards, containers and/or virtual machines, and the host identifications corresponding to multiple network cards, multiple containers or multiple virtual machines in a single host are the same;
and the controller generates a host topology according to the host identifier, wherein connection points with the same host identifier in the host topology are positioned in the same host, and the same host is used as a node.
2. The method of claim 1, wherein the controller obtaining attachment point information via a switch comprises:
the controller issues a host identity acquisition instruction to the switch;
the switch acquires a host identity of a host where the connection point is located from the connected connection point;
and the switch feeds back the connection point information comprising the host identity to a controller.
3. The method of claim 2, wherein the controller obtaining attachment point information via a switch further comprises:
when the host identity of the host is updated, the host identity is reported to the connected switch at the connection point of the host.
4. The method of claim 1, further comprising:
a unique and non-repeating host identity is deployed for each host.
5. The method of claim 4, wherein the deploying for each host a unique and non-repeating host identity comprises:
the host identity distribution module configured on each host distributes the host identity for the host, wherein the host identity distribution module of one host has management function so as to ensure that the host identity of each host is not repeated;
when the host identity distribution module with the management function fails, the host identity distribution module on each host selects a new host identity distribution module with the management function.
6. A host topology generation system, comprising a controller, the controller comprising:
the system comprises a connection point information acquisition unit, a connection point information acquisition unit and a control unit, wherein the connection point information acquisition unit is used for acquiring connection point information from a switch, the connection point information comprises a host identifier of a host where the connection point is located, and the host identifier is a unique and non-repeated identifier of the host;
the system comprises a host internal topology determining unit, a host identification determining unit and a host internal topology determining unit, wherein the host internal topology determining unit is used for determining connection points located in the same host by matching the host identification, the connection points comprise network cards, containers and/or virtual machines, and the host identifications corresponding to multiple network cards, multiple containers or multiple virtual machines existing in a single host are the same;
and the host topology determining unit is used for generating a host topology according to the host identifier, wherein connection points with the same host identifier in the host topology are positioned in the same host, and the same host is used as a node.
7. The system of claim 6,
the connection point information obtaining unit is configured to: issuing a host identity acquisition instruction to a switch; acquiring the connection point information from the switch;
the system further comprises: and the switch is used for acquiring the host identity of the host where the connection point is located from the connected connection point and feeding back the connection point information comprising the host identity to the controller.
8. The system of claim 7, wherein the point of attachment at the host reports the host identity to the connected switch when the host identity of the host is updated.
9. The system of claim 6, further comprising a host identity distribution module at the host for deploying a unique and non-repeating host identity for each host.
10. The system of claim 8,
each host is provided with a host identifier distribution module, wherein the host identifier distribution module of one host has management function so as to ensure that the host identifiers of the hosts are not repeated;
when the host identity distribution module with the management function fails, the host identity distribution module on each host selects a new host identity distribution module with the management function.
11. A host topology generation system, comprising:
a memory; and
a processor coupled to the memory, the processor configured to perform the method of any of claims 1-5 based on instructions stored in the memory.
12. A computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710747073.0A CN109428824B (en) | 2017-08-28 | 2017-08-28 | Host topology generation method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710747073.0A CN109428824B (en) | 2017-08-28 | 2017-08-28 | Host topology generation method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109428824A CN109428824A (en) | 2019-03-05 |
| CN109428824B true CN109428824B (en) | 2021-09-17 |
Family
ID=65501807
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710747073.0A Active CN109428824B (en) | 2017-08-28 | 2017-08-28 | Host topology generation method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109428824B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110380973B (en) * | 2019-06-18 | 2021-05-04 | 南京理工大学 | Software defined network topology detection method |
| CN111339095A (en) * | 2020-02-25 | 2020-06-26 | 深信服科技股份有限公司 | Method, device, equipment and storage medium for constructing network topology |
| CN114299655B (en) * | 2020-09-23 | 2023-09-05 | 成都中科信息技术有限公司 | Electronic voting system and working method thereof |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104468219A (en) * | 2014-12-11 | 2015-03-25 | 杭州华三通信技术有限公司 | Virtual networking network topology discovery method and device |
| CN106470142A (en) * | 2015-08-14 | 2017-03-01 | 中国电信股份有限公司 | The self-service generation method of virtual network topology and system |
| CN106489251A (en) * | 2015-12-21 | 2017-03-08 | 华为技术有限公司 | The methods, devices and systems that applied topology relation finds |
| CN107005781A (en) * | 2014-11-28 | 2017-08-01 | 华为技术有限公司 | For the System and method for for the virtual network topology for generating M2M communication |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100433936C (en) * | 2006-09-08 | 2008-11-12 | 华为技术有限公司 | Method and system for acquiring topological information of radio network |
| CN101729351B (en) * | 2009-11-03 | 2012-01-25 | 福建星网锐捷网络有限公司 | Method and system for finding topology information, query request device and awaiting query device |
| US9258266B2 (en) * | 2012-08-30 | 2016-02-09 | Cisco Technology, Inc. | Host detection by top of rack switch devices in data center environments |
| CN103281248B (en) * | 2013-06-09 | 2016-03-30 | 北京星网锐捷网络技术有限公司 | The discover method of network topology, device and system |
| CN106713042B (en) * | 2016-12-29 | 2020-05-26 | 中国银联股份有限公司 | Method and device for determining network topology |
-
2017
- 2017-08-28 CN CN201710747073.0A patent/CN109428824B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107005781A (en) * | 2014-11-28 | 2017-08-01 | 华为技术有限公司 | For the System and method for for the virtual network topology for generating M2M communication |
| CN104468219A (en) * | 2014-12-11 | 2015-03-25 | 杭州华三通信技术有限公司 | Virtual networking network topology discovery method and device |
| CN106470142A (en) * | 2015-08-14 | 2017-03-01 | 中国电信股份有限公司 | The self-service generation method of virtual network topology and system |
| CN106489251A (en) * | 2015-12-21 | 2017-03-08 | 华为技术有限公司 | The methods, devices and systems that applied topology relation finds |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109428824A (en) | 2019-03-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106797405B (en) | Distributed load balancing system, health check method and service node | |
| US10432460B2 (en) | Network service scaling method and apparatus | |
| CN107070691B (en) | Cross-host communication method and system of Docker container | |
| EP2562973B1 (en) | Virtual machine migration method, switch, virtual machine system | |
| US8718061B2 (en) | Data center network system and packet forwarding method thereof | |
| US9749182B2 (en) | Method and apparatus for configuring network policy of virtual network | |
| CN106412142B (en) | Resource equipment address obtaining method and device | |
| EP2854377B1 (en) | A method for centralized address resolution | |
| CN110635987B (en) | Message transmission method, device, equipment and machine readable storage medium | |
| CN107579900B (en) | Method, device and system for accessing VX L AN network from V L AN network | |
| US9525648B2 (en) | Method for acquiring physical address of virtual machine | |
| CN109428824B (en) | Host topology generation method and system | |
| EP2654250A2 (en) | Virtual local area network identity transformation method and apparatus | |
| CN109474443B (en) | Configuration method, device and system of newly added server and communication equipment | |
| EP3905598A1 (en) | Message processing method and apparatus, control plane device, and computer storage medium | |
| US11689499B2 (en) | Management of endpoint address discovery in a software defined networking environment | |
| CN108039968B (en) | Network optimization method, device and computer readable storage medium | |
| CN110391940A (en) | Response method, device, system, equipment and the storage medium of address of service | |
| CN107070719B (en) | Equipment management method and device | |
| US11929851B2 (en) | Gateway selection method, device, and system | |
| CN107733727B (en) | Zero configuration method, device and equipment | |
| CN108429641A (en) | A kind of network device management method and device | |
| CN109819059B (en) | Method, device, equipment and storage medium for managing network equipment | |
| CN104426759A (en) | Host machine router acquiring method, host machine router acquiring device, and host machine router acquiring system | |
| CN105122776B (en) | Address acquiring method and network virtualization edge device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220126 Address after: 100007 room 205-32, floor 2, building 2, No. 1 and No. 3, qinglonghutong a, Dongcheng District, Beijing Patentee after: Tianyiyun Technology Co.,Ltd. Address before: No.31, Financial Street, Xicheng District, Beijing, 100033 Patentee before: CHINA TELECOM Corp.,Ltd. |