CN116032770A - LLDP-based topology link discovery method - Google Patents

Abstract

The invention discloses a topology link discovery method based on LLDP, which belongs to the technical field of data communication, and comprises the following steps: the method comprises the steps of sending a topology information query message to a first transfer node through a center node, judging whether the first transfer node and the center node have the same domain identification through the first transfer node, adding a system identification of the first transfer node to a first system identification field of the topology information query message under the condition that the first transfer node judges whether the first transfer node and the center node have the same domain identification, sending the topology information query message to the first node, adding a system identification of an edge node to the first system identification field of the topology information query message under the condition that the first node is an edge node, adding a system identification linked list in the first system identification field to a topology query information reply message, and sending the topology query information reply message to the center node so that the center node obtains topology path information through the system identification linked list.

Description

LLDP-based topology link discovery method

Technical Field

The invention belongs to the technical field of data communication, and particularly relates to a topology link discovery method based on LLDP.

Background

Currently, the discovery and maintenance of topology in DCN networks mainly adopts the OpenFlow protocol. However, the OpenFlow protocol is not enough abstract to the network, and cannot adapt to a large-scale wide area network deployment scenario. In addition, in the network controlled by the OpenFlow, a plurality of key devices in a control path of a controller are often required, so that operation and maintenance are difficult, signaling pressure is increased, and expandability is poor. In another protocol SR, although the problem of insufficient network OpenFlow network abstraction is solved, the SR is currently only applicable to MPLS networks and IPV6 networks, and meanwhile, a source routing mechanism adopted by the SR is to require that network devices must forward according to a forwarding table, if a forwarding next hop is not in a direct-connection subnet of the network device, a data packet is discarded, and meanwhile, an ICMP message is sent to a source host, and when the source host receives the ICMP failure message, a network topology path is updated. However, this mechanism presents a security risk, and some network devices react to the source routing packet by using their designated routes and use reverse routes to transfer reply data, so that an intruder can impersonate the host to obtain some protected data, thereby achieving the purpose of attacking or stealing confidential data.

Disclosure of Invention

The embodiment of the invention aims to provide a topology link discovery method and device based on LLDP (link layer discovery protocol) so as to solve the problem of performance bottleneck and potential safety hazard related problems of topology link discovery in a large-scale wide area network.

In order to solve the technical problems, the invention is realized as follows:

in a first aspect, an embodiment of the present invention provides a topology link discovery method based on LLDP, which is characterized in that the method includes:

sending a topology information query message to a first transfer node through a central node;

judging whether the first transfer node and the central node have the same domain identifier or not through the first transfer node;

under the condition that the first transfer node judges whether the first transfer node and the central node have the same domain identification, adding the system identification of the first transfer node into a first system identification field of the topology information query message;

sending the topology information inquiry message to a first node;

if the first node is an edge node, adding a system identifier of the edge node to a first system identifier field of the topology information query message;

Adding a system identification linked list in the first system identification field to a topology query information reply message;

sending the topology inquiry information reply message to the central node so that the central node obtains topology path information through the system identification linked list;

the system identification linked list is all system identifications in the first system identification field with a first sequence, the first sequence is an adding sequence of all system identifications, the topology information query message and the topology information reply message are LLDP messages, and a target field of the LLDP messages is defined with a system identification field.

Optionally, after the sending the topology information query packet to the first node, the method further includes:

acquiring a system identification linked list in the first system identification field under the condition that the first node is a second transit node;

and under the condition that the system identification of the second transfer node is different from the system identification in the system identification linked list, adding the system identification of the second transfer node into the first system identification field, and sending the topology information query message to the next node.

Optionally, after the obtaining the system identifier linked list in the first system identifier field, the method further includes:

and under the condition that the system identifier of the second transfer node is the same as at least one system identifier of the system identifier linked list in the first system identifier field, not sending the topology information inquiry message to the second transfer node and sending the topology information inquiry message to a next node.

Optionally, the sending the topology query information reply message to the central node includes:

determining corresponding nodes according to the system identifications in the system identification linked list, and sequentially sending the topology inquiry information reply messages to the corresponding nodes according to a second sequence so as to send the topology inquiry information to the central node;

wherein the second order is opposite to the first order.

Optionally, the adding the system identifier linked list in the first system identifier field to the topology query information reply message includes:

adding a system identification linked list in the first system identification field to a second system identification field in a topology query information reply message;

After the topology query information reply message is sent to the central node, the method further comprises:

and analyzing a second system identification field of the topology inquiry information reply message through the central node so that the central node obtains the system identification linked list, and obtaining topology path information through the system identification in the system identification linked list and the first sequence.

Optionally, after the step of enabling the central node to obtain topology path information through the system identification linked list, the method further includes:

periodically sending a topology information synchronization request message to a central node through a standby central node;

and synchronizing the topology path information under the condition that the standby center node receives the topology information synchronization confirmation message replied by the center node.

Optionally, after the periodically sending, by the standby central node, a topology information synchronization request packet to the central node, the method further includes:

and under the condition that the standby central node does not receive the topology information synchronization confirmation message replied by the central node, confirming the fault of the central node, and switching the standby central node into the central node.

Optionally, after said confirming said central node failure, the method further comprises:

sending a topology information synchronization request message to the standby central node switched to the central node under the condition that the state of the LLDP of the central node is detected to be an enabled state;

sending a topology information synchronization confirmation message through the standby central node which is switched to the central node;

and under the condition that the central node receives the topology information synchronization confirmation message, switching the central node into a standby central node.

Optionally, before the sending, by the central node, the topology information query message to the first transit node, the method further includes:

and starting LLDP among the central node, the standby central node, the first transfer node, the first node and the host.

Optionally, the target field of the LLDP message further defines a domain identification field, a message type field and a node type field, where the domain identification field is used to indicate a region range;

the message type field is used for indicating the type of the message, and the type of the message comprises a topology information synchronization request message, a topology information synchronization confirmation message, a topology information inquiry message and a topology inquiry information reply message;

The node type field is used for indicating the type of the node, and the type of the node comprises a center node, a standby center node, a transit node and an edge node.

In a second aspect, an LLDP-based topology link discovery apparatus includes:

the first sending module is used for sending a topology information query message to the first transfer node through the central node;

the judging module is used for judging whether the first transfer node and the central node have the same domain identifier or not through the first transfer node;

the first adding module is configured to add a system identifier of the first transit node to a first system identifier field of the topology information query message when the first transit node determines whether the first transit node and the central node have the same domain identifier;

the second sending module is used for sending the topology information query message to the first node;

the second adding module is used for adding the system identifier of the edge node to the first system identifier field of the topology information query message under the condition that the first node is the edge node;

the third adding module is used for adding the system identification linked list in the first system identification field to the topology inquiry information reply message;

The third sending module is used for sending the topology inquiry information reply message to the central node so that the central node obtains topology path information through the system identification linked list;

the system identification linked list is all system identifications in the first system identification field with a first sequence, the first sequence is an adding sequence of all system identifications, the topology information query message and the topology information reply message are LLDP messages, and a target field of the LLDP messages is defined with a system identification field.

Optionally, the LLDP-based topology link discovery apparatus further includes:

the acquisition module is used for acquiring a system identification linked list in the first system identification field under the condition that the first node is a second transfer node;

and the fourth sending module is used for adding the system identifier of the second transfer node to the first system identifier field and sending the topology information query message to the next node under the condition that the system identifier of the second transfer node is different from the system identifier in the system identifier linked list.

Optionally, the fourth sending module is specifically configured to:

And the topology information query message is not sent to the second transfer node and is sent to the next node when the system identifier of the second transfer node is the same as at least one system identifier of the system identifier linked list in the acquired first system identifier field.

Optionally, the third sending module is specifically configured to:

determining corresponding nodes according to the system identifications in the system identification linked list, and sequentially sending the topology inquiry information reply messages to the corresponding nodes according to a second sequence so as to send the topology inquiry information to the central node;

wherein the second order is opposite to the first order.

Optionally, the third adding module is specifically configured to:

adding a system identification linked list in the first system identification field to a second system identification field in a topology query information reply message;

the LLDP-based topology link discovery apparatus further includes:

the analyzing module is used for analyzing the second system identification field of the topology inquiry information reply message through the central node so that the central node can obtain the system identification linked list and obtain the topology path information through the system identification in the system identification linked list and the first sequence.

Optionally, the LLDP-based topology link discovery apparatus further includes:

a fifth sending module, configured to periodically send a topology information synchronization request packet to a central node through a standby central node;

and the synchronization module is used for synchronizing the topology path information under the condition that the standby center node receives the topology information synchronization confirmation message replied by the center node.

Optionally, the LLDP-based topology link discovery apparatus further includes:

and the first switching module is used for confirming the fault of the central node and switching the standby central node into the central node under the condition that the standby central node does not receive the topology information synchronization confirmation message replied by the central node.

Optionally, the LLDP-based topology link discovery apparatus further includes:

a sixth sending module, configured to send a topology information synchronization request packet to the standby central node switched to a central node when detecting that the state of the LLDP of the central node is an enabled state;

sending a topology information synchronization confirmation message through the standby central node which is switched to the central node;

and the second switching module is used for switching the central node into a standby central node under the condition that the central node receives the topology information synchronization confirmation message.

Optionally, the LLDP-based topology link discovery apparatus further includes:

and the starting module is used for starting LLDP among the central node, the standby central node, the first transfer node, the first node and the host.

Optionally, the LLDP-based topology link discovery apparatus further includes: the target field of the LLDP message is also defined with a domain identification field, a message type field and a node type field, wherein the domain identification field is used for indicating a region range;

the message type field is used for indicating the type of the message, and the type of the message comprises a topology information synchronization request message, a topology information synchronization confirmation message, a topology information inquiry message and a topology inquiry information reply message;

the node type field is used for indicating the type of the node, and the type of the node comprises a center node, a standby center node, a transit node and an edge node.

The embodiment of the invention provides a topology link discovery method based on LLDP, which comprises the following steps: the method comprises the steps of sending a topology information query message to a first transfer node through a central node, judging whether the first transfer node and the central node have the same domain identification through the first transfer node, adding the system identification of the first transfer node to a first system identification field of the topology information query message under the condition that the first transfer node judges whether the first transfer node and the central node have the same domain identification, sending the topology information query message to the first node, adding the system identification of the edge node to a first system identification field of the topology information query message under the condition that the first node is an edge node, adding a system identification linked list in the first system identification field to a topology query information reply message, sending the topology query information reply message to the central node so that the central node obtains topology path information through the system identification, wherein the system identification linked list is all the system identifications in the first system identification field with a first sequence, and the system identification linked list is all the topology information reply message with the LLDP (LLDP) field, and the topology information reply message is the topology information query message. The embodiment of the invention automatically discovers the topology link based on the LLDP, which is a standard RFC protocol, simply reforms and innovates the option tlv, so that the management granularity is embodied, and the aim of efficiently discovering the topology is fulfilled. The topology discovery structure of the central node, the transit node and the edge node is adopted, the idea of SDN centralized control is provided, all the control is carried out in the central node, and the rest transit nodes and the edge node are only responsible for forwarding protocol messages, so that the transit nodes and the edge nodes are stateless. Compared with openflow, only the topology path information of the central node is required to be maintained, and a plurality of key nodes are not required to be maintained, so that the problems of difficult operation and maintenance, high signaling pressure, poor expandability and the like are solved, and the deployment scenario of a large-scale wide area network can be adapted due to the fact that the management granularity is embodied. In contrast to SR, it is first a link layer topology discovery protocol and is therefore not a concern for three-tier networks, making the topology discovery protocol suitable for any three-tier network scenario, not just MPLS networks and IPV6 networks. Secondly, the invention adopts the form of a system id linked list and a query confirmation mechanism to record the topology path, and discards an SR source routing mechanism, thereby avoiding potential safety hazards. Finally, the invention does not adopt a source routing mechanism, so that IPS equipment is not required to be additionally added, and network cost is saved to a certain extent.

Drawings

Fig. 1 is a schematic diagram of a modified LLDP Option TLV message field according to an embodiment of the invention;

fig. 2 is a schematic flow chart of a topology link discovery method based on LLDP according to an embodiment of the invention;

FIG. 3 is a topology link discovery flow chart provided by an embodiment of the invention;

fig. 4 is an application scenario schematic diagram of an LLDP-based topology link discovery method according to an embodiment of the invention;

FIG. 5 is a schematic diagram of a synchronization process and a recovery process after failure of a central node according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of an LLDP-based topology link discovery apparatus according to an embodiment of the invention;

the achievement of the object, functional features and advantages of the present invention will be further described with reference to the embodiments, referring to the accompanying drawings.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, as appropriate, such that embodiments of the present invention may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type, and are not limited to the number of objects, such as the first object may be one or more.

For a clear understanding of the invention, the following explanation is given for the relevant definitions mentioned for the invention:

LLDP: a link layer discovery protocol;

TLV is a type length value, and the format type of the information in LLDPDU;

DCN: a data center network;

SDN: a software defined network;

OpenFlow: SDN control protocol, realizing transfer control separation;

SR: segment routing;

OVS: a virtual switch;

IPS: attack defense device.

The following describes in detail the LLDP-based topology link discovery method provided by the embodiment of the invention through specific embodiments and application scenarios thereof with reference to the accompanying drawings.

Example 1

Referring to fig. 1, a schematic diagram of an improved LLDP Option TLV packet field provided by an embodiment of the present invention is shown, where a field identification field, a packet type field, and a node type field are further defined in a destination field of the LLDP packet, where the field identification field is used to indicate a region range;

The message type field is used for indicating the type of the message, and the type of the message comprises a topology information synchronization request message, a topology information synchronization confirmation message, a topology information inquiry message and a topology inquiry information reply message;

the node type field is used for indicating the type of the node, and the type of the node comprises a center node, a standby center node, a transit node and an edge node.

For example, the newly added option tlv field is explicitly defined as follows:

a Domain identification field (Domain Id) which is an auto-discovery area range of the topology link, i.e., the topology discovery object is a network device having the same Domain Id, the field length being 8 bits;

system identification field (System ID): each network device has a unique identifier, and the field has a length of 8 bits;

the message Type field (Type Id) is as shown in FIG. 2, the message types are divided into 4 types, the current available values are 00, 01, 10, 11, 00 represent topology information synchronization request messages, 01 represent topology information synchronization confirmation messages, 10 represent topology information inquiry messages, 11 represent topology inquiry information reply messages, and the field length is 2 bits.

Node type field (Code Id) which is divided into 4 types, wherein the node types are mc, bc, tc, ec, mc represents a central node, bc represents a standby central node, tc represents a transit node, ec represents an edge node, and the length of the field is 2bit; center node: and maintaining the topology and link information of the whole network in the area, and transmitting 4 protocol messages at the node. Standby central node: the standby central node is converted into the central node when the central node fails, 2 protocol messages of 00 and 01 can be transmitted at the node, and the 10 and 11 protocol messages are directly discarded after being received. Transfer node: the method refers to other nodes except a central node, a standby edge node and an edge node in the area, and logically, network connection exists between the relay node and the central node, between the relay node and between the relay node and the edge node, and 10 and 11 total 2 protocol messages can be transmitted at the node, and the 00 and 01 protocol messages are directly discarded after being received. Edge node: the method refers to physical network equipment or OVS (over the air) of which the logical network is connected with a cloud host or a physical machine, wherein 2 kinds of protocol messages, namely 10 and 11, can be transmitted at the node, the 00 and 01 protocol messages are directly discarded after being received, and the edge node does not forward 10 messages.

Referring to fig. 2, a flow chart of a topology link discovery method based on LLDP provided by an embodiment of the invention is shown based on an improved LLDP Option TLV message field.

The invention provides a flow diagram of a topology link discovery method based on LLDP, which comprises the following steps:

s201: sending a topology information query message to a first transfer node through a central node;

optionally, before the sending, by the central node, the topology information query message to the first transit node, the method further includes:

and starting LLDP among the central node, the standby central node, the first transfer node, the first node and the host.

Specifically, the network planning architect defines the region identifier, the system identifier, the node type and globally opens the lldp according to the requirement, including the central node and the standby central node, the central node and the transit node, the transit node and the transit node, and the edge node and the cloud host or the physical machine all need to open the lldp.

S202: judging whether the first transfer node and the central node have the same domain identifier or not through the first transfer node;

S203: under the condition that the first transfer node judges whether the first transfer node and the central node have the same domain identification, adding the system identification of the first transfer node into a first system identification field of the topology information query message;

specifically, a first System identification field in the topology information query message, namely a System identification field (System ID) in the topology information query message, is used for placing a System identification, the central node sends the topology information query message to the transfer node, the transfer node checks whether the topology information query message has the same Domain ID as the central node, if so, the topology information query message continues to be forwarded downwards, otherwise, the message is discarded, and the following steps assume that the related nodes all belong to the same area.

S204: sending the topology information inquiry message to a first node;

s205: if the first node is an edge node, adding a system identifier of the edge node to a first system identifier field of the topology information query message;

optionally, under the condition that the first node is a second transit node, acquiring a system identifier linked list in the first system identifier field;

and under the condition that the system identification of the second transfer node is different from the system identification in the system identification linked list, adding the system identification of the second transfer node into the first system identification field, and sending the topology information query message to the next node.

Specifically, the central node sends a topology information inquiry message to the transfer node, and after receiving the protocol message, the transfer node adds the system id of the transfer node to the initial system id of the message, and simultaneously forwards the message to other transfer nodes or edge nodes connected with the message. When other transit nodes receive the topology information inquiry message, the system id of the own network equipment is added at the same time, and the process is analogized in sequence after the received topology information inquiry message until the topology information inquiry message reaches the edge node.

S206: adding a system identification linked list in the first system identification field to a topology query information reply message;

specifically, after receiving the topology information inquiry message sent by the transit node, the edge node adds the system id of the own network device after receiving the topology information inquiry message, and fills the whole system id linked list into the system id field of the topology information inquiry reply message.

S207: sending the topology inquiry information reply message to the central node so that the central node obtains topology path information through the system identification linked list;

the system identification linked list is all system identifications in the first system identification field with a first sequence, the first sequence is an adding sequence of all system identifications, the topology information query message and the topology information reply message are LLDP messages, and a target field of the LLDP messages is defined with a system identification field.

Specifically, after the whole system id linked list is filled into the system id field of the topology inquiry information reply message, the topology inquiry information reply message is sent back to the central node, and after the central node receives the topology inquiry information reply message, the system id link field is resolved, so that the whole topology route information in the region can be known according to the sequence of the whole system id linked list.

Referring to fig. 3 and fig. 4, which show a topology link discovery flowchart and an application scenario schematic diagram of an LLDP-based topology link discovery method provided by the embodiments of the present invention, the embodiments of the present invention provide an LLDP-based topology link discovery method, which includes sending a topology information query message to a first transit node through a central node, determining whether the first transit node and the central node have the same domain identifier by the first transit node, sending the topology query message to the central node, determining whether the first transit node and the central node have the same domain identifier by the first transit node, adding the system identifier of the first transit node to a first system identifier field of the topology information query message, sending the topology information query message to the first node, adding the system identifier of the edge node to a first system identifier field of the topology information query message in the case that the first node is an edge node, adding a system identifier linked list in the first system identifier field to the topology query message, sending the topology query message to the first transit node, and sending the topology query message to the first transit node, where the first transit node and the first transit node determine whether the first transit node and the central node have the same domain identifier, and the system identifier in the complete system identifier sequence is the system identifier list in the order of the system identifier reply message, and the system identifier list is the system identifier reply message, and the system identifier sequence is the system identifier list message is the system identifier and the system identifier reply system identifier. The embodiment of the invention automatically discovers the topology link based on the LLDP, which is a standard RFC protocol, simply reforms and innovates the option tlv, so that the management granularity is embodied, and the aim of efficiently discovering the topology is fulfilled. The topology discovery structure of the central node, the transit node and the edge node is adopted, the idea of SDN centralized control is provided, all the control is carried out in the central node, and the rest transit nodes and the edge node are only responsible for forwarding protocol messages, so that the transit nodes and the edge nodes are stateless. Compared with openflow, only the topology path information of the central node is required to be maintained, and a plurality of key nodes are not required to be maintained, so that the problems of difficult operation and maintenance, high signaling pressure, poor expandability and the like are solved, and the deployment scenario of a large-scale wide area network can be adapted due to the fact that the management granularity is embodied. In contrast to SR, it is first a link layer topology discovery protocol and is therefore not a concern for three-tier networks, making the topology discovery protocol suitable for any three-tier network scenario, not just MPLS networks and IPV6 networks. Secondly, the invention adopts the form of a system id linked list and a query confirmation mechanism to record the topology path, and discards an SR source routing mechanism, thereby avoiding potential safety hazards. Finally, the invention does not adopt a source routing mechanism, so that IPS equipment is not required to be additionally added, and network cost is saved to a certain extent.

In a possible implementation manner, after the obtaining the system identifier linked list in the first system identifier field, the method further includes:

and under the condition that the system identifier of the second transfer node is the same as at least one system identifier of the system identifier linked list in the first system identifier field, not sending the topology information inquiry message to the second transfer node and sending the topology information inquiry message to a next node.

Specifically, the transfer node receives the topology information inquiry message sent by the central node to the transfer node, and after the system id of the transfer node is added to the initial system id of the message, the message is forwarded to other transfer nodes or edge nodes connected with the message. In this case, if the topology information inquiry message is sent to other transit nodes, in order to ensure that the transit nodes do not repeatedly send the topology information inquiry message, the transit nodes need to check the system id linked list before sending the topology information inquiry message each time, and if the system id linked list already contains the system id of the receiving end, the topology information inquiry message is not sent to the transit nodes.

In a possible implementation manner, step S207 may be specifically performed by step S2071:

S2071: determining corresponding nodes according to the system identifications in the system identification linked list, and sequentially sending the topology inquiry information reply messages to the corresponding nodes according to a second sequence so as to send the topology inquiry information to the central node;

wherein the second order is opposite to the first order.

Specifically, when the edge node fills the entire system id linked list into the system id field of the topology query information reply message, and then transmits the topology query information reply message according to the system id linked list, the transit node (the network device of the previous system id) transmits the topology query information reply message. After receiving the topology inquiry information reply message sent by the edge node, the transit node inquires the system id linked list, continuously forwards the message, and so on until the message is forwarded to the central node.

Optionally, the adding the system identifier linked list in the first system identifier field to the topology query information reply message includes:

adding a system identification linked list in the first system identification field to a second system identification field in a topology query information reply message;

specifically, the second System identification field in the topology query information reply message, that is, the System identification field (System ID) in the topology query information reply message, is used for placing the System identification.

After the topology query information reply message is sent to the central node, the method further comprises:

and analyzing a second system identification field of the topology inquiry information reply message through the central node so that the central node obtains the system identification linked list, and obtaining topology path information through the system identification in the system identification linked list and the first sequence.

That is, after receiving the topology query information reply message sent by the edge node, the transit node continues to forward the message, and so on, until the transit node receives the topology query information reply message after forwarding to the central node, the central node can parse the system id link field through the query information reply message, and then can know the whole topology route information in the region according to the sequence of the whole system id linked list.

In a possible implementation manner, referring to fig. 5, a schematic diagram of a synchronization flow and a post-failure recovery flow of a central node provided by an embodiment of the present invention is shown, and after step S207, the method further includes step S208 to step S209:

s208: periodically sending a topology information synchronization request message to a central node through a standby central node;

That is, the central node periodically transmits topology information inquiry message, ensuring that the topology link maintained by the central node is up to date, the period being configurable

S209: and synchronizing the topology path information under the condition that the standby center node receives the topology information synchronization confirmation message replied by the center node.

Optionally, after the periodically sending, by the standby central node, a topology information synchronization request packet to the central node, the method further includes:

and under the condition that the standby central node does not receive the topology information synchronization confirmation message replied by the central node, confirming the fault of the central node, and switching the standby central node into the central node.

Specifically, the standby central node periodically sends a topology information synchronization request message to the central node, and when receiving a topology information synchronization confirmation message replied by the central node, the topology link information is successfully synchronized. If the standby central node does not receive the topology information synchronization confirmation message replied by the central node or does not receive the topology information synchronization confirmation message replied by the central node for preset times (such as three times in succession), the central node is considered to be faulty, and the standby central node is switched to the central node.

Optionally, after said confirming said central node failure, the method further comprises:

sending a topology information synchronization request message to the standby central node switched to the central node under the condition that the state of the LLDP of the central node is detected to be an enabled state;

sending a topology information synchronization confirmation message through the standby central node which is switched to the central node;

and under the condition that the central node receives the topology information synchronization confirmation message, switching the central node into a standby central node.

That is, if the original failed central node is recovered, after the lldp up is detected, the topology information synchronization request message is sent to the central node first, and after the central node returns the topology information synchronization confirmation message, the original failed central node sets itself as a standby central node.

The embodiment of the invention adopts a central node-standby central node architecture, thereby increasing high reliability, and in addition, the central node can also migrate in the area, thereby increasing high availability.

Example two

Referring to fig. 6, a schematic structural diagram of an LLDP-based topology link discovery apparatus 60 according to an embodiment of the invention is shown, including:

A first sending module 601, configured to send a topology information query message to a first transit node through a central node;

a judging module 602, configured to judge, by using the first transit node, whether the first transit node and the central node have the same domain identifier;

a first adding module 603, configured to add, when the first transit node determines whether the first transit node and the central node have the same domain identifier, a system identifier of the first transit node to a first system identifier field of the topology information query message;

a second sending module 604, configured to send the topology information query packet to the first node;

a second adding module 605, configured to, if the first node is an edge node, add a system identifier of the edge node to a first system identifier field of the topology information query message;

a third adding module 606, configured to add a system identifier linked list in the first system identifier field to a topology query information reply message;

a third sending module 607, configured to send the topology query information reply packet to the central node, so that the central node obtains topology path information through the system identifier linked list;

The system identification linked list is all system identifications in the first system identification field with a first sequence, the first sequence is an adding sequence of all system identifications, the topology information query message and the topology information reply message are LLDP messages, and a target field of the LLDP messages is defined with a system identification field.

Optionally, the LLDP-based topology link discovery apparatus 60 further includes:

an obtaining module 608, configured to obtain a system identifier linked list in the first system identifier field when the first node is a second transit node;

a fourth sending module 609, configured to add the system identifier of the second transit node to the first system identifier field and send the topology information query message to a next node when the system identifier of the second transit node is different from the system identifier in the system identifier linked list;

optionally, the fourth transmitting module 609 is specifically configured to:

and the topology information query message is not sent to the second transfer node and is sent to the next node when the system identifier of the second transfer node is the same as at least one system identifier of the system identifier linked list in the acquired first system identifier field.

Optionally, the third sending module 607 is specifically configured to:

determining corresponding nodes according to the system identifications in the system identification linked list, and sequentially sending the topology inquiry information reply messages to the corresponding nodes according to a second sequence so as to send the topology inquiry information to the central node;

wherein the second order is opposite to the first order.

Optionally, the third adding module 606 is specifically configured to:

adding a system identification linked list in the first system identification field to a second system identification field in a topology query information reply message;

the LLDP-based topology link discovery apparatus 60 further includes:

the parsing module 610 is configured to parse the second system identifier field of the topology query information reply message through the central node, so that the central node obtains the system identifier linked list, and obtains topology path information through the system identifiers in the system identifier linked list and the first order.

Optionally, the LLDP-based topology link discovery apparatus 60 further includes:

a fifth sending module 611, configured to periodically send, by using a standby central node, a topology information synchronization request packet to the central node;

And the synchronization module 612 is configured to synchronize the topology path information when the standby central node receives the topology information synchronization confirmation message replied by the central node.

Optionally, the LLDP-based topology link discovery apparatus 60 further includes:

and the first switching module 613 is configured to, when the standby central node does not receive the topology information synchronization confirmation message replied by the central node, confirm that the central node is faulty, and switch the standby central node to the central node.

Optionally, the LLDP-based topology link discovery apparatus 60 further includes:

a sixth sending module 614, configured to send a topology information synchronization request packet to the standby central node that is switched to a central node when detecting that the state of the LLDP of the central node is an enabled state;

sending a topology information synchronization confirmation message through the standby central node which is switched to the central node;

and a second switching module 615, configured to switch the central node to a standby central node when the central node receives the topology information synchronization acknowledgement message.

Optionally, the LLDP-based topology link discovery apparatus 60 further includes:

And a starting module 616, configured to start LLDP between the central node and the standby central node, between the central node and the first transit node, between the first transit node and the first node, and between the first node and the host.

Optionally, the LLDP-based topology link discovery apparatus 60 further includes: the target field of the LLDP message is also defined with a domain identification field, a message type field and a node type field, wherein the domain identification field is used for indicating a region range;

the message type field is used for indicating the type of the message, and the type of the message comprises a topology information synchronization request message, a topology information synchronization confirmation message, a topology information inquiry message and a topology inquiry information reply message;

the node type field is used for indicating the type of the node, and the type of the node comprises a center node, a standby center node, a transit node and an edge node.

The forwarding device 60 for VXLAN messages based on OVS neighbor table entries provided in the embodiment of the present invention can implement each process implemented in the foregoing method embodiment, and in order to avoid repetition, a description is omitted here.

In the embodiment of the invention, a first sending module is used for sending a topology information query message to a first transfer node through a central node, a judging module is used for judging whether the first transfer node and the central node have the same domain identifier through the first transfer node, a first adding module is used for adding the system identifier of the first transfer node to a first system identifier field of the topology information query message when the first transfer node judges whether the first transfer node and the central node have the same domain identifier, a second sending module is used for sending the topology information query message to the first node, and a second adding module is used for adding the system identifier of the first transfer node to the first system identifier field of the topology information query message when the first node is an edge node, the method comprises the steps that system identifications of edge nodes are added to a first system identification field of a topology information query message, a third adding module is used for adding a system identification linked list in the first system identification field to a topology query information reply message, a third sending module is used for sending the topology query information reply message to a center node so that the center node obtains topology path information through the system identification linked list, wherein the system identification linked list is all the system identifications in the first system identification field with a first sequence, the first sequence is the addition sequence of all the system identifications, the topology information query message and the topology query information reply message are LLDP messages, and a target field of the LLDP message is defined with the system identification field. The embodiment of the invention automatically discovers the topology link based on the LLDP, which is a standard RFC protocol, simply reforms and innovates the option tlv, so that the management granularity is embodied, and the aim of efficiently discovering the topology is fulfilled. The topology discovery structure of the central node, the transit node and the edge node is adopted, the idea of SDN centralized control is provided, all the control is carried out in the central node, and the rest transit nodes and the edge node are only responsible for forwarding protocol messages, so that the transit nodes and the edge nodes are stateless. Compared with openflow, only the topology path information of the central node is required to be maintained, and a plurality of key nodes are not required to be maintained, so that the problems of difficult operation and maintenance, high signaling pressure, poor expandability and the like are solved, and the deployment scenario of a large-scale wide area network can be adapted due to the fact that the management granularity is embodied. In contrast to SR, it is first a link layer topology discovery protocol and is therefore not a concern for three-tier networks, making the topology discovery protocol suitable for any three-tier network scenario, not just MPLS networks and IPV6 networks. Secondly, the invention adopts the form of a system id linked list and a query confirmation mechanism to record the topology path, and discards an SR source routing mechanism, thereby avoiding potential safety hazards. Finally, the invention does not adopt a source routing mechanism, so that IPS equipment is not required to be additionally added, and network cost is saved to a certain extent.

The virtual system in the embodiment of the invention can be a device, a component in a terminal, an integrated circuit or a chip.

In addition, it should be noted that the above embodiment of the apparatus is merely illustrative, and does not limit the scope of the present invention, and in practical application, a person skilled in the art may select some or all modules according to actual needs to achieve the purpose of the embodiment, which is not limited herein.

In addition, technical details not described in detail in this embodiment may refer to the intelligent cognitive method and system provided in any embodiment of the present invention, which are not described herein.

The foregoing description of the preferred embodiments of the invention is not intended to be limiting, but rather is intended to cover all modifications, equivalents, alternatives, and improvements that fall within the spirit and scope of the invention.

Claims (10)

1. An LLDP-based topology link discovery method, said method comprising:

sending a topology information query message to a first transfer node through a central node;

judging whether the first transfer node and the central node have the same domain identifier or not through the first transfer node;

Under the condition that the first transfer node judges whether the first transfer node and the central node have the same domain identification, adding the system identification of the first transfer node into a first system identification field of the topology information query message;

sending the topology information inquiry message to a first node;

if the first node is an edge node, adding a system identifier of the edge node to a first system identifier field of the topology information query message;

adding a system identification linked list in the first system identification field to a topology query information reply message;

sending the topology inquiry information reply message to the central node so that the central node obtains topology path information through the system identification linked list;

the system identification linked list is all system identifications in the first system identification field with a first sequence, the first sequence is an adding sequence of all system identifications, the topology information query message and the topology information reply message are LLDP messages, and a target field of the LLDP messages is defined with a system identification field.

2. The topology link discovery method of claim 1, wherein after said sending the topology information query message to the first node, the method further comprises:

Acquiring a system identification linked list in the first system identification field under the condition that the first node is a second transit node;

and under the condition that the system identification of the second transfer node is different from the system identification in the system identification linked list, adding the system identification of the second transfer node into the first system identification field, and sending the topology information query message to the next node.

3. The topology link discovery method of claim 2, wherein after said obtaining a linked list of system identifications in said first system identification field, said method further comprises:

and under the condition that the system identifier of the second transfer node is the same as at least one system identifier of the system identifier linked list in the first system identifier field, not sending the topology information inquiry message to the second transfer node and sending the topology information inquiry message to a next node.

4. The topology link discovery method of claim 1, wherein said sending the topology query information reply message to the central node comprises:

determining corresponding nodes according to the system identifications in the system identification linked list, and sequentially sending the topology inquiry information reply messages to the corresponding nodes according to a second sequence so as to send the topology inquiry information to the central node;

Wherein the second order is opposite to the first order.

5. The topology link discovery method of claim 1, wherein adding the system identification linked list in the first system identification field to the topology query information reply message comprises:

adding a system identification linked list in the first system identification field to a second system identification field in a topology query information reply message;

after the topology query information reply message is sent to the central node, the method further comprises:

and analyzing a second system identification field of the topology inquiry information reply message through the central node so that the central node obtains the system identification linked list, and obtaining topology path information through the system identification in the system identification linked list and the first sequence.

6. The topology link discovery method of claim 1, wherein after said causing said central node to obtain topology path information through said system identification linked list, said method further comprises:

periodically sending a topology information synchronization request message to a central node through a standby central node;

And synchronizing the topology path information under the condition that the standby center node receives the topology information synchronization confirmation message replied by the center node.

7. The topology link discovery method of claim 6, wherein after said periodically sending a topology information synchronization request message to said hub node via a standby hub node, said method further comprises:

and under the condition that the standby central node does not receive the topology information synchronization confirmation message replied by the central node, confirming the fault of the central node, and switching the standby central node into the central node.

8. The topology link discovery method of claim 7, wherein after said confirming said central node failure, said method further comprises:

sending a topology information synchronization request message to the standby central node switched to the central node under the condition that the state of the LLDP of the central node is detected to be an enabled state;

sending a topology information synchronization confirmation message through the standby central node which is switched to the central node;

and under the condition that the central node receives the topology information synchronization confirmation message, switching the central node into a standby central node.

9. The method of topology link discovery of claim 6, wherein prior to said sending, by the central node, a topology information query message to the first transit node, the method further comprises:

and starting LLDP among the central node, the standby central node, the first transfer node, the first node and the host.

10. The topology link discovery method of claim 1, wherein the destination field of the LLDP message further defines a domain identification field, a message type field, and a node type field, the domain identification field being used to indicate a domain range;

the message type field is used for indicating the type of the message, and the type of the message comprises a topology information synchronization request message, a topology information synchronization confirmation message, a topology information inquiry message and a topology inquiry information reply message;

the node type field is used for indicating the type of the node, and the type of the node comprises a center node, a standby center node, a transit node and an edge node.

Images