WO2014019348A1

WO2014019348A1 - Method, device and system for operation, management and maintenance of oam configuration

Info

Publication number: WO2014019348A1
Application number: PCT/CN2013/070534
Authority: WO
Inventors: 古锐; 董杰; 郑莲淑
Original assignee: 华为技术有限公司
Priority date: 2012-07-31
Filing date: 2013-01-16
Publication date: 2014-02-06
Also published as: CN103580894B; CN103580894A

Abstract

A method, a device and a system for OAM configuration are disclosed. The method includes the following steps: a source PE configures a source OAM entity and the source OAM entity is forbidden to send OAM packets to a destination PE; the first LSP Ping request message carrying the source OAM entity configuration information is sent to the destination PE; the first LSP Ping response message carrying the destination OAM entity configuration information sent by destination PE is received; when the destination OAM entity configuration information matches the source OAM entity configuration information, the source OAM entity can has a function to send the OAM packets to the destination PE. Configuration systems of the source PE, the destination PE and the OAM are disclosed. Through the technical solution provided by embodiments of the present invention, the source and destination OAM configuration workload are reduced, both ends dynamically complete the OAM configuration by interactive LSP Ping message and the manual configuration errors are avoided.

Description

Method, device and system for operating, managing and maintaining OAM configuration

TECHNICAL FIELD The present invention relates to the field of network communications, and in particular, to a method, a device, and a system for configuring an OAM. BACKGROUND OF THE INVENTION Perfect operation, management, and maintenance (English called Operations, Administration and Maintenance, English abbreviated as OAM) is an important symbol of a carrier-class network. It is extremely important for operators. OAM can reduce the complexity of operators. Degrees and operation and maintenance costs can enhance the availability of the carrier network. It can also help the carrier network to verify the SLA (Service Level Agreement).

The OAM mechanism mainly includes three aspects: fault management, performance monitoring, and protection switching. Fault management can be divided into four aspects: fault detection, fault verification, fault localization and fault notification. Performance monitoring mainly provides packet loss and delay. And monitoring of the three indicators of jitter.

For the Internet Protocol/Multiprotocol Label Switching (IP/MPLS) network and Ethernet (Ethernet) network, there are mainly well-established OAM mechanisms, mainly Ethernet OAM and connection-oriented. Packet switching network technology (English full name Transport Profile for MPLS, English abbreviated as MPLS-TP) OAM. The former includes IEEE 802.3ah, IEEE 802. lag, ITU-T Y.1731 and some Metro Ethernet Forums (English called Metro Ethernet Forum, English abbreviated as MEF). The latter consists of a series of standards defined by the IETF. .

A virtual private network (English for Virtual Private Network, English abbreviated as VPN) is a virtual private network that operators provide to users through their public networks. That is, VPN is a proprietary network of users from the perspective of users. For operators, the public network includes public Backbone network and public carrier border equipment. The geographically separated VPN member sites are connected to the corresponding carrier edge routers (English Provider Edge, referred to as PEs) through the client device (CPE), and form the customer's VPN network through the operator's public network.

The Layer 3 Virtual Private Network (L3VPN in English) is a three-layer VPN technology based on MPLS. On the L3VPN network, you need to manually create the OAM entity of the source PE and the sink PE, and configure the parameters of the OAM entity of the source PE and the sink PE respectively. In the process, the configuration parameters of the OAM entity of the sink PE are the same as those of the OAM entity of the source PE. This not only makes the OAM configuration work much larger, but also is prone to configuration errors. SUMMARY OF THE INVENTION The embodiments of the present invention provide a method, a device, and a system for configuring an OAM to solve the problem of large configuration and configuration errors caused by manual configuration when a PE device is configured to detect a VPN by an OAM in an L3 VPN network. The problem.

In a first aspect, a method for configuring an OAM is provided. The method includes: configuring, by a source end operator, an edge router, a source OAM entity, and disabling the source OAM entity from sending an OAM packet to the sink PE. ;

Transmitting, by the sink PE, a first label switching path Internet packet explorer LSP ping request message carrying the source OAM entity configuration information, so that the sink PE configures the information according to the source OAM entity configuration information. The sinking OAM entity of the sinking PE starts the packet receiving function of the sinking OAM entity, and the first LSP ping request message further includes a VPN identifier of the Layer 3 virtual private network L3 VPN, where the VPN identifier is used to identify The sink PE device needs a VPN for OAM detection;

Receiving a first LSP ping response message sent by the sinking end PE, where the first LSP ping response message carries the configuration information of the sink OAM entity, and determining the configuration information of the sink OAM entity and the source OAM entity When the configuration information is matched, the function of the OAM entity sent by the source OAM entity to the sink PE is enabled.

In a first possible implementation manner of the first aspect, the method further includes: when determining the sink OAM entity configuration information and the source OAM entity configuration If the information is not matched, the source OAM entity configuration information is matched with the configuration of the sink OAM entity, and the function of the source OAM entity to send the OAM packet to the sink PE is enabled.

In the first aspect or the first possible implementation manner of the first aspect, the second possible implementation manner of the first aspect is further provided, where the first LSP ping request message is virtual private The network OAM forwarding equivalence class stack type, length, and content VPN OAM FEC TLV carries the VPN identifier, and the VPN OAM FEC TLV includes: a target global ID, a target global ID, a target node ID, a target node ID, and a target route identifier, Target Route Distinguishes.

In a third possible implementation manner of the second possible implementation manner of the first aspect, the VPN OAM FEC TLV further includes:

The target interface ID, the IF ID, is used to identify an interface that the sink PE needs to perform OAM detection.

The destination IP address is used to identify the sink end PE to perform OAM detection.

In the first aspect or any one of the foregoing possible implementation manners of the foregoing aspect, the fourth possible implementation manner of the first aspect is further provided, where the first LSP ping request message is Also includes the OAM Management Type, Length, and Content OAM Administration TLV, which includes:

The alarm enable flag is used to identify whether the OAM alarm reporting function is enabled. The two-way detection flag is used to identify whether the two-way OAM detection function between the source PE and the sink PE is established.

In a fourth possible implementation manner of the first aspect, the fifth possible implementation manner of the first aspect is further provided, where the method further includes:

Before sending the first LSP ping request message to the sink PE, the method includes: configuring, by the source PE, a function of receiving a source OAM entity, and setting a bidirectional detection flag of the 0 An enable state, so that the sink PE configures a function of sending the OAM entity of the sink OAM entity, and starts a function of the sink entity to send an OAM message to the source end; The first L SP ping request message further includes a VPN 0 AM source identifier type, a length, and a content VPN OAM Source Identifier TLV, where the VPN OAM Source Identifier TLV is used to identify the VPN label that the source PE needs to perform OAM detection. The VPN OAM Source Identifier TLV includes: a source global ID source global ID, a source node ID source node ID, and a source routing identifier Source Route Distinguisher.

In a fifth possible implementation manner of the first aspect, the sixth possible implementation manner of the first aspect is further provided, where the VPN 0 AM Source Identifier TLV further includes:

The source interface ID source IF ID is used to identify the interface that the source PE needs to perform OAM detection.

The source IP address is used to identify that the source PE needs to perform OAM detection.

In a fourth or fifth or a sixth possible implementation manner of the first aspect, a seventh possible implementation manner of the first aspect is further provided, in the first LSP Ping request message The alarm enable flag in the included OAM Administration TLV is in a forbidden state, so that the sinking PE suppresses the alarm reporting function of the sink OAM entity after configuring the sink OAM entity, where the enabling After the source OAM entity sends the OAM packet to the sink PE, the method includes:

Sending a second LSP ping request message to the sinking PE, where the second LSP ping request message includes the OAM Administration TLV, and the alarm enable flag in the OAM Administration TLV is enabled, so that the sink After receiving the second LSP ping request message, the end PE enables the alarm reporting function of the sink OAM entity.

In a seventh possible implementation of the first aspect, the eighth possible implementation manner of the first aspect is further provided, where the method further includes:

Receiving a second LSP ping response message sent by the sinking end PE, where the second LSP ping response message is a response message to the second LSP ping request message;

The alarm reporting function of the source OAM entity is enabled when the alarm enable flag of the OAM Administration TLV is enabled in the second LSP ping response message.

In a second aspect, a method for configuring an OAM is provided, where the method includes: receiving, by a sink operator, an edge router, a first label switching path, an Internet packet explorer LSP, that carries source-origin 0 MME configuration information sent by a source PE. Ping request message; the first LSP ping request message further includes a VPN of a three-layer virtual private network L3VPN Identification

And configuring a sink OAM entity according to the first LSP ping request message, and configuring the sink OAM entity to detect the VPN corresponding to the VPN identifier, and start a packet receiving function of the sink OAM entity;

Sending a first LSP ping response message to the source PE, where the first LSP ping response message carries configuration information of the sink OAM entity.

In a first possible implementation manner of the second aspect, the first LSP ping request message further includes an 0 AM management type, a length, and a content 0 AM Administration TLV, where the OAM Administration TLV includes:

When the bidirectional detection flag is set to the enabled state, the sink PE configures the 发送艮发送发送发送发送 function of the sink OAM entity, and starts the sink OAM entity to send the OAM to the source PE ^ The function of the text.

In the second aspect or the first possible implementation manner of the first aspect, the second possible implementation manner of the second aspect is further provided, when the first LSP is received When the alarm enable flag in the OAM Administration TLV in the ping request message is in the forbidden state, the sink PE suppresses the alarm reporting function of the sink OAM entity after configuring the sink OAM entity, and the method further includes :

And receiving the second LSP ping request message sent by the source PE, and enabling the alarm of the OAM entity of the OAM Administration TLV in the second LSP ping request message to be enabled. Reporting function.

In a second possible implementation manner of the second aspect, a third possible implementation manner of the second aspect is further provided, that: sending, by the source PE, a second LSP ping response message, where The second LSP ping response message includes an OAM Administration TLV, and when the two-way detection flag in the OAM Administration TLV included in the first LSP ping request message is enabled, the second LSP Ping response message is in the OAM Administration TLV. The alarm enable flag is enabled, so that the source PE can enable the alarm reporting function of the source OAM entity after receiving the second LSP ping response message.

In a third aspect, a source PE is provided, and the method includes: An OAM entity unit, configured to configure a source OAM entity, and prohibit the source OAM entity from sending an OAM packet to the sink PE;

a generating unit, configured to generate a first LSP ping request message according to the source OAM entity configured by the OAM entity unit, where the first LSP ping request message carries the source OAM entity configuration information, the first LSP ping request The message further includes a VPN identifier of the Layer 3 virtual private network L3VPN, where the VPN identifier is used to identify the VPN that the sink PE device needs to perform OAM detection;

a sending unit, configured to send the first LSP ping request message generated by the generating unit to a sinking PE, so that the sinking PE configures a sink OAM entity according to the first LSP ping request message, and starts Packet receiving work of the OAM entity

•6 fi匕 . ,

a receiving unit, configured to receive a first LSP ping response message sent by the sinking PE, where the first LSP ping response message carries the sink OAM entity configuration information of the sink PE;

The OAM entity unit is further configured to: when it is determined that the configuration information of the sink OAM entity matches the configuration information of the source OAM entity, enable the source OAM entity to send an OAM^ message to the sink PE. Features.

In a first possible implementation manner of the third aspect, the OAM entity unit is further configured to: when determining that the sink OAM entity configuration information does not match the source OAM entity configuration information, The source OAM entity configuration information is matched with the sink OAM entity configuration information, and the function of the source OAM entity to send the OAM packet to the sink PE is enabled.

In the third aspect or the first possible implementation manner of the third aspect, the second possible implementation manner of the third aspect is further provided, the first LSP generated by the generating unit The ping request message also includes:

OAM management type, length, content OAM Administration TLV, used to identify the VPN identifier; the 0 AM Admini stration TLV includes:

Before the sending unit sends the first LSP ping request message to the sink PE, the OAM entity unit is further configured to configure an OAM report of the source OAM entity. Receiving a function, and setting the bidirectional detection flag of the 0 Administration TLV to an enabled state, so that the sink PE configures an OAM packet sending function of the sink OAM entity, and starts the sink end The OAM entity sends the OAM packet to the source PE.

In a second possible implementation manner of the foregoing third aspect, the third possible implementation manner of the foregoing third aspect is further provided, where the 0 in the first LSP Ping request message generated by the generating unit is The alarm enable flag in the AM Administration TLV is in a forbidden state, so that the sinking PE suppresses the alarm reporting function of the sink OAM entity after configuring the sink OAM entity;

After the OAM entity unit enables the source OAM entity to send an OAM packet to the sink PE, the generating unit is further configured to generate a second LSP Ping request message, where the second LSP Ping The alarm enable flag in the OAM Administration TLV included in the request message is enabled.

The sending unit is further configured to send the second LSP ping request message generated by the generating unit to the sink PE, so that the sink PE after receiving the second LSP ping request message The alarm reporting function of the sink OAM entity is enabled.

In a third possible implementation manner of the foregoing third aspect, the fourth possible implementation manner of the foregoing third aspect is further provided, where the receiving unit is further configured to receive the sending by the sink PE a second LSP Ping response message;

The OAM entity unit is further configured to: when the alarm enable flag of the OAM Administration TLV included in the second LSP ping response message received by the receiving unit is enabled, enable the source OAM entity Alarm reporting function.

In a fourth aspect, a sink PE is provided, and the method includes:

a receiving unit, configured to receive a first label switching path Internet packet explorer LSP ping request message that is sent by the source PE and carries the source OAM entity configuration information; the first LSP ping request message includes a VPN of a three-layer virtual private network L3VPN Identification

An OAM entity unit, configured to configure a sink OAM entity according to the first LSP ping request message received by the receiving unit, and configure the sink OAM entity to detect a VPN corresponding to the VPN identifier, and start the The receiving function of the sink OAM entity;

a generating unit, configured to generate a first LSP Ping response message according to the sink OAM entity configured by the OAM entity unit, where the first LSP Ping response message carries the Slot OAM entity configuration information;

And a sending unit, configured to send the first LSP Ping response message generated by the generating unit to the source PE.

In the first possible implementation manner of the fourth aspect, the first LSP ping request message received by the receiving unit further includes an OAM management type, a length, and a content OAM Administration TLV, where the OAM Administration TLV includes :

The alarm enable flag is used to identify whether the 0AM alarm reporting function is enabled. The two-way detection flag is used to identify whether the two-way OAM detection function between the source PE and the sink PE is established.

The OAM entity unit is further configured to: when the bidirectional detection flag in the OAM Administration TLV is set to an enabled state, configure an OAM file sending function of the sink OAM entity, and start the sink OAM The function of sending an OAM packet to the source PE.

In the fourth aspect or the first possible implementation manner of the fourth aspect, a second possible implementation manner of the fourth aspect is further provided, when the receiving unit receives the 0 AM When the alarm enable flag in the Administration TLV is in the forbidden state, the OAM entity unit, after configuring the sink OAM entity, suppresses the alarm reporting function of the sink OAM entity;

The receiving unit is further configured to receive the second LSP ping request message, where the second LSP ping request message includes the OAM Administration TLV, and the alarm enable flag in the 0 AM Administration TLV is enabled. State

The OAM entity unit is further configured to enable the alarm reporting function of the sink OAM entity according to the second LSP ping request message received by the receiving unit.

In a second possible implementation manner of the fourth aspect, a third possible implementation manner of the foregoing third aspect is further provided, where the generating unit is further configured to generate a second LSP Ping response message, where The two-way detection, the alarm enable flag of the OAM Administration TLV included in the second L SP Ping response message is an enabled state, and the sending unit is further configured to send the generated to the source PE The second LSP ping response message generated by the unit is configured to enable the source end PE to enable the alarm reporting function of the source OAM entity after receiving the second LSP ping response message.

The fifth aspect provides an OAM configuration system, where the system includes: the third aspect or any one of the possible implementation manners provided by the third aspect The source PE provided in the middle;

The fourth aspect or the sink PE provided in any one of the possible implementation manners provided by the fourth aspect.

The embodiment of the present invention provides a method, a device, and a system for configuring an OAM. After the source PE device is configured with the source OAM entity, the OAM configuration information of the source PE is sent to the sink PE device by using the extended LSP ping request message. The function of the sinking end PE to configure the sink OAM entity of the sink PE according to the source OAM configuration information, and the function of the OAM entity to send the OAM packet to the source PE; The request message includes the VPN identifier that the sink PE needs to perform OAM detection. After the OAM entity of the source PE and the sink PE is configured, the source OAM entity is enabled to send the OAM to the sink PE. The function of the spoofing text, thereby completing the OAM configuration of the source PE and the sink PE, the source OAM entity and the sink OAM entity can enable the corresponding alarm reporting function, and the implementation manner reduces the configuration of the two ends. The OAM configuration workload is implemented by the two ends through the interactive LSP ping message to dynamically complete the OAM configuration, which avoids errors in manual configuration.

BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below, and obviously, in the following description The drawings are only some of the embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any creative work.

1 is a schematic diagram of an OAM configuration process between PE devices in a VPN network according to an embodiment of the present invention;

2 is a schematic flowchart of an OA configuration method according to an embodiment of the present invention; FIG. 3 is a schematic diagram of an OAM Function TLV according to an embodiment of the present invention; FIG. 4 is a schematic diagram of a VPNv4 OAM FEC Stack TLV format according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a VPNv6 OAM FEC Stack TLV format according to an embodiment of the present disclosure; FIG. 6 is a schematic diagram of an OAM Administration TLV format according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of a format of a VPNv4 OAM Source Identifier TLV according to an embodiment of the present disclosure;

FIG. 8 is a schematic diagram of a format of a VPNv6 OAM Source Identifier TLV according to an embodiment of the present disclosure;

FIG. 9 is an OAM Administration TLV carrying an alarm enable bit according to an embodiment of the present invention;

FIG. 10 is a schematic flow chart of another OAM configuration method according to an embodiment of the present disclosure;

FIG. 11 is a schematic diagram of a system for configuring an OAM according to an embodiment of the present invention; FIG. 12 is a schematic diagram of another system for configuring an OAM according to an embodiment of the present invention. The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. example. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

Figure 1 is a schematic diagram of OAM configuration process between PEs in a VPN network. PE1 10 indicates the source carrier edge router PE and PE2 11 indicates the sink operator edge router PE. PE2 11 issues a label to PE1 10; PE1 10 uses these labels for encapsulation and forwards the data stream to PE2 11. The direction in which the OAM performs the detection is the same as the direction in which the data stream is forwarded. In this scenario, PE1 10 acts as the active end—that is, the source end initiates the label switching path Internet packet explorer (English name is Label Switched Path Packet Internet Grope, LSP for short), and the PE2 11 acts as the passive end—that is, The sink responds to the LSP Ping response message.

It should be noted that the foregoing process is a one-way process. If the two ends of the PE1 10 and the PE 2 are mutually forwarded to form a bidirectional forwarding, the OAM is performed in both directions, and the PE at either end can serve as the source end, that is, the PE1 10 is the source PE. It is also a sink PE, and PE2 11 is a sink. The end PE is also the source PE.

Referring to FIG. 2, an embodiment of the present invention provides a method for OAM configuration, which includes the following content.

201. The source PE configures the source OAM entity, and the source OAM entity is prohibited from sending an OAM packet to the sink PE.

In all the embodiments of the present invention, the OAM detection performed by the VPN in the L3 VPN network is taken as an example for description. One end of the LSP ping request request (LSP Ping Echo Request) is the source PE; the LSP Ping Echo Reply is received passively, and one end of the LSP Ping response message is the sink PE.

As the source PE that initiates the LSP ping request message, you need to configure the source OAM sending function when configuring the source OAM entity. To prevent the source OAM entity and the sink OAM entity from being negotiated and configured, the source OAM entity sends the source OAM entity. The OAM entity and the sink OAM entity are unsuccessful. Therefore, the source OAM entity and the sink OAM entity are prohibited from being configured to the sink PE after the negotiation is configured. Send OAM packets.

For example, when the source PE and the same VPN to which the sink PE belongs are to perform OAM detection, and the source PE and the sink PE do not perform the corresponding OAM entity configuration, the source PE needs to be the source. 0 AM entity is configured. For example, the source 0 AM entity may be configured as follows: continuity detection, connectivity detection, error management signal detection, packet loss detection, delay detection, traffic detection, and the like.

202. Send, to the sinking PE, a first LSP ping request message that carries the configuration information of the source OAM entity, so that the sink PE configures the sink of the sink PE according to the source OAM entity configuration information. The end OAM entity starts the packet receiving function of the sink OAM entity, and the first LSP ping request message further includes a VPN identifier of the L3VPN, where the VPN identifier is used to identify that the sink PE device needs to perform OAM detection. VPN.

The sink PE may configure the configuration information of the sink OAM entity according to the source OAM entity configuration information. For example, when the source OAM entity configuration information includes packet loss detection, the sink PE configures the sink. The OAM entity is configured to perform packet loss detection. However, when the sink PE configures the OAM packet loss detection parameter, the sink PE may be different from the source OAM entity configuration information. Optionally, the source OAM entity configuration information may be carried by an OAM function type, a length, and a content TLV. For the OAM Function TLV, refer to [draft-ietf-mpls-lsp-ping-mpls-tp- Oam-conf-03], ^ mouth shown in Figure 3:

The C flag is used to identify continuity detection (English full name Continuity Check, English abbreviated as CC);

The V flag is used to identify connectivity detection (English full name is Connectivity Verification, English abbreviated as CV);

The F flag is used to identify the error management signal detection (English name is Fault Management Signals, English abbreviated as FMS);

The L flag is used to identify the packet loss detection ( Loss );

The D flag is used to identify the delay detection (Delay);

The T flag is used to identify traffic detection (English full name is Throughput Measurement, English abbreviated as ΤΜ).

Optionally, the first LSP ping request message further includes a virtual private network OAM forwarding equivalent class stack type, length, content (VPN OAM FEC Stack TLV), the first identifier. The VPN OAM FEC TLV includes: a target global ID (Target Global ID), a target node ID (Target Node ID), and a target route identifier (Target Route Distinguisher), and FIG. 4 shows that the VPN OAM FEC Stack TLV carries an IPv4 VPN. Figure 4 is a schematic diagram of the format of the packet when the IPv6 VPN identifier is carried in the VPN OAM FEC Stack TLV. The VPN can be identified by:

Target Global ID: : Target Node ID: : Target Route Distinguisher. Optionally, the VPN OAM FEC Stack TLV may further include: a target interface ID (Target IF ID), which is used to identify an interface that the sink PE needs to perform OAM detection; for FIG. 4, the VPN OAM FEC Stack The TLV further includes a target IPv4 prefix (Target IPv4 prefix) and a prefix length (Prefix Length), which are used to identify an IPv4 VPN route that the sink PE needs to perform OAM detection. For FIG. 5, the VPN OAM FEC Stack TLV further includes The target IPv6 prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) are used to identify that the sink PE needs to perform OAM to detect an IPv6 VPN route. The above settings of Target Global lD , Target Node lD and Target IF NUM follow the definition of [RFC6370], and the setting of Target Route Distinguisher follows the definition of [RFC4364].

Optionally, referring to FIG. 4 and FIG. 5, the format of the VPN OAM FEC Stack TLV may be: the first 1-4 bytes may indicate the Target Global ID, and the 5th-8th byte may indicate the Target Node ID, the 9th 16 bytes can indicate Target Route Distinguisher, the 17th-20th byte can indicate the Target IF ID, the 21st-24th byte can indicate the Target IPv4prefix and the Target IPv6 prefix, and the 25th byte can indicate the refix length, the 26th-28th word The section can be 0.

203. Receive a first LSP ping response message sent by the sinking PE, where the first LSP ping response message carries the configuration information of the sink OAM entity, and when determining the configuration information of the sink OAM entity and the source end When the OAM entity configuration information is matched, the function of the OAM entity sent by the source OAM entity to the sink PE is enabled.

After the sink PE configures the sink OAM entity, the first LSP ping response message is sent to the source PE. The configuration information of the sink OAM entity may not match the configuration information of the source OAM entity due to the capability of the sink PE.

Optionally, when determining that the sink OAM entity configuration information does not match the source OAM entity configuration information, adjusting the source OAM entity configuration information to match the sink OAM entity configuration information, and then, The function of the OAM packet sent by the source OAM entity to the sink PE. For example, the packet loss detection is taken as an example. Referring to FIG. 3, if the L flag of the packet loss detection is located, and the specific packet loss detection mode in the configuration information of the source OAM entity is a direct detection mode (Direct ), that is, the service text is directly tested. After receiving the configuration information of the OAM entity, the sink PE determines that the sink PE supports only the in-line detection mode (Inferred), and the sink PE can only configure the sink OAM. The configuration parameter is an Inferrer detection mode, and the sink PE sends the OAM configuration information that is supported by the sink PE to the source PE through the first LSP Ping response message, when the source PE receives the After the first LSP ping response message is sent, the OAM configuration information of the sinking PE is not matched with the configuration information of the source OAM entity, and the packet loss detection mode in the configuration information of the source OAM is adjusted to the Inferred mode. . Optionally, the sending, by the source PE, the first L SP ping request message to the sink PE further includes: an OAM management type, an OAM Administration TLV, and the OAM Administration TLV. Schematic diagram of the text format, where:

The intermediate provider router P is enabled with the OAM detection flag I, which is used to identify whether the intermediate P device OAM detection is enabled.

The alarm enable flag A is used to identify whether the OAM alarm reporting function is enabled. The two-way detection flag D is used to identify whether the two-way 0 AM detection function between the source PE and the sink PE is established.

Optionally, as shown in FIG. 6, the format of the OAM Administration TLV may be: The first and second bytes of the OAM Administration TLV may indicate the type of the OAM Administration TLV, and the third and fourth bytes of the OAM Administration TLV may indicate OAM Administration. The length of the TLV, the 5th to 8th bytes of the OAM Administration TLV can indicate the configuration information of the OAM detection.

The first bit of the 5th byte of the OAM Administration TLV (I flag in FIG. 6) indicates that the intermediate provider router P enables the OAM detection flag to identify whether the intermediate P device OAM detection is enabled, if the bit is set. Indicates that the first LSP ping request message is required to create an OAM Maintenance Entity Group Intermediate Point (MIP) entity along the transit node. The second bit of the fifth byte of the OAM Administration TLV (the A flag in FIG. 6) is used to identify whether the OAM alarm reporting function is enabled. When the bit is set, the device that receives the first LSP ping request message is configured. After the OAM entity is complete, the alarm reporting function is enabled. That is, when the OAM detects the fault, the related triggering action is generated, including the alarm. When the bit is reset, the alarm is suppressed and the subsequent actions are not triggered. The D flag in the 3rd bit of the 5th byte of the OAM Administration TLV (Fig. 6) is used to identify whether to establish a bidirectional OAM detection function between the source PE and the sink PE, the bit is set, indicating that Do two-way detection. The remaining 5th byte and the 6th, 7th, and 8th bytes are reserved, which is convenient for future OAM configuration enable extension.

Further, for the two-way detection, before the source PE sends the first LSP ping request message to the sink PE, the source PE further configures an OAM packet receiving function of the source OAM entity, and sets The bidirectional detection flag of the 0 AM Administration TLV in the first LSP ping request message is set, that is, the bidirectional detection flag is set to an enabled state, so that the sink PE further configures the sink OAM entity. The OAM file sending function is configured to start the function of sending the OAM message to the source PE by the sink OAM entity.

Optionally, for the two-way detection, the first LSP ping request message further includes: a VPN OAM source identifier type, a length, and a content (VPN OAM Source Identifier TLV), where the VPN OAM Source Identifier TLV is used to identify the source end Figure 5 is a schematic diagram of a packet format when the VPN OAM Source Identifier TLV carries an IPv4 VPN identifier, and Figure 8 is a schematic diagram of a packet format when the VPN OAM Source Identifier TLV carries an IPv6 VPN identifier. The VPN OAM Source Identifier TLV includes:

VPN OAM Source Identifier TLV type, VPN OAM Source

The information of the length of the Identifier TLV, the source global ID (Source Global ID), the source node ID (Source Node ID), and the source route identifier (Source Route Distinguisher). The source PE needs to perform OAM detection. It can be identified by:

Source Source ID: : Source Node ID: : Source Route Distinguishes Optionally, the VPN OAM Source Identifier TLV may further include: a source IF ID, which is used to identify that the source PE needs to perform OAM. For the detection of the interface, the source IPv4 prefix and the prefix length (Prefix Length) are further included to identify the IPv4 VPN route that the source PE needs to perform OAM detection; The VPN OAM FEC Stack TLV further includes a source IPv6 prefix (Source IPv6 prefix) and a prefix length (Prefix Length), and is used to identify that the sink PE needs to perform OAM to detect an IPv6 VPN route.

Optionally, referring to FIG. 7 and FIG. 8 , the format of the VPN OAM Source Identifier TLV may be: The 1-2th byte may indicate the type of the VPN OAM Source Identifier TLV, and the 3-4th byte may indicate the VPN OAM Source Identifier. The length of the TLV, the 5th-8th byte can indicate the Source Global ID, the 9th to 16th bytes can indicate the Source Node ID, the 17th to 20th bytes can indicate the Source IF ID, and the 21st to 24th bytes can indicate the Source IPv4 (in Figure 7) / IPv6 prefix (in Figure 8), the 25th byte can indicate the prefix length, and the 26th-28th byte can be 0.

Optionally, the source OAM entity and the sink OAM entity are not completed in the process of configuring the source OAM entity and the sink OAM entity. Before the configuration, the configuration of the source OAM entity and the sink OAM entity does not match, causing the sink OAM entity to report an error alarm, further triggering the sink PE or the source PE to perform an error operation according to the error alarm. The alarm enable flag of the OAM Administration TLV in the first LSP ping request message may be in a forbidden state, so that the sink PE suppresses the sink OAM entity after configuring the sink OAM entity. After the function of the OAM message is sent to the sinking PE, the function includes:

Sending a second LSP ping request message to the sink PE, where the second LSP ping request message includes an OAM Administration TLV, and the alarm enable flag in the OAM Administration TLV included in the second LSP ping request message is enabled. As shown in FIG. 9, the OAM Administration TLV carried in the second LSP ping request message includes a bit 1 for identifying an alarm enablement (may be any, as long as the enable alarm can be identified), and the remaining two-way The detection flag D and the intermediate provider router P enable the OAM detection flag I can be empty, and the sink PE enables the alarm reporting function of the sink OAM entity after receiving the second LSP ping request message. .

Optionally, the source end PE receives a second LSP ping response message sent by the sink PE, where the second LSP ping response message is a response message to the second LSP ping request message, where the sink end After receiving the second LSP ping response message, the PE may start sending an OAM detection message to the sink PE, where the source PE and the sink PE start to ping the request message for the first LSP. The VPN corresponding to the VPN ID is used for OAM detection.

After the bidirectional detection flag of the OAM Administration TLV in the first LSP ping request message is set, the sink PE configures the sink end to send the function, that is, after the configuration of the sink OAM entity, that is, And starting the detection function of the sink end to the source end direction, and setting an alarm enable flag of the 0 AM Administration TLV included in the second LSP Ping response message to an enable state, when the source The alarm reporting function of the source OAM entity is enabled when the alarm enable flag of the OAM Administration TLV is enabled in the second LSP ping response message. In addition, it should be noted that, for the process of updating the OAM configuration parameters and the process of deleting the session, the source PE and the sink PE send the LSP ping request message and the LSP ping response message carrying the relevant information. The negotiation process between the source PE and the sink PE, and the related parameters are exchanged for parameter update and session deletion.

The embodiment of the present invention provides a method for configuring an OAM. After the source PE device configures the source OAM entity, the OAM configuration information of the source PE is sent to the sink PE device by using the extended LSP ping request message, so that the The sink PE configures the sink OAM entity of the sink PE according to the source OAM configuration information, and starts the sink OAM entity to send an OAM packet to the source PE; the LSP Ping request message includes the The sinking PE needs to perform the OAM detection of the VPN identifier. After the OAM entity of the source PE and the sink PE is configured, the source OAM entity is enabled to send the OAM function to the sink PE. As a result, the OAM configuration of the source PE and the sink PE is completed. The source OAM entity and the sink OAM entity can be configured with the corresponding alarm reporting function. Because the two ends dynamically complete the OAM configuration by using the interactive LSP ping message, the errors in the manual configuration are avoided.

Referring to FIG. 10, an embodiment of the present invention provides another method for OAM configuration, which includes the following content.

301. The sinker operator edge router PE receives the first label switching path Internet packet explorer LSP ping request message that is sent by the source PE and carries the source OAM entity configuration information. The first LSP ping request message further includes three layers of virtual VPN ID of the private network L3VPN.

302. Configure a sink OAM entity according to the first LSP ping request message, and configure the sink OAM entity to detect a VPN corresponding to the VPN identifier, and start a packet receiving function of the sink OAM entity.

303. Send a first LSP ping response message to the source PE, where the first LSP ping response message carries configuration information of the sink OAM entity.

Optionally, the source OAM entity configuration information may be carried by an OAM Function TLV, which has been described in FIG. 3, and details are not described herein again.

Optionally, the first LSP ping request message further includes a virtual private network VPN OAM FEC Stack TLV, where the first LSP ping request message passes the VPN The OAM FEC Stack TLV carries the VPN identifier. The VPN OAM FEC TLV includes: a target global ID (Target Global ID), a target node ID (Target Node ID), and a target route identifier (Target Route Distinguisher), and FIG. 4 shows that the VPN OAM FEC Stack TLV carries an IPv4 VPN. Figure 5 is a schematic diagram of a packet format when the IPv6 VPN identifier is carried in the VPN OAM FEC Stack TLV. The VPN can be identified by:

Target Global ID: : Target Node ID: : Target Route Distinguisher.

Optionally, the VPN OAM FEC Stack TLV may further include: a target interface ID (Target IF ID), configured to identify an interface that the sink PE needs to perform OAM detection; for FIG. 4, the VPN OAM FEC Stack The TLV also includes a target IPv4 prefix (Target IPv4 prefix) and a prefix length (Prefix Length), which is used to identify an IPv4 VPN route that the sink PE needs to perform OAM detection. For FIG. 5, the VPN OAM FEC Stack TLV further includes The target IPv6 prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) are used to identify that the sink PE needs to perform OAM to detect an IPv6 VPN route.

The above settings of Target Global lD , Target Node lD and Target IF NUM follow the definition of [RFC6370], and the setting of Target Route Distinguisher follows the definition of [RFC4364].

Optionally, for the two-way detection, the first LSP ping request message further includes:

The VPN OAM Source Identifier TLV is used to identify the VPN identifier that the source PE needs to perform the OAM detection. FIG. 7 is a schematic diagram of the packet format when the VPN OAM Source Identifier TLV carries the IPv4 VPN identifier. FIG. 8 is a schematic diagram of a format of a message when the VPN OAM Source Identifier TLV carries an IPv6 VPN identifier.

Optionally, the VPN OAM Source Identifier TLV may further include: a source IF ID, which is used to identify an interface that the source PE needs to perform OAM detection. For FIG. 7, the method further includes The source IPv4 prefix and the prefix length (Prefix Length) are used to identify the IPv4 VPN route that the source PE needs to perform OAM detection. For FIG. 8, the VPN OAM FEC Stack TLV further includes the source IPv6. The source IPv6 prefix and the prefix length (prefix length) are used to identify that the sink PE needs to perform OAM to detect an IPv6 VPN route. Optionally, the first LSP ping request message further includes an OAM Administration TLV, and FIG. 6 is a schematic diagram of the OAM Administration TLV format, which has been described, and is not described herein again.

Optionally, when the alarm enable flag in the OAM Administration TLV in the received first LSP ping request message is in a forbidden state, the sink PE suppresses the The sinking OAM entity alarms the function, and the method further includes:

Optionally, when the bidirectional detection flag in the OAM Administration TLV that is further included in the first LSP ping request message is in an enabled state, sending a second LSP ping response message to the source PE, the second LSP The ping response message includes an OAM Administration TLV, and the alarm enable flag of the OAM Administration TLV in the second LSP ping response message is enabled, so that after the source PE receives the second LSP ping response message, Enable the alarm reporting function of the source OAM entity.

The embodiment of the present invention provides a method for configuring an OAM. After the source PE device configures the source OAM entity, the OAM configuration information of the source PE is sent to the sink PE device by using the extended LSP ping request message, so that the The sink PE configures the sink OAM entity of the sink PE according to the source OAM configuration information, and starts the sink OAM entity to send an OAM packet to the source PE; the LSP Ping request message includes the The sinking PE needs to perform the OAM detection of the VPN identifier. After the OAM entity of the source PE and the sink PE is configured, the source OAM entity is enabled to send the OAM function to the sink PE. As a result, the OAM configuration of the source PE and the sink PE is completed. The source OAM entity and the sink OAM entity can be configured with the corresponding alarm reporting function. Because the two ends dynamically complete the OAM configuration by using the interactive LSP ping message, the errors in the manual configuration are avoided. Referring to FIG. 11, an embodiment of the present invention provides a system for configuring an OAM, where the system includes: a source end PE 10 and a sink end PE 20.

The source PE10 includes:

The OAM entity unit 101 is configured to configure a source OAM entity, and the source OAM entity is prohibited from sending an OAM packet to the sink PE20.

The generating unit 102 is configured to generate, according to the source OAM entity configured by the OAM entity unit 101, a first LSP ping request message, where the first LSP ping request message carries the source MME entity configuration information, where the first The L SP Ping request message further includes a VPN identifier of the L3VPN, where the VPN identifier is used to identify a VPN that the sink PE device needs to perform OAM detection.

The sending unit 103 is configured to send the first LSP ping request message generated by the generating unit 102 to the sink PE20.

The receiving unit 104 is configured to receive a first LSP ping response message sent by the sink PE20, where the first LSP ping response message carries the sink OAM entity configuration information.

The OAM entity unit 101 is further configured to: according to the configuration information of the sink OAM entity carried in the first LSP ping response message received by the receiving unit 104, when determining the configuration information and location of the OAM entity of the sink end When the source OAM entity configuration information is matched, the function of the OAM packet sent by the source OAM entity to the sink PE20 is enabled.

The sink PE 20 includes:

The receiving unit 201 is configured to receive a first LSP ping request message that is sent by the sending unit 103 of the source PE 10 and that carries the source OAM entity configuration information, where the first LSP ping request message includes a VPN identifier of the Layer 3 virtual private network L3VPN.

The OAM entity unit 202 is configured to configure a sink OAM entity according to the first LSP ping request message received by the receiving unit 201, and start a packet receiving function of the sink OAM entity.

The generating unit 203 is configured to generate a first LSP ping response message according to the configuration information of the sink OAM entity configured by the OAM entity unit 202, where the first LSP ping response message carries the sink OAM entity configuration information.

The sending unit 204 is configured to ping the first LSP generated by the generating unit 203. The response message is sent to the source PE 10.

Optionally, the OAM entity unit 101 of the source PE 10 is further configured to: when determining that the configuration information of the sink OAM entity does not match the configuration information of the source OAM entity, adjust the configuration information of the source OAM entity. Matching with the configuration information of the sink OAM entity, the function of the OAM packet sent by the source OAM entity to the sink PE20 is enabled.

Optionally, the source OAM entity configuration information may be carried by an OAM Function TLV, and the OAM Function TLV format is as shown in FIG. 3.

Optionally, the first LSP ping request message generated by the generating unit 102 of the source PE10 further includes a VPN OAM FEC Stack TLV, where the first LSP ping request message is carried by the VPN OAM FEC Stack TLV. VPN ID. The VPN OAM FEC TLV includes: a target global ID (Target Global ID), a target node ID (Target Node ID), and a target route identifier (Target Route Distinguisher), and FIG. 4 shows that the VPN OAM FEC Stack TLV carries an IPv4 VPN. Figure 4 is a schematic diagram of the format of the packet when the IPv6 VPN identifier is carried in the VPN OAM FEC Stack TLV. The VPN can be identified by:

Target Global ID: : Target Node ID: : Target Route Distinguisher.

Optionally, the VPN OAM FEC Stack TLV may further include: a target interface ID (Target IF ID), configured to identify an interface that the sink PE 20 needs to perform OAM detection; for FIG. 4, the VPN OAM FEC Stack The TLV further includes a target IPv4 prefix (Target IPv4 prefix) and a prefix length (Prefix Length), which are used to identify the IPv4 VPN route that the sink PE20 needs to perform OAM detection. For FIG. 5, the VPN OAM FEC Stack TLV further includes The target IPv6 prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) are used to identify that the sink PE 20 needs to perform OAM to detect an IPv6 VPN route.

Optionally, the first LSP ping request message generated by the generating unit 102 of the source PE10 further includes:

0 AM Administration TLV, used to identify the VPN identifier; the 0 AM

The Administration TLV includes: The alarm enable flag is used to identify whether the OAM alarm reporting function is enabled. The two-way detection flag is used to identify whether the two-way OAM detection function between the source PE and the sink PE is established.

Before the sending unit 103 of the source PE 10 sends the first LSP ping request message to the sink PE 20, the OAM entity unit 101 of the source PE 10 is further configured to configure the OAM of the source OAM entity. Receiving a function, and setting the bidirectional detection flag of the OAM Administration TLV to an enabled state, so that the sink PE20 configures an OAM function of the sink OAM entity, and starts the sink end The OAM entity sends the function of the OAM^ message to the source PE. Correspondingly, the OAM entity unit 202 of the sink PE20 is further configured to: when the bidirectional detection flag in the OAM Administration TLV is set to an enabled state, configure the OAM packet sending of the sink OAM entity. And functioning, and starting the function of sending the OAM^ message to the source PE10 by the sinker OAM entity.

Optionally, for the two-way detection, the first LSP ping request message further includes: a VPN OAM Source Identifier TLV, where the VPN OAM Source Identifier TLV is used to identify the VPN identifier that the source PE 10 needs to perform OAM detection, and Figure 7 A schematic diagram of a packet format when the VPN OAM Source Identifier TLV carries an IPv4 VPN identifier, and FIG. 8 is a schematic diagram of a format of the IPv4 VPN identifier when the VPN OAM Source Identifier TLV carries an IPv6 VPN identifier.

Optionally, the VPN OAM Source Identifier TLV may further include: a source IF ID, which is used to identify an interface that the source PE 10 needs to perform OAM detection. For FIG. 7, the method further includes The source IPv4 prefix and the prefix length (Prefix Length) are used to identify the IPv4 VPN route that the source PE 10 needs to perform the 0 AM detection. For FIG. 8, the VPN OAM FEC Stack TLV further includes the source IPv6. The source IPv6 prefix and the prefix length (prefix length) are used to identify that the sink PE10 needs to perform OAM to detect an IPv6 VPN route.

Optionally, the first LSP ping request message further includes an OAM Administration TLV, and FIG. 6 is a schematic diagram of the format of the OAM Administration TLV, which has been described, and details are not described herein again.

Optionally, the alarm enable flag in the OAM Administration TLV in the first LSP ping request message generated by the generating unit 102 of the source PE 10 is prohibited. The state, when the alarm enable flag in the OAM Administration TLV received by the receiving unit 201 of the sink PE20 is in the forbidden state, the OAM entity unit 202 of the sink PE 20 is configured after the sink OAM entity The alarm reporting function of the sink OAM entity is suppressed.

After the OAM entity unit 101 of the source PE 10 enables the source OAM entity to send the OAM function to the sink PE, the generating unit 102 of the source PE 10 is further configured to generate the second The LSP ping request message, the alarm enable flag in the 0 AM Administration TLV included in the second LSP ping request message is an enabled state.

Correspondingly, the receiving unit 201 is further configured to receive the second LSP ping request message, where the OAM entity unit 202 of the sink PE20 is further configured to receive the second L SP according to the receiving unit 201. The ping request message enables the alarm reporting function of the sink 0 AM entity.

The sending unit 103 of the source PE 10 is further configured to send the second LSP ping request message generated by the generating unit 102 to the sink PE20, and correspondingly, the receiving unit 201 of the sink PE20 further uses Upon receiving the second LSP ping request message, the OAM entity unit 202 of the sink PE 20 is further configured to: when determining that the receiving unit 201 is further configured to receive the OAM Administration TLV included in the second LSP ping request message When the alarm enable flag is enabled, the alarm reporting function of the sink OAM entity is enabled.

Optionally, the receiving unit 104 of the source PE 10 is further configured to receive a second LSP ping response message sent by the sink PE20.

The generating unit 203 of the sink PE20 is further configured to generate a second LSP ping response message, where the alarm enable flag of the 0 AM Administration TLV included in the second LSP ping response message is Enable status.

The sending unit 204 of the sink PE20 is further configured to send the second LSP ping response message generated by the generating unit 203 to the source end PE10.

The OAM entity unit 101 of the source PE 10 is further configured to: when the alarm enable flag of the OAM Administration TLV included in the second LSP ping response message received by the receiving unit 104 is enabled, the enabling station The alarm reporting function of the source OAM entity.

The embodiment of the invention provides a system for configuring OAM, and the source end of the PE10 is configured. After the OAM entity, the OAM configuration information of the source PE 10 is sent to the sink PE20 by using the extended LSP ping request message, so that the sink PE 20 configures the sink OAM of the sink PE 20 according to the source OAM configuration information. An entity, and the sinking OAM entity is configured to send an OAM packet to the source PE 10; the LSP ping request message includes a VPN identifier that the sink PE 20 needs to perform OAM detection, when the source PE 10 and the sink After the OAM entity of the PE 20 is configured, the OAM function is enabled to send the OAM packet to the sink PE20. The OAM configuration of the source PE 10 and the sink PE 20 is completed. The entity and the sink OAM entity can be configured with the corresponding alarm reporting function. The implementation of the OAM configuration is implemented on the two ends. The two ends perform dynamic OAM configuration through the LSP ping message. An error has occurred.

Referring to FIG. 12, an embodiment of the present invention provides another OAM configuration system, where the system includes: a source PE30 and a sink PE40.

The source PE 30 includes:

The processor 301 is configured to configure the source OAM entity, and the source OAM entity is prohibited from sending the OAM^ message to the sink PE30, and is also used to generate a first LSP ping request message, the first LSP ping request The message carries the source OAM entity configuration information, and the first L SP ping request message further includes a VPN identifier of the L3 VPN, where the VPN identifier is used to identify the VPN that the sink PE 40 needs to perform OAM detection.

The sender 302 is configured to send the first LSP ping request message generated by the processor 301 to the sink PE40.

The receiver 303 is configured to receive a first LSP Ping response message sent by the sink PE 40, where the first L SP Ping response message carries the sink 0 AM entity configuration information.

The processor 301 is further configured to: according to the configuration information of the sink OAM entity carried in the first LSP ping response message received by the receiver 303, when determining the configuration information of the sink OAM entity and the source end When the OAM entity configuration information is matched, the function of the OAM packet sent by the source OAM entity to the sink PE 40 is enabled.

The sink PE40 includes:

The receiver 401 is configured to receive a first LSP ping request message that is sent by the transmitter 302 of the source PE 30 and that carries the source OAM entity configuration information. The first LSP ping request message includes a VPN identifier of the L3 VPN. The processor 402 is configured to configure, according to the first LSP ping request message received by the receiver 401, a sink OAM entity, and enable the receiving function of the sink OAM entity, and generate the first LSP ping. In response to the message, the first LSP Ping response message carries the sink OAM entity configuration information.

The transmitter 403 is configured to send the first LSP ping response message generated by the processor 402 to the source PE 30.

Optionally, the processor 301 is further configured to: when determining that the sink OAM entity configuration information does not match the source OAM entity configuration information, adjusting the source OAM entity configuration information and the sink OAM The entity configuration information is matched, and the function of the OAM packet sent by the source OAM entity to the sink PE 40 is enabled.

Optionally, the first LSP ping request message generated by the processor 301 of the source PE 30 further includes a VPN 0 AM FEC Stack TLV, where the first L SP ping request message is carried by the VPN OAM FEC Stack TLV. The VPN identifier. The VPN OAM FEC TLV includes: a target global ID (Target Global ID), a target node ID (Target Node ID), and a target route identifier (Target Route Distinguisher), and FIG. 4 shows that the VPN OAM FEC Stack TLV carries an IPv4 VPN. Figure 4 is a schematic diagram of the format of the packet when the IPv6 VPN identifier is carried in the VPN OAM FEC Stack TLV. The VPN can be identified by:

Target Global ID: : Target Node ID: : Target Route Distinguisher.

Optionally, the VPN OAM FEC Stack TLV may further include: a target interface ID (Target IF ID), configured to identify an interface that the sink PE 40 needs to perform OAM detection; for FIG. 4, the VPN OAM FEC Stack The TLV further includes a target IPv4 prefix (Target IPv4 prefix) and a prefix length (Prefix Length), which are used to identify the IPv4 VPN route that the sink PE20 needs to perform OAM detection. For FIG. 5, the VPN OAM FEC Stack TLV further includes The target IPv6 prefix information (Target IPv6 prefix) and the prefix length (Prefix Length) are used to identify that the sink PE 20 needs to perform OAM to detect an IPv6 VPN route. Optionally, the first LSP ping request message generated by the processor 301 of the source PE 30 further includes:

0 AM Administration TLV, used to identify the VPN identifier; the 0 AM Administration TLV includes:

Before the transmitter 303 of the source PE 30 sends the first LSP ping request message to the sink PE 40, the processor 301 of the source PE 30 is further configured to configure the OAM file receiving function of the source OAM entity. And setting the bidirectional detection flag of the OAM Administration TLV to an enabled state. Correspondingly, the processor 402 of the sinker PE40 is further configured to: when the bidirectional detection flag in the OAM Administration TLV is set to an enabled state, configure the sending of the sink OAM entity And functioning, and starting the function of sending the message to the source port 30 by the sink entity.

Optionally, for the two-way detection, the first LSP ping request message further includes: a VPN OAM Source Identifier TLV, where the VPN OAM Source Identifier TLV is used to identify the VPN identifier that the source PE 30 needs to perform OAM detection, and Figure 7 A schematic diagram of a packet format when the VPN OAM Source Identifier TLV carries an IPv4 VPN identifier, and FIG. 8 is a schematic diagram of a format of the IPv4 VPN identifier when the VPN OAM Source Identifier TLV carries an IPv6 VPN identifier.

Optionally, the VPN OAM Source Identifier TLV may further include: a source IF ID, which is used to identify an interface that the source PE 30 needs to perform OAM detection. For FIG. 7, the method further includes The source IPv4 prefix and the prefix length (Prefix Length) are used to identify the IPv4 VPN route that the source PE 30 needs to perform the 0 AM detection. For FIG. 8, the VPN OAM FEC Stack TLV further includes the source IPv6. The source IPv6 prefix and the prefix length (prefix length) are used to identify that the sink PE 30 needs to perform OAM to detect an IPv6 VPN route.

Optionally, the first LSP ping request message further includes an OAM Administration

TLV, FIG. 6 is a schematic diagram of the OAM Administration TLV format, which has been described and will not be described here. Optionally, the alarm enable flag in the OAM Administration TLV in the first LSP ping request message generated by the processor 301 of the source PE 30 is in a disabled state, and the OAM Administration received by the receiver 401 When the alarm enable flag in the TLV is in the forbidden state, the processor 402, after configuring the sink OAM entity, suppress the alarm on the sink OAM entity.

After the processor 301 of the source PE 30 enables the source OAM entity to send an OAM packet to the sink PE 40, the processor 301 is further configured to generate a second LSP ping request message, where The alarm enable flag in the OAM Administration TLV included in the second LSP ping request message is enabled.

Correspondingly, the receiver 401 of the sinker PE40 is further configured to receive the second LSP ping request message, where the processor 402 is further configured to use the second LSP ping request message received by the receiver 401. Enable the alarm reporting function of the sink OAM entity.

Fi.

The transmitter 302 of the source PE 30 is further configured to send the second LSP ping request message generated by the processor 301 to the sink PE 40, and the receiver 401 is further configured to receive the The second LSP ping request message is used, the processor 402 is further configured to: when determining that the receiver 401 receives the alarm enable flag in the 0 Administration TLV included in the second LSP ping request message to be enabled The alarm reporting function of the sink OAM entity is enabled.

Optionally, the receiver 303 of the source PE 30 is further configured to receive a second LSP ping response message sent by the sink PE 40.

The processor 402 of the sinker PE40 is further configured to generate a second LSP ping response message, where, in the two-way detection, the alarm enable flag of the OAM Administration TLV included in the second LSP ping response message is Can state.

The transmitter 403 of the sinker PE40 is further configured to send the second LSP ping response message generated by the processor 402 to the source PE 30.

The processor 303 of the source PE 30 is further configured to: when the alarm enable flag of the OAM Administration TLV included in the second LSP ping response message received by the receiver 303 is enabled, enable the Alarm reporting function of the source OAM entity.

The embodiment of the present invention provides a system for configuring an OAM. After the source end OAM entity is configured with the source OAM entity, the source end PE 30 sends the OAM configuration information of the source PE 30 to the sink PE 40 device to make the sink. End PE40 according to the source The OAM configuration information is configured to configure a sink OAM entity of the sink PE 40, and the sink OAM entity is configured to send an OAM packet to the source PE 30. The LSP Ping request message includes the OAM detection of the sink PE 40. After the OAM entity of the source PE 30 and the sink PE 40 is configured, the OAM entity is enabled to send an OAM packet to the sink PE 40, thereby completing the source PE 30. The OAM configuration works with the sinking PE40. The source OAM entity and the sink OAM entity can be configured with the corresponding alarm reporting function. The implementation of the OAM configuration is implemented on the two ends. To complete the OAM configuration dynamically, avoiding errors in manual configuration.

The source PE 30 and the sink PE 40 may be routers or switches.

Optionally, the processor 301 of the source PE30 and the processor 402 of the sink PE40 may be a central processing unit (referred to as a Central Processing Unit in English, abbreviated as CPU in English). The receiver 303, the transmitter 302, the receiver 401, and the transmitter 403 of the source PE 30 may include a common physical interface, and the physical interface may be an Ethernet interface or an asynchronous transmission mode (English name is Asynchronous). Transfer Mode, English abbreviated as ATM) interface. The receiver 303, the processor 301, and the transmitter 302 of the source PE 30 may be integrated into one or more independent circuits or hardware, such as: an application specific integrated circuit (English called Application Specific Integrated Circuit, ASIC for short). The receiver 401, the processor 402, and the transmitter 403 of the sink PE 40 may be integrated into one or more independent circuits or hardware, such as an ASIC.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to the program instructions. The foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The foregoing storage medium includes: a read-only memory (referred to as a read-only memory in English), a RAM, a magnetic disk, or an optical disk, and the like, which can store program codes. The present invention and the beneficial effects brought about by the present invention are described in detail with reference to the foregoing embodiments, and those skilled in the art should understand that the technical solutions described in the foregoing embodiments can still be performed. Modifications, or equivalents to some of the technical features, which are not intended to limit the nature of the corresponding technical solutions.

Claims

Rights request

1. A method of operating, managing and maintaining OAM configuration, characterized by including:

The source operator edge router PE configures the source OAM entity, and prohibits the source OAM entity from sending OAM messages to the sink PE;

Send the first label switched path Internet packet explorer LSP Ping request message carrying the source OAM entity configuration information to the sink PE, so that the sink PE configures the source OAM entity configuration information according to the source OAM entity configuration information. The sink OAM entity of the sink PE starts the message receiving function of the sink OAM entity. The first LSP Ping request message also includes the VPN identifier of the three-layer virtual private network L3 VPN. The VPN identifier is used to identify The destination PE equipment requires a VPN for OAM detection;

Receive the first LSP Ping response message sent by the sink PE. The first LSP Ping response message carries the sink OAM entity configuration information. When it is determined that the sink OAM entity configuration information is consistent with the source OAM entity When the configuration information matches, the source OAM entity is enabled to send an OAM message to the sink PE.

2. The method according to claim 1, characterized in that it includes:

When it is determined that the sink OAM entity configuration information does not match the source OAM entity configuration information, adjust the source OAM entity configuration information to match the sink OAM entity configuration information, and enable the source OAM. The function of an entity sending OAM messages to the sink PE.

3. The method according to claim 1 or 2, characterized in that the first LSP Ping request message forwards the equivalent class stack type, length, and content VPN OAM FEC TLV through the virtual private network OAM to carry the VPN identifier, The VPN OAM FEC TLV includes:

Target global ID Target Global ID, target node ID Target Node ID and target route identification Target Route Distinguishes

4. The method according to claim 3, wherein the VPN OAM FEC TLV further includes:

Target interface ID Target IF ID is used to identify the interface on which the sink PE needs to perform OAM detection;

Target IP address information is used to identify that the destination PE needs to perform OAM detection routing.

5. The method according to any one of claims 1 to 4, characterized in that the first LSP Ping request message also includes an OAM administration type, length, and content OAM Administration TLV, and the OAM Administration TLV includes: The alarm enable flag is used to identify whether the OAM alarm reporting function is enabled; the bidirectional detection flag is used to identify whether the bidirectional OAM detection function between the source PE and the sink PE is established.

6. The method according to claim 5, characterized in that, before sending the first LSP Ping request message to the destination PE, the method includes:

The source PE configures the OAM message receiving function of the source OAM entity, and sets the bidirectional detection flag of the OAM Administration TLV to the enabled state, so that the sink PE configures the sink OAM entity. OAM message sending function, and starts the function of the sink end OAM entity sending an OAM message to the source end PE; The first LSP Ping request message also includes VPN OAM source identification type, length, content VPN OAM Source Identifier TLV. The VPN OAM Source Identifier TLV is used to identify the VPN identifier that the source PE needs to perform OAM detection. The VPN OAM Source Identifier TLV includes:

Source global ID Source Global ID, source node ID Source Node ID and source route identifier Source Route Distinguisher information.

7. The method according to claim 6, wherein the VPN OAM Source Identifier TLV further includes:

Source interface ID Source IF ID is used to identify the interface on which the source PE needs to perform OAM detection;

Source IP address information is used to identify that the source PE needs to perform OAM detection routing.

8. The method according to any one of claims 5 to 7, characterized in that, the alarm enable flag in the OAM Administration TLV contained in the first LSP Ping request message is in a disabled state, so that the sink After configuring the sink OAM entity, the end PE suppresses the alarm reporting function of the sink OAM entity, and after enabling the function of the source OAM entity to send an OAM message to the sink PE, The method includes: sending a second LSP Ping request message to the destination PE, where the second LSP Ping request message includes the OAM Administration TLV, and the alarm enable flag in the OAM Administration TLV is in an enabled state, so that all Shusu Duan After receiving the second LSP Ping request message, the PE enables the alarm reporting function of the destination OAM entity.

9. The method according to claim 8, characterized in that it includes:

Receive a second LSP Ping response message sent by the destination PE, where the second LSP Ping response message is a response message to the second LSP Ping request message;

When the alarm enable flag of the OAM Administration TLV contained in the second LSP Ping response message is in the enabled state, the alarm reporting function of the source OAM entity is enabled.

10. A method of operating, managing and maintaining OAM configuration, characterized by including:

The destination operator edge router P E receives the first label switching path Internet packet explorer LSP Ping request message carrying the source end 0 AM entity configuration information sent by the source end P E; the first LSP Ping request message also includes a three-layer virtual private VPN logo of network L3VPN;

Configure the sink OAM entity according to the first LSP Ping request message, configure the sink OAM entity to detect the VPN corresponding to the VPN identifier, and activate the message receiving function of the sink OAM entity;

Send a first LSP Ping response message to the source PE, where the first LSP Ping response message carries the configuration information of the destination OAM entity.

11. The method according to claim 10, characterized in that the first LSP Ping request message also includes OAM management type, length, content OAM Administration TLV, and the OAM Administration TLV includes:

The alarm enable flag is used to identify whether the OAM alarm reporting function is enabled; the bidirectional detection flag is used to identify whether the bidirectional OAM detection function between the source PE and the sink PE is established;

When the bidirectional detection flag is set to the enabled state, the sink PE configures the OAM message sending function of the sink OAM entity, and starts the sink OAM entity to send OAM to the source PE. ^Gen text function.

12. The method according to claim 10 or 11, characterized in that, when the alarm enable flag in the OAM Administration TLV in the received first LSP Ping request message is in a disabled state, the sink PE After configuring the sink OAM entity, suppressing the alarm reporting function of the sink OAM entity, the method further includes: Receive the second LSP Ping request message sent by the source PE, and when the alarm enable flag of the OAM Administration TLV contained in the second LSP Ping request message is in the enabled state, enable the alarm of the sink OAM entity. Reporting function.

13. The method according to claim 12, comprising: sending a second LSP Ping response message to the source PE, where the second LSP Ping response message contains the OAM Administration TLV. When the first LSP When the bidirectional detection flag in the OAM Administration TLV also included in the Ping request message is in the enabled state, the alarm enable flag of the OAM Administration TLV in the second LSP Ping response message is in the enabled state, so that the source PE After receiving the second LSP Ping response message, enable the alarm reporting function of the source OAM entity.

14. A source-end operator edge router PE, characterized in that it includes: an OAM entity unit, used to configure the source-end OAM entity, and disable the source-end

The OAM entity sends an OAM message to the sink PE;

Generating unit, configured to generate a first LSP Ping request message according to the source OAM entity configured by the OAM entity unit, where the first LSP Ping request message carries the source OAM entity configuration information, and the first LSP Ping request The message also includes the VPN identifier of the Layer 3 virtual private network L3VPN. The VPN identifier is used to identify the VPN for which the destination PE device needs to perform OAM detection;

A sending unit, configured to send the first LSP Ping request message generated by the generating unit to the sink PE, so that the sink PE configures the sink OAM entity according to the first LSP Ping request message, and starts all Describes the message receiving function of the sink-end OAM entity.

•6 fidagger . ,

A receiving unit configured to receive the first LSP Ping response message sent by the sink PE, where the first LSP Ping response message carries the sink OAM entity configuration information of the sink PE;

The OAM entity unit is also configured to enable the source OAM entity to send an OAM message to the sink PE when it is determined that the sink OAM entity configuration information matches the source OAM entity configuration information. Function.

15. The source PE according to claim 14, wherein the OAM entity unit is further configured to adjust when it is determined that the sink OAM entity configuration information does not match the source OAM entity configuration information. The source OAM entity configuration information matches the sink OAM entity configuration information, enabling the source OAM entity to The function of the sink PE to send OAM messages.

16. The source PE according to claim 14 or 15, characterized in that the first LSP Ping request message generated by the generating unit further includes:

OAM management type, length, content OAM Administration TLV, used to identify the VPN identifier; the OAM Administration TLV includes:

Before the sending unit sends the first LSP Ping request message to the sink PE, the OAM entity unit is also used to configure the OAM message receiving function of the source OAM entity and set the OAM Administration The bidirectional detection flag of the TLV is in an enabled state, so that the sink PE configures the OAM message sending function of the sink OAM entity and starts the sink OAM entity to send an OAM message to the source PE. function of text.

17. The source PE according to claim 16, characterized in that, the alarm enable flag in the OAM Administration TLV in the first LSP Ping request message generated by the generating unit is in a disabled state, so that the After configuring the sink OAM entity, the sink PE suppresses the alarm reporting function of the sink OAM entity;

After the OAM entity unit enables the source OAM entity to send an OAM message to the sink PE, the generating unit is also used to generate a second LSP Ping request message, and the second LSP Ping The alarm enable flag in the OAM Administration TLV contained in the request message is enabled;

The sending unit is also configured to send the second LSP Ping request message generated by the generating unit to the destination PE; so that the destination PE , enable the alarm reporting function of the sink-end OAM entity.

18. The source PE according to claim 17, characterized in that it includes: the receiving unit, further configured to receive the second LSP Ping response message sent by the sink PE;

The OAM entity unit is also configured to enable the source OAM entity when the alarm enable flag of the OAM Administration TLV contained in the second LSP Ping response message received by the receiving unit is in an enabled state. Alarm reporting function.

19. A sink-end operator edge router PE, which is characterized by including: A receiving unit configured to receive a first Label Switched Path Internet Packet Explorer LSP Ping request message sent by the source PE that carries the source OAM entity configuration information; the first LSP Ping request message includes the VPN of the three-layer virtual private network L3VPN logo;

The OAM entity unit is configured to configure the sink OAM entity according to the first LSP Ping request message received by the receiving unit, and configure the sink OAM entity to detect the VPN corresponding to the VPN identifier, and start the Gen text receiving function of the sink end OAM entity;

A generating unit configured to generate a first LSP Ping response message according to the sink OAM entity configured by the OAM entity unit, where the first LSP Ping response message carries the configuration information of the sink OAM entity;

A sending unit, configured to send the first LSP Ping response message generated by the generating unit to the source PE.

20. The sink PE according to any one of claims 19, characterized in that, the first LSP Ping request message received by the receiving unit also includes OAM management type, length, content OAM Administration TLV, The OAM

Administration TLVs include:

The OAM entity unit is also configured to configure the OAM message sending function of the sink-side OAM entity and start the sink-side OAM when the bidirectional detection flag in the OAM Administration TLV is set to the enabled state. The function of the entity sending OAM messages to the source PE.

21. The sink PE according to claim 19 or 20, characterized in that when the alarm enable flag in the OAM Administration TLV received by the receiving unit is in a disabled state, the OAM entity unit configures the After describing the sink-end OAM entity, suppress the alarm function of the sink-end OAM entity;

The receiving unit is also configured to receive the second LSP Ping request message, the second LSP Ping request message contains the OAM Administration TLV, and the alarm enable flag in the OAM Administration TLV is enabled. state;

The OAM entity unit is further configured to enable the alarm reporting function of the sink end OAM entity according to the second LSP Ping request message received by the receiving unit.

22. The sink PE according to claim 21, characterized by comprising: the generating unit, further configured to generate a second LSP Ping response message; wherein, during bidirectional detection, in the second LSP Ping response message The alarm enable flag of the included OAM Administration TLV is in the enabled state;

The sending unit is also configured to send the second LSP Ping response message generated by the generating unit to the source PE; so that after the source PE receives the second LSP Ping response message, Enable the alarm reporting function of the source OAM entity.

23. An OAM configuration system, characterized by including:

The source operator edge router PE according to any one of claims 14 to 18, and the sink operator edge router PE according to any one of claims 19 to 22.