CN108337111B - Method and device for acquiring network node topology - Google Patents

Method and device for acquiring network node topology Download PDF

Info

Publication number
CN108337111B
CN108337111B CN201810010649.XA CN201810010649A CN108337111B CN 108337111 B CN108337111 B CN 108337111B CN 201810010649 A CN201810010649 A CN 201810010649A CN 108337111 B CN108337111 B CN 108337111B
Authority
CN
China
Prior art keywords
port
message
state information
neighbor
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
Application number
CN201810010649.XA
Other languages
Chinese (zh)
Other versions
CN108337111A (en
Inventor
宋小恒
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou H3C Technologies Co Ltd
Original Assignee
Hangzhou H3C Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou H3C Technologies Co Ltd filed Critical Hangzhou H3C Technologies Co Ltd
Priority to CN201810010649.XA priority Critical patent/CN108337111B/en
Publication of CN108337111A publication Critical patent/CN108337111A/en
Application granted granted Critical
Publication of CN108337111B publication Critical patent/CN108337111B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

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
    • 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
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks

Landscapes

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

Abstract

The disclosure relates to a method and a device for acquiring network node topology. The method comprises the following steps: receiving a Link Layer Discovery Protocol (LLDP) message through a first port; analyzing the LLDP message to acquire neighbor state information of the first port; when monitoring the neighbor change of the first port according to the neighbor state information, recording the neighbor state information after the change of the first port, and reporting the neighbor state information after the change of the first port to a controller through a first message. The switch learns the neighbor state information of the physical port through the LLDP protocol, and when the neighbor change is monitored, the switch timely informs the controller of the neighbor state information of the port through a first message. Therefore, the controller does not need to receive the LLDP message and the ARP message at regular time to maintain the physical connection relationship of the network equipment, the protocol interaction of a signaling channel between the controller and the switch is reduced, and the operation efficiency of the whole network is improved.

Description

Method and device for acquiring network node topology
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for acquiring a network node topology.
Background
An SDN (Software Defined Network) is a novel Network innovation architecture, and a core idea of the SDN is to separate a control plane and a forwarding plane of a Network device to realize flexible control of Network traffic, so as to provide a good platform for innovation of a core Network and application.
A controller and a switch in the SDN network establish a connection through an OpenFlow protocol, and an OpenFlow (OpenFlow) protocol is used as a signaling channel of a control plane and a forwarding plane, that is, signaling interaction is completed through the OpenFlow protocol, for example, the controller configures and manages the switch through the signaling channel. The controller needs to maintain the overall topology of the network, and sends a default flow table down on the switch, and the switch sends a message through the flow table.
The controller uses a packet out message to make the switch send an LLDP (Link Layer Discovery Protocol) message, after the LLDP message is sent by the switch, the opposite-end switch receives the LLDP message, and the opposite-end switch sends the received LLDP message to the controller through a packet in message. And the controller calculates the physical connection between the two switches through the device and port information in the LLDP message.
When the user virtual machine is accessed to the network, the ARP message is actively sent, the switch receives the ARP message and sends the received ARP message to the controller through the packetin message, and the controller discovers that the virtual machine is accessed to the switch through the information carried by the ARP message.
When the SDN network is large in scale, the controller needs to spend huge CPU resources to maintain the connection relationship between all network nodes, for example, when links between network nodes change, the controller needs to update the link state on one hand, and needs to update a large number of paths in the network on the other hand, which consumes very large resources.
Disclosure of Invention
In view of this, the present disclosure provides a method and an apparatus for obtaining a network node topology, where a controller no longer needs to send a packet tout message at regular time to actively trigger a switch to send an LLDP message for detecting a network topology, and also no longer needs to receive a packetin message encapsulated based on the LLDP message or an ARP message at regular time to maintain a physical connection relationship of a network device, so that protocol interaction of a signaling channel between the controller and the switch device is reduced, resources of the controller are saved, and operating efficiency of the entire network is improved.
According to a first aspect of the present disclosure, there is provided a method for acquiring a network node topology, the method being applied to a switch in a software defined network SDN, and the method including:
receiving a Link Layer Discovery Protocol (LLDP) message through a first port;
analyzing the LLDP message to acquire neighbor state information of the first port;
when monitoring the neighbor change of the first port according to the neighbor state information, recording the neighbor state information after the change of the first port, and reporting the neighbor state information after the change of the first port to a controller through a first message.
In one possible implementation, the method further includes:
receiving a second message sent by the controller, wherein the second message comprises a first port identifier and a reporting enabling identifier field;
and if the reporting enabling identification field of the second message meets the preset condition, setting a port corresponding to the first port identification to report the neighbor state information of the port to the controller through the first message.
In one possible implementation, the method further includes:
receiving a third message sent by the controller, wherein the third message comprises a second port identifier;
and reporting the neighbor state information of the port corresponding to the second port identification to the controller through a fourth message.
According to a second aspect of the present disclosure, there is provided a method for acquiring a network node topology, the method being applied to a controller in an SDN, the method comprising:
receiving a first message sent by a switch, wherein the first message comprises neighbor state information of a first port of the switch;
the first message is parsed to obtain and save neighbor state information.
In one possible implementation, the method further includes:
and sending a second message to the switch, wherein the second message comprises the first port identifier and the reporting enabling identifier field, so that the switch sets a mode that the port corresponding to the first port identifier reports the neighbor state information of the port to the controller according to the reporting enabling identifier field of the second message.
In a possible implementation manner, the report enabling identification field meets a preset condition.
In one possible implementation, the method further includes:
and sending a third message to the switch, wherein the third message comprises a second port identifier, so that the switch reports the neighbor state information of the port corresponding to the second port identifier to the controller through a fourth message after receiving the third message.
In one possible implementation, the neighbor state information includes a physical address, an IP address, an egress port, and a device type of a device connected to the first port.
In one possible implementation, the second Message is a Port Modification Message.
In a possible implementation manner, the first Message is a Port Status Message, and an experimental Experimenter field of the Port Status Message carries neighbor Status information.
According to a third aspect of the present disclosure, there is provided an apparatus for obtaining a network node topology, the apparatus being applied to a switch in a software defined network, SDN, and the apparatus comprising:
a first receiving module, configured to receive a link layer discovery protocol LLDP message through a first port;
the first analysis module is used for analyzing the LLDP message to acquire neighbor state information of the first port;
the first reporting module is used for recording the neighbor state information of the first port after the change when the neighbor change of the first port is monitored according to the neighbor state information, and reporting the neighbor state information of the first port after the change to the controller through a first message.
According to a fourth aspect of the present disclosure, there is provided an apparatus for acquiring a network node topology, the apparatus being applied to a controller in an SDN, the apparatus comprising:
the second receiving module is used for receiving a first message sent by a switch, wherein the first message comprises neighbor state information of a first port of the switch;
and the second analysis module is used for analyzing the first message to acquire and store the neighbor state information.
According to a fifth aspect of the present disclosure, there is provided an apparatus for obtaining a network node topology, the apparatus comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the method of any one of the first to second aspects of the disclosure.
According to another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the method of any one of the first to second aspects of the present disclosure.
The switch learns the neighbor state information of the physical port through the LLDP protocol so as to monitor the neighbor change of the switch port connection. When the neighbor change is monitored, the switch informs the neighbor state information of the port to the controller in time through the first message. Therefore, the controller can timely acquire the connection relationship between switch devices in the SDN and the connection relationship between the user virtual machine and the access switch, a packetout message does not need to be sent regularly to actively trigger the switch to send the LLDP message to detect the network topology, the controller does not need to receive the packetin message encapsulated based on the LLDP message or the ARP message regularly to maintain the physical connection relationship of the network devices, the protocol interaction of a signaling channel between the controller and the switch is reduced, and the operation efficiency of the whole network is improved. Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.
Fig. 1 shows a flowchart of a method of obtaining a network node topology according to an embodiment of the present disclosure.
Fig. 2 illustrates a schematic diagram of an exemplary LLDP message according to the present disclosure.
Fig. 3 shows a flowchart of a method of obtaining a network node topology according to an embodiment of the present disclosure.
Fig. 4 shows a flowchart of a method of obtaining a network node topology according to an embodiment of the present disclosure.
Fig. 5 shows a flowchart of a method of obtaining a network node topology according to an embodiment of the present disclosure.
Fig. 6 shows a flowchart of a method of obtaining a network node topology according to an embodiment of the present disclosure.
Fig. 7 is a schematic application scenario diagram illustrating a method for acquiring a network node topology according to an embodiment of the present disclosure.
Fig. 8 shows a block diagram of an apparatus for obtaining a network node topology according to an embodiment of the present disclosure.
Fig. 9 shows a block diagram of an apparatus for obtaining a network node topology according to an embodiment of the present disclosure.
Fig. 10 shows a block diagram of an apparatus for obtaining a network node topology according to an embodiment of the present disclosure.
Fig. 11 shows a block diagram of an apparatus for obtaining a network node topology according to an embodiment of the present disclosure.
Fig. 12 shows a block diagram of an apparatus for obtaining a network node topology according to an embodiment of the present disclosure.
Detailed Description
Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers can indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.
The connection relation collection mode of network nodes of the SDN is greatly influenced by the network scale at present, a controller needs to trigger sending of an LLDP message at regular time and receive a packetin message from a switch to discover and maintain links among the network nodes; the controller also needs to receive the ARP message of the virtual machine periodically to discover and maintain the online status of the virtual machine, which consumes very large resources.
In order to solve the technical problem, the Openflow switch learns the neighbor information of the physical Port through an LLDP protocol, identifies the device type of the neighbor and timely discovers the user virtual machine on the access side, and uses a Port Status Message to timely notify the neighbor state information of the Port to the controller. The controller can timely acquire the connection relationship between switch devices in a network and the connection relationship between a user virtual machine and an access switch, the controller does not need to send a packet tout message regularly to actively trigger the switch to send an LLDP message to detect the network topology, and does not need to receive a packet tin message encapsulated based on the LLDP message or an ARP message regularly to maintain the physical connection relationship of the network devices, so that the protocol interaction of a signaling channel between the controller and the switch devices is reduced, the resources of the controller are saved, and the operating efficiency of the whole network is improved.
Fig. 1 shows a flowchart of a method of obtaining a network node topology according to an embodiment of the present disclosure. The method may be applied to a switch in an SDN, such as an OF switch (i.e., an Openflow switch), as shown in fig. 1, and is specifically described as follows.
Step S11, receiving a link layer discovery protocol LLDP message through the first port.
The first port may be a port of a switch, and a switch may include one or more ports through which the switch may send and receive messages, such as LLDP messages.
In an SDN supporting an Openflow protocol, taking an Openflow switch as an example, an LLDP protocol function may be opened on a port of the switch, and the switch may send an LLDP message to another switch or receive an LLDP message sent by another switch through the port. If the user virtual machine supports the LLDP protocol, an LLDP message may be sent to a switch in the SDN.
Fig. 2 is a schematic diagram of an exemplary LLDP packet according to the present disclosure, and as shown in fig. 2, the LLDP packet may carry a physical address of a device sending the LLDP packet, an IP address, an egress port identification port id, a device type, and the like. The physical address may be an address uniquely identifying an identity of the device that sends the LLDP packet, for example, an MAC address of the device; the output port may be a port of a device that sends the LLDP packet, that is, a port of a neighbor device connected to the local; the device type may be an exchange or a user virtual machine, for example, the device type carried by the LLDP message sent by the exchange is the exchange, and the device type carried by the LLDP message sent by the user virtual machine is the user virtual machine; the IP address and the device type are carried by using an extension field of the LLDP message.
Step S12, the LLDP message is parsed to obtain the neighbor state information of the first port.
The neighbor state information includes a physical address, an IP address, an egress port, and a device type of the device that sends the LLDP packet.
After receiving the LLDP message, the switch may analyze the LLDP message according to the LLDP protocol, and obtain the neighbor state information of the first port carried by the LLDP message.
Step S13, when the neighbor change of the first port is monitored according to the neighbor state information, recording the neighbor state information after the change of the first port, and reporting the neighbor state information after the change of the first port to the controller through the first message.
The neighbor change of the first port may refer to a change of a neighbor device connected to the first port, for example, at least one of information of a newly found neighbor, a lost neighbor, connected neighbor port information, or neighbor state information is changed.
In a possible implementation manner, the switch may record and store the neighbor state information, and may monitor the neighbor change of the first port according to the locally recorded neighbor state information and the received neighbor state information.
For example, as described above, the neighbor state information includes a physical address, an IP address, an egress port, a device type, and the like of a neighbor device connected to the first port, the switch analyzes the LLDP message after receiving the LLDP message to obtain the neighbor state information, the switch may locally search the recorded neighbor state information, if the same record can be searched, it indicates that the neighbor connected to the first port is not changed, if records having the same physical address but different egress ports are searched, it may indicate that the neighbor port connected to the first port is changed, and if the record having the same physical address is not searched, it may indicate that the first port of the switch newly finds (connects) one neighbor, and so on.
When monitoring that the neighbor connected with the first port changes, the switch can record the neighbor state information after the change of the first port so as to update the neighbor connected with the first port. For example, if the switch monitors that the first port is newly connected with a neighbor, a new neighbor state information record can be created, and a new neighbor of the first port is recorded; if the switch monitors that the neighbor port connected to the first port changes, the originally recorded egress port of the neighbor may be updated to the egress port included in the neighbor state information of the first port, or the original record of the neighbor may be deleted, and a new neighbor state information record may be created, which is not limited by the present disclosure.
When monitoring that the neighbor connected to the first port changes, the switch may also report the neighbor state information after the change of the first port to the controller, where the reporting may be through the first message.
In a possible implementation manner, the neighbor state information may be carried by an Experimenter field of the Port Status Message, where the Experimenter field is an experimental field specified by an Openflow protocol and may carry any private data.
After receiving the Port Status Message (first Message) sent by the switch, the controller may determine the neighbor Status information by parsing the Port Status Message, for example, may parse the latest neighbor Status information of the Port from the Experimenter field, and update the device content connected to the Port of the switch according to the neighbor Status information obtained by parsing.
Optionally, when the neighbor change of the first port is not monitored, the switch does not send the first message to report the neighbor state information of the first port, and the connection relationship of the port of the switch on the controller is not changed.
The switch learns the neighbor state information of the physical port through the LLDP protocol so as to monitor the neighbor change of the switch port connection. When the neighbor change is monitored, the switch can inform the controller of the neighbor state information of the port in time through the first message. Therefore, the controller can timely acquire the connection relationship between switch devices in the SDN and the connection relationship between the user virtual machine and the access switch, and does not need to regularly send a packet tout message to actively trigger the switch to send an LLDP message for network topology detection, and does not need to regularly receive a packet tin message encapsulated based on the LLDP message or the ARP message to maintain the physical connection relationship of the network devices, so that protocol interaction of a signaling channel between the controller and the switch is reduced, and the operation efficiency of the whole network is improved.
For example, as described above, after receiving the Port Status Message sent by the switch, the controller may parse the latest neighbor state information of the first Port from the Experimenter field, and update the device content connected to the first Port of the switch according to the neighbor state information obtained by parsing. Therefore, the controller can acquire the device connected to each port of each switch and the device type, thereby acquiring the connection relationship between the network devices, that is, acquiring the network node topology.
Fig. 3 shows a flowchart of a method of obtaining a network node topology according to an embodiment of the present disclosure. The method may be applied to a switch in an SDN, such as an OF switch (i.e., Openflow switch), and as shown in fig. 3, the method may further include the following steps.
Step S14, receiving a second message sent by the controller, where the second message includes the first port identifier and the report-enabled identifier field.
Step S15, if the reporting enable flag field of the second message satisfies the preset condition, setting the port corresponding to the first port identifier to report the neighbor state information of the port to the controller through the first message.
The second Message may be a Port Modification Message, where the Port Modification Message includes a first Port identifier, and the first Port identifier may be information capable of uniquely identifying a Port identity. For example, in order to enable the switch to report the neighbor state information of the first port according to the requirement of the controller, the controller may set a manner in which the switch reports the neighbor state information of the first port by sending the second message.
In a possible implementation manner, the second message may include a reporting-enabling-identification field, and the reporting-enabling-identification field may include different state information, for example, the reporting-enabling-identification field may include a first state and a second state, where the first state may indicate that the setup switch reports the neighbor state information of the first port to the controller through the first message, and the second state may indicate that the setup switch reports the neighbor state information of the first port through the packetin message. The above way of setting up the switch to report the neighbor state information of its first port is merely an example, and does not limit the present disclosure in any way.
In an example, taking the Port Modification Message as an example, the reporting enabling identifier field may be a config field in the Port Modification Message, an OFPPC _ Port _ NEIGHBOR _ info bit in the config field may be in a first state, if the OFPPC _ Port _ NEIGHBOR _ info bit is set, the switch records the reporting enabling identifier of the Port corresponding to the Port identifier carried in the Message, and subsequently, once the NEIGHBOR of the Port changes, the switch reports the NEIGHBOR state information to the controller through the Port Status Message. The OFPPC _ PORT _ NEIGHBOR _ INFORM reset in the config field may be in the second state, and if the OFPPC _ PORT _ NEIGHBOR _ INFORM reset, the switch sends the LLDP packet to the controller through a packetin packet when receiving the LLDP packet.
For example: if OFPPC _ PORT _ NEIGHBOR _ INFORM is 1, the switch reports the NEIGHBOR state information to the controller through a Port Status Message; if the OFPPC _ PORT _ NEIGHBOR _ info is 0, the switch sends the LLDP message to the controller through a packetin message when receiving the LLDP message.
The above is merely one example of the present disclosure and is not intended to limit the present disclosure in any way.
In another example, if the controller does not send a Port Modification Message to the switch, the switch defaults to send a packet Message to the controller when receiving an LLDP Message.
After receiving the second message sent by the controller, the switch may determine the corresponding first port according to the first port identifier carried in the second message, and may further determine whether the reporting-enabled identifier field of the second message satisfies a preset condition, for example, whether the reporting-enabled identifier field is in the first state. If the reporting-enabled identifier field of the second message satisfies the preset condition (the reporting-enabled identifier field is in the first state), the switch may set the Port corresponding to the first Port identifier to report the neighbor state information of the Port to the controller through Port Status Messages.
The mode that the switch port reports the neighbor state information of the port is set through the second message, the mode that the neighbor state information of the switch port is acquired can be flexibly set according to the actual requirement of the network, and the operation efficiency of the whole network is improved.
Fig. 4 shows a flowchart of a method of obtaining a network node topology according to an embodiment of the present disclosure. The method may be applied to a switch in an SDN, such as an OF switch (i.e., Openflow switch), and as shown in fig. 4, the method may further include the following steps.
And step S16, receiving a third message sent by the controller, where the third message includes the second port identifier.
Step S17, reporting the neighbor state information of the port corresponding to the second port identifier to the controller through a fourth message.
The third Message may be a Port Description Request (Port Description Request) Multipart Message, and the third Message may include a second Port identifier, where the second Port identifier may refer to information capable of uniquely identifying a Port identity. The fourth message may be a message corresponding to the third message: the Port Description Reply (Port Description Reply) Multipart Message.
In order to enable the controller to actively acquire the neighbor state information of a certain port of the switch, the controller may send a third message to the switch. After receiving the third Message sent by the controller, the switch may determine that the second Port identifies the corresponding second Port, and then report the neighbor state information of the Port to the controller through a fourth Message (e.g., a Port Description Reply multicast Message). Specifically, after determining the second Port, the switch may locally search for neighbor state information of the second Port, and report the neighbor state information of the second Port to the controller through an Experimenter field of a Port Description Reply Multipart Message.
Through the mode, the controller can actively acquire the neighbor state information of the switch, so that the connection relations between the switch devices and between the switch and the user virtual machine are acquired, the connection change between the switch devices and the online and migration of the user virtual machine can be sensed more timely.
Optionally, the first message, the second message, the third message, and the fourth message may be sent and received through a signaling channel based on an Openflow protocol, which is pre-established between the controller and the switch.
Fig. 5 shows a flowchart of a method of obtaining a network node topology according to an embodiment of the present disclosure. The method may be applied to a controller in an SDN, as shown in fig. 5, and includes the following steps.
Step S21, receiving a first message sent by a switch, where the first message includes neighbor state information of a first port of the switch.
Step S22, the first message is parsed to obtain and save neighbor state information.
The neighbor state information includes a physical address, an IP address, an egress port, and a device type of a device connected to the switch port corresponding to the first message.
As described above, after receiving the Port Status Message (first Message) sent by the switch, the controller may obtain the neighbor state information of the first Port by parsing the Port Status Message, for example, may parse the latest neighbor state information of the Port from the Experimenter field. The controller may update the state information of the neighbor device connected to the port of the switch according to the neighbor state information obtained through parsing, for example, may update and store a physical address, an IP address, an egress port, a device type, and the like of the neighbor device connected to the port of the switch.
The controller may obtain a connection relationship between the network devices, that is, obtain a network node topology according to the obtained device and device type connected to each port of each switch.
The controller can establish the link connection relationship between the switches and the user virtual machine by receiving the first message of the switches, the controller does not need to send a packet tout message at regular time to actively trigger the switches to send an LLDP message to detect the network topology, the controller does not need to receive a packet tin message encapsulated based on the LLDP message or an ARP message at regular time to maintain the link connection relationship between the switches and the user virtual machine, and can sense the connection change between the switches and the online and migration of the user virtual machine more timely.
Fig. 6 shows a flowchart of a method of obtaining a network node topology according to an embodiment of the present disclosure. The method may be applied to a controller in an SDN, as shown in fig. 6, and further includes:
step S23, sending a second message to the switch, where the second message includes the first port identifier and the reporting-enabling identifier field, so that the switch sets a manner for the port corresponding to the first port identifier to report the neighbor state information of the port to the controller according to the reporting-enabling identifier field of the second message.
The second Message may be a Port Modification Message, where the Port Modification Message includes a first Port identifier, and the first Port identifier may be information capable of uniquely identifying a Port identity. For example, in order to enable the switch to report the neighbor state information of the first port according to the requirement of the controller, the controller may set a manner in which the switch reports the neighbor state information of the first port by sending the second message.
In a possible implementation manner, the second message may include a reporting-enabling-identification field, and the reporting-enabling-identification field may include different state information, for example, the reporting-enabling-identification field may include a first state and a second state, where the first state may indicate that the setup switch reports the neighbor state information of the first port to the controller through the first message, and the second state may indicate that the setup switch reports the neighbor state information of the first port through the packetin message. The above way of setting up the switch to report the neighbor state information of its first port is merely an example, and does not limit the present disclosure in any way.
In an example, taking the Port Modification Message as an example, the reporting enabling identifier field may be a config field in the Port Modification Message, an OFPPC _ Port _ NEIGHBOR _ information bit in the config field may be in a first state, if the OFPPC _ Port _ NEIGHBOR _ information bit is set, the switch records the reporting enabling identifier of the Port corresponding to the Port identifier carried in the Message, and subsequently, once the NEIGHBOR of the Port changes, the switch reports the NEIGHBOR state information thereof to the controller through a Port Status Message. The OFPPC _ PORT _ NEIGHBOR _ INFORM reset in the config field may be in the second state, and if the OFPPC _ PORT _ NEIGHBOR _ INFORM reset, the switch sends the LLDP packet to the controller through a packetin packet when receiving the LLDP packet.
For example: if OFPPC _ PORT _ NEIGHBOR _ INFORM is 1, the switch reports the NEIGHBOR state information to the controller through a Port Status Message; if the OFPPC _ PORT _ NEIGHBOR _ info is 0, the switch sends the LLDP message to the controller through a packetin message when receiving the LLDP message.
The above is merely one example of the present disclosure and is not intended to limit the present disclosure in any way.
In another example, if the controller does not send a Port Modification Message to the switch, the switch defaults to send a packet Message to the controller when receiving an LLDP Message.
After receiving the second message sent by the controller, the switch may determine the corresponding first port according to the first port identifier carried in the second message, and may further determine whether the reporting-enabled identifier field of the second message satisfies a preset condition, for example, whether the reporting-enabled identifier field is in the first state. If the reporting-enabled identifier field of the second message satisfies the preset condition (the reporting-enabled identifier field is in the first state), the switch may set the Port corresponding to the first Port identifier to report the neighbor state information of the Port to the controller through Port Status Messages.
The controller sends the second message to the switch to set the mode of reporting the neighbor state information of the port of the switch, so that the mode of acquiring the neighbor state information of the port of the switch can be flexibly set according to the actual requirement of the network, and the operation efficiency of the whole network is improved.
In one possible implementation, as shown in fig. 6, the method may further include:
step S24, sending a third message to the switch, where the third message includes the second port identifier, so that the switch reports the neighbor state information of the port corresponding to the second port identifier to the controller through a fourth message after receiving the third message.
Step S24 may be executed before or after step S21, which is not limited by the present disclosure.
The third Message may be a Port Description Request Multipart Message, and the third Message may include a second Port identifier, where the second Port identifier may be information capable of uniquely identifying a Port identity. The fourth message may be a message corresponding to the third message: a Port Description Reply Multipart Message.
In order to enable the controller to actively acquire the neighbor state information of a certain port of the switch, the controller may send a third message to the switch. After receiving the third Message sent by the controller, the switch may determine that the second Port identifies the corresponding second Port, and then report the neighbor state information of the Port to the controller through a fourth Message (e.g., a Port Description Reply multicast Message). Specifically, after determining the second Port, the switch may locally search for the neighbor state information of the second Port, and report the neighbor state information of the second Port to the controller through the Experimenter field of the Port Description Reply Multipart Message.
Through the mode, the controller can actively acquire the neighbor state information of the switch, so that the connection relations between the switch devices and between the switch and the user virtual machine are acquired, the connection change between the switch devices and the online and migration of the user virtual machine can be sensed more timely.
Optionally, the first message, the second message, the third message, and the fourth message may be sent and received through a signaling channel based on an Openflow protocol, which is pre-established between the controller and the switch.
Application example
Fig. 7 is a schematic application scenario diagram illustrating a method for acquiring a network node topology according to an embodiment of the present disclosure. In order to more clearly illustrate the method for acquiring the network node topology of the present disclosure, the following description is made in conjunction with possible application scenarios.
As shown in fig. 7, in the Openflow network, SW1, SW2, SW3, and SW4 are Openflow switches, all ports of the switches are opened with LLDP protocol functions and support LLDP protocols, VM10, VM20, VM30, and VM40 are user virtual machines, and the user virtual machines support LLDP protocols and can send LLDP messages to switches in the SDN. The SDN controller is connected with the SW1, the SW2, the SW3 and the SW4 through an Openflow protocol, the controller and the switch adopt the Openflow protocol as a signaling channel of a control layer and a forwarding layer, and signaling interaction is completed through the Openflow protocol.
The controller may request the switches SW1, SW2, SW3 and SW4 to report the neighbor state information of all ports through Port Status Message (first Message) by issuing a Port Modification Message (second Message) to the switches SW1, SW2, SW3 and SW 4. For example, a Message carrying multiple Port Modification messages may be issued to a switch (e.g., SW1), the number of Port Modification messages may be determined according to the number of switch ports, and each Port Modification Message may carry a different Port identifier.
The method comprises the steps that an OFPPC _ PORT _ NEIGHBOR _ INFORM is set in a config field of a Port Modification Message, a switch records a reporting enabling identifier of a Port corresponding to a Port identifier carried by the Message, and the switch reports NEIGHBOR state information of the Port to a controller through a Port Status Message once the NEIGHBOR of the Port corresponding to the Port identifier of the switch changes.
Initially, the SW switches (including SW1, SW2, SW3, and SW4) report local port information, and since the LLDP protocol negotiation is not completed, the port has no neighbor state information.
After the negotiation of the LLDP protocol is completed, the SW switch devices send LLDP messages to each other for link neighbor discovery, where the LLDP messages may include a physical address, an IP address, an egress port, a device type, and the like of the device that sends the messages.
Taking SW1 as an example, when SW1 sends an LLDP packet from port 4 to SW4 and receives an LLDP packet of SW4 from port 4, analyzing the LLDP packet sent by SW4 can obtain neighbor state information of port 4, including a physical address, an IP address, port 1, and a device type of SW 4. SW1 learns that port 4 is connected port 1 of SW4 and SW4 is an Openflow switch.
The SW1 finds that the neighbor state information of the Port 4 changes, and reports the neighbor state information of the Port 4 after the change to the controller through the Port Status Message, where the owner field of the Port Status Message includes the physical address, the IP address, the Port 1, and the device type (Openflow switch) of the SW 4.
The SW1 may also record the neighbor state information of the port 4, and when a new LLDP message is received through the port 4, compare the neighbor state information of the port 4 obtained by analyzing the new LLDP message with the already recorded neighbor state information of the port 4 to determine the neighbor change of the port 4.
The controller receives a Port Status Message including Port 4 neighbor state information of SW1 through a signaling channel, parses the neighbor state information of Port 4 from the Experimenter field, including a physical address, an IP address, a Port 1 and a device type of SW4 (Openflow switch), the controller can save that the neighbor of Port 4 of SW1 is SW4, the IP address of SW4, the connected Port of SW1 is Port 1, and SW4 is an Openflow switch.
Similarly, Port 1 of SW4 also receives the LLDP Message sent by SW1 from Port 4, SW4 discovers that the neighbor state information of Port 1 changes, discovers a new neighbor, reports the neighbor state information of Port 1 to the controller through a Port Status Message, the controller stores the neighbor of Port 1 of SW4 as SW1, the IP address of SW1, the connected Port of SW4 as Port 4, and SW1 as an Openflow switch.
The neighbor state information of the ports of other SW switches is also reported in the same way, and then the controller can obtain the physical connection relation between the SW switches according to the neighbor state information of the ports reported by the SW switches, so that the network node topological relation can be obtained.
Taking the user virtual machine VM10 as an example, the user virtual machine VM10 sends an LLDP message through port 1, and carries its own physical address, IP address, port 1, and device type (user virtual machine).
The SW1 receives the LLDP message from the port 10, and parses the LLDP message sent by the VM10 to obtain the neighbor state information of the port 10, including the physical address, IP address, port 1, and device type of the VM 10. SW1 learns that port 10 is connected port 1 of VM10 and VM10 is a user virtual machine.
The SW1 can locally search the recorded neighbor state information, and not search the record with the same physical address, the SW1 finds that the neighbor state information of the Port 10 changes, finds a new neighbor, and reports the neighbor state information of the Port 10 to the controller through the Port Status Message, where the Experimenter field of the Port Status Message includes the physical address, IP address, Port 1, and device type (user virtual machine) of the VM 10.
The SW1 may also record the acquired neighbor state information of the port 10, and when a new LLDP message is received through the port 10, compare the neighbor state information of the port 10 acquired by analyzing the new LLDP message with the already recorded neighbor state information of the port 10 to determine the neighbor change of the port 10.
The controller receives the Port Status Message including Port 10 neighbor Status information of SW1, parses the neighbor Status information of Port 10 from the Experimenter field, including the physical address, IP address, Port 1, and device type of VM10, the controller may save that the neighbor of Port 10 of SW1 is VM10, the IP address of VM10, the Port of connected VM10 is Port 1, and VM10 is a user virtual machine.
Other user virtual machines can also send LLDP messages, and the controller can obtain the connection relation between the SW exchanger and the user virtual machines.
The controller can also directly send a Port Description Request Multipart Message to the SW1, the Port identifier carried by the Port Description Request Multipart Message is Port 4, after receiving the Port Description Request Multipart Message sent by the controller, the SW1 can locally search the recorded neighbor state information of the Port 4, and if the neighbor state information of the Port 4 is recorded, the SW1 can report the neighbor state information of the Port 4 to the controller through the identifier field of the Port Description Reply Multipart Message.
By the mode, the controller can obtain the connection relation between the whole network devices by using very small CPU computing resources, the controller is not required to send a packetout message at regular time to actively trigger the switch to send an LLDP message to detect the network topology, the controller is not required to receive a packetin message packaged based on the LLDP message or the ARP message at regular time to maintain the physical connection between the network nodes, the protocol interaction of a signaling channel between the controller and the switch is reduced, and the operation efficiency of the whole network is improved.
Fig. 8 shows a block diagram of an apparatus for obtaining a network node topology according to an embodiment of the present disclosure. The apparatus may be applied to a switch in an SDN, as shown in fig. 8, and includes:
a first receiving module 41, configured to receive a link layer discovery protocol LLDP message through a first port;
the first parsing module 42 is configured to parse the LLDP packet to obtain neighbor state information of the first port;
the first reporting module 43 is configured to record neighbor state information of the first port after the change when the neighbor change of the first port is monitored according to the neighbor state information, and report the neighbor state information of the first port after the change to the controller through a first message.
The switch learns the neighbor state information of the physical port through the LLDP protocol so as to monitor the neighbor change of the switch port connection. When the neighbor change is monitored, the switch can inform the controller of the neighbor state information of the port in time through the first message. Therefore, the controller can timely acquire the connection relationship between switch devices in the SDN and the connection relationship between the user virtual machine and the access switch, a packetout message does not need to be sent regularly to actively trigger the switch to send the LLDP message to detect the network topology, the controller does not need to receive the packetin message encapsulated based on the LLDP message or the ARP message regularly to maintain the physical connection relationship of the network devices, the protocol interaction of a signaling channel between the controller and the switch is reduced, and the operation efficiency of the whole network is improved.
Fig. 9 shows a block diagram of an apparatus for obtaining a network node topology according to an embodiment of the present disclosure.
Optionally, the apparatus may further include:
a third receiving module 44, configured to receive a second message sent by the controller, where the second message includes the first port identifier and the reporting-enabled identifier field;
and a setting module 45, configured to set, if the reporting-enabled identifier field of the second message meets a preset condition, a port corresponding to the first port identifier to report the neighbor state information of the port to the controller through the first message.
Optionally, the apparatus may further include:
a fourth receiving module 47, configured to receive a third message sent by the controller, where the third message includes a second port identifier;
and a second reporting module 48, configured to report the neighbor state information of the port corresponding to the second port identifier to the controller through a fourth message.
Optionally, the neighbor state information includes a physical address, an IP address, an egress Port, and a device type of a device connected to the first Port, the second Message is a Port Modification Message, the first Message is a Port state Message, and an experimental Experimenter field of the Port state Message carries the neighbor state information.
Fig. 10 shows a block diagram of an apparatus for obtaining a network node topology according to an embodiment of the present disclosure. The apparatus may be applied to a controller in an SDN, as shown in fig. 10, and includes:
a second receiving module 51, configured to receive a first message sent by a switch, where the first message includes neighbor state information of a first port of the switch;
and a second parsing module 52, configured to parse the first message to obtain and store the neighbor state information.
Fig. 11 shows a block diagram of an apparatus for obtaining a network node topology according to an embodiment of the present disclosure.
Optionally, the apparatus may further include:
the first sending module 53 is configured to send a second message to the switch, where the second message includes the first port identifier and the reporting-enabled identifier field, so that the switch sets, according to the reporting-enabled identifier field of the second message, a manner in which the port corresponding to the first port identifier reports the neighbor state information of the port to the controller.
Optionally, the report enabling identifier field meets a preset condition.
Optionally, the apparatus may further include:
the second sending module 54 is configured to send a third message to the switch, where the third message includes the second port identifier, so that the switch reports the neighbor state information of the port corresponding to the second port identifier to the controller through a fourth message after receiving the third message.
Optionally, the neighbor state information includes a physical address, an IP address, an egress Port, and a device type of a device connected to the first Port, the second Message is a Port Modification Message, the first Message is a Port state Message, and an experimental Experimenter field of the Port state Message carries the neighbor state information.
Optionally, in order to enable the controller to actively acquire the neighbor state information of a certain port of the switch, the controller may send a third message to the switch through the second sending module 54. After receiving the third Message sent by the controller, the switch may determine that the second Port identifies the corresponding second Port, and then report the neighbor state information of the Port to the controller through a fourth Message (e.g., a Port Description Reply multicast Message). Specifically, after determining the second Port, the switch may locally search for the neighbor state information of the second Port, and report the neighbor state information of the second Port to the controller through the Experimenter field of the Port Description Reply Multipart Message.
Through the mode, the controller can actively acquire the neighbor state information of the switch, so that the connection relations between the switch devices and between the switch and the user virtual machine are acquired, the connection change between the switch devices and the online and migration of the user virtual machine can be sensed more timely.
Fig. 12 is a block diagram illustrating an apparatus 900 for obtaining a network node topology, according to an example embodiment. Referring to fig. 12, the apparatus 900 may include a processor 901, a machine-readable storage medium 902 having stored thereon machine-executable instructions. The processor 901 and the machine-readable storage medium 902 may communicate via a system bus 903. Also, the processor 901 performs the above-described method of acquiring a network node topology by reading machine-executable instructions in the machine-readable storage medium 902 corresponding to logic of acquiring a network node topology.
The machine-readable storage medium 902 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein were chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the techniques in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims (13)

1. A method for acquiring network node topology, wherein the method is applied to a switch in a Software Defined Network (SDN), and the method comprises the following steps:
receiving a Link Layer Discovery Protocol (LLDP) message through a first port;
analyzing the LLDP message to acquire neighbor state information of the first port;
when monitoring the neighbor change of a first port according to neighbor state information, recording the neighbor state information of the first port after the change, and reporting the neighbor state information of the first port after the change to a controller through a first message; the first Message is a Port Status Message;
the method further comprises the following steps:
receiving a second Message sent by the controller, wherein the second Message is a Port Modification Message, and the second Message comprises a first Port identifier and a reporting enabling identifier field; the reporting enabling identification field comprises a first state or a second state;
if the reporting enabling identification field of the second message is in the first state, setting a port corresponding to the first port identification to report the neighbor state information of the port to the controller through the first message;
if the reporting enabling identification field of the second message is in the second state, the port corresponding to the first port identification is set to report the neighbor state information of the port to the controller through the packetin message.
2. The method of obtaining a network node topology of claim 1, further comprising:
receiving a third message sent by the controller, wherein the third message comprises a second port identifier;
and reporting the neighbor state information of the port corresponding to the second port identification to the controller through a fourth message.
3. The method of claim 1, wherein the neighbor state information comprises a physical address, an IP address, an egress port, and a device type of a device connected to the first port.
4. The method of obtaining the topology of network nodes according to any of claims 1-3, wherein the experimental Experimenter field of the Port Status Message carries neighbor state information.
5. A method for acquiring network node topology, wherein the method is applied to a controller in an SDN, and the method comprises the following steps:
receiving a first message sent by a switch, wherein the first message comprises neighbor state information of a first port of the switch; the first Message is a Port Status Message;
analyzing the first message to acquire and store neighbor state information;
the method further comprises the following steps:
and sending a second Message to the switch, wherein the second Message is a Port Modification Message, the second Message comprises a first Port identifier and a reporting enabling identifier field, the reporting enabling identifier field comprises a first state or a second state, so that when the reporting enabling identifier field of the second Message is the first state, the switch sets a Port corresponding to the first Port identifier to report the neighbor state information of the Port to the controller through the Port state Message, and when the reporting enabling identifier field of the second Message is the second state, the switch sets a Port corresponding to the first Port identifier to report the neighbor state information of the Port to the controller through a packetin Message.
6. The method of claim 5, wherein the report enable identifier field satisfies a predetermined condition.
7. The method of obtaining a network node topology according to claim 5, further comprising:
and sending a third message to the switch, wherein the third message comprises a second port identifier, so that the switch reports the neighbor state information of the port corresponding to the second port identifier to the controller through a fourth message after receiving the third message.
8. The method of claim 5, wherein the neighbor state information comprises a physical address, an IP address, an egress port, and a device type of a device connected to the first port.
9. The method of obtaining the topology of network nodes according to any of claims 5-7, wherein the experimental Experimenter field of the Port Status Message carries neighbor state information.
10. An apparatus for obtaining network node topology, the apparatus being applied to a switch in a Software Defined Network (SDN), the apparatus comprising:
a first receiving module, configured to receive a link layer discovery protocol LLDP message through a first port;
the first analysis module is used for analyzing the LLDP message to acquire neighbor state information of the first port;
the first reporting module is used for recording neighbor state information of a first port after the change when monitoring the neighbor change of the first port according to the neighbor state information, and reporting the neighbor state information of the first port after the change to a controller through a first message; the first Message is a Port Status Message;
the third receiving module is used for receiving a second Message sent by the controller, wherein the second Message is a Port Modification Message, and the second Message comprises a first Port identifier and a reporting enabling identifier field; the reporting enabling identification field comprises a first state or a second state;
the setting module is used for setting a port corresponding to the first port identifier to report the neighbor state information of the port to the controller through the port state information if the reporting enabling identification field of the second message is in the first state; if the reporting enabling identification field of the second message is in the second state, the port corresponding to the first port identification is set to report the neighbor state information of the port to the controller through the packetin message.
11. An apparatus for acquiring network node topology, the apparatus being applied to a controller in an SDN, the apparatus comprising:
the second receiving module is used for receiving a first message sent by a switch, wherein the first message comprises neighbor state information of a first port of the switch; the first Message is a Port Status Message;
the second analysis module is used for analyzing the first message to acquire and store the neighbor state information;
the first sending module is configured to send a second Message to the switch, where the second Message is a Port Modification Message, the second Message includes a first Port identifier and a reporting enable identifier field, and the reporting enable identifier field includes a first state or a second state, so that when the reporting enable identifier field of the second Message is the first state, the switch sets a Port corresponding to the first Port identifier to report neighbor state information of the Port to the controller through a Port state Message, and when the reporting enable identifier field of the second Message is the second state, sets a Port corresponding to the first Port identifier to report the neighbor state information of the Port to the controller through a packetin Message.
12. An apparatus for obtaining a topology of a network node, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the method of any of the preceding claims 1-9.
13. A non-transitory computer readable storage medium having stored thereon computer program instructions, wherein the computer program instructions, when executed by a processor, implement the method of any one of claims 1 to 9.
CN201810010649.XA 2018-01-05 2018-01-05 Method and device for acquiring network node topology Active CN108337111B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810010649.XA CN108337111B (en) 2018-01-05 2018-01-05 Method and device for acquiring network node topology

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810010649.XA CN108337111B (en) 2018-01-05 2018-01-05 Method and device for acquiring network node topology

Publications (2)

Publication Number Publication Date
CN108337111A CN108337111A (en) 2018-07-27
CN108337111B true CN108337111B (en) 2021-07-30

Family

ID=62923927

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810010649.XA Active CN108337111B (en) 2018-01-05 2018-01-05 Method and device for acquiring network node topology

Country Status (1)

Country Link
CN (1) CN108337111B (en)

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110213089B (en) * 2019-05-17 2022-02-15 烽火通信科技股份有限公司 Method and system for accessing large-scale remote zero configuration equipment to network management
CN110401568B (en) * 2019-07-31 2022-05-24 普联技术有限公司 Network topology discovery method and equipment
CN110430265A (en) * 2019-08-06 2019-11-08 北京奇艺世纪科技有限公司 A kind of method and device obtaining server and inter-exchange corresponding relationship
CN110545206B (en) * 2019-09-10 2021-02-02 清华大学 Method, device and system for generating scheduling table in time-triggered network
CN111030296B (en) * 2019-12-04 2021-09-10 国电南瑞南京控制系统有限公司 Intelligent substation network topology step-by-step sniffing method based on LLDP protocol
CN113098776B (en) * 2020-01-08 2022-07-29 中国移动通信有限公司研究院 Method, device, equipment and storage medium for determining network topology
CN111314140B (en) * 2020-02-19 2021-12-17 迈普通信技术股份有限公司 Method and device for improving stability of network equipment, network equipment and storage medium
CN113872787B (en) * 2020-06-30 2023-05-12 华为技术有限公司 Network topology discovery method, device and computer readable storage medium
CN114268536B (en) * 2020-09-16 2024-01-05 中盈优创资讯科技有限公司 Method and device for describing equipment port in full-automatic standard telecommunication network
CN112152862B (en) * 2020-10-16 2023-04-07 中国联合网络通信集团有限公司 Topology acquisition method of hybrid network, SDN controller and SDN switch
CN112654028B (en) * 2020-12-15 2022-04-26 烽火通信科技股份有限公司 Easymesh protocol-based networking management method and system
CN112968846B (en) * 2021-02-02 2022-08-16 武汉迈威通信股份有限公司 Detection system for illegal short circuit of switch port
CN113225210A (en) * 2021-04-20 2021-08-06 深圳市信锐网科技术有限公司 Link determination method, device, controller and storage medium
CN115701044A (en) * 2021-07-21 2023-02-07 华为技术有限公司 Method and device for acquiring network topology
CN116366455A (en) * 2021-12-28 2023-06-30 华为技术有限公司 Network system, network message processing method, device and storage medium
CN116094957A (en) * 2023-01-04 2023-05-09 中国联合网络通信集团有限公司 Port connection detection method, device and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104158747A (en) * 2013-05-14 2014-11-19 中兴通讯股份有限公司 Network topology discovery method and system
CN104283802A (en) * 2014-10-09 2015-01-14 杭州华三通信技术有限公司 Neighbor discovery method and device
CN104468415A (en) * 2013-09-16 2015-03-25 中兴通讯股份有限公司 Method and device for reporting switch type
CN104702479A (en) * 2015-03-10 2015-06-10 杭州华三通信技术有限公司 Tunnel building method and device in Software Defined Network (SDN)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105337853A (en) * 2014-06-11 2016-02-17 杭州华三通信技术有限公司 Instance establishing method and apparatus in software defined network (SDN)
CN104486119A (en) * 2014-12-16 2015-04-01 盛科网络（苏州）有限公司 Method and system for achieving batch management switch through improved openflow protocol
CN105007221B (en) * 2015-07-28 2018-07-24 上海斐讯数据通信技术有限公司 A kind of loop detecting method and system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104158747A (en) * 2013-05-14 2014-11-19 中兴通讯股份有限公司 Network topology discovery method and system
CN104468415A (en) * 2013-09-16 2015-03-25 中兴通讯股份有限公司 Method and device for reporting switch type
CN104283802A (en) * 2014-10-09 2015-01-14 杭州华三通信技术有限公司 Neighbor discovery method and device
CN104702479A (en) * 2015-03-10 2015-06-10 杭州华三通信技术有限公司 Tunnel building method and device in Software Defined Network (SDN)

Also Published As

Publication number Publication date
CN108337111A (en) 2018-07-27

Similar Documents

Publication Publication Date Title
CN108337111B (en) Method and device for acquiring network node topology
CN108111432B (en) Message forwarding method and device
BR112021013594A2 (en) SHARED STORAGE SYSTEM AND METHOD FOR NETWORK DATA ANALYSIS
EP3425856A1 (en) Service chain routing method and system
CN103763121A (en) Method and device for quickly issuing network configuration information
CN102859952A (en) Switch, and flow table control method
CN106878184B (en) Data message transmission method and device
CN111726293B (en) Message transmission method and device
CN110580256A (en) Method, device and system for identifying application identifier
CN110557342B (en) Apparatus for analyzing and mitigating dropped packets
KR20130109193A (en) Communication system, control device, communication method and program
WO2014114196A1 (en) Keeping a terminal access location record alive
CN107547283B (en) Management method and device of distributed aggregation group
CN112887229B (en) Session information synchronization method and device
US10404544B2 (en) Network topology determining method and apparatus, and centralized network status information storage device
CN104283802A (en) Neighbor discovery method and device
WO2016114750A1 (en) Data link layer information
JPWO2004093481A1 (en) Mobile communication system, radio base station accommodation control apparatus in mobile communication system, and control method therefor
JP7119174B2 (en) Network topology discovery method, network topology discovery device and network topology discovery system
CN114726780A (en) Communication method, device and storage medium from cloud to cloud
CN105763463B (en) Method and device for transmitting link detection message
CN107733727B (en) Zero configuration method, device and equipment
CN106972973B (en) Control method, controller and switch
CN112787930B (en) Method, device and storage medium for monitoring running state of peer
US20230106077A1 (en) Distributed Storage System, Exception Handling Method Thereof, and Related Apparatus

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