tellabs genios ethernet oam configuration guide a f t d...

Revision 3, 3/12 76.9200FP/EthOAMCG

Copyright © 2011 Tellabs. All rights reserved.

Tellabs® GeniOS™

Ethernet OAM Configuration Guide

Tellabs SmartCore® 9200 Content-Aware Routing System

D R A

F T

FCC Notification Statement

Federal Communications Commission (FCC) Rules require that you be notified of the following:

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

Changes or modifications not expressly approved by Tellabs Operations, Inc., in writing can void the user’s authority to operate the equipment.

Industry Canada Notification Statement

Industry Canada interference-causing equipment regulations require that you be notified of the following:

This Class A digital apparatus complies with Canadian ICES-003.

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.

Copyright Statement This Tellabs manual is owned by Tellabs or its licensors and protected by U.S. and international copyright laws, conventions, and treaties. Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws. Unauthorized reproduction, modification, distribution, display or other use of this manual may result in criminal and civil penalties.

Trademark Notice The following trademarks, registered trademarks, and service marks are owned by

Tellabs Operations, Inc., or its affiliates in the United States and/or other countries: CABLESPAN®, DXX®, ®, FOCUS , GENIOS , INSIGHT ANALYTICS ,

INTELLIGENT SERVICE EDGE , MARTIS®, ®, MARTISDXX®, ®, METROWATCH®, SERVICEASSURED , SMARTCORE®, ®,

TELLABS®, ®, TELLABS PROPARTNER , TELLABS. THE FUTURE

OF YOUR BUSINESS. STARTING NOW , THE WORLD COMMUNICATES

THROUGH TELLABS , TITAN®, and YOUR NETWORKING PARTNER®

Any other company or product names may be trademarks of their respective companies.

Contact Information In an effort to improve the quality of this document, please notify Tellabs Technical Assistance at 1.800.443.5555 in North America or 1.630.798.7070 outside North America if any anomalous conditions are observed.

TM TM TM

TM

TM

TM

TM

TMD R A

F T

Tellabs SmartCore 9200 SeriesEthernet OAM Configuration Guide

Table of Contents

About This Manual .............................................................................................................. 5Reason for Issue ............................................................................................................. 5Audience ......................................................................................................................... 5Standards ........................................................................................................................ 5Text and Other Conventions ........................................................................................... 5Accessing the Tellabs Portal ........................................................................................... 7Contacting Tellabs Technical Support ............................................................................ 8

About Ethernet Service OAM CFM .................................................................................... 9Ethernet Service OAM Overview .................................................................................... 9Ethernet Service OAM Framework on the Tellabs 9200 ............................................... 11

OAM Framework Terms and Definitions ................................................................. 12Ethernet Service OAM Connectivity Fault Management ............................................... 13

Continuity Check Function ...................................................................................... 13Loopback Function .................................................................................................. 14Linktrace Function ................................................................................................... 15

Ethernet Service OAM Performance Management ....................................................... 15Ethernet OAM Loss Measurement .......................................................................... 16Ethernet OAM Delay Measurement ........................................................................ 18

Configuring Ethernet OAM CFM ...................................................................................... 23Service Types that Support Ethernet OAM ................................................................... 23Ethernet OAM and QoS Priority Settings ...................................................................... 24CFM Maintenance Domain Framework Guidelines ...................................................... 24 Configuring CFM Functions on a Local MEP ............................................................... 25

Configure a local MEP ............................................................................................ 25Configure CCM on local MEP ................................................................................. 27Configuring Loopback ............................................................................................. 27Configuring Linktrace .............................................................................................. 28

Configuring Ethernet OAM PM ......................................................................................... 31Ethernet OAM and QoS Priority Settings ...................................................................... 31Configuration Guidelines ............................................................................................... 31

Ethernet OAM PM DM Configuration Guidelines .................................................... 32Ethernet OAM PM LM Configuration Guidelines ..................................................... 33

Configuring PM Functions on a Local MEP ................................................................. 34Configure LM Functions on a Local MEP ................................................................ 34

Configure DM Functions on a Local MEP ..................................................................... 35

Link Level 802.3ah Ethernet OAM .................................................................................... 39About Link Level 802.3ah EFM ..................................................................................... 39Configuring Link Level 802.3ah Ethernet OAM on the Tellabs 9200 ............................ 40

802.3ah OAM Configuration Guidelines .................................................................. 41Configuring 802.3ah OAM on an Interface .............................................................. 42Configuring 802.3ah OAM Looback ........................................................................ 43

D R A

F T

Revision 3, 3/12 3

Tellabs SmartCore 9200 SeriesEthernet OAM Configuration Guide

Configuring 802.3ah OAM Testing .......................................................................... 43 Displaying 802.3ah OAM PDU Statistics ............................................................... 44Clearing 802.3ah OAM PDU Functions and Statistics ............................................ 44

D R A

F T

4 Revision 3, 3/12

About This Manual

This manual provides guidelines on how to configure Ethernet Operations, Administration, and Management (OAM) functions on the Tellabs SmartCore® 9200 Series using the Tellabs® GeniOSTM Operating System command-line interface (CLI) for fault monitoring and performance management of Ethernet service networks.

Refer to the following sections for additional information about this manual:

• Reason for Issue, page 5

• Audience, page 5

• Standards, page 5

• Text and Other Conventions, page 5

• Accessing the Tellabs Portal, page 7

• Contacting Tellabs Technical Support, page 8

Reason for Issue

This is the first release of the Ethernet OAM Configuration Guide.

Audience

This manual is intended for use by system administrators and NOC operators and personnel responsible for configuring network devices and performing day-to-day configuration and maintenance tasks.

Standards

Refer to Appendix A in the Initial Configuration Guide, Appendix A for a list of the standards supported by Tellabs 9200.

Text and Other Conventions

This document uses the following basic text conventions:

• Courier font represent particular commands, keywords, variables, or window sessions

• Blue text indicates cross-reference hyperlinks to additional information

D R A

F T

Revision 3, 3/12 5

About This Manual Ethernet OAM Configuration GuideText and Other Conventions Tellabs SmartCore 9200 Series

Table 1 describes the general text conventions used in this document including conventions for software procedures that are explained using the CLI.

Table 2 describes the symbol conventions used in this document and other related documents for notification and important instructions.

Table 1 Document Text Conventions

Conventions Description

boldface font Commands and keywords appear in boldface

boldface screen font Information you must type into the system is shown in boldface screen font.

italic screen font Variables you enter to complete an operation or a command are shown in italic screen font

character string, or string

Unless otherwise noted, defined as a set of characters that do not require single or double quotation marks.

hyperlink text

Hyperlinked text is displayed in blue, and indicates a cross-reference to a related section, appendix, table, or figure. Blue text indicates a live hyperlink that users can click to display the related section, appendix, table, or figure.

command notations

[ ]Square brackets contain optional command elements

| Vertical bars separate mutually exclusive command element choices

[a | b | c]Optional elements are grouped in square brackets and separated by vertical bars to denote mutual exclusivity.

{a | b | c}Required elements are grouped in curly brackets and separated by vertical bars to denote mutual exclusivity.

< > Angle brackets enclose a numeric range.D R

A F T

6 Revision 3, 3/12

Ethernet OAM Configuration Guide About This ManualTellabs SmartCore 9200 Series Accessing the Tellabs Portal

Accessing the Tellabs Portal

To find the documentation on the Tellabs Portal website, perform the following steps:

1. Go to https://www.portal.tellabs.com/.

2. Log in using your customer user name and password.

3. Click the Product Documentation tab.

4. Click Data Networking.

5. Click Tellabs SmartCore 9200 Series.

6. Click Technical Documentation.

7. Click the feature pack or version.

8. Click the document to view its contents.

Table 2 Symbol Conventions

Icon Type Description

NoteProvides helpful suggestions needed in understanding a feature or references to material not available in the manual.

AlertAlerts you of potential damage to a program, device, or system or the loss of data or service.

CautionCautions you about a situation that could result in minor or moderate bodily injury if not avoided.

WarningWarns you of a potential situation that could result in death or serious bodily injury if not avoided.

ESD Alert! Notifies you to take proper grounding precautions before handling a product because of Electrostatic Discharge (ESD).

Laser Caution!Notifies you that invisible Laser radiation is present. Avoid direct eye exposure to beam.

NOTE: You must first contact Tellabs to set up an account, and obtain a customer user name and password before you can access the Tellabs Portal. D R

A F T

Revision 3, 3/12 7

http://www.portal.tellabs.com/

About This Manual Ethernet OAM Configuration GuideContacting Tellabs Technical Support Tellabs SmartCore 9200 Series

Contacting Tellabs Technical Support

For more Technical Support information or assistance, perform the following steps:

1. Point your browser to http://www.tellabs.com.

2. Click Services & Support, and click Technical Support.

The following information is displayed:

• Telephone number contact information by region

• Links to overviews of support agreements

• Links FAQs and product technical documentation

• Links to PDFs of support policies

• An online RMA request form

North America 800.443.5555

Outside North America 630.798.7070

Postal Address

Tellabs, Inc. One Tellabs Center 1415 West Diehl Road Naperville, IL 60563 U.S.A.

D R A

F T

8 Revision 3, 3/12

http://www.tellabs.com

About Ethernet Service OAM CFM

This chapter describes the Tellabs SmartCore 9200 Series Ethernet service Operations, Administration, and Maintenance (OAM) application for fault monitoring and performance management of Ethernet service networks in the following sections:

• Ethernet Service OAM Overview, page 9

• Ethernet Service OAM Framework on the Tellabs 9200, page 11

• Ethernet Service OAM Connectivity Fault Management, page 13

• Ethernet Service OAM Performance Management, page 15

Ethernet Service OAM Overview

Ethernet service OAM as defined in the IEEC 802.1ag and ITU Y.1731 standards provide following functions in Ethernet service networks:

• Connectivity Fault Management (CFM). CFM functions detect, verify, and isolate connectivity failures across an Ethernet network.

• Performance Measurement (PM). OAM PM functions provide performance measurements across an Ethernet network. These measurements include frame loss measurements, delay, and jitter.

A hierarchical maintenance domain model as shown in Figure 1, page 10 is the functional architecture for Ethernet service OAM and provides the framework for CFM and PM functions in an Ethernet service network. The domains in descending order of hierarchy are typically associated with an Ethernet service Customer, Provider, and Operator. The CE equipment in a Customer domain defines the endpoints of the Ethernet service. The boundaries of a maintenance domain are defined by network elements configured as Maintenance End Points (MEPs). You can also configure Maintenance Intermediate Points (MIPs) within a domain. Multiple maintenance domains may operate within an Ethernet service network.

A session is an active instance of an Ethernet service OAM CFM or PM function configured on the Tellabs 9200. A session can be on-demand or continuous (indefinite) and operates at the service level or at the same 802.1p priority level as the monitored data flow.

D R A

F T

Revision 3, 3/12 9

About Ethernet Service OAM CFM Ethernet OAM Configuration GuideEthernet Service OAM Overview Tellabs SmartCore 9200 Series

Figure 1 Hierarchical Domain Model in an Ethernet Service OAM Network

D R A

F T

10 Revision 3, 3/12

Ethernet OAM Configuration Guide About Ethernet Service OAM CFMTellabs SmartCore 9200 Series Ethernet Service OAM Framework on the Tellabs

Figure 2, page 4-11 compares the functions defined in the IEEE 802.1ag and Y.1731 protocols as well as MPLS OAM coverage.

Figure 2 IEEE 802.1ag and Y.1731

Ethernet Service OAM Framework on the Tellabs 9200

In a network, an Ethernet Service OAM framework may be multiple domains configured as Maintenance Domains (MD) in hierarchy with multiple maintenance associations (MA) as shown in Figure 1, page 10. Within each domain, Up MEPs, Down MEPs and MIPs are configured on network element interfaces.

An Ethernet service OAM framework manages domain hierarchies through assignment of up to eight numeric Maintenance Domain Levels (MDL). An MD contains Maintenance Points (MPs). The endpoints of an Ethernet OAM maintenance domain are Maintenance End Points (MEPs). All OAM functions are initiated at MEPs. You can also define a Maintenance Association Intermediate Point (MIP) within a maintenance domain. A MIP only reacts to some OAM functions and is transparent to all others. The collection of all MPs in a domain is a Maintenance Association. An MD can have several MAs (known as MEGs in Y.1731).

The operational conditions of MDs in an Ethernet service network are:

• The MDL values range from 0 through 7.

• Multiple MDs of different levels may be nested but not overlap.

• If MDs are nested, the outer MD must have a higher domain level than the one used in the inner MD.

D R A

F T

Revision 3, 3/12 11

About Ethernet Service OAM CFM Ethernet OAM Configuration GuideEthernet Service OAM Framework on the Tellabs 9200 Tellabs SmartCore 9200 Series

• The same network element interface can participate in multiple domains.

• Each MD at a particular level is associated to an MA.

Typical MDL assignments for various network types are as follows:

• Customer domain: 5–7

• Service Provider domain: 3–4

• Operator domain: 0–2

OAM Framework Terms and Definitions

This section describes the terms used to manage and configure Ethernet OAM on the Tellabs 9200.

• Maintenance Domain (MD). The administrative partition of a Ethernet service network.

• Maintenance Domain Level (MDL). A numerical value representing an MD.

• Maintenance Endpoint (MEP). An edge of an MD. A MEP is either an up MEP or down MEP.

• Up MEP. An up MEP faces the ingress side of an interface. An up MEP domain includes the path within the network element equipment and the network beyond the network element egress port.OAM sessions originating from the up MEP and OAM sessions received by the up MEP traverse the network element equipment when communicating with peers.

• Down MEP. A down MEP faces the egress side of an interface to communicate with peers within an MD.

• Local MEP (LMEP). A MEP defined locally at the network element. A MEP can be configured per physical interface or logical interface.

• Remote MEP (RMEP). A MEP located at a remote node that belongs to the same MA as an LMEP.

• Maintenance Association Intermediate Point (MIP). A MIP is an intermediate point within an MD consisting of two half-functions, one facing the line, and the other facing the equipment. OAM sessions traversing a MIP may be processed or may be transparent depending upon the type of session.

• Maintenance Point (MP). Either a MEP or a MIP.

• Maintenance Association (MA). A set of MEPs and MIPs in the same domain that verify the integrity of a single service instance. An MA is configured per service instance.

• Maintenance Association Identifier (MAID). A MAID uniquely identifies an MA and protects against accidental concatenation of service instances. A MAID consists of an MD name and the short MA name, and is carried by CCMs.

• Protocol Data Units (PDUs)

D R A

F T

12 Revision 3, 3/12

Ethernet OAM Configuration Guide About Ethernet Service OAM CFMTellabs SmartCore 9200 Series Ethernet Service OAM Connectivity Fault Manage-

• HMDL - Highest MEP Domain Level

• PW - PseudoWire

• PWE3 - PseudoWire Emulation Edge-to-Edge

• RMEP - Remote MEP

• SAP -Service Access Point

• TLV - Type-Length-Value tuple

• VLAN - Virtual Local Area Network

• VPLS - Virtual Private LAN Service

Ethernet Service OAM Connectivity Fault Management

CFM operates within a maintenance domain by applying fault detection mechanisms that identify a fault for a selected level, and then alarms the fault at that level and the next higher level. This provides fault management within the appropriate domain and prevents broadcasting of alarms across the layers of the network.

CFM functions that detect, verify, and isolate Ethernet service connectivity failures on the Tellabs 9200 at port, interface, and service levels are:

• Continuity Check.The continuity check function in a MEP monitors Ethernet service connectivity faults in an MA by periodically sending and monitoring Continuity Check Messages (CCMs). When enabled, each MEP in an MA sends a multicast CCM to all other MEPs following the exact user data path. A loss of CCMs indicates disconnection of service. Refer to Continuity Check Function, page 13 for details.

• Loopback. The loopback (CFM ping) function provides fault verification by transmitting loopback messages (LBM) and receiving loopback replies (LBR). Configure a loopback session priority to be the same as the configured 802.1p QoS data path service priorities. Refer to Loopback Function, page 14 for details.

• Linktrace. Linktrace messages (LTM) and linktrace replies (LTR) provide fault isolation functionality. This functionality allows the operator or service provider to determine the path used by the service in the network, and when a fault is detected allows the tracing of the fault location.Refer to Linktrace Function, page 15 for details.

• AIS. The Tellabs 9200 Ethernet OAM CFM AIS function provides a mechanism to propagate failure indications through the network and higher OAM domains.

Continuity Check Function

The continuity check function monitors the connectivity between the local MEP and the remote MEPs within an MA. Monitoring is performed through the exchange of Continuity check messages (CCMs).

D R A

F T

Revision 3, 3/12 13

About Ethernet Service OAM CFM Ethernet OAM Configuration GuideEthernet Service OAM Performance Management Tellabs SmartCore 9200 Series

When activated, the local MEP periodically transmits multicast CCMs that are propagated to other MEPs in the MA. The local MEP then monitors the stream of CCMs arriving from each remote MEP. If the local MEP does not detect CCMs from the remote MEP, the local MEP raises a loss of continuity (LOC) alarm against the remote MEP.

Only one CCM session is configured per MEP, and the 802.1p QoS configurable priority should the same as the one configured for the data path.

Loopback Function

The Ethernet OAM CFM loopback on the Tellabs 9200 troubleshoots connectivity to remote MEPs and MIPs.

Use the Ethernet OAM CFM loopback function to identify the connectivity fault location within an MA. Also known as CFM ping, the loopback verifies connectivity of a MEP via the MEP ID or MAC address. A loopback message (LBM) session initiates when the CFM ping sends a sequence of LBM from a local MEP to a remote MEP within the maintenance domain. The local MEP collects loopback replies (LBRs) from the remote MEP and then issues results of the loopback.

The loopback results contain the following information:

• Number of LBRs for each addressed MP

• Round trip delay, as minimum, maximum, and average values

• Transmit and receive counters, and packet loss, as a percentage

• Error conditions, like out of sequence LBR frames, number of duplicated LBRs received, and LBR frames with payload mismatch.

You can configure loopback frame size and priority to suit your network needs.

Linktrace Function

The Ethernet OAM CFM linktrace fault isolation tool troubleshoots and traces paths to remote MEPs and MIPs.

Use Ethernet OAM CFM linktrace to identify the connectivity fault location within an MA. A linktrace session initiates when the local MEP transmits a linktrace message (LTM) towards the remote MEP. Each MIP on the remote MEP path sends a linktrace reply (LTR) to the local MEP and forwards the LTM to the destination MEP. The destination MEP sends an LTR to the local MEP. Based on the responses, the local MEP displays an ordered list of responders to use in tracing the service path and localizing the network segment containing the fault.

Ethernet Service OAM Performance Management

Configure Tellabs 9200 Ethernet OAM PM functions, such as frame delay and frame delay variation (jitter) to manage Service Level Agreements to enforce QoS on Ethernet-based packet networks.

D R A

F T

14 Revision 3, 3/12

Ethernet OAM Configuration Guide About Ethernet Service OAM CFMTellabs SmartCore 9200 Series Ethernet Service OAM Performance Management

The Tellabs 9200 applies ITU-T Y.1731 and IEEE 802.1ag Ethernet OAM performance management protocols to enforce SLAs by measuring frame loss, frame delay and delay variations between configured MEPs and MIPs at defined locations within provider, operator, and customer domains. Refer to Figure 2, page 11 for a comparison of the standards.

• Frame Loss Ratio (FLR). FLR is defined as a ratio, expressed as a percentage, of the number of service frames not delivered divided by the number of service frames, where the number of service frames not delivered is the difference between the number of service frames sent to ingress UNI and the number of service frames received at egress UNI.

• Frame Delay (FD). FD can be specified as round-trip delay for a frame, where FD is defined as the time elapsed since start of transmission of the first bit of the frame by a source node until the reception of the last bit of the loop backed frame by the same source node, when the loop back is performed at the frame's destination node.

• Frame Delay Variation (FDV). FDV is a measure of the variations in the Frame Delay (FD) between a pair of Service Frames, where the service frames belong to the same CoS instance on a point-to-point ETH connection.

Ethernet OAM Performance Measurement (PM) functions measure the following characteristics of an Ethernet service network and are intended for point to point services:

• Ethernet Loss Measurement (Eth-LM).Y.1731 Eth-LM measures frame loss of Ethernet service frames by collecting bidirectional counter values of service frames between a pair of MEPs. The difference between the transmitted counters on a MEP and the received counters at the peer MEP form the basis for the near-end and far-end frame loss ratio.

• Ethernet Delay Measurement (Eth-DM).Y.1731 Eth-DM measures delay parameters between two MEPs by exchanging timestamped DMM PDUs. A MEP sends a sequence of DMM PDUs and then over multiple measurements, calculates statistical performance parameters. Eth-DM measures the following characteristics:

• Round Trip Delay

• One Way Delay

• Delay Variation

An Ethernet OAM PM measurement session (MS) takes place between an LMEP-RMEP pair along the 802.1p QoS priority path on which the function is activated. The LMEP-RMEP pair may be involved with multiple, per priority sessions. You must configure the RMEP for an MS. As with other OAM sessions, configure the PM session priority the same as the data flow priority.

The Tellabs 9200 Ethernet OAM PM framework is interoperable with other Tellabs products and provides the following:

• Implements DMM/DMR single-ended protocol for two-way measurements

• Collects DM for both near-end and far-end metrics at the same MEP

• Implements LMM/LMR single-ended protocol with multiple priority sessions and low rate message exchange

D R A

F T

Revision 3, 3/12 15


• Available on VLAN and VLAN Q-in-Q interfaces

• Provides proactive monitoring

• Stores reports in 15 minute and 24 hour buckets

• Allows multiple per-priority sessions on each service MEP

• HW assisted for accuracy and scalability

• Support both initiator and responder roles

• Both Near-end and Far-end measurements reported by the initiator

• Configurable session priority, measurement frequency

Ethernet OAM Loss Measurement

The Ethernet OAM loss measurement (Eth-LM) function measures how many frames are lost between two MEPs at a configured QoS level in an MA within a point-to-point network. Eth-LM collects bidirectional counter values of data service frames. Based on the difference between the frames transmitted by the local MEP and the frames received by the remote MEP, the Eth-LM function calculates frame loss and frame loss ratios for near-end and far-end sessions.

The Tellabs SmartCore 9200 Series supports a single-ended Eth-LM protocol. The single-ended Eth-LM protocol is an asymmetrical initiator-responder architecture. One MEP serves as initiator and generates Loss Measurement Message (LMM) PDUs towards the responder MEP at a configured QoS level. The responder MEP replies with Loss Measurement Replies (LMRs). This is similar to other OAM protocols like LBM-LBRs. The initiator MEP performs all data collection.

For each LM session, a MEP is either an initiator or a responder. The initiator schedules and collects the measurement while the responder only responds. Configure Eth-LM parameters at the initiator MEP but you must also activate the responder MEP. When configured, an Eth-LM session is continuous and operates until halted.

Loss Measurement is done by two nodes comparing how many data frames are present on a flow between a pair of LMMs / LMRs

Frame loss measurements involve the following Eth-LM parameters:

• TxFCf. Transmit frame count forward is the number of frames that the initiator (LMEP) sends to the responder (RMEP) within the configured interval.

• RxFCf. Receive frame count forward is the number of frames transmitted by the initiator that the responder actually received within the configured interval.

• TxFCb. Transmit frame count back is the number of frames that the responder sends to the initiator within the configured interval.

Figure 3, page 17 illustrates an example of an Ethernet OAM LM session. When the Tellabs 9200 executes the command, it firsts validates that the configured parameters are associated with the remote MEP ID.

D R A

F T

16 Revision 3, 3/12


Figure 3 Ethernet OAM PM Loss Measurement Function on a Tellabs 9200

Ethernet OAM Delay Measurement

Similar to Eth-LM, the two-way Eth-DM protocol is an asymmetrical initiator-responder architecture. One MEP serves as initiator and generates Delay Measurement Messages (DMM) PDUs towards the responder MEP. The responder MEP replies with Delay Measurement Replies (DMRs). As with other PM functions, an Eth-DM session is activated on an LMEP-RMEP pair on a configured 802.1p QoS priority. But in Eth-DM an MEP pair can be part of a multipoint MA, so the same MEP can activate Eth-DM sessions with multiple MEPs simultaneously.

Depending on timestamp fields, Eth-DM measures all three parameters:

• Round Trip Delay

• One-Way Delay

• Delay Variation

The accuracy of one-way delay measurement is directly affected by the synchronization of the Time of Day clock between the MEP pairs. This release does verify accurate Time Of Date synchronization so one-way delay is not supported.

When activating a DM session, apply the following parameters:

• Vlan priority. Set the vlan-priority to the value of the data flow vlan-priority being measured. The range is 0–7.

• Interval. Sets the period of time between two consecutive DMMs generated by the initiator. The range is 100–300,000 milliseconds. the default is 1,000 milliseconds. The interval is how ofen the LMEP transmits a DMM. The DMM contains a timestamp of sent time and the DMR responds timestamp sent, the timestamp received and the difference timestamp, which is the two-way (round trip) time delay.

D R A

F T

Revision 3, 3/12 17


• DMM frame size. Sets the frame size of the DMM and includes a TLV that is part of the total PDU frame. The range is 64–1,400 bytes. The default is 64 bytes.

• Selection offset. Sets the number of frames to offset during the collection period. For example, if you configure the selection offset as 3, the Tellabs 9200 bases IFDV calculations on DMR pairs that are three frames apart. Selection offset only impacts the delay variation calculation and influences fine or coarse granularity in the measurement.

• One way delay, two way delay, and IFDV bins. Refer to Delay Measurements Bin, page 18 for details.

• Delay boundary value. Refer to Delay Measurements Bin, page 18 for details.

• DMM version. Sets the DMM message version, either Y.1731-2008 or Y.1731-2011. This parameters determines interoperability with other equipment. Check with your Tellabs system sales engineer for interoperability guidelines before configuring.

Delay Measurements Bin

Delay measurement bins are collections of delay measurements distributed by time interval. Each bin represents a time range and contains the number of delay measurements that fall within the time range across the defined interval. Refer to Figure 4, page 19 for a graphical depiction of a delay measurements bin.

The Tellabs 9200 supports a total of five bins, with bin number 1 defining the lower delay boundary and bin 5 defining the upper delay boundary. Bins are defined for one-way, two-way, and IFDV for both near and far end measurements in 15-minute and 24-hour periods.

The delay boundary value for a bin must greater than the delay boundary value for the previous bin. For instance, when the delay boundary value for bin 1 is set to 5000, then the boundary value for bin 2 must be greater than 5,000.

All historical 24 hour equal a period of 24 hours. The current 24-hour bin displays the measurement collected since the current 24-hour period began.

Within the measured period, the Tellabs 9200 displays the lowest value, the highest value and the average value.

Figure 4 DMs Collected Within a 24-Hour or 15-Minute Time Period

The following optional bin parameters are configurable for theTellabs 9200:

• One-way delay bin. Indicates which bin that will be configured. The range is 1–5

D R A

F T

18 Revision 3, 3/12


• One-way delay boundary value. The configured boundary value for a bin, in microseconds. The default values are as follows:

– Bin 1 is 0 to 5,000

– Bin 2 is 5,000 to 10,000

– Bin 3 is 10,000 to 15, 000

– Bin 4 is 15,000 to 20,000

– Bin 5 is 20,000 to the measured period, either 15 minutes or 24 hours

• Two- way delay bin. Indicates which bin that will be configured. The range is 1–5.

• Two-way delay boundary value. The configured boundary value for a bin, in microseconds. The default values are as follows:

– Bin 1 is 0 to 10,000

– Bin 2 is 10,000 to 20,000

– Bin 3 is 20,000 to 30, 000

– Bin 4 is 30,000 to 40,000


• IFDV bin. Indicates which interframe delay variation (IFDV) bin will be configured. The range is 1–5.

• IFDV-way delay boundary value. The configured boundary value for a bin, in microseconds. The default values are as follows:

– Bin 1 is 0 to 2,000

– Bin 2 is 2,000 to 4,000

– Bin 3 is 4,000 to 8, 000

– Bin 4 is 8,000 to 10,000


Support for Round Trip and One-Way Delays

The Tellabs 9200 provides the following Ethernet OAM PM Y.1731 delay measurement capabilities:

• The Tellabs 9200 uses DM PDUs to measure frame delay between two MEPs.

• The two MEPs can be in a point to point or multipoint MA

• The frequency and priority of DM PDUs are configurable and are transparent to MIPs.

• Supports the DMM/DMR protocol for round-trip delay and one-way delay, also known as single-ended delay measurement.

• Support for multiple per priority sessions for a given service. The DMM is timestamped (TxTimeStampf) at DMM transmission time.

D R A

F T

Revision 3, 3/12 19


• The DMR copies the received TxTimeStampf and adds, RxTimeStampf, the time of receiving the DMM, and TxTimeStampb, the time of transmitting the DMR. These two values help account for processing time and calculate the one- way delay.

The Tellabs 9200 applies the DMM/DMR protocol to accurately measure the two-way delay. Two-way delay differs from round trip delay, as responder processing is not included, resulting in a measure of the net network delay.

Support for Delay Variation

The Tellabs 9200 applies the DMM/DMR protocol to provide one-way frame delay variation measurements. The measurement is known as InterFrame Delay Variation (IFDV) in Metro Ethernet Forum 10.2. IFDV is the difference between the one-way delays of a pair of DM frames. The configurable parameters for InterFrame Delay Variation (IFDV) include:

• Measurement Interval: The time over which IFDV is measured (e.g. 15 minutes for ongoing measurement)

• Period: The time between two consecutive DMM frames

• Selection Offset: index offset to identify pairs of frames that is sent DT apart during the measurement interval

The Figure 5, page 21 illustrates the selection function and delay measurement. (the frame pairs are denoted by colors)

TXi+1 – TXi is equal to the period parameter, equal for any i

A single measurement Si for the IFDV is defined as the absolute value of the difference of their one way delay, that is: Si = | Di+so - Di |

Figure 5 Frame Delay Measurement Intervals

Ingress MEP

Egress MEP

i i+1 i+so i+so+1 DM frame index:DM TX time: TXi TXi+1 TXi+so TXi+so+1

DM RX time: RXi RXi+so Di Di+so

time

time

MeasurementInterval

Measurement Interval

DM periodD R

A F T

20 Revision 3, 3/12

Configuring Ethernet OAM CFM

This chapter describes the guidelines and procedures for configuring Ethernet OAM CFM Tellabs SmartCore 9200 Series routers in the following sections:

• Service Types that Support Ethernet OAM, page 23

• Ethernet OAM and QoS Priority Settings, page 24

• CFM Maintenance Domain Framework Guidelines, page 24

• Configure a local MEP, page 25

Service Types that Support Ethernet OAM

The following Tellabs 9200 Ethernet physical interfaces and services, including LAG members, support Ethernet OAM:

• Port (physical interface)

• Point-to-point services

– Pseudowire circuits

– Port

– VLAN

– Q-in-Q. Double-to-Single and Double-to-Double.

– LSPs

– Port-to-port circuits

– Port

– VLAN. With range and without range.

– Q-in-Q. With inner VLAN range, without inner VLAN range, with inner VLAN translation, and without inner VLAN translation.

– Circuit bundles

– LAG interfaces

• VPLS Subinterface types (Point-to-multipoint)

The 9200 series provides only Up MEP support

– Port

– Untagged

– Single VLAN tag

– Two VLAN tags

D R A

F T

Revision 3, 3/12 23

Configuring Ethernet OAM CFM Ethernet OAM Configuration GuideEthernet OAM and QoS Priority Settings Tellabs SmartCore 9200 Series

– VLAN untagged interface

– Untagged

– VLAN tag 0

– VLAN access mode

– VLAN trunk mode

– Q-in-Q trunk mode

– Q-in-Q access mode

Ethernet OAM and QoS Priority Settings

The following conditions apply when configuring QoS on Ethernet OAM PM sessions.

• Ethernet OAM PDUs are control packets which flow through the same path as data packets and are used to monitor data flow, and identify and isolate any faults in the data path.

• The priority of Ethernet OAM PDUs is determined by the 802.1.p priority bits setting. If double tagged, then the outer tag priority applies. If untagged, then the bits setting in not applicable.

• An Ethernet OAM session is an instance of an Ethernet OAM function activated by a MEP for a configured service priority. The possible instantiation of sessions is different for each function, both in the standards and in common implementations. Generally, CFM functions run on a single configured priority, while PM functions run on multiple concurrent priorities of the same service.

• Down MEP PDUs are not subject to line card processing like policing and remarking.

• Up MEP PDUs process through system equipment and subject to line card processing.

• Prioritizing Ethernet OAM PDUs do not affect user data QoS but there is fate sharing of both data types. Fate sharing takes place because Ethernet OAM PDUs merge with the service flow of the same QoS priority and traverse exactly the same system and network path. This assures that service OAM functions are indicative of user traffic behavior.

CFM Maintenance Domain Framework Guidelines

When configuring the Tellabs 9200 to provide Ethernet service OAM apply the guidelines as follows:

• MD name, level, and format

• MA name and level

• Local MEPs. Configure under an MA associated with a service interface.

D R A

F T

24 Revision 3, 3/12

Ethernet OAM Configuration Guide Configuring Ethernet OAM CFMTellabs SmartCore 9200 Series Configuring CFM Functions on a Local MEP

• Remote MEPs. Configure or auto-discover. In the case of explicit configuration, configure the MEP list with remote and local MEP IDs. To activate the MEP list, administratively enable the list. Use the MEP list only to support AIS and RDI.

• Enabling and disabling CFM within an MA occurs at the at the service level. Associate the service to the MA to enable and activate the CFM session.

• MIPs are automatically configured on a service interface that does not have a MEP

Configuring CFM Functions on a Local MEP

The following sections provide configuration examples to enable CFM functionality:

• Configure a local MEP, page 25

• Configure CCM on local MEP, page 27

• Configuring Loopback, page 27

• Configuring Linktrace, page 28

Configure a local MEP

The following example shows the a sample configuration of an MD, an MA, and MEP on the local interface.

1. Configure an MD by setting an MD name and level, an MA by setting an MA name and level, and MEP by setting a MEP ID. Commit changes.9200# config eth-oam cfm md md1 level 1 md-format 1 ma ma2 ma-format 2 mep 3 3

9200#(config-mep-3)# commitCommit complete.

2. Configure MEP direction. Commit changes.9200# config eth-oam cfm md md1 ma ma2 direction down

3. Assign a MEP to a physical or logical interface.9200#(config-mep-3)# interface ge-1/2/2/2.1 9200#(config-mep-3)# commitCommit complete.

4. Administratively enable the MEP9200#(config-mep-3)# admin enable 9200#(config-mep-3)# commitCommit complete.

5. Optionally, to modify additional MEP parameters, first administrative disable the MEP, modify MEP parameters, then administratively enable the MEP.9200#(config-mep-3)# ccm enable ais-interval 1min 9200#(config-mep-3)# commitCommit complete.

9200#(config-mep-3)# admin enable

D R A

F T

Revision 3, 3/12 25

Configuring Ethernet OAM CFM Ethernet OAM Configuration GuideConfiguring CFM Functions on a Local MEP Tellabs SmartCore 9200 Series

9200#(config-mep-3)# commitCommit complete.

6. Exit the configuration mode.9200#(config-mep-3)# exit

7. Display the configuration parameters for the local MEP.9200# show eth-oam cfm md

eth-oam cfm md md1 ma ma2 mep 3 macAddress 00:1c:ae:00:00:fc ccm-transmitted 0 ping-responses-transmitted 0 ais-transmitted 0 cfm-ping-status dest-mep-id 0 cfm-ping-status dest-mac-addr 00:00:00:00:00:00 cfm-ping-status num-packets-transmitted 0 cfm-ping-status num-packets-received 0 cfm-ping-status num-packets-received-out-of-order 0 cfm-ping-status transmitLbmResult true cfm-ping-status num-packets-received-bad-msdu 0 cfm-ping-status pkt-priority 0 cfm-ping-status drop disable cfm-ping-status last-lbm-seq-num 0 cfm-ping-status next-lbm-seq-num 0 cfm-traceroute-status dest-mep-id 0 cfm-traceroute-status dest-mac-addr 00:00:00:00:00:00 cfm-traceroute-status transmitLtmResult true cfm-traceroute-status priority 0 cfm-traceroute-status ttl 64 cfm-traceroute-status lastLtmSeqNum 0 cfm-traceroute-status nextLtmSeqNum 0 cfm-traceroute-status unexpectedTraceRouteRespReceivedNum 0 cfm-traceroute-status useForwardingDbOnly 0 dm 4004 4LMep: 3; MA: ma2; RMep: 4004; Vlan-priority: 4 Current 15min: [Eth-DM compromised][Eth-DM cleared][DMM/DMR lost 15]Elapsed time: 821 secs; End time: Sun Jan 2 17:26:47 2011 Near End Two Way Delay: min/avg/max(microsec)/bincount[1-5]= 1/2/3 1/2/3/4/5 Near End Frame Delay Var (Two Way): min/avg/max(microsec)/bincount[1-5]= 10/11/12 10/11/12/13/14 Near End Frame Delay Var (One Way): min/avg/max(microsec)/bincount[1-5]= 13/14/15 13/14/15/16/17 Far End Frame Delay Var (One Way): min/avg/max(microsec)/bincount[1-5]= 16/17/18 16/17/18/19/20 LMep: 3; MA: ma2; RMep: 4004; Vlan-priority: 4 Current 24hrs: [Eth-DM compromised][DMM/DMR lost 24]Elapsed time: 921 secs; End time: Sun Jan 2 17:26:47 2011 Near End Two Way Delay: min/avg/max(microsec)/bincount[1-5]= 101/102/103 101/102/103/104/105 Near End One Way Delay: min/avg/max(microsec)/bincount[1-5]= 104/105/106 104/105/106/107/108 Far End One Way Delay: min/avg/max(microsec)/bincount[1-5]= 107/108/109 107/108/109/110/111

D R A

F T

26 Revision 3, 3/12


Near End Frame Delay Var (Two Way): min/avg/max(microsec)/bincount[1-5]= 110/111/112 110/111/112/113/114 Near End Frame Delay Var (One Way): min/avg/max(microsec)/bincount[1-5]= 113/114/115 113/114/115/116/117 Far End Frame Delay Var (One Way): min/avg/max(microsec)/bincount[1-5]= 116/117/118 116/117/118/119/120 LMep: 3; MA: ma2; RMep: 4004; Vlan-priority: 4 ...(rest of output omitted)

Configure CCM on local MEP

The following example show how to enable CCMs on a configured MEP.

1. Enter MA configuration mode. 9200# config eth-oam cfm md md1 ma ma2

2. If required, configure CCM settings.9200(config-ma-2)# cc-interval 1sec cc-priority 0

3. Enter MEP configuration mode.9200(config-ma-2)# mep 3

4. Enable CC messaging on the MEP. Commit changes.9200(config-mep-3)# ccm enable9200(config-mep-3)# commitCommit complete.

5. Administratively enable the MEP.9200#(config-mep-3)# admin enable 9200#(config-mep-3)# commitCommit complete.

6. Display the configuration parameters for the local MEP.9200# show eth-oam cfm md1

eth-oam cfm md md1 ma ma2...(rest of output omitted)

Configuring Loopback

To initiate a loopback session, perform the following steps.

D R A

F T

Revision 3, 3/12 27


4. Display CFM ping results.9200(config-mep-3)# show eth-oam cfm md md1 ma ma2 mep 3 cfm-ping-status

cfm-ping-status dest-mep-id 0cfm-ping-status dest-mac-addr 00:00:00:00:00:00cfm-ping-status num-packets-transmitted 0cfm-ping-status num-packets-received 0cfm-ping-status num-packets-received-out-of-order 0cfm-ping-status transmitLbmResult falsecfm-ping-status num-packets-received-bad-msdu 0cfm-ping-status pkt-priority 0cfm-ping-status drop disablecfm-ping-status last-lbm-seq-num 0cfm-ping-status next-lbm-seq-num 09200#

Configuring Linktrace

Use Ethernet OAM CFM linktrace to identify the connectivity fault location within an MA. A linktrace session initiates when the local MEP transmits a linktrace message (LTM) towards the remote MEP. Each MIP on the remote MEP path sends a linktrace reply (LTR) to the local MEP and forwards the LTM to the destination MEP. The destination MEP sends an LTR to the local MEP. Based on the responses, the local MEP displays an ordered list of responders to use in tracing the service path and localizing the network segment containing the fault.

1. Enter MEP configuration mode. 9200# config eth-oam cfm md md1 ma ma2 mep 3

2. Activate CFM linktrace on the local MEP to the remote MEP. Commit changes.9200(config-mep-3)# cfm-traceroute dest-mep-id 15 priority 19200(config-mep-3)# commitCommit complete.

3. Display CFM traceroute results.9200(config-mep-3)# show eth-oam cfm md md1 ma ma2 mep 3 cfm-ping-traceroute-status

cfm-traceroute-status dest-mep-id 0cfm-traceroute-status dest-mac-addr 00:00:00:00:00:00

Step Command Entry Purpose

1. 9200# config eth-oam cfm md md1 ma ma2 mep 3 Enter MEP configuration mode.

2. 9200# 9200(config-mep-3)# cfm-ping dest-mep-id 15 priority 1

9200(config-mep-3)# commitCommit complete.

Activate CFM ping on the local MEP to the remote MEP. Commit changes

3. 9200(config-mep-3)# show eth-oam cfm md md1 ma ma2 mep 3 cfm-ping-status

Display CFM ping results.

D R A

F T

28 Revision 3, 3/12


cfm-traceroute-status transmitLtmResult falsecfm-traceroute-status priority 0cfm-traceroute-status ttl 0cfm-traceroute-status lastLtmSeqNum 0cfm-traceroute-status nextLtmSeqNum 0cfm-traceroute-status unexpectedTraceRouteRespReceivedNum 0cfm-traceroute-status useForwardingDbOnly 09200#

Configure RDI

Configure Ethernet OAM CFM.

Configuring CFM Ping


Configuring CFM Traceroute


Configure AIS

To configure AIS on an Ethernet OAM interface, perform the following steps.

To display AIS status, enter the following command.9200# show eth-oam cfm md md1 ma detail

Domain: md1; Level: 1; Format: 2 Association: ma1; Format: 2; Direction: up Type: none; Instance: GE1/5/2/2.1 Mep list admin: disable CC interval: 10sec; CC loss factor: 35; Hold time: 12 hrs AIS Rx admin: enable; Ais expiry threshold: 35; AIS state: none Num of local MEP: 0; Num of remote MEP: 0

Domain: md1; Level: 1; Format: 2 Association: ma2; Format: 2; Direction: up Type: none; Instance: ge-1/5/2.2.2 Mep list admin: disable CC interval: 10sec; CC loss factor: 35; Hold time: 12 hrs AIS Rx admin: enable; Ais expiry threshold: 35; AIS state: none


1. 9200# config eth-oam cfm md md1 ma ma2 Enter MA configuration mode.

2. 9200# 9200(config-ma-2)# ais-rx-admin enable

9200(config-ma-2)# commitCommit complete.

Activate AIS on the MA. Commit changes

3. 9200(config-ma-2)# show eth-oam cfm md md1 ma ma2 Display AIS configuration.D R

A F T

Revision 3, 3/12 29


Num of local MEP: 0; Num of remote MEP: 0

9200#

D R A

F T

30 Revision 3, 3/12

Configuring Ethernet OAM PM

This chapter describes the guidelines and procedures to configure Ethernet OAM performance management on the Tellabs SmartCore 9200 Series routers in the following sections:

• Ethernet OAM and QoS Priority Settings, page 31

• Configuration Guidelines, page 31

• Configuring PM Functions on a Local MEP, page 34

Ethernet OAM and QoS Priority Settings

The following conditions apply when configuring QoS on Ethernet OAM PM sessions.

• Ethernet OAM PDUs are control packets which flow through the same path as data packets and are used to monitor data flow, and identify and isolate any faults in the data path.

• The priority of Ethernet OAM PDUs is determined by the 802.1.p priority bits setting. If double tagged, then the outer tag priority applies. If untagged, then the bits setting in not applicable.

• An Ethernet OAM session is an instance of an Ethernet OAM function activated by a MEP for a configured service priority. The possible instantiation of sessions is different for each function, both in the standards and in common implementations. Generally, CFM functions run on a single configured priority, while PM functions run on multiple concurrent priorities of the same service.

• Down MEP PDUs are not subject to line card processing like policing and remarking.

• Up MEP PDUs process through system equipment and subject to line card processing.

• Prioritizing Ethernet OAM PDUs do not affect user data QoS but there is fate sharing of both data types. Fate sharing takes place because Ethernet OAM PDUs merge with the service flow of the same QoS priority and traverse exactly the same system and network path. This assures that service OAM functions are indicative of user traffic behavior.

Configuration Guidelines

When configuring the Tellabs 9200 to provide Ethernet service OAM, apply the guidelines described in the following sections:

• Ethernet OAM PM DM Configuration Guidelines, page 32

• Ethernet OAM PM LM Configuration Guidelines, page 33

D R A

F T

Revision 3, 3/12 31

Configuring Ethernet OAM PM Ethernet OAM Configuration GuideConfiguration Guidelines Tellabs SmartCore 9200 Series

Ethernet OAM PM DM Configuration Guidelines

Apply the following guidelines when configuring Ethernet OAM PM DM on a network interface acting as a MEP in an MA:

• The measurement is between a given Local MEP (LMEP) and Remote MEP (RMEP).

• The LMEP at the node where the DM is launched functions as an initiator and the specified RMEP as a responder.

• A DM session is identified by the MEP pair and QoS; there could be multiple (per QoS) sessions for one MEP.

• The configuration of DM function is performed only at the initiator node.

• The responder MEP reacts automatically (similar to responder function of loopback or linktrace).

• A MIP must transfer PM frames transparently without processing delay and reordering

• Configure a DM function on a point-to-point MA or a multipoint MA consisting of a single configured LMEP and a single configured RMEP. The LMEP can be an up MEP or a down MEP.

• Configure an DM function on a interface indicated on table L2OAM-498.

• The Tellabs 9200 does not allow DM sessions at the port level and blocks configuration at the port level. Therefore, the Tellabs 9200 does not support DM sessions on a VLAN.

• You can configure DM sessions on down MEP and up MEP on the same interface simultaneously. This allows performance measurements on two network segments of for same service.

• Apply the same 802.1p QoS priority settings configured for the data service to the priority setting for transmitted DMMs and DMRs.

• DMM and DMR frames are marked as drop ineligible.

• A LAG does not support DM sessions.

The Tellabs 9200 collects DM metrics as follows:

• DM runs continuously, and collects measurements in current and previous 32 15-minute intervals, and current and previous 24-hour intervals

• Collected information includes:

• Near end two way delay: Min, Max, Average, Distribution

• Near end one way IFDV (near end, far end): Max, Average, Distribution

• Far end one way IFDV (near end, far end): Max, Average, Distribution

• Near end two way IFDV (near end, far end): Max, Average, Distribution

• Distribution is represented by measurement bins. Measurement bins indicate distribution of delay metrics. Each bin is assigned a time range and contains the number of measured samples that fall within the range across the measurement

D R A

F T

32 Revision 3, 3/12

Ethernet OAM Configuration Guide Configuring Ethernet OAM PMTellabs SmartCore 9200 Series Configuration Guidelines

interval. The lower bound of the time range (Lrange) is configurable. The Upper value is assumed to be the following bin Lrange. There are five configurable ranges.

Ethernet OAM PM LM Configuration Guidelines

Apply the following considerations when configuring Ethernet OAM PM LM on a network interface acting as a MEP in an MA:

• LM is only available on point-to-point service topologies, and not on multipoint service topologies.

• Configure an LM function on a point-to-point MA consisting of a single configured LMEP and a single configured RMEP. The LMEP can be an up MEP or a down MEP.

• You can configure LM sessions on down MEP and up MEP on the same interface simultaneously. This allows performance measurements on two network segments of for same service.

• Configure an LM function on a VLAN level interface. LM functions can operate on VLAN Q-in-Q. For Q-in-Q, when the sub-interface is classified by two tags, the OAM PDU is also classified with the same two tags. Only the outer tag priority classifies the data flow and LM session.

• Initiator/ responder designation similar to DM

• A LM session is identified by the MEP pair and QoS; there could be multiple (per QoS) sessions for one MEP

• Most configuration of LM function is performed at the initiator node.

• Responder needs to be activated.

• The LM interval is configurable with a range of 100–80000 milliseconds, default is 10000 milliseconds.

• Apply the same 802.1p QoS priority settings configured for the data service as the priority for the LM session.

• LMM and LMR frames are marked as drop ineligible.

The Tellabs 9200 collects LM metrics as follows:

• LM runs continuously, and collects measurements in performance monitoring style, that is, current and previous 32 15-minute buckets and current and previous 24-hour buckets

• The LM metrics collected are:

• Near end RX and TX counters

• Far end RX and TX counters

• Near end lost frame counters

• Far end lost frame counters

• Near end frame loss ratio (FLR) as a percentage

D R A

F T

Revision 3, 3/12 33

Configuring Ethernet OAM PM Ethernet OAM Configuration GuideConfiguring PM Functions on a Local MEP Tellabs SmartCore 9200 Series

• Far end FLR as a percentage

Configuring PM Functions on a Local MEP

The following sections provide configuration examples to enable CFM functionality:

• Configure LM Functions on a Local MEP, page 34

• Configure DM Functions on a Local MEP, page 35

Configure LM Functions on a Local MEP

This procedure assumes that you have configured both the local and remote MEPs. To configure an LM session, perform the following steps.


2. Activate LM on the local MEP to the remote MEP. Commit changes.9200(config-mep-3)# lm 300 rmep 13 vlan-priority 1 interval 20000 mode initiator-responder9200(config-mep-3)# commitCommit complete.

3. Display LM results.9200(config-mep-3)# show eth-oam cfm md md1 ma ma2 mep 3 lm 300 current 24hrsLMep: 3; MA: ma2; RMep: 13; Vlan-priority: 1 Current 24hrs: [Eth-DM compromised][LMM/LMR lost 24]Elapsed time: 1221 secs; End time: Sun Jan 2 17:26:53 2011 Near End Frames Rx: 11 Near End Frames Tx: 12 Far End Frames Rx: 13 Far End Frames Tx: 14 Near End Frames Lost: 15 Far End Frames Lost: 16 Near End FLR percentage: 17 Far End FLR percentage: 18

Interpretation Table for Loss Measurements

LMep Configured ID of initiator MEP

MA Configured name of maintenance association

RMep Configured ID of responder MEP

Vlan-priority Configured QoS VLAN priority of the LMM.

D R A

F T

34 Revision 3, 3/12

Ethernet OAM Configuration Guide Configuring Ethernet OAM PMTellabs SmartCore 9200 Series Configure DM Functions on a Local MEP

Configure DM Functions on a Local MEP

Configure Ethernet OAM DM on a defined LMEP-RMEP pair and a specified QoS priority. Ethernet OAM DM functions use the same framework as Ethernet OAM CFM.

This procedure assumes that you have configured both the local and remote MEPs. To configure an DM session, perform the following steps.


2. Activate DM on the local MEP to the remote MEP. Commit changes.9200(config-mep-3)# dm 4 rmep 4004 vlan-priority 4 interval 150000 DMM-version 1 9200(config-mep-3)# commitCommit complete.

Current 24 hrs Eth-LM compromisedEth-LM clearedLMM/LMR lost

For a 24-hour period, the number of Eth-LM frames:

Not sent

Cleared

LMM and LMR frames lost during transmission

Elasped time The time elapsed since the time period reset. For a 24-hour period, the time elapsed since midnight. For a 15-minute period, the time elapsed since the hour, 15, 30, and 45 minutes after the hour.

End time For current time, the time since the last collection.

Near End Frames, Tx and Rx

Near End is the Local MEP

Rx – Number of frames received by the responder MEP.

Tx – Number of frames sent by the initiator MEP.

Far End Frames, Tx and Rx

Far End is the Remote MEP

Rx – Number of frames received by the responder MEP.

Tx – Number of frames sent by the initiator MEP.

Near End Frames Lost At the local MEP, the difference between the number of frames sent by the initiator MEP and received by the responder MEP.

Far End Frames Lost At the remote MEP, the difference between the number of frames sent by the initiator MEP and received by the responder MEP.

Near End FLR percentage

At the local MEP, the frame loss ration (FLR) expressed as a percentage.

Far End FLr percentage

At the remote MEP, the frame loss ration (FLR) expressed as a percentage.

D R A

F T

Revision 3, 3/12 35

Configuring Ethernet OAM PM Ethernet OAM Configuration GuideConfigure DM Functions on a Local MEP Tellabs SmartCore 9200 Series

3. Display LM results.9200(config-mep-3)# show eth-oam cfm md md1 ma ma2 mep 3 dm 300 current 24hrs

LMep: 3; MA: ma2; RMep: 4004; Vlan-priority: 4 Current 15min: [Eth-DM compromised][Eth-DM cleared][DMM/DMR lost 15]Elapsed time: 821 secs; End time: Sun Jan 2 17:26:47 2011 Near End Two Way Delay: min/avg/max(microsec)/bincount[1-5]= 1/2/3 1/2/3/4/5 Near End One Way Delay: min/avg/max(microsec)/bincount[1-5]= 4/5/6 4/5/6/7/8 Far End One Way Delay: min/avg/max(microsec)/bincount[1-5]= 7/8/9 7/8/9/10/11 Near End Frame Delay Var (Two Way): min/avg/max(microsec)/bincount[1-5]= 10/11/12 10/11/12/13/14 Near End Frame Delay Var (One Way): min/avg/max(microsec)/bincount[1-5]= 13/14/15 13/14/15/16/17 Far End Frame Delay Var (One Way): min/avg/max(microsec)/bincount[1-5]= 16/17/18 16/17/18/19/20 LMep: 3; MA: ma2; RMep: 4004; Vlan-priority: 4 Current 24hrs: [Eth-DM compromised][DMM/DMR lost 24]Elapsed time: 921 secs; End time: Sun Jan 2 17:26:47 2011 Near End Two Way Delay: min/avg/max(microsec)/bincount[1-5]= 101/102/103 101/102/103/104/105 Near End One Way Delay: min/avg/max(microsec)/bincount[1-5]= 104/105/106 104/105/106/107/108 Far End One Way Delay: min/avg/max(microsec)/bincount[1-5]= 107/108/109 107/108/109/110/111 Near End Frame Delay Var (Two Way): min/avg/max(microsec)/bincount[1-5]= 110/111/112 110/111/112/113/114 Near End Frame Delay Var (One Way): min/avg/max(microsec)/bincount[1-5]= 113/114/115 113/114/115/116/117 Far End Frame Delay Var (One Way): min/avg/max(microsec)/bincount[1-5]= 116/117/118 116/117/118/119/120 ...(rest of output omitted)D R

A F T

36 Revision 3, 3/12

Ethernet OAM Configuration Guide Link Level 802.3ah Ethernet OAMTellabs SmartCore 9200 Series About Link Level 802.3ah EFM

Link Level 802.3ah Ethernet OAM

This chapter describes the Tellabs SmartCore 9200 Series link level 802.3ah Ethernet service Operations, Administration, and Maintenance (OAM) application for fault monitoring and performance management on the single-hop in the network at the link access side, also known as Ethernet in the First Mile (EFM) in the following sections:

• About Link Level 802.3ah EFM, page 39

• Configuring Link Level 802.3ah Ethernet OAM on the Tellabs 9200, page 40

About Link Level 802.3ah EFM

Link level Ethernet OAM as defined in IEEE 802.3ah provides standards to monitor link operation and improve fault isolation at the CPE side of the network. 802.3ah is used exclusively as a single-hop in the network at the link access side of the network, usually the connection between the CPE and the PE as shown in Figure 1, page 39.

Figure 1 Ethernet OAM with 802.3ah Link Level Monitoring

Link level 802.3ah Ethernet OAM includes the following functions:

• Discovery and link monitoring. Link monitoring provides functions to detect failed and degraded connections. When 802.3ah Ethernet OAM is enabled on an interface, the interface discovers and monitors its peer on the link. Discovery can be either active or passive. In active

D R A

F T

Revision 3, 3/12 39

Link Level 802.3ah Ethernet OAM Ethernet OAM Configuration GuideConfiguring Link Level 802.3ah Ethernet OAM on the Tellabs 9200 Tellabs SmartCore 9200 Series

mode, the interface initiates discovery and monitors the peer. In passive mode, the peer initiates discovery. Link monitoring takes place with transmission of OAM PDUs to communicate mode, capabilities, and status.

• Fault signaling provides fault detection mechanisms for a network interface to signal another that it has detected an error during runtime. OAM fault signaling events include:

– Link fault. A link loss is a fault detected by the remote that the receive path is broken.

– Dying gasp. A dying gasp signals the remote device that an unrecoverable fault has occurred.

– Critical event. An unspecified, vendor specific failure condition has occurred.

• Remote loopback. Configure and activate remote loopback to send test traffic after initiating a loopback. Remote loopback on the network interface puts the other network interface into a state whereby all inbound traffic is immediately reflected back onto the link as a form of auto-OAM client detection. Interface loopback is a test protocol used for turn up, commissioning, and performance monitoring.

• Remote Failure Indication (RDI). On the receive side, the network interface processes process remote failure indication from a peer and generate notifications in response to the RDI.

• Link performance monitoring provides detection and notification of link level 802.3ah Ethernet OAM performance degradation or failure during run-time that includes display of following OAM PDU statistics:

– Rx and TX OAM PDU information

– Rx and Tx remote loopback control OAM PDUs

– Rx for unsupported codes

– Rx Error Frames

• Ability to send test traffic (test data packets Tx, Rx, and Errored) on demand after initiation of a loopback.

Configuring Link Level 802.3ah Ethernet OAM on the Tellabs 9200

802.3ah Ethernet OAM capabilities provided by the Tellabs 9200 allows you to monitor Ethernet links through the discovery and monitoring of interfaces or nodes that are OAM-enabled. The Tellabs 9200 can also help troubleshoot with remote loopback testing to ensure connectivity between two OAM entities providing critical event trap generation depending on the response to remote failure indicators, and retrieval of OAM PDU statistics.

D R A

F T

40 Revision 3, 3/12

Ethernet OAM Configuration Guide Link Level 802.3ah Ethernet OAMTellabs SmartCore 9200 Series Configuring Link Level 802.3ah Ethernet OAM on

This section describes how to use the CLI to configure link level 802.3ah Ethernet OAM capabilities for the Tellabs 9200, in the following sections:

• 802.3ah OAM Configuration Guidelines, page 41

• Configuring 802.3ah OAM on an Interface, page 42

• Configuring 802.3ah OAM Loopback, page 43

• Configuring 802.3ah OAM Testing, page 43

• Displaying 802.3ah OAM PDU Statistics, page 44

• Clearing 802.3ah OAM PDU Functions and Statistics, page 44

802.3ah OAM Configuration Guidelines

When configuring link level 802.3ah Ethernet OAM, apply the guidelines in this section.

By default, 802.3ah Ethernet OAM EFM is enabled.

In active mode, the interface initiates the discovery process, while in passive mode the interface waits for the peer to initiate the process. The interface in both modes can send various OAM PDUs.

A network interface enabled for 802.3 active mode can:

• initiate the OAM discovery process

• send information PDUs

• may send event notification PDUS

• may send variable request/response PDUs

• may send loopback control PDUs

A network interface enabled for 802.3 passive mode can:

• wait for a remote device to initiate the OAM discovery process

• send information PDUs

• may send event notification PDUs

• may respond to variable request PDUs

• may react to received loopback control PDUs

• Not send variable request or loopback control PDUs

802.3ah configuration includes:

• Administratively enable or disable 802.3ah OAM per globally at the network element level.

• Administratively enable or disable 802.3ah OAM per interface.

• Configure OAM modes, either active or passive.

• In active mode, configure to receive a remote loopback.

D R A

F T

Revision 3, 3/12 41


• Initiate a test function with:

– Set packet size, period, test pattern

– Stop and start test data transmission

• Collect statistics

Configuring 802.3ah OAM on an Interface

The OAM discovery process starts when 802.3ah Ethernet link level OAM is enabled on an Ethernet interface, globally on the node, when OAM mode is set to active. The Ethernet interface discovers the following about the remote peer through exchange of OAM PDUs:

• OAM PDU configuration, such as the maximum OAM PDU size that an interface can support.

• Platform identity, which is determined by a combination of an Organization Unique Identifier (OUI) and 32-bits of vendor-specific information. The OUI allocation is typically the first three bytes of a MAC address.

• The link goes down and comes back up again.

• An OAM PDU is not received on either link for 5 seconds.

Other than enabling Ethernet OAM on an interface, no OAM discovery-specific configuration is needed.

To enable link level and discovery and monitoring on an interface, perform the following steps.

To display EFM results, enter the show eth-oam efm command.9200(config-efm)# show eth-oam efm GigE-5/1

Link: GigE-5/1

Local OAM client:Admin state: enable; Oper state: up; Failure reason: none;Mode: active; Max OAM PDU size: 64; Loopback Ctrl: deny;Loopback status: remote; Functions supported: none;

Test pattern: 1010; Status: in progress; Interval: 5s;Pkts sent: 100; Pkts in queue: 400


1. 9200# config eth-oam efm session-timeout 10 link GigE-5/1 lpbk-ctrl accept mode passive max-frame-size 1524

9200(config-efm)# commitCommit complete.

Enter EFM configuration mode and set 802.1ah monitoring parameters.

2. 9200# 9200(config-efm)# exit Exit EFM configuration mode.

3. 9200(config-efm)# show eth-oam efm Display EFM results.D R

A F T

42 Revision 3, 3/12

Ethernet OAM Configuration Guide Link Level 802.3ah Ethernet OAMTellabs SmartCore 9200 Series Configuring Link Level 802.3ah Ethernet OAM on

Remote OAM client:MAC Address: 00:30:96:fe:5d:fb; Mode: Active; Max OAM PDU size: 0;Functions Supported: loopback;

Configuring 802.3ah OAM Loopback

To start and stop link level loopback on an interface, perform the following steps.

Display EFM loopback results.8800# show eth-oam eth-oam efm GigE-5/1 summary

No of Active OAM links: 5No of Remote Lpbk session initiated: 3No of Remote Lpbk session accepted: 2

Configuring 802.3ah OAM Testing

To start and stop link level testing on an interface, perform the following steps.

Display EFM OAM test results.

9200# show eth-oam eth-oam efm GigE-5/1 stats

OAMPDU Statistics:

Category counts Category counts--------- ------- --------- ------Tx Info 900078 Rx Info 0Tx Rem Lpbk Ctrl 1002 Rx Rem Lpbk Ctrl 0


1. 9200# config eth-oam efm GigE-5/1 Enter EFM configuration mode.

2. 9200# 9200(config-efm)# start-lpbk


Initiate 802.3ah loopback.

3. 9200(config-efm)# show eth-oam efm Display EFM results.

4. 9200# 9200(config-efm)# stop-lpbk


Stop 802.3ah loopback.


1. 9200# config eth-oam efm GigE-5/1 Enter EFM configuration mode.

2. 9200# 9200(config-efm)# test pattern mtu 100 interval 10 num-of-packet 100


Initiate 802.3ah test.

3. 9200(config-efm)# show eth-oam efm stats Display EFM results.

D R A

F T

Revision 3, 3/12 43


Rx Unsupported 0Rx Error Frames 0

Test Data Statistics:

Category counts Category counts Category counts--------- ------- --------- ------- --------- ------Tx Packets 999 Rx Packets 999 Error Packets 0

Displaying 802.3ah OAM PDU Statistics

Display EFM OAM statistics test results.

9200# show eth-oam eth-oam efm GigE-5/1 stats

txInfo: <uint32>txRemLpbkCtrl: <uint32>rxInfo: <uint32>rxRemLpbkCtrl: <uint32>rxUnsupported: <uint32>rxErrorFrames: <uint32>

Clearing 802.3ah OAM PDU Functions and Statistics

The Tellabs SmartCore 9200 Series provides commands to clear various 802.3ah functions.

To clear 802.3ah statistics, enter the following command.9200# eth-oam efm link GigE-1/5 clear-stats

To clear an 802.3ah test, enter the following command.9200# eth-oam eth-oam link efm GigE-1/5 clear-test

To clear 802.3ah configuration on an interface, enter the following command.9200# eth-oam eth-oam link efm GigE-1/5 clear-oamD R

A F T

44 Revision 3, 3/12

tellabs genios ethernet oam configuration guide a f t d...

Documents