CN107104824B - Network topology determination method and device - Google Patents
Network topology determination method and device Download PDFInfo
- Publication number
- CN107104824B CN107104824B CN201710209970.6A CN201710209970A CN107104824B CN 107104824 B CN107104824 B CN 107104824B CN 201710209970 A CN201710209970 A CN 201710209970A CN 107104824 B CN107104824 B CN 107104824B
- Authority
- CN
- China
- Prior art keywords
- network device
- network
- link
- determining
- port
- 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
Classifications
-
- 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
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
The application provides a method and a device for determining network topology, wherein the method comprises the following steps: acquiring topology information of first network equipment, wherein the topology information comprises an equipment level of the first network equipment; the process of obtaining the device hierarchy of the first network device includes: receiving a first message sent by a first network device, wherein the first message carries identification information of a neighbor network device of the first network device; analyzing the identification information from the first message, and acquiring a device level corresponding to the identification information; determining the equipment level of the first network equipment according to the equipment level corresponding to the identification information; and determining the network topology according to the topology information of the first network equipment. According to the technical scheme, the device levels of all the network devices do not need to be determined in a recursive traversal mode, the obtaining efficiency of the device levels is improved, and the computing resources of the management devices are saved.
Description
Technical Field
The present application relates to the field of network management technologies, and in particular, to a method and an apparatus for determining a network topology.
background
In a traditional cloud computing platform, computing resources, storage resources, network resources and the like are respectively managed by using different management platforms, so that management is complex. Based on this, a Unified management matrix of UIS (Unified Infrastructure System) is proposed, which can integrate computing resources, storage resources, network resources, etc., and manage all resources in a Unified manner.
Disclosure of Invention
The application provides a network topology determination method, which is applied to management equipment and comprises the following steps:
Acquiring topology information of first network equipment, wherein the topology information comprises an equipment level of the first network equipment; the process of obtaining the device hierarchy of the first network device includes: receiving a first message sent by a first network device, wherein the first message carries identification information of a neighbor network device of the first network device; analyzing the identification information from the first message, and acquiring a device level corresponding to the identification information; determining the equipment level of the first network equipment according to the equipment level corresponding to the identification information;
and determining the network topology according to the topology information of the first network equipment.
the application provides a network topology determination device, is applied to the management equipment, the device includes:
An obtaining module, configured to obtain topology information of a first network device, where the topology information includes a device level of the first network device; in the process of acquiring the device level of the first network device, receiving a first message sent by the first network device, wherein the first message carries identification information of a neighbor network device of the first network device; analyzing the identification information from the first message, and acquiring a device level corresponding to the identification information; determining the equipment level of the first network equipment according to the equipment level corresponding to the identification information;
And the determining module is used for determining the network topology according to the topology information of the first network equipment.
Based on the above technical solution, in the embodiment of the present application, after receiving a first message sent by a first network device, a management device may determine a device level of the first network device by using identification information of a neighbor network device of the first network device, which is carried in the first message, without determining device levels of other network devices except the first network device, and without determining device levels of all network devices in a recursive traversal manner, so that an obtaining efficiency of the device levels may be improved, and a computing resource of the management device may be saved.
Drawings
in order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present application or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present application.
FIGS. 1A-1C are flow diagrams of a network topology determination method in one embodiment of the present application;
FIGS. 2A and 2B are schematic diagrams of an application scenario in an embodiment of the present application;
FIG. 3 is a hardware block diagram of a management device in one embodiment of the present application;
Fig. 4 is a block diagram of a network topology determination device according to an embodiment of the present application.
Detailed Description
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein is meant to encompass any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Depending on the context, moreover, the word "if" as used may be interpreted as "at … …" or "at … …" or "in response to a determination".
the UIS unified management matrix can provide a graphical user interface and a simplified operation mode, so that the connection and management of the network are more intuitive and clear. When the UIS unified management matrix is used for carrying out unified management on computing resources, storage resources and network resources, the network topology among the network devices can be obtained and displayed, so that a user can know the connection relation of the network devices according to the network topology, and the user management is facilitated. However, the network topology cannot be directly obtained from the device.
The embodiment of the present application provides a method for determining a network topology, where the method may be applied to a management device (e.g., a UIS unified management matrix), and the management device may manage a plurality of network devices (e.g., a router, a switch, a virtual machine, a server, and the like). In this embodiment, the detailed description is given of the management device determining the network topology and displaying the network topology to the network administrator, so that the network administrator performs management according to the network topology.
in one example, the processing manner of each of the plurality of network devices is the same, and for convenience of description, the processing of one network device is taken as an example and referred to as a first network device.
referring to fig. 1A, a schematic flow chart of the method for determining a network topology may include:
Step 101, topology information of a first network device is obtained.
In one example, the topology information may include, but is not limited to: a device hierarchy of the first network device, the device hierarchy may be a number of hops for a shortest path for the first network device to reach the management device. For the process of acquiring the device hierarchy of the first network device, as shown in fig. 1B, the following steps may be included:
step 10111, receiving a first message sent by the first network device, where the first message carries identification information of a neighbor network device (a device having a neighbor relationship with the first network device) of the first network device. The identification information may include a Media Access Control (MAC) address, an IP address, a device index, and the like of the neighboring network device, and is not limited to this identification information.
Step 10112, the identification information of the neighbor network device is analyzed from the first message, and the device hierarchy corresponding to the identification information is obtained. The device hierarchy corresponding to the identification information is the hop count of the shortest path from the neighbor network device to the management device.
Step 10113, determining the device level of the first network device according to the device level corresponding to the identification information. Specifically, the minimum device hierarchy may be obtained from the device hierarchies corresponding to the identification information, and the device hierarchy of the first network device is determined to be the sum of the minimum device hierarchy and a preset value (e.g., 1).
in an example, the first network device may periodically send a first message to the management device, and the management device may periodically receive the first message, acquire a device hierarchy corresponding to identification information carried in the first message, and determine the device hierarchy of the first network device according to the device hierarchy corresponding to the identification information. Each process of determining the device hierarchy of the first network device may be referred to as a statistical period, that is, each statistical period may be used to determine the device hierarchy of the first network device according to the device hierarchy corresponding to the identification information.
in each statistical period, if the device hierarchy corresponding to the identification information is already locally recorded, the device hierarchy of the first network device may be determined according to the device hierarchy corresponding to the identification information, and then the corresponding relationship between the identification information of the first network device and the device hierarchy is locally recorded for use in the next statistical period. If the device hierarchy corresponding to the identification information is not recorded locally, the device hierarchy of the first network device is no longer determined according to the device hierarchy corresponding to the identification information, that is, the device hierarchy of the first network device is no longer determined in the current statistical period, and the device hierarchy of the first network device is determined after the next statistical period.
For example, in a first statistical period, the management device receives a first message of the network device 1, where the first message carries the identification information 2 of the network device 2 and the identification information 3 of the network device 3, and since the corresponding relationship between the identification information 2 and the device hierarchy is not recorded locally and the corresponding relationship between the identification information 3 and the device hierarchy is not recorded locally, the device hierarchy of the network device 1 is no longer determined in the current statistical period. Then, the management device receives a first message of the network device 2, where the first message carries identification information 0 of the management device and identification information 1 of the network device 1, and since a correspondence between the identification information 0 and the device level 0 is locally recorded (initially configured in the management device), it is determined that the device level of the network device 2 is the device level 1 according to the device level 0, and a correspondence between the identification information 2 and the device level 1 is locally recorded.
In the second statistical period, after the management device receives the first message of the network device 1, assuming that the first message carries the identification information 2 and the identification information 3, since the corresponding relationship between the identification information 2 and the device level 1 is locally recorded, it can be determined that the device level of the network device 1 is the device level 2 according to the device level 1, and the corresponding relationship between the identification information 1 and the device level 2 is locally recorded.
By analogy, the management device may determine the device hierarchy from the first message at each statistical period.
In one example, the topology information may further include a link STP (Spanning Tree Protocol) state of a first network device, where the link is formed by a first port on the first network device being connected to a second port on a neighboring network device; the number of the first port and the second port is one or more. The link STP state may include, but is not limited to, link normal, link blocked. For the process of acquiring the link STP state of the first network device, as shown in fig. 1C, the method may include the following steps:
Step 10121, receiving a second message sent by the first network device, where the second message may carry the status information of the first port. Wherein the state information may be a blocking state or a forwarding state.
step 10122, parsing the status information of the first port from the second message.
Step 10123, determining a link STP state of the first network device according to the state information of the first port.
For a procedure of determining a link STP state of a first network device from state information of a first port, comprising: when the state information of each first port is a blocking state, determining that the link STP state of the first network equipment is a link blocking state; when a first port with the state information in a forwarding state exists, if the state information of a second port forming a link with the first port with the state information in the forwarding state is in the forwarding state, determining that the link STP state of the first network equipment is normal; and if the state information of each second port is a blocking state, determining that the port link STP state of the first network equipment is a link blocking state.
taking the first network device as the network device a and the neighboring network device as the network device B as an example, assuming that the number of the first ports and the number of the second ports are two or more, if the port a1 of the network device a is connected to the port B1 of the network device B and the port a2 of the network device a is connected to the port B2 of the network device B, then: when the state information of the port A1 and the port A2 is in a blocking state, the link STP state is a link blocking state; when the state information of the port A1 and/or the port A2 is a forwarding state, the state information of the port B1 and the port B2 is determined, if the state information of the port B1 and/or the port B2 is the forwarding state, the link STP state is determined to be normal, and if the state information of the port B1 and the port B2 is a blocking state, the link STP state is determined to be link blocking. Wherein, the status information of the port a1 and the status information of the port a2 can be known from the second message sent by the network device a, and the status information of the port B1 and the status information of the port B2 can be known from the second message sent by the network device B.
Assuming that the number of the first ports and the number of the second ports are respectively one, if the port a1 of the network device a is connected with the port B1 of the network device B, when the status information of the port a1 is all in a blocking state, the link STP state is a link blocking state; and when the state information of the port A1 is a forwarding state, determining the state information of the port B1, if the state information of the port B1 is the forwarding state, determining that the link STP state is normal, and if the state information of the port B1 is a blocking state, determining that the link STP state is link blocking. Therein, the status information of port a1 may be learned from the second message sent by network device a, and the status information of port B1 may be learned from the second message sent by network device B.
In one example, the topology information may further include, but is not limited to: the link type of the first network device, which is the link type between the first network device and the neighbor network device, may include, but is not limited to, add, invalidate, normal, offline. For the process of obtaining the link type of the first network device, the following steps may be included: in each statistical period, determining neighbor network equipment having a neighbor relation with the first network equipment, and determining the link types of the first network equipment and the neighbor network equipment according to the snapshot condition; wherein the snapshot condition comprises: the snapshot is not taken when the snapshot processing is not performed on the network topology, or the snapshot is taken when the snapshot processing is performed on the network topology.
The process of determining the link type between the first network device and the neighbor network device according to the snapshot condition may include, but is not limited to: if the snapshot condition is not snapshot, determining that the link type corresponding to the neighbor network device existing in the current counting period is new, and determining that the link type corresponding to the neighbor network device not existing in the current counting period is invalid. If the snapshot condition is a snapshot, determining that the current statistical period exists and the link type corresponding to the neighbor network device existing before the snapshot is normal, determining that the current statistical period exists and the link type corresponding to the neighbor network device not existing before the snapshot is newly added, determining that the current statistical period does not exist and the link type corresponding to the neighbor network device existing before the snapshot is offline, and determining that the current statistical period does not exist and the link type corresponding to the neighbor network device not existing before the snapshot is invalid. After the snapshot is cancelled, the normal is modified to be newly added (i.e. the link type corresponding to the neighbor network device with the link type being normal is modified to be newly added), and the offline is modified to be invalid (i.e. the link type corresponding to the neighbor network device with the link type being offline is modified to be invalid).
Step 102, determining a network topology according to the topology information of the first network device.
In an example, after performing the processing of step 101 for each first network device, the network topology may be determined according to the topology information of each first network device, that is, the network topology includes topology information of each network device, such as a neighbor relation between network devices, a device level of each network device, a link STP state between network devices, a link type between network devices, and the like, which is not described again.
After determining the network topology, the management device may display the network topology to the network manager, so that the network manager performs management according to the network topology, and the management process of the network manager is not described again.
Based on the above technical solution, in the embodiment of the present application, after receiving a first message sent by a first network device, a management device may determine a device level of the first network device by using identification information of a neighbor network device of the first network device, which is carried in the first message, without determining device levels of other network devices except the first network device, and without determining device levels of all network devices in a recursive traversal manner, so that an obtaining efficiency of the device levels may be improved, and a computing resource of the management device may be saved.
the above-described scheme of the embodiment of the present application is described below with reference to the application scenario of fig. 2A. In fig. 2A, the neighbor relationship of each network device is as follows: the management device, the network device 2, the network device 3, the network device 4, and the network device 7 are neighbor network devices of the network device 1; the management device, the network device 1, the network device 4, and the network device 5 are neighbor network devices of the network device 2; network device 1, network device 6, and network device 7 are neighbor network devices of network device 3; and so on, and will not be described herein.
In one example, the management device maintains a data structure for each network device, where the data structure is used to store topology information of the network device, and for convenience of description, the network device 1 is taken as an example for illustration.
As shown in table 1, an example of the data structure of the network device 1, the topology information stored in the data structure includes, but is not limited to, one or any combination of the following: identification information of the network device 1 (such as MAC address, IP address, device index, etc.); the device hierarchy of network device 1 (i.e., the number of hops for the shortest path for network device 1 to reach the management device, such as hop number 1); identification information of the neighbor network device; a device hierarchy of neighbor network devices; link STP state, link type between network device 1 and the neighbor network device.
TABLE 1
As can be seen from table 1, this data structure is a data structure for the network device 1 corresponding to the device index 1, the device hierarchy of the network device 1 is 1, and the neighbor network devices of the network device 1 include a management device, a network device 2, a network device 3, a network device 4, a network device 7, and the like, and can know identification information, device hierarchy, link STP state, link type, and the like corresponding to each neighbor network device.
of course, the data structure is only one implementation way of storing topology information, and in practical applications, the data structure is not limited to the data structure, and further details of other ways of storing topology information are not described herein. The content of the topology information is not limited to the above content, and the content of the topology information is not limited.
in one example, after acquiring the topology information, the management device may store the topology information according to the data structure shown in table 1, and how to acquire the topology information will be described below.
In case one, the management device obtains identification information of a neighbor network device of the network device 1.
After the network device 1 is started, it may discover a neighbor network device connected to itself, for example, the network device 1 discovers a neighbor network device connected to itself based on Link Layer Discovery Protocol (LLDP), and details of the Discovery process are not further described. Then, the network device 1 may send a first message carrying the identification information of the neighbor network devices to the management device. After receiving the first message, the management device may analyze identification information of each neighboring network device connected to the network device 1, such as identification information of the management device, identification information of the network device 2, identification information of the network device 3, identification information of the network device 4, and identification information of the network device 7, and determine the neighboring network device of the network device 1.
in one example, the first message may include, but is not limited to: a message based on an SNMP (Simple Network Management Protocol) type; or a message based on a NETCONF (Network Configuration Protocol) type.
in an example, the management device may periodically collect the identification information of the neighbor network devices of the network device 1, that is, the management device periodically sends a request message to the network device 1, so that the network device 1 sends the identification information of the neighbor network devices of the network device 1 to the management device through the first message.
And in case two, the management device acquires the identification information and the device hierarchy of the network device 1.
In an example, the first message may further carry identification information of the network device 1, and therefore, after receiving the first message, the management device may analyze the identification information of the network device 1 from the first message.
The process of acquiring the device hierarchy of the network device 1 for the management device may include the following ways:
in the first mode, after receiving the first message sent by the network device 1, the management device may acquire the device hierarchies of all the network devices, that is, may acquire the device hierarchies of the network device 1.
Referring to fig. 2A, after receiving the first message sent by the network device 1, the management device triggers to acquire the device hierarchies of all network devices. In the device hierarchy acquisition process, the device hierarchy of the management device is preset to 0, then all the neighbor network devices (network device 1 and network device 2) of the management device are queried, and the device hierarchies of the network device 1 and the network device 2 are determined to 1 (device hierarchy 0+1 of the management device). Then, the management device queries all the neighbor network devices (management device, network device 2, network device 3, network device 4, network device 7) of the network device 1, and since the device hierarchy of the management device and the network device 2 has already been determined, the device hierarchy of the network device 3, the network device 4, and the network device 7 can be determined to be 2 (device hierarchy 1+1 of the network device 1). The management device may then query all neighbor network devices of network device 2, all neighbor network devices of network device 3, …, and so on, in turn. Through the above processing, the management device can acquire the device hierarchies of all the network devices.
in the above process, the method of querying all neighboring network devices of each device (e.g., the management device, the network device 1, the network device 2, etc.) may be the method of case one, and details are not described here.
As for the first mode, after receiving the first message sent by the network device 1, the management device triggers to acquire the device hierarchies of all the network devices, and after receiving the first message sent by the network device 2, the management device triggers to acquire the device hierarchies of all the network devices, and so on, each first message triggers the management device to acquire the device hierarchies of all the network devices.
In the second mode, after receiving the first message sent by the network device 1, the management device may obtain only the device hierarchy of the network device 1, instead of obtaining the device hierarchies of all network devices.
in the second mode, after receiving the first message sent by the network device 1, the management device may determine the device level of the network device 1 by using the identification information of the neighbor network device carried in the first message, without determining the device levels of other network devices, and without determining the device levels of all network devices in a recursive traversal manner, thereby improving the acquisition efficiency of the device levels and saving the computing resources of the management device.
Referring to fig. 2A, after receiving the first message sent by the network device 1, the management device triggers to acquire the device hierarchy of the network device 1. The identification information carried by the first message comprises: the identification information of the management device, the identification information of the network device 2, the identification information of the network device 3, the identification information of the network device 4, and the identification information of the network device 7, so that the management device can acquire the device level 0 of the management device, the device level 1 of the network device 2, the device level 2 of the network device 3, the device level 2 of the network device 4, and the device level 2 of the network device 7; then, the management device determines the smallest device level, i.e., device level 0; the management device then determines the device level of the network device 1 as the minimum device level +1, i.e., the device level of the network device 1 is 1. This completes the determination process of the device hierarchy of the network device 1.
In the above process, for the process of acquiring the device hierarchy of the neighboring network device (such as the management device, the network device 2, the network device 3, the network device 4, and the network device 7), in each statistical period, if the device hierarchy corresponding to the identification information is already recorded locally, the device hierarchy of the network device 1 is determined according to the device hierarchy corresponding to the identification information, and then the correspondence between the identification information of the network device 1 and the device hierarchy is recorded locally. If the device hierarchy corresponding to the identification information is not recorded locally, the device hierarchy of the network device 1 is no longer determined according to the device hierarchy corresponding to the identification information, that is, the device hierarchy of the network device 1 is no longer determined in the current statistical period, but the device hierarchy of the network device 1 is determined again after the next statistical period.
For example, for the first statistical period, if the device hierarchy of any neighbor network device cannot be obtained when the device hierarchy of the network device 1 is determined, the device hierarchy of the network device 1 may not be determined any more, but the device hierarchy of the network device 1 may be determined again after waiting for the next statistical period. If the device hierarchy of part or all of the neighbor network devices can be obtained, the device hierarchy of the network device 1 can be determined based on the device hierarchy of part or all of the neighbor network devices, and the specific determination method is not repeated.
For the second and each subsequent statistical cycle, if the device hierarchy of any neighbor network device cannot be obtained in the process of determining the device hierarchy of the network device 1, the device hierarchy of the network device 1 may not be determined any more, and if the device hierarchy of some or all neighbor network devices may be obtained, the device hierarchy of the network device 1 may be determined based on the device hierarchy of some or all neighbor network devices.
In practical applications, the first statistical period may be processed in a first manner, and the second and subsequent statistical periods may be processed in a second manner. Alternatively, the first statistical period, and the second and subsequent statistical periods may be processed in the second manner.
And thirdly, the management equipment acquires the identification information and the equipment level of the neighbor network equipment of the network equipment 1.
Since the data structure of the network device 1 further includes the identification information and the device hierarchy of the neighbor network device of the network device 1, the management device can determine the identification information and the device hierarchy of the neighbor network device. Based on case one, the management device may determine identification information of neighbor network devices of network device 1. For each neighbor network device, after receiving the first message sent by the neighbor network device, the management device may obtain the device hierarchy of the neighbor network device based on the second condition, and details of the obtaining process are not repeated.
And in case four, the management equipment acquires the link STP state of the network equipment 1.
for example, the management device may acquire a link STP state between the network device 1 and the management device, a link STP state between the network device 1 and the network device 2, a link STP state between the network device 1 and the network device 3, a link STP state between the network device 1 and the network device 4, and a link STP state between the network device 1 and the network device 7.
In an example, after acquiring the neighbor network device of the network device 1, the management device may further send a query message to the network device 1 to trigger the network device 1 to report state information of each port connected to the neighbor network device. After receiving the query message, the network device 1 may send the state information of each port connected to the neighbor network device on the network device 1 to the management device through the second message. Wherein the query message/second message may include, but is not limited to: messages based on the SNMP type or messages based on the NETCONF type. In order to send the state information of each port connected to the neighbor network device on the network device 1 to the management device, after the network device 1 is started, the state information of each port connected to the neighbor network device may be obtained first, for example, the state information of each port connected to the neighbor network device is obtained through STP, which is not described in detail herein.
Further, after receiving the second message, the management device may analyze, from the second message, the state information of each port where the network device 1 is connected to the neighbor network device, for example: state information of each port to which the network device 1 is connected to the management device, state information of each port to which the network device 1 is connected to the network device 2, state information of each port to which the network device 1 is connected to the network device 3, state information of each port to which the network device 1 is connected to the network device 4, and state information of each port to which the network device 1 is connected to the network device 7. Then, the management device determines the link STP state between the network device 1 and the neighbor network device using these state information, for example, determines the link STP state between the network device 1 and the network device 2 using the state information of each port to which the network device 1 and the network device 2 are connected, or the like.
Taking the determination of the link STP state between the network device 1 and the network device 2 as an example, it is assumed that the second message carries port a1 of the network device 1 and port B1 of the network device 2, and port a2 of the network device 1 is connected to port B2 of the network device 2, and carries the state information of port a1 and the state information of port a2, and if the state information of port a1 is a Blocking state (Blocking) and the state information of port a2 is a Blocking state, it is determined that the link STP state of the network device 1 is link Blocking; if the state information of the port a1 is Forwarding state (Forwarding) and/or the state information of the port a2 is Forwarding state, and the state information of the port B1 is Forwarding state and/or the state information of the port B2 is Forwarding state, determining that the link STP state of the network device 1 is normal; if the state information of the port a1 is the forwarding state and/or the state information of the port a2 is the forwarding state, the state information of the port B1 is the blocking state, and the state information of the port B2 is the blocking state, it is determined that the link STP state of the network device 1 is the link blocking.
In one example, the link STP state is determined as topology information, so that when the network topology is determined by using the topology information, the link STP state can be displayed on the network topology, so that network management personnel can view the link STP state. Further, when the link STP state is the link blocking, the network administrator can know that a loop occurs between the network device 1 and the neighboring network device, and the port is blocked.
and in case five, the management device acquires the link type (such as new, invalid, normal, offline and the like) of the network device 1.
For example, the link type between the network device 1 and the management device, the link type between the network device 1 and the network device 2, the link type between the network device 1 and the network device 3, the link type between the network device 1 and the network device 4, and the link type between the network device 1 and the network device 7 are acquired.
In practical applications, the network topology may change, for example, in the last statistical period, the network topology includes the network device 1 and the network device 2, and in the current statistical period, the network topology includes the network device 1, the network device 2 and the network device 3, that is, one network device 3 is added, or the network topology includes the network device 1, that is, one network device 2 is added. In the conventional method, when the network topology changes, only the network topology of the current statistical period is displayed to the network management staff, and the network management staff cannot know whether the network topology changes. On the basis, in the embodiment of the application, the link type is determined as the topology information, so that when the network topology is determined by using the topology information, the link type can be displayed on the network topology, and when the network topology changes, a network manager can check the change condition of the network topology from the network topology, such as checking whether a newly added network device, a leaving network device and the like from the network topology.
In one example, to account for changes in network topology, a concept of taking a snapshot of the network topology is proposed. Before the network topology is subjected to snapshot, the network topology does not display the change condition of the network topology, and the network topology only reflects the actual network topology in the current environment; after the network topology is snapshot, the network topology will show the change of the network topology, i.e. the change of the network topology when snapshot is performed.
The link types are classified into new types and invalid types before the network topology is subjected to snapshot, and the link types are classified into new types, invalid types, normal types and offline types after the network topology is subjected to snapshot. Referring to fig. 2B, the link type corresponding to the neighbor network device existing in the current statistics period is new (transition 1), and the link type corresponding to the neighbor network device not existing in the current statistics period is invalid (transition 2). For example, in the previous statistical period, the neighbor network devices of the network device 1 are the network device 2 and the network device 3, and in the current statistical period, the neighbor network devices of the network device 1 are the network device 2 and the network device 4, so that the link types corresponding to the network device 2 and the network device 4 existing in the current statistical period are newly added, and the link types corresponding to the network device 3 existing in the current statistical period and the previous statistical period are invalid.
As shown in fig. 2B, after the snapshot is executed, the link type corresponding to the neighbor network device that exists in the current statistics period and exists before the snapshot is normal (transition 3), the link type corresponding to the neighbor network device that exists in the current statistics period and does not exist before the snapshot is newly added (transition 5), the link type corresponding to the neighbor network device that does not exist in the current statistics period and exists before the snapshot is offline (transition 4), and the link type corresponding to the neighbor network device that does not exist in the current statistics period and does not exist before the snapshot is invalid. For example, in the last statistical period, the neighbor network devices of the network device 1 are the network device 2 and the network device 3, that is, the link types corresponding to the network device 2 and the network device 3 are new, and if the network topology is snapshot at this time, the link types corresponding to the network device 2 and the network device 3 are changed to be normal. Assuming that, in the current statistical period, the neighboring network devices of the network device 1 are the network device 2 and the network device 4, the link type corresponding to the network device 2 existing in the current statistical period and existing before the snapshot is normal, the link type corresponding to the network device 4 existing in the current statistical period and not existing before the snapshot is newly added, and the link type corresponding to the network device 3 existing in the current statistical period and existing in the previous statistical period is offline.
Continuing with FIG. 2B, after the snapshot is performed, it is modified to be new for normal link types (transition 5) and invalid for offline link types (transition 6), assuming the snapshot is cancelled. For example, since the link type corresponding to the network device 2 is normal, the link type corresponding to the network device 4 is newly added, and the link type corresponding to the network device 3 is offline, the link type corresponding to the network device 2 may be modified to be newly added, and the link type corresponding to the network device 3 may be modified to be invalid.
After the above processing, the link type can be obtained, and by displaying the link type on the network topology, network management personnel can know the change condition of the network topology based on the link type. For example, if the link type corresponding to the network device 2 is normal, the link type corresponding to the network device 4 is newly added, and the link type corresponding to the network device 3 is offline, the network manager can know that: network device 2 was a neighbor network device of network device 1 before the snapshot, while network device 4 was not a neighbor network device of network device 1 before the snapshot, but was a neighbor network device of network device 1 after the snapshot, while network device 3 was a neighbor network device of network device 1 before the snapshot, but was not a neighbor network device of network device 1 after the snapshot.
In the above process, there may be operations involved when the network topology is to be snapshot. In one example, the management device may snapshot the network topology upon receiving a snapshot command input by a user. In another example, the management device may periodically snapshot the network topology. In another example, the management device may take a snapshot of the network topology each time the network topology changes.
And sixthly, the management device deletes the invalid neighbor network device of the network device 1.
in one example, at each statistical period, the management device may determine a neighbor network device having a neighbor relationship with the network device, and delete a neighbor network device that does not exist in the current statistical period and exists in the previous statistical period from the neighbor relationship of the network device. For example, for a neighbor network device where the current statistical period does not exist and the last statistical period exists, it indicates that the previous statistical period of the neighbor network device is a neighbor of the network device 1, but is not a neighbor of the network device 1 in the current statistical period, that is, the neighbor network device is already an invalid neighbor network device of the network device 1, and therefore, the neighbor relationship between the network device 1 and the neighbor network device may be deleted, such as deleting the content related to the neighbor network device from table 1, and the neighbor network device is no longer a neighbor of the network device 1.
In practical applications, the management device may set a counter for the neighbor network device, where the initial value of the counter is 0. For example, in a first statistical period, if the neighboring network devices having a neighboring relationship with the network device 1 are the network device 2 and the network device 4, the counter of the network device 2 is 1, and the counter of the network device 4 is 1; in the second statistical period, if the neighboring network device having a neighboring relationship with the network device 1 is the network device 2, the counter of the network device 2 is 2, and the counter of the network device 4 is 1; in the second statistical period, a neighboring network device having a neighboring relationship with network device 1 is assumed to be network device 2,
the counter of the network device 2 is 3, and the counter of the network device 4 is 1; and so on.
on this basis, the management device may further set a threshold, when the counter corresponding to the neighbor network device having the neighbor relationship with the network device 1 is greater than or equal to the threshold, the neighbor relationship between the neighbor network device and the network device 1 is retained, and when the counter corresponding to the neighbor network device having the neighbor relationship with the network device 1 is smaller than the threshold, the neighbor relationship between the neighbor network device and the network device 1 is deleted.
The threshold may be a dynamic value, and may be less than or equal to the number of statistical cycles.
And seventhly, the management equipment maintains an adjacency matrix for storing the neighbor relation among the network equipment.
In order to more conveniently acquire the neighbor relation between the network devices, and then execute the operations related to the cases from the first case to the sixth case by using the neighbor relation, the management device may also maintain the adjacency matrix. Based on this adjacency matrix, the management device can know the neighbor relation of the network device. Assuming there are 6 network devices, the adjacency matrix may be as shown in table 2, and in the initial state, all positions are marked a, indicating that it is not a neighbor relation.
TABLE 2
In the subsequent process, assuming that the neighbor network devices of the network device 1 are the network device 2 and the network device 4, the mark a at the corresponding position is modified to the mark B, which indicates that the neighbor relationship is shown in table 3.
TABLE 3
| network device 1 | Network device 2 | Network device 3 | Network device 4 | network device 5 | Network device 6 | |
| Network device 1 | Mark A | Mark B | Mark A | Mark B | Mark A | Mark A |
| Network device 2 | Mark B | Mark A | Mark A | Mark A | mark A | Mark A |
| Network device 3 | mark A | Mark A | Mark A | Mark A | mark A | Mark A |
| Network device 4 | Mark B | Mark A | Mark A | Mark A | Mark A | Mark A |
| Network device 5 | Mark A | Mark A | Mark A | Mark A | Mark A | Mark A |
| Network device 6 | Mark A | mark A | mark A | Mark A | Mark A | Mark A |
In the subsequent process, assuming that other neighbor relations are known again, the adjacency matrix shown in table 3 is continuously adjusted, which is not described again, and the following description will be given by taking table 3 as an example. Based on table 3, the management device may know that the neighbor network devices of the network device 1 may be the network device 2 and the network device 4, the neighbor network device of the network device 2 is the network device 1, and the neighbor network device of the network device 4 is the network device 1.
Based on the same application concept as the method, the embodiment of the application also provides a network topology determining device, and the network topology determining device is applied to the management equipment. The network topology determining apparatus may be implemented by software, or may be implemented by hardware, or a combination of hardware and software. Taking a software implementation as an example, as a logical means, the device is formed by reading a corresponding computer program instruction in the nonvolatile memory through a processor of the management apparatus where the device is located. From a hardware aspect, as shown in fig. 3, for a hardware structure diagram of a management device in which the network topology determining apparatus provided by the present application is located, in addition to the processor and the nonvolatile memory shown in fig. 3, the management device may further include other hardware, such as a forwarding chip, a network interface, and a memory, which are responsible for processing a packet; from the hardware structure, the management device may also be a distributed device, and may include a plurality of interface cards, so as to perform the extension of message processing at the hardware level.
As shown in fig. 4, a structure diagram of a network topology determining apparatus proposed by the present application includes:
An obtaining module 11, configured to obtain topology information of a first network device, where the topology information includes a device level of the first network device; in the process of acquiring the device level of the first network device, receiving a first message sent by the first network device, wherein the first message carries identification information of a neighbor network device of the first network device; analyzing the identification information from the first message, and acquiring a device level corresponding to the identification information; determining the equipment level of the first network equipment according to the equipment level corresponding to the identification information;
A determining module 12, configured to determine a network topology according to the topology information of the first network device.
The obtaining module 11 is specifically configured to, in a process of determining a device level of the first network device according to the device level corresponding to the identification information, obtain a minimum device level from the device level corresponding to the identification information, and determine that the device level of the first network device is a sum of the minimum device level and a preset value.
The topology information acquired by the acquiring module 11 includes a link STP state, where the link is formed by connecting a first port on the first network device with a second port on a neighboring network device; the number of the first port and the second port is one or more; the obtaining module 11 is specifically configured to receive a second message sent by the first network device in a process of obtaining a link STP state of the first network device, where the second message carries state information of a first port; analyzing the state information of the first port from the second message; and determining the link STP state of the first network equipment according to the state information of the first port.
The obtaining module 11 is specifically configured to, in a process of determining a link STP state of the first network device according to state information of first ports, determine that the link STP state of the first network device is link blocking when the state information of each first port is a blocking state; when a first port with state information in a forwarding state exists, if the state information of a second port forming a link with the first port with the state information in the forwarding state is in the forwarding state, determining that the link STP state of the first network equipment is normal; and if the state information of each second port is a blocking state, determining that the port link STP state of the first network equipment is a link blocking state.
In an example, the topology information acquired by the acquiring module 11 further includes a link type, where the link type is a link type between the first network device and a neighboring network device;
The obtaining module 11 is specifically configured to, in a process of obtaining the link type of the first network device, determine, in each statistical period, a neighbor network device having a neighbor relationship with the first network device, and determine, according to a snapshot condition, the link type of the first network device and the neighbor network device;
wherein the snapshot condition comprises: the snapshot is not taken when the snapshot processing is not performed on the network topology, or the snapshot is taken when the snapshot processing is performed on the network topology.
In an example, the obtaining module 11 is specifically configured to, in a process of determining link types of the first network device and the neighbor network device according to a snapshot condition, determine that a link type corresponding to a neighbor network device existing in a current statistics period is new if the snapshot condition is not snapshot; determining that the link type corresponding to the neighbor network equipment without the current statistical period is invalid;
If the snapshot condition is a snapshot, determining that the current statistical period exists and the link type corresponding to the neighbor network equipment existing before the snapshot is normal; determining that the link types corresponding to the neighbor network devices which exist in the current statistical period and do not exist before the snapshot are newly added; determining that the link type corresponding to the neighbor network equipment does not exist in the current statistical period and exists before the snapshot is offline; and determining that the link type corresponding to the neighbor network equipment which does not exist in the current statistical period and does not exist before the snapshot is invalid.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, 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, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable 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.
Furthermore, 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.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, 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 storage media (which may include, but is not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A network topology determining method is applied to a management device, and is characterized by comprising the following steps:
Acquiring topology information of first network equipment, wherein the topology information comprises an equipment level of the first network equipment; the process of obtaining the device hierarchy of the first network device includes: receiving a first message sent by a first network device, wherein the first message carries identification information of a neighbor network device of the first network device; analyzing the identification information from the first message, and acquiring a device level corresponding to the identification information; determining the equipment level of the first network equipment according to the equipment level corresponding to the identification information;
determining a network topology according to the topology information of the first network equipment;
The process of determining the device level of the first network device according to the device level corresponding to the identification information specifically includes:
And acquiring a minimum device level from the device levels corresponding to the identification information, and determining that the device level of the first network device is the sum of the minimum device level and a preset value.
2. The method of claim 1, wherein the topology information includes a link STP state, wherein the link is formed by a first port on the first network device being connected to a second port on a neighboring network device; the number of the first port and the second port is one or more;
The process of acquiring the link STP state of the first network device specifically includes:
Receiving a second message sent by the first network device, wherein the second message carries state information of a first port;
analyzing the state information of the first port from the second message;
And determining the link STP state of the first network equipment according to the state information of the first port.
3. The method according to claim 2, wherein the determining the link STP state of the first network device according to the state information of the first port specifically comprises:
When the state information of each first port is a blocking state, determining that the link STP state of the first network equipment is a link blocking state; when a first port with state information in a forwarding state exists, if the state information of a second port forming a link with the first port with the state information in the forwarding state is in the forwarding state, determining that the link STP state of the first network equipment is normal; and if the state information of each second port is a blocking state, determining that the port link STP state of the first network equipment is a link blocking state.
4. The method of claim 1, wherein the topology information comprises a link type, and wherein the link type is a link type between the first network device and a neighboring network device;
The process of obtaining the link type of the first network device specifically includes:
in each statistical period, determining neighbor network equipment having a neighbor relation with the first network equipment, and determining the link types of the first network equipment and the neighbor network equipment according to the snapshot condition;
Wherein the snapshot condition comprises: the snapshot is not taken when the snapshot processing is not performed on the network topology, or the snapshot is taken when the snapshot processing is performed on the network topology.
5. The method according to claim 4, wherein the process of determining the link type of the first network device and the neighbor network device according to the snapshot condition specifically includes:
If the snapshot condition is not snapshot, determining that the link type corresponding to the neighbor network equipment existing in the current statistical period is new; determining that the link type corresponding to the neighbor network equipment without the current statistical period is invalid;
If the snapshot condition is a snapshot, determining that the current statistical period exists and the link type corresponding to the neighbor network equipment existing before the snapshot is normal; determining that the link types corresponding to the neighbor network devices which exist in the current statistical period and do not exist before the snapshot are newly added; determining that the link type corresponding to the neighbor network equipment does not exist in the current statistical period and exists before the snapshot is offline; and determining that the link type corresponding to the neighbor network equipment which does not exist in the current statistical period and does not exist before the snapshot is invalid.
6. A network topology determining apparatus applied to a management device, the apparatus comprising:
An obtaining module, configured to obtain topology information of a first network device, where the topology information includes a device level of the first network device; in the process of acquiring the device level of the first network device, receiving a first message sent by the first network device, wherein the first message carries identification information of a neighbor network device of the first network device; analyzing the identification information from the first message, and acquiring a device level corresponding to the identification information; determining the equipment level of the first network equipment according to the equipment level corresponding to the identification information;
The determining module is used for determining network topology according to the topology information of the first network equipment;
The obtaining module is specifically configured to, in a process of determining the device level of the first network device according to the device level corresponding to the identification information, obtain a minimum device level from the device level corresponding to the identification information, and determine that the device level of the first network device is a sum of the minimum device level and a preset value.
7. The apparatus according to claim 6, wherein the topology information obtained by the obtaining module includes a link STP state, the link is formed by a connection between a first port on the first network device and a second port on a neighboring network device; the number of the first port and the second port is one or more;
The obtaining module is specifically configured to receive a second message sent by the first network device in a process of obtaining a link STP state of the first network device, where the second message carries state information of a first port; analyzing the state information of the first port from the second message; and determining the link STP state of the first network equipment according to the state information of the first port.
8. The apparatus according to claim 7, wherein the obtaining module is specifically configured to, in a process of determining the link STP state of the first network device according to the state information of the first port, determine that the link STP state of the first network device is link blocking when the state information of each first port is a blocking state; when a first port with state information in a forwarding state exists, if the state information of a second port forming a link with the first port with the state information in the forwarding state is in the forwarding state, determining that the link STP state of the first network equipment is normal; and if the state information of each second port is a blocking state, determining that the port link STP state of the first network equipment is a link blocking state.
9. The apparatus of claim 6,
The topology information acquired by the acquisition module further includes a link type, and the link type is a link type between the first network device and a neighboring network device;
The acquiring module is specifically configured to, during the process of acquiring the link type of the first network device, determine, in each statistical cycle, a neighbor network device having a neighbor relationship with the first network device, and determine, according to a snapshot condition, the link type of the first network device and the neighbor network device;
Wherein the snapshot condition comprises: the snapshot is not taken when the snapshot processing is not performed on the network topology, or the snapshot is taken when the snapshot processing is performed on the network topology.
10. the apparatus of claim 9,
the acquiring module is specifically configured to, in a process of determining the link types of the first network device and the neighbor network devices according to a snapshot condition, determine that a link type corresponding to a neighbor network device existing in a current statistics period is newly added if the snapshot condition is not snapshot; determining that the link type corresponding to the neighbor network equipment without the current statistical period is invalid;
if the snapshot condition is a snapshot, determining that the current statistical period exists and the link type corresponding to the neighbor network equipment existing before the snapshot is normal; determining that the link types corresponding to the neighbor network devices which exist in the current statistical period and do not exist before the snapshot are newly added; determining that the link type corresponding to the neighbor network equipment does not exist in the current statistical period and exists before the snapshot is offline; and determining that the link type corresponding to the neighbor network equipment which does not exist in the current statistical period and does not exist before the snapshot is invalid.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710209970.6A CN107104824B (en) | 2017-03-31 | 2017-03-31 | Network topology determination method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710209970.6A CN107104824B (en) | 2017-03-31 | 2017-03-31 | Network topology determination method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107104824A CN107104824A (en) | 2017-08-29 |
| CN107104824B true CN107104824B (en) | 2019-12-06 |
Family
ID=59674780
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710209970.6A Active CN107104824B (en) | 2017-03-31 | 2017-03-31 | Network topology determination method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107104824B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109981329A (en) * | 2017-12-28 | 2019-07-05 | 华为终端有限公司 | Determine the method, equipment and system of network equipment connection relationship |
| CN109510726A (en) * | 2018-12-21 | 2019-03-22 | 深圳市万网博通科技有限公司 | Network visualization implementation method, device, computer equipment and storage medium |
| CN109831334B (en) * | 2019-02-20 | 2022-03-08 | 普联技术有限公司 | Network topology construction method and device and terminal equipment |
| CN112688805B (en) * | 2020-12-17 | 2023-02-28 | 上海燧原科技有限公司 | Enumeration method and device for topological structure of chip cluster |
| CN113312734B (en) * | 2021-05-12 | 2023-07-04 | 广东顺畅科技有限公司 | Ammeter network topology generation method and device and computer readable storage medium |
| CN113568918A (en) * | 2021-06-11 | 2021-10-29 | 济南浪潮数据技术有限公司 | Method, system, equipment and medium for reporting information change |
| CN113542015B (en) * | 2021-06-29 | 2022-09-27 | 武汉思普崚技术有限公司 | Method for automatically drawing network physical link |
| CN115701044A (en) * | 2021-07-21 | 2023-02-07 | 华为技术有限公司 | Method and device for acquiring network topology |
| CN116137594B (en) * | 2021-11-18 | 2024-09-13 | 中国移动通信集团重庆有限公司 | Method, device, equipment and storage medium for generating network topology |
| CN116232902A (en) * | 2021-12-02 | 2023-06-06 | 大唐移动通信设备有限公司 | Network topology acquisition method, device, controller and core network element |
| CN114584470A (en) * | 2022-03-10 | 2022-06-03 | 北京自如信息科技有限公司 | Network equipment topological graph generation method and device and electronic equipment |
| CN117390801A (en) * | 2023-09-27 | 2024-01-12 | 上海格蒂电力科技有限公司 | Method and device for quickly identifying topological structure of power distribution network |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6654802B1 (en) * | 1999-02-12 | 2003-11-25 | Sprint Communications Company, L.P. | Network system and method for automatic discovery of topology using overhead bandwidth |
| CN102045190A (en) * | 2009-10-21 | 2011-05-04 | 杭州华三通信技术有限公司 | Network topology discovery method and device |
| CN102790950A (en) * | 2011-05-18 | 2012-11-21 | 中兴通讯股份有限公司 | Methods for neighbor topology discovery and cooperative communication of multi-interface terminal and multi-interface terminal |
| CN104158747A (en) * | 2013-05-14 | 2014-11-19 | 中兴通讯股份有限公司 | Network topology discovery method and system |
| CN104320345A (en) * | 2014-10-30 | 2015-01-28 | 杭州华三通信技术有限公司 | Method and device for collecting topological information in SDN network |
| WO2015171329A1 (en) * | 2014-05-06 | 2015-11-12 | Lattice Semiconductor Corporation | Network topology discovery |
-
2017
- 2017-03-31 CN CN201710209970.6A patent/CN107104824B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6654802B1 (en) * | 1999-02-12 | 2003-11-25 | Sprint Communications Company, L.P. | Network system and method for automatic discovery of topology using overhead bandwidth |
| CN102045190A (en) * | 2009-10-21 | 2011-05-04 | 杭州华三通信技术有限公司 | Network topology discovery method and device |
| CN102790950A (en) * | 2011-05-18 | 2012-11-21 | 中兴通讯股份有限公司 | Methods for neighbor topology discovery and cooperative communication of multi-interface terminal and multi-interface terminal |
| CN104158747A (en) * | 2013-05-14 | 2014-11-19 | 中兴通讯股份有限公司 | Network topology discovery method and system |
| WO2015171329A1 (en) * | 2014-05-06 | 2015-11-12 | Lattice Semiconductor Corporation | Network topology discovery |
| CN104320345A (en) * | 2014-10-30 | 2015-01-28 | 杭州华三通信技术有限公司 | Method and device for collecting topological information in SDN network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107104824A (en) | 2017-08-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107104824B (en) | Network topology determination method and device | |
| CN109981493B (en) | Method and device for configuring virtual machine network | |
| US20140172919A1 (en) | Automatic correlation of dynamic system events within computing devices | |
| CN108712286A (en) | The determination method, apparatus and storage medium of network topology structure | |
| CN109831334B (en) | Network topology construction method and device and terminal equipment | |
| US10241847B2 (en) | Anomaly detection using sequences of system calls | |
| US11831492B2 (en) | Group-based network event notification | |
| CN111131079B (en) | Policy query method and device | |
| CN107977254B (en) | Method for responding to request in cloud data system and computer-readable storage medium | |
| CN105247814B (en) | The method and apparatus for managing the physical location of the network equipment | |
| CN114398397A (en) | Data processing method, device, storage medium and system | |
| CN107526690B (en) | Method and device for clearing cache | |
| JP6501924B2 (en) | Method and server for canceling alert | |
| CN106411545A (en) | Service attribute counting method and device | |
| CN107547382B (en) | Neighbor relation discovery method and device | |
| CN113965492A (en) | Data flow statistical method and device | |
| CN115296985B (en) | Breakpoint positioning method and device and electronic equipment | |
| CN108259214B (en) | Configuration command management method, device and machine-readable storage medium | |
| CN105634999A (en) | Aging method and device for medium access control address | |
| CN103970860B (en) | Method, device and system for processing data | |
| CN111897983A (en) | Network topological graph generation method, device and system based on graph database | |
| CN110633274A (en) | Alarm management method and device | |
| CN104808985B (en) | The management method and device of object in application program | |
| CN108737522A (en) | A kind of processing method of message, device and system | |
| CN111221847A (en) | Monitoring data storage method and device and computer 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 | ||
| CB02 | Change of applicant information |
Address after: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province Applicant after: Xinhua Sanxin Information Technology Co., Ltd. Address before: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province Applicant before: Huashan Information Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |