CN108282383B

CN108282383B - Method and equipment for realizing fault processing

Info

Publication number: CN108282383B
Application number: CN201711366116.7A
Authority: CN
Inventors: 彭泽; 张强; 龚红艳
Original assignee: Raisecom Technology Co Ltd
Current assignee: Raisecom Technology Co Ltd
Priority date: 2017-12-18
Filing date: 2017-12-18
Publication date: 2020-09-18
Anticipated expiration: 2037-12-18
Also published as: CN108282383A

Abstract

A method and equipment for realizing fault processing comprise the following steps: setting a forwarding port for receiving and transmitting a Connectivity Fault Management (CFM) message on a switching chip; the forwarding port is bound with a Maintenance End Point (MEP) which is created in advance on a user side interface (UNI); carrying out fault judgment processing through the set forwarding port; wherein, the CFM message comprises a CCM message. When the switching chip does not support the hardware inward maintenance end point, the embodiment of the invention realizes the fault processing through the hardware and simplifies the complexity of the system fault processing.

Description

Method and equipment for realizing fault processing

Technical Field

The present disclosure relates to, but not limited to, communications technologies, and in particular, to a method and apparatus for performing fault handling.

Background

Connectivity Fault Management (CFM) is a two-layer (data link layer) link, end-to-end, Virtual Local Area Network (VLAN) based Operation, Administration and Maintenance (OAM) mechanism defined by the Institute of Electrical and Electronics Engineers (IEEE) 802.1ag, supporting the OAM standard defined by the international telecommunication union telecommunication standardization organization (ITU-T) primarily for detecting link Connectivity, confirming faults, and determining the location of faults occurring in a two-layer network. For the sake of sufficient clarity of the related art, the following description is made on the definition of the CFM message:

maintenance Domain (MD, Maintenance Domain): MD designates the network covered by connectivity error Detection (CFD), whose boundaries are defined by a series of maintenance endpoints configured on the device ports, the maintenance domains being identified by maintenance domain names;

maintenance Association (MA, Maintenance Association): an MA is a collection of maintenance points in a maintenance domain. Maintenance associations are identified as "maintenance domain name + maintenance association name". The MA indicates the VLAN to be served, the message sent by the maintenance point in the MA is provided with the VLAN label, meanwhile, the maintenance point in the MA can receive the messages sent by other maintenance points in the MA, and each MA corresponds to a Service Instance (Service Instance);

maintenance Point (MP, maintanence Point): configured on a device port, belonging to a certain MA. The maintenance points can be divided into two types: MEP and Maintenance Intermediate Point (MIP);

maintenance End Point (MEP, Maintenance association End Point): the MEP is configured on a device port, belongs to a certain MA, and is identified by an integer called MEP identification (MEP id). The MEP determines the scope and boundaries of the maintenance domain. And the maintenance association and maintenance domain to which the MEP belongs determines the VLAN attribute and the level of the message sent by the MEP. The maintenance end points have directivity and are divided into an outward maintenance end point (DOWN MEP) and an inward maintenance end point (UP MEP). The direction of the MEP indicates the location of the maintenance domain relative to the port; wherein, the outward MEP (down MEP) is used for receiving and transmitting the CFM protocol message at the port where the outward MEP is located, and the inward MEP (up MEP) is used for receiving and transmitting the CFM protocol message at other ports except the port where the inward MEP is located in the same VLAN on the device;

a Connectivity Check Message (CCM) is the most important one of the CFM messages, and a detection end periodically sends a CCM Message to notify the Connectivity of an opposite-end link;

a Local Breakout Message (LBM) is a CFM used to verify the bidirectional connectivity between a Local Maintenance End Point (Local MEP) and a peer Maintenance Intermediate Point (MIP) or an opposite End MEP, and is divided into a unicast LoopBack and a multicast LoopBack;

a connectivity fault isolation Message (LTM, LinkTrace Message) is used by the CFM to confirm a specific location where a connectivity path fault occurs;

communication Check Interval (CCI): the maintenance endpoint sends the time interval in the CCM.

The CFM message is a two-layer Ethernet packet, and the type of a two-layer protocol is 0x 8902; on the switching chip of the receiving end, a message with an ethernet protocol type of 0x8902 is received, and then the message is subjected to a CFM message processing flow. Since CFM supports OAM standard defined by ITU-T, the Protocol Data Unit (PDU) content of CFM message adopts OAM Data format defined by ITU-T. The CFM messages are divided into DOWN CFM (DOWN Connectivity fault Management) messages and UP CFM (UP CFM) messages, the UP CFM messages are initiated and terminated at the UP MEP, and the DOWN CFM messages are initiated from the main control board and sent to the main control board of the opposite end node through the Network Node Interface (NNI) for termination.

In the related technology, when the switching chip in the network device supports the hardware UP MEP, the switching chip sends the UP MEP message without designating a forwarding port, and the UP MEP message is routed and forwarded on other ports of the same VLAN except the MEP-associated port. However, if the switch chip does not support the hardware UP MEP, the UP MEP message transmission can only be realized by using the software function of the Central Processing Unit (CPU), and this way will consume a lot of CPU resources when the CFM (e.g., CCM) message is periodically transmitted, and at the same time will increase the complexity of the system software processing, thereby becoming a problem to be solved in the CFM fault detection process.

Disclosure of Invention

The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

Embodiments of the present invention provide a method and an apparatus for implementing fault handling, which can implement fault handling through hardware when an exchange chip does not support a hardware inward maintenance endpoint, thereby simplifying complexity of system fault handling.

The embodiment of the invention provides a method for realizing fault processing, which comprises the following steps:

a forwarding port for receiving and transmitting a Connectivity Fault Management (CFM) message is arranged on a switching chip;

when receiving the CFM message forwarded by the switching chip where the forwarding port is located, the forwarding port in the working state sends the CFM message to a remote MEP in the same maintenance association MA according to a hardware forwarding table item;

when the forwarding port in a working state receives a CCM message sent by a remote MEP in the same MA, fault judgment processing is carried out according to whether the configuration information carried by the received CFM message is matched with the binding information of the MEP bound by the forwarding port;

the forwarding port is bound with a Maintenance End Point (MEP) which is pre-established on a user side interface (UNI); the CFM message comprises a CCM message; the switch chip does not support an inward maintenance end point UP MEP.

Optionally, the hardware forwarding table entry is set in the forwarding port.

Optionally, the forwarding port includes: and the network node interface NNI port of the switching chip.

Optionally, the binding between the forwarding port and the MEP pre-created on the user side interface UNI includes:

setting a hardware forwarding table item capable of acquiring the local MEP and the remote MEP through the forwarding port;

wherein the hardware forwarding table entry includes: configuration information of MEPs.

Optionally, when the CFM packet is a CCM packet, the performing fault determination processing according to whether the received configuration information carried by the CFM packet matches with the binding information of the MEP bound to the forwarding port includes:

when the configuration information carried by the CCM message and the binding information of the MEP bound by the forwarding port are judged to be matched and consistent, the CFM message is received, and a far-end receiving overtime state bit is cleared to determine that the message is normally received and sent;

setting a link fault code when the configuration information carried in the CCM message and the binding information of the MEP bound by the forwarding port are judged to be matched and inconsistent; periodically polling a fault register, and performing subsequent polling when judging that a link fault code in the fault register is the same as a previous query result; determining that a fault occurs when the link fault code in the fault register is judged to be different from the previous query result; and when the fault is determined, determining the fault type according to the inquired link fault code, and performing fault processing according to the determined fault type.

Optionally, when the CFM level included in the configuration information of the MEP is higher than the CFM level determined from the obtained CCM packet, the method further includes:

and flooding the CCM message to other ports except the locally associated port in the VLAN where the CCM message is located.

On the other hand, an embodiment of the present invention further provides a device for implementing fault handling, including: a setting unit and a processing unit; wherein the content of the first and second substances,

the setting unit is used for: a forwarding port for receiving and transmitting a Connectivity Fault Management (CFM) message is arranged on a switching chip;

the processing unit is used for: when receiving the CFM message forwarded by the switching chip where the forwarding port is located, the forwarding port in the working state sends the CFM message to a remote MEP in the same maintenance association MA according to a hardware forwarding table item; when the forwarding port in a working state receives a CCM message sent by a remote MEP in the same MA, fault judgment processing is carried out according to whether the configuration information carried by the received CFM message is matched with the binding information of the MEP bound by the forwarding port;

Optionally, the hardware forwarding table entry is set in the forwarding port.

Optionally, the setting unit is further configured to:

setting a hardware forwarding table item capable of acquiring a local MEP and a remote MEP through the forwarding port so as to bind the forwarding port with an MEP pre-established on a user side interface UNI;

Optionally, when the CFM packet is a CCM packet, the processing unit is configured to perform fault judgment processing according to whether the configuration information carried by the received CFM packet matches with the binding information of the MEP bound to the forwarding port, where the fault judgment processing includes:

Optionally, the apparatus further includes a flooding unit, configured to: and when the CFM grade contained in the configuration information of the MEP is higher than the CFM grade determined from the obtained CCM message, flooding the CCM message to other ports except the locally associated port in the VLAN where the CCM message is located.

Compared with the related art, the technical scheme of the application comprises the following steps: a forwarding port for receiving and transmitting a Connectivity Fault Management (CFM) message is arranged on a switching chip; the forwarding port is bound with a Maintenance End Point (MEP) which is pre-established on a user side interface (UNI); carrying out fault judgment processing through the set forwarding port; wherein, the CFM message comprises a CCM message. When the switching chip does not support the hardware inward maintenance end point, the embodiment of the invention realizes the fault processing through the hardware and simplifies the complexity of the system fault processing.

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 flow chart of a method for implementing fault handling in accordance with an embodiment of the present invention;

FIG. 2 is a block diagram of an apparatus for implementing fault handling according to an embodiment of the present invention;

FIG. 3 is a flowchart of a method of a first application example of the present invention;

FIG. 4 is a block diagram of a system for implementing fault handling according to a second exemplary application of the present invention;

FIG. 5 is a schematic topology diagram of a third exemplary system for implementing the present invention;

fig. 6 is a schematic diagram of another system topology according to a third exemplary application 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.

The steps illustrated in the flow charts of the figures may be performed in a computer system such as a set of computer-executable instructions. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here. Fig. 1 is a flowchart of a method for implementing fault handling according to an embodiment of the present invention, as shown in fig. 1, including:

step 101, setting a forwarding port for receiving and transmitting Connectivity Fault Management (CFM) messages on a switching chip;

the forwarding port is bound with a Maintenance End Point (MEP) which is pre-established on a user side interface (UNI) in the embodiment of the invention; the CFM message comprises a CCM message.

Optionally, the forwarding port in the embodiment of the present invention includes: and the network node interface NNI port of the switching chip.

Optionally, the binding between the forwarding port and the MEP pre-created on the user side interface UNI in the embodiment of the present invention includes:

And 102, performing fault judgment processing through the set forwarding port.

Optionally, the step 102 of performing the fault determination processing in the embodiment of the present invention includes:

when receiving the CFM message forwarded by the switching chip where the forwarding port is located, the forwarding port in the working state sends the CFM message to a remote end MEP (RMEP) in the same maintenance association MA according to a hardware forwarding table entry;

when the forwarding port in a working state receives a CCM message sent by an RMEP in the same MA, fault judgment processing is carried out according to whether the configuration information carried by the received CFM message is matched with the binding information of the MEP bound by the forwarding port.

Optionally, in the embodiment of the present invention, the hardware forwarding table entry is disposed at the forwarding port.

Optionally, when the CFM packet is a CCM packet, performing fault determination processing according to whether the configuration information carried by the received CFM packet matches with the binding information of the MEP bound to the forwarding port includes:

when the configuration information carried by the received CCM message is judged to be matched and consistent with the binding information of the MEP bound by the forwarding port, the receiving of the CFM message is ended, and a far-end receiving overtime state bit is cleared to determine that the message is normally received and sent;

Optionally, when the CFM level included in the configuration information of the MEP is higher than the CFM level determined from the obtained CCM packet, the method according to the embodiment of the present invention further includes:

Fig. 2 is a block diagram of a device for implementing fault handling according to an embodiment of the present invention, as shown in fig. 2, including: a setting unit and a processing unit; wherein the content of the first and second substances,

Optionally, the setting unit is further configured to:

Wherein, the forwarding port is bound with a maintenance end point MEP which is pre-established on a user side interface UNI; the CFM message comprises a CCM message;

the processing unit is used for: and carrying out fault judgment processing through the set forwarding port.

Optionally, the processing unit is specifically configured to:

Optionally, the hardware forwarding table entry is set in the forwarding port.

The following description of the embodiments of the present invention is made by way of application examples, which are only used to illustrate the present invention and are not intended to limit the scope of the present invention.

Application example 1

Fig. 3 is a flowchart of a method of a first application example of the present invention, as shown in fig. 3, including:

step 301, when a first forwarding port of a first device receives a connectivity fault management CFM message, determining a working state of the first forwarding port;

step 302, when the first device determines that the first forwarding port is in a sending state, forwarding the received CFM message to the second device according to the hardware forwarding table entry;

step 303, the second device determines whether the CFM packet received through the second forwarding port is a connectivity detection message CCM packet;

step 304, when the second device determines that the CFM message is a CCM message, performing fault processing according to whether the configuration information carried in the CCM message is consistent with the binding information of the second MEP bound to the second forwarding port;

wherein the first device and the second device are connected through a network node interface NNI;

a first Maintenance End Point (MEP) is pre-created on a user network side interface (UNI) of the first equipment, and a second MEP is pre-created on a UNI of the second equipment;

the first forwarding port is a forwarding port bound with the first MEP and used for receiving and transmitting a service message and a CFM message; and the second forwarding port is a forwarding port bound with the second MEP and used for receiving and transmitting a service message and a CFM message.

Optionally, the first MEP and the second MEP belong to the same maintenance domain and are associated with the same maintenance domain; the identity of the first MEP and the identity of the second MEP are uniquely determined in the same maintenance association.

Optionally, the first forwarding port is an NNI connected between the switch chip of the first device and the switch chip of the second device; the second forwarding port is an NNI connected to the switch chip of the second device and the switch chip of the first device.

Optionally, before the forwarding port is used for transceiving a service packet and a CFM packet, the method further includes:

when the forwarding port is configured to be in a sending state, forwarding the CFM message of the inward maintenance end point is carried out, and when the forwarding port is in a blocking state, forwarding the CFM message of the inward maintenance end point is not carried out.

Optionally, when the first device determines that the first forwarding port is in the blocking state, the method in the embodiment of the present invention further includes:

and the first equipment discards the received CFM message.

Optionally, the performing fault processing includes:

the second equipment analyzes the received CCM message and acquires the configuration information carried in the CCM message;

when the second device judges that the configuration information acquired from the CCM message is consistent with the configuration information of the second MEP, the second device finishes receiving the CCM message and clears a far-end receiving overtime state bit to determine that the message is normally received and transmitted;

when the second device judges that the configuration information acquired from the CCM message is inconsistent with the configuration information of the second MEP, setting a link fault code; the second equipment polls the fault register periodically, judges that the link fault code in the fault register is the same as the query result of the previous time, and polls the next time; determining that a fault occurs when the link fault code in the fault register is judged to be different from the previous query result; and when the fault is determined, the second equipment determines the fault type according to the inquired link fault code and carries out fault processing according to the determined fault type.

Optionally, when the CFM level included in the configuration information of the second MEP is higher than the CFM level determined from the obtained CCM packet, the method according to the embodiment of the present invention further includes:

and flooding the CCM message to other ports except the port locally associated with the second equipment in the same VLAN as the second equipment.

It should be noted that the locally associated port is an NNI that belongs to a maintenance association MA with a User Network Interface (UNI), which is not described herein again.

Optionally, when the second device determines that the received CFM packet is a non-CCM packet, the method in the embodiment of the present invention further includes:

determining the message type of the received CFM message;

and carrying out fault processing according to the determined message type of the CFM message.

Application example 2

Fig. 4 is a block diagram of a system for implementing fault handling according to a second exemplary application of the present invention, as shown in fig. 4, including: a first device and a second device; wherein the content of the first and second substances,

the first device comprises a first judgment unit and a forwarding unit; wherein the content of the first and second substances,

the first judging unit is used for: when a first forwarding port of first equipment of the first forwarding port receives a Connectivity Fault Management (CFM) message, judging the working state of the first forwarding port;

the forwarding unit is configured to: when the first forwarding port is judged to be in a sending state, forwarding the received CFM message to the second equipment according to the hardware forwarding table item;

the second device comprises a second judging unit and a processing unit; wherein the content of the first and second substances,

the second judgment unit is used for: judging whether the CFM message received through a second forwarding port of the second device belongs to the CFM message is a connectivity detection message CCM message;

the processing unit is used for: when the CFM message is judged to be a CCM message, fault processing is carried out according to whether the configuration information carried in the CCM message is consistent with the binding information of the second MEP bound by the second forwarding port;

The application example forwarding unit and the processing unit are respectively arranged on the first device and the second device; when the forwarding unit and the processing unit are both disposed on one side of the device, the forwarding unit can be integrated as a function of the processing unit.

Optionally, the first device in the embodiment of the present invention further includes a first configuration unit, configured to: when the first forwarding port is configured to be in a sending state, forwarding the CFM message of the inward maintenance end point, and when the first forwarding port is in a blocking state, not forwarding the CFM message of the inward maintenance end point;

optionally, the second device in the embodiment of the present invention further includes a second configuration unit, configured to: and when the second forwarding port is configured to be in a sending state, forwarding the CFM message of the inward maintenance end point, and when the second forwarding port is in a blocking state, not forwarding the CFM message of the inward maintenance end point.

Optionally, the first device further includes a discarding unit, configured to: and when the first forwarding port of the first device is judged to be in a blocking state, discarding the received CFM message.

Optionally, the processing unit in the embodiment of the present invention is specifically configured to: analyzing the received CCM message to acquire configuration information carried in the CCM message;

when the configuration information acquired from the CCM message is judged to be consistent with the configuration information of the second MEP, the CCM message is received, and a remote receiving overtime state bit is cleared to determine that the message is normally received and transmitted;

setting a link fault code when the configuration information acquired from the CCM message is judged to be inconsistent with the configuration information of the second MEP; periodically polling a fault register, and performing subsequent polling when judging that a link fault code in the fault register is the same as a previous query result; determining that a fault occurs when the link fault code in the fault register is judged to be different from the previous query result; and when the fault is determined, determining the fault type according to the inquired link fault code, and performing fault processing according to the determined fault type.

Optionally, the second device in the embodiment of the present invention further includes a flooding unit, configured to: and when the CFM level contained in the configuration information of the second MEP is higher than the CFM level determined from the obtained CCM message, flooding the CCM message to other ports except the port locally associated with the second device in the same VLAN as the second device.

Optionally, the processing unit in the embodiment of the present invention is further configured to: determining the message type of the received CFM message when the received CFM message is judged to be a non-CCM message; and carrying out fault processing according to the determined message type of the CFM message.

The first and second embodiments of the present invention are merely relative.

Application example 3

Fig. 5 is a schematic topology diagram of a third exemplary application system of the present invention, and as shown in fig. 5, a first device and a second device are directly connected through a Network Node Interface (NNI) and perform CFM packet transceiving through an NNI port, where the NNI is an uplink port or a link aggregation port of the device, a first MEP (having an identity MEP ID1 of the first MEP) is created on a UNI on the first device, and a second MEP (having an identity MEP ID2 of the second MEP) is created on a UNI on the second device; the first MEP and the second MEP belong to the same designated maintenance domain MD and the same maintenance association MA, and the identification MEP ID1 of the first MEP and the identification MEP ID2 of the second MEP are uniquely determined in the same maintenance association MA;

in the system shown in fig. 5, for a first installation, the first MEP is a local MEP (lmep) and the second MEP is a remote MEP (rmep); correspondingly, for the second plant, the second MEP is a local MEP (lmep), and the first MEP is an RMEP.

The method for processing the fault according to the embodiment of the present invention is described below by taking an example in which a first device sends a CFM message and a second device receives the CFM message, and includes:

setting two NNIs connected on a switching chip of first equipment and a switching chip of second equipment as a first forwarding port and a second forwarding port respectively, wherein the first forwarding port on the first equipment is bound with a first MEP, the second forwarding port on the second equipment is bound with a second MEP, the CFM message forwarding of the UPMEP is carried out when the first forwarding port and the second forwarding port are in a forwarding state, and the CFM message forwarding is forbidden when the first forwarding port and the second forwarding port are in a blocking (block) state;

setting NNIs on the first equipment and the second equipment as MEP (maintenance association network interfaces) associated ports which belong to a maintenance association MA together with a User Network Interface (UNI); the first forwarding port and the second forwarding port are transmitting and receiving ports of CFM messages under the same maintenance association MA;

setting MEP associated ports (UNIs on first equipment and second equipment) and first forwarding ports and second forwarding ports as the same service virtual local area network which belongs to the current CFM and needs to be monitored;

with regard to the above settings, the present application example will be briefly explained:

1. the binding of the first forwarding port and the first MEP means: the hardware table entry information of the local MEP and the remote MEP can be obtained at the first forwarding port, and the hardware table entry information of the MEP may include configuration information, and may include part or all of the following: CFM message grade, MD name, MA name, packet sending period, first and second MEP identity, first forwarding port physical state and logic state; the application example acquires the hardware table item information, which indicates that the application does not limit the storage position of the hardware table item information; optionally, in the embodiment of the present invention, after the hardware table entry information is sent to the first forwarding port, the hardware table entry information is stored in the first forwarding port, so as to accelerate the information reading speed;

2. in the application example, the configuration information related to the local MEP of the first device and the second device may also be recorded in the switch chip register of the device, so that the switch chip may automatically send and analyze the CFM message according to the configuration information;

3. in this application example, in one MA, when one LMEP may correspond to multiple RMEPs, and one LMEP may correspond to multiple RMEPs, taking the first device as an LMEP as an example, the binding information of the first forwarding port includes configuration information of all the RMEPs.

Based on the above setting, the fault processing method of the embodiment of the invention comprises the following steps:

firstly, after a first forwarding port bound with a first MEP on a first device receives a CFM message, judging the working state of the first forwarding port bound with the first MEP, and if the first forwarding port bound with the first MEP is in a block state, discarding the received CFM message; if the first forwarding port bound by the first MEP is in a forward state, analyzing the received CFM message, and forwarding the CFM message to a second device (a second MEP) according to a hardware forwarding table item obtained by analysis;

optionally, in this embodiment of the present invention, the CFM packet may include: connectivity Check Message (CCM), and Message types such as a two-layer ethernet packet (e.g., Link Trace Message (LTM) and Loopback Message (LBM)) with a two-layer protocol type of 0x8902 except the CCM; wherein the content of the first and second substances,

the CCM is formed by encapsulating a switch chip in the first device according to a predetermined sending period and according to configuration information and protocol requirements preset by the MA and the first MEP, and then sending the encapsulated result to the first forwarding port, where a specific encapsulation process may be encapsulation conventionally used by those skilled in the art, and is not described herein again;

except CCM, other two-layer protocol type 0x8902 two-layer Ethernet packets (such as LBM, LTM and the like) are sent to a first forwarding port after being encapsulated according to the protocol when the CPU in the first device determines that the current configuration information is correct; the current configuration information includes: the MD name, the MA name, the associated service VLAN, the LMEP, and the physical state and the logic state of the first forwarding port;

then, after a second forwarding port bound with a second MEP on the second device receives the CFM message, judging the type of the received CFM message; if the received CFM message is a CCM message, executing branch one; if the received CFM message is a non-CCM, other unicast two-layer protocol type is a two-layer Ethernet message (for example, an LBM message) of 0x8902, executing branch two; if the received CFM message is a non-CCM two-layer Ethernet packet (for example, LTM message) with the type of other multicast two-layer protocol being 0x8902, directly forwarding the CFM message to a CPU, and then executing branch three;

in this step, each message type may be determined by information carried in a preset field (e.g., field selection code) in the CFM message, and whether the message is a multicast message or a unicast message may be determined by a destination address of the CFM message;

the branch one comprises:

the exchange chip on the second device analyzes the received CCM message and acquires the configuration information carried in the CCM message; the configuration information may include: CFM message grade, MD name, MA name, packet sending period, first and second MEP ID, NNI port physical state and logic state information on the first device, judging whether the obtained configuration information is consistent with the second MEP binding information of the second forwarding port currently receiving CCM message (namely: the configuration information of the first MEP and the second MEP), if the obtained configuration information is completely consistent with the second MEP binding information of the second forwarding port currently receiving CCM message, terminating the received CCM message, clearing the far-end receiving overtime state bit in the switching chip fault register to indicate normal receiving and sending;

if the obtained configuration information is inconsistent with the binding information of a second MEP bound by a second forwarding port currently receiving the CCM message, setting a corresponding link fault code in a fault register of the switching chip;

in this step, the fault register of the switch chip saves the link connection fault code in real time, and the link connection fault code is the value saved in the fault register; specific examples may be known to those of ordinary skill in the art: the exchange chip stores the state identification of the determined link fault, and the identification bit corresponding to the set state is set every time; it should be noted that, when the CFM level information is higher than the CFM level information acquired by the current forwarding port, the method in the embodiment of the present invention further includes: and flooding CCM messages to other local ports of the same VLAN except the associated port UNI.

The CPU in the second device polls the fault register periodically and judges whether the link fault code in the fault register is the same as the previous query result; if the link fault code in the fault register is the same as the previous query result, the processing is not performed for the moment, and the next query is continuously waited; if the link fault code in the fault register is different from the previous query result, sending a message to inform the CPU of generating a fault;

the CPU determines the fault type according to the current link fault code value so as to process the fault; the fault processing comprises the following steps: and informing the user of fault generation or fault recovery so as to execute a corresponding fault processing flow or fault recovery flow.

In the step, the fault processing flow and the fault recovery flow can be implemented by methods familiar to those skilled in the art;

the fault processing flow of the embodiment of the invention can comprise the following steps:

judging whether a valid static far-end MEP (RMEP) exists or not, and if not, not performing any processing operation; if an effective static far-end MEP exists, the CPU polls the far-end MEP (RMEP), directly processes corresponding faults for the faults belonging to the far-end MEP, and needs to poll all RMEPs belonging to the current LMEP for the faults belonging to the far-end MEP, and performs OR operation for the same type of faults, if the operation result value is 1, the faults exist; if the fault is reported and not recovered, the fault is not processed; if the fault occurs for the first time, notifying a user; if the operation value is 0, a fail-over operation needs to be performed.

The fault recovery process of the embodiment of the invention can comprise the following steps:

judging whether a valid static far-end MEP (rmep) exists, and if the valid static far-end MEP does not exist, directly recovering all faults belonging to the far-end MA, namely: clearing the faults recorded in the remote MEP in the current fault register, and informing the user that all the faults under the current MA are completely recovered; if the effective static far-end MEP exists, the CPU polls the effective static far-end MEP (RMEP), inquires a link connection fault code value in a fault register of a switching chip and carries out recovery operation on the fault belonging to the far-end MA; specifically, for all RMEPs belonging to an LMEP to be polled for faults belonging to a remote MEP, fault recovery is considered complete when the faults of all RMEPs are recovered.

In the above determination process, it is determined whether there is an effective static far-end MEP, which may be the first MEP, by querying the binding information of the forwarding port through the CPU.

In the above steps, if the CPU polls that the current failure code value is null or invalid, it indicates that there is no failure in the current link, that is: and (4) generating no fault or completely recovering the existing fault, and continuously executing the fault recovery processing flow.

The second branch comprises: the switching chip judges whether the destination MAC address of the received two-layer Ethernet message with the two-layer protocol type of 0x8902 except CCM is a local MAC address, and if the destination MAC address of the received two-layer Ethernet message with the two-layer protocol type of 0x8902 except CCM is the local MAC address, the two-layer Ethernet message is sent to a local CPU; and the local CPU judges that the received two-layer Ethernet message is a packet receiving port from a local forwarding port, judges that the binding information of the forwarding port does not have MEP configuration information carried in the message, and directly forwards the message to an MEP associated port for processing and terminating processing. If the destination MAC address of the received two-layer Ethernet message with the two-layer protocol type of 0x8902 except CCM is not the local MAC address, discarding the message;

the branch three includes: and judging that the binding information of the second forwarding port does not have MEP configuration information carried by the CFM message, and forwarding the CFM message to a processing flow of an associated port of the second MEP from a processing flow of the forwarding port for subsequent processing. Optionally, when the CFM message is successfully matched, the final message is subjected to subsequent message processing; if the CFM message fails to be matched, judging whether the CFM grade carried by the CFM message is greater than the configuration grade of the MD to which the MEP belongs; if the configuration level of the MD is larger than that of the MEP, the multicast message is continuously forwarded at the MEP related port, and if the configuration level of the MD is smaller than or equal to that of the MEP, the multicast message is discarded; wherein the matching information includes: CFM level, MA name, associated VLAN, etc.

In the above application example, for an LMEP, the configuration information of an RMEP stored in the switch chip register is updated when the associated RMEP changes.

It should be noted that the method is implemented when the first MEP, the second MEP, the first forwarding port, and the second forwarding port all enable the CFM function, and how the ports enable the CFM function is known to those skilled in the art and is not described herein again.

In the above embodiment, the hardware forwarding table entry information of the MEP can be directly obtained only after the first forwarding port is bound to the first MEP, and before the first forwarding port is not bound, the configuration information of each equipment MEP is recorded only in the equipment software. If the state of the associated port UNI of the current local MEP is known to change, the application example may update configuration information stored in the local software, and update hardware entry information of the local MEP.

In order to support link protection, in the present application example, two first forwarding ports may be set on the device, but only one first forwarding port serves as a currently working port, and the operations in the above embodiments are executed, and the other port does not participate in executing the operations, but may also obtain hardware table information, so that the message forwarding is performed in time after the protection link switching occurs; fig. 6 is a schematic diagram of another system topology according to a third exemplary application of the present invention, and as shown in fig. 6, NNIs 1 and 2 are first forwarding ports for forwarding two messages associated with an MA; the NNI1 port direct-connection link is a main link, and the NNI2 port direct-connection link is a standby link; under normal conditions, the main link is a forwarding link, the standby link is a blocking link, the configuration is carried out based on the method in the embodiment, the message forwarding is carried out through the main link, and when the disconnection fault occurs in the main link, the link is switched to the standby link.

In the application example, the first forwarding port is arranged on the switch chip, so that the first forwarding port is bound with the first MEP, the first forwarding port can acquire the hardware forwarding table item information, and the CFM message is received and transmitted under the condition that the switch chip hardware does not support the UP MEP, thereby reducing the consumption requirement of CPU resources and the software processing complexity.

It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by a program instructing associated hardware (e.g., a processor) to perform the steps, and the program may be stored in a computer readable storage medium, such as a read only memory, a magnetic or optical disk, and the like. Alternatively, all or part of the steps of the above embodiments may be implemented using one or more integrated circuits. Accordingly, each module/unit in the above embodiments may be implemented in hardware, for example, by an integrated circuit to implement its corresponding function, or in software, for example, by a processor executing a program/instruction stored in a memory to implement its corresponding function. The present invention is not limited to any specific form of combination of hardware and software.

Although the embodiments of the present invention have been described above, the above description is only for the convenience of understanding the present invention, and is not intended to limit the present invention. 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 for implementing fault handling,

2. The method of claim 1, wherein the hardware forwarding entry is located on the forwarding port.

3. The method of claim 1 or 2, wherein the forwarding port comprises: and the network node interface NNI port of the switching chip.

4. The method according to claim 1 or 2, wherein the binding of the forwarding port with the pre-created MEP on the user side interface UNI comprises:

5. The method according to claim 1 or 2, wherein when the CFM packet is a CCM packet, the performing fault determination processing according to whether the configuration information carried by the received CFM packet matches with the binding information of the MEP bound to the forwarding port includes:

6. The method according to claim 5, wherein when the CFM level included in the configuration information of the MEP is higher than the CFM level determined from the obtained CCM message, the method further comprises:

7. An apparatus for implementing fault handling, comprising: a setting unit and a processing unit; wherein the content of the first and second substances,

the forwarding port is bound with a Maintenance End Point (MEP) which is pre-established on a user side interface (UNI); the CFM message comprises a CCM message.

8. The apparatus of claim 7, wherein the hardware forwarding entry is located on the forwarding port.

9. The apparatus of claim 7 or 8, wherein the forwarding port comprises: and the network node interface NNI port of the switching chip.

10. The apparatus according to claim 7 or 8, wherein the setting unit is further configured to:

11. The device according to claim 7 or 8, wherein, when the CFM packet is a CCM packet, the processing unit is configured to perform the fault determination processing according to whether the configuration information carried by the received CFM packet matches with the binding information of the MEP bound to the forwarding port, including:

12. The apparatus of claim 11, further comprising a flooding unit configured to: and when the CFM grade contained in the configuration information of the MEP is higher than the CFM grade determined from the obtained CCM message, flooding the CCM message to other ports except the locally associated port in the VLAN where the CCM message is located.