CN108055162B

CN108055162B - Fault determination method and node

Info

Publication number: CN108055162B
Application number: CN201711490149.2A
Authority: CN
Inventors: 岳丽娟; 谭近
Original assignee: Raisecom Technology Co Ltd
Current assignee: Raisecom Technology Co Ltd
Priority date: 2017-12-29
Filing date: 2017-12-29
Publication date: 2020-12-25
Anticipated expiration: 2037-12-29
Also published as: CN108055162A

Abstract

The embodiment of the invention discloses a fault determination method and a node, which comprise the following steps: the initial maintenance end node MEP acquires VLAN state information in a VLAN list maintained by the initial maintenance end node MEP, and the acquired information is used as first VLAN state information; sending a VLAN state acquisition request to a maintenance intermediate node MIP adjacent to the maintenance intermediate node MIP; receiving second VLAN state information sent by MIPs adjacent to the second VLAN state information; and determining the failed node and the VLAN according to the first VLAN state information and the second VLAN state information. It can be seen from the embodiments of the present invention that the first VLAN state information can reflect the VLAN state of the originating MEP, and the second VLAN state information can reflect the VLAN states of the MIP and the destination MEP, so that the originating MEP can determine the failed node and VLAN according to the first VLAN state information and the second VLAN state information, thereby implementing accurate location of the failed specific node and specific VLAN.

Description

Fault determination method and node

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a fault determination method and a node.

Background

The service transmission of the ethernet is a secure transmission of two-layer data implemented based on a Virtual Local Area Network (VLAN), and Operation, management and Maintenance (OAM) is a technology for monitoring ethernet Network failures with a wide application range. MEPs and MIPs are logical concepts built into a service instance model, and in practice, they may correspond to one physical device, and one physical device may also correspond to a plurality of MEPs or MIPs.

The 802.1ag protocol is one of OAM technologies, and establishes a pair of Connectivity Fault Management (CFM) on an originating MEP and a destination MEP, and uses a device passing through from the originating MEP to the destination MEP as an MIP, thereby detecting whether a link from the originating MEP to the destination MEP fails.

However, although the 802.1ag protocol can detect whether a link fails, it cannot further determine the specific node and the specific VLAN that failed.

Disclosure of Invention

In order to solve the above technical problems, the present invention provides a fault determining method and a node, which can accurately locate a specific node and a specific VLAN of a fault.

In order to achieve the object of the present invention, the present invention provides a fault determining method, including:

the initial MEP acquires VLAN state information in a VLAN list maintained by the initial MEP, and the acquired information is used as first VLAN state information;

sending a VLAN state acquisition request to the MIP adjacent to the MIP;

receiving second VLAN state information sent by the MIP adjacent to the second VLAN state information; wherein the second VLAN state information includes: all MIPs and VLAN state information in a VLAN list maintained by a destination MEP;

and determining the failed node and the VLAN according to the first VLAN state information and the second VLAN state information.

The determining the failed node and the VLAN according to the first VLAN state information and the second VLAN state information comprises the following steps:

if VLAN fault information exists in the first VLAN state information, determining a fault node as the first VLAN and determining a fault VLAN as the first VLAN with the VLAN fault information;

if VLAN fault information exists in a VLAN list maintained by the MIP in the second VLAN state information, determining a node with fault as the MIP, and determining a VLAN with fault as the VLAN with VLAN fault information of the MIP;

and if VLAN fault information exists in a VLAN list maintained by the target MEP in the second VLAN state information, determining the node with the fault as the target MEP, and determining the VLAN with the fault as the VLAN with the VLAN fault information of the target MEP.

Before sending the VLAN state obtaining request to the adjacent MIP, the method further includes:

acquiring the number of VLAN sections in a VLAN list maintained by the VLAN, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section, and taking the acquired information as first VLAN deployment information;

the sending of the VLAN state acquisition request to the MIP adjacent to the VLAN state acquisition request includes:

and sending the VLAN state acquisition request and the first VLAN deployment information to the MIP adjacent to the MIP.

The VLAN status acquisition request is included in a Link Trace Message (LTM) Message; the sending of the VLAN state acquisition request and the first VLAN deployment information to the MIP adjacent to the sending of the VLAN state acquisition request and the first VLAN deployment information includes:

sending an LTM message carrying a first TLV to the MIP adjacent to the MIP; wherein the first TLV includes: presetting a VLAN state identifier and the first VLAN deployment information;

the starting MEP obtains information of VLAN state in a VLAN list maintained by the starting MEP, and after taking the obtained information as first VLAN state information, the method further includes:

acquiring a VLAN state identifier corresponding to the first VLAN state information according to a pre-established state and state identifier corresponding relation, and taking the acquired VLAN state identifier as a first VLAN state identifier;

the receiving the second VLAN state information sent by the MIP adjacent to the receiving device includes:

receiving a Link Trace Response (LTR) message carrying a second TLV and sent by the MIP adjacent to the MIP; wherein the second TLV includes: VLAN state identifiers corresponding to the second VLAN state information, and the number of VLAN sections in a VLAN list maintained by all MIPs and target MEPs, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section;

acquiring the VLAN state identifier corresponding to the second VLAN state information in the second TLV, and taking the obtained VLAN state identifier as a second VLAN state identifier;

and determining the failed node and VLAN according to the preset VLAN state identifier, the first VLAN state identifier and the second VLAN state identifier.

The determining of the failed node and the VLAN according to the preset VLAN state identifier, the first VLAN state identifier and the second VLAN state identifier comprises the following steps:

judging whether the first VLAN state identifier, the second VLAN state identifiers of all MIPs and the second VLAN state identifier of the target MEP are the same as the preset VLAN state identifier or not;

if the first VLAN state identifier is different from the preset VLAN state identifier, determining the failed node as the node, and determining the failed VLAN as the VLAN of which the VLAN state identifier is different from the preset VLAN state identifier;

if the second VLAN state identifier of the MIP is different from the preset VLAN state identifier, determining the failed node as the MIP, and determining the failed VLAN as the VLAN of which the second VLAN state identifier of the MIP is different from the preset VLAN state identifier;

and if the second VLAN state identifier of the destination MEP is different from the preset VLAN state identifier, determining the failed node as the destination MEP, and determining the failed VLAN as the VLAN of which the second VLAN state identifier of the destination MEP is different from the preset VLAN state identifier.

The invention also provides a fault determination method, which comprises the following steps:

the MIP adjacent to the starting MEP receives the VLAN state acquisition request sent by the starting MEP;

obtaining VLAN state information in a VLAN list maintained by the VLAN information acquisition device, and taking the obtained information as third VLAN state information;

sending the VLAN state acquisition request to nodes adjacent to the VLAN state acquisition request; wherein the node adjacent to itself includes: when the MIP adjacent to the self exists, the node adjacent to the self is the MIP, and when the MIP adjacent to the self does not exist, the node adjacent to the self is the target MEP;

receiving fourth VLAN state information sent by the nodes adjacent to the fourth VLAN state information; wherein the fourth VLAN status information comprises: information of VLAN state in VLAN list maintained by all nodes except initial MEP and itself;

and sending the third VLAN state information and the fourth VLAN state information to the starting MEP as second VLAN state information.

The receiving of the VLAN state acquisition request sent by the originating MEP includes:

receiving a VLAN state acquisition request and first VLAN deployment information sent by the starting MEP; wherein the first VLAN deployment information comprises: the number of VLAN sections in a VLAN list maintained by the starting MEP, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section;

the acquiring information of the VLAN state in the VLAN list maintained by the VLAN information processing apparatus, and using the acquired information as third VLAN state information, includes:

acquiring the number of VLAN sections in a VLAN list maintained by the VLAN, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section, and taking the acquired information as second VLAN deployment information;

judging whether the second VLAN deployment information is the same as the first VLAN deployment information or not;

if the second VLAN deployment information is the same as the first VLAN deployment information, obtaining VLAN state information in a VLAN list maintained by the VLAN deployment information, and taking the obtained information as third VLAN state information;

the sending of the received VLAN status acquisition request to the node adjacent to itself includes:

and sending the VLAN state acquisition request and the first VLAN deployment information to the nodes adjacent to the VLAN state acquisition request and the first VLAN deployment information.

The VLAN state acquisition request is contained in an LTM message; the receiving of the VLAN state acquisition request and the first VLAN deployment information sent by the starting MEP includes:

receiving an LTM message which is sent by the initial MEP and carries a first TLV; wherein the first TLV includes: presetting a VLAN state identifier and the first VLAN deployment information;

the obtaining of the information of the VLAN state in the VLAN list maintained by the VLAN terminal, and after taking the obtained information as third VLAN state information, further includes:

changing a preset VLAN state identifier in the first TLV according to the third VLAN state information to generate a third TLV;

generating an LTR message carrying the third TLV;

the sending of the VLAN state acquisition request and the first VLAN deployment information to the nodes adjacent to the sending of the VLAN state acquisition request and the first VLAN deployment information includes:

sending the LTM message carrying the first TLV to the node adjacent to the LTM message;

the receiving the information of the fourth VLAN state sent by the node adjacent to the receiving node includes:

receiving the LTR message carrying the fourth TLV and sent by the node adjacent to the LTR message receiving node; wherein the fourth TLV includes: the number of VLAN sections in a VLAN list maintained by all nodes except the initial MEP and the initial MEP, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section;

the sending the third VLAN status information and the fourth VLAN status information as second VLAN status information to the initial MEP includes:

and sending the LTR message carrying the third TLV and the LTR message carrying the fourth TLV to the starting MEP as LTR messages carrying the second TLV.

the target MEP receives a VLAN state acquisition request sent by the MIP adjacent to the target MEP;

obtaining VLAN state information in a VLAN list maintained by the VLAN information acquisition device, and taking the obtained information as fifth VLAN state information;

and sending the fifth VLAN state information to the MIP adjacent to the fifth VLAN state information.

The receiving, by the destination MEP, a VLAN state obtaining request sent by an MIP adjacent to the destination MEP includes:

the target MEP receives the VLAN state acquisition request and first VLAN deployment information sent by the MIP adjacent to the target MEP; wherein the first VLAN deployment information comprises: the number of VLAN sections in a VLAN list maintained by the starting MEP, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section;

the acquiring information of the VLAN state in the VLAN list maintained by the VLAN information processing apparatus, and using the acquired information as fifth VLAN state information, includes:

acquiring the number of VLAN sections in a VLAN list maintained by the VLAN, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section, and taking the acquired information as fourth VLAN deployment information;

judging whether the fourth VLAN deployment information is the same as the first VLAN deployment information or not;

and if the fourth VLAN deployment information is the same as the first VLAN deployment information, obtaining VLAN state information in a VLAN list maintained by the fourth VLAN deployment information, and taking the obtained information as fifth VLAN state information.

The VLAN state acquisition request is contained in an LTM message; the receiving of the VLAN state acquisition request and the first VLAN deployment information sent by the MIP adjacent to the receiving includes:

receiving the LTM message carrying the first TLV and sent by the MIP adjacent to the LTM message; wherein the first TLV includes: presetting a VLAN state identifier and the first VLAN deployment information;

the obtaining of the information of the VLAN state in the VLAN list maintained by the VLAN terminal, after taking the obtained information as fifth VLAN state information, further includes:

changing a preset VLAN state identifier in the first TLV according to the fifth VLAN state information to generate a fifth TLV;

generating an LTR message carrying the fifth TLV;

the sending the fifth VLAN status information to the MIP adjacent to the fifth VLAN status information includes:

and sending the LTR message carrying the fifth TLV to the MIP adjacent to the LTR message.

The present invention also provides an initiating MEP, comprising:

a first obtaining module, configured to obtain information about a VLAN state in a VLAN list maintained by an originating MEP, and use the obtained information as first VLAN state information;

a first sending module, configured to send a VLAN status acquisition request to an MIP adjacent to the starting MEP;

a first receiving module, configured to receive the second VLAN status information sent by the MIP adjacent to the starting MEP; wherein the second VLAN status information includes: all MIPs and VLAN state information in a VLAN list maintained by a destination MEP;

and the first processing module is used for determining the failed node and the VLAN according to the first VLAN state information and the second VLAN state information.

The present invention also provides a MIP adjacent to an initial MEP, comprising:

a second receiving module, configured to receive a VLAN status acquisition request sent by an initial MEP;

a second obtaining module, configured to obtain information about a VLAN state in a VLAN list maintained by an MIP adjacent to the initial MEP, and use the obtained information as third VLAN state information;

a second sending module, configured to send the VLAN status acquisition request to a node that is not adjacent to the initial MEP; wherein the node not adjacent to the starting MEP comprises: when there is a MIP not adjacent to the starting MEP, the node not adjacent to the starting MEP is the MIP, and when there is no MIP not adjacent to the starting MEP, the node not adjacent to the starting MEP is the destination MEP;

the second receiving module is further configured to receive fourth VLAN status information sent by the node that is not adjacent to the starting MEP; wherein the fourth VLAN status information comprises: information of VLAN status in VLAN lists maintained by all nodes except the originating MEP and MIPs adjacent to the originating MEP;

the second sending module is further configured to send the third VLAN status information and the fourth VLAN status information to the initial MEP as second VLAN status information.

The present invention also provides a target MEP, comprising:

a third receiving module, configured to receive a VLAN status acquisition request sent by a MIP adjacent to the third receiving module;

a third obtaining module, configured to obtain information about a VLAN status in a VLAN list maintained by the third obtaining module, and use the obtained information as fifth VLAN status information;

and a third sending module, configured to send the fifth VLAN status information to the MIP adjacent to the third sending module.

Compared with the prior art, the method at least comprises the steps that the initial MEP obtains the information of the VLAN state in the VLAN list maintained by the initial MEP, and the obtained information is used as the first VLAN state information; sending a VLAN state acquisition request to the MIP adjacent to the MIP; receiving second VLAN state information sent by MIPs adjacent to the second VLAN state information; wherein the second VLAN status information includes: all MIPs and VLAN state information in a VLAN list maintained by a destination MEP; and determining the failed node and the VLAN according to the first VLAN state information and the second VLAN state information. According to the technical scheme provided by the invention, the first VLAN state information can reflect the VLAN state of the initial MEP, and the second VLAN state information can reflect the VLAN states of the MIP and the target MEP, so that the initial MEP can determine the failed node and VLAN according to the first state information and the second VLAN state information, and the accurate positioning of the failed specific node and specific VLAN is realized.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the example serve to explain the principles of the invention and not to limit the invention.

Fig. 1 is a schematic flow chart of a fault determination method according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a network topology according to an embodiment of the present invention;

fig. 3 is a schematic flow chart of another fault determination method according to an embodiment of the present invention;

fig. 4 is a schematic flowchart of another fault determination method according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a TLV structure provided in an embodiment of the present invention;

fig. 6 is a schematic structural diagram of an LTM packet carrying a TLV structure according to an embodiment of the present invention;

fig. 7 is a schematic structural diagram of an LTR packet carrying a TLV structure according to an embodiment of the present invention;

fig. 8 is a schematic flowchart of another fault determination method according to an embodiment of the present invention;

fig. 9 is a schematic flowchart of another fault determination method according to an embodiment of the present invention;

fig. 10 is a schematic flowchart of another fault determination method according to an embodiment of the present invention;

fig. 11 is a schematic flowchart of another fault determination method according to an embodiment of the present invention;

fig. 12 is a schematic flowchart of another fault determination method according to an embodiment of the present invention;

fig. 13 is a schematic flowchart of another fault determination method according to an embodiment of the present invention;

FIG. 14 is a schematic diagram of another network topology provided by embodiments of the present invention;

fig. 15 is a schematic flowchart of another fault determination method according to an embodiment of the present invention;

FIG. 16 is a schematic diagram of another network topology provided by an embodiment of the present invention;

fig. 17 is a schematic structural diagram of a starting MEP according to an embodiment of the present invention;

fig. 18 provides a schematic diagram of a MIP adjacent to an initial MEP, in accordance with an embodiment of the present invention;

fig. 19 is a schematic structural diagram of a target MEP according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.

An embodiment of the present invention provides a fault determination method, as shown in fig. 1, the method includes:

step 101, the initial MEP obtains information of VLAN status in a VLAN list maintained by the initial MEP, and the obtained information is used as first VLAN status information.

Specifically, the information of the VLAN status in the maintained VLAN list refers to the status of the VLAN traffic in the maintained VLAN list, and generally, the status of the VLAN traffic may include a fault status (block) and a non-fault status (active). If the VLAN traffic in the VLAN list maintained by the initial MEP is a continuous whole segment, for example, VLAN 1-32 traffic, the information of the VLAN state in the VLAN list maintained by the initial MEP is: VLAN 1 status, VLAN2 status … VLAN 32 status. If the VLAN services in the VLAN list maintained by the initial MEP are not continuous and whole, such as VLAN 1-16 services, VLAN 20-24 services and VLAN 30-32 services, the information of the VLAN state in the VLAN list maintained by the initial MEP is: VLAN 1 status, VLAN2 status … VLAN 16 status; the status of VLAN20, the status of VLAN 21, status identifier … VLAN 24; the state of VLAN 30, the state of VLAN 31 and the state of VLAN 32.

Step 102, sending VLAN state acquisition request to MIP adjacent to itself.

And 103, receiving the second VLAN state information sent by the MIP adjacent to the VLAN.

Wherein the second VLAN status information includes: information of VLAN status in all MIPs and in the VLAN list maintained by the destination MEP.

Specifically, the number of all MIPs may be one or multiple, and when the number of the MIPs is one, the MIP sends the information of the VLAN status in the VLAN list maintained by the MIP to the originating MEP, and receives and forwards the information of the VLAN status in the VLAN list maintained by the destination MEP to the originating MEP. When the number of MIPs is multiple, except for the MIP adjacent to the starting MEP, the information of the VLAN status in the VLAN list maintained by the other MIPs and the destination MEP is finally forwarded to the starting MEP by the MIP adjacent to the starting MEP. For example, assuming that the generated network topology applying the 802.1ag protocol is as shown in fig. 2, and includes the originating MEP, MIP _1, MIP _2, MIP _3, and the destination MEP, the receiving, by the originating MEP, of the second VLAN status information sent by MIP _1 includes: the information of the VLAN status in the VLAN list maintained by MIP _1, the information of the VLAN status in the VLAN list maintained by MIP _2, the information of the VLAN status in the VLAN list maintained by MIP _3, and the information of the VLAN status in the VLAN list maintained by the destination MEP. That is, the VLAN status information of MIP _2 is first sent to MIP _1, and then MIP _1 forwards the VLAN status information to MEP; VLAN state information of MIP _3 is firstly sent to MIP _2, then is forwarded to MIP _1 by MIP _2, and finally is forwarded to MEP by MIP _ 1; the VLAN status information of the destination MEP is first sent to MIP _3, then forwarded from MIP _3 to MIP _2, then forwarded from MIP _2 to MIP _1, and finally forwarded from MIP _1 to the MEP.

And step 104, determining the failed node and the VLAN according to the first VLAN state information and the second VLAN state information.

It should be noted that the determined failed node may be one node or multiple nodes, and the failed VLAN may be one VLAN of one node, multiple VLANs of one node, or multiple VLANs of multiple nodes, which is determined according to actual situations.

Specifically, step 104 can be implemented by steps 104a to 104 d:

and 104a, if VLAN fault information exists in the first VLAN state information, determining the node with the fault as the VLAN with the VLAN fault information.

And step 104b, if VLAN fault information exists in the VLAN list maintained by the MIP in the second VLAN state information, determining the node with the fault as the MIP, and determining the VLAN with the fault as the VLAN with the VLAN fault information of the MIP.

Specifically, if the number of MIPs is plural, step 104b can be implemented by steps 104b1 and 104b 2:

step 104b1, if the VLAN fault information exists in the VLAN list maintained by the MIP adjacent to the second VLAN status information, determining that the failed node is the MIP adjacent to the second VLAN status information, and determining that the failed VLAN is the VLAN of the MIP adjacent to the second VLAN status information, where the VLAN fault information exists.

Step 104b2, if the second VLAN status information includes VLAN fault information in the VLAN list maintained by the MIP that is not adjacent to the second VLAN status information, determining that the failed node is the MIP that is not adjacent to the second VLAN status information, and determining that the failed VLAN is the VLAN with VLAN fault information of the MIP that is not adjacent to the second VLAN status information.

It should be noted that steps 104b1 and 104b2 may only perform one of the steps, or may perform both steps.

And step 104c, if VLAN fault information exists in a VLAN list maintained by the target MEP in the second VLAN state information, determining the node with the fault as the target MEP, and determining the VLAN with the VLAN fault information, which is the VLAN with the fault as the target MEP.

It should be noted that steps 104a, 104b, and 104c may only perform one of the steps, two of the steps, or all three steps.

Specifically, when the MIP adjacent to the starting MEP, the MIP not adjacent to the starting MEP, and the destination MEP send the second VLAN status information, the node identifier of the MIP should be additionally sent, so that when the starting MEP determines that the second VLAN status information has a fault information condition (assuming that the starting MEP is a faulty node at this time), and further determines that the MIP or the destination MEP is a faulty node, the determination may be performed according to the node identifier sent by the node and the VLAN status information in the maintained VLAN list at the same time, where the node identifier may be a Media Access Control (MAC) address. For example, suppose that the generated network topology applying the 802.1ag protocol is as shown in fig. 2, MIP _1 attaches the MAC address of itself when sending the information of the VLAN state in the VLAN list maintained by itself; MIP _2 additionally sends the MAC address of itself when sending the information of VLAN state in the VLAN list maintained by itself; MIP _3 attaches and sends own MAC address when sending information of VLAN state in the VLAN list maintained by itself; when sending information of VLAN state in a VLAN list maintained by a target MEP, the target MEP additionally sends the MAC address of the target MEP; thus, when the originating MEP receives the second VLAN status information, the MAC addresses of the nodes that generated these second VLAN status information are also received.

The method for determining the fault provided by the invention comprises the steps that an initial MEP obtains information of VLAN state in a VLAN list maintained by the initial MEP, and the obtained information is used as first VLAN state information; sending a VLAN state acquisition request to the MIP adjacent to the MIP; receiving second VLAN state information sent by MIPs adjacent to the second VLAN state information; wherein, the second VLAN state information comprises: all MIPs and VLAN state information in a VLAN list maintained by a destination MEP; and determining the failed node and the VLAN according to the first VLAN state information and the second VLAN state information. According to the technical scheme provided by the invention, the first VLAN state information can reflect the VLAN state of the initial MEP, and the second VLAN state information can reflect the VLAN states of the MIP and the target MEP, so that the initial MEP can determine the failed node and VLAN according to the first VLAN state information and the second VLAN state information, and the accurate positioning of the failed specific node and specific VLAN is realized.

An embodiment of the present invention provides another fault determining method, as shown in fig. 3, where the method includes:

step 201, the initial MEP obtains information of VLAN status in a VLAN list maintained by the initial MEP, and uses the obtained information as first VLAN status information.

Step 202, obtaining the number of segments of the VLAN in the VLAN list maintained by itself, the number of VLANs in each segment of the VLAN, and the VLAN initial value of each segment of the VLAN, and using the obtained information as first VLAN deployment information.

Specifically, the number of segments of the VLAN refers to the number of segments of the VLAN service to be maintained, the number of VLANs in each segment of the VLAN refers to the number of VLAN services included in each segment of the VLAN service to be maintained, and the VLAN start value of each segment of the VLAN refers to the value of the first VLAN service in each segment of the VLAN service to be maintained. If the service of the maintained VLAN is a continuous whole segment, such as VLAN 1-32 service, the number of the segments of the VLAN is 1, the number of the VLAN in the VLAN is 32, and the initial value of the VLAN is the value of VLAN 1. If the maintained VLAN service is not a continuous whole segment, such as VLAN 1-16 service, VLAN 20-24 service and VLAN 30-32 service, the number of VLAN segments is 3, the number of VLAN in the 1 st segment is 16, and the VLAN initial value of the 1 st segment is VLAN 1; the number of VLANs in the 2 nd VLAN section is 5, and the VLAN initial value of the 2 nd VLAN section is the value of VLAN 20; the number of the VLANs in the 3 rd VLAN section is 3, and the VLAN initial value of the 3 rd VLAN section is the value of the VLAN 30.

Step 203, sending a VLAN state acquisition request and first VLAN deployment information to the MIPs adjacent to itself.

Specifically, sending the first VLAN deployment information to the MIP adjacent to the starting MEP may enable the MIP adjacent to the starting MEP to detect whether VLAN information in the maintained VLAN list is correct according to the first VLAN deployment information, and a specific detection process is explained on the MIP side adjacent to the starting MEP.

And step 204, receiving the second VLAN state information sent by the MIP adjacent to the VLAN.

Wherein the second VLAN status information includes: information of VLAN status in all MIPs and VLAN lists maintained by destination MEP

And step 205, determining the failed node and the VLAN according to the first VLAN state information and the second VLAN state information.

The method for determining the fault provided by the invention comprises the steps that an initial MEP obtains information of VLAN state in a VLAN list maintained by the initial MEP, and the obtained information is used as first VLAN state information; sending a VLAN state acquisition request and first VLAN deployment information to MIPs adjacent to the MIPs; receiving second VLAN state information sent by MIPs adjacent to the second VLAN state information; wherein, the second VLAN state information comprises: all MIPs and VLAN state information in a VLAN list maintained by a destination MEP; and determining the failed node and the VLAN according to the first VLAN state information and the second VLAN state information. According to the technical scheme provided by the invention, the first VLAN state information can reflect the VLAN state of the initial MEP, and the second VLAN state information can reflect the VLAN states of the MIP and the target MEP, so that the initial MEP can determine the failed node and VLAN according to the first VLAN state information and the second VLAN state information, and the accurate positioning of the failed specific node and specific VLAN is realized.

An embodiment of the present invention provides another method for determining a fault, where a VLAN status acquisition request is included in an LTM message, as shown in fig. 4, the method includes:

step 301, the initial MEP obtains information of VLAN status in a VLAN list maintained by the initial MEP, and uses the obtained information as first VLAN status information.

Step 302, obtaining a VLAN status identifier corresponding to the first VLAN status information according to a pre-established correspondence between the status and the status identifier, and using the obtained VLAN status identifier as the first VLAN status identifier.

Specifically, the pre-established state-to-state identifier correspondence may be as shown in table 1,

TABLE 1

Step 303, obtaining the number of segments of the VLAN in the VLAN list maintained by the VLAN management device, the number of VLANs in each segment of the VLAN, and the VLAN initial value of each segment of the VLAN, and using the obtained information as the first VLAN deployment information.

And step 304, sending the LTM message carrying the first TLV to the MIP adjacent to the MIP.

Wherein the first TLV includes: presetting a VLAN state identifier and first VLAN deployment information.

Specifically, the preset VLAN status identifier is a VLAN status identifier corresponding to a VLAN in a VLAN list maintained by the starting MEP when all VLANs are in a non-failure (active) state. The VLAN status identifier of each VLAN traffic may be displayed in 1 bit, 8 bits constitute 1 byte, and for a VLAN status identifier that cannot constitute 1 byte, fill in Null, specifically, if the VLAN traffic in the VLAN list maintained by the initial MEP is VLANs 1 to 34, the status identifiers of VLANs 1 to 32 may constitute 4 bytes, and the remaining VLANs 33 and 34 cannot constitute 1 byte, so fill in 6 bits with Null, thereby constituting 1 byte.

Specifically, fig. 5 is a schematic diagram of a TLV structure provided in the embodiment of the present invention, and as shown in fig. 5, a Type: occupying 1 byte, and defining vendor-defined TLV type by 802.1ag protocol, wherein the field in TLV provided by the sending embodiment is 31; length: occupies 2 bytes, which is specified by the 802.1ag protocol to identify the total length of the subsequent field, which is 13 in the TLV provided in this transmission embodiment; OUI: 3 bytes are occupied, and the manufacturer identification is carried out according to the 802.1ag protocol; SubType: 1 byte, specified by 802.1ag to indicate the vendor's chart type; value _ i (section): 1 byte, i (where i is 1, 2 … N) represents the sequence number of the VLAN segment, where when the configured VLAN list is not a continuous VLAN, the number is set according to the VLAN segment; value _ i (vlan count): occupies 2 bytes and represents the number M of VLANs in the ith VLAN section in the VLAN list_i(ii) a Value _ i (start vlan): occupying 2 bytes, representing the initial VLAN value of the ith VLAN in the VLAN list, and having the range of 0x0001-0x0 FFE; value _ i (vlan flag): occupancy

(wherein,

indicating a rounding up) byte, which field, per bit (bit), represents the status of each VLAN in the ith VLAN segment in the VLAN list on the network element (where 0 represents a failed state, 1 represents a non-failed state, and Null represents a Null state).

Specifically, fig. 6 is a schematic diagram of the generated LTM packet carrying the TLV structure, as shown in fig. 6, where TTL occupies 1 byte and represents the number of nodes to be passed through, and the value is automatically decremented by 1 every time a node passes through, and when the TTL of the received LTM packet is 1, the LTM packet is not forwarded any more. Therefore, the setting is generally large so that the LTM message can reach the destination MEP.

And 305, receiving an LTR message which is sent by the MIP adjacent to the LTR message and carries the second TLV.

Wherein the second TLV includes: a VLAN state identifier corresponding to the second VLAN state information, and the number of VLAN sections in a VLAN list maintained by all MIPs and destination MEPs, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section.

Specifically, the LTR packet carrying the second TLV and sent by the MIP adjacent to the starting MEP includes: all MIP LTR messages carrying the second TLV and target MEP LTR messages carrying the second TLV. The LTR packet carrying the second TLV of each MIP includes: VLAN state identifiers corresponding to VLAN state information in a VLAN list maintained by self MIP in the second VLAN state information, the number of VLAN sections in the VLAN list maintained by self MIP, the number of VLAN sections in each VLAN section and the VLAN initial value of each VLAN section; the LTR packet carrying the second TLV of the destination MEP includes: the second VLAN state information includes a VLAN state identifier corresponding to the information of the VLAN state in the VLAN list maintained by the target MEP, the number of VLAN segments in the VLAN list maintained by the target MEP, the number of VLANs in each VLAN segment, and the VLAN start value of each VLAN segment.

Specifically, when the number of MIPs is multiple, except for the MIP adjacent to the starting MEP, the LTR messages carrying the second TLV of the remaining MIPs and the destination MEP are all finally forwarded to the starting MEP by the MIP adjacent to the starting MEP via the MIP adjacent to the starting MEP. For example, assuming that the generated network topology applying the 802.1ag protocol is as shown in fig. 2, and includes an originating MEP, an MIP _1, an MIP _2, an MIP _3, and a destination MEP, the receiving, by the originating MEP, an LTR packet carrying a second state identifier sent by the MIP _1 includes: the LTR message of MIP _1 carrying the second TLV, the LTR message of MIP _2 carrying the second TLV, the LTR message of MIP _3 carrying the second TLV and the LTR message of destination MEP carrying the second TLV. That is, the LTR message generated by MIP _2 is first sent to MIP _1, and is finally forwarded to MEP by MIP _ 1; the LTR message generated by MIP _3 is firstly sent to MIP _2, then is forwarded to MIP _1 by MIP _2, and finally is forwarded to MEP by MIP _ 1; the LTR message generated by the destination MEP is first sent to MIP _3, then forwarded from MIP _3 to MIP _2, then forwarded from MIP _2 to MIP _1, and finally forwarded from MIP _1 to the MEP.

Specifically, fig. 7 is a schematic diagram of a generated LTR packet with a TLV structure, where, as shown in fig. 7, TTL occupies 1 byte, and is obtained by automatically subtracting 1 from TTL in the LTM packet obtained after receiving the LTM packet, and the LTR packet is sent to MIP without being changed and is sent or forwarded to the originating MEP.

Step 306, obtaining the VLAN status identifier corresponding to the second VLAN status information in the second TLV, and using the obtained VLAN status identifier as the second VLAN status identifier.

Step 307, determining the failed node and VLAN according to the preset VLAN status identifier, the first VLAN status identifier and the second VLAN status identifier.

Specifically, step 307 can be implemented by steps 307a to 307 e:

step 307a, determining whether the first VLAN status identifier, the second VLAN status identifiers of all MIPs and the second VLAN status identifier of the destination MEP are the same as the preset VLAN status identifier.

Step 307b, if the first VLAN status identifier is different from the preset VLAN status identifier, determining the failed node as the failed node, and determining the failed VLAN as the VLAN whose VLAN status identifier is different from the preset VLAN status identifier.

Step 307c, if the second VLAN status identifier of the MIP is different from the preset VLAN status identifier, determining that the failed node is the MIP, and determining that the failed VLAN is the VLAN with the second VLAN status identifier of the MIP different from the preset VLAN status identifier.

Specifically, when the number of MIPs is plural, step 307c may be implemented by steps 307c1 and 307c 2:

step 307c1, if the second VLAN status identifier of the MIP adjacent to the node is different from the preset VLAN status identifier, determining that the failed node is the MIP adjacent to the node, and determining that the failed VLAN is the VLAN having the second VLAN status identifier of the MIP adjacent to the node and the preset VLAN status identifier.

Step 307c2, if the second VLAN status identifier of the MIP that is not adjacent to the failed VLAN is different from the preset VLAN status identifier, determining that the failed node is the MIP that is not adjacent to the failed node, and determining that the failed VLAN is the VLAN whose second VLAN status identifier of the MIP that is not adjacent to the failed node is different from the preset VLAN status identifier.

It should be noted that steps 307c1 and 307c2 may only perform one of the steps, or may perform both steps.

Specifically, there may be one or more MIPs that are not adjacent to the MIP, and if there are multiple MIPs that are not adjacent to the MIP, there are multiple sets of second VLAN status identifiers carried by the LTR packet of the MIP that is not adjacent to the MIP, which set of second VLAN status identifiers is different from the preset VLAN status identifier needs to be compared, and the MIP corresponding to the LTR packet where the set of second VLAN status identifiers that is different from the preset VLAN status identifier is the failed MIP. For example, assuming that a network topology diagram is shown in fig. 2, MIPs that are not adjacent to a starting MEP are MIP _2 and MIP _3, respectively, LTR messages that carry a second VLAN status identifier with MIPs that are not adjacent to the MIP are LTR messages that carry a second VLAN status identifier with MIP _2 and LTR messages that carry a second VLAN status identifier with MIP _3, and if a second VLAN status identifier carried by the LTR message of MIP _2 is different from a preset VLAN status identifier, it is determined that a node with a fault is MIP _ 2; if the second VLAN state identifier carried by the LTR message of MIP _3 is different from the preset VLAN state identifier, determining the node with the fault as MIP _ 3; if the second VLAN state identifiers carried by the LTR message of MIP _2 and the LTR message of MIP _3 are different from the preset VLAN state identifiers, determining that the nodes with faults are respectively MIP _2 and MIP _3, and determining that the VLRs with faults are respectively VLRs with the second VLAN state identifiers different from the preset VLAN state identifiers in the LTR messages of MIP _2 and MIP _ 3.

Step 307d, if the second VLAN status identifier of the destination MEP is different from the preset VLAN status identifier, determining the failed node as the destination MEP, and determining the second VLAN status identifier of the failed VLAN as the destination MEP as a VLAN different from the preset VLAN status identifier.

It should be noted that steps 306b, 306c, and 306d may only perform one of the steps, two of the steps, or all three steps.

The failure determination method provided by the invention comprises the steps that an initial MEP sends an LTM message carrying a first TLV to an MIP adjacent to the initial MEP; wherein the first TLV includes: presetting a VLAN state identifier and first VLAN deployment information; acquiring a VLAN state identifier corresponding to the first VLAN state information according to the pre-established state and state identifier corresponding relation, and taking the acquired VLAN state identifier as the first VLAN state identifier; receiving an LTR message carrying a second TLV and sent by the MIP adjacent to the LTR message; obtaining a VLAN state identifier corresponding to second VLAN state information in the second TLV, and taking the obtained VLAN state identifier as a second VLAN state identifier; and determining the failed node and the VLAN according to the preset VLAN state identifier, the first VLAN state identifier and the third VLAN state identifier. According to the technical scheme provided by the invention, the first TLV can reflect the VLAN state of the initial MEP, and the second TLV can reflect the VLAN state of the MIP and the target MEP, so that the initial MEP can determine the failed node and VLAN according to the preset VLAN state identifier, the first VLAN state identifier in the first TLV and the second VLAN state identifier in the second TLV, and the accurate positioning of the failed specific node and specific VLAN is realized.

It should be noted that the execution subjects of the fault determination methods provided by the embodiments corresponding to fig. 1, fig. 3, and fig. 4 are all start MEPs.

An embodiment of the present invention provides another fault determining method, as shown in fig. 8, where the method includes:

step 401, the MIP adjacent to the starting MEP receives the VLAN status obtaining request sent by the starting MEP.

Step 402, obtaining information of VLAN status in the VLAN list maintained by the device, and using the obtained information as third VLAN status information.

Step 403, sending a VLAN status acquisition request to the nodes adjacent to the VLAN status acquisition request.

Wherein, the node adjacent to itself includes: when there is a MIP adjacent to the node itself, the node adjacent to the node itself is the MIP, and when there is no MIP adjacent to the node itself, the node adjacent to the node itself is the destination MEP.

It should be noted that there is no strict sequence between step 402 and step 403, step 402 may be executed first and then step 403 is executed, step 403 may be executed first and then step 402 is executed, or step 403 may be executed while step 402 is executed.

It should be noted that when the number of MIPs is one, the node in this step refers to the destination MEP, and when the number of MIPs is multiple, the node in this step refers to the MIP.

And step 404, receiving fourth VLAN state information sent by the nodes adjacent to the VLAN state information.

Wherein the fourth VLAN status information includes: information of VLAN state in VLAN list maintained by all nodes except initial MEP and itself;

step 405, sending the third VLAN status information and the fourth VLAN status information as second VLAN status information to the initial MEP.

In the fault determining method provided by the invention, an MIP adjacent to an initial MEP receives a VLAN state acquisition request sent by the initial MEP; obtaining VLAN state information in a VLAN list maintained by the VLAN information acquisition device, and taking the obtained information as third VLAN state information; sending a VLAN state acquisition request to the MIP adjacent to the MIP; receiving fourth VLAN state information sent by MIPs adjacent to the fourth VLAN state information; and sending the third VLAN state information and the fourth VLAN state information as second VLAN state information to the initial MEP. According to the technical scheme provided by the invention, the first VLAN state information can reflect the VLAN state of the initial MEP, and the second VLAN state information can reflect the VLAN states of the MIP and the target MEP, so that the initial MEP can determine the failed node and VLAN according to the first VLAN state information and the second VLAN state information, and the accurate positioning of the failed specific node and specific VLAN is realized.

An embodiment of the present invention provides another fault determining method, as shown in fig. 9, where the method includes:

step 501, the MIP adjacent to the starting MEP receives the VLAN state acquisition request and the first VLAN deployment information sent by the starting MEP.

Wherein the first VLAN deployment information comprises: the number of VLAN segments in the VLAN list maintained by the initial MEP, the number of VLANs in each VLAN segment and the VLAN initial value of each VLAN segment.

Step 502, obtaining the number of segments of the VLAN in the VLAN list maintained by itself, the number of VLANs in each segment of the VLAN, and the VLAN initial value of each segment of the VLAN, and using the obtained information as second VLAN deployment information.

Step 503, determine whether the second VLAN deployment information is the same as the first VLAN deployment information.

Specifically, the step is a pre-detection process, and the MIP adjacent to the initial MEP detects whether the VLAN service maintained by the initial MEP is the same as the VLAN service maintained by itself, if the second VLAN deployment information is the same as the first VLAN deployment information, it indicates that the VLAN service maintained by itself is the same as the VLAN service maintained by the initial MEP, and if the second VLAN deployment information is different from the first VLAN deployment information, it indicates that the VLAN service maintained by itself is different from the VLAN service maintained by the initial MEP, that is, the VLAN service maintained by itself is wrong.

Specifically, the step of determining whether the second VLAN deployment information is the same as the first VLAN deployment information includes: judging whether the number of VLAN sections in the VLAN list maintained by the self is the same as that of VLAN sections in the VLAN list maintained by the initial MEP, whether the number of VLAN sections in each VLAN section in the VLAN list maintained by the self is the same as that of VLAN sections in the VLAN list maintained by the initial MEP, and whether the VLAN initial value of each VLAN section in the VLAN list maintained by the self is the same as that of each VLAN section in the VLAN list maintained by the initial MEP. If the VLAN deployment information is the same as the first VLAN deployment information, the second VLAN deployment information is the same as the first VLAN deployment information, and if one of the VLAN deployment information is different from the first VLAN deployment information, the second VLAN deployment information is different from the first VLAN deployment information.

Step 504, if the second VLAN deployment information is the same as the first VLAN deployment information, obtaining information of VLAN status in a VLAN list maintained by the VLAN deployment information, and using the obtained information as third VLAN status information.

And 505, sending a VLAN state acquisition request and first VLAN deployment information to nodes adjacent to the VLAN state acquisition request.

Specifically, after receiving a VLAN state acquisition request and first VLAN deployment information sent by an MIP adjacent to the initial MEP, a node not adjacent to the initial MEP detects whether a VLAN service maintained by the initial MEP is the same as a VLAN service maintained by the node itself.

Step 506, receiving the fourth VLAN status information sent by the node adjacent to the node.

Wherein the fourth VLAN status information includes: information of VLAN status in VLAN lists maintained by all nodes except the originating MEP and itself.

And step 507, sending the third VLAN state information and the fourth VLAN state information to the initial MEP as second VLAN state information.

An embodiment of the present invention provides another method for determining a fault, where a VLAN status acquisition request is included in an LTM message, as shown in fig. 10, and the method includes:

step 601, the MIP adjacent to the starting MEP receives the LTM packet carrying the first TLV sent by the starting MEP.

Wherein the first TLV includes: presetting a VLAN state identifier and first VLAN deployment information. The first VLAN deployment information includes: the number of VLAN segments in the VLAN list maintained by the initial MEP, the number of VLANs in each VLAN segment and the VLAN initial value of each VLAN segment.

Step 602, obtaining the number of segments of the VLAN in the VLAN list maintained by itself, the number of VLANs in each segment of the VLAN, and the VLAN initial value of each segment of the VLAN, and using the obtained information as second VLAN deployment information.

Step 603, determining whether the second VLAN deployment information is the same as the first VLAN deployment information.

Step 604, if the second VLAN deployment information is the same as the first VLAN deployment information, obtaining information about the VLAN status in the VLAN list maintained by the VLAN management apparatus, and using the obtained information as third VLAN status information.

Step 605, changing the preset VLAN status identifier in the first TLV according to the third VLAN status information, and generating a third TLV.

Specifically, the first TLV includes a preset VLAN status identifier, and the preset VLAN status identifier of the first TLV may be directly changed according to the third VLAN status information, so as to generate the third TLV.

And step 606, generating an LTR message carrying a third TLV.

Step 607, sending the VLAN status acquisition request and the first VLAN deployment information to the nodes adjacent to itself.

And step 608, receiving the LTR packet carrying the fourth TLV sent by the node adjacent to the LTR packet.

Wherein the fourth TLV includes: VLAN state identification corresponding to the fourth VLAN state information, and the number of VLAN sections in a VLAN list maintained by all nodes except the initial MEP and the VLAN, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section.

And step 609, sending the LTR message carrying the third TLV and the LTR message carrying the fourth TLV to the starting MEP as LTR messages carrying the second TLV.

Specifically, the LTR packet of the second TLV includes: LTR message carrying the third TLV and LTR message carrying the fourth TLV.

In the failure determination method provided by the invention, an MIP adjacent to an initial MEP receives an LTM message which is sent by the initial MEP and carries a first TLV; obtaining VLAN state information in a VLAN list maintained by the VLAN information acquisition device, and taking the obtained information as third VLAN state information; changing the preset VLAN state identifier in the first TLV according to the third VLAN state information to generate a third TLV; generating an LTR message carrying a third TLV; sending a VLAN state acquisition request and first VLAN deployment information to MIPs adjacent to the MIPs; receiving an LTR message carrying a fourth TLV and sent by an MIP adjacent to the LTR message; and sending the LTR message carrying the third TLV and the LTR message carrying the fourth TLV to the starting MEP as LTR messages carrying the second TLV. According to the technical scheme provided by the invention, the first TLV can reflect the VLAN state of the initial MEP, and the second TLV can reflect the VLAN state of the MIP and the target MEP, so that the initial MEP can determine the failed node and VLAN according to the preset VLAN state identifier, the first VLAN state identifier in the first TLV and the second VLAN state identifier in the second TLV, and the accurate positioning of the failed specific node and specific VLAN is realized.

It should be noted that the execution subjects of the failure determination methods provided by the embodiments corresponding to fig. 8 to 10 are all MIPs adjacent to the starting MEP.

An embodiment of the present invention provides another fault determining method, as shown in fig. 11, where the method includes:

step 701, the destination MEP receives a VLAN state acquisition request sent by the MIP adjacent to the destination MEP.

It should be noted that, a VLAN status obtaining request is generated by an initial MEP and sent to MIPs adjacent to a destination MEP through respective MIPs, it is assumed that a network topology diagram is as shown in fig. 2, a MIP adjacent to a destination MEP is referred to as MIP _3, a VLAN status obtaining request sent by a MIP adjacent to itself is referred to as a VLAN status obtaining request sent by receiving MIP _3, and a VLAN status obtaining request is sent by an initial MEP to MEP _1, then sent by MEP _1 to MEP _2, and finally sent by MEP _2 to MEP _ 3.

Step 702, obtaining the information of the VLAN status in the VLAN list maintained by the device, and using the obtained information as fifth VLAN information.

Step 703, sending the fifth VLAN status information to the MIP adjacent to the fifth VLAN status information.

Specifically, assuming that a network topology is shown in fig. 2, the destination MEP obtains its own VLAN status information (fifth VLAN status information) and then sends the VLAN status information to MIP _3, MIP _3 sends the VLAN status information to MIP _2, MIP _2 sends the VLAN status information to MIP _1, and MIP _1 sends the start MEP.

In the fault determination method provided by the embodiment of the present invention, a destination MEP receives a VLAN status acquisition request sent by an MIP adjacent to the destination MEP; obtaining VLAN state information in a VLAN list maintained by the VLAN state information self; and sending the obtained VLAN state information to the MIPs adjacent to the VLAN. According to the technical scheme provided by the invention, the first VLAN state information can reflect the VLAN state of the initial MEP, and the second VLAN state information can reflect the VLAN states of the MIP and the target MEP, so that the initial MEP can determine the failed node and VLAN according to the first VLAN state information and the second VLAN state information, and the accurate positioning of the failed specific node and specific VLAN is realized.

An embodiment of the present invention provides another fault determining method, as shown in fig. 12, where the method includes:

step 801, the destination MEP receives a VLAN state acquisition request and first VLAN deployment information sent by the MIP adjacent to the destination MEP.

Step 802, obtaining the number of segments of the VLAN in the VLAN list maintained by itself, the number of VLANs in each segment of the VLAN, and the VLAN initial value of each segment of the VLAN, and using the obtained information as fourth VLAN deployment information.

Step 803, determine whether the fourth VLAN deployment information is the same as the first VLAN deployment information.

Specifically, the step is a pre-detection process, where the destination MEP detects whether a VLAN service maintained by the originating MEP is the same as a VLAN service maintained by the destination MEP, if the fourth VLAN deployment information is the same as the first VLAN deployment information, it indicates that the VLAN service maintained by the destination MEP is the same as the VLAN service maintained by the originating MEP, and if the fourth VLAN deployment information is different from the first VLAN deployment information, it indicates that the VLAN service maintained by the destination MEP is different from the VLAN service maintained by the originating MEP, that is, the VLAN service maintained by the destination MEP is incorrect.

Step 804, if the fourth VLAN deployment information is the same as the first VLAN deployment information, obtaining information of VLAN status in a VLAN list maintained by the VLAN deployment information, and using the obtained information as fifth VLAN status information.

Step 805, the fifth VLAN status information is sent to the MIP adjacent to the fifth VLAN status information.

An embodiment of the present invention provides another method for determining a fault, where a VLAN status acquisition request is included in an LTM message, as shown in fig. 13, and the method includes:

step 901, the target MEP receives an LTM packet carrying a first TLV sent by the MIP adjacent to the target MEP.

Step 902, obtaining the number of segments of the VLAN in the VLAN list maintained by itself, the number of VLANs in each segment of the VLAN, and the VLAN initial value of each segment of the VLAN, and using the obtained information as fourth VLAN deployment information.

Step 903, judging whether the fourth VLAN deployment information is the same as the first VLAN deployment information.

Step 904, if the fourth VLAN deployment information is the same as the first VLAN deployment information, obtaining information of VLAN status in a VLAN list maintained by the VLAN deployment information, and using the obtained information as fifth VLAN status information.

Step 905, changing the preset VLAN status identifier in the first TLV according to the fifth VLAN status information, and generating a fifth TLV.

And step 906, generating an LTR message carrying a fifth TLV.

Step 907, sending the LTR packet carrying the fifth TLV to the MIP adjacent to itself.

In the fault determination method provided by the embodiment of the present invention, a target MEP receives an LTM packet carrying a first TLV and sent by an MIP adjacent to the target MEP; acquiring the state information of a fifth VLAN in a VLAN list maintained by the VLAN information acquisition device; changing the preset VLAN state identifier in the first TLV according to the fifth VLAN state information to generate a fifth TLV; generating an LTR message carrying a fifth TLV; and sending the LTR message carrying the fifth TLV to the MIP adjacent to the LTR message. According to the technical scheme provided by the invention, the first TLV can reflect the VLAN state of the initial MEP, and the second TLV can reflect the VLAN state of the MIP and the target MEP, so that the initial MEP can determine the failed node and VLAN according to the preset VLAN state identifier, the first VLAN state identifier in the first TLV and the second VLAN state identifier in the second TLV, and the accurate positioning of the failed specific node and specific VLAN is realized.

It should be noted that the execution subjects of the fault determination methods provided by the embodiments corresponding to fig. 11 to 13 are all target MEPs.

For convenience of description, it is assumed that a network topology structure diagram is shown in fig. 14, and then an MIP adjacent to a starting MEP is MIP _1, and an MIP adjacent to a destination MEP is MIP _2, as shown in fig. 15, the method includes:

step 1001, the initiating MEP obtains a VLAN list of the VLAN service maintained by the initiating MEP.

Step 1002, the initial MEP obtains the number of segments of the VLAN, the number of VLANs in each segment of the VLAN, the VLAN initial value of each segment of the VLAN, and the state of the VLAN in each segment of the VLAN according to the obtained VLAN list.

Step 1003, the start MEP fills a TLV structure according to the obtained number of the segments of the VLAN, the number of the VLANs in each segment of the VLAN, the VLAN start value of each segment of the VLAN, and the preset VLAN status identifier, and generates a TLV.

Step 1004, the start MEP adds the obtained TLV to the tail of the LTM packet to generate an LTM packet carrying the TLV.

Step 1005, the starting MEP represents the obtained VLAN states in all VLAN segments by the first VLAN state identifier according to the corresponding relationship between the state and the state identifier.

Step 1006, the initial MEP sends an LTM packet carrying TLV to MIP _ 1.

Step 1007, MIP _1 receives the LTM message sent by the initial MEP.

Step 1008, MIP _1 generates LTR message carrying TLV.

Step 1009, MIP _1 sends the generated LTR message to the originating MEP.

Step 1010, the start MEP receives the LTR message sent by MIP _ 1.

It should be noted that the LTR messages in steps 1008 to 1010 all refer to LTR messages generated by MIP _1, where the LTR messages carry MAC information of MIP _ 1.

Step 1011, MIP _1 sends the received LTM message to MIP _ 2.

It should be noted that step 1008 and step 1011 are executed without a specific sequence, and step 1008 may be executed first, step 1011 may also be executed first, or step 1008 and step 1011 may also be executed simultaneously.

Step 1012, MIP _2 receives the LTM packet sent by MIP _ 1.

And step 1013, the MIP _2 generates LTR messages carrying TLV.

And step 1014, the MIP _2 sends the generated LTR message to the MIP _ 1.

Step 1015, MIP _1 receives the LTR message sent by MIP _ 2.

Step 1016, MIP _1 forwards the received LTR message to the originating MEP.

Step 1017, the initiating MEP receives the LTR message forwarded by MIP _ 1.

It should be noted that the LTR messages in steps 1013-1017 refer to LTR messages generated by MIP _2, where the LTR messages carry MAC information of MIP _ 2.

Step 1018, MIP _2 sends the received LTM message to the destination MEP.

It should be noted that step 1013 and step 1018 are not executed in a specific order, and step 1013 may be executed first, step 1018 may be executed first, or step 1018 may be executed at the same time when step 1013 is executed.

Step 1019, the target MEP receives the LTM packet sent by MIP _ 2.

Step 1020, the destination MEP generates an LTR packet carrying TLV.

And step 1021, the destination MEP sends the generated LTR message to MIP _ 2.

Step 1022, MIP _2 receives the LTR message sent by the destination MEP.

Step 1023, MIP _2 forwards the received LTR message to MIP _ 1.

Step 1024, MIP _1 receives the LTR message sent by MIP _ 2.

Step 1025, MIP _1 forwards the received LTR message to the originating MEP.

In step 1026, the initiating MEP receives the LTR message sent by MIP _ 1.

It should be noted that the LTR messages in steps 1021 to 1026 refer to LTR messages generated by the destination MEP, where the LTR messages carry MAC information of the destination MEP.

Step 1027, the initiating MEP determines the failed node and VLAN according to the preset VLAN status identifier, the VLAN status identifier in TLV carried by LTM message, the received VLAN status identifier in TLV carried by LTR message of MIP _1, the received VLAN status identifier in TLV carried by LTR message of MIP _2, the received VLAN status identifier in TLV carried by LTR message of destination MEP, and the MAC information of MIP _1, MIP _2, and destination MEP.

A specific scenario is further provided below to describe the fault determining method provided in the embodiment of the present invention, assuming that a network topology schematic diagram is shown in fig. 16, assuming that a starting MEP sends a VLAN20-51 service, a receiving destination MEP finds that data has packet loss, the starting MEP needs to determine which specific node and which VLAN have a fault, and it is assumed that VLAN 21 of MIP _2 has a fault, and a fault determining process is as follows:

step 1, configuring 802.1ag OAM for each network element of the network: and according to the maintained service, performing 802.1ag OAM configuration on each network element. The scheme is embodied in configuring the maintained VLAN, configuring a switch for opening or closing the function of analyzing the TLV structure and the like under the 802.1ag OAM service instance.

Step 2, the initial MEP performs LT operation: starting the MEP equipment to perform LT operation, checking the opening of the equipment switch, and packaging TLV according to the actual condition by using the VLAN list of the VLAN service maintained by the equipment. Here, since there is only one VLAN, a Value _ i (Section) field is filled with a Value corresponding to 1, so that Value _1(Section) is obtained; 51-20+1 ═ 32, so the Value _1(VLAN count) field is filled with the Value _1 corresponding to 32, resulting in Value _1 (32); the initial Value of this VLAN is VLAN20, so the Value of VLAN20 (the Value of VLAN20 is in 0x0001-0x0 FFE) is filled in Value _1(Start VLAN); by the formula

Value _1(VLAN Flag) is calculated as 4 bytes, the obtained VLAN status is mapped to the corresponding bit, and 32 VLANs are non-faulty. Encapsulating TLV for the corresponding bit position 1, encapsulating the LTM message, and sending out the LTM message carrying the TLV structure.

Step 3, the MIP and the target MEP equipment process the LTM message: after receiving the LTM message, the MIP forwards the LTM and replies the LTR. And after receiving the LTM message, the target MEP equipment replies LTR. After receiving the LTM message, MIP _2 analyzes the TLV added to the received LTM message due to the switch being turned on, obtains Value _1(Section), Value _1(VLAN count), Value _1(Start VLAN), and Value _1(VLAN Flag) in the TLV, compares the Value _1(VLAN Flag) in the LTM message with the mapping state of the VLAN in the VLAN list of the device on the device, and when replying the LTR message, fills the bit position of the VLAN 21 corresponding to the Value _1(VLAN Flag) in the LTR message to 0 because the VLAN 21 of the device fails, encapsulates the TLV, and sends the carried LTR message to MIP _ 1.

Step 4, starting MEP to process LTR message: the initial MEP analyzes the received LTR message, analyzes and processes the TLV structure carried by the LTR message, and extracts the field Value 1 of Value _1(Section), the field Value 32 of Value _1(Vlan count), the field Value 20 of Value _1(Start Vlan), and the Vlan status Value in the Vlan list represented by the 4-byte bit of Value _1(Vlan Flag) to compare with the Vlan status Value in the TLV structure carried by the LTM message, so as to find that the Vlan 21 status Value in the TLV structure carried by the LTR message of MIP _2 is inconsistent, thereby locating the fault node as MIP _2 and the fault Vlan as Vlan 21.

The embodiment of the invention also provides a computer-readable storage medium, which stores computer-executable instructions, wherein the computer-executable instructions are used for executing the method for testing the performance of any one of the magnetic disks.

An embodiment of the present invention further provides an initial MEP, as shown in fig. 17, the initial MEP 11 includes:

the first obtaining module 1101 is configured to obtain information of a VLAN state in a VLAN list maintained by an MEP of the first obtaining module, and use the obtained information as first VLAN state information.

A first sending module 1102, configured to send a VLAN status obtaining request to the MIP adjacent to the starting MEP.

A first receiving module 1103, configured to receive second VLAN status information sent by an MIP adjacent to the starting MEP; wherein, the second VLAN state information comprises: information of VLAN status in all MIPs and in the VLAN list maintained by the destination MEP.

The first processing module 1104 is configured to determine a failed node and a failed VLAN according to the first VLAN status information and the second VLAN status information.

Further, the first processing module 1104 is specifically configured to:

if VLAN fault information exists in the first VLAN state information, the node with the fault is determined to be the initial MEP, and the VLAN with the fault is determined to be the VLAN with the VLAN fault information of the initial MEP.

If VLAN fault information exists in a VLAN list maintained by the MIP in the second VLAN state information, the node with the fault is determined to be the MIP, and the VLAN with the fault is determined to be the VLAN with the VLAN fault information of the MIP.

If VLAN fault information exists in a VLAN list maintained by the target MEP in the second VLAN state information, the node with the fault is determined to be the target MEP, and the VLAN with the fault information is determined to be the VLAN of the target MEP.

Further, the first obtaining module 1101 is further configured to obtain the number of segments of the VLAN in the VLAN list maintained by the starting MEP, the number of VLANs in each segment of the VLAN, and a VLAN start value of each segment of the VLAN, and use the obtained information as the first VLAN deployment information.

The first sending module 1102 is further configured to send a VLAN status acquisition request and first VLAN deployment information to the MIPs adjacent to the starting MEP.

Further, the VLAN status obtaining request is included in an LTM message, and the first sending module 1102 is specifically configured to send an LTM message carrying a first TLV to an MIP adjacent to the initial MEP; wherein the first TLV includes: presetting a VLAN state identifier and first VLAN deployment information.

The first obtaining module 1101 is further configured to obtain a VLAN status identifier corresponding to the first VLAN status information according to a pre-established correspondence between a status and a status identifier, and use the obtained VLAN status identifier as the first VLAN status identifier.

The first receiving module 1103 is specifically configured to:

receiving an LTR message carrying a second TLV and sent by an MIP adjacent to the starting MEP; wherein the second TLV includes: a VLAN state identifier corresponding to the second VLAN state information, and the number of VLAN sections in a VLAN list maintained by all MIPs and destination MEPs, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section.

And acquiring the VLAN state identifier corresponding to the second VLAN state information in the second TLV, and taking the obtained VLAN state identifier as the second VLAN state identifier.

The first processing module 1104 is specifically configured to: and determining the failed node and the VLAN according to the preset VLAN state identifier, the first VLAN state identifier and the second VLAN state identifier.

Further, the first processing module 1104 is further specifically configured to:

and if the first VLAN state identifier is different from the preset VLAN state identifier, determining the failed node as an initial MEP, and determining the failed VLAN as a VLAN of which the VLAN state identifier is different from the preset VLAN state identifier.

If the second VLAN state identifier of the MIP is different from the preset VLAN state identifier, the node with the fault is determined to be the MIP, and the VLAN with the fault is determined to be the VLAN with the second VLAN state identifier of the MIP different from the preset VLAN state identifier.

And if the second VLAN state identifier of the destination MEP is different from the preset VLAN state identifier, determining the node with the fault as the destination MEP, and determining the VLAN with the fault as the second VLAN state identifier of the destination MEP and the preset VLAN state identifier as different.

The initial MEP provided by the invention acquires VLAN state information in a VLAN list maintained by the initial MEP, and takes the acquired information as first VLAN state information; sending a VLAN state acquisition request to the MIP adjacent to the MIP; receiving second VLAN state information sent by MIPs adjacent to the second VLAN state information; wherein the second VLAN status information includes: all MIPs and VLAN state information in a VLAN list maintained by a destination MEP; and determining the failed node and the VLAN according to the first VLAN state information and the second VLAN state information. According to the technical scheme provided by the invention, the first VLAN state information can reflect the VLAN state of the initial MEP, and the second VLAN state information can reflect the VLAN states of the MIP and the target MEP, so that the initial MEP can determine the failed node and VLAN according to the first VLAN state information and the second VLAN state information, and the accurate positioning of the failed specific node and specific VLAN is realized.

In practical applications, the first obtaining module 1101, the first sending module 1102, the first receiving module 1103, and the first Processing module 1104 may be implemented by a Central Processing Unit (CPU), a microprocessor Unit (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like located at the start MEP.

An embodiment of the present invention further provides a MIP adjacent to the starting MEP, as shown in fig. 18, the MIP 12 adjacent to the starting MEP includes:

a second receiving module 1201, configured to receive a VLAN status obtaining request sent by the starting MEP.

A second obtaining module 1202, configured to obtain information of a VLAN state in a VLAN list maintained by a MIP adjacent to the starting MEP, and use the obtained information as third VLAN state information.

A second sending module 1203, configured to send a VLAN status obtaining request to a node that is not adjacent to the initial MEP.

Wherein the nodes not adjacent to the starting MEP include: when there is an MIP that is not adjacent to the starting MEP, the node that is not adjacent to the starting MEP is the MIP, and when there is no MIP that is not adjacent to the starting MEP, the node that is not adjacent to the starting MEP is the destination MEP.

It should be noted that, assuming that the generated network topology applying the 802.1ag protocol is as shown in fig. 2, the MIP adjacent to the starting MEP is MIP _1, and the MIP adjacent to MIP _1 is MIP _2, then the MIP not adjacent to the starting MEP is MIP _ 2.

The second receiving module 1201 is further configured to receive fourth VLAN status information sent by a node that is not adjacent to the starting MEP; wherein the fourth VLAN status information includes: information of VLAN status in VLAN lists maintained by all nodes except the originating MEP and MIPs adjacent to the originating MEP.

The second sending module 1203 is further configured to send the third VLAN status information and the fourth VLAN status information to the initial MEP as second VLAN status information.

Further, the second receiving module 1201 is specifically configured to receive a VLAN state acquisition request and first VLAN deployment information sent by the initial MEP; wherein the first VLAN deployment information comprises: the number of VLAN segments in the VLAN list maintained by the initial MEP, the number of VLANs in each VLAN segment and the VLAN initial value of each VLAN segment.

The second obtaining module 1202 is specifically configured to:

and acquiring the number of VLAN sections in a VLAN list maintained by the MIP adjacent to the initial MEP, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section, and taking the acquired information as second VLAN deployment information.

And judging whether the second VLAN deployment information is the same as the first VLAN deployment information.

And if the second VLAN deployment information is the same as the first VLAN deployment information, obtaining VLAN state information in a VLAN list maintained by the MIP adjacent to the initial MEP, and taking the obtained information as third VLAN state information.

The second sending module 1203 is specifically configured to send a VLAN status acquisition request and first VLAN deployment information to a node that is not adjacent to the starting MEP.

Further, the VLAN status acquisition request is included in the LTM message. A second receiving module 1201, specifically configured to receive an LTM packet carrying a first TLV sent by an initial MEP; wherein the first TLV includes: presetting a VLAN state identifier and first VLAN deployment information.

MIP 12 adjacent to the starting MEP further comprises: the second processing module 1204 is configured to change the preset VLAN status identifier in the first TLV according to the third VLAN status information, and generate a third TLV; and generating an LTR message carrying a third TLV.

The second sending module 1203 is specifically configured to send the LTM packet carrying the first TLV to a node not adjacent to the initial MEP.

A second receiving module 1201, specifically configured to receive an LTR packet carrying a fourth TLV sent by a node adjacent to the second receiving module; wherein the fourth TLV includes: VLAN state identification corresponding to the fourth VLAN state information, and the number of VLAN sections in a VLAN list, the number of VLAN in each VLAN section and VLAN initial value of each VLAN section which are maintained by all nodes except the initial MEP and MIP adjacent to the initial MEP.

The second sending module 1203 is further specifically configured to send the LTR packet carrying the third TLV and the LTR packet carrying the fourth TLV to the originating MEP as LTR packets carrying the second TLV

The MIP adjacent to the initial MEP receives a VLAN state acquisition request sent by the initial MEP; obtaining information of VLAN state in a VLAN list maintained by MIP adjacent to the initial MEP, and taking the obtained information as third VLAN state information; sending a VLAN state acquisition request to a MIP which is not adjacent to the initial MEP; receiving fourth VLAN state information sent by MIP which is not adjacent to the initial MEP; and sending the third VLAN state information and the fourth VLAN state information as second VLAN state information to the initial MEP. According to the technical scheme provided by the invention, the first VLAN state information can reflect the VLAN state of the initial MEP, and the second VLAN state information can reflect the VLAN states of the MIP and the target MEP, so that the initial MEP can determine the failed node and VLAN according to the first VLAN state information and the second VLAN state information, and the accurate positioning of the failed specific node and specific VLAN is realized.

In practical applications, the second receiving module 1201, the second obtaining module 1202, the second sending module 1203, and the second processing module 1204 may be implemented by a CPU, an MPU, a DSP, an FPGA, or the like of the MIP adjacent to the starting MEP.

An embodiment of the present invention further provides a target MEP, as shown in fig. 19, where the target MEP 13 includes:

a third receiving module 1301, configured to receive a VLAN status obtaining request sent by a MIP adjacent to the destination MEP.

A third obtaining module 1302, configured to obtain information of a VLAN state in the VLAN list maintained by the destination MEP, and use the obtained information as fifth VLAN state information.

A third sending module 1303, configured to send the fifth VLAN status information to the MIP adjacent to the destination MEP.

Further, the third receiving module 1301 is specifically configured to receive a VLAN state acquisition request and first VLAN deployment information sent by an MIP adjacent to the destination MEP; wherein the first VLAN deployment information comprises: the number of VLAN segments in the VLAN list maintained by the initial MEP, the number of VLANs in each VLAN segment and the VLAN initial value of each VLAN segment.

The third obtaining module 1302 is specifically configured to:

and acquiring the number of VLAN sections in a VLAN list maintained by the target MEP, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section, and taking the acquired information as fourth VLAN deployment information.

And judging whether the fourth VLAN deployment information is the same as the first VLAN deployment information.

And if the fourth VLAN deployment information is the same as the first VLAN deployment information, obtaining VLAN state information in a VLAN list maintained by the target MEP, and taking the obtained information as fifth VLAN state information.

Further, the VLAN status acquisition request is included in the LTM message. A third receiving module 1301, specifically configured to receive an LTM packet carrying a first TLV and sent by an MIP adjacent to the target MEP; wherein the first TLV includes: presetting a VLAN state identifier and first VLAN deployment information.

Destination MEP 13 further includes: a third processing module 1304, configured to change the preset VLAN status identifier in the first TLV according to the fifth VLAN status information, and generate a fifth TLV; and generating an LTR message carrying a fifth TLV.

The third sending module 1303 is specifically configured to send the LTR packet carrying the fifth TLV to the MIP adjacent to the destination MEP.

The target MEP provided by the embodiment of the invention receives a VLAN state acquisition request sent by a MIP adjacent to the target MEP; obtaining VLAN state information in a VLAN list maintained by a target MEP; and sending the obtained VLAN state information to MIPs adjacent to the target MEP. According to the technical scheme provided by the invention, the first VLAN state information can reflect the VLAN state of the initial MEP, and the second VLAN state information can reflect the VLAN states of the MIP and the target MEP, so that the initial MEP can determine the failed node and VLAN according to the first VLAN state information and the second VLAN state information, and the accurate positioning of the failed specific node and specific VLAN is realized.

In practical applications, the third receiving module 1301, the third obtaining module 1302, the third sending module 1303, and the third processing module 1304 can be implemented by a CPU, an MPU, a DSP, or an FPGA located in the target MEP.

Although the embodiments of the present invention have been described above, the present invention is not limited to the embodiments described above. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method of fault determination, comprising:

the initial maintenance end node MEP acquires VLAN state information in a VLAN list maintained by the initial maintenance end node MEP, and the acquired information is used as first VLAN state information;

sending a VLAN state acquisition request to a maintenance intermediate node MIP adjacent to the maintenance intermediate node MIP;

receiving second VLAN state information sent by the maintenance intermediate node MIP adjacent to the second VLAN state information; wherein the second VLAN state information includes: all MIPs and VLAN state information in a VLAN list maintained by a destination MEP;

2. The method of claim 1, wherein determining the failed node and VLAN based on the first VLAN status information and the second VLAN status information comprises:

3. The method according to claim 1, wherein before sending the VLAN status obtaining request to the maintenance intermediate node MIP adjacent to itself, the method further comprises: acquiring the number of VLAN sections in a VLAN list maintained by the VLAN, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section, and taking the acquired information as first VLAN deployment information;

sending a VLAN state acquisition request to a maintenance intermediate node MIP adjacent to the VLAN state acquisition request, wherein the VLAN state acquisition request comprises the following steps:

and sending the VLAN state acquisition request and the first VLAN deployment information to a maintenance intermediate node MIP adjacent to the VLAN state acquisition request.

4. The method of claim 3, wherein the VLAN status acquisition request is included in an LTM message; the sending the VLAN state acquisition request and the first VLAN deployment information to a maintenance intermediate node MIP adjacent to the maintenance intermediate node MIP comprises the following steps:

sending an LTM message carrying a first TLV to a maintenance intermediate node MIP adjacent to the LTM message; wherein the first TLV includes: presetting a VLAN state identifier and the first VLAN deployment information;

the starting maintenance end node MEP acquires VLAN state information in a VLAN list maintained by the starting maintenance end node MEP, and after the acquired information is used as first VLAN state information, the method further comprises the following steps:

receiving second VLAN state information sent by a maintenance intermediate node MIP adjacent to the second VLAN state information, wherein the second VLAN state information comprises:

receiving a link tracking response LTR message which is sent by a maintenance intermediate node MIP adjacent to the link tracking response LTR message and carries a second TLV; wherein the second TLV includes: VLAN state identifiers corresponding to the second VLAN state information, and the number of VLAN sections in a VLAN list maintained by all the maintenance intermediate nodes MIP and the target MEP, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section;

and determining the failed node and VLAN according to a preset VLAN state identifier, the first VLAN state identifier and the second VLAN state identifier.

5. The method of claim 4, wherein determining the failed node and VLAN based on a predetermined VLAN state identifier, the first VLAN state identifier and the second VLAN state identifier comprises:

6. A method of fault determination, comprising:

receiving fourth VLAN state information sent by the nodes adjacent to the fourth VLAN state information; wherein the fourth VLAN status information comprises: information of VLAN states in a VLAN list maintained by all nodes except the initial MEP and the initial MEP;

7. The method of claim 6, wherein receiving the VLAN status acquisition request sent by the originating MEP comprises:

sending the VLAN state acquisition request to the nodes adjacent to the VLAN state acquisition request, wherein the VLAN state acquisition request comprises the following steps:

8. The method of claim 7, wherein the VLAN status acquisition request is included in an LTM message; receiving a VLAN status acquisition request and first VLAN deployment information sent by the starting MEP, including:

generating an LTR message carrying the third TLV;

sending the VLAN status acquisition request and the first VLAN deployment information to the node adjacent to itself, including:

receiving the information of the fourth VLAN state sent by the node adjacent to the node, including:

receiving the LTR message carrying the fourth TLV and sent by the node adjacent to the LTR message receiving node; wherein the fourth TLV includes: a VLAN state identifier corresponding to the fourth VLAN state information, and the number of VLAN sections in a VLAN list maintained by all nodes except the initial MEP and the VLAN, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section;

sending the third VLAN status information and the fourth VLAN status information as second VLAN status information to the originating MEP, including:

9. A method of fault determination, comprising:

sending the fifth VLAN state information to the MIP adjacent to the fifth VLAN state information;

generating an LTR message carrying the fifth TLV;

sending the fifth VLAN status information to the MIP adjacent to the fifth VLAN status information, including:

10. The method according to claim 9, wherein the receiving, by the destination MEP, the VLAN status obtaining request sent by the MIP adjacent to the destination MEP includes:

the target MEP receives the VLAN state acquisition request and first VLAN deployment information sent by the MIP adjacent to the target MEP; wherein the first VLAN deployment information comprises: the number of VLAN sections in a VLAN list maintained by the initial MEP, the number of VLANs in each VLAN section and the VLAN initial value of each VLAN section;

11. An initial maintenance end node, comprising:

a first receiving module, configured to receive second VLAN status information sent by an MIP adjacent to the starting MEP; wherein the second VLAN state information includes: all MIPs and VLAN state information in a VLAN list maintained by a destination MEP;

12. A maintenance intermediate node adjacent to an initial maintenance end node, comprising:

the second receiving module is further configured to receive fourth VLAN status information sent by the node that is not adjacent to the starting MEP; wherein the fourth VLAN status information comprises: information of VLAN states in a VLAN list maintained by all nodes except the initial MEP and the initial MEP;

13. A destination maintenance end node, comprising:

a third sending module, configured to send the fifth VLAN status information to the MIP adjacent to the third sending module;

generating an LTR message carrying the fifth TLV;