WO2016015606A1

WO2016015606A1 - Method for locating port connection error and related device

Info

Publication number: WO2016015606A1
Application number: PCT/CN2015/085123
Authority: WO
Inventors: 陈照宇
Original assignee: 华为技术有限公司
Priority date: 2014-07-31
Filing date: 2015-07-25
Publication date: 2016-02-04
Also published as: CN105450432A

Abstract

The present invention relates to the field of communications. Provided in an embodiment of the present invention are a method for locating a port connection error and related device, facilitating efficient location of a physical connection error of a port in certain scenarios. The specific solution comprises: the first port of a first device sends a local system management information base (MIB) of the first port to the second port of a second device; the third port of the first device receives the local system MIB of the first port sent by the second port of the second device; when the first device determines that the local system MIB of the third port is different from the local system MIB of the first port sent by the second device, the first device determines that an error occurred in a physical connection between the first port and the second device or between the third port and the second device. The present invention is used to locate a physical connection error of ports.

Description

Method and related device for locating port connection error

Technical field

The present invention relates to the field of communications, and in particular, to a method and related device for locating port connection errors.

Background technique

For some network devices on the live network, there may be an error in the physical connection of the port during the fiber connection construction. A situation in which the physical connection of the port is incorrect may be a broken line. As shown in FIG. 1, the A device includes port 1, port 2, and port 3. The B device includes port 1 ', port 2', and port 3'. The correct port connection is the RX connection of port 1's TX and port 1'. The RX of port 1 is connected to the TX of port 1'. However, if the RX of port 2 is connected to the TX of port 3', and the RX of port 3 is connected to the TX of port 2', a squall line appears. The presence of a squall line may cause communication to fail. As a result, business traffic cannot be forwarded.

The Link Layer Discovery Protocol (LLDP) provides a standard link layer discovery method. Each port of the first device and the second device independently maintains a local system management information base (MIB) and a remote system MIB. Each port of the first device can periodically organize information such as a primary capability, a management address, a device identifier, and a port identifier of the first device into different types/Length/Values (TLVs), and is encapsulated in In an LLDP packet. The port of the first device may send the LLDP packet to the port of the second device directly connected to the port of the first device. The second device is a neighbor device of the first device. The second device performs validity check on the received LLDP packet and the TLV carried by the LLDP packet, and saves the received local system MIB of the first device as the remote system MIB of the port of the second device. If the LLDP local system MIB or the LLDP remote system MIB of the port of the second device changes, the port of the second device of the neighbor sends an LLDP alarm, indicating that there is a problem with the physical connection of the port of the second device.

The above method for determining whether a physical connection of a port is problematic through the LLDP protocol cannot efficiently locate whether a physical connection of a port is incorrect in some scenarios. For example, when a fiber connection is made, a twist line appears, and the TX of the port of the network device can transmit light. The signal, and the RX of the port can receive the optical signal, the problem of the port physical connection sending error cannot be found. Therefore, it is not possible to locate the physical connection of the port in time.

Summary of the invention

Embodiments of the present invention provide a method and related apparatus for locating port connection errors, which in some scenarios facilitates an error in physically connecting a port.

In order to achieve the above object, embodiments of the present invention adopt the following technical solutions:

The first aspect provides a method for locating a port connection error, including:

The first port of the first device sends the local system management information base MIB of the first port to the second port of the second device;

The third port of the first device receives the local system MIB of the first port sent by the second port of the second device;

Determining, by the first device, that the local system MIB of the third port is different from the local system MIB of the first port that is sent by the second device;

Determining, by the first device, that the physical connection between the first port and the second device is incorrect or the third port is different, based on the local system MIB of the third port being different from the local MIB system of the first port The physical connection of the second device is incorrect.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the third port of the first device receives the local system MIB of the first port that is sent by the second port of the second device The third port of the first device receives the identifier information sent by the second port of the second device, where the identifier information is used to identify that the local system MIB of the first port sent by the second device is a remote system MIB of the port of the second device;

The determining, by the first device, that the local system MIB of the third port is different from the local system MIB of the first port that is sent by the second device includes:

The first device compares the local system MIB of the third port with the local system MIB of the first port sent by the second device, according to the indication of the identifier information;

The first device determines that the local system MIB of the third port is different from the local system MIB of the first port based on the result of the comparison.

In conjunction with the first possible implementation of the first aspect, in a second possible implementation manner of the first aspect, the third port of the first device receives the second The local system MIB of the first port sent by the port specifically includes:

The third port of the first device receives the link layer discovery protocol LLDP packet sent by the second port of the second device, where the LLDP packet carries the local system MIB of the first port and the identifier information.

With reference to the second possible implementation of the first aspect, in a third possible implementation manner of the first aspect, the LLDP packet includes a first TLV and a second TLV, where the identifier information includes the first TLV. The value of the type field and the value of the type field in the second TLV, the value of the type field in the first TLV indicates that the information string field in the first TLV carries the identifier of the device, the second TLV The value of the type field in the second TLV indicates that the information string field in the second TLV carries the identifier of the port, and the remote system MIB of the port of the second device includes the identifier of the first device and the first port The identifier of the type field in the first TLV is used to identify that the identifier of the first device sent by the second device is the first one of the remote system MIBs of the port of the second device The identifier of the device, the value of the type field in the second TLV is used to identify that the identifier of the first port sent by the second device is the first in the remote system MIB of the port of the second device The identity of a port.

In conjunction with the first aspect to any one of the third possible implementation manners of the first aspect, in a fourth possible implementation manner of the first aspect, the first device sends an error alarm to the management device, The error alarm carries the identifier of the first port or the identifier of the third port, and the identifier of the first port in the error alarm is used to identify that the physical connection between the first port and the second device occurs. The identifier of the third port in the error alarm is used to identify that the physical connection between the third port and the second device is incorrect.

In a second aspect, a method for locating a port connection error is provided, including:

The second port of the second device receives the local system management information base MIB of the first port sent by the first port of the first device;

The second port of the second device sends the local system MIB of the first port to the third port of the first device.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the sending, by the second port of the second device, the local system MIB of the first port to the third port of the first device further includes :

The second port of the second device sends the identifier information to the third port of the first device, where the identifier information is used to identify that the local system MIB of the first port sent by the second device is the first The remote system MIB of the port of the second device.

In conjunction with the first possible implementation of the second aspect, in a second possible implementation manner of the second aspect, the second port of the second device sends the first port to the third port of the first device A port's local system MIB includes:

The second port of the second device sends a link layer discovery protocol LLDP packet to the third port of the first device, where the LLDP packet carries the local system MIB of the first port and the identifier information. .

With reference to the second possible implementation of the second aspect, in a third possible implementation manner of the second aspect, the LLDP packet includes a first TLV and a second TLV, where the identifier information includes the first TLV. The value of the type field and the value of the type field in the second TLV, the value of the type field in the first TLV indicates that the information string field in the first TLV carries the identifier of the device, the second TLV The value of the type field in the second TLV indicates that the information string field in the second TLV carries the identifier of the port, and the remote system MIB of the port of the second device includes the identifier of the first device and the first port The identifier of the type field in the first TLV is used to identify that the identifier of the first device sent by the second device is the first one of the remote system MIBs of the port of the second device The identifier of the device, the value of the type field in the second TLV is used to identify that the identifier of the first port sent by the second device is the first in the remote system MIB of the port of the second device The identity of a port.

In a third aspect, a first device is provided, where the first device includes a first port and a third port, including:

a sending unit, configured to send, by using the first port, a local system management information base MIB of the first port to a second port of the second device;

a receiving unit, configured to receive, by using the third port, a local system MIB of the first port that is sent by the second port of the second device;

a determining unit, configured to determine that the local system MIB of the third port is different from the local system MIB of the first port that is sent by the second device by the receiving unit;

The determining unit is further configured to determine, according to the local system MIB of the third port, different from the local MIB system of the first port, that the first port and the second device are An error occurs in the physical connection or an error occurs in the physical connection of the third port to the second device.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the receiving unit is further configured to receive, by using the third port, identifier information that is sent by a second port of the second device, where The identifier information is used to identify that the local system MIB of the first port sent by the second device is a remote system MIB of the port of the second device;

The determining unit is specifically configured to:

Comparing the local system MIB of the third port with the local system MIB of the first port sent by the second device according to the indication of the identifier information;

Based on the result of the comparison, it is determined that the local system MIB of the third port is different from the local system MIB of the first port.

With the first possible implementation of the third aspect, in a second possible implementation manner of the third aspect, the receiving unit is configured to: receive, by using the third port, a second port of the second device The transmitted link layer discovery protocol LLDP packet carries the local system MIB of the first port and the identifier information.

With reference to the second possible implementation of the third aspect, in a third possible implementation manner of the third aspect, the LLDP packet includes a first TLV and a second TLV, and the identifier information includes the first TLV. The value of the type field and the value of the type field in the second TLV, the value of the type field in the first TLV indicates that the information string field in the first TLV carries the identifier of the device, the second TLV The value of the type field in the second TLV indicates that the information string field in the second TLV carries the identifier of the port, and the remote system MIB of the port of the second device includes the identifier of the first device and the first port The identifier of the type field in the first TLV is used to identify that the identifier of the first device sent by the second device is the first one of the remote system MIBs of the port of the second device The identifier of the device, the value of the type field in the second TLV is used to identify that the identifier of the first port sent by the second device is the first in the remote system MIB of the port of the second device The identity of a port.

With reference to any one of the third aspect to the third possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, the sending unit is further configured to:

Sending an error alarm to the management device, where the error alarm carries the identifier of the first port or the identifier of the third port, and the identifier of the first port in the error alarm is used An error is generated in the physical connection between the first port and the second device, and the identifier of the third port in the error alarm is used to identify that the physical connection between the third port and the second device occurs. error.

In a fourth aspect, a second device is provided, where the second device includes a second port, including:

a receiving unit, configured to receive, by using the second port, a local system management information base MIB of the first port that is sent by the first port of the first device;

And a sending unit, configured to send, by using the second port, a local system MIB of the first port that is received by the receiving unit to a third port of the first device.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the sending unit is further configured to: send, by using the second port, identifier information to a third port of the first device, where the identifier is The information is used to identify that the local system MIB of the first port sent by the second device is a remote system MIB of a port of the second device.

In conjunction with the first possible implementation of the fourth aspect, in a second possible implementation manner of the fourth aspect, the sending unit is configured to: use the second port to the third port of the first device The link layer discovery protocol LLDP packet is sent, where the LLDP packet carries the local system MIB of the first port and the identifier information.

With the second possible implementation of the fourth aspect, in a third possible implementation manner of the fourth aspect, the LLDP packet includes a first TLV and a second TLV, where the identifier information is included in the first TLV. The value of the type field and the value of the type field in the second TLV, the value of the type field in the first TLV indicates that the information string field in the first TLV carries the identifier of the device, the second TLV The value of the type field in the second TLV indicates that the information string field in the second TLV carries the identifier of the port, and the remote system MIB of the port of the second device includes the identifier of the first device and the first port The identifier of the type field in the first TLV is used to identify that the identifier of the first device sent by the second device is the first one of the remote system MIBs of the port of the second device The identifier of the device, the value of the type field in the second TLV is used to identify that the identifier of the first port sent by the second device is the first in the remote system MIB of the port of the second device The identity of a port.

The embodiment of the invention provides a method for locating a port connection error and a related device, where the first port of the first device sends the local port of the first port to the second port of the second device The system management information base MIB, and the third port of the first device receives the local system MIB of the first port sent by the second port of the second device, where the first device determines the local system MIB of the third port and the second device sends When the local system MIB of the first port is different, the first device determines that the physical connection between the first port and the second device is incorrect or the physical connection between the third port and the second device is incorrect. The above technical solution helps to make an error in the physical connection of the efficiently located port.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

1 is a schematic diagram of a physical connection error of a port of a network device;

2 is a schematic flowchart of a method for locating a port connection error according to an embodiment of the present invention;

3 is a schematic flowchart of another method for locating a port connection error according to an embodiment of the present invention;

4 is a schematic flowchart of another method for locating a port connection error according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a first device frame according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram of a second device according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of a first device according to an embodiment of the present disclosure;

FIG. 8 is a schematic diagram of a second device according to an embodiment of the present invention.

detailed description

The technical solutions in the embodiments of the present invention will be clearly described below with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and It is the entire embodiment. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

If not stated to the contrary, the device referred to in this application may be a router. The port mentioned in this application refers to a physical port. The port can be an optical port. The optical port can be an Ethernet interface. The optical port can include an optical modem. The optical port may include a transmitting end (TX) and a receiving end (RX). The transmitting end may correspond to one optical fiber, and the receiving end may correspond to another optical fiber.

The MIB involved in this application may be an LLDP MIB. The local system MIB (English: local system MIB) may be specifically an LLDP local system MIB. The remote system MIB (English: remote system MIB) may be specifically an LLDP remote system MIB. For the above technical terms, reference can be made to IEEE P802.1AB-REV/D6.0. For example, reference can be made to 11. LLDP MIB definitions in IEEE P802.1AB-REV/D6.0.

The local system MIB of the port involved in the present application is generated by the device to which the port belongs, and can be sent to the MIB of the neighbor device through the port. The port of the neighboring device receives the local system MIB of the port, and the local system MIB of the port can be saved as the remote MIB of the port of the neighboring device. The neighbor device may be an LLDP neighbor.

The remote system MIB of the port involved in the present application is that after the port receives the local system MIB of the neighbor device sent by the neighboring device, the device to which the port belongs saves the local system MIB of the neighbor device as the remote end of the port. System MIB. The neighbor device may be an LLDP neighbor.

The technical solution provided by the embodiment of the present invention can be applied to a network device connected through an optical fiber. For example, the network device can be a forwarding device such as a router. For example, the A device and the B device are connected by an optical fiber. The A device includes port 1, port 2, and port 3. The B device includes port 1 ', port 2', and port 3'. Port 1 corresponds to port 1 'one-to-one, port 2 corresponds to port 2', and port 3 and port 3' correspond one-to-one. The fiber-receiving connection between the fiber of each port and the peer port, that is, the port connection is correct, the TX of port 1 and the RX of port 1' should be connected, and the RX of port 1 and the TX of port 1'. And so on. Figure 1 shows the situation of the squall line. The RX of port 2 is connected to the TX of port 3', and the RX of port 3 is connected to the TX of port 2'. That is to say, in FIG. 1, port 1 is not implemented in one-to-one correspondence with port 2'. Port 1 does not have a one-to-one correspondence with port 3' in FIG. The above situation may lead to business failure Normal forwarding.

Embodiment 1

An embodiment of the present invention provides a method for locating a port connection error. Referring to FIG. 2, the steps include:

101. The first port of the first device sends the local system management information base MIB of the first port to the second port of the second device.

For example, in the link layer discovery protocol LLDP, each port of each device has a local system MIB and a remote system MIB, and each port independently maintains its own local system MIB and remote system MIB. Among them, "management information" refers to a collection of managed objects in the network management framework of the Internet. Managed objects must maintain several control and status information that can be read and written by the hypervisor. These managed objects constitute a virtual information store, so it is called the management information base MIB. A MIB is a database that represents a set of manageable objects for a device or service.

For example, for a port, the local system MIB stores the local MIB of the port, which is the information of the port to be sent to the peer device, and the remote MIB stores the port of the peer device connected to the port. The MIB, that is, the remote MIB stores information received from the port of the peer device. The MIB may include a device ID, a port ID, a system name, a system description, a port description, a device capability, and a network management address.

Specifically, the LLDP is applied, and the first port of the first device sends the local system MIB of the first port to the second port of the second device, where the first port of the first device is connected to the second port of the second device. The first LLDP packet is sent, and the first LLDP packet carries the local system MIB of the first port.

102. The third port of the first device receives the local system MIB of the first port sent by the second port of the second device.

After the second port of the second device receives the first LLDP packet sent by the first port of the first device, the second device establishes the remote MIB, that is, the second device carries the first port of the first LLDP packet. The local system MIB is saved as the remote system MIB of the second port to store the local system MIB of the first port sent by the first port of the first device.

Then, the second port of the second device returns the local system MIB of the first port to the first device by using the second LLDP packet, and the second LLDP packet carries the identifier information, where the identifier information is used to identify the second device. The local system MIB of the first port is the port of the second device Remote system MIB.

Specifically, the port of the second device may be the second port.

For example, the second LLDP packet may include a first TLV and a second TLV, where the identifier information includes a value of a type field in the first TLV and a value of a type field in the second TLV, and a type field in the first TLV. The value indicates that the information string field in the first TLV carries the identifier of the device, and the value of the type field in the second TLV indicates that the information string field in the second TLV carries the identifier of the port, and the port of the second device is far. The end system MIB includes an identifier of the first device and an identifier of the first port, where the value of the type field in the first TLV is used to identify that the identifier of the first device sent by the second device is the remote system MIB of the port of the second device. The first device identifier (Chassis ID), the value of the type field in the second TLV is used to identify that the identifier of the first port sent by the second device is the first port in the remote system MIB of the port of the second device Identification (Port ID).

Specifically, the identifier of the device carried in the information string field in the first TLV may be an identifier of the first device. The identifier of the port carried in the information string field in the second TLV may be an identifier of the first port.

This is because, in the existing LLDP packet, nine types of TLVs are defined. The value of the TLV type field uses 0-8 to indicate the local system MIB sent by the sender, so that two types of TLVs can be extended. The value of the TLV type field may be 9 and 10. The value of the TLV type field is 9 indicates that the device sends the device identifier in the remote system MIB of the port, and the value of the TLV type field is 10 indicates that the port sent by the sender is the port. Port ID in the remote system MIB. In this way, the third port of the first device can identify the remote system MIB of the received MIB from the peer device, that is, the port of the second device, according to the identification information. The TLV with a value of 9 in the TLV type field may carry the identifier of the first device, and the TLV with the value of 10 in the TLV type field may carry the identifier of the first port.

103. The first device determines that the local system MIB of the third port is different from the local system MIB of the first port that is sent by the second device.

If the third port of the first device receives the local system MIB of the first port and the identifier information sent by the second device, according to the identifier information, the local system MIB of the first port is obtained from the remote system of the port of the second device. The MIB, the first device compares the local system MIB of the third port with the local system MIB of the first port sent by the second device based on the indication of the identification information, and determines the local system MIB of the third port and the first according to the comparison result. Port Whether the local system MIB is the same.

For example, the local system MIB of the first port herein may include the identifier of the first device and the identifier of the first port, and the local system MIB of the third port may include the identifier of the first device and the identifier of the third port. That is to say, in the comparison, the identification of the device and the identification of the port can be compared to confirm whether they are the same.

104. The first device determines that the physical connection between the first port and the second device is incorrect or the physical connection between the third port and the second device is incorrect according to the local system MIB of the third port is different from the local MIB system of the first port.

When the first port of the first device sends the local system MIB of the first port to the second port of the second device, the RX connection of the TX of the first port of the first device and the second port of the second device is described, according to If the physical connection of the device is correct, the RX of the first port of the first device needs to connect to the TX of the second port of the second device, that is, the second port of the second device should be received from the first device. The local system MIB of the first port is transmitted back to the first port of the first device, and if the TX physical connection of the second port of the second device is incorrect to the RX of the third port of the first device, when the third port receives When the second device returns the local system MIB of the first port, the third port compares the local system of the third port with the local system MIB of the received first port, and the third port confirms the first port and The physical connection of the second device is incorrect, or the physical connection of the third port to the second device is incorrect.

The physical connection error refers to a TX or RX connection error between a port of the device and a port of the peer device.

When the first device confirms that the physical connection of the first port or the third port is incorrect, the first device may send an error alarm to the management device, where the error alarm carries the identifier of the first port or the identifier of the third port, and the error alarm is generated. The identifier of the first port is used to identify that the physical connection between the first port and the second device is incorrect. The identifier of the third port in the error alarm is used to identify that the physical connection between the third port and the second device is incorrect.

Since each port of each device receives and sends information independently, each port that has a physical connection error can independently send an error alarm, so that the four connections involved in the physical connection error occur. Each port can send an error alarm independently.

The embodiment of the present invention provides a method for locating a port connection error. The first port of the first device sends the local system MIB of the first port to the second port of the second device, and the third port of the first device receives the second port. The second port of the device sends the local system MIB of the first port, and then When the first device determines that the local system MIB of the third port is different from the local system MIB of the first port sent by the second device, the first device determines that the physical connection between the first port and the second device is incorrect or the third port and the third port The physical connection of the second device is incorrect. In this way, the physical connection of the port to the first port is transmitted back to the first device, which helps to locate the physical connection of the port efficiently.

Embodiment 2

The second device of the peer device of the first device in the first embodiment is the main body. The embodiment of the present invention provides another method for locating the port connection error. Referring to Figure 3, the steps include:

201. The second port of the second device receives the local system MIB of the first port sent by the first port of the first device.

After receiving the local system MIB of the first port, the second port of the second device may save the local system MIB of the first port as the remote system MIB of the second port.

202. The second port of the second device sends the local system MIB of the first port to the third port of the first device.

After the second device saves the received local system MIB of the first port as the remote system MIB of the second port, the second device may be the third device to the first device according to the local system MIB of the first port saved in the remote system MIB. The port sends the local system MIB of the first port, so that after receiving the local system MIB of the first port, the third port of the first device may determine that the local system MIB of the third port is different from the local system MIB of the first port. An error occurs in the physical connection of one port to the second device or the physical connection of the third port to the second device.

The second port of the second device sends the identifier information to the third port of the first device, where the second port of the second device sends the local system MIB of the first port to the third port of the first device. The local system MIB for identifying the first port sent by the second device is the remote system MIB of the port of the second device. The port of the second device may specifically be the second port. This may instruct the third port to compare the local system MIB that received the first port with the local system MIB of the third port to confirm whether it is the same to confirm whether the third port or the first port has a physical connection error.

For the specific implementation of the first device and the second device in this embodiment, refer to the description process in the first embodiment, and details are not described herein again.

An embodiment of the present invention provides a method for locating a port connection error, where a second port of the second device receives a local system MIB of the first port sent by the first port of the first device, and then The second port of the second device sends the local system MIB of the first port to the third port of the first device, so that the first device determines the first port and the first node based on the local system MIB of the third port different from the local system MIB of the first port. The physical connection of the second device is incorrect or the physical connection between the third port and the second device is incorrect. In this way, the physical connection of the port is efficiently located by transmitting the local system MIB of the first port to the first device. error.

Embodiment 3

The embodiment of the present invention provides a method for locating a port connection error. Referring to the splicing error connection shown in FIG. 1, the first device in the first embodiment and the second embodiment is the A device in FIG. The device is described in Figure 1 for the B device. The first port is port 2 of the device A. The third port is port 3 of the device B. Referring to Figure 4, the steps include:

301. Port 2 of the A device sends the local system MIB of the port 2 of the A device to the port 2' of the B device through the first LLDP packet.

The format of the first LLDP packet can be as shown in Table 1 below:

Table 1

The Link Layer Discovery Protocol Data Unit (LLDPDU) currently defines nine TLVs to carry the local system MIB sent by the port, and the value of the TLV type field uses 0-8. When an LLDP packet is sent, the LLDP packet contains at least the following four types: Chassis ID TLV, Port ID TLV, Time to live TLV, and End of LLDPDU TLV.

The Time to live TLV type field has a value of 3, which is used to set the aging time of the remote MIB library. For example, if the physical connection of the optical fiber is correct, port 2 of the A device periodically sends the local system MIB to the port 2' of the B device through the multicast packet, and the port 2 of the B device receives the port of the A device. 2 The local system MIB sent is stored in the remote system MIB of port 2' of the B device. If the port 2' of the B device exceeds the predetermined aging time, it is not received. To the local system MIB of port 2 sent from port 2 of the A device, the port 2' of the B device clears the local system MIB that was last stored in port 2 of the remote system MIB.

End of LLDPDU The TLV type field has a value of 0 and is used to indicate the end of an LLDPDU. There are multiple TLVs in the LLDPDU data block. The value of the type field of the last TLV is 0, which means that the TLV is End of LLDPDU TLV, indicating the end of an LLDPDU.

Chassis ID TLV, the value of the TLV type field is 1, indicating that the information string field of the TLV carries the device identifier. The format of the Chassis ID TLV can be as shown in Table 2 below:

Table 2

Currently, the value of the type field in the TLV is 1 to indicate that the LLDP packet carries the identifier of the device in the local system MIB of the port of the device, and may also be referred to as a frame identifier. The Chassis ID subtype, which is generally 4, indicates that the identifier of the device is identified by a Medium Access Control (MAC) address. Therefore, the Chassis ID in Table 2 can be a MAC address.

Port ID TLV, the value of the TLV type field can be 2, indicating that the TLV carries the port identifier. The format of the TLV can be as shown in Table 3 below:

table 3

The value of the TLV type field is 2, indicating that the TLV information string field of the LLDP packet carries the identifier of the port in the local system MIB of the port. Port ID subtype, typically 5, Indicates that the identity of the port is identified by the name of the port.

302. After receiving the local system MIB of the port 2 of the A device, the port 2' of the B device saves the local system MIB of the port 2 of the A device to the remote system MIB of the port 2'.

In FIG. 1, the TX of port 2 of the A device is connected to the RX of the port 2' of the B device, so the first LLDP packet sent by the A device is received by the port 2' of the B device, and the port 2 of the B device is The local system MIB of port 2 of the received A device is added to the remote system MIB of port 2'.

303. The port 2' of the B device sends the local system MIB of the port 2 to the A device by using the second LLDP packet.

After the port 2' of the B device saves the local system MIB of the port 2 received from the A device, the B device acquires the local system MIB of the port 2 of the A device from the remote system MIB of the port 2' of the B device. And sent to the A device. The local system MIB of the port 2 of the A device acquired by the B device may include the identifier of the device of the port 2 of the A device and the identifier of the port.

While transmitting the local system MIB of the port 2 of the A device, the B device needs to simultaneously send an identification information in order to identify that it is obtained from the remote system MIB of the port 2' of the B device. The specific manner is: the second LLDP packet includes the first TLV and the second TLV, where the first TLV and the second TLV are extended TLVs, the first TLV may be an extended Chassis ID TLV, and the second TLV may be extended Port ID TLV, the identification information may include the value of the type field in the extended Chassis ID TLV and the value of the type field in the extended Port ID TLV, for example, the value of the type field in the extended Chassis ID TLV may be 9, extension The value of the Type field in the Port ID TLV can be 10.

The TLV type=9 in the extended Chassis ID TLV may indicate that the information string field in the extended Chassis ID TLV carries the identifier of the device, and is used to identify that the identifier of the A device sent by the B device is the port of the B device. The identifier of the A device in the remote system MIB, the TLV type=10 in the extended port ID TLV, may indicate that the information in the extended port ID TLV carries the identifier of the port, and is used to identify the B device to send. The identity of port 2 is the identity of port 2 in the remote system MIB of the port of the B device.

In this way, an extended LLDP packet includes at least the following four types: an extended Chassis ID TLV, an extended Port ID TLV, a Time to live TLV, and an End of LLDPDU TLV. The Time to live TLV and the End of LLD PDU TLV are the same as those in step 301.

The format and content of the extended Chassis ID TLV can be as shown in Table 4 below:

Table 4

The format and content of the extended Port ID TLV can be as shown in Table 5 below:

table 5

After receiving the second LLDP packet sent by the port 2' of the B device, the port 3 of the device A identifies the remote system MIB that is the port of the B device carried in the second LLDP packet.

Since the TX of the port 2' of the B device is incorrectly connected to the RX of the A device port 3, the B device port 2' is sent to the port 3 of the A device when the second LLDP packet is returned to the A device. Port 3 of the device A finds that the value of one of the TLVs is 9 according to the extended TLV in the second LLDP packet, and learns that the TLV carries the Chassis ID in the remote system MIB of the port of the B device, and passes another A type of the TLV is 10, and it is learned that the TLV carries the port ID in the remote system MIB of the port of the B device. Then, the port 3 of the device A learns the second LLDP received by the device A according to the extended TLV. The message is used to confirm that the port connection is correct, not the local system MIB of the port of the B device, and does not need to store the received MIB information.

305. The port 3 of the device A extracts the Chassis ID and Port ID in the local system MIB of the port 2 of the A device in the remote system MIB carried by the second LLDP packet, and the port 3 The Chassis ID and the Port ID in the local system MIB are compared. If the two are different, the port 3 determines that the physical connection of the port is incorrect, and sends an alarm to the network management device.

The second LLDP packet returned by the B device carries the remote system MIB of the port from the B device, and the remote system MIB includes the local system MIB of the port 2 of the A device to the port 2 of the port 2'. Port 3 of the device A identifies the Chassis ID and Port ID of the remote system MIB of the port carried by the second LLDP packet, after the remote system MIB of the port of the B device is carried in the second LLDP packet. The Chassis ID and Port ID in the remote system MIB are the Chassis ID and Port ID in the local system MIB of the port 2 of the A device, and the port 3 of the A device passes the local system MIB of the port 2 of the received A device. The Chassis ID and the Port ID are compared with the Chassis ID and the Port ID in the local system MIB of the port 3, and the two are different. Thus, the port 3 of the A device confirms that the physical connection of the port is incorrect, and sends the error to the network management device. Alarm.

The error alarm may carry the identifier of the port 2 or the identifier of the port 3, and the identifier of the port 2 in the error alarm is used to identify that the physical connection between the port 2 and the B device is incorrect, and the identifier of the port 3 in the error alarm is used to identify The physical connection between port 3 and device B has an error.

Since each port of each device receives and sends information independently, each port with a wrong physical connection can independently report an alarm. The four ports involved in the connection error can be independently used. Report the police.

After receiving the local system MIB information of the peer end, the local end adds the local system MIB information of the peer end to the remote system MIB of the local port, and then sends the remote system MIB to the peer end through the extended TLV. The process of confirming whether the port connection is wrong by the peer end can accurately and accurately determine the location of the physical connection error of the port.

The embodiment of the present invention provides a method for locating a port connection error. Port 2 of the A device sends the local system MIB of the port 2 of the A device to the port 2 of the B device through the first LLDP message, and the port 2 of the B device. 'Save the local system MIB of port 2 of the A device to the remote system MIB of port 2', and port 2' of the B device sends the local system MIB of port 2 to the A device through the second LLDP message, port 3 of the A device After receiving the second LLDP packet sent by the port 2' of the B device, the device identifies the remote system MIB that is the port of the B device carried by the second LLDP packet according to the identifier information, and the device port 3 of the device A The Chassis ID and Port ID in the local system MIB of the port 2 of the A device in the remote system MIB carried in the second LLDP packet are compared with the Chassis ID and the Port ID in the local system MIB of the port 3, if If the two are different, port 3 determines that the physical connection of the port is incorrect, and sends an alarm to the network management device, which helps to locate the physical connection of the port efficiently.

Embodiment 4

An embodiment of the present invention provides a first device 04. The first device 04 can be used to perform the method provided in Embodiment 1. As shown in Figure 5, it includes:

The sending unit 041 is configured to send, by using the first port, the local system management information base MIB of the first port to the second port of the second device;

The receiving unit 042 is configured to receive, by using the third port, a local system MIB of the first port that is sent by the second port of the second device;

a determining unit 043, configured to determine that the local system MIB of the third port is different from the local system MIB of the first port that is sent by the second device received by the receiving unit 042;

The determining unit 043 is further configured to determine that the physical connection between the first port and the second device is incorrect or the physical connection between the third port and the second device is incorrect, based on the local system MIB of the third port being different from the local MIB system of the first port. .

Optionally, the receiving unit 042 is further configured to receive the identifier information sent by the second port of the second device by using the third port, where the identifier information is used to identify that the local system MIB of the first port sent by the second device is the second device. Remote system MIB of the port;

The determining unit 043 is specifically configured to:

Comparing the local system MIB of the third port with the local system MIB of the first port sent by the second device based on the indication of the identification information;

In the above technical solution, the port of the second device may specifically be the second port.

Optionally, the receiving unit 042 is configured to: receive, by using the third port, a link layer discovery protocol LLDP packet sent by the second port of the second device, where the LLDP packet carries the local system MIB of the first port and the identifier information.

Optionally, the LLDP packet includes a first TLV and a second TLV, where the identifier information includes a value of a type field in the first TLV and a value of a type field in the second TLV, where the value of the type field in the first TLV indicates The information string field in a TLV carries the identifier of the device. The value of the type field in the second TLV indicates that the information string field in the second TLV carries the identifier of the port, and the remote system MIB of the port of the second device includes The identifier of the first device and the identifier of the first port, the value of the type field in the first TLV is used to identify that the identifier of the first device sent by the second device is the first device in the remote system MIB of the port of the second device The identifier of the type field in the second TLV is used to identify that the identifier of the first port sent by the second device is the identifier of the first port in the remote system MIB of the port of the second device.

In the foregoing technical solution, the identifier of the device carried in the information string field in the first TLV may specifically be the identifier of the first device. The identifier of the port carried in the information string field in the second TLV may specifically be the identifier of the first port.

Optionally, the sending unit 041 is further configured to:

Sending an error alarm to the management device. The error alarm carries the identifier of the first port or the identifier of the third port. The identifier of the first port in the error alarm is used to identify that the physical connection between the first port and the second device is incorrect. The identifier of the third port is used to identify that the physical connection of the third port to the second device is incorrect.

For the specific implementation of the device involved in each unit in the embodiment of the present invention, reference may be made to the embodiment shown in FIG.

An embodiment of the present invention provides a first device, including: a sending unit, a receiving unit, and a determining unit. The sending unit is configured to send, by using the first port, the local system management information base MIB of the first port to the second port of the second device, and the receiving unit, configured to receive, by using the third port, the second port sent by the second port of the second device a local system MIB of a port; a determining unit, configured to determine that the local system MIB of the third port is different from the local system MIB of the first port sent by the second device; the determining unit is further configured to use the local system MIB of the third port The local MIB system of the first port differently determines that an error occurs in the physical connection between the first port and the second device or an error occurs in the physical connection between the third port and the second device. In this way, by sending the local system MIB information of the peer end back to the peer end for confirmation, the physical connection of the efficiently located port is mistaken.

Embodiment 5

An embodiment of the present invention provides a second device 05. The second device 05 can be used to perform the method provided in the second embodiment. As shown in Figure 6, it includes:

The receiving unit 051 is configured to receive, by using the second port, a local system management information base MIB of the first port sent by the first port of the first device;

The sending unit 052 is configured to send, by using the second port, the local system MIB of the first port received by the receiving unit to the third port of the first device.

The first device may determine that an error occurs in the physical connection of the first port and the second device or an error occurs in the physical connection between the third port and the second device, based on the local system MIB of the third port being different from the local system MIB of the first port.

After receiving the local system management information base MIB of the first port, the second device 05 saves the local system management information base MIB of the first port as the remote system MIB of the second port.

Optionally, the sending unit 052 is further configured to send the identifier information to the third port of the first device by using the second port, where the identifier information is used to identify that the local system MIB of the first port sent by the second device is a port of the second device. Remote system MIB.

In the above technical solution, the port of the second device may specifically be the second port. The identifier of the device carried in the information string field in the first TLV may specifically be the identifier of the first device. The identifier of the port carried in the information string field in the second TLV may specifically be the identifier of the first port.

Optionally, the sending unit 052 is configured to: send, by using the second port, a link layer discovery protocol LLDP packet to the third port of the first device, where the LLDP packet carries the local system MIB of the first port and the identifier information.

Optionally, the LLDP packet includes a first TLV and a second TLV, where the identifier information includes a value of a type field in the first TLV and a value of a type field in the second TLV, where the value of the type field in the first TLV indicates The information string field in a TLV carries the identifier of the device. The value of the type field in the second TLV indicates that the information string field in the second TLV carries the identifier of the port, and the remote system MIB of the port of the second device includes The identifier of the first device and the identifier of the first port, the value of the type field in the first TLV is used to identify that the identifier of the first device sent by the second device is the first device in the remote system MIB of the port of the second device The identifier of the type field in the second TLV is used to identify that the identifier of the first port sent by the second device is in the remote system MIB of the port of the second device. The identity of the first port.

An embodiment of the present invention provides a second device, including: a receiving unit and a sending unit. The receiving unit is configured to receive, by using the second port, a local system management information base MIB of the first port sent by the first port of the first device, and a sending unit, configured to send, by using the second port, the third port of the first device The local system MIB of the first port, the first device based on the local system MIB of the third port is different from the local system MIB of the first port, determining that the physical connection between the first port and the second device is incorrect or that the third port and the second device are An error occurs in the physical connection. This helps to efficiently locate the physical connection of the port by sending the MIB information of the peer back to the peer for confirmation.

Embodiment 6

An embodiment of the present invention provides a first device 06. The first device 06 can be used to perform the method provided in the first embodiment. Referring to Figure 7, there is included a bus 061, a memory 062 coupled to bus 061, a transmitter 063, a receiver 064, and a processor 065, wherein the memory 062 is for storing instructions and data; the transmitter 063 is for passing the first port Transmitting, by the second port of the second device, the local system management information base MIB of the first port; the receiver 064 is configured to receive, by using the third port, the local system MIB of the first port sent by the second port of the second device; the processor 065 The local system MIB for determining the third port is different from the local system MIB of the first port sent by the second device; the processor 065 is further configured to determine that the local system MIB based on the third port is different from the local MIB system of the first port. An error occurs in the physical connection of one port to the second device or the physical connection of the third port to the second device.

In the embodiment of the present invention, optionally, the receiver 064 is further configured to receive the identifier information sent by the second port of the second device by using the third port, where the identifier information is used to identify the first port that is sent by the second device. The local system MIB is a remote system MIB of the port of the second device;

The processor 065 can be specifically configured to:

Comparing the local system MIB of the third port with the second device based on the indication of the identification information The local system MIB of the first port sent;

In the embodiment of the present invention, the receiver 064 may be configured to: receive, by using the third port, a link layer discovery protocol LLDP packet sent by the second port of the second device, where the LLDP packet carries the first port. Local system MIB and identification information.

In the embodiment of the present invention, optionally, the LLDP packet includes a first TLV and a second TLV, and the identifier information includes a value of a type field in the first TLV and a value of a type field in the second TLV, where the first TLV is in the first TLV. The value of the type field indicates that the information string field in the first TLV carries the identifier of the device, and the value of the type field in the second TLV indicates that the information string field in the second TLV carries the identifier of the port, and the second device The remote system MIB of the port includes the identifier of the first device and the identifier of the first port. The value of the type field in the first TLV is used to identify that the identifier of the first device sent by the second device is the remote end of the port of the second device. The identifier of the first device in the system MIB, the value of the type field in the second TLV is used to identify that the identifier of the first port sent by the second device is the identifier of the first port in the remote system MIB of the port of the second device. .

In the embodiment of the present invention, optionally, the transmitter 064 is further configured to:

For a specific implementation manner of the device involved in the embodiment of the present invention, refer to the embodiment shown in FIG. 1 and FIG.

An embodiment of the present invention provides a first device, including: a bus, a memory connected to the bus, a transmitter, a receiver, and a processor, wherein the memory is used to store instructions and data; and the transmitter is configured to pass the first port to the first The second port of the second device sends the local system management information base MIB of the first port; the receiver is configured to receive the local system MIB of the first port sent by the second port of the second device through the third port; the processor is configured to determine the third port The local system MIB is different from the local system MIB of the first port sent by the second device; the processor is further configured to determine the first port and the second device differently according to the third port-based local system MIB and the first port local MIB system Physical connection error or An error occurred in the physical connection between the three ports and the second device. In this way, by sending the MIB information of the peer end back to the peer end for confirmation, it is helpful to make an error in the physical connection of the efficiently located port.

Example 7

The embodiment of the invention provides a second device 07. The second device 07 can be used to perform the method provided by the second embodiment. Referring to FIG. 8, a bus 071, a memory 072 connected to the bus 071, a receiver 073, and a transmitter 074, wherein the memory 072 is used to store instructions and data, and the receiver 073 is configured to receive the first through the second port. The local port management information base MIB of the first port sent by the first port of the device; the transmitter 074 is configured to send the local system MIB of the first port to the third port of the first device through the second port.

Then, the first device may determine that an error occurs in the physical connection of the first port and the second device or an error occurs in the physical connection between the third port and the second device, based on the local system MIB of the third port being different from the local system MIB of the first port.

After receiving the local system management information base MIB of the first port, the second device may save the local system management information base MIB of the first port as the remote system MIB of the second port.

In the embodiment of the present invention, the transmitter 074 is further configured to: send, by using the second port, the identifier information to the third port of the first device, where the identifier information is used to identify the local system of the first port sent by the second device. The MIB is the remote system MIB of the port of the second device.

In the embodiment of the present invention, the transmitter 074 is configured to: send, by using the second port, a link layer discovery protocol (LLDP) packet to the third port of the first device, where the LLDP packet carries the local system of the first port. MIB and identification information.

In this embodiment, optionally, the LLDP packet includes a first TLV and a second TLV, where the identifier information includes a value of a type field in the first TLV and a value of a type field in the second TLV, in the first TLV. The value of the type field indicates that the information string field in the first TLV carries the identifier of the device, and the value of the type field in the second TLV indicates that the information string field in the second TLV carries the identifier of the port, and the port of the second device The remote system MIB includes an identifier of the first device and an identifier of the first port, where the value of the type field in the first TLV is used to identify the remote system of the port of the second device that is sent by the second device The identifier of the first device in the MIB, and the value of the type field in the second TLV. The identifier of the first port sent by the second device is the identifier of the first port in the remote system MIB of the port of the second device.

An embodiment of the present invention provides a second device, including: a bus, a memory connected to the bus, a receiver, and a transmitter, wherein the memory is used to store instructions and data; and the receiver is configured to receive the first device through the second port. The local port management information base MIB of the first port sent by the first port; the transmitter is configured to send the local system MIB of the first port to the third port of the first device through the second port, so that the first device can be based on the third port The local system MIB is different from the local system MIB of the first port to determine that the physical connection between the first port and the second device is incorrect, or the physical connection between the third port and the second device is incorrect, so that the MIB information of the opposite end is sent back to the The method of confirming the peer end helps to make an error in the physical connection of the efficiently located port.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

In addition, in the devices and systems in various embodiments of the present invention, each functional unit may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit. The above units may be implemented in the form of hardware or in the form of hardware plus software functional units.

All or part of the steps of implementing the foregoing method embodiments may be performed by hardware related to the program instructions. The foregoing program may be stored in a computer readable storage medium, and when executed, the program includes the steps of the foregoing method embodiments; The foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. medium.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

A method for locating a port connection error, comprising:

The first port of the first device sends the local system management information base MIB of the first port to the second port of the second device;

The third port of the first device receives the local system MIB of the first port sent by the second port of the second device;

Determining, by the first device, that the local system MIB of the third port is different from the local system MIB of the first port that is sent by the second device;

Determining, by the first device, that the physical connection between the first port and the second device is incorrect or the third port is different, based on the local system MIB of the third port being different from the local MIB system of the first port The physical connection of the second device is incorrect.
The method according to claim 1, wherein the receiving, by the third port of the first device, the local system MIB of the first port sent by the second port of the second device further comprises: the first The third port of the device receives the identifier information sent by the second port of the second device, where the identifier information is used to identify that the local system MIB of the first port sent by the second device is the second device Remote system MIB of the port;

The determining, by the first device, that the local system MIB of the third port is different from the local system MIB of the first port that is sent by the second device includes:

The first device compares the local system MIB of the third port with the local system MIB of the first port sent by the second device, according to the indication of the identifier information;

The first device determines that the local system MIB of the third port is different from the local system MIB of the first port based on the result of the comparison.
The method according to claim 2, wherein the receiving, by the third port of the first device, the local system MIB of the first port sent by the second port of the second device comprises:

The third port of the first device receives the link layer discovery protocol LLDP packet sent by the second port of the second device, where the LLDP packet carries the local system MIB of the first port and the identifier information.
The method according to claim 3, wherein the LLDP message includes a first TLV and a second TLV, and the identification information includes a value of a type field in the first TLV and a type field in the second TLV. Value, the type word in the first TLV The value of the segment indicates that the information string field in the first TLV carries the identifier of the device, and the value of the type field in the second TLV indicates that the information string field in the second TLV carries the identifier of the port. The remote system MIB of the port of the second device includes an identifier of the first device and an identifier of the first port, and a value of a type field in the first TLV is used to identify that the second device sends The identifier of the first device is an identifier of the first device in a remote system MIB of a port of the second device, and a value of a type field in the second TLV is used to identify that the second device sends The identifier of the first port is an identifier of the first port in a remote system MIB of a port of the second device.
The method according to any one of claims 1 to 4, wherein the method further comprises:

The first device sends an error alarm to the management device, where the error alarm carries the identifier of the first port or the identifier of the third port, and the identifier of the first port in the error alarm is used to identify the identifier An error occurs in the physical connection between the first port and the second device, and the identifier of the third port in the error alarm is used to identify that the physical connection between the third port and the second device is incorrect.
A method for locating a port connection error, comprising:

The second port of the second device receives the local system management information base MIB of the first port sent by the first port of the first device;

The second port of the second device sends the local system MIB of the first port to the third port of the first device.
The method according to claim 6, wherein the sending, by the second port of the second device, the local system MIB of the first port to the third port of the first device further comprises:

The second port of the second device sends the identifier information to the third port of the first device, where the identifier information is used to identify that the local system MIB of the first port sent by the second device is the first The remote system MIB of the port of the second device.
The method according to claim 7, wherein the sending, by the second port of the second device, the local system MIB of the first port to the third port of the first device comprises:

The second port of the second device sends a link layer discovery protocol LLDP packet to the third port of the first device, where the LLDP packet carries the locality of the first port. System MIB and the identification information.
The method according to claim 8, wherein the LLDP message includes a first TLV and a second TLV, and the identification information includes a value of a type field in the first TLV and a type field in the second TLV. a value, the value of the type field in the first TLV indicates that the information string field in the first TLV carries an identifier of the device, and the value of the type field in the second TLV indicates in the second TLV. The information string field carries the identifier of the port, and the remote system MIB of the port of the second device includes the identifier of the first device and the identifier of the first port, and the value of the type field in the first TLV. The identifier of the first device that is used to identify the second device is the identifier of the first device in the remote system MIB of the port of the second device, and the type field in the second TLV The value is used to identify that the identifier of the first port sent by the second device is an identifier of the first port in a remote system MIB of a port of the second device.
A first device, where the first device includes a first port and a third port, and includes:

a sending unit, configured to send, by using the first port, a local system management information base MIB of the first port to a second port of the second device;

a receiving unit, configured to receive, by using the third port, a local system MIB of the first port that is sent by the second port of the second device;

a determining unit, configured to determine that the local system MIB of the third port is different from the local system MIB of the first port that is sent by the second device by the receiving unit;

The determining unit is further configured to determine, according to the local system MIB of the third port, that the physical connection between the first port and the second device is incorrect or the first one is different from the local MIB system of the first port An error occurs in the physical connection of the three ports to the second device.
The first device according to claim 10, wherein the receiving unit is further configured to receive, by using the third port, identifier information sent by a second port of the second device, where the identifier information is used by Determining, by the second device, that the local system MIB of the first port is a remote system MIB of a port of the second device;

The determining unit is specifically configured to:

Comparing the local system MIB of the third port with the indication of the identification information The local system MIB of the first port sent by the second device;

Based on the result of the comparison, it is determined that the local system MIB of the third port is different from the local system MIB of the first port.
The first device according to claim 11, wherein the receiving unit is configured to: receive, by using the third port, a link layer discovery protocol LLDP packet sent by a second port of the second device, where The local system MIB of the first port and the identifier information are carried in the LLDP packet.
The first device according to claim 12, wherein the LLDP message includes a first TLV and a second TLV, and the identification information includes a value of a type field in the first TLV and a type in the second TLV. a value of the field, the value of the type field in the first TLV indicates that the information string field in the first TLV carries an identifier of the device, and the value of the type field in the second TLV indicates the second TLV The information string field in the port carries the identifier of the port, and the remote system MIB of the port of the second device includes the identifier of the first device and the identifier of the first port, and the type field in the first TLV The value of the second device is used to identify that the identifier of the first device sent by the second device is the identifier of the first device in the remote system MIB of the port of the second device, and the type in the second TLV The value of the field is used to identify that the identifier of the first port sent by the second device is the identifier of the first port in the remote system MIB of the port of the second device.
The first device according to any one of claims 10 to 13, wherein the sending unit is further configured to:

Sending an error alarm to the management device, where the error alarm carries the identifier of the first port or the identifier of the third port, where the identifier of the first port in the error alarm is used to identify the first port and The physical connection of the second device is incorrect, and the identifier of the third port in the error alarm is used to identify that the physical connection between the third port and the second device is incorrect.
A second device, where the second device includes a second port, including:

a receiving unit, configured to receive, by using the second port, a local system management information base MIB of the first port that is sent by the first port of the first device;

And a sending unit, configured to send, by using the second port, a local system MIB of the first port that is received by the receiving unit to a third port of the first device.
The second device according to claim 15, wherein the sending unit is further configured to: send, by using the second port, identifier information to a third port of the first device, where the identifier information is used to identify The local system MIB of the first port sent by the second device is a remote system MIB of a port of the second device.
The second device according to claim 16, wherein the sending unit is configured to: send, by using the second port, a link layer discovery protocol LLDP packet to a third port of the first device, where The LLDP packet carries the local system MIB of the first port and the identifier information.
The second device according to claim 17, wherein the LLDP message includes a first TLV and a second TLV, and the identification information includes a value of a type field in the first TLV and a type in the second TLV. a value of the field, the value of the type field in the first TLV indicates that the information string field in the first TLV carries an identifier of the device, and the value of the type field in the second TLV indicates the second TLV The information string field in the port carries the identifier of the port, and the remote system MIB of the port of the second device includes the identifier of the first device and the identifier of the first port, and the type field in the first TLV The value of the second device is used to identify that the identifier of the first device sent by the second device is the identifier of the first device in the remote system MIB of the port of the second device, and the type in the second TLV The value of the field is used to identify that the identifier of the first port sent by the second device is the identifier of the first port in the remote system MIB of the port of the second device.