CN104205729B - Method, device, and system for configuring device in network - Google Patents

Abstract

The device configuration method, device and system in the network involved in the present invention, the method includes: the LLDP master device receives the IP message of the OSS, and extracts the SNMP message from the IP message; the LLDP master device according to the LLDP target device to be configured The identification information queries the local neighbor table to obtain forwarding information and SNMP information to the target device; the LLDP master device completes SNMP message format conversion and LLDP encapsulation according to the SNMP information, and forwards the obtained outbound interface to a specific LLDP target device, so that LLDP The target device is configured with the configuration information. Therefore, the present invention communicates by encapsulating SNMP messages into LLDP messages, thereby reducing the operational complexity of remote management of the OSS, and realizing remote management of the OSS without obtaining an IP address.

Description

Device configuration method, device and system in network

technical field

The present invention relates to the communication field, in particular to a device configuration method, device and system in a network.

Background technique

With the development of communication technology, there are increasingly various types of network devices and their respective configurations are intricate. The plug-and-play technology of network equipment can make it very easy for users to add new network equipment to the system. This technology can be applied in various fields and brings great convenience.

Currently, the plug-and-play technology of network devices is configured through a protocol (Internet Protocol, IP) for interconnection between networks. Wherein, when the device uses IP for configuration, it is necessary to configure an IP packet forwarding path, including a virtual local area network (Virtual Local Area Network, VLAN), an IP address, a route, and the like.

Fig. 1 is a schematic structural diagram of a remote management system in the prior art. As shown in FIG. 1 , in the remote management system, network devices and a Dynamic Host Configuration Protocol (Dynamic Host Configuration Protocol, DHCP) server need to be configured. Wherein, the configuration content of the network equipment includes traffic volume and DHCP configuration; the purpose of configuring the DHCP server is to assign IP addresses to plug-and-play devices. When the plug-and-play device is inserted into the configuration system, the network device records the obtained IP address, and the operation support system (Operation Support System, OSS) configures the plug-and-play device according to the obtained IP address.

Fig. 2 is a schematic structural diagram of another remote management system in the prior art. As shown in FIG. 2 , in the remote management system, the network device and the DHCP server also need to be configured. After the plug-and-play device is inserted into the configuration system, the network device records the IP address obtained by the plug-and-play device, and the plug-and-play device 2 and the network device communicate with each other through Link Layer Discovery Protocol (LLDP). Perceive the other party, and send the device information of the plug-and-play device 2 to the OSS in the form of LLDP neighbor information. The OSS perceives the location of the plug-and-play device based on neighbor information, and delivers configuration information based on the location information of the plug-and-play device.

However, the above two remote management systems all need to configure the network equipment and the DHCP server; in addition, no matter whether the LLDP protocol is used or not, it is necessary to configure the IP address of the plug-and-play device, and the configuration process is very complicated.

Contents of the invention

The invention provides a device configuration method, device and system in a network, which solves the problem of configuring network devices and DHCP servers in the prior art, and configuring IP addresses for plug-and-play devices at the same time, using extended LLDP protocol, which reduces the operational complexity of remote management and enables remote management through OSS without obtaining an IP address.

In a first aspect, the present invention provides a device configuration method in a network, the network includes an operation support system OSS, a Link Layer Discovery Protocol LLDP master device, and one or more LLDP target devices, and the one or more The LLDP target device connects to the OSS through the LLDP master device, and the method includes:

The LLDP main device receives the IP message of the OSS, and extracts a Simple Network Management Protocol SNMP message from the IP message, and the SNMP message carries the identification information of the LLDP target device to be configured and the to-be-configured Configuration information required by the configured LLDP target device;

The LLDP master device queries the correspondence between the identification information of the LLDP target device and the forwarding information of the LLDP target device according to the identification information of the LLDP target device to be configured, thereby obtaining the forwarding information of the LLDP target device to be configured;

The LLDP master device encapsulates the SNMP message into an LLDP message, and sends the LLDP message to the LLDP target device to be configured according to the obtained forwarding information, so that the LLDP target device uses the configuration file to configure.

Wherein, the obtained forwarding information includes an outgoing interface on the LLDP master device connected to the LLDP target device to be configured.

Further, the LLDP master device encapsulates the SNMP message into an LLDP message specifically including:

The LLDP master device encapsulates the SNMP message into the LLDP message in the form of type length value TLV. The LLDP packet also carries a TLV for identifying the LLDP target device to be configured, and the TLV for identifying the LLDP target device to be configured carries identification information of the LLDP target device to be configured.

In a first possible implementation manner, before receiving the IP packet of the OSS, the LLDP master device further includes: obtaining the topology structure of the one or more LLDP target devices, and reporting the obtained topology structure to the The OSS generates a neighbor-topology entry locally, which includes the neighbor device ID, the neighbor SNMP version number and SNMP ID, and the network topology information reaching the neighbor.

In a second possible implementation manner, the one or more LLDP target devices and the LLDP master device form a ring network structure, then obtaining the topology structure of the one or more LLDP target devices specifically includes: the LLDP The master device sends a Neighbor Advertisement message to the one or more LLDP target devices, so that the LLDP target device that receives the Neighbor Advertisement message adds its own identification information and the interface information that receives the Neighbor Advertisement message to the Neighbor Advertisement message. The text is sent to the next-hop LLDP target device; the LLDP master device receives the Neighbor Advertisement message, and obtains the topology structure of the one or more LLDP target devices from the received Neighbor Advertisement message.

With reference to the second possible implementation of the first aspect, in a third possible implementation, the LLDP master device is connected to the first LLDP target device on one side, and connected to the second LLDP target device on the other side, so The LLDP master device sending a Neighbor Advertisement message to the one or more LLDP target devices specifically includes: the LLDP master device sending a first Neighbor Advertisement message to the first LLDP target device, so that receiving the first The LLDP target device of the Neighbor Advertisement message adds its own identification information and the interface information that received the first Neighbor Advertisement message to the first Neighbor Advertisement message, and forwards it to the next-hop LLDP target device; the LLDP master device sending a second Neighbor Advertisement message to the second LLDP target device, so that the LLDP target device receiving the second Neighbor Advertisement message adds its own identification information and the interface information that received the second Neighbor Advertisement message to the The second NA packet is forwarded to the next-hop LLDP target device; the LLDP master device receives the first NA packet and the second NA packet, and according to the received first NA packet and the second NA packet, The neighbor advertisement message obtains the topology structure of the one or more LLDP target devices.

Further, before the LLDP master device encapsulates the SNMP message into the LLDP message, the method also includes:

The LLDP master device is further configured to obtain SNMP version information that the LLDP target device to be configured can recognize according to the identification information of the LLDP target device to be configured, and perform the LLDP to be configured according to the SNMP version information. The configuration information required by the target device for conversion.

In a second aspect, the present invention provides a Link Layer Discovery Protocol LLDP device, the device comprising:

The first interface is used to connect to the operation support system OSS;

The second interface is used to connect one or more LLDP target devices;

A data receiver, configured to receive the IP message of the OSS, and extract a Simple Network Management Protocol SNMP message from the IP message, wherein the SNMP message carries the identification information of the LLDP target device to be configured and the Configuration information required by the LLDP target device to be configured;

A processor, configured to query the correspondence between the identification information of the LLDP target device and the forwarding information of the LLDP target device according to the identification information of the LLDP target device to be configured, so as to obtain the forwarding information of the LLDP target device to be configured; and The SNMP message is encapsulated into the LLDP message;

A data transmitter, configured to send the LLDP packet to the LLDP target device to be configured according to the obtained forwarding information, so that the LLDP target device uses the configuration file for configuration.

In a first possible implementation manner, the processor is further configured to acquire the topology of the one or more LLDP target devices; the data transmitter is further configured to report the acquired topology to the OSS.

With reference to the first possible implementation of the second aspect, in the second possible implementation, the one or more LLDP target devices and the LLDP master device form a ring network structure, then the data transmitter, It is also used to send a Neighbor Advertisement message to the one or more LLDP target devices, so that the LLDP target device that receives the Neighbor Advertisement message adds its own identification information and the interface information that receives the Neighbor Advertisement message to the Neighbor Advertisement The message is sent to the next-hop LLDP target device; the data receiver is also used to receive a neighbor notification message; the processor is also used to obtain the one or more from the received neighbor notification message The topology of the LLDP target device.

In a third aspect, the present invention provides a device configuration system, the system includes a Link Layer Discovery Protocol LLDP master device and one or more LLDP target devices, and the one or more LLDP target devices pass through the LLDP master The device is connected to the OSS,

The LLDP master device is used to receive the IP message of the operation support system OSS, extract the Simple Network Management Protocol SNMP message from the IP message, and carry the identification information of the LLDP target device to be configured in the SNMP message And the configuration information required by the LLDP target device to be configured; according to the identification information of the LLDP target device to be configured, query the correspondence between the identification information of the LLDP target device and the forwarding information of the LLDP target device, so as to obtain the to-be-configured Configure the forwarding information of the LLDP target device; and encapsulate the SNMP message into an LLDP message, and send the LLDP message to the LLDP target device to be configured according to the obtained forwarding information, so that the LLDP target devices are configured using the configuration file.

In a first possible implementation manner, the LLDP master device is further configured to obtain the topology structure of the one or more LLDP target devices, and report the obtained topology structure to the OSS.

With reference to the first possible implementation of the third aspect, in the second possible implementation, the one or more LLDP target devices and the LLDP master device form a ring network structure, and the LLDP master device specifically It is used to send a neighbor notification message to the one or more LLDP target devices; receive the neighbor notification message, and obtain the topology structure of the one or more LLDP target devices from the received neighbor notification message; the LLDP The target device is configured to receive the Neighbor Advertisement message, add its own identification information and the interface information of the received Neighbor Advertisement message to the Neighbor Advertisement message and send it to the next-hop LLDP target device.

By applying the device configuration method, device and system provided above, the LLDP master device receives the IP message of the OSS, and extracts the Simple Network Management Protocol SNMP message from the IP message, and the SNMP message carries the identification of the LLDP target device to be configured information and the configuration files required by the LLDP target device to be configured; the LLDP master device queries the local neighbor table according to the identification information of the LLDP target device to be configured, and obtains the forwarding information and SNMP information of the target device. The outbound interface of the target device, and the SNMP information includes information such as the SNMP version and identification of the target; the LLDP master device completes SNMP message format conversion and LLDP encapsulation according to the SNMP information, and forwards the obtained outbound interface to the characteristic LLDP target device, so that LLDP The target device is configured using the configuration file, and the extended LLDP protocol is used to communicate between the LLDP master device and the LLDP target device by encapsulating SNMP messages into LLDP messages, thereby reducing the complexity of OSS remote management operations It can achieve remote management of OSS without obtaining an IP address.

Description of drawings

Fig. 1 is a schematic structural diagram of a remote management system in the prior art;

FIG. 2 is a schematic structural diagram of another remote management system in the prior art;

FIG. 3 is a flowchart of a device configuration method in a network provided by an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a management system provided by an embodiment of the present invention;

FIG. 5 is a flowchart of a device configuration method in a network provided by an embodiment of the present invention;

FIG. 6 is a flowchart of a device configuration method in a network provided by an embodiment of the present invention;

FIG. 7 is an information interaction diagram of a device configuration method provided by an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a link layer discovery protocol LLDP master device provided by an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a device configuration system provided by an embodiment of the present invention.

detailed description

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

An embodiment of the present invention provides a device configuration method, as shown in Figure 3, the provided method includes:

Step 300, the LLDP master device receives the IP message of the OSS, extracts the Simple Network Management Protocol SNMP message from the IP message, and the SNMP message carries the identification information of the LLDP target device to be configured and the LLDP target device to be configured. configuration information;

Wherein, the identification information of the LLDP target device to be configured may be the MAC (Meidia Access Control, Media Access Control) address of the LLDP target device to be configured, the device identifier of the LLDP target device to be configured, or other LLDP devices that can identify the LLDP target device to be configured Identification information of the target device, etc.

The configuration information may be parameters that need to be configured, values of related parameters, and the like.

Step 310, the LLDP master device queries the correspondence between the identification information of the LLDP target device and the forwarding information of the LLDP target device according to the identification information of the LLDP target device to be configured, so as to obtain the forwarding information of the LLDP target device to be configured;

Specifically, the forwarding information may be the outbound interface of the LLDP master device connected to the LLDP target device to be configured, etc. The neighbor table of the LLDP master device stores the correspondence between the identification information of the LLDP target device and the forwarding information of the LLDP target device. The master device can use the identification information of the LLDP target device to be configured to query the neighbor table, so as to obtain the corresponding outbound interface.

Step 320, the LLDP master device encapsulates the SNMP message into an LLDP message, and forwards it to the LLDP target device to be configured according to the forwarding information, so that the LLDP target device to be configured uses the configuration information for configuration.

Specifically, the LLDP master device can encapsulate the configuration information into the LLDP packet in the form of TLV (Type-Length-Valve, type length value), and the LLDP master device can also use the identification information of the LLDP target device to be configured in the form of TLV In this way, the LLDP target device receiving the LLDP message can judge whether the identification information in the TLV is consistent with its own, and if it is consistent, it will process the message; Obtain the corresponding outgoing interface in the table and forward it.

The method provided in this embodiment realizes the use of the extended LLDP protocol to communicate between the LLDP master device and the LLDP target device by encapsulating SNMP messages into LLDP messages, thereby reducing the operational complexity of OSS remote management , and the OSS can remotely manage the LLDP target device without obtaining an IP address.

Specifically, FIG. 4 is a schematic structural diagram of a management system provided by an embodiment of the present invention. As shown in FIG. 4 , the system includes an OSS 41 , an LLDP master device 42 and one or more LLDP target devices. One or more LLDP target devices are connected to OSS41 through the LLDP master device. For example, the LLDP master device 42 has multiple interfaces for connecting to LLDP plug-and-play devices, such as: interface 1, interface 2, . . . , interface m. Each interface of the LLDP master device 42 can be connected to one or more LLDP target devices, for example: the multiple LLDP plug-and-play devices connected to the interface 1 are respectively LLDP target device 1, LLDP target device 2, ..., LLDP target Device n-1 and LLDP target device n.

In addition, describe in detail the self-defined message names and table formats involved in all embodiments of the present invention.

First, the full name of TLV is Type-Length-Value. Among them, Type is the label, Length is the length, and Value is the value. The lengths of the T and L fields are often fixed, the most common T is 8 bits, the L is also 8 bits, and the length of the V field is variable. As the name implies, the T field indicates the message type, the L field indicates the message length, and the V field is often used to store the content of the message.

(1) Proxy ID TLV (LLDP proxy TLV): The Type in the message is not specific, and 32 can be used, that is, the Type is equal to 32, and the proxy priority is recorded in it. The priority is mainly used to select the main proxy device from the device. Different proxy devices can realize redundant backup. Carrying the TLV indicates that the device has the capability of proxy management, and is generally the LLDP master device. The format is shown in Table 1.

Table 1

7 bits 9 bits 8 bits Type 32 length priority

(2) Target device TLV (LLDP Destination TLV): The Type in the message is not specific, and 33 can be used, that is, the Type is equal to 33, and the specified target device identifier is recorded in it. It is mainly used to specify the target device when requesting or responding. The format is shown in Table 2.

Table 2

7 bits 9 bits 48 bits Type 33 length target device identification

(3) Topology query TLV (LLDP topo query TLV): The Type in the message is not specific, and 34 can be used, that is, the Type is equal to 34. This TLV is used to indicate that the message is a device topology query request. The message format is shown in Table 3.

table 3

7 bits 9 bits Type 34 length = 0

(4) Topology answer TLV (LLDP topo answer TLV): The Type in the message is not specific, and 35 can be used, that is, Type is equal to 35. This TLV is used to indicate that the message is a device topology query response. The message format is shown in Table 4.

Table 4

7 bits 9 bits Type 35 length = 0

(5) Link topology TLV (LLDP topo TLV): The Type in the message is not specific, and 36 can be used, that is, the Type is equal to 36. In the device topology response message, this TLV is used to carry link topology information, which generally consists of a device identifier and an interface identifier, and the device identifier TLV and interface identifier TLV have been defined in the LLDP standard protocol. The message format is shown in Table 5.

table 5

(6) Simple Network Management Protocol message TLV (SNMP TLV): it is a self-defined functional term, which means to encapsulate SNMP messages into LLDP messages. In the embodiment of the present invention, it specifically refers to that the LLDP master device or the target device encapsulates all original Simple Network Management Protocol (Simple Network Management Protocol, SNMP) messages into LLDP messages, including OSS issued messages, LLDP target device Reply message, and active notification message sent when the LLDP target device fails or changes. This TLV is not specific to Type, and 37 can be used, that is, Type is equal to 37. The message format is shown in Table 6.

Table 6

7 bits 9 bits n*8 bits Type 37 length (n bytes) SNMP message information

(7) Simple Network Management Protocol Identification TLV (SNMP Identification TLV): Use the custom TLV type Type in the LLDP standard. The Type is not specific here, and 38 can be used, that is, Type is equal to 38. Distinguishes the SNMP identifier of the LLDP device, which is used to identify the target device to which the OSS delivers the configuration. Among them, V can contain SNMP version number and identifier (SNMP V1/V2 version can use community name, V3 version can use USM USER and key information), as shown in Table 7.

Table 7

7 bits 9 bits 8 bits n bits Type 38 Length (n+8 bits) SNMP version SNMP ID

Second, forwarding table definition.

(1) Neighbor table of the LLDP master device: used to find and maintain neighbor information. Neighbors include directly connected and non-directly connected, and can find outbound interfaces when forwarding packets. Only the necessary information is listed here. , you can also add description and other information. The LLDP neighbor table is shown in Table 8.

Table 8

Neighbor ID hop count interface SNMP version SNMP ID

(2) Neighbor table of the LLDP target device: After the LLDP device receives the LLDP message, it needs to record or refresh the table. It is mainly used for network intermediate devices to find the forwarding egress, and when the target device actively reports information to OSS to select the master device according to the proxy priority. If the neighbor does not have the proxy capability, the proxy priority 0 can be used to indicate. The LLDP neighbor table is shown in Table 9.

Table 9

Neighbor ID hop count interface Proxy priority

Based on the foregoing packets and forwarding table entries, the functions of the LLDP master device and the LLDP target device will be described in detail below.

(1) LLDP master device function: agent communication between LLDP target device and OSS (mainly convert SNMP overLLDP message and SNMP over IP message to each other, and then forward the message to the corresponding device and OSS, including the original need to report Neighbor information to OSS); regularly or manually notify other LLDP target devices of LLDP master device information; learn neighbor topology and report to OSS system, including directly connected neighbors and non-directly connected neighbors.

Specifically, after receiving the SNMP configuration or query request sent by the OSS, the LLDP master device judges whether the device is configured according to the identifier in the SNMP message. If yes, it hands over to the SNMP Agent to complete the configuration; Then query the neighbor entry according to the identifier. After the SNMP message version and identifier conversion are completed, it is encapsulated into an LLDP packet. After adding the target device TLV to specify the target device, send it to the next-hop neighbor from the outgoing interface in the neighbor entry, and finally forward it. to the specified target device.

After the LLDP master device receives the SNMP over LLDP message responded or reported by the target device, it completes the SNMP version and identifier conversion and sends it to the OSS system in the form of an IP message.

When the LLDP master device learns neighbors, it sends a target device topology query request through the device topology query TLV, and sends it to the target device through the target device TLV; after receiving the request, the target device responds with a device topology reply message, and the LLDP master The device obtains the complete link topology information of the target device from the device TLV, receiving interface TLV, and link topology TLV added by each intermediate device in the message, and reports this information together with the SNMP information notified by the neighbor to the OSS system , which is convenient for the OSS system to deliver configurations.

(2) LLDP target device functions: forward LLDP packets, process LLDP topology query requests, process SNMPover LLDP configuration or query requests, and use SNMP over LLDP to proactively report information to the OSS system.

Specifically, after the LLDP target device receives the LLDP packet, if the packet does not carry the TLV of the target device, it inserts the TLV of the local device and the receiving interface TLV, and sends it to all directly connected neighbors that are not the receiving interface; TLV of the target device, judge whether it is the device according to the TLV, if not, query the neighbor entry and forward it to the next-hop device.

If it is determined according to the target device TLV that it is the device, then it is judged whether it is a topology query request based on whether the link topology query TLV is included. If so, the link topology information is obtained from the message and encapsulated in the form of the link topology TLV , add the device topology response TLV and specify the target device TLV, and specify the response to the source device that initiated the neighbor query.

If it is judged according to the TLV of the target device that it is the device, it is also necessary to judge whether the SNMP over LLDP configuration or query request is based on whether the message carries the Simple Network Management Protocol message TLV. If so, it will be handed over to the SNMP agent to process the request. The processing result constructs an SNMP response message, which is also encapsulated in the TLV mode of the simple network management protocol message, and is specified to respond to the source requesting device through the TLV mode of the target device, usually the LLDP master device.

When the target device needs to actively report information to the OSS, it is also encapsulated in the form of SNMP over LLDP, and the LLDP master device is selected according to the proxy priority of the neighbor, and then sent to the LLDP master device by specifying the TLV of the target device.

Based on FIG. 4, an embodiment of the present invention provides a device configuration method in a network. As shown in FIG. 5, the provided method may specifically include:

Step 510, the LLDP master device receives the IP message of the OSS, extracts the Simple Network Management Protocol SNMP message from the IP message, and the SNMP message carries the identification information of the LLDP target device to be configured and the LLDP target device to be configured. configuration information.

Specifically, the OSS is a comprehensive service operation and management platform capable of managing LLDP master devices. The LLDP master device receives the SNMP capability of the LLDP target device, such as the supported SNMP version information. The LLDP master device will convert the SNMP capability of LLDP and report it to OSS. This conversion process is mainly to consider that the SNMP version supported by the LLDP master device may be inconsistent with the SNMP version supported by the LLDP target device. Generally, the SNMP version supported by the LLDP target device can be converted to the LLDP master device and OSS according to the SNMP identifier carried by the LLDP target device. Supported SNMP versions. Different SNMP versions identify devices in different ways. For example, some versions identify LLDP target devices by community names, and some versions identify LLDP target devices by user names. The specific conversion content can be converted between community names and user names. The LLDP master device will also receive management request information carrying the LLDP target device ID sent by the OSS, such as query request information or configuration request information. The management request information needs to be received by the LLDP target device corresponding to the LLDP target device identifier. The LLDP master device acting as a proxy is responsible for sending the management request information to the LLDP target device.

The configuration information may include parameters and related values that need to be configured for the LLDP target device to be configured.

The device management method provided by the embodiment of the present invention, before step 510, further includes: step 500, the LLDP master device also needs to obtain the topology structure of the LLDP target device, and report the topology structure of the LLDP target device to the OSS.

If the LLDP target device connected to the LLDP master device forms a ring network structure, the specific topology structure of the LLDP target device can be obtained as follows:

The LLDP master device sends Neighbor Advertisement packets to the LLDP target device.

The LLDP target device adds its own identification information and the interface information of the received neighbor advertisement message to the neighbor advertisement message and sends it to the next-hop LLDP target device. The LLDP target device can add its own identification information and the interface information of the received Neighbor Advertisement message to the Neighbor Advertisement message in the form of the device identification TLV and interface identification TLV. The LLDP target device can also add the SNMP version number and The identifier is added to the neighbor advertisement message, and the SNMP version number and SNMP identifier supported by the LLDP target device can be added to the neighbor advertisement message in the form of the TLV shown in Table 7.

Due to the ring network structure, the Neighbor Advertisement packets sent by the LLDP master device will eventually return to the LLDP master device. The Neighbor Advertisement packets received by the LLDP master device will carry the device identification TLV and The interface identifies the TLV so that the LLDP master can know the topology in one direction.

In order to obtain a bidirectional topology structure, the LLDP master device can send a Neighbor Advertisement packet in two different directions, so that the LLDP master device will receive two Neighbor Advertisement packets, and obtain from the two Neighbor Advertisement packets topology in both directions.

Assuming that the LLDP master device is connected to the first LLDP target device on one side and the second LLDP target device on the other side, the process for the LLDP master device to obtain the topology structure in two directions may specifically include:

(1) The LLDP master device sends a first neighbor advertisement message to the first LLDP target device. The LLDP target device that receives the first neighbor advertisement message adds its own identification information and the interface information that received the first neighbor advertisement message to the first neighbor advertisement message, and forwards it to the next-hop LLDP target device; The hop count information may also be carried in the neighbor advertisement message, and the LLDP target device receiving the first neighbor advertisement message may modify the hop count information, for example, add 1 and so on.

(2) The LLDP master device sends a second neighbor advertisement message to the second LLDP target device. The LLDP target device receiving the second Neighbor Advertisement message adds its own identification information and the interface information receiving the second Neighbor Advertisement message to the second Neighbor Advertisement message, and forwards it to the next-hop LLDP target device; The hop count information may also be carried in the second neighbor advertisement message, and the LLDP target device receiving the second neighbor advertisement message may add 1 to the hop count.

(3) The LLDP master device receives the first Neighbor Advertisement message and the second Neighbor Advertisement message, and obtains the topology structure of the one or more LLDP target devices according to the received first Neighbor Advertisement message and the second Neighbor Advertisement message .

The first and second NA packets received by the LLDP master device carry the device ID TLV and interface ID TLV of the LLDP target device. From these device ID TLVs and interface ID TLVs, two direction topology.

In order for the LLDP target device to identify the LLDP master device, the LLDP master device can also carry the Proxy ID in the neighbor notification message sent, so that the LLDP target device can identify the LLDP master device that can communicate with the OSS based on the Proxy ID.

After the LLDP master device obtains the topology structure in both directions, it can also generate neighbor entries locally. The neighbor entries can include the identification information of the neighbor device and the network topology information reaching the neighbor, such as the outgoing interface. The neighbor entry can also include Including the SNMP version number and SNMP ID of the neighbor. The neighbor table may also include the number of hops from the LLDP master device to each LLDP target device, and the like.

If the LLDP target device connected to the LLDP master device forms a non-ring network structure, the specific topology structure of the LLDP target device can be obtained as follows:

(1) The LLDP master device receives the neighbor advertisement message, which carries the device identification TLV and the interface identification TLV, and the LLDP master device identifies the LLDP target at the end of the link from the device identification TLV and the interface identification TLV The device obtains the identification information of the LLDP target device at the end of the link and the network topology from the LLDP target device at the end of the link to the LLDP master device;

(2) The LLDP master device sends a topology query request to the LLDP target device at the end of the link. The topology query request carries the TLV shown in Table 3. The LLDP target device that receives the topology query request can identify the Topology query request.

(3) After receiving the topology query request, the LLDP target device recognizes that it is a topology query request, adds its own identification information and the interface information that received the topology query request to the topology query request, and forwards it to the next-hop LLDP target device . The LLDP target device may add its own identification information and interface information that receives the topology query request to the topology query request in the form of a device identifier TLV and an interface identifier TLV.

The topology query request can carry hop count information. After receiving the topology query request, the LLDP target device in the middle can reduce the hop count by 1, and the LLDP target device that is 0 after the deduction can be the LLDP target device at the end of the link. Of course, The LLDP target device can also identify whether it is the LLDP target device at the end of the link according to the identification information of the LLDP target device in the topology query request.

(4) After the LLDP target device at the end of the link receives the topology query request, it encapsulates the topology information of other LLDP target devices carried in the topology query request in the form of link topology TLV (see Table 5), and combines it with the LLDP master device The identification information of the LLDP master device can be carried in the response message in the form of the target option TLV shown in Table 2; during the forwarding process of the response message, other target devices continue to add link topology information. In this way, the response packet received by the LLDP master device carries the topology structure from the LLDP master device to the LLDP target device at the end of the link and the topology structure from the LLDP target device at the end of the link to the LLDP master device. The bidirectional link topology between the LLDP master device and the LLDP target device to be configured is found in the response packet.

In order for the LLDP target device to identify the LLDP master device, the LLDP master device can also carry the Proxy ID in the neighbor notification message sent, so that the LLDP target device can identify the LLDP master device that can communicate with the OSS based on the Proxy ID.

After the LLDP master device obtains the topology structure of the LLDP target device, it can also generate a neighbor entry locally. The neighbor entry can include the identification information of the neighbor device, the network topology information of the neighbor, such as the outgoing interface, etc. The neighbor entry can also include Including the SNMP version number and SNMP ID of the neighbor. The neighbor table may also include the number of hops from the LLDP master device to each LLDP target device, and the like.

Step 520, the LLDP master device queries the correspondence between the identification information of the LLDP target device and the forwarding information of the LLDP target device according to the identification information of the LLDP target device to be configured, so as to obtain the forwarding information of the LLDP target device to be configured.

Specifically, the forwarding information obtained by the LLDP master device may be the outbound interface information on the LLDP master device connected to the LLDP target device to be configured. The process of obtaining the forwarding information is that the LLDP master device queries the neighbor table, which stores the LLDP target device The correspondence between the identification information of the LLDP target device and the forwarding information of the LLDP target device.

After receiving the management request information carrying the LLDP target device ID, the LLDP master device queries the forwarding information corresponding to the LLDP target device ID in the neighbor table of the LLDP master device. Wherein, the neighbor table of the LLDP master device is shown in Table 8.

In addition, if the interface of the LLDP master device is turned from up to down, the neighbor entries passing through the interface of this end are deleted. When the state of a neighbor device changes, the LLDP target device encapsulates the neighbor information it maintains into an LLDP packet and reports it to the LLDP master device, and the LLDP master device encapsulates it into an IP packet and reports it to the OSS.

Step 530, the LLDP master device encapsulates the SNMP message into an LLDP message, and forwards the LLDP message to the LLDP target device to be configured according to the obtained forwarding information, so that the LLDP target device to be configured is configured using the configuration information.

The LLDP master device can encapsulate the SNMP message into the LLDP message in the form of TLV. Before the encapsulation, the LLDP master device can also obtain the information of the LLDP target device to be configured according to the identification information of the LLDP target device to be configured. The identifiable SNMP version information is used to convert the configuration information required by the LLDP target device to be configured according to the SNMP version information.

The SNMP message carries configuration information, and the LLDP target device to be configured can be configured according to the parameters and corresponding values in the configuration information.

Therefore, in the device configuration method in the network provided by the embodiment of the present invention, the LLDP master device receives the management request information carrying the LLDP target device identifier sent by the OSS in the form of an SNMP message, and obtains the forwarding information of the LLDP target device according to the LLDP target device identifier According to the forwarding information of the LLDP target device, the management request information is encapsulated into the LLDP message through the SNMP message and sent to the LLDP target device. Finally, the management request response information is decapsulated into an SNMP message and sent to the OSS, so that the OSS can remotely manage the LLDP target device without obtaining an IP address.

Fig. 6 is a flowchart of a device configuration method in a network provided by an embodiment of the present invention. As shown in the figure, the embodiment of the present invention specifically includes:

Step 610, the LLDP target device receives the management request information carrying the LLDP target device identifier sent by the LLDP master device in the form of encapsulating the SNMP message into an LLDP message. Wherein, the management request information includes query request information or configuration request information.

Step 620, when the LLDP target device ID is the same as the LLDP target device ID, decapsulate the management request information into an SNMP message, and perform processing corresponding to the management request information, so as to obtain management request response information.

Further, step 620 also includes: when the target device identifier in the message is different from the LLDP target device identifier, query the forwarding information corresponding to the target device identifier in the message in the LLDP target device forwarding table; and insert the device according to the forwarding information After the TLV and interface TLV, the SNMP over LLDP packet is forwarded to the next-hop LLDP target device or LLDP master device.

Further, before step 620, the method further includes: the LLDP target device actively sends a neighbor advertisement, so as to facilitate the intermediate target device and the LLDP master device to learn neighbor entries. In addition to the standard capabilities defined by the LLDP protocol, the notification information also includes an SNMP version number and an SNMP identifier.

The LLDP target device establishes the neighbor table of the LLDP target device, and the result of the neighbor forwarding table is shown in Table 9. When the LLDP target device receives the LLDP packet sent by the neighbor, it learns or refreshes the neighbor table entry. In addition to the neighbor ID, the table entry also learns the neighbor’s hop count, the receiving interface, and the neighbor’s proxy priority. The interface is generally The outgoing interface for forwarding packets, and the priority is used to identify whether the neighbor has the proxy management capability and the priority of proxy management. Generally speaking, the LLDP master device is capable of proxy management. When the network scale is large or requires high reliability, two or more LLDP master devices can be set up. Different LLDP master devices should use Proxy to indicate The priority of agent management.

When the interface of the LLDP target device changes from up to down, delete the neighbor entries learned by the interface, including directly connected neighbors and non-directly connected neighbors. And when there is a neighbor state change, the LLDP target device encapsulates the neighbor information maintained by itself into an LLDP packet and reports it to the LLDP master device, and the LLDP master device encapsulates it into an IP packet and reports it to the OSS.

Step 630: Encapsulate the management request response information into an LLDP message through the SNMP message and send it to the LLDP master device, so that the LLDP master device forwards the management request response information to the operation support system OSS through the SNMP message.

Further, step 630 also includes: when using SNMP over LLDP to send a response to the LLDP master device, use the target device TLV to specify the LLDP master device, and the LLDP master device can be identified according to the source MAC in the management request message, regardless of Proxy priority of the LLDP master device. Before forwarding the message, the LLDP target device also needs to learn the forwarding information to the LLDP master device, and the forwarding information can be learned or refreshed when receiving an SNMP over LLDP management request.

Therefore, in the device configuration method in the network provided by the embodiment of the present invention, the LLDP target device receives the management request information carrying the LLDP target device identifier sent by the LLDP master device by encapsulating the LLDP message into an LLDP message. When the target device ID in LLDP is the same as the LLDP target device ID, the management request information will be decapsulated into an SNMP message, and the corresponding processing will be performed to obtain the management request response information, and the management request response information will be passed through SNMP The message is encapsulated into an LLDP message and sent to the LLDP master device, so that the LLDP master device forwards the management request response information to the operation support system OSS in the form of an SNMP message, so that the OSS can communicate with the LLDP target device without obtaining an IP address. remote management.

FIG. 7 is an information interaction diagram of a device configuration method in a network provided by an embodiment of the present invention. As shown in the figure, the embodiment of the present invention specifically includes:

In step 701, the OSS sends management request information carrying the identifier of the LLDP target device to the LLDP master device in the form of an SNMP message. Wherein, the management request information includes query request information or configuration request information.

In step 702, the LLDP master device determines the target device to be configured after receiving the management request information carrying the LLDP target device identifier. If the target setting is consistent with the LLDP master device, the configuration or query request is directly processed; if other LLDP target devices are configured as a proxy, the neighbor table is queried, and step 703 is executed.

Step 703, the LLDP master device completes the SNMP version and identifier conversion according to the SNMP version and SNMP identifier queried in the neighbor table, and adds LLDP encapsulation, uses the target device TLV in the encapsulation to specify the target device to be configured, and uses the SNMP TLV to encapsulate Original SNMP message, which does not contain IP and UDP headers.

Step 704, after the LLDP target device 1 receives the SNMP over LLDP message sent by the LLDP master device, it learns or refreshes the neighbor table entry, and compares the LLDP target device ID carried in the message with its own device ID. If the ID of the target device is the same as the ID of the LLDP target device 1, execute step 707; when the ID of the target device in the packet is different from the ID of the LLDP target device 1, execute step 705.

Step 705, LLDP target device 1 queries the neighbor table, and forwards the management configuration request according to the outgoing interface in the neighbor table; before forwarding, it will insert the device TLV and the interface TLV that receives the message, and learn or refresh the neighbor table entry.

Step 706, after the LLDP target device 2 receives the management configuration request message forwarded by the LLDP target device 1, it learns or refreshes the neighbor entry, and compares the target device identifier carried in the device query message with its own device identifier, When the target device ID is the same as the LLDP target device 1 ID, execute step 707; when the target device ID is different from the LLDP target device 1 ID, query the neighbor entry and forward it to the next-hop LLDP target according to the outgoing interface in the neighbor entry The device will insert the device TLV and the interface TLV that receives the packet before forwarding.

In step 707, the LLDP target device 2 decapsulates the management request information into an SNMP message, and performs processing corresponding to the management request information, thereby obtaining management request response information. Then execute step 708 .

In step 708, the LLDP target device 2 encapsulates the management request response information in the form of an SNMP over LLDP message, encapsulates the SNMP response message with the SNMP TLV, and sends it to the LLDP master device through the target device TLV. Before sending, it will query the neighbor table from the The outgoing interface in the neighbor table sends.

Step 709, after receiving the management request response information encapsulated by SNMP over LLDP, the LLDP target device 1 learns or refreshes the neighbor table, and queries the neighbor table through the target device TLV to obtain the outbound interface. Then step 710 is executed.

Step 710, the LLDP target device 1 forwards the LLDP message according to the outgoing interface found in the neighbor table, and inserts the device TLV and the interface TLV that receives the message before forwarding.

Step 711, after the LLDP master device receives the management request response information, it recognizes that the message should be processed through the target device TLV, takes out the original SNMP message from the SNMP TLV, completes the SNMP format and identification conversion, and uses the standard SNMP message Formal response to the operation support system OSS (step 712), the standard SNMP message is encapsulated in IP message format.

Therefore, in the device configuration method in the network provided by the embodiment of the present invention, the LLDP master device receives the management request information carrying the LLDP target device identifier sent by the OSS in the form of an SNMP message, and obtains the LLDP target device according to the target device identifier in the message. forwarding information, forward the management request information to LLDP target device 1 or LLDP target device 2 according to the forwarding information, and LLDP target device 1 or LLDP target device 2 receives the management request information, when the target device identifier in the packet is consistent with the LLDP When the target device IDs are the same, the management request information is decapsulated into an SNMP message, and the corresponding processing is performed to obtain the management request response information, and the management request response information is encapsulated into an LLDP message through the SNMP message When the LLDP master device receives the management request response information sent by LLDP target device 1 or LLDP target device 2 by encapsulating SNMP packets into LLDP packets, it decapsulates the management request response information into SNMP packets. After converting the SNMP version and identifier, it sends it to the OSS in a standard SNMP message format, so that the OSS can remotely manage the LLDP target device without obtaining an IP address.

FIG. 8 is a schematic structural diagram of a link layer discovery protocol LLDP device provided by an embodiment of the present invention. The LLDP device is used to execute the device configuration method in the network provided in FIG. 3 to FIG. 7 . As shown in the figure, the embodiment of the present invention specifically includes: a first port 81 , a second port 82 , a data receiver 83 , a processor 84 and a data transmitter 85 .

The first port 81 is used to connect to the operation support system OSS;

The second port 82 is used to connect one or more LLDP target devices;

The data receiver 83 is used to receive the IP message of the OSS, extract the Simple Network Management Protocol SNMP message from the IP message, and carry the identification information of the LLDP target device to be configured and the required information of the LLDP target device to be configured in the SNMP message. configuration information;

The processor 84 is used to query the correspondence between the identification information of the LLDP target device and the forwarding information of the LLDP target device according to the identification information of the LLDP target device to be configured, thereby obtaining the forwarding information of the LLDP target device to be configured; and encapsulating the SNMP message into the LLDP packet;

The data transmitter 85 is configured to send the LLDP message to the LLDP target device to be configured according to the obtained forwarding information, so that the LLDP target device uses configuration information for configuration.

In one embodiment, the processor 84 is further configured to acquire the topology of one or more LLDP target devices; the data transmitter is also configured to report the acquired topology to the OSS.

In another embodiment, one or more LLDP target devices and the LLDP master device form a ring network structure, then the data transmitter 85 is also used to send a neighbor notification message to one or more LLDP target devices, so that the neighbors can be received The LLDP target device of the notification message adds its own identification information and the interface information that receives the Neighbor Advertisement message to the Neighbor Advertisement message and sends it to the next-hop LLDP target device; the data receiver 83 is also used to receive the Neighbor Advertisement report The processor 84 is also configured to obtain the topology structure of one or more LLDP target devices from the received Neighbor Advertisement message.

Therefore, the LLDP device provided by the embodiment of the present invention receives the management request information carrying the LLDP target device identifier sent by the OSS in the form of an SNMP message, obtains the forwarding information of the LLDP target device according to the LLDP target device identifier, and obtains the forwarding information of the LLDP target device according to the forwarding information of the LLDP target device. The information sends the management request information to the LLDP target device in the form of SNMP packets encapsulated into LLDP packets. After receiving the management request response information sent by the LLDP target device in the form of LLDP packets encapsulated in SNMP packets, the management request response information Decapsulate it into an SNMP message and send it to the OSS, so that the OSS can remotely manage the LLDP target device without obtaining an IP address.

FIG. 9 is a schematic structural diagram of a device configuration system provided by an embodiment of the present invention. As shown in the figure, the device is configured with a system link layer discovery protocol LLDP master device 91 and one or more LLDP target devices 92 , and one or more LLDP target devices 92 are connected to the OSS through the LLDP master device 91 .

The LLDP main device 91 is used to receive the IP message of the operation support system OSS, extract the Simple Network Management Protocol SNMP message from the IP message, and carry the identification information of the LLDP target device to be configured and the LLDP message to be configured in the SNMP message The configuration information required by the target device; according to the identification information of the LLDP target device to be configured, query the corresponding relationship between the identification information of the LLDP target device and the forwarding information of the LLDP target device, thereby obtaining the forwarding information of the LLDP target device to be configured; and the SNMP The message is encapsulated into the LLDP message, and the LLDP message is sent to the LLDP target device to be configured according to the obtained forwarding information, so that the LLDP target device uses the configuration information for configuration.

In one embodiment, the LLDP master device 91 is further configured to obtain the topology structure of one or more LLDP target devices, and report the obtained topology structure to the OSS.

In another embodiment, one or more LLDP target devices 92 and LLDP master device 91 form a ring network structure, then the LLDP master device 91 is specifically used to send a neighbor notification message to one or more LLDP target devices; receive a neighbor notification message, obtain the topology structure of one or more LLDP target devices from the received Neighbor Advertisement message; the LLDP target device is used to receive the Neighbor Advertisement message, and send its own identification information and the interface information that received the Neighbor Advertisement message Added to the Neighbor Advertisement message and sent to the next-hop LLDP target device.

Professionals should further realize that the units and algorithm steps described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the relationship between hardware and software Interchangeability. In the above description, the composition and steps of each example have been generally described according to their functions. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present invention.

The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be implemented by hardware, software modules executed by a processor, or a combination of both. Software modules can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other Any other known storage medium.

The specific embodiments described above have further described the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above descriptions are only specific embodiments of the present invention and are not intended to limit the scope of the present invention. Protection scope, within the spirit and principles of the present invention, any modification, equivalent replacement, improvement, etc., shall be included in the protection scope of the present invention.

Claims (17)

1. the equipment configuration method in a kind of network, the network include OSS OSS, Link Layer Discovery Protocol LLDP Main equipment and one or more LLDP target devices, one or more of LLDP target devices pass through the LLDP main equipments Connect the OSS, methods described includes：

The LLDP main equipments receive the IP messages of the OSS, and Simple Network Management Protocol SNMP is extracted from the IP messages Message, carries the identification information and the LLDP mesh to be configured of LLDP target devices to be configured in the SNMP messages Configuration information needed for marking device；

Mark of the LLDP main equipments according to the identification information-enquiry LLDP target devices of the LLDP target devices to be configured The corresponding relation of the forwarding information of knowledge information and LLDP target devices, so as to obtain the forwarding of the LLDP target devices to be configured Information；

The SNMP messages are packaged into LLDP messages by the LLDP main equipments, are reported the LLDP according to the forwarding information for obtaining Text is sent to the LLDP target devices to be configured, so that the LLDP target devices are matched somebody with somebody using the configuration information Put.

2. the equipment configuration method in network according to claim 1, it is characterised in that the forward packets of the acquisition Include the outgoing interface for connecting the LLDP target devices to be configured on the LLDP main equipments.

3. the equipment configuration method in network according to claim 1, it is characterised in that the LLDP main equipments will be described SNMP messages are packaged into LLDP messages and specifically include：

The LLDP main equipments are encapsulated into the SNMP messages in the LLDP messages in the form of type lengths values TLV.

4. the equipment configuration method in network according to claim 3, it is characterised in that the LLDP messages are also carried For identifying the TLV of the LLDP target devices to be configured, the TLV for identifying LLDP target devices to be configured takes Identification information with the LLDP target devices to be configured.

5. the equipment configuration method in network according to claim 1, it is characterised in that the LLDP main equipments receive institute Also include before the IP messages for stating OSS：

The topological structure of one or more of LLDP target devices is obtained, the topological structure of acquisition is reported into the OSS.

6. the equipment configuration method in network according to claim 5, it is characterised in that one or more of LLDP mesh Marking device constitutes ring network structure with the LLDP main equipments, then obtain the topological structure of one or more of LLDP target devices Specifically include：

The LLDP main equipments send neighbor advertisement message to one or more of LLDP target devices, so that receiving neighbour The LLDP target devices of notification packet are occupied by the identification information of itself and the interface message addition of neighbor advertisement message is received To in neighbor advertisement message, down hop LLDP target device sends；

The LLDP main equipments receive neighbor advertisement message, from the neighbor advertisement message for receiving obtain one or more of The topological structure of LLDP target devices.

7. the equipment configuration method in network according to claim 6, it is characterised in that the LLDP main equipments are in side Connect a LLDP target devices, connect the 2nd LLDP target devices in opposite side, the LLDP main equipments to one or Multiple LLDP target devices send neighbor advertisement message and specifically include：

The LLDP main equipments send the first neighbor advertisement message to a LLDP target devices, so that receiving described the The LLDP target devices of one neighbor advertisement message are by the identification information of itself and receive the interface of the first neighbor advertisement message Information is added in the first neighbor advertisement message, and the forwarding of down hop LLDP target device；

The LLDP main equipments send the second neighbor advertisement message to the 2nd LLDP target devices, so that receiving described the The LLDP target devices of two neighbor advertisement messages are by the identification information of itself and receive the interface of the second neighbor advertisement message Information is added in the second neighbor advertisement message, and the forwarding of down hop LLDP target device；

The LLDP main equipments receive the first neighbor advertisement message and the second neighbor advertisement message, are led to according to the first neighbours for receiving Accuse the topological structure of message and the one or more of LLDP target devices of the second neighbor advertisement Receive message.

8. the equipment configuration method in network according to claim 7, it is characterised in that the first neighbor advertisement message Proxy marks are acted on behalf of with also carrying in the second neighbor advertisement message, so that reception the first neighbor advertisement message, Or the LLDP target devices of the second neighbor advertisement message learn the identification information of the LLDP main equipments.

9. the equipment configuration method in network according to claim 5, it is characterised in that one or more of LLDP mesh Marking device constitutes non-ring network structure with the LLDP main equipments, then obtain the topology knot of one or more of LLDP target devices Structure is specifically included：

The LLDP main equipments receive the neighbor advertisement message of LLDP target devices, obtain and be in from the neighbor advertisement message The topology of the identification information of the LLDP target devices of link end and the arrival LLDP target devices in link end Information；

The LLDP main equipments are according to the topology information of the LLDP target devices for reaching the link end to the link end LLDP target devices send Query of Topological request so that receive the LLDP target devices of Query of Topological request by itself Identification information and receive the interface message of Query of Topological request and be added in Query of Topological request, and down hop LLDP Target device is forwarded；

Receive the response message for Query of Topological request of the LLDP target devices from link end, the response message In carry from the LLDP main equipments to the topological structure of the link end LLDP target devices and from the link end Topological structure of the end LLDP target devices to the LLDP main equipments；

The LLDP main equipments according to the response message of link end equipment carry from the LLDP main equipments to the link The topological structure of end LLDP target devices and from link end LLDP target devices the opening up to the LLDP main equipments Flutter Structure Calculation and go out full link topology.

10. the equipment configuration method in network according to claim 9, it is characterised in that in the Query of Topological request Proxy marks are carried also, so that the LLDP target devices for receiving the Query of Topological request learn the LLDP main equipments Identification information.

Equipment configuration method in 11. networks according to claim 1-10 any one, it is characterised in that the LLDP Before the SNMP messages are encapsulated into LLDP messages by main equipment, methods described also includes：

The LLDP main equipments are additionally operable to obtain described to be configured according to the identification information of the LLDP target devices to be configured The SNMP version informations that can recognize of LLDP target devices, according to the SNMP version informations to the LLDP mesh to be configured Configuration information needed for marking device is changed.

12. a kind of Link Layer Discovery Protocol LLDP equipment, it is characterised in that the equipment includes：

First interface, for connecting OSS OSS；

Second interface, for connecting one or more LLDP target devices；

Data sink, for receiving the IP messages of the OSS, extracts Simple Network Management Protocol SNMP from the IP messages Message, carries the identification information and the LLDP mesh to be configured of LLDP target devices to be configured in the SNMP messages Configuration information needed for marking device；

Processor, the mark for the identification information-enquiry LLDP target devices according to the LLDP target devices to be configured are believed The corresponding relation of the forwarding information of breath and LLDP target devices, so as to the forwarding for obtaining the LLDP target devices to be configured is believed Breath；And the SNMP messages are encapsulated in LLDP messages；

Data transmitter, for the LLDP messages are sent to the LLDP to be configured according to the forwarding information of the acquisition Target device, so that the LLDP target devices are configured using the configuration information.

13. LLDP equipment according to claim 12, it is characterised in that

The processor is additionally operable to the topological structure for obtaining one or more of LLDP target devices；

The data transmitter is additionally operable to for the topological structure of acquisition to report the OSS.

14. LLDP equipment according to claim 13, it is characterised in that one or more of LLDP target devices and institute LLDP main equipments composition ring network structure is stated, then

The data transmitter, is additionally operable to send neighbor advertisement message to one or more of LLDP target devices, so that The LLDP target devices of neighbor advertisement message are received by the identification information of itself and the interface of neighbor advertisement message is received During information is added to neighbor advertisement message, down hop LLDP target device sends；

The data sink, is additionally operable to receive neighbor advertisement message；

The processor, is additionally operable to obtain opening up for one or more of LLDP target devices from the neighbor advertisement message for receiving Flutter structure.

15. a kind of equipment configuration systems, it is characterised in that the system includes Link Layer Discovery Protocol LLDP main equipments and one Individual or multiple LLDP target devices, one or more of LLDP target devices connect OSS by the LLDP main equipments,

The LLDP main equipments, for receiving the IP messages of OSS OSS, extract simple network from the IP messages Management agreement SNMP messages, carry the identification information of LLDP target devices to be configured and described treat in the SNMP messages Configuration information needed for the LLDP target devices of configuration；According to the identification information-enquiry of the LLDP target devices to be configured The corresponding relation of the identification information of LLDP target devices and the forwarding information of LLDP target devices, it is described to be configured so as to obtain The forwarding information of LLDP target devices；And the SNMP messages are encapsulated in LLDP messages, according to the forwarding of the acquisition The LLDP messages are sent to the LLDP target devices to be configured by information, so that the LLDP target devices utilize institute State configuration information to be configured.

16. equipment configuration systems according to claim 15, it is characterised in that the LLDP main equipments are additionally operable to obtain institute The topological structure of one or more LLDP target devices is stated, the topological structure of acquisition is reported into the OSS.

17. equipment configuration systems according to claim 16, it is characterised in that one or more of LLDP target devices Ring network structure is constituted with the LLDP main equipments, then

The LLDP main equipments are specifically for sending neighbor advertisement message to one or more of LLDP target devices；Receive Neighbor advertisement message, obtains the topological structure of one or more of LLDP target devices from the neighbor advertisement message for receiving；

The LLDP target devices are used for, and receive neighbor advertisement message, by the identification information of itself and receive neighbor advertisement During the interface message of message is added to neighbor advertisement message, down hop LLDP target device sends.