CN103684887B

CN103684887B - A kind of method and apparatus connecting the generation of error detection group network system hardware table item

Info

Publication number: CN103684887B
Application number: CN201310755355.7A
Authority: CN
Inventors: 李磊方
Original assignee: Hangzhou H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2013-12-31
Filing date: 2013-12-31
Publication date: 2017-01-04
Anticipated expiration: 2033-12-31
Also published as: CN103684887A

Abstract

The invention discloses a kind of method connecting the generation of error detection group network system hardware table item, the method is applied to first equipment to be added in described connection error detection CFD networking with hardware detection ability, the method includes: described first equipment sends link trace LTM multicast address message to the member device in described CFD networking, described LTM multicast address message carries the rank safeguarding end points MEP and the MEP ID value of described first equipment, purpose MAC in PDU field is multicast MAC, and the source MAC in PDU field is the bridge MAC of described first equipment；Described first equipment receives the LTM unicast address message or link trace response LTR message that in described CFD networking, member device sends, setting up the hardware table item of each member device MEP ID in corresponding described CFD networking respectively, arranging with the neighborhood of corresponding member device is normal.

Description

Method and equipment for generating hardware table entry of connectivity error detection networking system

Technical Field

The invention relates to a network communication transmission technology, in particular to a method and equipment for generating a hardware table entry of a connectivity error detection networking system.

Background

CFD (Connectivity Fault Detection) is an end-to-end OAM (Operations, Administration, and Maintenance) mechanism based on VLAN in a two-layer network, and is mainly used for detecting link Connectivity in the two-layer network, and confirming and locating a Fault when the Fault occurs.

MD (Maintenance Domain) refers to a network or a part of a network covered by CFD. In order to accurately locate the failure point, a concept of level (hierarchy) is introduced in MD. The MD is divided into eight grades and is represented by integers 0-7, and the larger the number is, the higher the grade is, the larger the range of the MD is. Different MD can be adjacent or nested but can not be crossed, and the nesting can be only from high-level MD to low-level MD

Fig. 1 is a schematic diagram of a typical CFD networking, in which a maintenance domain MD _ a in a solid line box and a maintenance domain MD _ B in a dashed line box are nested, and the maintenance domain MD _ a is higher in level than the maintenance domain MD _ B. If the link is found to be not through on the boundary of the MD _ A domain, the failure of the Device inside the MD _ A domain is indicated, and the failure may occur on five devices, namely the devices A to E. At this time, if the link is found to be not through at the boundary of the MD _ B domain, the possible range of the failure point is narrowed to three devices, i.e., Device B to Device D, and if the devices in the MD _ B domain are working properly, it can be determined that at least Device C is not failed.

Devices a to E are 5 devices in the CFD networking, white boxes on the devices are MEPs (Maintenance End points), CCMs (Continuity Check Message connection detection messages) are periodically sent through the MEPs to obtain far-End MEP information, and the sending period of the messages is 7 levels, as shown in table 1.

TABLE 1

Value of time interval field in CCM message	Sending interval of CCM message	Timeout of remote MEP
			1	10/3 ms	35/3 ms
2	10 milliseconds	35 milliseconds
			3	100 milliseconds	350 milliseconds
4	1 second	3.5 seconds
			5	10 seconds	35 seconds
6	60 seconds	210 seconds
			7	600 seconds	2100 seconds

When a CCM sending period specified by a protocol is 10/3 milliseconds (the level of the CCM message sending period is 1) in a high-reliability network environment, that is, 300 CCM messages are sent per second, which needs the support of a hardware chip, so that devices can be divided into two types according to the capability of the devices to send the CCM messages: a device with hardware detection capability (the device can send a CCM message of level 1), a device without hardware detection capability (the device cannot send a CCM message of level 1, and can only send a CCM message of level 2 or below level 2).

The equipment with hardware detection capability needs to set the information of the remote neighbor in advance due to the limitation of a chip; namely, the designated remote MEP list is issued to the hardware, and then the hardware resource corresponding to the remote MEP list is provided. There are two general implementations:

1. all MEP lists that a service instance can contain are issued to the hardware.

2. A partial MEP in a service instance is selected and then manually issued by the user.

The implementation mode 1 has the disadvantages that no selection is made, the actual use number is not considered, a plurality of hardware table entries are issued by default, a large amount of hardware resources are occupied, the waste of the hardware resources is caused, and the number of service instances which can be supported by the equipment is limited.

The implementation mode 2 is not flexible enough, and the detection list needs to be manually specified again when the network capacity is expanded; in addition, the specified list cannot be matched with the number of MEPs actually used until the list is unchanged, and thus, certain hardware resources are wasted.

Disclosure of Invention

In view of this, the present invention provides a method and a device for generating a hardware table entry of a connectivity error detection networking system, where a device to be added with a hardware detection capability receives a Link tracking unicast address Message (LTM) or a Link tracking response Message (LTR, Link Trace Reply) sent by a CFD networking member device, extracts MEP (Maintenance end Point) information of the CFD networking member device carried in the LTM unicast address Message or the LTR Message, and creates a hardware table entry corresponding to the CFD networking member device MEP, thereby avoiding a phenomenon that all MEP lists that can be included in a service instance are issued to cause a useless MEP resource occupation. The technical scheme provided by the invention is as follows:

a method for generating a hardware table entry of a connectivity error detection networking system is applied to a first device to be added with hardware detection capability in a connectivity error detection CFD networking, and comprises the following steps:

the first device sends a Link Tracking (LTM) multicast address message to member devices in the CFD networking, wherein the LTM multicast address message carries the level of a Maintenance Endpoint (MEP) and an MEP ID value of the first device, a destination MAC in a Protocol Data Unit (PDU) field of the LTM multicast address message is a multicast MAC, and a source MAC in the PDU field is a bridge MAC of the first device;

the first device receives an LTM unicast address message or a link tracking response LTR message sent by member devices in the CFD networking, respectively establishes hardware table entries corresponding to MEP IDs of the member devices in the CFD networking, and sets neighbor relations with the corresponding member devices as normal; wherein,

the LTM unicast address message is sent after a member device with hardware detection capability in the CFD networking establishes a hardware table entry corresponding to an MEP ID of the first device according to the LTM multicast address message sent by the first device and sets a neighbor relation with the first device as normal, a destination MAC in a PDU field of the LTM unicast address message is a bridge MAC of the first device, and the LTM unicast address message carries the MEP ID of the member device with hardware detection capability in the CFD networking sending the LTM unicast address message;

the LTR message is sent by the member device without hardware detection capability in the CFD networking according to the LTM multicast address message sent by the first device, and the LTR message carries the MEP ID of the member device without hardware detection capability in the CFD networking sending the LTR message.

In the above scheme, the method further comprises:

after receiving the LTM unicast address message or the LTR message sent by the member equipment in the CFD networking, the first equipment judges whether a hardware list item corresponding to each member equipment MEP ID in the CFD networking is established or not, if so, the first equipment replies the LTR message to the member equipment sending the LTM unicast address message in the CFD networking, if not, the first equipment establishes the hardware list item corresponding to the member equipment MEP ID in the CFD networking and replies the LTR message to the member equipment sending the LTM unicast address message in the CFD networking, wherein the LTR message does not carry the MEP ID of the first equipment.

A method for generating a hardware table entry of a connectivity error detection networking system is applied to a first device to be added in the connectivity error detection CFD networking, which does not have hardware detection capability, and comprises the following steps:

the first device receives an LTM unicast address message or a link tracking response LTR message sent by member devices in the CFD networking; wherein,

In the above scheme, the method further comprises:

after the first device receives the LTM unicast address message sent by the member device in the CFD networking, the first device replies the LTR message to the member device sending the LTM unicast address message in the CFD networking, and the LTR message does not carry the MEP ID of the first device.

A method for generating a hardware table entry of a connectivity error detection networking system is applied to member equipment with hardware detection capability in the connectivity error detection CFD networking, and first equipment is equipment to be added in the CFD networking, and the method comprises the following steps:

the member equipment receives a Link Tracking (LTM) multicast address message sent by the first equipment, wherein the LTM multicast address message carries the Maintenance End Point (MEP) level and the MEP ID value of the first equipment, a destination MAC in a Protocol Data Unit (PDU) field of the LTM multicast address message is a multicast MAC, and a source MAC in the PDU field is a bridge MAC of the first equipment;

the member equipment establishes a hardware table entry corresponding to the MEP ID of the first equipment, and sets a neighbor relation with the first equipment as normal;

the member device sends an LTM unicast address message to the first device, so as to establish a hardware table entry corresponding to the MEP ID of the member device when the first device has hardware detection capability, a destination MAC in a PDU field of the LTM unicast address message is a bridge MAC of the first device, and the LTM unicast address message carries the MEP ID of the member device.

In the above scheme, the method further comprises:

and after receiving the LTM multicast address message sent by the first equipment, the member equipment judges whether a hardware table entry corresponding to the MEP ID of the first equipment is established, if so, sends an LTM unicast address message to the first equipment, otherwise, establishes a hardware table entry corresponding to the MEP ID of the first equipment, and sends an LTM unicast address message to the first equipment.

A method for generating a hardware table entry of a connectivity error detection networking system is applied to member equipment without hardware detection capability in a connectivity error detection CFD networking, and first equipment is equipment to be added in the CFD networking, and the method comprises the following steps:

and the member equipment replies an LTR message to the first equipment so as to establish a hardware table entry corresponding to the MEP ID of the member equipment when the first equipment has hardware detection capability, wherein the LTR message carries the MEP ID of the member equipment.

An apparatus to be joined with hardware detection capability in a connectivity error detection, CFD, networking, comprising:

a message sending module, configured to send a link tracking LTM multicast address message to member devices in the CFD networking, where the LTM multicast address message carries a maintenance endpoint MEP level and an MEP ID value of the device, a destination MAC in a PDU field of a protocol data unit PDU of the LTM multicast address message is a multicast MAC, and a source MAC in the PDU field is a bridge MAC of the device;

a message receiving module, configured to receive an LTM unicast address message or a link tracking response LTR message sent by a member device in the CFD networking, where,

the LTM unicast address message is sent after a member device with hardware detection capability in the CFD networking establishes a hardware table entry corresponding to an MEP ID of the device according to the LTM multicast address message sent by the device and sets a neighbor relation with the device as normal, a destination MAC in a PDU field of the LTM unicast address message is a bridge MAC of the device, and the LTM unicast address message carries the MEP ID of the member device with hardware detection capability in the CFD networking sending the LTM unicast address message;

the LTR message is sent by member equipment without hardware detection capability in the CFD networking according to an LTM multicast address message sent by the equipment, and the LTR message carries the MEP ID of the member equipment without hardware detection capability in the CFD networking sending the LTR message;

and the table item creating module is used for respectively creating hardware table items corresponding to MEP IDs of all member devices in the CFD networking, and setting the neighbor relation of the corresponding member devices as normal.

In the above scheme, the apparatus further comprises:

a judging module, configured to judge, after the first device receives an LTM unicast address packet or an LTR packet sent by a member device in the CFD networking, whether a hardware entry corresponding to an MEP ID of each member device in the CFD networking has been created, if not, instruct the entry creating module to create a corresponding hardware entry, and set a neighbor relationship with the corresponding member device as normal;

the message sending module is further configured to send an LTR message to the member device in the CFD networking, which sends the LTR unicast address message, if the message receiving module receives the LTM unicast address message sent by the member device in the CFD networking, where the LTR message does not carry the MEP ID of the first device.

An apparatus to be joined in a connectivity error detection, CFD, networking without hardware detection capability, comprising:

a message receiving module, configured to receive an LTM unicast address message or a link tracking response LTR message sent by a member device in the CFD networking; wherein,

the LTM unicast address message is sent after a member device with hardware detection capability in the CFD networking establishes a hardware table entry corresponding to the MEP ID of the device according to the LTM multicast address message sent by the message sending module and sets the neighbor relation with the device as normal, a destination MAC in a PDU field of the LTM unicast address message is a bridge MAC of the device, and the LTM unicast address message carries the MEP ID of the member device with hardware detection capability in the CFD networking sending the LTM unicast address message;

the LTR message is sent by the member device without hardware detection capability in the CFD networking according to the LTM multicast address message sent by the message sending module, and the LTR message carries the MEP ID of the member device without hardware detection capability in the CFD networking that sends the LTR message.

In the above solution, if the message receiving module receives the LTM unicast address message sent by the member device in the CFD networking,

the message sending module is further configured to send an LTR message to the member device in the CFD networking that sends an LTM unicast address message, where the LTR message does not carry the MEP ID of the first device.

A device is a member device with hardware detection capability for a Connectivity Fault Detection (CFD) networking, a first device is a device to be added in the CFD networking, and the device comprises:

a message receiving module, configured to receive a link tracking LTM multicast address message sent by the first device, where the LTM multicast address message carries a maintenance endpoint MEP level and an MEP ID value of the first device, a destination MAC in a protocol data unit PDU field of the LTM multicast address message is a multicast MAC, and a source MAC in the PDU field is a bridge MAC of the first device;

the table item creating module is used for creating a hardware table item corresponding to the MEP ID of the first equipment and setting the neighbor relation of the first equipment as normal;

a message sending module, configured to send an LTM unicast address message to the first device, so as to establish a hardware table entry corresponding to an MEP ID of the device when the first device has a hardware detection capability, where a destination MAC in a PDU field of the LTM unicast address message is a bridge MAC of the first device, and the LTM unicast address message carries the MEP ID of the device.

In the above scheme, the apparatus further comprises:

and the judging module is used for judging whether a hardware table entry corresponding to the MEP ID of the first equipment is established or not after the member equipment receives the LTM multicast address message sent by the first equipment, indicating the table entry establishing module to establish the hardware table entry corresponding to the MEP ID of the first equipment if the hardware table entry is not established, and setting the neighbor relation with the first equipment as normal.

A device, the device is a member device of a Connectivity Fault Detection (CFD) network without hardware detection capability, a first device is a device to be joined of the CFD network, and the device comprises:

and the message sending module is used for sending an LTR message to the first equipment so as to establish a hardware table entry corresponding to the MEP ID of the first equipment when the first equipment has hardware detection capability, wherein the LTR message carries the MEPID of the member equipment.

In summary, the technical scheme provided by the invention can effectively solve the problem that hardware resources are wasted due to the fact that numerous hardware entries occupy a large amount of hardware resources without being selectively issued, and by dynamically adding and deleting the hardware entries needing to establish the neighbor relation, the number of service instances supported by the device is increased, and the hard resources occupied by useless MEPs are avoided.

Drawings

Fig. 1 is a schematic diagram of CFD networking.

Fig. 2 shows an LTM multicast address packet format.

Fig. 3 is a customized LTR message format.

Fig. 4 is a schematic networking diagram in the embodiment.

Fig. 5 is a flow chart of method embodiment 1.

Fig. 6 is a flowchart of method embodiment 2.

Fig. 7 is a flowchart of method embodiment 3.

Fig. 8 is a flowchart of method embodiment 4.

Fig. 9 is a schematic structural diagram of a CFD networking to-be-added device with hardware detection capability according to an embodiment of the present invention.

Fig. 10 is a schematic structural diagram of a CFD networking to-be-added device without hardware detection capability according to an embodiment of the present invention.

Fig. 11 is a schematic structural diagram of a CFD networking member device with hardware detection capability according to an embodiment of the present invention.

Fig. 12 is a schematic structural diagram of a CFD networking member device without hardware detection capability 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, the present invention will be further described in detail with reference to the accompanying drawings and specific embodiments.

The technical scheme of one embodiment of the invention is as follows:

In this embodiment, before the first device applies for joining CFD networking, the basic configuration of CFD is completed: enabling a CFD detection function, configuring a service instance configuration MEP, and enabling a CCM (connectivity Check Message) Message sending function of the MEP. The first device is used as a device to be added to the CFD networking, and whether the first device has a hardware detection capability or not, when the first device is added to the CFD networking, the first device first sends a Link Trace Message (LTM), where the LTM is an LTM multicast address Message.

The LTM multicast address packet is sent to the CFD networking member device by the first device, a destination MAC (target MAC) in a Protocol Data Unit (PDU) field of the LTM multicast address packet is a destination MAC (multicast MAC) in an ethernet header, and is in a form of 01-80-c2-00-00-3y, a value of y is an MEP level, a value of y corresponding to an MEP at a level of 0 to 7 is 8-F, and a packet format is shown in fig. 2. Because the LTM multicast address message is a multicast message, MEPs in the same service instance in the CFD networking will all receive the LTM multicast address message, and at this time, all member devices in the CFD networking that receive the LTM multicast address message will process the LTM multicast address message because the destination MAC in the LTM PDU field is a multicast address.

The member devices in the CFD networking are divided into two categories, member devices with hardware detection capability and member devices without hardware detection capability. The two types of member devices have different processing after receiving the LTM multicast address message sent by the first device, and the description is given in different cases:

(1) after receiving the LTM multicast address message sent by the first device, the member device with hardware detection capability establishes a hardware table entry corresponding to the MEP ID carried in the LTM multicast address message, and sets a neighbor relationship with the first device as normal. After the member device with the hardware detection capability sets the new MEP ID hardware table entry, the CCM message sent by the first device can be identified.

After receiving the LTM multicast address packet sent by the first device, the member device may further determine whether a hardware entry corresponding to the MEP ID of the first device has been created, if so, send an LTM unicast address packet to the first device, if not, establish a hardware entry corresponding to the MEP ID of the first device, and send an LTM unicast address packet to the first device.

And the target MAC in the field of the LTM unicast address message PDU is the bridge MAC of the first equipment, and the self-defined TLV field of the LTM unicast address message carries the MEP ID of the member equipment with hardware detection capability which sends the LTM unicast address message. Because the destination MAC in the LTM PDU field sent by the member device with hardware detection capability is the bridge MAC of the first device, that is, the unicast address, only the first device will process the LTM unicast address packet in the same service instance.

If the first device has the hardware detection capability, after receiving the LTM unicast address message, generating a hardware table entry corresponding to the MEP ID of the member device with the hardware detection capability, so that the CCM message sent by the member device with the hardware detection capability can be processed, and the neighbor relation between the CCM message and the member device with the hardware detection capability of the CFD networking is established as normal.

After receiving the LTM unicast address message, the first device may further determine whether a hardware entry corresponding to the MEP ID of each member device in the CFD networking has been created, if so, reply an LTR message to the member device in the CFD networking that sends the LTM unicast address message, otherwise, establish a hardware entry corresponding to the MEP ID of the member device in the CFD networking that sends the LTM unicast address message, and then reply an LTR message to the member device in the CFD networking that sends the LTM unicast address message, where the LTR message does not carry the MEP ID of the first device.

If the first device does not have the hardware detection capability, the CCM message sent by the member device with the hardware detection capability of the CFD networking can be directly processed without establishing a corresponding hardware table entry, and the neighbor relation between the CCM message and the member device with the hardware detection capability of the CFD networking is established to be normal, so that the first device without the hardware detection capability directly replies an LTR message after receiving the LTM unicast address message sent by the member device with the hardware detection capability of the CFD networking, and the LTR message does not carry the MEP ID of the device.

(2) The member device without hardware detection capability can directly process the CCM message sent by the first device, so that the member device without hardware detection capability responds to a self-defined LTR message after receiving the LTM multicast address message sent by the first device. As shown in fig. 3, the MEP ID Value of the member device without hardware detection capability is carried in the custom TLV (Type/Length/Value) of the custom LTR message.

If the first device has the hardware detection capability, after receiving the LTR message, generating a hardware table entry corresponding to the MEP ID of the member device without the hardware detection capability, so that the CCM message sent by the member device without the hardware detection capability can be processed, and the neighbor relation between the CCM message and the member device without the hardware detection capability of the CFD networking is established as normal.

After receiving the self-defined LTR message, the first device may further determine whether a hardware entry corresponding to a member device MEP ID without hardware detection capability in the CFD networking has been created, if so, perform no processing, otherwise, establish a hardware entry corresponding to a member device MEP ID without hardware detection capability in the CFD networking.

If the first device does not have the hardware detection capability, the CCM message sent by the member device which does not have the hardware detection capability in the CFD networking can be directly processed without establishing a corresponding hardware table entry, and the neighbor relation between the first device and the member device which does not have the hardware detection capability in the CFD networking is established as normal.

In order to prevent the neighbors in the fail state from occupying hardware resources for a long time, a user can enable the device to enable an automatic Link Tracking (LT) function according to own needs, and when the LT function is enabled, the device can clear the hardware resources occupied by the neighbors in the fail state for a long time. The concrete implementation is as follows:

and setting a timer, triggering the timer when the equipment senses the fail of the neighbor equipment, and deleting the hardware table entry corresponding to the MEP ID of the neighbor equipment in the fail state by the equipment after the timer is overtime. The timer sets a time range for which the user specifies a duration.

The user enables the automatic LT function, that is, after a MEP senses the far-end neighbor state fail and the timer times out and deletes the corresponding hardware entry, the user-defined LT message (LTM message or LTR message) in the present application is periodically sent, and the subsequent processing flow is as described above. Therefore, the situation that the link cannot normally process the CCM message after being normal due to the fact that hardware resources are directly deleted under abnormal conditions such as single-pass is avoided.

The present application will be described below with reference to specific examples. As shown in fig. 4, Device a is a Device to be added in CFD networking, its MEP level is 5, and Device b to Device D are member devices in CFD networking. Device A-Device D belong to the same service instance. Wherein Device B is a Device with hardware detection capability, and Device C and Device D do not have hardware detection capability. And Device B does not establish a hardware entry corresponding to Device a's MEP ID.

Example 1

In this embodiment, it is assumed that Device a has a hardware detection capability and does not establish a hardware entry corresponding to the MEP ID of Device B, and the technical solution of the present application is described by taking an example that Device a having a hardware detection capability and Device B having a hardware detection capability in a CFD networking create a hardware entry to establish a neighbor relationship, and other member devices having a hardware detection capability in a CFD networking are the same as the method for Device a to create a hardware entry, and are not described herein again. Fig. 5 is a flowchart of the present embodiment, which includes the following steps:

step 501: the Device A sends an LTM multicast address message to member equipment in the CFD networking, wherein a self-defined TLV field of the LTM multicast address message carries an MEP ID value of the Device A, a destination MAC in a PDU field is a multicast MAC, and a source MAC in the PDU field is a bridge MAC of the Device A.

In this step, the destination MAC in the PDU field of the LTM multicast address packet sent by Device a is a multicast MAC, the form of the multicast MAC is 01-80-c2-00-00-3y, y is the level of the MEP, the corresponding y value of the MEP at the level 0 to 7 is 8-F, the MEP level of Device a in this embodiment is 5, and the corresponding y value is D.

Because the LTM multicast address message is a multicast message, all devices in the CFD networking that belong to the same service instance as Device a can process the message, that is, any Device from Device B to Device D can receive and process the LTM multicast address message.

Step 502: the Device B receives the LTM multicast address message sent by the Device A, establishes a hardware table entry corresponding to the MEP ID of the Device A, sets a neighbor relation with the Device A as normal, and sends the LTM unicast address message to the Device A.

In this step, Device B receives the LTM multicast address message sent by Device a, compares the existing hardware table entries, finds that there is no hardware table entry corresponding to the LTM multicast address message, establishes the hardware table entry corresponding to the MEP ID of Device a, and sets the neighbor relation with Device a to be normal. After the Device B sets the hardware table entry corresponding to the MEP ID of the Device a, the CCM packet sent by the Device a can be identified, so as to establish the neighbor relationship with the Device a.

After the Device B creates a hardware table entry corresponding to the MEP ID of the Device A, an LTM unicast address message is sent, a target MAC in the PDU field of the LTM unicast address message is the bridge MAC of the Device A, and the self-defined TLV field carries the MEP ID of the Device B. Since the destination MAC in the field of the LTM unicast address message PDU sent by Device B is the bridge MAC of Device a, i.e. the unicast address, only Device a will process the LTM unicast address message in the same service instance.

Step 503: and the Device A receives the LTM unicast address message sent by the Device B, creates a hardware table entry corresponding to the MEP ID of the Device B, and replies the LTR message to the Device B.

In this step, Device a receives the LTM unicast address message sent by Device B, compares the existing hardware table entries, finds that there is no hardware table entry corresponding to the LTM unicast address message, creates a hardware table entry corresponding to the MEP ID of Device B, sets the neighbor relationship with Device B to be normal, and after Device a sets the hardware table entry corresponding to the MEP ID of Device B, can identify the CCM message sent by Device B, thereby establishing the neighbor relationship with Device B.

Device a then replies an LTR message to Device B. Here, if Device a finds that there is a hardware entry corresponding to the MEP ID of Device B, it directly replies an LTR message to Device B without any processing on the LTM unicast address message, where the LTR message does not carry the MEP ID of Device a.

Example 2

In this embodiment, it is assumed that Device a has a hardware detection capability and does not establish a hardware entry corresponding to the MEP ID of Device C, and the technical solution of the present application is described by taking an example that Device a having a hardware detection capability and Device C having no hardware detection capability in a CFD networking establish a neighbor relationship, and other member devices having no hardware detection capability in the CFD networking are the same as the method for Device a to establish a hardware entry, and no further description is given here. Fig. 6 is a flowchart of the present embodiment, which includes the following steps:

step 601 is the same as step 501 and will not be described in detail.

Step 602: after receiving the LTM multicast address message sent by Device A, Device C responds to a self-defined LTR message, wherein the self-defined LTR message carries the MEP ID of Device C.

In this step, Device C does not have hardware detection capability, and can directly process the CCM message sent by Device a without establishing a hardware table entry corresponding to the MEPID of Device a, so that Device C responds to a self-defined LTR message after receiving the LTM multicast address message sent by Device a. The MEP ID value of Device C is carried in the self-defining TLV of the self-defining LTR message.

Step 603: and the Device A receives the self-defined LTR message from the Device C and creates a hardware table entry corresponding to the MEPID of the Device C.

In this step, Device a receives the self-defined LTR message from Device C, compares the existing hardware entries, and creates a hardware entry corresponding to the MEP ID of Device C if it finds that there is no corresponding hardware entry. After setting a new MEP ID hardware table entry, the Device a can identify the CCM message sent by the Device C, thereby establishing a neighbor relationship with the Device C, and the neighbor state is normal.

Example 3

In this embodiment, it is assumed that Device a does not have a hardware detection capability, and the technical solution of the present application is described by taking an example of creating a hardware table entry to establish a neighbor relationship between Device a without a hardware detection capability and Device B with a hardware detection capability in a CFD networking. Fig. 7 is a flowchart of the present embodiment, which includes the following steps:

step 701 is the same as step 501 and will not be described in detail here.

Step 702 is the same as step 502 and will not be described in detail here.

Step 703: and the Device A receives the LTM unicast address message sent by the Device B and replies the LTR message to the Device B.

Because Device a does not have hardware detection capability, it can directly process CCM message sent by Device B without establishing hardware table entry corresponding to MEP ID of Device B, and its neighbor relation with Device B is normal, so after Device a receives LTM unicast address message sent by Device B, it does not make any processing, and directly replies an LTR message, which does not carry MEP ID of Device a.

Example 4

In this embodiment, it is assumed that Device a does not have a hardware detection capability, and the technical solution of the present application is described by taking an example of establishing a neighbor relationship between Device a without a hardware detection capability and Device C without a hardware detection capability in a CFD networking. Fig. 8 is a flowchart of the present embodiment, which includes the following steps:

step 801 is the same as step 601 and will not be described in detail.

Step 802 is the same as step 602 and will not be described in detail.

Because the Device a does not have the hardware detection capability, the CCM message sent by the Device C can be directly processed without establishing a hardware table entry corresponding to the MEP ID of the Device C, and the neighbor relation between the CCM message and the Device C is normal, so the Device a does not perform any processing after receiving the self-defined LTR message sent by the Device C.

The technical solution of the present invention is described in the above embodiments, when a device with hardware detection capability joins a CFD networking, a hardware table is created between the device with hardware detection capability and a device without hardware detection capability in the CFD networking to establish a neighbor relationship, and when a device without hardware detection capability joins the CFD networking, a hardware table is created between the device with hardware detection capability and the device without hardware detection capability in the CFD networking to establish a neighbor relationship.

To the above method, the present invention further discloses a device to be added in a connectivity fault detection CFD networking, where the device has a hardware detection capability, and as shown in fig. 9, the device disclosed in the present invention includes:

a message sending module 901, configured to send a link tracking LTM multicast address message to member devices in the CFD networking, where the LTM multicast address message carries a maintenance endpoint MEP level and an MEP ID value of the device, a destination MAC in a PDU field of a protocol data unit PDU of the LTM multicast address message is a multicast MAC, and a source MAC in the PDU field is a bridge MAC of the device;

a message receiving module 902, configured to receive an LTM unicast address message or a link tracking response LTR message sent by a member device in the CFD networking, where,

the table entry creating module 903 is configured to create hardware table entries corresponding to MEPIDs of each member device in the CFD networking, and set a neighbor relationship between the hardware table entries and the corresponding member devices as normal.

The apparatus further comprises a means for controlling the operation of the apparatus,

a determining module 904, configured to determine whether a hardware entry corresponding to the MEP ID of each member device in the CFD networking has been created after the message receiving module 902 receives the LTM unicast address message or the LTR message sent by the member device in the CFD networking, if not, instruct the entry creating module to create a corresponding hardware entry, and set a neighbor relationship with the corresponding member device as normal.

The message sending module 901 is further configured to, if the message receiving module receives an LTM unicast address message sent by a member device in the CFD networking, send an LTR message to the member device in the CFD networking that sends the LTM unicast address message, where the LTR message does not carry the MEPID of the first device.

To the above method, the present invention also discloses a device, where the device is a device to be added in a connectivity fault detection CFD networking, which does not have a hardware detection capability, as shown in fig. 10, and the device includes:

a message sending module 1001, configured to send a link tracking LTM multicast address message to a member device in the CFD networking, where the LTM multicast address message carries a maintenance endpoint MEP level and an MEP ID value of the device, a destination MAC in a PDU field of a protocol data unit PDU of the LTM multicast address message is a multicast MAC, and a source MAC in the PDU field is a bridge MAC of the device;

a message receiving module 1002, configured to receive an LTM unicast address message or a link tracking response LTR message sent by a member device in the CFD networking; wherein,

If the message receiving module 1002 receives an LTM unicast address message sent by a member device in the CFD networking,

the message sending module 1001 is further configured to send an LTR message to a member device in the CFD networking, where the LTR message does not carry the MEPID of the first device, and the member device sends an LTM unicast address message.

To the above method, the present invention further discloses a device, where the device is a member device connected to a CFD networking and having a hardware detection capability, and the first device is a device to be joined in the CFD networking, as shown in fig. 11, the device includes:

a message receiving module 1101, configured to receive a link tracking LTM multicast address message sent by the first device, where the LTM multicast address message carries a maintenance endpoint MEP level and an MEP ID value of the first device, a destination MAC in a protocol data unit PDU field of the LTM multicast address message is a multicast MAC, and a source MAC in the PDU field is a bridge MAC of the first device;

an entry creating module 1102, configured to create a hardware entry corresponding to the MEP ID of the first device, and set a neighbor relationship with the first device to be normal;

a message sending module 1103, configured to send an LTM unicast address message to the first device, so as to establish a hardware table entry corresponding to an MEP ID of the device when the first device has a hardware detection capability, where a destination MAC in a PDU field of the LTM unicast address message is a bridge MAC of the first device, and the LTM unicast address message carries the MEP ID of the device.

The device further includes a determining module 1104, configured to determine, after the member device receives the LTM multicast address packet sent by the first device, whether a hardware entry corresponding to the MEP of the first device has been created, if not, instruct the entry creating module to create a hardware entry corresponding to the MEP ID of the first device, and set a neighbor relationship with the first device to be normal.

To the above method, the present invention further discloses a device, where the device is a member device that is connected to a CFD networking and does not have a hardware detection capability, and the first device is a device to be joined in the CFD networking, as shown in fig. 12, the device includes:

a message receiving module 1201, configured to receive a link tracking LTM multicast address message sent by the first device, where the LTM multicast address message carries a maintenance endpoint MEP level and an MEP ID value of the first device, a destination MAC in a protocol data unit PDU field of the LTM multicast address message is a multicast MAC, and a source MAC in the PDU field is a bridge MAC of the first device;

a message sending module 1202, configured to send a link tracking response LTR message to the first device, so as to establish a hardware entry corresponding to an MEP of the first device when the first device has a hardware detection capability, where the LTR message carries the MEP ID of the member device.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that are within the spirit and principle of the present invention are intended to be included within the scope of the present invention.

Claims

1. A method for generating a hardware table entry of a connectivity error detection networking system is applied to a first device to be added with hardware detection capability in a connectivity error detection CFD networking, and is characterized by comprising the following steps:

2. The method of claim 1, further comprising:

3. A method for generating a hardware table entry of a connectivity error detection networking system is applied to a first device to be added without hardware detection capability in the connectivity error detection CFD networking, and is characterized by comprising the following steps:

4. The method of claim 3, further comprising:

5. A method for generating a hardware table entry of a connectivity error detection networking system is applied to member equipment with hardware detection capability in a connectivity error detection CFD networking, and first equipment is equipment to be added in the CFD networking, and the method is characterized by comprising the following steps:

6. The method of claim 5, further comprising:

7. A method for generating a hardware table entry of a connectivity error detection networking system is applied to member equipment without hardware detection capability in a connectivity error detection CFD networking, and first equipment is equipment to be added in the CFD networking, and the method is characterized by comprising the following steps:

and the member equipment replies an LTR message to the first equipment so as to establish a hardware table entry corresponding to the MEP ID of the member equipment when the first equipment has hardware detection capability, wherein the LTR message carries the MEPID of the member equipment.

8. A device to join with hardware detection capability in connectivity error detection, CFD, networking, the device comprising:

9. The apparatus of claim 8, further comprising:

a judging module, configured to judge whether a hardware entry corresponding to an MEP ID of each member device in the CFD networking has been created after the device receives an LTM unicast address packet or an LTR packet sent by a member device in the CFD networking, and if not, instruct the entry creating module to create a corresponding hardware entry, and set a neighbor relationship with the corresponding member device as normal;

10. A device to join in a connectivity error detection, CFD, networking without hardware detection capability, the device comprising:

11. The device of claim 10, wherein if the message receiving module receives an LTM unicast address message sent by a member device in the CFD networking,

the message sending module is further configured to send an LTR message to the member device in the CFD networking that sends an LTM unicast address message, where the LTR message does not carry the MEP ID of the device.

12. A member device with hardware detection capability for communication error detection CFD networking, a first device being a device to be joined in the CFD networking, the device comprising:

13. The apparatus of claim 12, further comprising:

14. A member device for connecting fault detection CFD networking without hardware detection capability, a first device being a device to be joined of the CFD networking, the device comprising:

and the message sending module is used for sending an LTR message to the first equipment so as to establish a hardware table entry corresponding to the MEP ID of the first equipment when the first equipment has hardware detection capability, wherein the LTR message carries the MEP ID of the member equipment.