CN103580894A

Movatterモバイル変換

Info

Publication number: CN103580894A
Application number: CN201210268576.7A
Authority: CN
Inventors: 古锐; 董杰; 郑莲淑
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2012-07-31
Filing date: 2012-07-31
Publication date: 2014-02-12
Anticipated expiration: 2032-07-31
Also published as: WO2014019348A1; CN103580894B

Abstract

Translated fromChinese

本发明实施例提供一种OAM配置的方法、设备及系统。该方法包括：源端PE配置源端OAM实体，禁止源端OAM实体向宿端PE发送OAM报文；向宿端PE发送携带源端OAM实体配置信息的第一LSP Ping请求消息；接收宿端PE发送的携带宿端OAM实体配置信息的第一LSP Ping响应消息，当宿端OAM实体配置信息与源端OAM实体配置信息匹配时，使能源端OAM实体向宿端PE发送OAM报文的功能。本发明实施例还提供了源端PE、宿端PE及OAM配置系统，通过本发明实施例提供的技术方案，减少源端和宿端配置OAM的工作量，且两端通过交互LSP Ping消息动态的完成OAM配置，避免了手动配置中出现的错误。

Embodiments of the present invention provide a method, device and system for OAM configuration. The method includes: the source PE configures the source OAM entity, prohibits the source OAM entity from sending OAM messages to the sink PE; sends the first LSP Ping request message carrying the source OAM entity configuration information to the sink PE; receives the sink The first LSP Ping response message sent by the PE that carries the configuration information of the sink OAM entity, when the configuration information of the sink OAM entity matches the configuration information of the source OAM entity, enables the source OAM entity to send an OAM message to the sink PE . The embodiment of the present invention also provides a source PE, a sink PE, and an OAM configuration system. Through the technical solution provided by the embodiment of the present invention, the workload of OAM configuration at the source and sink is reduced, and the two ends exchange LSP Ping messages dynamically OAM configuration can be completed quickly, avoiding errors in manual configuration.

Description

Translated fromChinese

操作、管理和维护OAM配置的方法、设备及系统Method, device and system for operating, managing and maintaining OAM configuration

技术领域technical field

本发明涉及网络通信领域，尤其涉及一种OAM配置的方法、设备及系统。The present invention relates to the field of network communication, in particular to an OAM configuration method, device and system.

背景技术Background technique

完善的操作、管理和维护(英文全称为Operations,Administrationand Maintenance，英文简称为OAM)功能是电信级网络的重要标志对于运营商来说是极端重要的，OAM可以降低运营商的操作复杂度和运维成本，可以增强运营商网络的可用性，还可以帮助运营商网络验证与用户签订的SLA(Service-Level Agreement，服务等级协议)。Perfect operation, management and maintenance (English full name is Operations, Administration and Maintenance, English abbreviation OAM) function is an important symbol of carrier-class network. It is extremely important for operators. OAM can reduce the operator's operational complexity and operation Maintenance costs can enhance the availability of the operator's network, and can also help the operator's network verify the SLA (Service-Level Agreement) signed with the user.

OAM机制主要包括故障管理(Fault Management)、性能监控(Performance Monitoring)和保护倒换(Protection Switching)三个方面。其中故障管理又可分为故障检测(Fault Detection)、故障验证(FaultVerification)、故障定位(Fault Localization)和故障通告(FaultNotification)这四个方面；而性能监控主要提供对丢包、时延和抖动这三个指标的监测。The OAM mechanism mainly includes three aspects: Fault Management, Performance Monitoring and Protection Switching. Among them, fault management can be divided into four aspects: fault detection (Fault Detection), fault verification (Fault Verification), fault localization (Fault Localization) and fault notification (Fault Notification). Performance monitoring mainly provides information on packet loss, delay and jitter. Monitoring of these three indicators.

对于网际协议/多协议标记交换(英文全称为InternetProtocol/Multiprotocol Label Switching，英文简称为IP/MPLS)和以太网(Ethernet)网络，目前主要有较为完善的OAM机制主要是EthernetOAM和面向连接的分组交换网络技术(英文全称为Transport Profilefor MPLS，英文简称为MPLS-TP)OAM。前者包括IEEE802.3ah、IEEE802.1ag、ITU-T Y.1731以及一些城域以太论坛(英文全称为MetroEthernet Forum，英文简称为MEF)的标准，后者由IETF所定义的一系列标准组成。For Internet Protocol/Multiprotocol Label Switching (English full name is Internet Protocol/Multiprotocol Label Switching, English abbreviation is IP/MPLS) and Ethernet (Ethernet) networks, there are relatively complete OAM mechanisms, mainly EthernetOAM and connection-oriented packet switching. Network technology (full English name is Transport Profile for MPLS, English abbreviation is MPLS-TP) OAM. The former includes IEEE802.3ah, IEEE802.1ag, ITU-T Y.1731 and some standards of the Metro Ethernet Forum (MetroEthernet Forum in English, MEF in English for short), and the latter consists of a series of standards defined by IETF.

虚拟专用网络(英文全称为Virtual Private Network，英文简称为VPN)是运营商通过其公网向用户提供的虚拟专有网络，即在用户的角度VPN是用户的一个专有网络。对于运营商来说公网包括公共的骨干网和公共的运营商边界设备。地理上彼此分离的VPN成员站点通过客户端设备(CPE)连接到对应的运营商边缘路由器(英文全称为Provider Edge,英文简称为为PE)，通过运营商的公网组成客户的VPN网络。Virtual Private Network (English full name is Virtual Private Network, English abbreviation is VPN) is a virtual private network provided by operators to users through their public network, that is, from the user's point of view, VPN is a private network of users. For operators, the public network includes public backbone networks and public operator border devices. VPN member sites that are geographically separated from each other are connected to the corresponding operator's edge router (provider edge in English, PE in English) through the client equipment (CPE), and form the customer's VPN network through the operator's public network.

三层虚拟专用网(英文全称为Layer 3 Virtual Private Network，英文简称为L3VPN)，是一种基于MPLS的三层VPN技术。在L3VPN网络中，现有技术中配置OAM对VPN进行检测时，需要手动创建源端PE和宿端PE的OAM实体，并分别对源端PE和宿端PE的OAM实体进行参数配置，在这个过程中要人工保证宿端PE的OAM实体的配置参数和源端PE的OAM实体的配置参数一致，这样不仅使得OAM配置的工作量较大，而且容易出现配置错误。Layer 3 Virtual Private Network (English full name is Layer 3 Virtual Private Network, English abbreviation is L3VPN), is a three-layer VPN technology based on MPLS. In the L3VPN network, when configuring OAM to detect VPN in the prior art, it is necessary to manually create the OAM entities of the source PE and the sink PE, and configure the parameters of the OAM entities of the source PE and the sink PE respectively. During the process, it is necessary to manually ensure that the configuration parameters of the OAM entity of the sink PE are consistent with the configuration parameters of the OAM entity of the source PE. This not only makes the OAM configuration heavy, but also prone to configuration errors.

发明内容Contents of the invention

本发明的实施例提供一种OAM配置的方法、设备及系统，以解决在L3VPN组网中PE设备配置OAM对VPN进行检测时，人工配置导致的配置工作量大及容易出现配置错误的问题。Embodiments of the present invention provide an OAM configuration method, device, and system to solve the problems of heavy configuration workload and easy configuration errors caused by manual configuration when PE devices are configured with OAM to detect VPNs in L3VPN networking.

第一个方面，提供了一种OAM配置的方法，所述方法包括：In the first aspect, a method for OAM configuration is provided, and the method includes:

源端运营商边缘路由器PE配置源端OAM实体，并且禁止所述源端OAM实体向所述宿端PE发送OAM报文；The source-end operator edge router PE configures the source-end OAM entity, and prohibits the source-end OAM entity from sending OAM messages to the sink-end PE;

向所述宿端PE发送携带所述源端OAM实体配置信息的第一标签交换路径因特网包探索器LSP Ping请求消息，以使得所述宿端PE根据所述源端OAM实体配置信息配置所述宿端PE的宿端OAM实体，启动所述宿端OAM实体的报文接收功能，所述第一LSP Ping请求消息还包括三层虚拟专用网L3VPN的VPN标识，所述VPN标识用于标识所述宿端PE设备需要进行OAM检测的VPN；sending a first Label Switched Path Internet Packet Explorer LSP Ping request message carrying configuration information of the source-end OAM entity to the sink-end PE, so that the sink-end PE configures the The sink-end OAM entity of the sink-end PE starts the message receiving function of the sink-end OAM entity, and the first LSP Ping request message also includes the VPN identifier of the three-layer virtual private network L3VPN, and the VPN identifier is used to identify the The VPN on which the sink PE device needs to perform OAM detection;

接收所述宿端PE发送的第一LSP Ping响应消息，所述第一LSPPing响应消息携带所述宿端OAM实体配置信息，当确定所述宿端OAM实体配置信息与所述源端OAM实体配置信息匹配时，使能所述源端OAM实体向所述宿端PE发送OAM报文的功能。Receiving the first LSP Ping response message sent by the sink-end PE, the first LSPPing response message carrying the sink-end OAM entity configuration information, when determining that the sink-end OAM entity configuration information is consistent with the source-end OAM entity configuration When the information matches, enable the function of the source-end OAM entity to send an OAM message to the sink-end PE.

在所述第一方面的第一种可能的实现方式中，所述方法还包括：In a first possible implementation manner of the first aspect, the method further includes:

当确定所述宿端OAM实体配置信息与所述源端OAM实体配置信息不匹配时，调整所述源端OAM实体配置信息与所述宿端OAM实体配置信息匹配，使能所述源端OAM实体向所述宿端PE发送OAM报文的功能。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 A function of the entity sending an OAM packet to the sink PE.

在所述第一方面或所述第一方面的第一种可能的实现方式中，还提供了所述第一方面的第二种可能的实现方式，所述第一LSP Ping请求消息通过虚拟专用网OAM转发等价类栈类型、长度、内容VPNOAM FEC TLV携带所述VPN标识，所述VPN OAM FEC TLV包括：In the first aspect or the first possible implementation of the first aspect, a second possible implementation of the first aspect is also provided, the first LSP Ping request message is sent through the virtual private Network OAM forwarding equivalent class stack type, length, content VPNOAM FEC TLV carries the VPN identifier, and the VPN OAM FEC TLV includes:

目标全球ID Target Global ID、目标节点ID Target Node ID及目标路由标识Target Route Distinguisher。Target Global ID Target Global ID, Target Node ID Target Node ID and Target Route Distinguisher.

在所述第一方面的第二种可能的实现方式中的第三种可能的实现方式，所述VPN OAM FEC TLV还包括：In the third possible implementation in the second possible implementation of the first aspect, the VPN OAM FEC TLV also includes:

目标接口ID Target IF ID，用于标识所述宿端PE需要进行OAM检测的接口：Target interface ID Target IF ID, used to identify the interface on which the sink PE needs to perform OAM detection:

目标IP地址信息，用于标识所述宿端PE需要进行OAM检测路由。The target IP address information is used to identify that the sink PE needs to perform OAM detection routing.

在所述第一方面或所述第一方面的前述任意一种可能的实现方式中，还提供了所述第一方面的第第四种可能的实现方式，所述第一LSPPing请求消息中还包括OAM管理类型、长度、内容OAMAdministration TLV，所述OAM Administration TLV包括：In the first aspect or any one of the foregoing possible implementation manners of the first aspect, a fourth possible implementation manner of the first aspect is also provided, and the first LSPPing request message further includes Including OAM management type, length, content OAMAdministration TLV, said OAM Administration TLV includes:

告警使能标志，用于标识是否使能OAM告警上报功能；The alarm enable flag is used to identify whether to enable the OAM alarm reporting function;

双向检测标志，用于标识是否建立所述源端PE和宿端PE之间的双向OAM检测功能。The bidirectional detection flag is used to identify whether to establish the bidirectional OAM detection function between the source PE and the sink PE.

在所述第一方面的第四种可能的实现方式中，还提供了所述第一方面的第五种可能的实现方式，所述方法还包括：In the fourth possible implementation manner of the first aspect, a fifth possible implementation manner of the first aspect is also provided, and the method further includes:

向所述宿端PE发送所述第一LSP Ping请求消息之前，包括：Before sending the first LSP Ping request message to the sink PE, including:

所述源端PE配置源端OAM实体的OAM报文接收功能，并设置所述OAM Administration TLV的双向检测标志为使能状态，以使得所述宿端PE配置所述宿端OAM实体的OAM报文发送功能，并启动所述宿端OAM实体向所述源端PE发送OAM报文的功能；The source-end PE configures the OAM packet receiving function of the source-end OAM entity, and sets the bidirectional detection flag of the OAM Administration TLV to an enabled state, so that the sink-end PE configures the OAM packet of the sink-end OAM entity text sending function, and start the function of the sink OAM entity sending the OAM message to the source PE;

所述第一LSP Ping请求消息还包括VPN OAM源标识类型、长度、内容VPN OAM Source Identifier TLV，所述VPN OAM Source IdentifierTLV用于标识所述源端PE需要进行OAM检测的VPN标识，其中，所述VPN OAM Source Identifier TLV包括：The first LSP Ping request message also includes VPN OAM source identification type, length, content VPN OAM Source Identifier TLV, and the VPN OAM Source Identifier TLV is used to identify the VPN identification that the source PE needs to perform OAM detection, wherein the The above VPN OAM Source Identifier TLV includes:

源端全球ID Source Global ID、源端节点ID Source Node ID及源端路由标识Source Route Distinguisher的信息。Information about Source Global ID, Source Global ID, Source Node ID, and Source Route Distinguisher.

在所述第一方面的第五种可能的实现方式中，还提供了所述第一方面的第六种可能的实现方式，所述VPN OAM Source Identifier TLV还包括：In the fifth possible implementation of the first aspect, a sixth possible implementation of the first aspect is also provided, and the VPN OAM Source Identifier TLV also includes:

源端接口ID Source IF ID，用于标识所述源端PE需要进行OAM检测的接口；Source interface ID Source IF ID, used to identify the interface that the source PE needs to perform OAM detection;

源端IP地址信息，用于标识所述源端PE需要进行OAM检测路由。The source IP address information is used to identify that the source PE needs to perform OAM detection routing.

在所述第一方面的第四种或第五种或第六种可能的实现方式中，还提供了所述第一方面的第七种可能的实现方式，所述第一LSP Ping请求消息中包含的OAM Administration TLV中的告警使能标志为禁止状态，以使得所述宿端PE在配置所述宿端OAM实体后，抑制所述宿端OAM实体告警上报功能，在所述使能所述源端OAM实体向所述宿端PE发送OAM报文的功能之后，包括：In the fourth or fifth or sixth possible implementation of the first aspect, a seventh possible implementation of the first aspect is also provided, in the first LSP Ping request message The alarm enable flag in the included OAM Administration TLV is disabled, so that the sink PE suppresses the alarm reporting function of the sink OAM entity after configuring the sink OAM entity. After the source-end OAM entity sends the OAM message to the sink-end PE, it includes:

向所述宿端PE发送第二LSP Ping请求消息，所述第二LSP Ping请求消息包含所述OAM Administration TLV，所述OAMAdministration TLV中的告警使能标志为使能状态，以使得所述宿端PE在接收到所述第二LSP Ping请求消息后，使能所述宿端OAM实体的告警上报功能。Send a second LSP Ping request message to the sink PE, the second LSP Ping request message includes the OAM Administration TLV, and the alarm enable flag in the OAMAdministration TLV is in an enabled state, so that the sink After receiving the second LSP Ping request message, the PE enables the alarm reporting function of the sink OAM entity.

在所述第一方面的第七种可能的实现方式中，还提供了所述第一方面的第第八种可能的实现方式，所述方法还包括：In the seventh possible implementation manner of the first aspect, an eighth possible implementation manner of the first aspect is also provided, and the method further includes:

接收所述宿端PE发送的第二LSP Ping响应消息，所述第二LSPPing响应消息是针对所述第二LSP Ping请求消息的响应消息；Receiving a second LSP Ping response message sent by the sink PE, where the second LSPPing response message is a response message to the second LSP Ping request message;

当所述第二LSP Ping响应消息包含的OAM Administration TLV的告警使能标志为使能状态时，使能所述源端OAM实体的告警上报功能。When the alarm enable flag of the OAM Administration TLV contained in the second LSP Ping response message is in an enabled state, enable the alarm reporting function of the source OAM entity.

第二方面，提供了一种OAM配置的方法，所述方法包括：In a second aspect, a method for OAM configuration is provided, and the method includes:

宿端运营商边缘路由器PE接收源端PE发送的携带源端OAM实体配置信息的第一标签交换路径因特网包探索器LSP Ping请求消息；所述第一LSP Ping请求消息还包括三层虚拟专用网L3VPN的VPN标识；The sink end operator edge router PE receives the first label switched path Internet packet explorer LSP Ping request message carrying the source end OAM entity configuration information sent by the source end PE; the first LSP Ping request message also includes a three-layer virtual private network VPN ID of L3VPN;

根据所述第一LSP Ping请求消息配置宿端OAM实体，并配置所述宿端OAM实体对所述VPN标识对应的VPN进行检测，启动所述宿端OAM实体的报文接收功能；Configure the sink OAM entity according to the first LSP Ping request message, and configure the sink OAM entity to detect the VPN corresponding to the VPN identifier, and start the message receiving function of the sink OAM entity;

向所述源端PE发送第一LSP Ping响应消息，所述第一LSP Ping响应消息携带所述宿端OAM实体的配置信息。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.

在所述第二方面的第一种可能的实现方式中，所述第一LSP Ping请求消息中还包括OAM管理类型、长度、内容OAM AdministrationTLV，所述OAM Administration TLV包括：In the first possible implementation of the second aspect, the first LSP Ping request message also includes OAM management type, length, content OAM AdministrationTLV, and the OAM Administration TLV includes:

双向检测标志，用于标识是否建立所述源端PE和宿端PE之间的双向OAM检测功能：The bidirectional detection flag is used to identify whether to establish the bidirectional OAM detection function between the source PE and the sink PE:

当所述双向检测标志设置为使能状态时，所述宿端PE配置所述宿端OAM实体的OAM报文发送功能，并启动所述宿端OAM实体向所述源端PE发送OAM报文的功能。When the bidirectional detection flag is set to the enable state, the sink-end PE configures the OAM message sending function of the sink-end OAM entity, and starts the sink-end OAM entity to send an OAM message to the source-end PE function.

在所述第二方面或所述第一方面的第一种可能的实现方式中，还提供了所述第二方面的第二种可能的实现方式，所述当接收到的所述第一LSP Ping请求消息中的OAM Administration TLV中的告警使能标志为禁止状态时，所述宿端PE在配置所述宿端OAM实体后，抑制所述宿端OAM实体告警上报功能，所述方法还包括：In the second aspect or the first possible implementation of the first aspect, a second possible implementation of the second aspect is also provided, when the received first LSP When the alarm enable flag in the OAM Administration TLV in the Ping request message is in a prohibited 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 :

接收所述源端PE发送的第二LSP Ping请求消息，当所述第二LSPPing请求消息中包含的OAM Administration TLV的告警使能标志为使能状态，使能所述宿端OAM实体的告警上报功能。Receive the second LSP Ping request message sent by the source PE, when the alarm enable flag of the OAM Administration TLV contained in the second LSPPing request message is in an enabled state, enable the alarm reporting of the sink OAM entity Function.

在所述第二方面的第二种可能的实现方式中，还提供了所述第二方面的第三种可能的实现方式，向所述源端PE发送第二LSP Ping响应消息，所述第二LSP Ping响应消息包含OAM Administration TLV，当所述第一LSP Ping请求消息中还包括的OAM Administration TLV中的双向检测标志为使能状态时，所述第二LSP Ping响应消息中OAMAdministration TLV的告警使能标志为使能状态，以使得所述源端PE在收到所述第二LSP Ping响应消息后，使能所述源端OAM实体的告警上报功能。In the second possible implementation of the second aspect, a third possible implementation of the second aspect is also provided, sending a second LSP Ping response message to the source PE, the first The second LSP Ping response message contains the OAM Administration TLV, and when the bidirectional detection flag in the OAM Administration TLV included in the first LSP Ping request message is enabled, the alarm of the OAMAdministration TLV in the second LSP Ping response message The enabling flag is enabled, so that the source PE enables the alarm reporting function of the source OAM entity after receiving the second LSP Ping response message.

第三方面，提供了一种源端PE，其特征在于，包括：In a third aspect, a source PE is provided, which is characterized in that it includes:

OAM实体单元，用于配置源端OAM实体，并且禁止所述源端OAM实体向所述宿端PE发送OAM报文；The OAM entity unit is configured to configure a source-end OAM entity, and prohibit the source-end OAM entity from sending an OAM message to the sink-end PE;

生成单元，用于根据所述OAM实体单元配置的源端OAM实体生成第一LSP Ping请求消息，所述第一LSP Ping请求消息携带所述源端OAM实体配置信息，所述第一LSP Ping请求消息还包括三层虚拟专用网L3VPN的VPN标识，所述VPN标识用于标识所述宿端PE设备需要进行OAM检测的VPN；A generating unit configured to generate a first LSP Ping request message according to the source OAM entity configured by the OAM entity unit, the first LSP Ping request message carrying configuration information of the source OAM entity, and the first LSP Ping request The message also includes the VPN identification of the three-layer virtual private network L3VPN, and the VPN identification is used to identify the VPN that the sink PE device needs to perform OAM detection;

发送单元，用于将所述生成单元生成的所述第一LSP Ping请求消息发送到宿端PE，以使得所述宿端PE根据所述第一LSP Ping请求消息配置宿端OAM实体，启动所述宿端OAM实体的报文接收功能；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 the Describe the message receiving function of the sink OAM entity;

接收单元，用于接收所述宿端PE发送的第一LSP Ping响应消息，所述第一LSP Ping响应消息携带所述宿端PE的宿端OAM实体配置信息；A receiving unit, configured to receive a 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;

所述OAM实体单元还用于当确定所述宿端OAM实体配置信息与所述源端OAM实体配置信息匹配时，使能所述源端OAM实体向所述宿端PE发送OAM报文的功能。The OAM entity unit is further configured to enable the source-end OAM entity to send an OAM message to the sink-end PE when it is determined that the sink-end OAM entity configuration information matches the source-end OAM entity configuration information .

在所述第三方面的第一种可能的实现方式中，所述OAM实体单元，还用于当确定所述宿端OAM实体配置信息与所述源端OAM实体配置信息不匹配时，调整所述源端OAM实体配置信息与所述宿端OAM实体配置信息匹配，使能所述源端OAM实体向所述宿端PE发送OAM报文的功能。In a first possible implementation manner of the third aspect, the OAM entity unit is further configured to, when it is determined that the sink OAM entity configuration information does not match the source OAM entity configuration information, adjust the The source-end OAM entity configuration information matches the sink-end OAM entity configuration information, enabling the source-end OAM entity to send an OAM message to the sink-end PE.

在所述第三方面或所述第三方面的第一种可能的实现方式中，还提供了所述第三方面的第二种可能的实现方式，所述生成单元生成的所述第一LSP Ping请求消息还包括：In the third aspect or the first possible implementation manner of the third aspect, a second possible implementation manner of the third aspect is also provided, the first LSP generated by the generating unit Ping request messages also include:

OAM管理类型、长度、内容OAM Administration TLV，用于标识所述VPN标识；所述OAM Administration TLV包括：OAM management type, length, content OAM Administration TLV, used to identify the VPN identifier; the OAM Administration TLV includes:

双向检测标志，用于标识是否建立所述源端PE和宿端PE之间的双向OAM检测功能；A bidirectional detection flag, used to identify whether to establish a bidirectional OAM detection function between the source PE and the sink PE;

在所述发送单元向所述宿端PE发送所述第一LSP Ping请求消息之前，所述OAM实体单元，还用于配置源端OAM实体的OAM报文接收功能，并设置所述OAM Administration TLV的所述双向检测标志为使能状态，以使得所述宿端PE配置所述宿端OAM实体的OAM报文发送功能，并启动所述宿端OAM实体向所述源端PE发送OAM报文的功能。Before the sending unit sends the first LSP Ping request message to the sink PE, the OAM entity unit is also configured to configure the OAM message receiving function of the source OAM entity, and set the OAM Administration TLV The two-way detection flag is enabled, so that the sink PE configures the OAM packet sending function of the sink OAM entity, and starts the sink OAM entity to send OAM packets to the source PE function.

在所述第三方面的第二种可能的实现方式中，还提供了所述第三方面的第三种可能的实现方式，所述生成单元生成的第一LSP Ping请求消息中的所述OAM Administration TLV中的告警使能标志为禁止状态，以使得所述宿端PE在配置所述宿端OAM实体后，抑制所述宿端OAM实体告警上报功能；In the second possible implementation of the third aspect, a third possible implementation of the third aspect is also provided, the OAM in the first LSP Ping request message generated by the generating unit The alarm enabling flag in the Administration TLV is in a disabled state, so that the sink PE suppresses the sink OAM entity alarm reporting function after configuring the sink OAM entity;

在所述OAM实体单元使能所述源端OAM实体向所述宿端PE发送OAM报文的功能之后，所述生成单元，还用于生成第二LSP Ping请求消息，所述第二LSP Ping请求消息包含的OAM AdministrationTLV中的告警使能标志为使能状态；After the OAM entity unit enables the source-end OAM entity to send an OAM message to the sink-end PE, the generating unit is further configured to generate a second LSP Ping request message, and the second LSP Ping The alarm enable flag in the OAM AdministrationTLV included in the request message is enabled;

所述发送单元，还用于将所述生成单元生成的所述第二LSP Ping请求消息发送到所述宿端PE；以使得所述宿端PE在接收到所述第二LSP Ping请求消息后，使能所述宿端OAM实体的告警上报功能。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 after receiving the second LSP Ping request message, the sink PE , enabling the alarm reporting function of the sink OAM entity.

在所述第三方面的第三种可能的实现方式中，还提供了所述第三方面的第四种可能的实现方式，所述接收到单元，还用于接收所述宿端PE发送的第二LSP Ping响应消息；In the third possible implementation manner of the third aspect, a fourth possible implementation manner of the third aspect is also provided, the receiving unit is further configured to receive the The second LSP Ping response message;

所述OAM实体单元，还用于当所述接收单元接收到的所述第二LSP Ping响应消息包含的OAM Administration TLV的告警使能标志为使能状态时，使能所述源端OAM实体的告警上报功能。The OAM entity unit is further configured to enable the source end OAM entity when the alarm enable flag of the OAM Administration TLV included in the second LSP Ping response message received by the receiving unit is in an enabled state Alarm reporting function.

第四方面，提供了一种宿端PE，其特征在于，包括：In a fourth aspect, a sink PE is provided, which is characterized in that it includes:

接收单元，用于接收源端PE发送的携带源端OAM实体配置信息的第一标签交换路径因特网包探索器LSP Ping请求消息；所述第一LSP Ping请求消息包括三层虚拟专用网L3VPN的VPN标识；The receiving unit is used to receive the first label switching path Internet packet explorer LSP Ping request message carrying the configuration information of the source end OAM entity sent by the source end PE; the first LSP Ping request message includes the VPN of the three-layer virtual private network L3VPN logo;

OAM实体单元，用于根据所述接收单元接收到的所述第一LSPPing请求消息配置宿端OAM实体，并配置所述宿端OAM实体对所述VPN标识对应的VPN进行检测，启动所述宿端OAM实体的报文接收功能；The OAM entity unit is configured to configure a sink OAM entity according to the first LSPPing 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 sink The message receiving function of the terminal OAM entity;

生成单元，用于根据所述OAM实体单元配置的宿端OAM实体，生成第一LSP Ping响应消息，所述第一LSP Ping响应消息携带所述宿端OAM实体配置信息；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 configuration information of the sink OAM entity;

发送单元，用于将生成单元生成的所述第一LSP Ping响应消息发送到源端PE。A sending unit, configured to send the first LSP Ping response message generated by the generating unit to the source PE.

在所述第四方面的第一种可能的实现方式中，所述接收单元接收到的所述第一LSP Ping请求消息还包括OAM管理类型、长度、内容OAM Administration TLV，所述OAM Administration TLV包括：In the first possible implementation of the fourth aspect, the first LSP Ping request message received by the receiving unit further includes OAM management type, length, content OAM Administration TLV, and the OAM Administration TLV includes :

所述OAM实体单元，还用于当所述OAM Administration TLV中的所述双向检测标志设置为使能状态时，还配置所述宿端OAM实体的OAM报文发送功能，并启动所述宿端OAM实体向所述源端PE发送OAM报文的功能。The OAM entity unit is further configured to configure the OAM packet sending function of the sink OAM entity and start the sink when the bidirectional detection flag in the OAM Administration TLV is set to an enabled state The function of the OAM entity sending an OAM message to the source PE.

在所述第四方面或所述第四方面的第一种可能的实现方式中，还提供了所述第四方面的第二种可能的实现方式，当所述接收单元接收的所述OAM Administration TLV中的告警使能标志为禁止状态时，所述OAM实体单元在配置所述宿端OAM实体后，抑制所述宿端OAM实体告警上报功能；In the fourth aspect or the first possible implementation of the fourth aspect, a second possible implementation of the fourth aspect is also provided, when the receiving unit receives the OAM Administration When the alarm enable flag in the TLV is in a disabled state, the OAM entity unit suppresses the alarm reporting function of the sink OAM entity after configuring the sink OAM entity;

所述接收单元，还用于接收所述第二LSP Ping请求消息，所述第二LSP Ping请求消息中包含所述OAM Administration TLV，且所述OAM Administration TLV中的告警使能标志为使能状态；The receiving unit is also configured to receive the second LSP Ping request message, 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 ;

所述OAM实体单元，还用于根据所述接收单元接收的所述第二LSP Ping请求消息使能所述宿端OAM实体的告警上报功能。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.

在所述第四方面的第二种可能的实现方式中，还提供了所述第三方面的第三种可能的实现方式，所述生成单元，还用于生成第二LSPPing响应消息；其中，双向检测时，所述第二LSP Ping响应消息中包含的所述OAM Administration TLV的告警使能标志为使能状态；In the second possible implementation manner of the fourth aspect, a third possible implementation manner of the third aspect is also provided, the generating unit is further configured to generate a second LSPPing response message; wherein, During bidirectional detection, the alarm enabling flag of the OAM Administration TLV contained in the second LSP Ping response message is enabled;

所述发送单元，还用于向所述源端PE发送所述生成单元生成的所述第二LSP Ping响应消息；以使得所述源端PE在收到所述第二LSPPing响应消息后，使能所述源端OAM实体的告警上报功能。The sending unit is further configured to send the second LSP Ping response message generated by the generating unit to the source PE; so that after receiving the second LSPPing response message, the source PE uses The alarm reporting function of the OAM entity at the source end can be realized.

第五方面，提供了一种OAM配置系统，所述系统包括：In a fifth aspect, an OAM configuration system is provided, and the system includes:

所述第三方面或所述第三方面提供的任意一种可能的实现方式中的提供的源端PE；The third aspect or the source PE provided in any possible implementation manner provided by the third aspect;

所述第四方面或所述第四方面提供的任意一种可能的实现方式中的提供的宿端PE。The sink PE provided in the fourth aspect or any possible implementation manner provided in the fourth aspect.

本发明实施例提供一种OAM配置的方法、设备及系统，源端PE设备配置源端OAM实体后，通过扩展LSP Ping请求消息将所述源端PE的OAM配置信息发送到宿端PE设备，以使得所述宿端PE根据所述源端OAM配置信息配置宿端PE的宿端OAM实体，并启动所述宿端OAM实体向所述源端PE发送OAM报文的功能；所述LSP Ping请求消息包含了所述宿端PE需要进行OAM检测的VPN标识，当所述源端PE和宿端PE的OAM实体配置好后，使能所述源端OAM实体向所述宿端PE发送OAM报文的功能，由此，完成了源端PE和宿端PE的OAM配置工作，源端OAM实体和宿端OAM实体可使能相应的告警上报功能，通过上述实现方式减少了两端配置OAM的配置工作量，由于两端通过交互LSP Ping消息来动态的完成OAM配置，避免了手动配置中出现的错误。Embodiments of the present invention provide a method, device, and system for OAM configuration. After the source-end PE device configures the source-end OAM entity, it sends the OAM configuration information of the source-end PE to the sink-end PE device through an extended LSP Ping request message. so that the sink-end PE configures the sink-end OAM entity of the sink-end PE according to the source-end OAM configuration information, and starts the function of the sink-end OAM entity sending an OAM message to the source-end PE; the LSP Ping The request message contains the VPN identifier that the sink PE needs to perform OAM detection. When the OAM entities of the source PE and the sink PE are configured, enable the source OAM entity to send OAM to the sink PE. The function of the message, thus, the OAM configuration work of the source PE and the sink PE is completed. The source OAM entity and the sink OAM entity can enable the corresponding alarm reporting function, and the above implementation method reduces the number of OAM configurations at both ends. Since the two ends dynamically complete the OAM configuration by exchanging LSP Ping messages, errors in manual configuration are avoided.

附图说明Description of drawings

为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

图1为本发明实施例提供的VPN网络中PE设备之间OAM配置过程示意图；FIG. 1 is a schematic diagram of an OAM configuration process between PE devices in a VPN network provided by an embodiment of the present invention;

图2为本发明实施例提供的一种OAM配置方法的流程示意图；FIG. 2 is a schematic flowchart of an OAM configuration method provided by an embodiment of the present invention;

图3为本发明实施例提供的OAM Function TLV示意图；FIG. 3 is a schematic diagram of the OAM Function TLV provided by the embodiment of the present invention;

图4为本发明实施例提供的VPNv4 OAM FEC Stack TLV格式示意图；Fig. 4 is a schematic diagram of the VPNv4 OAM FEC Stack TLV format provided by the embodiment of the present invention;

图5为本发明实施例提供的VPNv6OAM FEC Stack TLV格式示意图；FIG. 5 is a schematic diagram of the VPNv6OAM FEC Stack TLV format provided by the embodiment of the present invention;

图6为本发明实施例提供的OAM Administration TLV格式示意图；FIG. 6 is a schematic diagram of the OAM Administration TLV format provided by the embodiment of the present invention;

图7为本发明实施例提供的VPNv4 OAM Source Identifier TLV格式示意图;Fig. 7 is a schematic diagram of the VPNv4 OAM Source Identifier TLV format provided by the embodiment of the present invention;

图8为本发明实施例提供的VPNv6 OAM Source Identifier TLV格式示意图;Figure 8 is a schematic diagram of the VPNv6 OAM Source Identifier TLV format provided by the embodiment of the present invention;

图9为本发明实施例提供的携带告警使能比特位的OAMAdministration TLV；Fig. 9 is the OAMAdministration TLV carrying the alarm enable bit provided by the embodiment of the present invention;

图10为本发明实施例提供的另一种OAM配置方法的流程示意图；FIG. 10 is a schematic flowchart of another OAM configuration method provided by an embodiment of the present invention;

图11为本发明实施例提供的一种OAM配置的系统示意图；FIG. 11 is a system schematic diagram of an OAM configuration provided by an embodiment of the present invention;

图12为本发明实施例提供的另一种OAM配置的系统示意图。Fig. 12 is a system schematic diagram of another OAM configuration provided by an embodiment of the present invention.

具体实施方式Detailed ways

下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

图1为VPN网络中PE设备之间OAM配置过程示意图，PE1 10表示源端运营商边缘路由器PE，PE211表示宿端运营商边缘路由器PE。PE211向PE110发布标签；PE110使用这些标签进行报文封装，向PE211转发数据流。OAM执行检测的方向与数据流转发的方向相同。在此场景下PE110作为主动端——即源端发起标签交换路径因特网包探索器(英文全称为Label Switched Path Packet Internet Grope，英文简称为LSP Ping)请求消息；PE211作为被动端——即宿端响应LSP Ping响应消息。Figure 1 is a schematic diagram of the OAM configuration process between PE devices in a VPN network.PE1 10 represents the source-end operator edge router PE, and PE211 indicates the sink-end operator edge router PE. PE211 issues labels to PE110; PE110 uses these labels to encapsulate packets and forwards data streams to PE211. The direction in which OAM performs detection is the same as the direction in which data flows are forwarded. In this scenario, PE110 acts as the active end—that is, the source end initiates a Label Switched Path Packet Internet Grope (English full name is Label Switched Path Packet Internet Grope, English abbreviation is LSP Ping) request message; PE211 acts as the passive end—that is, the sink end Respond to the LSP Ping Response message.

需要说明的是，上述过程为单向过程，如果PE110和PE211两端相互发送标签形成双向转发，则OAM为双向执行，任意一端PE均可作为源端，即PE110即是源端PE也是宿端PE，PE211即是宿端PE也是源端PE。It should be noted that the above process is a one-way process. If PE110 and PE211 send labels to each other to form two-way forwarding, OAM is performed in two directions. Either PE can be used as the source end, that is, PE110 is both the source end PE and the sink end. PE, PE211 is both the sink PE and the source PE.

参见图2，本发明实施例提供了一种OAM配置的方法，该方法包括以下内容。Referring to FIG. 2 , an embodiment of the present invention provides a method for OAM configuration, and the method includes the following content.

201，源端PE配置源端OAM实体，并且禁止所述源端OAM实体向所述宿端PE发送OAM报文。201. A source-end PE configures a source-end OAM entity, and prohibits the source-end OAM entity from sending an OAM message to the sink-end PE.

在本发明所有实施例中，以L3VPN网络中的VPN进行OAM检测为例进行说明。主动发起LSP Ping请求消息(LSP Ping EchoRequest)的一端为源端PE；被动接收该LSP Ping请求消息(LSP PingEcho Reply)，并响应LSP Ping响应消息的一端为宿端PE。In all the embodiments of the present invention, the OAM detection performed by the VPN in the L3VPN network is taken as an example for illustration. The end that actively initiates the LSP Ping request message (LSP Ping EchoRequest) is the source PE; the end that passively receives the LSP Ping request message (LSP Ping Echo Reply) and responds to the LSP Ping response message is the sink PE.

作为发起LSP Ping请求消息的源端PE，在配置源端OAM实体时，要配置源端OAM发送功能，为了避免源端OAM实体和宿端OAM实体在没有协商配置好前，源端OAM实体发送OAM报文，而导致OAM实体和宿端OAM实体配置不成功，因此，在源端OAM实体和宿端OAM实体在没有协商配置好前，禁止所述源端OAM实体向所述宿端PE发送OAM报文。As the source PE that initiates the LSP Ping request message, when configuring the source OAM entity, you must configure the source OAM sending function. In order to prevent the source OAM entity and the sink OAM entity from sending OAM message, resulting in the OAM entity and the sink OAM entity configuration failure, therefore, before the source OAM entity and the sink OAM entity are not negotiated and configured, the source OAM entity is prohibited from sending to the sink PE OAM packets.

示例性的，当源端PE与宿端PE所属的同一个VPN要进行OAM检测，而此时源端PE与宿端PE没有进行相应的OAM实体的配置，则源端PE需对该源端OAM实体进行配置。例如，可对所述源端OAM实体进行如下的配置：连续性检测、连通性检测、错误管理信号检测、丢包检测、延迟检测、流量检测等。Exemplarily, when the same VPN that the source PE and the sink PE belong to needs to perform OAM detection, but at this time the source PE and the sink PE have not configured the corresponding OAM entity, the source PE needs to OAM entities are configured. For example, the following configurations may be performed on the source-end OAM entity: continuity detection, connectivity detection, error management signal detection, packet loss detection, delay detection, traffic detection, and the like.

202，向所述宿端PE发送携带所述源端OAM实体配置信息的第一LSP Ping请求消息，以使得所述宿端PE根据所述源端OAM实体配置信息配置所述宿端PE的宿端OAM实体，启动所述宿端OAM实体的报文接收功能，所述第一LSP Ping请求消息还包括L3VPN的VPN标识，所述VPN标识用于标识所述宿端PE设备需要进行OAM检测的VPN。202. Send a first LSP Ping request message carrying configuration information of the source-end OAM entity to the sink-end PE, so that the sink-end PE configures the sink of the sink-end PE according to the configuration information of the source-end OAM entity The terminal OAM entity starts the message receiving function of the sink-end OAM entity, and the first LSP Ping request message also includes the VPN identifier of the L3VPN, and the VPN identifier is used to identify that the sink-end PE equipment needs to perform OAM detection. VPN.

所述宿端PE可以根据源端OAM实体配置信息配置宿端OAM实体的配置信息，例如，当所述源端OAM实体配置信息中包含丢包检测时，所述宿端PE在配置所述宿端OAM实体时也配置进行丢包检测，但所述宿端PE配置OAM丢包检测的参数时，可以根据所述宿端PE的能力和所述源端OAM实体配置信息不同。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 end OAM entity is also configured to perform packet loss detection, but when the sink PE configures the parameters of the OAM packet loss detection, it may be different according to the capability of the sink PE and the configuration information of the source OAM entity.

可选地，所述源端OAM实体配置信息可以通过OAM功能(Function)类型、长度、内容TLV来携带，所述OAM Function TLV可参见[draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf-03]，如图3所示：Optionally, the source OAM entity configuration information may be carried by OAM function (Function) type, length, and content TLV, and the OAM Function TLV may refer to [draft-ietf-mpls-lsp-ping-mpls-tp- oam-conf-03], as shown in Figure 3:

C标志位用来标识连续性检测(英文全称为Continuity Check，英文简称为CC)；The C flag is used to identify the continuity check (the English full name is Continuity Check, and the English abbreviation is CC);

V标志位用来标识连通性检测(英文全称为ConnectivityVerification，英文简称为CV)；The V flag is used to identify the connectivity detection (the English full name is ConnectivityVerification, and the English abbreviation is CV);

F标志位用来标识错误管理信号检测(英文全称为FaultManagement Signals，英文简称为FMS)；The F flag is used to identify the fault management signal detection (full name in English is FaultManagement Signals, and the English abbreviation is FMS);

L标志位用来标识丢包检测(Loss)；The L flag is used to identify packet loss detection (Loss);

D标志位用来标识延迟检测(Delay)；The D flag bit is used to identify the delay detection (Delay);

T标志位用来标识流量检测(英文全称为ThroughputMeasurement，英文简称为TM)。The T flag bit is used to identify traffic detection (full English name is ThroughputMeasurement, English abbreviation is TM).

可选的，所述第一LSP Ping请求消息还包括虚拟专用网OAM转发等价类栈类型、长度、内容(VPN OAM FEC Stack TLV)，所述第一LSP Ping请求消息通过所述VPN OAM FEC Stack TLV携带所述VPN标识。所述VPN OAM FEC TLV包括：目标全球ID(Target Global ID)、目标节点ID(Target Node ID)及目标路由标识(Target RouteDistinguisher)的信息，图4为所述VPN OAM FEC Stack TLV携带IPv4VPN标识时的报文格式示意图，图5为所述VPN OAM FEC Stack TLV携带IPv6VPN标识时的报文格式示意图。所述VPN可以通过以下方式来标识：Optionally, the first LSP Ping request message also includes virtual private network OAM forwarding equivalence class stack type, length, content (VPN OAM FEC Stack TLV), and the first LSP Ping request message passes through the VPN OAM FEC The Stack TLV carries the VPN identifier. The VPN OAM FEC TLV includes: the target global ID (Target Global ID), the target node ID (Target Node ID) and the information of the target route identification (Target Route Distinguisher), and Fig. 4 is when the VPN OAM FEC Stack TLV carries the IPv4VPN identification Fig. 5 is a schematic diagram of the packet format when the VPN OAM FEC Stack TLV carries the IPv6VPN identifier. The VPN can be identified by:

Target Global ID::Target Node ID::Target Route Distinguisher(目标路由标识)。可选地，所述VPN OAM FEC Stack TLV中还可以包括：目标接口ID(Target IF ID)，用于标识所述宿端PE需要进行OAM检测的接口；对于图4，所述VPN OAM FEC Stack TLV还包括目标IPv4的前缀(Target IPv4 prefix)及前缀长度(Prefix Length)，用于标识所述宿端PE需要进行OAM检测的IPv4VPN路由；对于图5，所述VPN OAM FEC Stack TLV还包括目标IPv6的前缀信息(Target IPv6prefix)及前缀长度(Prefix Length)，用于标识所述宿端PE需要进行OAM检测IPv6VPN路由。Target Global ID::Target Node ID::Target Route Distinguisher. Optionally, the VPN OAM FEC Stack TLV may also include: a target interface ID (Target IF ID), used to identify the interface that the sink PE needs to perform OAM detection; for Figure 4, the VPN OAM FEC Stack The TLV also includes the target IPv4 prefix (Target IPv4 prefix) and prefix length (Prefix Length), which are used to identify the IPv4VPN route that the sink PE needs to perform OAM detection; for Figure 5, the VPN OAM FEC Stack TLV also includes the target The IPv6 prefix information (Target IPv6 prefix) and prefix length (Prefix Length) are used to identify that the sink PE needs to perform OAM detection for IPv6VPN routing.

以上Target Glob al_ID、Target Node_ID和Target IF_NUM的设置遵循[RFC6370]的定义，Target Route Distinguisher的设置遵循[RFC4364]的定义。The above settings of Target Global_ID, Target Node_ID and Target IF_NUM follow the definition of [RFC6370], and the settings of Target Route Distinguisher follow the definition of [RFC4364].

可选地，参考图4和图5，所述VPN OAM FEC Stack TLV的格式可以为：第1-4字节可以指示Target Global ID，第5-8字节可以指示Target Node ID，第9-16字节可以指示Target Route Distinguisher，第17-20字节可以指示Target IF ID，第21-24字节可以指示TargetIPv4prefix及Target IPv6 prefix，第25字节可以指示prefix length，第26-28字节可以为0。Optionally, referring to Fig. 4 and Fig. 5, the format of the VPN OAM FEC Stack TLV can be: the first 1-4 bytes can indicate the Target Global ID, the 5th-8 bytes can indicate the Target Node ID, the 9th- 16 bytes can indicate Target Route Distinguisher, 17-20 bytes can indicate Target IF ID, 21-24 bytes can indicate TargetIPv4 prefix and Target IPv6 prefix, 25 bytes can indicate prefix length, 26-28 bytes Can be 0.

203，接收所述宿端PE发送的第一LSP Ping响应消息，所述第一LSP Ping响应消息携带所述宿端OAM实体配置信息，当确定所述宿端OAM实体配置信息与所述源端OAM实体配置信息匹配时，使能所述源端OAM实体向所述宿端PE发送OAM报文的功能。203. Receive the first LSP Ping response message sent by the sink-end PE, where the first LSP Ping response message carries the sink-end OAM entity configuration information, and when it is determined that the sink-end OAM entity configuration information is consistent with the source-end When the OAM entity configuration information matches, enable the function of the source-end OAM entity to send an OAM message to the sink-end PE.

当所述宿端PE配置完所述宿端OAM实体后，向所述源端PE发送所述第一LSP Ping响应消息。由于所述宿端PE自身能力限制所述宿端OAM实体配置信息可能会和所述源端OAM实体配置信息不匹配。After the sink-end PE configures the sink-end OAM entity, send the first LSP Ping response message to the source-end PE. The configuration information of the OAM entity at the sink end may not match the configuration information of the OAM entity at the source end due to the capability limitation of the PE at the sink end.

可选地，当确定所述宿端OAM实体配置信息与所述源端OAM实体配置信息不匹配时，调整所述源端OAM实体配置信息与所述宿端OAM实体配置信息匹配，然后，使能所述源端OAM实体向所述宿端PE发送OAM报文的功能。举例来说，以丢包检测为例，参考图3，若标识丢包检测的L标志位置位时，并且所述源端OAM实体的配置信息中的具体丢包检测方式为直接检测方式(Direct)，即直接对业务报文进行测试，当宿端PE收到OAM实体的配置信息后，判断宿端PE只支持插入式检测方式(Inferred)，所述宿端PE只能配置所述宿端OAM的配置参数为Inferrer检测方式，所述宿端PE向将所述宿端PE支持的OAM配置信息通过所述第一LSP Ping响应消息发送到所述源端PE,当所述源端PE接收到所述第一LSP Ping响应消息后，发现所述宿端PE的OAM配置信息和所述源端OAM实体的配置信息不匹配，则调整源端OAM的配置信息中的丢包检测方式为Inferred方式。Optionally, when it is determined that the sink-end OAM entity configuration information does not match the source-end OAM entity configuration information, adjust the source-end OAM entity configuration information to match the sink-end OAM entity configuration information, and then make The function of enabling the source-end OAM entity to send an OAM message to the sink-end PE. For example, taking packet loss detection as an example, with reference to FIG. ), that is, directly test the service packets. When the sink PE receives the configuration information of the OAM entity, it judges that the sink PE only supports the plug-in detection mode (Inferred), and the sink PE can only configure the sink PE The configuration parameter of OAM is the Inferrer detection mode, and the OAM configuration information supported by the sink PE is sent to the source PE through the first LSP Ping response message by the sink PE. When the source PE receives After receiving the first LSP Ping response message, it is found that the OAM configuration information of the sink PE does not match the configuration information of the source OAM entity, then adjust the packet loss detection mode in the configuration information of the source OAM to Inferred Way.

可选地，源端PE向宿端PE发送第一LSP Ping请求消息还包括：OAM管理类型、长度、内容(OAM Administration TLV)，所述OAMAdministration TLV，图6为所述OAM Administration TLV报文格式示意图，其中：Optionally, the first LSP Ping request message sent by the source PE to the sink PE also includes: OAM management type, length, content (OAM Administration TLV), the OAMAdministration TLV, and Figure 6 is the message format of the OAM Administration TLV Schematic where:

中间供应商路由器P使能OAM检测标志I，用于标识是否使能中间P设备OAM检测；The intermediate provider router P enables the OAM detection flag I, which is used to identify whether to enable the OAM detection of the intermediate P equipment;

告警使能标志A，用于标识是否使能OAM告警上报功能；Alarm enabling flag A, used to identify whether to enable the OAM alarm reporting function;

双向检测标志D，用于标识是否建立所述源端PE和宿端PE之间的双向OAM检测功能。The bidirectional detection flag D is used to identify whether to establish the bidirectional OAM detection function between the source PE and the sink PE.

可选的，参考图6所示，OAM Administration TLV的格式可以为：OAM Administration TLV的第1、2字节可以指示OAM AdministrationTLV的类型，OAM Administration TLV的第3、4字节可以指示OAMAdministration TLV的长度，OAM Administration TLV的第5至8字节可以指示OAM检测的配置信息。Optionally, as shown in Figure 6, the format of the OAM Administration TLV can be: the first and second bytes of the OAM Administration TLV can indicate the type of the OAM Administration TLV, and the third and fourth bytes of the OAM Administration TLV can indicate the type of the OAM Administration TLV Length, the 5th to 8th bytes of OAM Administration TLV can indicate the configuration information of OAM detection.

其中，OAM Administration TLV的第5字节的第1比特(图6中I标志)指示中间供应商路由器P使能OAM检测标志，用于标识是否使能中间P设备OAM检测，如果该比特置位，表示要求所述第一LSPPing请求消息沿途传输节点创建OAM维护实体组中间点(MIP)实体。OAM Administration TLV的第5字节的第2比特(图6中A标志)用于标识是否使能OAM告警上报功能，当该比特置位，接收到所述第一LSP Ping请求消息的设备在配置完OAM实体后，使能告警上报功能，即当OAM检测到故障产生相关的触发动作，包括上报告警，当该比特复位，则告警被抑制并且不触发后续动作。OAM AdministrationTLV的第5字节的第3比特(图6)中的D标志)用于标识是否建立所述源端PE和宿端PE之间的双向OAM检测功能，该比特置位，表示需要做双向检测。其余第5字节剩余比特及第6、第7、第8字节为预留，方便日后对OAM配置使能进行扩展。Among them, the first bit of the fifth byte of the OAM Administration TLV (the I flag in Figure 6) indicates that the intermediate provider router P enables the OAM detection flag, which is used to identify whether to enable the OAM detection of the intermediate P device. If this bit is set , indicating that the transit node along the way of the first LSPPing request message is required to create an OAM maintenance entity group intermediate point (MIP) entity. The second bit of the fifth byte of the OAM Administration TLV (A flag in Figure 6) is used to identify whether to enable the OAM alarm reporting function. When this bit is set, the device that receives the first LSP Ping request message is configured After completing the OAM entity, enable the alarm reporting function, that is, when OAM detects a fault, it will generate related trigger actions, including reporting an alarm. When this bit is reset, the alarm will be suppressed and no subsequent actions will be triggered. The third bit of the fifth byte of OAM AdministrationTLV (the D flag in Figure 6) is used to identify whether to establish the bidirectional OAM detection function between the source PE and the sink PE, and this bit is set to indicate that it needs to be done. Bidirectional detection. The remaining bits of the 5th byte and the 6th, 7th, and 8th bytes are reserved for future expansion of the OAM configuration.

进一步地，对于双向检测，所述源端PE在向所述宿端PE发送所述第一LSP Ping请求消息之前，所述源端PE还配置源端OAM实体的OAM报文接收功能，并设置所述第一LSP Ping请求消息中的OAMAdministration TLV的双向检测标志置位，即将所述双向检测标识设置为使能状态，以使得所述宿端PE还配置所述宿端OAM实体的OAM报文发送功能，并启动所述宿端OAM实体向所述源端PE发送OAM报文的功能。Further, for bidirectional detection, before the source PE sends the first LSP Ping request message to the sink PE, the source PE also configures the OAM message receiving function of the source OAM entity, and sets The bidirectional detection flag of the OAMAdministration 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 also configures the OAM message of the sink OAM entity Sending function, and start the function of the OAM entity at the sink end to send the OAM message to the PE at the source end.

可选的，对于双向检测，所述第一LSP Ping请求消息还包括：VPNOAM源标识类型、长度、内容(VPN OAM Source Identifier TLV)，所述VPN OAM Source Identifier TLV用于标识所述源端PE需要进行OAM检测的VPN标识，图7为所述VPN OAM Source Identifier TLV携带IPv4 VPN标识时的报文格式示意图，图8为所述VPN OAMSource Identifier TLV携带IPv6VPN标识时的报文格式示意图，其中，所述VPN OAM Source Identifier TLV中包括：Optionally, for bidirectional detection, the first LSP Ping request message also includes: VPNOAM source identification type, length, content (VPN OAM Source Identifier TLV), and the VPN OAM Source Identifier TLV is used to identify the source PE Need to carry out the VPN identification of OAM detection, Fig. 7 is the message format schematic diagram when described VPN OAM Source Identifier TLV carries IPv4 VPN identification, Fig. 8 is the message format schematic diagram when described VPN OAM Source Identifier TLV carries IPv6VPN identification, wherein, The VPN OAM Source Identifier TLV includes:

VPN OAM Source Identifier TLV的类型、VPN OAM SourceIdentifier TLV的长度、源端全球ID(Source Global ID)、源端节点ID(Source Node ID)、及源端目标路由标识(Source Route Distinguisher)的信息，所述源端PE需要进行OAM检测的VPN可以通过以下方式来标识：The type of VPN OAM Source Identifier TLV, the length of VPN OAM Source Identifier TLV, the source global ID (Source Global ID), the source node ID (Source Node ID), and the information of the source destination route identifier (Source Route Distinguisher), all The VPNs that need to perform OAM detection on the source PE can be identified in the following ways:

Source Global ID::Source Node ID::Source Route Distinguisher。Source Global ID::Source Node ID::Source Route Distinguisher.

可选地，所述VPN OAM Source Identifier TLV中还可以包括：源端接口ID(Source IF ID)，用于标识所述源端PE需要进行OAM检测的接口；对于图7中，还包括还包括源IPv4的前缀(Source IPv4prefix)及前缀长度(Prefix Length)，用于标识所述源端PE需要进行OAM检测的IPv4VPN路由；对于图8，所述VPN OAM FEC StackTLV还包括源IPv6的前缀信息(Source IPv6 prefix)及前缀长度(PrefixLength)，用于标识所述宿端PE需要进行OAM检测IPv6VPN路由。Optionally, the VPN OAM Source Identifier TLV may also include: a source interface ID (Source IF ID), which is used to identify the interface that the source PE needs to perform OAM detection; for Figure 7, it also includes The prefix (Source IPv4 prefix) and prefix length (Prefix Length) of source IPv4 are used to identify the IPv4VPN route that the source PE needs to perform OAM detection; for Fig. 8, the VPN OAM FEC StackTLV also includes the prefix information of source IPv6 ( Source IPv6 prefix) and prefix length (PrefixLength), used to identify that the sink PE needs to perform OAM to detect IPv6VPN routes.

可选的，参考图7和图8，该VPN OAM Source Identifier TLV的格式可以为：第1-2字节可以指示VPN OAM Source Identifier TLV的类型，第3-4字节可以指示VPN OAM Source Identifier TLV的长度，第5-8字节可以指示Source Global ID，第9-16字节可以指示SourceNode ID，第17-20字节可以指示Source IF ID，第21-24字节可以指示Source IPv4(图7中)/IPv6prefix(图8中)，第25字节可以指示prefix length，第26-28字节可以为0。Optionally, referring to Fig. 7 and Fig. 8, the format of the VPN OAM Source Identifier TLV can be: the first 1-2 bytes can indicate the type of VPN OAM Source Identifier TLV, and the 3rd-4 bytes can indicate the VPN OAM Source Identifier The length of the TLV, the 5th-8th byte can indicate the Source Global ID, the 9th-16th byte can indicate the SourceNode ID, the 17th-20th byte can indicate the Source IF ID, and the 21st-24th byte can indicate the Source IPv4 ( In Figure 7)/IPv6prefix (in Figure 8), the 25th byte can indicate the prefix length, and the 26th-28th bytes can be 0.

可选地，为防止在所述源端OAM实体和所述宿端OAM实体配置过程中，所述源端OAM实体和所述宿端OAM实体在没有都完成配置之前，或所述源端OAM实体和所述宿端OAM实体配置信息不匹配时导致所述宿端OAM实体上报错误告警，进一步触发所述宿端PE或源端PE根据错误报警进行错误操作的问题，所述第一LSP Ping请求消息中的OAM Administration TLV的告警使能标志可以为禁止状态，以使得所述宿端PE在配置所述宿端OAM实体后，抑制所述宿端OAM实体告警上报功能，进一步，在所述使能所述源端OAM实体向所述宿端PE发送OAM报文的功能之后，包括：Optionally, in order to prevent that during the configuration process of the source OAM entity and the sink OAM entity, before the configuration of the source OAM entity and the sink OAM entity is completed, or the source OAM When the entity does not match the configuration information of the sink-end OAM entity, the sink-end OAM entity reports an error alarm, which further triggers the problem that the sink-end PE or the source-end PE performs an erroneous operation according to the error alarm, and the first LSP Ping The alarm enable flag of the OAM Administration TLV in the request message may be in a disabled state, so that the sink PE suppresses the alarm reporting function of the sink OAM entity after configuring the sink OAM entity, and further, in the After enabling the function of the source-end OAM entity to send the OAM message to the sink-end PE, it includes:

向所述宿端PE发送第二LSP Ping请求消息，所述第二LSP Ping请求消息包含OAM Administration TLV，所述第二LSP Ping请求消息包含的OAM Administration TLV中的告警使能标志为使能状态，参考图9所示，所述第二LSP Ping请求消息中携带的OAM AdministrationTLV中含有标识告警使能的比特位1(也可以是任意，只要能标识使能告警即可),其余的双向检测标志D和中间供应商路由器P使能OAM检测标志I均可为空，所述宿端PE在接收到所述第二LSP Ping请求消息后，使能所述宿端OAM实体的告警上报功能。Send a second LSP Ping request message to the sink PE, the second LSP Ping request message includes an OAM Administration TLV, and the alarm enabling flag in the OAM Administration TLV included in the second LSP Ping request message is an enabled state , as shown in FIG. 9, the OAM AdministrationTLV carried in the second LSP Ping request message containsbit 1 for identifying alarm enablement (also can be arbitrary, as long as the alarm can be identified and enabled), and the rest of the bidirectional detection Both the flag D and the OAM detection flag I enabled by the intermediate provider router P 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.

可选地，所述源端PE接收所述宿端PE发送的第二LSP Ping响应消息，所述第二LSP Ping响应消息是针对所述第二LSP Ping请求消息的响应消息，所述宿端PE接收到所述第二LSP Ping响应消息后，即可以开始向所述宿端PE发送OAM检测报文，所述源端PE和所述宿端PE开始针对所述第一LSP Ping请求消息包括的VPN标识对应的VPN进行OAM检测。Optionally, the source PE receives the second LSP Ping response message sent by the sink PE, the second LSP Ping response message is a response message to the second LSP Ping request message, and the sink After the PE receives the second LSP Ping response message, it can start to send an OAM detection message to the sink PE, and the source PE and the sink PE start to include the first LSP Ping request message for the first LSP. The VPN corresponding to the VPN ID performs OAM detection.

当所述第一LSP Ping请求消息中的OAM Administration TLV的双向检测标志置位，所述宿端PE在配置所述宿端OAM实体后，还配置所述宿端OAM报文发送功能，即启动所述宿端PE到所述源端PE方向的OAM检测功能，并将所述第二LSP Ping响应消息中包含的OAM Administration TLV的告警使能标志设置为使能状态，当所述源端PE接收到的所述第二LSP Ping响应消息包含的OAMAdministration TLV的告警使能标志为使能状态时，使能所述源端OAM实体的告警上报功能。When the bidirectional detection flag of the OAM Administration TLV in the first LSP Ping request message is set, the sink PE configures the sink OAM message sending function after configuring the sink OAM entity, that is, starts The OAM detection function of the direction from the sink PE to the source PE, and setting the alarm enable flag of the OAM Administration TLV contained in the second LSP Ping response message to an enabled state, when the source PE When the alarm enable flag of the OAMAdministration TLV contained in the received second LSP Ping response message is enabled, the alarm reporting function of the source OAM entity is enabled.

此外，需要说明的是，对于OAM配置参数的更新及会话删除的过程，与上述过程相似，都是源端PE和宿端PE通过发送携带相关信息的LSP Ping请求消息和LSP Ping响应消息，通过源端PE与宿端PE的协商过程，交互相关的参数以进行参数更新及会话删除过程。In addition, it should be noted that the process of updating OAM configuration parameters and deleting a session is similar to the above-mentioned process. Both the source PE and the sink PE send the LSP Ping request message and the LSP Ping response message carrying relevant information. During the negotiation process between the source PE and the sink PE, related parameters are exchanged for parameter update and session deletion.

本发明实施例提供一种OAM配置的方法，源端PE设备配置源端OAM实体后，通过扩展LSP Ping请求消息将所述源端PE的OAM配置信息发送到宿端PE设备，以使得所述宿端PE根据所述源端OAM配置信息配置宿端PE的宿端OAM实体，并启动所述宿端OAM实体向所述源端PE发送OAM报文；所述LSP Ping请求消息包含了所述宿端PE需要进行OAM检测的VPN标识，当所述源端PE和宿端PE的OAM实体配置好后，使能所述源端OAM实体向所述宿端PE发送OAM报文的功能，由此，完成了源端PE和宿端PE的OAM配置工作，源端OAM实体和宿端OAM实体可使能相应的告警上报功能，通过上述实现方式减少了两端配置OAM的配置工作量，由于两端通过交互LSP Ping消息来动态的完成OAM配置，避免了手动配置中出现的错误。The embodiment of the present invention provides an OAM configuration method. After the source-end PE device configures the source-end OAM entity, it sends the OAM configuration information of the source-end PE to the sink-end PE device through an 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 message to the source PE; the LSP Ping request message includes the The sink PE needs to carry out the VPN identification of OAM detection. After the OAM entities of the source PE and the sink PE are configured, enable the function of the source OAM entity to send OAM messages to the sink PE, by Therefore, the OAM configuration work of the source PE and the sink PE is completed. The source OAM entity and the sink OAM entity can enable the corresponding alarm reporting function. The above implementation method reduces the configuration workload of OAM configuration at both ends. The two ends dynamically complete the OAM configuration by exchanging LSP Ping messages, avoiding errors in manual configuration.

参见图10，本发明实施例提供了另一种OAM配置的方法，该方法包括以下内容。Referring to FIG. 10 , an embodiment of the present invention provides another OAM configuration method, which includes the following content.

301，宿端运营商边缘路由器PE接收源端PE发送的携带源端OAM实体配置信息的第一标签交换路径因特网包探索器LSP Ping请求消息；所述第一LSP Ping请求消息还包括三层虚拟专用网L3VPN的VPN标识。301. The edge router PE of the sink-end operator receives the first label switched path Internet packet explorer LSP Ping request message carrying the configuration information of the source-end OAM entity sent by the source-end PE; the first LSP Ping request message also includes a three-layer virtual VPN ID of the private network L3VPN.

302，根据所述第一LSP Ping请求消息配置宿端OAM实体，并配置所述宿端OAM实体对所述VPN标识对应的VPN进行检测，启动所述宿端OAM实体的报文接收功能。302. 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 start the packet receiving function of the sink OAM entity.

303，向所述源端PE发送第一LSP Ping响应消息，所述第一LSPPing响应消息携带所述宿端OAM实体的配置信息。303. Send a first LSP Ping response message to the source PE, where the first LSPPing response message carries configuration information of the sink OAM entity.

可选地，所述源端OAM实体配置信息可以通过OAM FunctionTLV来携带，所述OAM Function TLV已经在图3已经描述过，此处不再赘述。Optionally, the source-end OAM entity configuration information may be carried by an OAM Function TLV. The OAM Function TLV has been described in FIG. 3 and will not be repeated here.

可选的，所述第一LSP Ping请求消息还包括虚拟专用网VPNOAM FEC Stack TLV，所述第一LSP Ping请求消息通过所述VPNOAM FEC Stack TLV携带所述VPN标识。所述VPN OAM FEC TLV包括：目标全球ID(Target Global ID)、目标节点ID(Target NodeID)及目标路由标识(Target Route Distinguisher)的信息，图4为所述VPN OAM FEC Stack TLV携带IPv4VPN标识时的报文格式示意图，图5为所述VPN OAM FEC Stack TLV携带IPv6VPN标识时的报文格式示意图。所述VPN可以通过以下方式来标识：Optionally, the first LSP Ping request message further includes a virtual private network VPNOAM FEC Stack TLV, and the first LSP Ping request message carries the VPN identifier through the VPNOAM FEC Stack TLV. The VPN OAM FEC TLV includes: the information of the target global ID (Target Global ID), the target node ID (Target NodeID) and the target route identification (Target Route Distinguisher), and Fig. 4 is when the VPN OAM FEC Stack TLV carries the IPv4VPN identification Fig. 5 is a schematic diagram of the packet format when the VPN OAM FEC Stack TLV carries the IPv6VPN identifier. The VPN can be identified by:

Target Global ID::Target Node ID::Target Route Distinguisher(目标路由标识)。Target Global ID::Target Node ID::Target Route Distinguisher.

可选地，所述VPN OAM FEC Stack TLV中还可以包括：目标接口ID(Target IF ID)，用于标识所述宿端PE需要进行OAM检测的接口；对于图4，所述VPN OAM FEC Stack TLV还包括目标IPv4的前缀(Target IPv4 prefix)及前缀长度(Prefix Length)，用于标识所述宿端PE需要进行OAM检测的IPv4 VPN路由；对于图5，所述VPNOAM FEC Stack TLV还包括目标IPv6的前缀信息(Target IPv6 prefix)及前缀长度(Prefix Length)，用于标识所述宿端PE需要进行OAM检测IPv6VPN路由。Optionally, the VPN OAM FEC Stack TLV may also include: a target interface ID (Target IF ID), used to identify the interface that the sink PE needs to perform OAM detection; for Figure 4, the VPN OAM FEC Stack The TLV also includes the target IPv4 prefix (Target IPv4 prefix) and prefix length (Prefix Length), which are used to identify the IPv4 VPN route that the sink PE needs to perform OAM detection; for Figure 5, the VPNOAM FEC Stack TLV also includes the target IPv6 prefix information (Target IPv6 prefix) and prefix length (Prefix Length) are used to identify that the sink PE needs to perform OAM to detect IPv6VPN routes.

可选的，对于双向检测，所述第一LSP Ping请求消息还包括：VPNOAM Source Identifier TLV，所述VPN OAM Source Identifier TLV用于标识所述源端PE需要进行OAM检测的VPN标识，图7为所述VPNOAM Source Identifier TLV携带IPv4VPN标识时的报文格式示意图，图8为所述VPN OAM Source Identifier TLV携带IPv6VPN标识时的报文格式示意图。Optionally, for bidirectional detection, the first LSP Ping request message also includes: VPNOAM 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, as shown in Figure 7 A schematic diagram of the packet format when the VPNOAM Source Identifier TLV carries an IPv4VPN identifier, and FIG. 8 is a schematic diagram of a packet format when the VPN OAM Source Identifier TLV carries an IPv6VPN identifier.

可选地，所述第一LSP Ping请求消息还包括OAM AdministrationTLV，图6为为所述OAM Administration TLV报文格式示意图，已经描述过，此处不再赘述Optionally, the first LSP Ping request message also includes OAM AdministrationTLV, and Fig. 6 is a schematic diagram of the message format of the OAM Administration TLV, which has been described and will not be repeated here

可选地，当接收到的所述第一LSP Ping请求消息中的OAMAdministration TLV中的告警使能标志为禁止状态时，所述宿端PE在配置所述宿端OAM实体后，抑制所述宿端OAM实体告警上报功能，所述方法还包括：Optionally, when the alarm enable flag in the OAMAdministration TLV in the received first LSP Ping request message is disabled, the sink PE suppresses the sink End OAM entity alarm reporting function, the method also includes:

可选地，当所述第一LSP Ping请求消息中还包括的OAMAdministration TLV中的双向检测标志为使能状态时，向所述源端PE发送第二LSP Ping响应消息，所述第二LSP Ping响应消息包含OAMAdministration TLV，所述第二LSP Ping响应消息中OAMAdministration TLV的告警使能标志为使能状态，以使得所述源端PE在收到所述第二LSP Ping响应消息后，使能所述源端OAM实体的告警上报功能。Optionally, when the bidirectional detection flag in the OAMAdministration TLV included in the first LSP Ping request message is enabled, send a second LSP Ping response message to the source PE, and the second LSP Ping The response message includes the OAMAdministration TLV, and the alarm enabling flag of the OAMAdministration TLV in the second LSP Ping response message is enabled, so that the source PE enables all Describe the alarm reporting function of the source OAM entity.

参见图11，本发明实施例提供了一种OAM配置的系统，所述系统包括：源端PE10和宿端PE20。Referring to FIG. 11 , an embodiment of the present invention provides an OAM configuration system, and the system includes: a source PE10 and a sink PE20.

所述源端PE10包括：The source PE10 includes:

OAM实体单元101，用于配置源端OAM实体，并且禁止所述源端OAM实体向所述宿端PE20发送OAM报文。TheOAM entity unit 101 is configured to configure a source-end OAM entity, and prohibit the source-end OAM entity from sending OAM messages to the sink-end PE20.

生成单元102，用于根据所述OAM实体单元101配置的源端OAM实体生成第一LSP Ping请求消息，所述第一LSP Ping请求消息携带所述源端OAM实体配置信息，所述第一LSP Ping请求消息还包括L3VPN的VPN标识，所述VPN标识用于标识所述宿端PE设备需要进行OAM检测的VPN。The generatingunit 102 is configured to generate a first LSP Ping request message according to the source OAM entity configured by theOAM entity unit 101, the first LSP Ping request message carrying configuration information of the source OAM entity, and the first LSP The Ping request message also includes the VPN identifier of the L3VPN, where the VPN identifier is used to identify the VPN that the sink PE device needs to perform OAM detection on.

发送单元103，用于将所述生成单元102生成的所述第一LSP Ping请求消息发送到宿端PE20。The sendingunit 103 is configured to send the first LSP Ping request message generated by the generatingunit 102 to the sink PE20.

接收单元104，用于接收所述宿端PE20发送的第一LSP Ping响应消息，所述第一LSP Ping响应消息携带所述宿端OAM实体配置信息。The receivingunit 104 is configured to receive the first LSP Ping response message sent by the sink PE20, where the first LSP Ping response message carries configuration information of the sink OAM entity.

所述OAM实体单元101，还用于根据所述接收单元104接收的所述第一LSP Ping响应消息中携带的所述宿端OAM实体配置信息，当确定所述宿端OAM实体配置信息与所述源端OAM实体配置信息匹配时，使能所述源端OAM实体向所述宿端PE20发送OAM报文的功能。TheOAM entity unit 101 is further configured to, according to the sink-end OAM entity configuration information carried in the first LSP Ping response message received by the receivingunit 104, when determining that the sink-end OAM entity configuration information is consistent with the When the configuration information of the source-end OAM entity matches, enable the function of the source-end OAM entity to send an OAM message to the sink-end PE20.

所述宿端PE20包括：The sink PE20 includes:

接收单元201，用于接收源端PE10的发送单元103发送的携带源端OAM实体配置信息的第一LSP Ping请求消息，所述第一LSP Ping请求消息包括三层虚拟专用网L3VPN的VPN标识。The receivingunit 201 is configured to receive the first LSP Ping request message carrying the configuration information of the source-end OAM entity sent by the sendingunit 103 of the source-end PE10, the first LSP Ping request message including the VPN identifier of the three-layer virtual private network L3VPN.

OAM实体单元202，用于根据所述接收单元201接收到的所述第一LSP Ping请求消息配置宿端OAM实体，启动所述宿端OAM实体的报文接收功能。TheOAM entity unit 202 is configured to configure a sink OAM entity according to the first LSP Ping request message received by the receivingunit 201, and start a message receiving function of the sink OAM entity.

生成单元203，用于根据所述OAM实体单元202配置的宿端OAM实体的配置信息，生成第一LSP Ping响应消息，所述第一LSP Ping响应消息携带所述宿端OAM实体配置信息。The generatingunit 203 is configured to generate a first LSP Ping response message according to the configuration information of the sink OAM entity configured by theOAM entity unit 202, and the first LSP Ping response message carries the configuration information of the sink OAM entity.

发送单元204，用于将生成单元203生成的所述第一LSP Ping响应消息发送到源端PE10。The sendingunit 204 is configured to send the first LSP Ping response message generated by the generatingunit 203 to the source PE10.

可选的，所述源端P E10的OAM实体单元101，还用于当确定所述宿端OAM实体配置信息与所述源端OAM实体配置信息不匹配时，调整所述源端OAM实体配置信息与所述宿端OAM实体配置信息匹配，使能所述源端OAM实体向所述宿端PE20发送OAM报文的功能。Optionally, theOAM entity unit 101 of the source-end PE10 is further configured to adjust the source-end OAM entity configuration when it is determined that the sink-end OAM entity configuration information does not match the source-end OAM entity configuration information The information matches the sink-end OAM entity configuration information, enabling the source-end OAM entity to send OAM packets to the sink-end PE20.

可选地，所述源端OAM实体配置信息可以通过OAM FunctionTLV来携带，所述OAM Function TLV格式如图3所示。Optionally, the source-end OAM entity configuration information may be carried by an OAM Function TLV, and the format of the OAM Function TLV is shown in FIG. 3 .

可选地，所述源端PE10的生成单元102生成的所述第一LSP Ping请求消息还包括VPN OAM FEC Stack TLV，所述第一LSP Ping请求消息通过所述VPN OAM FEC Stack TLV携带所述VPN标识。所述VPN OAM FEC TLV包括：目标全球ID(Target Global ID)、目标节点ID(Target Node ID)及目标路由标识(Target Route Distinguisher)的信息，图4为所述VPN OAM FEC Stack TLV携带IPv4 VPN标识时的报文格式示意图，图5为所述VPN OAM FEC Stack TLV携带IPv6VPN标识时的报文格式示意图。所述VPN可以通过以下方式来标识：Optionally, the first LSP Ping request message generated by the generatingunit 102 of the source PE10 further includes a VPN OAM FEC Stack TLV, and the first LSP Ping request message carries the VPN OAM FEC Stack TLV through the VPN OAM FEC Stack TLV. VPN ID. The VPN OAM FEC TLV includes: the target global ID (Target Global ID), the target node ID (Target Node ID) and the information of the target routing identifier (Target Route Distinguisher), and Fig. 4 is that the VPN OAM FEC Stack TLV carries IPv4 VPN A schematic diagram of the message format when identifying, and Fig. 5 is a schematic diagram of the message format when the VPN OAM FEC Stack TLV carries the IPv6VPN identification. The VPN can be identified by:

可选地，所述VPN OAM FEC Stack TLV中还可以包括：目标接口ID(Target IF ID)，用于标识所述宿端PE20需要进行OAM检测的接口；对于图4，所述VPN OAM FEC Stack TLV还包括目标IPv4的前缀(Target IPv4 prefix)及前缀长度(Prefix Length)，用于标识所述宿端PE20需要进行OAM检测的IPv4 VPN路由；对于图5，所述VPN OAM FEC Stack TLV还包括目标IPv6的前缀信息(Target IPv6prefix)及前缀长度(Prefix Length)，用于标识所述宿端PE20需要进行OAM检测IPv6VPN路由。Optionally, the VPN OAM FEC Stack TLV may also include: a target interface ID (Target IF ID), used to identify the interface that the sink PE20 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 are used to identify the IPv4 VPN route that the sink PE20 needs to perform OAM detection; for Figure 5, the VPN OAM FEC Stack TLV also includes The prefix information (Target IPv6 prefix) and prefix length (Prefix Length) of the target IPv6 are used to identify that the sink PE20 needs to perform OAM detection of IPv6VPN routing.

可选地，所述源端PE10的生成单元102生成的所述第一LSP Ping请求消息还包括:Optionally, the first LSP Ping request message generated by the generatingunit 102 of the source PE10 also includes:

OAM Administration TLV，用于标识所述VPN标识；所述OAMAdministration TLV包括：OAM Administration TLV, used to identify the VPN identity; the OAMAdministration TLV includes:

在所述源端P E10的发送单元103向所述宿端PE20发送所述第一LSP Ping请求消息之前，所述源端PE10的OAM实体单元101，还用于配置源端OAM实体的OAM报文接收功能，并设置所述OAMAdministration TLV的所述双向检测标志为使能状态，以使得所述宿端PE20配置所述宿端OAM实体的OAM报文发送功能，并启动所述宿端OAM实体向所述源端PE发送OAM报文的功能。相应地，所述宿端PE20的OAM实体单元202，还用于当所述OAM Administration TLV中的所述双向检测标志设置为使能状态时，还配置所述宿端OAM实体的OAM报文发送功能，并启动所述宿端OAM实体向所述源端PE10发送OAM报文的功能。Before the sendingunit 103 of the source PE10 sends the first LSP Ping request message to the sink PE20, theOAM entity unit 101 of the source PE10 is also used to configure the OAM report of the source OAM entity text receiving function, and set the bidirectional detection flag of the OAMAdministration TLV to an enabled state, so that the sink PE20 configures the OAM message sending function of the sink OAM entity, and starts the sink OAM entity A function of sending an OAM message to the source PE. Correspondingly, theOAM entity unit 202 of the sink-end PE20 is also configured to configure the OAM message sending of the sink-end OAM entity when the bidirectional detection flag in the OAM Administration TLV is set to an enabled state function, and enable the sink-end OAM entity to send OAM packets to the source-end PE10.

可选的，对于双向检测，所述第一LSP Ping请求消息还包括：VPNOAM Source Identifier TLV，所述VPN OAM Source Identifier TLV用于标识所述源端PE10需要进行OAM检测的VPN标识，图7为所述VPN OAM Source Identifier TLV携带IPv4VPN标识时的报文格式示意图，图8为所述VPN OAM Source Identifier TLV携带IPv6VPN标识时的报文格式示意图。Optionally, for bidirectional detection, the first LSP Ping request message also includes: VPNOAM Source Identifier TLV, and the VPN OAM Source Identifier TLV is used to identify the VPN identifier that the source PE10 needs to perform OAM detection, as shown in Figure 7 A schematic diagram of a packet format when the VPN OAM Source Identifier TLV carries an IPv4VPN identifier, and FIG. 8 is a schematic diagram of a packet format when the VPN OAM Source Identifier TLV carries an IPv6VPN identifier.

可选地，所述VPN OAM Source Identifier TLV中还可以包括：源端接口ID(Source IF ID)，用于标识所述源端P E10需要进行OAM检测的接口；对于图7中，还包括还包括源IPv4的前缀(Source IPv4prefix)及前缀长度(Prefix Length)，用于标识所述源端PE10需要进行OAM检测的IPv4VPN路由；对于图8，所述VPN OAM FEC StackTLV还包括源IPv6的前缀信息(Source IPv6 prefix)及前缀长度(PrefixLength)，用于标识所述宿端PE10需要进行OAM检测IPv6 VPN路由。Optionally, the VPN OAM Source Identifier TLV may also include: a source interface ID (Source IF ID), which is used to identify the interface that the source PE10 needs to perform OAM detection; for Fig. 7, also includes Including the source IPv4 prefix (Source IPv4prefix) and prefix length (Prefix Length), used to identify the IPv4VPN route that the source PE10 needs to perform OAM detection; for Figure 8, the VPN OAM FEC StackTLV also includes source IPv6 prefix information (Source IPv6 prefix) and prefix length (PrefixLength), used to identify that the sink PE10 needs to perform OAM detection IPv6 VPN routing.

可选地，所述第一LSP Ping请求消息还包括OAM AdministrationTLV，图6为为所述OAM Administration TLV报文格式示意图，已经描述过，此处不再赘述。Optionally, the first LSP Ping request message also includes an OAM AdministrationTLV, and FIG. 6 is a schematic diagram of the OAM Administration TLV message format, which has already been described and will not be repeated here.

可选地，所述源端PE10的生成单元102生成的第一LSP Ping请求消息中的所述OAM Administration TLV中的告警使能标志为禁止状态，当所述宿端PE20的接收单元201接收的所述OAM AdministrationTLV中的告警使能标志为禁止状态时，所述宿端PE20的OAM实体单元202在配置所述宿端OAM实体后，抑制所述宿端OAM实体告警上报功能。Optionally, the alarm enable flag in the OAM Administration TLV in the first LSP Ping request message generated by the generatingunit 102 of the source PE10 is in a disabled state, when the receivingunit 201 of the sink PE20 receives When the alarm enable flag in the OAM AdministrationTLV is disabled, theOAM entity unit 202 of the sink PE20 suppresses the alarm reporting function of the sink OAM entity after configuring the sink OAM entity.

在所述源端PE10的OAM实体单元101使能所述源端OAM实体向所述宿端PE发送OAM报文的功能之后，所述源端PE10的生成单元102，还用于生成第二LSP Ping请求消息，所述第二LSP Ping请求消息包含的OAM Administration TLV中的告警使能标志为使能状态。After theOAM entity unit 101 of the source-end PE10 enables the function of the source-end OAM entity to send OAM packets to the sink-end PE, the generatingunit 102 of the source-end PE10 is further configured to generate a second LSP Ping request message, the alarm enabling flag in the OAM Administration TLV contained in the second LSP Ping request message is in an enabled state.

相应地，所述接收单元201，还用于接收所述第二LSP Ping请求消息，所述宿端PE20的OAM实体单元202，还用于根据所述接收单元201接收的所述第二LSP Ping请求消息使能所述宿端OAM实体的告警上报功能。Correspondingly, the receivingunit 201 is also configured to receive the second LSP Ping request message, and theOAM entity unit 202 of the sink PE20 is also configured to receive the second LSP Ping request message according to the receivingunit 201. The request message enables the alarm reporting function of the sink OAM entity.

所述源端PE10的发送单元103，还用于将所述生成单元102生成的所述第二LSP Ping请求消息发送到所述宿端PE20，相应地所述宿端PE20的接收单元201还用于接收到所述第二LSP Ping请求消息，所述宿端PE20的OAM实体单元202还用于当判断所述接收单元201还用于接收到所述第二LSP Ping请求消息包含的OAM AdministrationTLV中的告警使能标志为使能状态时，使能所述宿端OAM实体的告警上报功能。The sendingunit 103 of the source PE10 is also configured to send the second LSP Ping request message generated by the generatingunit 102 to the sink PE20, and accordingly the receivingunit 201 of the sink PE20 is also used After receiving the second LSP Ping request message, theOAM entity unit 202 of the sink PE20 is also used to judge that the receivingunit 201 is also used to receive the OAM AdministrationTLV contained in the second LSP Ping request message When the alarm enable flag of is enabled, the alarm reporting function of the sink OAM entity is enabled.

可选地，所述源端PE10的接收到单元104，还用于接收所述宿端PE20发送的第二LSP Ping响应消息。Optionally, the receivingunit 104 of the source PE10 is further configured to receive the second LSP Ping response message sent by the sink PE20.

所述宿端PE20的生成单元203，还用于生成第二LSP Ping响应消息；其中，双向检测时，所述第二LSP Ping响应消息中包含的所述OAM Administration TLV的告警使能标志为使能状态。The generatingunit 203 of the sink PE20 is also configured to generate a second LSP Ping response message; wherein, during bidirectional detection, the alarm enable flag of the OAM Administration TLV contained in the second LSP Ping response message is enabled able state.

所述宿端PE20的发送单元204，还用于向所述源端PE10发送所述生成单元203生成的所述第二LSP Ping响应消息。The sendingunit 204 of the sink PE20 is further configured to send the second LSP Ping response message generated by the generatingunit 203 to the source PE10.

所述源端PE10的OAM实体单元101，还用于当所述接收单元104接收到的所述第二LSP Ping响应消息包含的OAM Administration TLV的告警使能标志为使能状态时，使能所述源端OAM实体的告警上报功能。TheOAM entity unit 101 of the source PE10 is further configured to enable all Describe the alarm reporting function of the source OAM entity.

本发明实施例提供一种OAM配置的系统，源端PE10配置源端OAM实体后，通过扩展LSP Ping请求消息将所述源端PE10的OAM配置信息发送到宿端PE20设备，以使得所述宿端PE20根据所述源端OAM配置信息配置宿端PE20的宿端OAM实体，并启动所述宿端OAM实体向所述源端PE10发送OAM报文；所述LSP Ping请求消息包含了所述宿端PE20需要进行OAM检测的VPN标识，当所述源端PE10和宿端PE20的OAM实体配置好后，使能所述源端OAM实体向所述宿端PE20发送OAM报文的功能，由此，完成了源端PE10和宿端PE20的OAM配置工作，源端OAM实体和宿端OAM实体可使能相应的告警上报功能，通过上述实现方式减少了两端配置OAM的配置工作量，由于两端通过交互LSP Ping消息来动态的完成OAM配置，避免了手动配置中出现的错误。The embodiment of the present invention provides an OAM configuration system. After the source-end PE10 configures the source-end OAM entity, it sends the OAM configuration information of the source-end PE10 to the sink-end PE20 through an extended LSP Ping request message, so that the sink The terminal PE20 configures the sink OAM entity of the sink PE20 according to the source OAM configuration information, and starts the sink OAM entity to send an OAM message to the source PE10; the LSP Ping request message includes the sink End PE20 needs to carry out the VPN identification of OAM detection, after the OAM entities of described source end PE10 and sink end PE20 are configured, enable the function of described source end OAM entity to send OAM message to described sink end PE20, thereby , the OAM configuration work of the source PE10 and the sink PE20 is completed, the source OAM entity and the sink OAM entity can enable the corresponding alarm reporting function, and the above implementation method reduces the configuration workload of OAM configuration at both ends, because the two The end dynamically completes the OAM configuration by exchanging LSP Ping messages, avoiding errors in manual configuration.

参见图12，本发明实施例提供了另一种OAM配置的系统，所述系统包括：源端PE30和宿端PE40。Referring to FIG. 12 , an embodiment of the present invention provides another system configured with OAM, and the system includes: a source PE30 and a sink PE40.

所述源端PE30包括：The source PE30 includes:

处理器301，用于配置源端OAM实体，并且禁止所述源端OAM实体向所述宿端PE30发送OAM报文，还用于生成第一LSP Ping请求消息，所述第一LSP Ping请求消息携带所述源端OAM实体配置信息，所述第一LSP Ping请求消息还包括L3VPN的VPN标识，所述VPN标识用于标识所述宿端PE40需要进行OAM检测的VPN。Theprocessor 301 is configured to configure a source-end OAM entity, and prohibit the source-end OAM entity from sending an OAM message to the sink-end PE30, and is also used to generate a first LSP Ping request message, and the first LSP Ping request message Carrying the configuration information of the source-end OAM entity, the first LSP Ping request message also includes the VPN identifier of the L3VPN, and the VPN identifier is used to identify the VPN that the sink-end PE40 needs to perform OAM detection.

发送器302，用于将所述处理器301生成的所述第一LSP Ping请求消息发送到宿端PE40。Thesender 302 is configured to send the first LSP Ping request message generated by theprocessor 301 to the sink PE40.

接收器303，用于接收所述宿端PE40发送的第一LSP Ping响应消息，所述第一LSP Ping响应消息携带所述宿端OAM实体配置信息。Thereceiver 303 is configured to receive the first LSP Ping response message sent by the sink PE40, where the first LSP Ping response message carries configuration information of the sink OAM entity.

所述处理器301，还用于根据所述接收器303接收的所述第一LSPPing响应消息中携带的宿端OAM实体配置信息，当确定所述宿端OAM实体配置信息与所述源端OAM实体配置信息匹配时，使能所述源端OAM实体向所述宿端PE40发送OAM报文的功能。Theprocessor 301 is further configured to, according to the sink-end OAM entity configuration information carried in the first LSPPing response message received by thereceiver 303, determine that the sink-end OAM entity configuration information is consistent with the source-end OAM entity configuration information. When the entity configuration information matches, enable the function of the source-end OAM entity to send an OAM message to the sink-end PE40.

所述宿端PE40包括：The sink PE40 includes:

接收器401，用于接收源端PE30的发送器302发送的携带源端OAM实体配置信息的第一LSP Ping请求消息；所述第一LSP Ping请求消息包括L3VPN的VPN标识。Thereceiver 401 is configured to receive the first LSP Ping request message carrying the configuration information of the source-end OAM entity sent by thesender 302 of the source-end PE30; the first LSP Ping request message includes the VPN identifier of the L3VPN.

处理器402，用于根据所述接收器401接收到的所述第一LSP Ping请求消息配置宿端OAM实体，启动所述宿端OAM实体的报文接收功能，并用于生成第一LSP Ping响应消息，所述第一LSP Ping响应消息携带所述宿端OAM实体配置信息。Processor 402, configured to configure a sink-end OAM entity according to the first LSP Ping request message received by thereceiver 401, start a message receiving function of the sink-end OAM entity, and generate a first LSP Ping response message, the first LSP Ping response message carries the sink OAM entity configuration information.

发送器403，用于将处理器402生成的所述第一LSP Ping响应消息发送到源端PE30。Thesender 403 is configured to send the first LSP Ping response message generated by theprocessor 402 to the source PE30.

可选的，所述处理器301还用于当确定所述宿端OAM实体配置信息与所述源端OAM实体配置信息不匹配时，调整所述源端OAM实体配置信息与所述宿端OAM实体配置信息匹配，使能所述源端OAM实体向所述宿端PE40发送OAM报文的功能。Optionally, theprocessor 301 is further configured to adjust the source OAM entity configuration information and the sink OAM entity configuration information when it is determined that the sink OAM entity configuration information does not match the source OAM entity configuration information. The entity configuration information matches, enabling the function of the source-end OAM entity to send an OAM message to the sink-end PE40.

可选地，所述源端PE30的处理器301生成的所述第一LSP Ping请求消息还包括VPN OAM FEC Stack TLV，所述第一LSP Ping请求消息通过所述VPN OAM FEC Stack TLV携带所述VPN标识。所述VPN OAM FEC TLV包括：目标全球ID(Target Global ID)、目标节点ID(Target Node ID)及目标路由标识(Target Route Distinguisher)的信息，图4为所述VPN OAM FEC Stack TLV携带IPv4VPN标识时的报文格式示意图，图5为所述VPN OAM FEC Stack TLV携带IPv6VPN标识时的报文格式示意图。所述VPN可以通过以下方式来标识：Optionally, the first LSP Ping request message generated by theprocessor 301 of the source PE30 further includes a VPN OAM FEC Stack TLV, and the first LSP Ping request message carries the VPN OAM FEC Stack TLV through the VPN OAM FEC Stack TLV. VPN ID. The VPN OAM FEC TLV includes: the target global ID (Target Global ID), the target node ID (Target Node ID) and the information of the target route identification (Target Route Distinguisher), and Fig. 4 is that the VPN OAM FEC Stack TLV carries the IPv4VPN identification Fig. 5 is a schematic diagram of the packet format when the VPN OAM FEC Stack TLV carries the IPv6VPN identifier. The VPN can be identified by:

可选地，所述VPN OAM FEC Stack TLV中还可以包括：目标接口ID(Target IF ID)，用于标识所述宿端PE40需要进行OAM检测的接口；对于图4，所述VPN OAM FEC Stack TLV还包括目标IPv4的前缀(Target IPv4 prefix)及前缀长度(Prefix Length)，用于标识所述宿端PE20需要进行OAM检测的IPv4 VPN路由；对于图5，所述VPN OAM FEC Stack TLV还包括目标IPv6的前缀信息(Target IPv6prefix)及前缀长度(Prefix Length)，用于标识所述宿端PE20需要进行OAM检测IPv6VPN路由。Optionally, the VPN OAM FEC Stack TLV may also include: a target interface ID (Target IF ID), used to identify the interface that the sink PE40 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 are used to identify the IPv4 VPN route that the sink PE20 needs to perform OAM detection; for Figure 5, the VPN OAM FEC Stack TLV also includes The prefix information (Target IPv6 prefix) and prefix length (Prefix Length) of the target IPv6 are used to identify that the sink PE20 needs to perform OAM detection of IPv6VPN routing.

可选地，所述源端PE30的处理器301生成的所述第一LSP Ping请求消息还包括:Optionally, the first LSP Ping request message generated by theprocessor 301 of the source PE30 further includes:

在所述源端PE30的发送器303向所述宿端PE40发送所述第一LSP Ping请求消息之前，所述源端PE30的处理器301，还用于配置源端OAM实体的OAM报文接收功能，并设置所述OAM AdministrationTLV的所述双向检测标志为使能状态。相应地，所述宿端PE40的处理器402，还用于当所述OAM Administration TLV中的所述双向检测标志设置为使能状态时，还配置所述宿端OAM实体的OAM报文发送功能，并启动所述宿端OAM实体向所述源端PE30发送OAM报文的功能。Before thetransmitter 303 of the source PE30 sends the first LSP Ping request message to the sink PE40, theprocessor 301 of the source PE30 is also configured to receive the OAM message of the source OAM entity function, and set the bidirectional detection flag of the OAM AdministrationTLV to enable state. Correspondingly, theprocessor 402 of the sink-end PE40 is further configured to configure the OAM message sending function of the sink-end OAM entity when the bidirectional detection flag in the OAM Administration TLV is set to an enabled state , and start the function of the sink-end OAM entity sending an OAM packet to the source-end PE30.

可选的，对于双向检测，所述第一LSP Ping请求消息还包括：VPNOAM Source Identifier TLV，所述VPN OAM S ource Identifier TLV用于标识所述源端PE30需要进行OAM检测的VPN标识，图7为所述VPN OAM Source Identifier TLV携带IPv4VPN标识时的报文格式示意图，图8为所述VPN OAM Source Identifier TLV携带IPv6VPN标识时的报文格式示意图。Optionally, for bidirectional detection, the first LSP Ping request message also includes: VPNOAM Source Identifier TLV, and the VPN OAM Source Identifier TLV is used to identify the VPN identifier that the source PE30 needs to perform OAM detection, as shown in Figure 7 It is a schematic diagram of the packet format when the VPN OAM Source Identifier TLV carries the IPv4VPN identifier, and FIG. 8 is a schematic diagram of the packet format when the VPN OAM Source Identifier TLV carries the IPv6VPN identifier.

可选地，所述VPN OAM Source Identifier TLV中还可以包括：源端接口ID(Source IF ID)，用于标识所述源端PE30需要进行OAM检测的接口；对于图7中，还包括还包括源IPv4的前缀(Source IPv4prefix)及前缀长度(Prefix Length)，用于标识所述源端PE30需要进行OAM检测的IPv4VPN路由；对于图8，所述VPN OAM FEC StackTLV还包括源IPv6的前缀信息(Source IPv6 prefix)及前缀长度(PrefixLength)，用于标识所述宿端PE30需要进行OAM检测IPv6 VPN路由。Optionally, the VPN OAM Source Identifier TLV may also include: a source interface ID (Source IF ID), which is used to identify the interface that the source PE30 needs to perform OAM detection; for FIG. 7, it also includes The prefix (Source IPv4 prefix) and prefix length (Prefix Length) of source IPv4 are used to identify the IPv4VPN route that the source end PE30 needs to carry out OAM detection; For Fig. 8, the VPN OAM FEC StackTLV also includes the prefix information of source IPv6 ( Source IPv6 prefix) and prefix length (PrefixLength), used to identify that the sink PE30 needs to perform OAM detection of IPv6 VPN routes.

可选地，所述第一LSP Ping请求消息还包括OAM AdministrationTLV，图6为所述OAM Administration TLV报文格式示意图，已经描述过，此处不再赘述。Optionally, the first LSP Ping request message also includes an OAM AdministrationTLV, and FIG. 6 is a schematic diagram of the OAM Administration TLV message format, which has already been described and will not be repeated here.

可选地，所述源端PE30的处理器301生成的第一LSP Ping请求消息中的所述OAM Administration TLV中的告警使能标志为禁止状态，当所述接收器401接收的所述OAM Administration TLV中的告警使能标志为禁止状态时，所述处理器402在配置所述宿端OAM实体后，抑制所述宿端OAM实体告警上报功能。Optionally, the alarm enable flag in the OAM Administration TLV in the first LSP Ping request message generated by theprocessor 301 of the source PE30 is disabled, and when thereceiver 401 receives the OAM Administration When the alarm enable flag in the TLV is disabled, theprocessor 402 inhibits the alarm reporting function of the sink OAM entity after configuring the sink OAM entity.

在所述源端PE30的处理器301使能所述源端OAM实体向所述宿端PE40发送OAM报文的功能之后，所述处理器301还用于生成第二LSP Ping请求消息，所述第二LSP Ping请求消息包含的OAMAdministration TLV中的告警使能标志为使能状态。After theprocessor 301 of the source-end PE30 enables the function of the source-end OAM entity to send an OAM message to the sink-end PE40, theprocessor 301 is further configured to generate a second LSP Ping request message, the The alarm enabling flag in the OAMAdministration TLV included in the second LSP Ping request message is in an enabled state.

相应地，所述宿端PE40的接收器401还用于接收所述第二LSPPing请求消息，所述处理器402，还用于根据所述接收器401接收的所述第二LSP Ping请求消息使能所述宿端OAM实体的告警上报功能。Correspondingly, thereceiver 401 of the sink PE40 is further configured to receive the second LSPPing request message, and theprocessor 402 is further configured to use the second LSP Ping request message received by thereceiver 401 to Enable the alarm reporting function of the sink OAM entity.

所述源端PE30的发送器302，还用于将所述处理器301生成的所述第二LSP Ping请求消息发送到所述宿端PE40，相应地所述接收器401还用于接收到所述第二LSP Ping请求消息，所述处理器402还用于当判断所述接收器401接收到所述第二LSP Ping请求消息包含的OAM Administration TLV中的告警使能标志为使能状态时，使能所述宿端OAM实体的告警上报功能。Thetransmitter 302 of the source PE30 is further configured to send the second LSP Ping request message generated by theprocessor 301 to the sink PE40, and correspondingly thereceiver 401 is further configured to receive the In the second LSP Ping request message, theprocessor 402 is further configured to determine that the alarm enable flag in the OAM Administration TLV contained in the second LSP Ping request message received by thereceiver 401 is in an enabled state, Enable the alarm reporting function of the sink OAM entity.

可选地，所述源端PE30的接收到器303，还用于接收所述宿端PE40发送的第二LSP Ping响应消息。Optionally, thereceiver 303 of the source PE30 is further configured to receive the second LSP Ping response message sent by the sink PE40.

所述宿端PE40的处理器402，还用于生成第二LSP Ping响应消息；其中，双向检测时，所述第二LSP Ping响应消息中包含的所述OAM Administration TLV的告警使能标志为使能状态。Theprocessor 402 of the sink PE40 is also configured to generate a second LSP Ping response message; wherein, during bidirectional detection, the alarm enable flag of the OAM Administration TLV contained in the second LSP Ping response message is enabled able state.

所述宿端PE40的发送器403，还用于向所述源端PE30发送所述处理器402生成的所述第二LSP Ping响应消息。Thesender 403 of the sink PE40 is further configured to send the second LSP Ping response message generated by theprocessor 402 to the source PE30.

所述源端PE30的处理器303，还用于当所述接收器303收到的所述第二LSP Ping响应消息包含的OAM Administration TLV的告警使能标志为使能状态时，使能所述源端OAM实体的告警上报功能。Theprocessor 303 of the source PE30 is further configured to enable the alarm enable flag of the OAM Administration TLV included in the second LSP Ping response message received by thereceiver 303 to be enabled. The alarm reporting function of the OAM entity at the source end.

本发明实施例提供一种OAM配置的系统，源端PE30配置源端OAM实体后，通过扩展LSP Ping请求消息将所述源端PE30的OAM配置信息发送到宿端PE40设备，以使得所述宿端PE40根据所述源端OAM配置信息配置宿端PE40的宿端OAM实体，并启动所述宿端OAM实体向所述源端PE30发送OAM报文；所述LSP Ping请求消息包含了所述宿端PE40需要进行OAM检测的VPN标识，当所述源端PE30和宿端PE40的OAM实体配置好后，使能所述源端OAM实体向所述宿端PE40发送OAM报文的功能，由此，完成了源端PE30和宿端PE40的OAM配置工作，源端OAM实体和宿端OAM实体可使能相应的告警上报功能，通过上述实现方式减少了两端配置OAM的配置工作量，由于两端通过交互LSP Ping消息来动态的完成OAM配置，避免了手动配置中出现的错误。The embodiment of the present invention provides an OAM configuration system. After the source PE30 configures the source OAM entity, it sends the OAM configuration information of the source PE30 to the sink PE40 device through an extended LSP Ping request message, so that the sink The terminal PE40 configures the sink OAM entity of the sink PE40 according to the source OAM configuration information, and starts the sink OAM entity to send an OAM message to the source PE30; the LSP Ping request message includes the sink End PE40 needs to carry out the VPN identification of OAM detection, after the OAM entities of described source end PE30 and sink end PE40 are configured, enable the function of described source end OAM entity to send OAM message to described sink end PE40, thereby , the OAM configuration work of source-end PE30 and sink-end PE40 is completed, and the source-end OAM entity and sink-end OAM entity can enable the corresponding alarm reporting function. The end dynamically completes the OAM configuration by exchanging LSP Ping messages, avoiding errors in manual configuration.

所述源端PE30和所述宿端PE40可以为路由器或交换机。The source PE30 and the sink PE40 may be routers or switches.

可选地，上述源端PE30的处理器301和宿端PE40的处理器402可以为中央处理器(英文全称为Central Processing Unit，英文简称为CPU)。上述源端PE30的接收器303、发送器302、宿端PE40的接收器401、发送器403可以包含普通物理接口，所述物理接口可以为以太(Ethernet)接口或异步传输模式(英文全称为Asynchronous TransferMode，英文简称为ATM)接口。上述源端PE30的接收器303、处理器301和发送器302可以集成为一个或多个独立的电路或硬件，如：专用集成电路(英文全称为Application Specific Integrated Circuit，英文简称为ASIC)，上述宿端PE40的接收器401、处理器402、发送器403可以集成为一个或多个独立的电路或硬件，如：ASIC。Optionally, theprocessor 301 of the source-end PE30 and theprocessor 402 of the sink-end PE40 may be central processing units (English full name is Central Processing Unit, English abbreviation is CPU). Thereceiver 303 of the source PE30, thetransmitter 302, thereceiver 401 of the sink PE40, and thetransmitter 403 can include a common physical interface, and the physical interface can be an Ethernet (Ethernet) interface or an asynchronous transfer mode (English full name is Asynchronous TransferMode, the English abbreviation is ATM) interface. Thereceiver 303, theprocessor 301 and thetransmitter 302 of the above-mentioned source PE30 can be integrated into one or more independent circuits or hardware, such as: Application Specific Integrated Circuit (English full name is Application Specific Integrated Circuit, English abbreviation is ASIC), the above-mentioned Thereceiver 401,processor 402, andtransmitter 403 of the sink PE40 may be integrated into one or more independent circuits or hardware, such as ASIC.

本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过程序指令相关的硬件来完成，前述程序可以存储于一计算机可读取存储介质中，该程序在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：只读存储器(英文全称为read-only memory，英文简称为ROM)、RAM、磁碟或者光盘等各种可以存储程序代码的介质。Those of ordinary skill in the art can understand that all or part of the steps to realize the above method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the execution includes: The steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: various media that can store program codes such as read-only memory (English full name is read-only memory, English abbreviation is ROM), RAM, magnetic disk or optical disk.

最后应说明的是：以上实施例仅用以示例性说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明及本发明带来的有益效果进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明权利要求的范围。Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention and the beneficial effects brought by the present invention have been described in detail with reference to the foregoing embodiments, those skilled in the art Those of ordinary skill in the art should understand that: they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the present invention Scope of Claims.