第27章 OAM配置

MPLS OAM 目录目录第1章 MPLS OAM配置.........................................................................................................1-11.1 MPLS OAM简介................................................................................................................1-11.1.1 MPLS OAM背景介绍..............................................................................................1-11.1.2 MPLS OAM主要消息类型的格式............................................................................1-21.1.3 MPLS OAM的主要功能..........................................................................................1-51.1.4 参考信息..................................................................................................................1-71.2 MPLS OAM配置................................................................................................................1-71.2.1 MPLS OAM配置任务简介.......................................................................................1-71.2.2 配置MPLS OAM基本检测功能...............................................................................1-71.2.3 配置保护组..............................................................................................................1-81.3 MPLS OAM基本功能的显示和维护...................................................................................1-91.3.1 配置过程................................................................................................................1-101.4 MPLS OAM典型配置举例...............................................................................................1-111.5 MPLS OAM配置的故障排除............................................................................................1-151.5.1 无法启动入节点OAM功能....................................................................................1-151.5.2 无法启动出节点OAM功能....................................................................................1-151.5.3 出节点出现检测异常..............................................................................................1-161.5.4 入节点和出节点缺陷状态不一致............................................................................1-161.5.5 入节点缺陷不能触发保护倒换...............................................................................1-171.5.6 主LSP恢复无缺陷，保护组无法回切...................................................................1-18第1章 MPLS OAM配置下表列出了本章所包含的内容。

第20章OAM故障排除
本章介绍了分析OAM模块故障的基本思路，以及OAM的常用方法和使用命令等。

本章内容
OAM故障排除基本思路
OAM常见故障处理
20.1OAM故障排除基本思路
1、检查网络环境
检查网络环境是否因为环路出现了广播风暴，交换机是否受到大量报文冲击导致交换机无法处理OAM 协议报文。

2、检查配置及参数设置
查看相关配置和参数配置是否合理。

20.2OAM常见故障处理
故障一：OAM邻居无法建立
故障二：OAM邻居震荡
故障三：OAM环回测试功能不能使用
故障四：链路检测功能不能检测到错误。

ENT-AN1267-4.5Application Note Ethernet Link OAM Software ConfigurationGuideReleasedJuly20181Revision History (1)2Ethernet Link OAM (2)2.1Overview (2)2.2Ethernet Link OAM Configuration Examples (2)2.2.1Enabling/Disabling Link OAM on an Interface (2)2.2.2Setting Link OAM Mode to Active (2)2.2.3Enabling MIB Retrieval Support (3)2.2.4Enabling Link OAM Remote Loopback Support (3)2.2.5Enabling/Disabling Link Monitor (4)2.2.6Link OAM Event Configuration (4)2.2.7Viewing Link OAM Status (5)2.2.8Viewing Link Monitor Status (6)2.2.9Viewing Link OAM Statistics (10)Figure1•Link OAM Port Configuration (2)Figure2•Link OAM Event Configuration (4)Figure3•Link OAM Detailed Per Port Status (6)Figure4•:Link OAM Detailed Per Port Event Status (7)Figure5•.Link OAM Detailed Per Port Statistics (10)1Revision HistoryThe revision history describes the changes that were implemented in the document.The changes are listed by revision,starting with the most current publication.Revision 1.0Revision 1.0was published in July 2018.It was the first publication of this document.Revision History2Ethernet Link OAM2.1OverviewEthernet link operations,administration,and maintenance(OAM)is a protocol for monitoring the linkoperations as specified in IEEE802.3ah specification.Ethernet Link OAM enables user to monitor andtroubleshoot a single ethernet link.Ethernet link OAM is a slow protocol with low bandwidth requirements,so the impact of OAM on normal operations is negligible.2.2Ethernet Link OAM Configuration ExamplesThe following examples describe configuration of Ethernet Link OAM feature.2.2.1Enabling/Disabling Link OAM on an InterfaceTo enable link OAM on an interface,perform the following steps.1.Click Configuration>Link OAM>Port Settings.The Link OAM Port Configuration page opens.2.In the Link OAM Port Configuration page,select or clear the required OAM Enabled check boxes forthe respective ports as shown in the following figure,and then click Save.Figure1•Link OAM Port ConfigurationThe equivalent CLI commands to enable and disable link OAM on an interface are:# configure terminal(config)# interface GigabitEthernet 1/2(config-if)# link-oamTo disable Link OAM on an interface:# configure terminal(config)# interface GigabitEthernet 1/2(config-if)# no link-oam2.2.2Setting Link OAM Mode to ActiveBy default,the mode is set to passive.In active mode,the interface will initiate the discovery process.Active interfaces do not respond to OAMremote loopback commands and variable requests from a passive peer.To set link OAM mode to active/passive on an interface,perform the following steps.1.Click Configuration>Link OAM>Port Settings.The Link OAM Port Configuration page opens.2.In the Link OAM Port Configuration page,in the OAM Mode list,click Active/Passive for the respectiveports as shown in Figure1on page2,and then click Save.The equivalent CLI commands to set link OAM mode to active on an interface are:# configure terminal(config)# interface GigabitEthernet 1/2(config-if)# link-oam mode ?active Enable Link OAM Active mode on this interfacepassive Enable Link OAM Passive mode on this interface(config-if)# link-oam mode activeIn passive mode,interface does not initiate the discovery process.Passive interface reacts to the initiationof the discovery process by the remote peer interface.Passive interface does not send variable request orloopback control OAMPDUs.The equivalent CLI commands to set link OAM mode to passive on an interface are:# configure terminal(config)# interface GigabitEthernet 1/2(config-if)# link-oam mode passive2.2.3Enabling MIB Retrieval SupportOn enabling the MIB retrieval support,the switch supports polling of various Link OAM based MIB variables'contents.To enable MIB retrieval support on an interface,perform the following steps.1.Click Configuration>Link OAM>Port Settings.The Link OAM Port Configuration page opens.2.In the Link OAM Port Configuration page,select or clear the required OAM Enabled check boxes forthe respective ports as shown in Figure1on page2,and then click Save.To enable MIB retrieval support on an interface,execute the following command.# configure terminal(config)# interface GigabitEthernet 1/2(config-if)# link-oam mib-retrieval supported2.2.4Enabling Link OAM Remote Loopback SupportLink OAM remote loopback can be used for fault localization and link performance testing.Enabling theloopback support will allow the switch to execute the remote loopback command that helps in the faultdetection.To enable remote loopback support on an interface,perform the following steps.1.Click Configuration>Link OAM>Port Settings.The Link OAM Port Configuration page opens.2.In the Link OAM Port Configuration page,select the required Loopback Support check boxes for therespective ports as shown in Figure1on page2,and then click Save.The equivalent CLI commands to enable remote loopback support on an interface are:# configure terminal(config)# interface GigabitEthernet 1/2(config-if)# link-oam remote-loopback supported2.2.5Enabling/Disabling Link MonitorTo enable or disable link monitoring,perform the following steps.1.Click Configuration>Link OAM>Port Settings.The Link OAM Port Configuration page opens.2.In the Link OAM Port Configuration page,select Link Monitor Support check boxes for the respectiveports as shown in Figure1on page2,and then click Save.The equivalent CLI commands to enable/disable link monitoring(when the no keyword is entered)on theport are:# configure terminal(config)# interface GigabitEthernet 1/2(config-if)# link-oam link-monitor supported2.2.6Link OAM Event ConfigurationThe following examples demonstrate how to configure various link OAM events.2.2.6.1Configuring Error Frame EventErrored frame event counts the number of erred frames detected during the specified period.The periodis specified by a time interval window(seconds).This event is generated if the errored frame count is equalto or greater than the specified threshold for that period.Errored frames are frames that had transmission errors as detected at the media access control(MAC)sublayer.The allowed range for error window is1–60with the default value as1.The allowed range for the thresholdis0–4294967295with the default value as1.To configure the error frame event,perform the following steps.1.Click Configuration>Link OAM>Event Settings.2.In the list,click Port2,configure Error Window and Error Threshold fields for Error Frame Event asshown in the following figure,and then click Save.Figure2•Link OAM Event Configuration# configure terminal(config)# interface GigabitEthernet 1/2(config-if)# link-oam link-monitor frame window 5(config-if)# link-oam link-monitor frame threshold 1002.2.6.2Configuring Symbol Period Error EventSymbol period event counts the number of symbol errors at underlying physical layer that occurred duringthe specified period.The period is specified by the number of seconds.This event is generated if the symbolerror count is equal to or greater than the specified threshold for that period.The allowed range for the error window is1–60with the default value as1.The allowed range for errorthreshold is0–4294967295with the default value as1.To configure the symbol period error event,perform the following steps.1.Click Configuration>Link OAM>Event Settings.2.In the list,click Port2,configure Error Window and Error Threshold fields for Symbol Period Error Eventas shown in Figure1on page4,and then click Save.The equivalent CLI commands are:# configure terminal(config)# interface GigabitEthernet 1/2(config-if)# link-oam link-monitor symbol-period window 5(config-if)# link-oam link-monitor symbol-period threshold 1002.2.6.3Configuring Seconds Summary EventThe errored frame seconds summary event counts the number of erred frame seconds that occurred duringthe specified period.The period is specified by a time interval.This event is generated if the number oferrored frame seconds is equal to or greater than the specified threshold for that period.An errored frame second is a one second interval wherein at least one frame error was detected.Theallowed range for error window is10–900with the default value as60.The allowed range for error thresholdis0–65535with the default value as1.To configure the summary event window and threshold,perform the following steps.1.Click Configuration>Link OAM>Event Settings.2.In the list,click Port2,configure Error Window and Error Threshold fields for Seconds Summary Eventas shown in Figure1on page4,and then click Save.The equivalent CLI commands are:# configure terminal(config)# interface GigabitEthernet 1/2(config-if)# link-oam link-monitor frame-seconds window 10(config-if)# link-oam link-monitor frame-seconds threshold 32.2.7Viewing Link OAM StatusTo View the link OAM status(both local and peer status),perform the following steps.1.Click Monitor>Link OAM>Port Status.Figure3•Link OAM Detailed Per Port StatusThe equivalent CLI commands:# show link-oam status interface GigabitEthernet 1/2GigabitEthernet 1/2-----------------------------------------Admin state: EnabledPDU permission: AnyDiscovery state: SEND_ANY_STATERemote MAC Address: 00:10:94:00:00:03Local client Remote Client------------- --------------Operational status:port status: operational operationalMode: passive activeUnidirectional operation support: disabled enabledRemote loopback support: disabled enabledLink monitoring support: enabled enabledMIB retrieval support: disabled enabledMTU Size: 1500 1500Multiplexer state: Forwarding ForwardingParser state: Forwarding ForwardingOUI: 00:01:c1 00:10:94PDU revision: 0 0Event Name Error Window Error Threshold---------------- ------------- ---------------Error Frame 5 100Symbol Period Error 5 100Seconds Summary 10 32.2.8Viewing Link Monitor StatusTo view the link monitor status(both local and peer status),perform the following steps.1.Click Monitor>Link OAM>Event Status.Figure4•:Link OAM Detailed Per Port Event StatusThe equivalent CLI commands are:# show link-oam status link-monitor interface GigabitEthernet 1/2GigabitEthernet 1/2-----------------------------------------Admin state: EnabledPDU permission: AnyDiscovery state: SEND_ANY_STATERemote MAC Address: 00:10:94:00:00:03Local client Remote Client------------- --------------Operational status:port status: operational operational Mode: passive active Unidirectional operation support: disabled enabled Remote loopback support: disabled enabledLink monitoring support: enabled enabledMIB retrieval support: disabled enabledMTU Size: 1500 1500 Multiplexer state: Forwarding Forwarding Parser state: Forwarding Forwarding OUI: 00:01:c1 00:10:94PDU revision: 0 0Event Name Error Window Error Threshold ---------------- ------------- ---------------Error Frame 5 100Symbol Period Error 5 100Seconds Summary 10 3GigabitEthernet 1/2-----------------------------------------Sequence number : 0Local Symbol Period Status--------------------------Symbol period error event Timestamp: 0Symbol period error event window: 5Symbol period error event threshold: 100Symbol period errors: 8000Total symbol period errors: 951722Total symbol period error events: 8Remote Symbol Period Status---------------------------Symbol period error event Timestamp: 0Symbol period error event window: 0Symbol period error event threshold: 0Symbol period errors: 0Total symbol period errors: 0Total symbol period error events: 0Local Frame Error Status------------------------Frame error event Timestamp: 0Frame error event window: 5Frame error event threshold: 100Frame errors: 8000Total frame errors: 951722Total frame error events: 8Remote Frame Error Status-------------------------Frame error event Timestamp: 0Frame error event window: 0Frame error event threshold: 0Frame errors: 0Total frame errors: 0Total frame error events: 0Local Frame Period Status-------------------------Frame period error event Timestamp: 0Frame period error event window: 0Frame period error event threshold: 0Frame period errors: 0Total frame period errors: 0Total frame period error events: 0Remote Frame Period Status--------------------------Frame period error event Timestamp: 0Frame period error event window: 0Frame period error event threshold: 0Frame period errors: 0Total frame period errors: 0Total frame period error events: 0Local Event Seconds Summary Status----------------------------------Error Frame Seconds Summary Event Timestamp: 0Error Frame Seconds Summary Event window: 10Error Frame Seconds Summary Event Threshold: 3Error Frame Seconds Summary Errors: 5Total Error Frame Seconds Summary Errors: 9Total Error Frame Seconds Summary Events: 1Remote Event Seconds Summary Status-----------------------------------Error Frame Seconds Summary Event Timestamp: 0Error Frame Seconds Summary Event window: 0Error Frame Seconds Summary Event Threshold: 0Error Frame Seconds Summary Errors: 0Total Error Frame Seconds Summary Errors: 0Total Error Frame Seconds Summary Events: 0#2.2.9Viewing Link OAM StatisticsTo view the link OAM statistics(both local and peer status),perform the following steps.1.Click Monitor>Link OAM>Statistics.2.In the list,click Port2,and then click Refresh for any update in the status.Figure5•.Link OAM Detailed Per Port Statistics# show link-oam statistics interface GigabitEthernet 1/2GigabitEthernet 1/2-----------------------------------------PDU stats-----------Information PDU TX: 348Information PDU RX: 347Variable request PDU RX: 0Variable request PDU TX: 0Variable response PDU RX: 0Variable response PDU TX: 0Loopback PDU RX: 0Loopback PDU TX: 0Link Unique event notification PDU TX: 18Link Unique event notification PDU RX: 0Link Duplicate event notification PDU TX: 0Link Duplicate event notification PDU RX: 0Org Specific PDU RX: 0Org Specific PDU TX: 0Unsupported PDU RX: 0Unsupported PDU TX: 0Link Fault PDU TX: 0Link Fault PDU RX: 0Dying gasp PDU TX: 2Dying gasp PDU RX: 1Critical event PDU TX: 0Critical event PDU RX: 0#Microsemi makes no warranty,representation,or guarantee regarding the information contained herein or the suitability of its products and services for any particular purpose,nor does Microsemi assume any liability whatsoever arising out of the application or use of any product or circuit.The products sold hereunder and any other products sold by Microsemi have been subject to limited testing and should not be used in conjunction with mission-critical equipment or applications.Any performance specifications are believed to be reliable but are not verified,and Buyer must conduct and complete all performance and other testing of the products,alone and together with,or installed in,any end-products.Buyer shall not rely on any data and performance specifications or parameters provided by Microsemi.It is the Buyer's responsibility to independently determine suitability of any products and to test and verify the same.The information provided by Microsemi hereunder is provided "as is,where is"and with all faults,and the entire risk associated with such information is entirely with the Buyer.Microsemi does not grant,explicitly or implicitly,to any party any patent rights,licenses,or any other IP rights,whether with regard to such information itself or anything described by such rmation provided in this document is proprietary to Microsemi,and Microsemi reserves the right to make any changes to the information in this document or to any products and services at any time withoutnotice.Microsemi HeadquartersOne Enterprise,Aliso Viejo,CA 92656USAWithin the USA:+1(800)713-4113Outside the USA:+1(949)380-6100Sales:+1(949)380-6136Fax:+1(949)215-4996Email:***************************©2019Microsemi.All rights reserved.Microsemi and the Microsemi logo aretrademarks of Microsemi Corporation.Allother trademarks and service marks are theproperty of their respective owners.Microsemi,a wholly owned subsidiary of Microchip Technology Inc.(Nasdaq:MCHP),offers a comprehensive portfolio of semiconductor and system solutions for aerospace &defense,communications,data center and industrial markets.Products include high-performance and radiation-hardened analog mixed-signal integratedcircuits,FPGAs,SoCs and ASICs;power management products;timing and synchronization devices and precise time solutions,setting the world's standard for time;voice processing devices;RF solutions;discrete components;enterprise storage and communication solutions;security technologies and scalable anti-tamper products;Ethernet solutions;Power-over-Ethernet ICs and midspans;as well as custom design capabilities and services.Microsemi is headquartered in Aliso Viejo,California,and has approximately 4,800employees globally.Learn more at .VPPD-04656Legal。

WAS环境配置OAM步骤说明J2EE统一平台项目组2013年5月目录目录 (2)1接入流程 (3)2申请接入IAM系统 (3)2.1接入申请 (3)2.2文档说明 (3)3统一身份验证及下载数据配置 (4)3.1配置统一身份验证 (4)3.1.1配置说明 (4)3.1.2配置示例 (4)3.2下载用户数据配置 (4)3.2.1配置说明 (5)3.3导出EAR包 (5)1 接入流程未上线的项目在http://22.5.228.194/中获取最新发布的应用框架ecd包上线的项目应提前与统一开发平台项目组工作人员沟通，获取相应的补丁包应用项目需提供：应用程序部署的IP地址、端口、应用项目名称信息给IAMIAM集成人员在IAM进行注册2 申请接入IAM系统2.1 接入申请应用接入IAM系统时，需要获得如下文档：《XX项目-应用接入调研表》《XX项目-数据准备表》《XX项目-环境、数据反馈表》应用系统项目组可以发送邮件至huangxiaoxi@ 向IAM项目组获取以上文档。

2.2 文档说明一、《XX项目-应用接入调研表》文档说明应用系统项目组需填写《XX项目-应用接入调研表》，帮助IAM项目组了解应用系统的相关信息，并根据这些信息进行相应配置。

该调用表中的主要关注点如下：a.接入系统业务描述（1）身份数据普通用户范围、管理员用户范围；（2）交互系统：由于需要在应用web层增加拦截器，还可以需要推拉数据，故可能会影响交互的系统。

（3）安全管理用户管理、认证，权限管理、单点登录等情况。

b.业务系统技术描述（1）系统结构图由于需要在应用web层增加拦截器，还可能需要推拉数据，故需要了解与认证和数据流向相关的系统的结构。

（2）系统部署图由于需要在应用web层增加拦截器，还可能需要推送数据，故需要了解与认证和数据流向相关的系统的部署情况。

（3）系统数据发布由于可能需要推送数据，故需要了解数据流向相关的系统的发布情况。

OAM配置目录目录第1章 OAM配置 (1)1.1 OAM概述 (1)1.1.1 OAM协议的特性 (1)1.1.2 OAM模式 (2)1.1.3 OAM报文结构简介 (3)1.2 OAM特性与型号对照表 (4)1.3 OAM配置任务列表 (5)1.4 OAM配置任务 (5)1.4.1 在端口上开启OAM (5)1.4.2 开启OAM远端环回 (6)1.4.3 配置OAM链路监控 (6)1.4.4 配置OAM远端故障指示 (7)1.4.5 显示OAM协议信息 (8)1.5 配置示例 (9)1.5.1 网络环境需求 (9)1.5.2 网络拓扑图 (9)1.5.3 配置步骤 (9)第1章 OAM配置1.1 OAM概述IEEE 802.3ah的EFM OAM可以提供点到点链路故障和性能检测。

EFM OAM只适用于单链路，不能监控EVC，无法实现对端到端的以太网业务监控。

OAM PDU不会被转发到其他端口。

IEEE 802.3ah规定的以太网OAM是一个相对慢的协议，最大传输速率为10帧每秒，最小传输速率为1帧每秒。

1.1.1 OAM协议的特性z发现支持以太网OAM的设备和他们所支持的OAM特性以太网OAM连接过程也称作Discovery阶段，本阶段是OAM实体发现远端设备的OAM实体，并与之建立稳定对话的过程。

在这个阶段中，相连的以太网OAM实体（即使能OAM功能的端口）通过周期的交互Information OAM PDU向对端通报各自的OAM模式、以太网OAM配置信息及本地节点支持的以太网OAM能力信息，OAM实体收到对端配置参数后，决定是否同意建立点对点OAM连接。

如果两端的以太网OAM对Loopback功能、单向链路检测及链路事件的配置都通过检查时，以太网OAM协议将在链路层开始正常工作。

z链路监控以太网OAM利用Event Notification OAM PDU的交互来进行链路监控。

当链路故障发生时，本地链路监控到故障后，将向对端以太网OAM实体发送EventNotification OAMPDU，通报一般链路事件。

[Docs][txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits] [IPR]Versions: (draft-busi-mpls-tp-oam-framework)00 01 02 03 04 05 06 07 08 09 10 11MPLS Working Group I. Busi (Ed)Internet Draft Alcatel-LucentIntended status: Informational D. Allan (Ed)EricssonExpires: August 11, 2011 February 11, 2011Operations, Administration and Maintenance Framework forMPLS-based Transport Networksdraft-ietf-mpls-tp-oam-framework-11.txtAbstractThe Transport Profile of Multi-Protocol Label Switching(MPLS-TP) is a packet-based transport technology based on theMPLS Traffic Engineering (MPLS-TE) and Pseudowire (PW) dataplane architectures.This document describes a framework to support a comprehensiveset of Operations, Administration and Maintenance (OAM)procedures that fulfill the MPLS-TP OAM requirements for fault,performance and protection-switching management and that do notrely on the presence of a control plane.This document is a product of a joint Internet Engineering TaskForce (IETF) / International Telecommunications UnionTelecommunication Standardization Sector (ITU-T) effort toinclude an MPLS Transport Profile within the IETF MPLS and PWE3architectures to support the capabilities and functionalities ofa packet transport network as defined by the ITU-T.Status of this MemoThis Internet-Draft is submitted to IETF in full conformancewith the provisions of BCP 78 and BCP 79.Internet-Drafts are working documents of the InternetEngineering Task Force (IETF), its areas, and its workinggroups. Note that other groups may also distribute workingdocuments as Internet-Drafts.Internet-Drafts are draft documents valid for a maximum of sixmonths and may be updated, replaced, or obsoleted by otherdocuments at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "workin progress".Busi et al. Expires April 10, 2011 [Page 1] Internet-Draft OAM Framework for MPLS-based Transport February 2011The list of current Internet-Drafts can be accessed at/ietf/1id-abstracts.txt.The list of Internet-Draft Shadow Directories can be accessed at/shadow.html.This Internet-Draft will expire on August 11, 2011.Copyright NoticeCopyright (c) 2011 IETF Trust and the persons identified as thedocument authors. All rights reserved.This document is subject to BCP 78 and the IETF Trust's LegalProvisions Relating to IETF Documents(/license-info) in effect on the date ofpublication of this document. Please review these documentscarefully, as they describe your rights and restrictions withrespect to this document. Code Components extracted from thisdocument must include Simplified BSD License text as describedin Section 4.e of the Trust Legal Provisions and are providedwithout warranty as described in the Simplified BSD License.Busi et al. Expires August 11, 2011 [Page 2] Internet-Draft OAM Framework for MPLS-based Transport February 2011 Table of Contents1. Introduction (5)1.1. Contributing Authors (7)2. Conventions used in this document (7)2.1. Terminology (7)2.2. Definitions (9)3. Functional Components (12)3.1. Maintenance Entity and Maintenance Entity Group (12)3.2. MEG Nesting: SPMEs and Tandem Connection Monitoring (14)3.3. MEG End Points (MEPs) (16)3.4. MEG Intermediate Points (MIPs) (20)3.5. Server MEPs (22)3.6. Configuration Considerations (23)3.7. P2MP considerations (23)3.8. Further considerations of enhanced segment monitoring (24)4. Reference Model (26)4.1. MPLS-TP Section Monitoring (SMEG) (28)4.2. MPLS-TP LSP End-to-End Monitoring Group (LMEG) (29)4.3. MPLS-TP PW Monitoring (PMEG) (29)4.4. MPLS-TP LSP SPME Monitoring (LSMEG) (30)4.5. MPLS-TP MS-PW SPME Monitoring (PSMEG) (31)4.6. Fate sharing considerations for multilink (33)5. OAM Functions for proactive monitoring (33)5.1. Continuity Check and Connectivity Verification (34)5.1.1. Defects identified by CC-V (37)5.1.2. Consequent action (39)5.1.3. Configuration considerations (40)5.2. Remote Defect Indication (42)5.2.1. Configuration considerations (43)5.3. Alarm Reporting (43)5.4. Lock Reporting (44)5.5. Packet Loss Measurement (46)5.5.1. Configuration considerations (47)5.5.2. Sampling skew (48)5.5.3. Multilink issues (48)5.6. Packet Delay Measurement (48)5.6.1. Configuration considerations (49)5.7. Client Failure Indication (49)5.7.1. Configuration considerations (50)6. OAM Functions for on-demand monitoring (50)6.1. Connectivity Verification (51)6.1.1. Configuration considerations (52)6.2. Packet Loss Measurement (52)6.2.1. Configuration considerations (53)6.2.2. Sampling skew (53)6.2.3. Multilink issues (53)6.3. Diagnostic Tests (53)Busi et al. Expires August 11, 2011 [Page 3]Internet-Draft OAM Framework for MPLS-based Transport February 20116.3.1. Throughput Estimation (53)6.3.2. Data plane Loopback (55)6.4. Route Tracing (57)6.4.1. Configuration considerations (57)6.5. Packet Delay Measurement (57)6.5.1. Configuration considerations (58)7. OAM Functions for administration control (58)7.1. Lock Instruct (58)7.1.1. Locking a transport path (59)7.1.2. Unlocking a transport path (59)8. Security Considerations (60)9. IANA Considerations (61)10. Acknowledgments (61)11. References (62)11.1. Normative References (62)11.2. Informative References (63)Busi et al. Expires August 11, 2011 [Page 4]Internet-Draft OAM Framework for MPLS-based Transport February 2011 Editors' Note:This Informational Internet-Draft is aimed at achieving IETFConsensus before publication as an RFC and will be subject to anIETF Last Call.[RFC Editor, please remove this note before publication as anRFC and insert the correct Streams Boilerplate to indicate thatthe published RFC has IETF Consensus.]1. IntroductionAs noted in the multi-protocol label switching (MPLS-TP) FrameworkRFCs (RFC 5921 [8] and [9]), MPLS-TP is a packet-based transporttechnology based on the MPLS Traffic Engineering (MPLS-TE) and Pseudo Wire (PW) data plane architectures defined in RFC 3031 [1], RFC 3985 [2] and RFC 5659 [4].MPLS-TP supports a comprehensive set of Operations,Administration and Maintenance (OAM) procedures for fault,performance and protection-switching management that do not relyon the presence of a control plane.In line with [15], existing MPLS OAM mechanisms will be usedwherever possible and extensions or new OAM mechanisms will bedefined only where existing mechanisms are not sufficient tomeet the requirements. Some extensions discussed in thisframework may end up as aspirational capabilities and may bedetermined to be not tractably realizable in someimplementations. Extensions do not deprecate support forexisting MPLS OAM capabilities.The MPLS-TP OAM framework defined in this document provides aprotocol neutral description of the required OAM functions andof the data plane OAM architecture to support a comprehensiveset of OAM procedures that satisfy the MPLS-TP OAM requirementsof RFC 5860 [11]. In this regard, it defines similar OAMfunctionality as for existing SONET/SDH and OTN OAM mechanisms(e.g. [19]).The MPLS-TP OAM framework is applicable to sections, LabelSwitched Paths (LSPs), Multi-Segment Pseudowires (MS-)PWs andSub Path Maintenance Entities (SPMEs). It supports co-routed andassociated bidirectional p2p transport paths as well asunidirectional p2p and p2mp transport paths.OAM packets that instrument a particular direction of atransport path are subject to the same forwarding treatmentBusi et al. Expires August 11, 2011 [Page 5]Internet-Draft OAM Framework for MPLS-based Transport February 2011(i.e. fate-share) as the user data packets and in some cases,where Explicitly TC-encoded-PSC LSPs (E-LSPs) are employed, maybe required to have common Per-hop Behavior (PHB) schedulingclass (PSC) E2E with the class of traffic monitored. In case ofLabel-Only-Inferred-PSC LSP (L-LSP), only one class of trafficneeds to be monitored and therefore the OAM packets have commonPSC with the monitored traffic class.OAM packets can be distinguished from the used data packetsusing the GAL and ACH constructs of RFC 5586 [7] for LSP, SPMEand Section or the ACH construct of RFC 5085 [3] and RFC 5586[7] for (MS-)PW. OAM packets are never fragmented and are notcombined with user data in the same packet payload.This framework makes certain assumptions as to the utility andfrequency of different classes of measurement that naturallysuggest different functions are implemented as distinct OAMflows or packets. This is dictated by the combination of theclass of problem being detected and the need for timeliness ofnetwork response to the problem. For example fault detection isexpected to operate on an entirely different time base thanperformance monitoring which is also expected to operate on anentirely different time base than in-band managementtransactions.The remainder of this memo is structured as follow:Section 2 covers the definitions and terminology used in thismemo.Section 3 describes the functional component that generates andprocesses OAM packets.Section 4 describes the reference models for applying OAMfunctions to Sections, LSP, MS-PW and their SPMEs.Sections 5, 6 and 7 provide a protocol-neutral description ofthe OAM functions, defined in RFC 5860 [11], aimed at clarifyinghow the OAM protocol solutions will behave to achieve theirfunctional objectives.Section 8 discusses the security implications of OAM protocoldesign in the MPLS-TP context.The OAM protocol solutions designed as a consequence of thisdocument are expected to comply with the functional behaviordescribed in sections 5, 6 and 7. Alternative solutions torequired functional behaviors may also be defined.Busi et al. Expires August 11, 2011 [Page 6]Internet-Draft OAM Framework for MPLS-based Transport February 2011OAM specifications following this OAM framework may be providedin different documents to cover distinct OAM functions.This document is a product of a joint Internet Engineering TaskForce (IETF) / International Telecommunication UnionTelecommunication Standardization Sector (ITU-T) effort toinclude an MPLS Transport Profile within the IETF MPLS and PWE3architectures to support the capabilities and functionalities ofa packet transport network as defined by the ITU-T.1.1. Contributing AuthorsDave Allan, Italo Busi, Ben Niven-Jenkins, Annamaria Fulignoli,Enrique Hernandez-Valencia, Lieven Levrau, Vincenzo Sestito,Nurit Sprecher, Huub van Helvoort, Martin Vigoureux, YaacovWeingarten, Rolf Winter2. Conventions used in this document2.1. TerminologyAC Attachment CircuitAIS Alarm indication signalCC Continuity CheckCC-V Continuity Check and/or Connectivity VerificationCV Connectivity VerificationDBN Domain Border NodeE-LSP Explicitly TC-encoded-PSC LSPICC ITU Carrier CodeLER Label Edge RouterLKR Lock ReportL-LSP Label-Only-Inferred-PSC LSPLM Loss MeasurementLME LSP Maintenance EntityLMEG LSP ME GroupBusi et al. Expires August 11, 2011 [Page 7] Internet-Draft OAM Framework for MPLS-based Transport February 2011 LSP Label Switched PathLSR Label Switching RouterLSME LSP SPME MELSMEG LSP SPME ME GroupME Maintenance EntityMEG Maintenance Entity GroupMEP Maintenance Entity Group End PointMIP Maintenance Entity Group Intermediate Point NMS Network Management SystemPE Provider EdgePHB Per-hop BehaviorPM Performance MonitoringPME PW Maintenance EntityPMEG PW ME GroupPSC PHB Scheduling ClassPSME PW SPME MEPSMEG PW SPME ME GroupPW PseudowireSLA Service Level AgreementSME Section Maintenance EntitySMEG Section ME GroupSPME Sub-path Maintenance ElementS-PE Switching Provider EdgeTC Traffic ClassBusi et al. Expires August 11, 2011 [Page 8] Internet-Draft OAM Framework for MPLS-based Transport February 2011 T-PE Terminating Provider Edge2.2. DefinitionsThis document uses the terms defined in RFC 5654 [5].This document uses the term 'Per-hop Behavior' as defined in RFC2474 [16].This document uses the term LSP to indicate either a service LSPor a transport LSP (as defined in RFC 5921 [8]).This document uses the term Sub Path Maintenance Element (SPME)as defined in RFC 5921 [8].This document uses the term traffic profile as defined in RFC2475 [13].Where appropriate, the following definitions are aligned withITU-T recommendation Y.1731 [21] in order to have a common,unambiguous terminology. They do not however intend to imply acertain implementation but rather serve as a framework todescribe the necessary OAM functions for MPLS-TP.Adaptation function: The adaptation function is the interfacebetween the client (sub)-layer and the server (sub-)layer.Branch Node: A node along a point-to-multipoint transport paththat is connected to more than one downstream node.Bud Node: A node along a point-to-multipoint transport path thatis at the same time a branch node and a leaf node for thistransport path.Data plane loopback: An out-of-service test where a transportpath at either an intermediate or terminating node is placedinto a data plane loopback state, such that all traffic(including both payload and OAM) received on the looped backinterface is sent on the reverse direction of the transportpath.Note - The only way to send an OAM packet to a node that has been put into data plane loopback mode is via TTL expiry, irrespective ofwhether the node is hosting MIPs or MEPs.Domain Border Node (DBN): An intermediate node in an MPLS-TP LSPthat is at the boundary between two MPLS-TP OAM domains. Such anode may be present on the edge of two domains or may beBusi et al. Expires August 11, 2011 [Page 9]Internet-Draft OAM Framework for MPLS-based Transport February 2011connected by a link to the DBN at the edge of another OAMdomain.Down MEP: A MEP that receives OAM packets from, and transmitsthem towards, the direction of a server layer.Forwarding Engine: An abstract functional component, residing inan LSR, that forwards the packets from an ingress interfacetoward the egress interface(s).In-Service: The administrative status of a transport path whenit is unlocked.Interface: An interface is the attachment point to a server(sub-)layer e.g., MPLS-TP section or MPLS-TP tunnel.Intermediate Node: An intermediate node transits traffic for anLSP or a PW. An intermediate node may originate OAM flowsdirected to downstream intermediate nodes or MEPs.Loopback: See data plane loopback and OAM loopback definitions.Maintenance Entity (ME): Some portion of a transport path thatrequires management bounded by two points (called MEPs), and therelationship between those points to which maintenance andmonitoring operations apply (details in section 3.1).Maintenance Entity Group (MEG): The set of one or moremaintenance entities that maintain and monitor a section or atransport path in an OAM domain.MEP: A MEG end point (MEP) is capable of initiating (Source MEP)and terminating (sink MEP) OAM packets for fault management andperformance monitoring. MEPs define the boundaries of an ME(details in section 3.3).MIP: A MEG intermediate point (MIP) terminates and processes OAMpackets that are sent to this particular MIP and may generateOAM packets in reaction to received OAM packets. It nevergenerates unsolicited OAM packets itself. A MIP resides within aMEG between MEPs (details in section 3.3).MPLS-TP Section: As defined in [8], it is a link that can betraversed by one or more MPLS-TP LSPs.OAM domain: A domain, as defined in [5], whose entities aregrouped for the purpose of keeping the OAM confined within thatdomain. An OAM domain contains zero or more MEGs.Busi et al. Expires August 11, 2011 [Page 10]Internet-Draft OAM Framework for MPLS-based Transport February 2011Note - within the rest of this document the term "domain" isused to indicate an "OAM domain"OAM flow: Is the set of all OAM packets originating with aspecific source MEP that instrument one direction of a MEG (orpossibly both in the special case of data plane loopback).OAM loopback: The capability of a node to be directed by areceived OAM packet to generate a reply back to the sender. OAMloopback can work in-service and can support different OAMfunctions (e.g., bidirectional on-demand connectivityverification).OAM Packet: A packet that carries OAM information between MEPsand/or MIPs in MEG to perform some OAM functionality (e.g.connectivity verification).Originating MEP: A MEP that originates an OAM transaction packet(toward a target MIP/MEP) and expects a reply, either in-band orout-of-band, from that target MIP/MEP. The originating MEPalways generates the OAM request packets in-band and expects andprocesses only OAM reply packets returned by the target MIP/MEP.Out-of-Service: The administrative status of a transport pathwhen it is locked. When a path is in a locked condition, it isblocked from carrying client traffic.Path Segment: It is either a segment or a concatenated segment,as defined in RFC 5654 [5].Signal Degrade: A condition declared by a MEP when the dataforwarding capability associated with a transport path hasdeteriorated, as determined by performance monitoring (PM). See also ITU-T recommendation G.806 [14].Signal Fail: A condition declared by a MEP when the dataforwarding capability associated with a transport path hasfailed, e.g. loss of continuity. See also ITU-T recommendationG.806 [14].Sink MEP: A MEP acts as a sink MEP for an OAM packet when itterminates and processes the packets received from itsassociated MEG.Source MEP: A MEP acts as source MEP for an OAM packet when itoriginates and inserts the packet into the transport path forits associated MEG.Busi et al. Expires August 11, 2011 [Page 11]Internet-Draft OAM Framework for MPLS-based Transport February 2011Tandem Connection: A tandem connection is an arbitrary part of atransport path that can be monitored (via OAM) independent ofthe end-to-end monitoring (OAM). The tandem connection may alsoinclude the forwarding engine(s) of the node(s) at theboundaries of the tandem connection. Tandem connections may benested but cannot overlap. See also ITU-T recommendation G.805[20].Target MEP/MIP: A MEP or a MIP that is targeted by OAMtransaction packets and that replies to the originating MEP thatinitiated the OAM transactions. The target MEP or MIP can replyeither in-band or out-of-band. The target sink MEP functionalways receives the OAM request packets in-band while the targetsource MEP function only generates the OAM reply packets thatare sent in-band.Up MEP: A MEP that transmits OAM packets towards, and receivesthem from, the direction of the forwarding engine.3. Functional Components3.功能组件MPLS-TP is a packet-based transport technology based on the MPLSand PW data plane architectures ([1], [2] and [4]) and iscapable of transporting service traffic where thecharacteristics of information transfer between the transportpath endpoints can be demonstrated to comply with certainperformance and quality guarantees.MPLS-TP是基于MPLS和PW数据平面结构的分组传输技术，在传输路径端点间的信息特征符合某种性能或质量保证的地方，传输服务业务。

H3C S5130-EI 以太网OAM 典型配置举例目录1 简介···························································································································· 1-12 配置前提······················································································································ 1-13 配置举例······················································································································ 1-13.1 组网需求···················································································································1-13.2 配置思路···················································································································1-13.3 使用版本···················································································································1-23.4 配置注意事项·············································································································1-23.5 配置步骤···················································································································1-23.5.1 Device A的配置·································································································1-23.5.2 Device B的配置·································································································1-23.6 验证配置···················································································································1-23.7 配置文件···················································································································1-44 相关资料······················································································································ 4-41 简介本文档介绍了使用以太网OAM 监控链路性能的典型配置举例。

OAM及OIM安装详细过程一．安装产品虚拟机：VMware8系统：Oracle Enterprise Linux5.564位介质：Oracle database11.2.0JDK_1.6.0.24OID_11.1.1.5.0OAM_11.1.1.5.0WebTier_11.1.1.5.0Webgate_11.1.1.5.0SOA_11.1.1.5.0OIM_11.1.1.5.0二．OAM安装及配置步骤1.安装数据库创建oracle用户及用户组[root@localhost~]#useradd oracle[root@localhost~]#passwd oracle(输入密码)[root@localhost~]#groupadd oinstall[root@localhost~]#groupadd dba[root@localhost oracle]#mkdir odrive[root@localhost oracle]#mkdir install[root@localhost oracle]#usermod-g oinstall-G dba oracle[root@localhost oracle]#chown-R oracle:oinstall/home/oracle/odrive修改hosts文件：[root@localhost oracle]#vi/etc/hosts127.0.0.1localhost.localdomain localhost::1localhost6.localdomain6localhost6 idmtest修改网络并重启[root@localhost~]#vi/etc/sysconfig/networkHOSTNAME=启动数据库安装[oracle@idmtest database]$pwd/home/oracle/install/database[oracle@idmtest database]$./runInstaller（注：如果Checking monitor:没有通过，则要安装VM-tool）按图示步骤进行正确的Oracle Base为：/home/oracle/odrive/db11g正确的组名为:oinstall正确的ORACLE_SID:buy360Database Operator(OSOPER)Group:oinstall先决条件检查:(1).点击fix and check again,按提示执行脚本(2).载入系统安装盘，进入到Server目录，安装先决条件中检查失败的包(3).Swap Size问题选择忽略(4).继续安装安装完成后执行安装后脚本修改.bah_profile文件[oracle@idmtest~]$vi.bash_profile#.bash_profile#Get the aliases and functionsif[-f~/.bashrc];then.~/.bashrcfi#User specific environment and startup programsPATH=$PATH:$HOME/binexport PATHORACLE_HOME=/home/oracle/odrive/db11g/product/11.2.0/dbhome_1 export ORACLE_HOMEPATH=$ORACLE_HOME/bin:$PATHexport PATH保存后执行:[oracle@idmtest~]$source.bash_profile关闭防火墙[root@idmtest~]#vi/etc/selinux/config#This file controls the state of SELinux on the system.#SELINUX=can take one of these three values:#enforcing-SELinux security policy is enforced.#permissive-SELinux prints warnings instead of enforcing.#disabled-SELinux is fully disabled.SELINUX=disabled#SELINUXTYPE=type of policy in use.Possible values are:#targeted-Only targeted network daemons are protected.#strict-Full SELinux protection.SELINUXTYPE=targeted启动监听器[oracle@idmtest~]$lsnrctl start如果报错，提示libclntsh.so.11.1找不到或者有问题，解决方法：[root@idmtest~]#chcon-t texrel_shlib_t/home/oracle/odrive/db11g/product/11.2.0/dbhome_1/lib/libclntsh.so.11.1查看监听器状态[oracle@idmtest~]$lsnrctl statusLSNRCTL for Linux:Version11.2.0.1.0-Production on14-MAY-201220:17:20Copyright(c)1991,2009,Oracle.All rights reserved.Connecting to(ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))STATUS of the LISTENER------------------------Alias LISTENERVersion TNSLSNR for Linux:Version11.2.0.1.0-ProductionStart Date14-MAY-201220:15:50Uptime0days0hr.1min.32secTrace Level offSecurity ON:Local OS AuthenticationSNMP OFFListener Log File /home/oracle/odrive/db11g/product/11.2.0/dbhome_1/log/diag/tnslsnr/idmtest/listener/alert/log.xm lListening Endpoints Summary...(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))) The listener supports no servicesThe command completed successfully创建数据库实例[oracle@idmtest~]$dbca 按图示操作正确的SID:buy360完成后再修改.bash_profile文件添加两行:ORACLE_SID=buy360export ORACLE_SID在查看监听器状态，会看到如下信息所示:[oracle@idmtest db11g]$lsnrctl statusLSNRCTL for Linux:Version11.2.0.1.0-Production on23-JUL-201223:20:33Copyright(c)1991,2009,Oracle.All rights reserved.Connecting to(ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))STATUS of the LISTENER------------------------Alias LISTENERVersion TNSLSNR for Linux:Version11.2.0.1.0-ProductionStart Date22-JUL-201221:39:10Uptime1days1hr.41min.23secTrace Level offSecurity ON:Local OS AuthenticationSNMP OFFListener Log File /home/oracle/odrive/db11g/product/11.2.0/dbhome_1/log/diag/tnslsnr/idmtest/listener/alert/log.xm lListening Endpoints Summary...(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))) Services Summary...Service"buy360"has1instance(s).Instance"buy360",status READY,has1handler(s)for this service...Service"buy360XDB"has1instance(s).Instance"buy360",status READY,has1handler(s)for this service...The command completed successfully至此数据库安装完成2.安装JDK执行：oracle@idmtest odrive]$/home/oracle/install/jdk-6u26-linux-x64.bin切换到root用户修改.bash_profile文件#JAVAJAV A_HOME=/home/oracle/odrive/jdk1.6.0_24export JAV A_HOMEPATH=$JAV A_HOME/bin:$PATHexport PATH检验结果：[oracle@idmtest~]$su-oracle[oracle@idmtest~]$java-versionjava version"1.6.0_26"Java(TM)SE Runtime Environment(build1.6.0_26-b03)Java HotSpot(TM)Client VM(build20.1-b02,mixed mode,sharing) JDK安装完成3.安装Weblogic[oracle@idmtest install]$java-jar wls1035_generic.zip按图示执行：4.创建OID和OAM Schema执行：./rcuHome/bin/rcu启动RCU 按图示步骤执行:密码：abcd1234Schema创建完成5.安装OID启动Installer按图示步骤进行:执行安装后脚本安装11.1.1.5升级补丁6.创建OID实例[oracle@idmtest bin]$cd/home/oracle/odrive/middleware/Oracle_IDM1/bin [oracle@idmtest bin]$./config.shOracle Instance Location:/home/oracle/odrive/middleware/asinst_1 Oracle Instance Name:asinst_1密码:abcd12347.安装WebTier安装11.1.1.5.0补丁8.安装Webgate[oracle@idmtest Disk1]$./runInstallerStarting Oracle Universal Installer...Checking if CPU speed is above300MHz.Actual2393MHz PassedChecking Temp space:must be greater than150MB.Actual1307MB PassedChecking swap space:must be greater than512MB.Actual1507MB PassedChecking monitor:must be configured to display at least256colors.Actual16777216Passed Preparing to launch Oracle Universal Installer from/tmp/OraInstall2012-05-15_03-08-59AM. Please wait...Please specify JRE/JDK location(Ex./home/jre),<location>/bin/java should exist:/home/oracle/odrive/jdk1.6.0_24此处输入jdk的安装位置按图示进行。