3he09527aaaa - v1 - 7210 Sas M, T, X, r6 Oam A

Alcatel-Lucent
Service Access Switch| Release 7.0 Rev.01

7 2 1 0 S A S M , T, X , R 6
OAM and Diagnostics Guide
3H E 09 52 7A AAA
3HE09527AAAA
Alcatel-Lucent Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to be disclosed
or used except in accordance with applicable agreements.
Copyright 2014 © Alcatel-Lucent. All rights reserved.
This document is protected by copyright. Except as specifically permitted herein, no portion of the provided information can be reproduced in any form, or by any means, without
prior written permission from Alcatel-Lucent.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.
The information presented is subject to change without notice.
Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2013 Alcatel-Lucent. All rights reserved.

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Getting Started
Alcatel-Lucent 7210 SAS-Series Services Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Mirror Services
Service Mirroring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Mirror Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Mirror Source and Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Mirroring Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Mirroring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Configuration Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Configuring Service Mirroring with CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Mirror Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Defining Mirrored Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Basic Mirroring Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Mirror Classification Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Common Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Configuring a Local Mirror Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Configuring a Remote Mirror Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Service Management Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Modifying a Local Mirrored Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Deleting a Local Mirrored Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Modifying a Remote Mirrored Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Deleting a Remote Mirrored Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
OAM and SAA

OAM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Two-Way Active Measurement Protocol (TWAMP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Configuration Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
LSP Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
SDP Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
SDP Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
SDP MTU Path Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Service Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
VPLS MAC Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
MAC Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
MAC Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
CPE Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76
MAC Populate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
MAC Purge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
VLL Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
VCCV Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
7210 SAS-M, T, X, R6 OS OAM and Diagnostic Guide Page 3

Table of Contents
Automated VCCV-Trace Capability for MS-Pseudowire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

MPLS-TP On-Demand OAM Commands (Supported only on 7210 SAS-R6 and 7210 SAS-T). . . . . .85
MPLS-TP Pseudowires: VCCV-Ping/VCCV-Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
MPLS-TP LSPs: LSP-Ping/LSP Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
MPLS-TP Show Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Static MPLS Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
MPLS-TP Tunnel Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
MPLS-TP Path configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
MPLS-TP Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
BFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
MPLS TP Node Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
MPLS-TP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Services using MPLS-TP PWs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
MPLS-TP DEBUG COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Ethernet Connectivity Fault Management (ETH-CFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
ETH-CFM Building Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Linktrace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Continuity Check (CC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Alarm Indication Signal (ETH-AIS Y.1731). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Test (ETH-TST Y.1731) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Y.1731 Time Stamp Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119
Synthetic Loss Measurement (ETH-SL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
OAM Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
CFM Connectivity Fault Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
CFM Fault Propagation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129
Epipe Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
Fault Propagation to access dot1q/QinQ ports in Access-uplink mode. . . . . . . . . . . . . . . . . . . . . . . .133
Configuring Fault propagation: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
Service Assurance Agent Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
Traceroute Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136
Writing SAA Results to Accounting Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137
Configuring SAA Test Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137
Y.1564 Testhead OAM tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
Pre-requisites for using the Testhead Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Port Loopback for Ethernet ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
Configuring testhead tool parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
Diagnostics Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153
Tools Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293
Common CLI Command Descriptions

Common Service Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334
Standards and Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335
Page 4 7210 SAS-M, T, X, R6 OS OAM and Diagnostic

List of Tables
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Getting Started
Table 1: Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Mirror Services
Table 2: Combinations of SAPs, spoke-sdp, and remote sources allowed in a mirror service . . . . . . . . .17
Table 3: Mirror Source Port Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
OAM and SAA

Table 4: ETH-CFM Support Matrix for 7210 SAS-M Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Table 5: ETH-CFM Support Matrix for 7210 SAS-M Access-Uplink Mode . . . . . . . . . . . . . . . . . . . . . . .107
Table 6: ETH-CFM Support Matrix for 7210 SAS-T Access-Uplink Mode . . . . . . . . . . . . . . . . . . . . . . .108
Table 7: ETH-CFM Support Matrix for 7210 SAS-T Network Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Table 8: ETH-CFM Support Matrix for 7210 SAS-X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Table 9: ETH-CFM Support Matrix for 7210 SAS-R6 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
Table 10: SAP Encapsulations supported for testhead. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .148
Table 11: Request Packet and Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
Table 12: Request Packet and Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
Table 13: Output fieldstools dump system-resource sap-ingress-qos . . . . . . . . . . . . . . . . . . . . . . . . . . .302

List of Figures
Mirror Services
Figure 1: Service Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Figure 2: Local Mirroring Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Figure 3: Remote Mirroring Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Figure 4: Mirror Configuration and Implementation Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Figure 5: Local Mirrored Service Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Figure 6: Remote Mirrored Service Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
OAM and SAA

Figure 7: OAM Control Word Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Figure 8: VCCV TLV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Figure 9: VCCV-Ping Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
Figure 10: MEP and MIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Figure 11: MEP, MIP and MD Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Figure 12: CFM Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Figure 13: CFM Linktrace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Figure 14: CFM Continuity Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Figure 15: CFM CC Failure Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Figure 16: SLM Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Figure 17: Local Fault Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
Figure 18: 7210 acting as traffic generator and traffic analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
Page 6 7210 SAS-M, T, X, R6 OS OAM and Diagnostic

Guide
Preface
About This Guide

This guide describes service mirroring and Operations, Administration and
Management (OAM) and diagnostic tools provided by the 7210 SAS-M, T, X and R6.
On 7210 SAS devices, not all the CLI commands are supported on all the platforms
and in all the modes. In many cases, the CLI commands are mentioned explicitly in
this document. In other cases, it is implied and easy to know the CLIs that are not
supported on a particular platform.
All the variants of 7210 SAS-M and 7210 SAS-T can be configured in two modes,
that is in network mode and in access-uplink mode. In network mode configuration
7210 SAS-M and 7210 SAS-T uses IP/MPLS to provide service transport. In access-
uplink mode configuration 7210 SAS-M and 7210 SAS-T uses Ethernet QinQ
technology to provide service transport. The mode can be selected by configuring the
BOF appropriately.
This guide also presents examples to configure and implement various tests.
Notes:
• This user guide is applicable to all 7210 SAS-M, 7210 SAS-T, 7210 SAS-R6
and 7210 SAS-X platforms, unless specified otherwise.
• In either mode, it is expected that the user will only configure the required
CLI parameters appropriate for the mode he intends to use. Unless otherwise
noted, most of the configuration is similar in both the network mode and
Access uplink mode.
• Only 7210 SAS-M and 7210 SAS-T supports access-uplink mode. 7210 SAS-
X and 7210 SAS-R6 does not support access-uplink mode. 7210 SAS-X and
7210 SAS-R6 supports only MPLS uplinks and implicitly operates in network
mode.
• On 7210 SAS devices, not all the CLI commands are supported on all the
platforms and in all the modes. In many cases, the CLI commands are
mentioned explicitly in this document. In other cases, it is implied and easy to
know the CLIs that are not supported on a particular platform.
7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide Page 7

Preface
This document is organized into functional chapters and provides concepts and descriptions of the
implementation flow, as well as Command Line Interface (CLI) syntax and command usage.
Audience
This manual is intended for network administrators who are responsible for configuring the 7210
SAS routers. It is assumed that the network administrators have an understanding of networking
principles and configurations. Protocols, standards, and services described in this manual include
the following:
• CLI concepts
• Subscriber services
• Service mirroring
• Operation, Administration and Maintenance (OAM) operations
Page 8 7210 SAS-M, T, X, and R6 OS OAM and Diag-

nostic Guide
Preface
List of Technical Publications

The 7210-SAS-M, T, X, R6 OS documentation set is composed of the following books:
• 7210-SAS-M, T, X, R6 OS Basic System Configuration Guide

This guide describes basic system configurations and operations.
• 7210-SAS-M, T, X, R6 OS System Management Guide
This guide describes system security and access configurations as well as event
logging and accounting logs.
• 7210-SAS-M, T, X, R6 OS Interface Configuration Guide
This guide describes card, Media Dependent Adapter (MDA), and port provisioning.
• 7210-SAS-M, T, X, R6 OS Router Configuration Guide
This guide describes logical IP routing interfaces and associated attributes such as an
IP address, port, link aggregation group (LAG) as well as IP and MAC-based filtering.
• 7210-SAS-M, T, X, R6 OS OS Routing Protocols Guide
This guide provides an overview of routing concepts and provides configuration
examples for protocols and route policies.
• 7210 SAS-M, T, X, R6 OS MPLS Guide
This guide describes how to configure Multiprotocol Label Switching (MPLS),
Resource Reservation Protocol (RSVP), and Label Distribution Protocol (LDP).
• 7210 SAS-M, T OS and 7210-SAS-X, R6 OS Services Guide
This guide describes how to configure service parameters such as, customer
information and user services.
• 7210-SAS-M, T, X, R6 OS OAM and Diagnostic Guide
This guide describes how to configure features such as service mirroring and
Operations, Administration and Management (OAM) tools.
• 7210 SAS-M, T OS and 7210-SAS-X, R6 OS Quality of Service Guide
This guide describes how to configure Quality of Service (QoS) policy management.

Preface
Technical Support
If you purchased a service agreement for your 7210 SAS and related products from a distributor or
authorized reseller, contact the technical support staff for that distributor or reseller for assistance.
If you purchased an Alcatel-Lucent service agreement, contact your welcome center.
Web: http://www1.alcatel-lucent.com/comps/pages/carrier_support.jhtml

nostic Guide
Getting Started
In This Chapter
This book provides process flow information to configure service mirroring and
Operations, Administration and Management (OAM) tools.
Alcatel-Lucent 7210 SAS-Series Services Configuration Process

Table 1 lists the tasks necessary to configure mirroring, and perform tools monitoring
functions.
This guide is presented in an overall logical configuration flow. Each section
describes a software area and provides CLI syntax and command usage to configure
parameters for a functional area.
Table 1: Configuration Process

Area Task Chapter
Diagnostics/ Mirroring Mirror Services on page 13

Service verification
OAM OAM and SAA on page 69
Reference List of IEEE, IETF, and other Standards and Protocols section.
proprietary entities.

Getting Started

nostic Guide
Mirror Services
In This Chapter
This chapter provides information to configure mirroring.
Topics in this chapter include:
• Service Mirroring on page 14

• Mirror Implementation on page 15
→ Mirror Source and Destinations on page 16
− Local and Remote Mirroring on page 18
→ Mirroring Performance on page 19
→ Mirroring Configuration on page 20
• Configuration Process Overview on page 22
• Configuration Notes on page 23
• Configuring Service Mirroring with CLI on page 25
• Basic Mirroring Configuration on page 27
• Common Configuration Tasks on page 30
• Service Management Tasks on page 37
• Mirror Service Command Reference on page 43
• Configuration Commands on page 47

Service Mirroring
Service Mirroring
When troubleshooting complex operational problems, customer packets can be examined as they
traverse the network. Alcatel-Lucent’s service mirroring provides the capability to mirror
customer packets to allow for trouble shooting and offline analysis.
This capability also extends beyond troubleshooting services. Telephone companies have the
ability to obtain itemized calling records and wire-taps where legally required by investigating
authorities. The process can be very complex and costly to carry out on data networks. Service
Mirroring greatly simplifies these tasks, as well as reduces costs through centralization of analysis
tools and skilled technicians.
Original packets are forwarded while a copy is sent out the mirrored port to the mirroring
(destination) port. Service mirroring allows an operator to see the actual traffic on a customer’s
service with a sniffer sitting in a central location. In many cases, this reduces the need for a
separate, costly overlay sniffer network.
7210 SAS devices configured in access-uplink mode support only local mirroring.
When using local mirroring user has an option to use NULL SAP or a dot1q SAP or a Q1.* SAP as
mirror destination. Use of Dot1q SAP or a Q1.* SAP as the mirror destination allows the mirrored
traffic to share the same uplink as the service traffic (when the uplinks are L2 based).
On some 7210 SAS platforms, when using Dot1q SAP or a Q1.* SAP or MPLS SDP as the mirror
destination user needs to dedicate the resources of a port for use with mirror application (see below
for more details).
MPLS
DLC VC Control Customer Packet
Tunnel
Header Label Word
Label
Customer Traffic Customer Traffic
IP/MPLS Core Sniffer

Mirrored
Traffic VL
100 Byte Slice
AN
of Customer Packet
ID
OSSG025
Figure 1: Service Mirroring
Page 14 7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide

Mirror Services
Mirror Implementation
Mirroring can be implemented on ingress service access points (SAPs). For 7210 SAS devices,
egress mirroring is supported only on the port. Egress mirroring is not supported for SAPs and
filters.
Alcatel-Lucent’s implementation of packet mirroring is based on the following assumptions:
• Ingress and egress packets are mirrored as they appear on the wire. This is important for
troubleshooting encapsulation and protocol issues.
When mirroring at ingress, an exact copy of the original ingress packet is sent to the
mirror destination while normal forwarding proceeds on the original packet.
• When mirroring is at egress, the system performs normal packet handling on the egress
packet, encapsulating it for the destination interface. A copy of the forwarded packet (as
seen on the wire) is forwarded to the mirror destination.
In 7210 SAS, mirroring at egress takes place before the packet is processed by egress QoS.
Hence, there exists a possibility that a packet is dropped by egress QoS mechanisms
(because of RED mechanisms and so on) and thus not forwarded, but it is still mirrored.
→ Remote destinations are reached by encapsulating the ingress or egress packet within
an SDP, like the traffic for distributed VPN connectivity services. At the remote
destination, the tunnel encapsulation is removed and the packet is forwarded out a
local SAP.

Mirror Source and Destinations

Mirror sources and destinations have the following characteristics for 7210 SAS devices operating
in network mode.
• Mirror source and mirror destination can be on the same node (local mirroring) or on
different nodes (remote mirroring).
• Each mirror destination should terminate on a distinct port carrying only null
encapsulation or a Dot1q SAP or a Q1.* SAP or a MPLS SDP in case of remote mirroring.
• Packets ingressing a port can have a mirror destination separate from packets egressing
another or the same port (the ports must be on the same node).
• Multiple mirror destinations are supported (local only) on a single chassis.
Listed below are the mirror sources and destination characteristics for 7210 SAS devices
configured in access-uplink mode:
• Mirroring source and destination can only be on the same 7210 SAS-M node (local
mirroring).
• A mirror destination can terminate on only one port (NULL SAP or dot1q SAP or a Q1.*
SAP).
• Packets ingressing a port can have a mirror destination separate from packets egressing
another or the same port.
The following table lists the allowed combinations of SAPs, spoke-sdp and remote sources
allowed in a mirror service using different mirror-source-type on 7210 SAS devices configured in
network mode:

Mirror Services
Table 2: Combinations of SAPs, spoke-sdp, and remote sources allowed in a mirror service
Mirror-source-type Mirror sources Allowed Mirror Destination Allowed
Local Port Ingress NULL SAP

Port Egress Dot1q SAP
SAP ingress QinQ SAP
ACL ingress Spoke-SDP
Remote remote-source NULL SAP
Dot1q SAP
QinQ SAP
Both Port Ingress NULL SAP
Port Egress Dot1q SAP
SAP ingress QinQ SAP
ACL ingress
remote-source

Local and Remote Mirroring
NOTE: This sections describes the local and remote mirroring that are applicable for the platforms
on which the mirroring feature is supported. The 7210 SAS devices configured in access-uplink
mode supports only local mirroring and the 7210 SAS devices configured in network mode
supports both local and remote mirroring.
The 7210 SAS devices allows multiple concurrent mirroring sessions so traffic from more than
one ingress mirror source can be mirrored to the same or different mirror destinations. In case of
port egress mirroring, only a maximum of 4 egress mirror sources are allowed and one egress
mirror source can be configured to only one mirror destination.
Remote mirroring uses a service distribution path (SDP) which acts as a logical way of directing
traffic from one router to another through a uni-directional (one-way) service tunnel. The SDP
terminates at the far-end router which directs packets to the correct destination on that device.
The SDP configuration from the mirrored device to a far-end router requires a return path SDP
from the far-end router back to the mirrored router. Each device must have an SDP defined for
every remote router to which it provides mirroring services. SDPs must be created first, before
services can be configured.

Mirror Services
Mirroring Performance
Replication of mirrored packets can, typically, affect performance and should be used carefully.
On 7210 SAS devices, mirroring can be performed based on the following criteria:
• Port (ingress and egress)

• SAP (ingress only)
• MAC filter (ingress only)
• IP filter (ingress only)

Mirroring Configuration
Configuring mirroring is similar to creating a uni-direction service. Mirroring requires the
configuration of:
• Mirror source — The traffic on a specific point(s) to mirror.

• Mirror destination — The location to send the mirrored traffic, where the sniffer will be
located.
Figure 2 depicts a local mirror service configured on ALA-A.
• Port 1/1/2 is specified as the source. Mirrored traffic ingressing and egressing this port
will be sent to port 1/1/3.
• SAP 1/1/3 is specified as the destination. The sniffer is physically connected to this port.
Mirrored traffic ingressing and egressing port 1/1/2 is sent here. SAP, encapsulation
requirements, and mirror classification parameters are configured.
ALA-A
1/1/1 1/1/2 1/1/3
Sniffer
Configure a mirror service specifying

source and destination parameters
OSSG026-7210
Figure 2: Local Mirroring Example
Figure 3 depicts a remote mirror service configured as ALA B as the mirror source and ALA A as
the mirror destination. Mirrored traffic ingressing and egressing port 5/2/1 (the source) on ALA B
is handled the following ways:
• Port 5/2/1 is specified as the mirror source port. Parameters are defined to select specific
traffic ingressing and egressing this port.
Destination parameters are defined to specify where the mirrored traffic is sent. In this
case, mirrored traffic sent to a SAP configured as part of the mirror service on port 3/1/3
on ALA A (the mirror destination).
ALA A decodes the service ID and sends the traffic out of port 3/1/3.
The sniffer is physically connected to this port (3/1/3). SAP, encapsulation requirements,

Mirror Services
packet slicing, and mirror classification parameters are configured in the destination
parameters.
Mirror Destination Mirror Source

ALA-A ALA-B
SDP 1000
Port 3/1/3
Port 5/2/1
Sniffer
Configure a mirror service specifying

source and destination parameters
OSSG027
Figure 3: Remote Mirroring Example

Configuration Process Overview
Configuration Process Overview

Figure 4 displays the process to provision basic mirroring parameters.
START
CONFIGURE MIRROR DESTINATION MIRROR DESTINATION
CONFIGURE SAP
CONFIGURE MIRROR SOURCE MIRROR SOURCE
ENABLE
Figure 4: Mirror Configuration and Implementation Flow

Mirror Services
Configuration Notes
This section describes mirroring configuration caveats.
• Multiple mirroring service IDs (mirror destinations) may be created within a single
system.
• A mirrored source can only have one destination.
• On 7210 SAS-R6, 7210 SAS-M, 7210 SAS-T and 7210 SAS-X, before using a Dot1q
SAP or Q1.* SAP as a mirror destination, the user must configure a port for use with this
feature using the command config> system> loopback-no-svc-port mirror. No services
can be configured on this port. More details of this command can be found in the 7210
SAS Interfaces Guide.
• On 7210 SAS-R6, 7210 SAS-M, 7210 SAS-X, and 7210 SAS-T before using a MPLS
SDP as a mirror destination, the user must configure a port for use with this feature using
the command config> system> loopback-no-svc-port mirror. No services can be
configured on this port. More details of this command can be found in the 7210 SAS
Interfaces Guide.
• Spoke sdp is supported only on local mirror service type. Please refer to the Combinations
of SAPs, spoke-sdp, and remote sources allowed in a mirror service on page 17 above for
more information.
• Remote source mirror type service accepts only MPLS labeled traffic from remote
sources.
• The destination mirroring service IDs and service parameters are persistent between
router (re)boots and are included in the configuration saves.
Mirror source criteria configuration (defined in debug>mirror>mirror-source) is not
preserved in a configuration save (admin save). Debug mirror source configuration can
be saved using admin>debug-save.
• Physical layer problems such as collisions, jabbers, etc., are not mirrored. Typically, only
complete packets are mirrored.
• Starting and shutting down mirroring:

Configuration Notes
Mirror destinations:
→ The default state for a mirror destination service ID is shutdown. You must issue a no
shutdown command to enable the feature.
→ When a mirror destination service ID is shutdown, mirrored packets associated with
the service ID are not accepted from its mirror source. The associated mirror source is
put into an operationally down mode. Mirrored packets are not transmitted out the
SAP. Each mirrored packet is silently discarded.
→ Issuing the shutdown command causes the mirror destination service or its mirror
source to be put into an administratively down state. Mirror destination service IDs
must be shut down first in order to delete a service ID, or SAP association from the
system.
Mirror sources:
→ The default state for a mirror source for a given mirror-dest service ID is no
shutdown. Enter a shutdown command to deactivate (disable) mirroring from that
mirror-source.
→ Mirror sources do not need to be shutdown to remove them from the system. When a
mirror source is shutdown, mirroring is terminated for all sources defined locally for
the mirror destination service ID.

Mirror Services
Configuring Service Mirroring with CLI

This section provides information about service mirroring
Topics in this section include:
• Mirror Configuration Overview on page 26

• Basic Mirroring Configuration on page 27
→ Mirror Classification Rules on page 28
• Common Configuration Tasks on page 30
→ Configuring a Local Mirror Service on page 31
→ Configuring a Remote Mirror Service on page 33
• Service Management Tasks on page 37
→ Modifying a Local Mirrored Service on page 38
→ Deleting a Local Mirrored Service on page 39
→ Modifying a Remote Mirrored Service on page 40
→ Deleting a Remote Mirrored Service on page 42

Configuring Service Mirroring with CLI
Mirror Configuration Overview

7210 SAS M mirroring can be organized in the following logical entities:
• The mirror source is defined as the location where ingress traffic specific to a port, SAP,
MAC or IP filter, is to be mirrored (copied). The original frames are not altered or affected
in any way. The egress traffic specific to a port can be mirrored.
• A SAP is defined in local mirror services as the mirror destination to where the mirrored
packets are sent.
Defining Mirrored Traffic

In some scenarios, or when multiple services are configured on the same port, specifying the port
does not provide sufficient resolution to separate traffic. In Alcatel-Lucent’s implementation of
mirroring, multiple source mirroring parameters can be specified to further identify traffic.
Mirroring of packets matching specific filter entries in an IP or MAC filter can be applied to refine
what traffic is mirrored to flows of traffic within a service. The IP criteria can be combinations of:
• Source IP address/mask
• Destination IP address/mask
• IP Protocol value
• Source port value (for example, UDP or TCP port)
• Destination port value (for example, UDP or TCP port)
• DiffServ Code Point (DSCP) value
• ICMP code
• ICMP type
• IP fragments
• TCP ACK set/reset
• TCP SYN set/reset
The MAC criteria can be combinations of:
• IEEE 802.1p value/mask

• Source MAC address/mask
• Destination MAC address/mask
• Ethernet Type II Ethernet type value

Mirror Services
Basic Mirroring Configuration

Destination mirroring parameters must include at least:
• A mirror destination ID (same as the mirror source service ID).

• A mirror destination SAP.
Mirror source parameters must include at least:
• A mirror service ID (same as the mirror destination service ID).

• At least one source type (port, SAP, IP filter or MAC filter) specified.
The following example displays a sample configuration of a local mirrored service (ALA-A).
*A:ALA-A>config>mirror# info
----------------------------------------------
mirror-dest 103 create
sap 1/1/1 create
exit
no shutdown
exit
----------------------------------------------
*A:ALA-A>config>mirror#
The following displays the mirror source configuration:
*A:ALA-A>debug>mirror-source# show debug mirror

debug
mirror-source 103
port 1/1/24 egress ingress
no shutdown
exit
exit
*A:ALA-A>debug>mirror-source# exit

Basic Mirroring Configuration
Mirror Classification Rules

Alcatel-Lucent’s implementation of mirroring can be performed by configuring parameters to
select network traffic according to any of the following entities:
• Port
• SAP
• MAC filter
• IP filter
Port The port command associates a port to a mirror source. The port is identified by the port ID. The
defined port can be Ethernet or a Link Aggregation Group (LAG) ID. When a LAG ID is given as
the port ID, mirroring is enabled on all ports making up the LAG.
Mirror sources can be ports in either access or network mode. Port mirroring is supported in the
following combinations:
Table 3: Mirror Source Port Requirements
Port Type Port Mode Port Encap Type
faste/gige/10gige access null, dot1q and QinQ

faste/gige/10gige access uplink qinq
faste/gige/10gige network null/dot1q
faste/gige/10gige hybrid null/dot1q/qinq
CLI Syntax: debug>mirror-source# port {port-id|lag lag-id} {[egress][in-

gress]}
Example: *A:ALA-A>debug>mirror-source# port 1/1/2 ingress egress
SAP More than one SAP can be associated within a single mirror-source. Each SAP has its own ingress
parameter keyword to define which packets are mirrored to the mirror-dest service ID. A SAP that
is defined within a mirror destination cannot be used in a mirror source.
CLI Syntax: debug>mirror-source# sap sap-id {[ingress]}
Example: *A:ALA-A>debug>mirror-source# sap 1/1/4:100 ingress

Mirror Services
MAC filter MAC filters are configured in the config>filter>mac-filter context. The mac-filter command
causes all the packets matching the explicitly defined list of entry IDs to be mirrored to the mirror
destination specified by the service-id of the mirror source.
CLI Syntax: debug>mirror-source# mac-filter mac-filter-id entry entry-id

[entry-id …]
Example: *A:ALA-2>debug>mirror-source# mac-filter 12 entry 15 20 25
IP filter IP filters are configured in the config>filter>ip-filter context. The ip-filter command causes all
the packets matching the explicitly defined list of entry IDs to be mirrored to the mirror destination
specified by the service-id of the mirror source.
Ingress mirrored packets are mirrored to the mirror destination prior to any ingress packet
modifications.
CLI Syntax: debug>mirror-source# ip-filter ip-filter-id entry entry-id

[entry-id …]
Example: *A:ALA-A>debug>mirror-source# ip-filter 1 entry 20
NOTES:
− An IP filter cannot be applied to a mirror destination SAP.

− Ingress mirroring for IPv6 ACL entries are supported.

Common Configuration Tasks

This section provides a brief overview of the tasks that must be performed to configure local
mirror services and provides CLI command syntax. Note that the local mirror source and mirror
destination components must be configured under the same service ID context.
Each local mirrored service (Figure 5) (within the same router) requires the following
configurations:
1. Specify mirror destination (SAP).

2. Specify mirror source (port, SAP, IP filter, MAC filter).
Mirror Source
1/1/2
ALA-A
Mirror Destination
1/1/3
1/1/1 1/1/2 1/1/3
Sniffer
OSSG028A
Figure 5: Local Mirrored Service Tasks

Mirror Services
Configuring a Local Mirror Service

To configure a local mirror service, the source and destinations must be located on the same router.
Note that local mirror source and mirror destination components must be configured under the
same service ID context.
The mirror-source commands are used as traffic selection criteria to identify traffic to be
mirrored at the source. Each of these criteria are independent. For example, use the
debug>mirror-source>port {port-id | lag lag-id} {[egress] [ingress]} command and
debug>mirror-source ip-filter ip-filter-id entry entry-id [entry-id…] command to capture
(mirror) traffic that matches a specific IP filter entry and traffic ingressing and egressing a specific
port. A filter must be applied to the SAP or interface if only specific packets are to be mirrored.
Use the CLI syntax to configure one or more mirror source parameters:
The mirror-dest commands are used to specify where the mirrored traffic is to be sent. Use the
following CLI syntax to configure mirror destination parameters:
CLI Syntax: config>mirror mirror-dest service-id [type {ether}] [create]

description string
sap sap-id [create]
no shutdown
CLI Syntax: debug# mirror-source service-id

ip-filter ip-filter-id entry entry-id [entry-id …]
mac-filter mac-filter-id entry entry-id [entry-id …]
port {port-id|lag lag-id} {[egress][ingress]}
sap sap-id {[ingress]}
no shutdown
The following output displays an example of a local mirrored service using a NULL SAP. On
ALA-A, mirror service 103 is mirroring traffic matching IP filter 2, entry 1 as well as egress and
ingress traffic on port 1/1/23 and sending the mirrored packets to SAP 1/1/24
----------------------------------------------
sap 1/1/24 create
exit
no shutdown
exit
----------------------------------------------
The following output displays an example of local mirrored service using a dot1q SAP. User needs
to configure a front-panel port for use with the mirroring application when the mirror destination is
a Dot1q SAP or a Q1.* SAP, as shown below.

*A:ALA-A>config>system>
------------------------------------------------------
loopback-no-svc-port mirror 1/1/14
-------------------------------------------------------
----------------------------------------------
sap 1/1/10:100 create
exit
no shutdown
exit
----------------------------------------------
The following displays the debug mirroring information:

debug
mirror-source 103
no shutdown
port 1/1/23 ingress
ip-filter 2 entry 1
exit
exit
*A:ALA-A>debug>mirror-source# exit

Mirror Services
Configuring a Remote Mirror Service

The source and destination are configured on different routers for remote mirroring. Note that
mirror source and mirror destination parameters must be configured under the same service ID
context.
NOTE: Remote Mirroring using MPLS SDP is supported only on 7210 SAS devices configured in
Network Mode. It is not supported on 7210 SAS devices configured in access-uplink mode.
The mirror-source commands are used as traffic selection criteria to identify traffic to be
mirrored at the source. For example, use the port port-id [lag-id] {[egress] [ingress]} and mac-
filter mac-filter-id entry entry-id [entry-id …] commands.
Use the CLI syntax to configure one or more mirror source parameters:
CLI Syntax: debug> mirror-source service-id

ip-filter ip-filter-id entry entry-id [entry-id …]
mac-filter mac-filter-id entry entry-id [entry-id …]
port {port-id|lag lag-id} {[egress][ingress]}
sap sap-id {[ingress]}
no shutdown
The mirror-dest commands are used to specify where the mirrored traffic is to be sent, the
forwarding class, and the size of the packet. Use the following CLI syntax to configure mirror
destination parameters:
CLI Syntax: config>mirror#
mirror-dest service-id
[create] [type <mirror-type>] [mirror-source-type <mirror-

source-type>]
description string
fc fc-name [profile <profile>]
remote-source
far-end <ip-address> [vc-id <vc-id>] [ing-svc-label <i
ngress-vc-label>|tldp]
sap sap-id create
no shutdown
The following Table 6, Remote Mirrored Service Tasks, on page 34 displays the mirror
destination, which is on ALA-A, configuration for mirror service 1216. This configuration
specifies that the mirrored traffic coming from the mirror source (10.10.0.91) is to be directed to
SAP /1/58 and states that the service only accepts traffic from far end 10.10.0.92 (ALA-B) with an
ingress service label of 5678. When a forwarding class is specified, then all mirrored packets

transmitted to the destination SAP or SDP override the default (be) forwarding class. The slice size
limits the size of the stream of packet through 7210 SAS and the core network.
Figure 6: Remote Mirrored Service Tasks
Mirror Remote Destination Mirror

Destination Source SDP 4 Source
SAP 1/1/58:0 Port 1/1/60 ingress/egress
System IP System IP
10.10.0.92/32 SDP 4 10.10.0.91/32
Sniffer
ALA-A ALA-B
OSSG030A
The following example displays the CLI output showing the configuration of remote mirrored
service 1216. The traffic ingressing and egressing port 1/1/60 on 10.10.0.92 (ALA-B) will be
mirrored to the destination SAP 1/1/58:0 on ALA-A.
The following example displayed is the remote mirror destination configuring the front panel port
with mirroring application:
*A:7210SAS>config>mirror# info
----------------------------------------------
mirror-dest 23 mirror-source-type remote create
description "Added by createMirrorDestination 23"
fc be
remote-source
far-end 2.2.2.2 ing-svc-label 14000
exit
sap 1/1/4 create
exit
no shutdown
exit
fc be
spoke-sdp 200:1000 create
egress
vc-label 15000
exit
no shutdown
exit
no shutdown
exit
----------------------------------------------
*A:7210SAS>config>mirror# /show system internal-loopback-ports
===============================================================================
Internal Loopback Port Status

Mirror Services
===============================================================================
Port Loopback Application Service
Id Type Enabled
-------------------------------------------------------------------------------
1/1/9 Physical Dot1q-Mirror No
===============================================================================
The following example displayed is the mirror destination configuration for mirror service 1216
on ALA-A.
----------------------------------------------
mirror-dest 1000 type ether mirror-source-type remote create
description "Receiving mirror traffic from .91"
remote-source
far-end 2.2.2.2 tldp
exit
egress
qos 1
exit
exit
no shutdown
exit
----------------------------------------------
The following example displays the remote mirror destination configured on ALA-B:
*A:ALA-B>config>mirror# info
----------------------------------------------
mirror-dest 2000 type ether mirror-source-type local create
no description
no service-name
fc be
no remote-source
egress
no vc-label
exit
no shutdown
exit
no shutdown
exit
----------------------------------------------
*A:ALA-B>config>mirror#
The following example displays the mirror source configuration for ALA-B:
*A:ALA-B# show debug mirror

debug
mirror-source 1000
no shutdown

exit
mirror-source 2000
no shutdown
exit
exit
*A:ALA-B#
The following example displays the SDP configuration from ALA-A to ALA-B (SDP 2) and the
SDP configuration from ALA-B to ALA-A (SDP 4).
*A:ALA-A>config>service>sdp# info
---------------------------------------------
description "MPLS-10.10.0.91"
far-end 10.10.0.01
signalling tldp
no shutdown
---------------------------------------------
*A:ALA-A>config>service>sdp#
*A:ALA-B>config>service>sdp# info
----------------------------------------------
description "MPLS-10.10.20.92"
far-end 10.10.10.103
signalling tldp
no shutdown
----------------------------------------------
*A:ALA-B>config>service>sdp#

Mirror Services
Service Management Tasks

This section discusses the following service management tasks:
• Modifying a Local Mirrored Service on page 38

• Deleting a Local Mirrored Service on page 39
• Modifying a Remote Mirrored Service on page 40
• Deleting a Remote Mirrored Service on page 42
Use the following command syntax to modify an existing mirrored service:
CLI Syntax: config>mirror#

mirror-dest service-id [type {ether}]
description description-string
no description
sap sap-id
no sap
[no] shutdown
CLI Syntax: debug

[no] mirror-source service-id
ip-filter ip-filter-id entry entry-id [entry-id...]
no ip-filter ip-filter-id
no ip-filter entry entry-id [entry-id...]
mac-filter mac-filter-id entry entry-id [entry-id...]
no mac-filter mac-filter-id
no mac-filter mac-filter-id entry entry-id [entry-id...]
[no] port {port-id|lag lag-id} {[egress][ingress]}
[no] sap sap-id {[ingress]}
[no] shutdown

Modifying a Local Mirrored Service

Existing mirroring parameters can be modified in the CLI. The changes are applied immediately.
The service must be shut down if changes to the SAP are made.
The following example displays commands to modify parameters for a basic local mirroring
service.
Example: config>mirror# mirror-dest 103

config>mirror>mirror-dest# shutdown
config>mirror>mirror-dest# no sap
config>mirror>mirror-dest# sap 1/1/5 create
config>mirror>mirror-dest>sap$ exit
config>mirror>mirror-dest# no shutdown
debug# mirror-source 103
debug>mirror-source# no port 1/1/23
debug>mirror-source# port 1/1/7 ingress egress
The following displays the local mirrored service modifications:
----------------------------------------------
no shutdown
sap 1/1/5 create
exit

debug
mirror-source 103
no shutdown
port 1/1/7 egress ingress
exit
*A:ALA-A>debug>mirror-source#

Mirror Services
Deleting a Local Mirrored Service

Existing mirroring parameters can be deleted in the CLI. A shutdown must be issued on a service
level in order to delete the service. It is not necessary to shut down or remove SAP or port
references to delete a local mirrored service.
The following example displays commands to delete a local mirrored service.
Example:ALA-A>config>mirror# mirror-dest 103

config>mirror>mirror-dest# exit
config>mirror# no mirror-dest 103
config>mirror# exit

Modifying a Remote Mirrored Service

Existing mirroring parameters can be modified in the CLI. The changes are applied immediately.
The service must be shut down if changes to the SAP are made.
In the following example, the mirror destination is changed from 10.10.10.2 (ALA-B) to
10.10.10.3 (SR3). Note that the mirror-dest service ID on ALA-B must be shut down first before it
can be deleted.
The following example displays commands to modify parameters for a remote mirrored service.
Example:*A:ALA-A>config>mirror# mirror-dest 104

config>mirror>mirror-dest# remote-source
config>mirror>mirror-dest>remote-source# no far-end 10.10.10.2
remote-source# far-end 10.10.10.3 ing-svc-label 3500
*A:ALA-B>config>mirror# mirror-dest 104

SR3>config>mirror# mirror-dest 104 create

config>mirror>mirror-dest# sdp 4 egr-svc-label 3500
config>mirror>mirror-dest# no shutdown
config>mirror>mirror-dest# exit all
SR3># debug
debug# mirror-source 104
debug>mirror-source# port 551/1/2 ingress egress
debug>mirror-source# no shutdown
----------------------------------------------
remote-source
far-end 2.2.2.2 tldp
exit
egress
qos 1
exit
exit
no shutdown
exit
A:SR3>config>mirror# info
----------------------------------------------
no shutdown

Mirror Services
exit
----------------------------------------------
A:SR3>config>mirror#
A:SR3# show debug mirror

debug
mirror-source 104
no shutdown

Deleting a Remote Mirrored Service

Existing mirroring parameters can be deleted in the CLI. A shut down must be issued on a service
level to delete the service. It is not necessary to shut down or remove SAP, or far-end references to
delete a remote mirrored service.
To delete a mirror service, the spoke-SDP service has to be deleted from the service. Mirror
destinations must be shut down first before they are deleted.
Example:*A:ALA-A>config>mirror# mirror-dest 105

config>mirror# exit
*A:ALA-B>config>mirror# mirror-dest 105

config>mirror# exit
The mirror-destination service ID 105 was removed from the configuration on ALA-A and ALA-
B, thus, does not appear in the info command output.
----------------------------------------------
----------------------------------------------
*A:ALA-A>config>mirror# exit
*A:ALA-B>config>mirror# info
----------------------------------------------
----------------------------------------------
*A:ALA-B>config>mirror# exit
Since the mirror destination was removed from the configuration on ALA-B, the port information
was automatically removed from the debug mirror-source configuration.
*A:ALA-B# show debug mirror

debug
exit
*A:ALA-B#

Mirror Services
Mirror Service Command Reference
• Mirror Configuration Commands for 7210 SAS-M and 7210 SAS-T in Network mode on page
43
• Mirror Configuration Commands for 7210 SAS devices configured in Access-uplink mode on
page 45
• Mirror Configuration Commands for 7210 SAS-X and 7210 SAS-R6 on page 45
• Show Commands on page 46
• Debug Commands on page 46
Mirror Configuration Commands for 7210 SAS-M and 7210 SAS-T in Network
mode
config
— mirror
— mirror-dest service-id [type mirror-type] [mirror-source-type mirror-source-type]
[create]
— no mirror-dest service-id
— description description-string
— no description
— [no] fc [fc-name] profile { profile }
— no remote-source
— remote-source
— far-end ip-address [vc-id vc-id] [ing-svc-label ingress-vc-label| tldp]
— no far-end ip-address
— sap sap-id [create]
— no sap
— service-name service-name
— [no]service-name
— [no] shutdown
— no spoke-sdp sdp-id:vc-id
— spoke-sdp sdp-id:vc-id [create]
— egress
— no vc-label [egress-vc-label]
— vc-label egress-vc-label
— no shutdown
— shutdown

Mirror Services
Mirror Configuration Commands for 7210 SAS devices configured in Access-

uplink mode
config
— mirror
— mirror-dest service-id [type mirror-type] [create]
— no description
— [no] fc [fc-name] profile { profile }
— no sap
— [no] shutdown
Mirror Configuration Commands for 7210 SAS-X and 7210 SAS-R6

config
— mirror
— mirror-dest service-id [type encap-type][mirror-source-type mirror-source-type] [create]
— no description
— [no] fc [fc-name]
— no remote-source
— remote-source
— far-end ip-address [vc-id vc-id] [ing-svc-label ingress-vc-label| tldp]
— no far-end ip-address
— no sap
— [no] egress
— [no] qos policy-id
— [no] shutdown
— no spoke-sdp sdp-id:vc-id
— spoke-sdp sdp-id:vc-id [create]
— egress
— no vc-label [egress-vc-label]
— vc-label egress-vc-label
— no shutdown
— shutdown

Show Commands
show
— debug [application]
— mirror mirror-dest [service-id]
— service
— service-using mirror
Debug Commands
debug
— [no] mirror-source service-id
— ip-filter ip-filter-id entry entry-id [entry-id …]
— no ip-filter ip-filter-id [entry entry-id]
— mac-filter mac-filter-id entry entry-id [entry-id …]
— no mac-filter mac-filter-id [entry entry-id...]
— port {port-id | lag lag-id} {[egress] [ingress]}
— no port {port-id | lag lag-id} [egress] [ingress]
— sap sap-id {[ingress]}
— no sap sap-id [ingress]
— [no] shutdown

Mirror Services
Configuration Commands
Generic Commands
description
Syntax description description-string
no description
Context config>mirror>mirror-dest
Description This command creates a text description stored in the configuration file for a configuration context to help
the administrator identify the content of the file.
The no form of the command removes the description string.
Default There is no default description associated with the configuration context.
Parameters description-string — The description character string. Allowed values are any string up to 80 characters
long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $,
spaces, etc.), the entire string must be enclosed within double quotes.
shutdown
Syntax [no] shutdown
config>mirror>mirror-dest>spoke-sdp>egress
debug>mirror-source
Description The shutdown command administratively disables an entity. When disabled, an entity does not change,
reset, or remove any configuration settings or statistics. Many entities must be explicitly enabled using the
no shutdown command.
The shutdown command administratively disables an entity. The operational state of the entity is disabled
as well as the operational state of any entities contained within. Many objects must be shut down before they
may be deleted.
Unlike other commands and parameters where the default state is not indicated in the configuration file,
shutdown and no shutdown are always indicated in system generated configuration files.
The no form of the command puts an entity into the administratively enabled state.
Default See Special Cases below.

Special Cases Mirror Destination — When a mirror destination service ID is shutdown, mirrored packets associated
with the service ID are not accepted from the mirror source device. The associated mirror source is put into

an operationally down mode. Mirrored packets are not transmitted out of the SAP. Each mirrored packet is
silently discarded. If the mirror destination is a SAP, the SAP’s discard counters are increased.
The shutdown command places the mirror destination service or mirror source into an administratively
down state. The mirror-dest service ID must be shut down in order to delete the service ID, SAP associa-
tion from the system.
The default state for a mirror destination service ID is shutdown. A no shutdown command is required to
enable the service.
Mirror Source — Mirror sources do not need to be shutdown in order to remove them from the system.
When a mirror source is shutdown, mirroring is terminated for all sources defined locally for the mirror-
dest service ID.
The default state for a mirror source for a given mirror-dest service ID is no shutdown. A shutdown com-
mand is required to disable mirroring from that mirror-source.

Mirror Services
Mirror Destination Configuration Commands
mirror-dest
Syntax mirror-dest service-id [type encap-type] [mirror-source-type mirror-source-type][create]
no mirror-dest
Context config>mirror
Description Note: The “mirror-source-type” parameter is not applicable for 7210 SAS-M in Access-
uplink mode.
This command creates a context to set up a service that is intended for packet mirroring. It is configured as a
service to allow mirrored packets to be directed locally (within the same device), over the core of the net-
work and have a far end device decode the mirror encapsulation.
The mirror-dest service is comprised of destination parameters that define where the mirrored packets are
to be sent. It also specifies whether the defined service-id will receive mirrored packets from far end devices
over the network core.
The mirror-dest service IDs are persistent between boots of the router and are included in the configuration
backups. The local sources of mirrored packets for the service ID are defined within the debug mirror mir-
ror-source command that references the same service-id.
The mirror-dest command is used to create or edit a service ID for mirroring purposes. If the service-id
does not exist within the context of all defined services, the mirror-dest service is created and the context of
the CLI is changed to that service ID. If the service-id exists within the context of defined mirror-dest ser-
vices, the CLI context is changed for editing parameters on that service ID. If the service-id exists within the
context of another service type, an error message is returned and CLI context is not changed from the cur-
rent context.
The no form of the command removes a mirror destination from the system. The mirror-source associa-
tions with the mirror-dest service-id do not need to be removed or shutdown first. The mirror-dest
service-id must be shutdown before the service ID can be removed. When the service ID is removed, all
mirror-source commands that have the service ID defined will also be removed from the system.
Default No packet mirroring services are defined.
Parameters service-id — The service id identifies the service in the service domain. This ID is unique to this service and
cannot be used by any other service, regardless of service type. The same service ID must be configured
on every device that this particular service is defined on.
service-id
If a particular service ID already exists for a service, then the same value cannot be used to create a mir-
ror destination service ID with the same value.
For example:
If an Epipe service-ID 11 exists, then a mirror destination service-ID 11 cannot be created. If a VPLS
service-ID 12 exists, then a mirror destination service-ID 12 cannot be created.
If an IES service-ID 13 exists, then a mirror destination service-ID 13 cannot be created.
Values service-id: 1 — 2147483647

type encap-type — The type describes the encapsulation supported by the mirror service.
Values ether
mirror-source-type — This allows scaling of mirror services that can be used only with remote mirror
sources, while limiting the mirror services that can be used by local mirror sources or by both local and
remote mirror sources. For more information, see Table 2, Combinations of SAPs, spoke-sdp, and
remote sources allowed in a mirror service, on page 17.
Values local | remote | both
local — indicates that the mirror service can only be used by local mirror sources.
remote — indicates that the mirror service can only be used by remote mirror sources.
both — indicates that the mirror service can be used by both local and remote mirror sources.
Default local
fc
Syntax fc fc-name profile { profile }
no fc
Description This command specifies a forwarding class for all mirrored copy of the packets transmitted to the destina-
tion SAP overriding the default (be) forwarding class. All packets are sent with the same class of service to
minimize out of sequence issues. The mirrored copy of the packet does not inherit the forwarding class of
the original packet.
When the destination is on a SAP, it pulls buffers from the queue associated with the fc-name and the shap-
ing and scheduling treatment given to the packet is as per the user configuration for that queue.
FC can be assigned only when the mirror source is local. When the mirror source is remote, the network
QoS ingress policies that are applied to all the traffic received on the network port and network IP interface
are also applied to mirror traffic.
On 7210 SAS-M and 7210 SAS-T, all SAPs configured on a port use the port-based egress queues. If the
mirror destination SAP (that is, dot1q SAP or a Q1.* SAP) is configured to share an uplink with service traf-
fic, mirrored copy of the traffic sent out of the Dot1q or Q1.* SAP will share the port-based egress queues
with the other service traffic. User is provided an option to assign the profile mirrored copy to the packet, so
that during congestion mirrored copy of thepackets marked as out-of-profile is dropped before in-profile ser-
vice traffic (and possibly in-profile mirrored traffic, if user has configured mirrored traffic to be in-profile).
The profile is used to determine the slope policy to use for the packet and determines the packet's drop pre-
cedence. Additionally, if marking is enabled, it determines the marking value to be used in the packet
header.
On 7210 SAS-X and 7210 SAS-R6, SAP based egress QoS policy can be used on the mirrored destination
SAP, allowing users to control the bandwidth allocated for mirrored traffic.

Mirror Services
The no form of the command returns the mirror-dest service ID forwarding class to the default forwarding
class.
Default The best effort (be) forwarding class is associated with the mirror-dest service ID and profile is out.
Parameters fc-name — The name of the forwarding class with which to associate mirrored service traffic. The
forwarding class name must already be defined within the system. If the fc-name does not exist, an error will
be returned and the fc command will have no effect. If the fc-name does exist, the forwarding class
associated with fc-name will override the default forwarding class.
Values be, l2, af, l1, h2, ef, h1, nc
profile — The profile to assign to mirrored copy of the service traffic. The profile is used to determine the
slope policy to use for the packet and determines the packet's drop precedence. Additionally, if marking is
enabled, it determines the marking value to be used in the packet header. A value of in marks the traffic as
in-profile traffic and results in use of high slope parameters. A value of out marks the traffic as out-of-profile
and results in use of low slope parameters.
Values in, out
Default out
far-end
Syntax far-end ip-address [ing-svc-label ing-vc-label | tldp]
no far-end ip-addr
Context config>mirror>mirror-dest>remote-source
Description This command defines the remote device and configures parameters for mirror destination services on other
devices allowed to mirror to the mirror destination service ID.
The far-end command is used within the context of the remote-source node. It allows the definition of
accepted remote sources for mirrored packets to this mirror-dest-service-id. If a far end router has not been
specified, packets sent to the router are discarded.
The far-end command is used to define a remote source that may send mirrored packets to this 7210 SAS
for handling by this mirror-dest service-id.
The ing-svc-label keyword must be given to manually define the expected ingress service label. This
ingress label must also be manually defined on the far end address through the mirror-dest SDP binding
keyword egr-svc-label.
The no form of the command deletes a far end address from the allowed remote senders to this mirror-dest
service. All far-end addresses are removed when no remote-source is executed. All signaled ingress ser-
vice labels are withdrawn from the far end address affected. All manually defined ing-svc-label are
removed.
Default No far end service ingress addresses are defined.
Parameters ip-address — The service IP address (system IP address) of the remote device sending mirrored traffic to
this mirror destination service. If 0.0.0.0 is specified, any remote is allowed to send to this service.
Values 1.0.0.1 — 223.255.255.254

The ingress service label must be manually defined using the ing-svc-label keyword. On the far end
7210 SAS, the associated SDP egr-svc-label must be manually set and equal to the label defined in ing-
svc-label.
ing-svc-label ing-vc-label — Specifies the ingress service label for mirrored service traffic on the far end
device for manually configured mirror service labels.
The defined ing-svc-label is entered into the ingress service label table which causes ingress packet
with that service label to be handled by this mirror-dest service.
The specified ing-svc-label must not have been used for any other service ID and must match the far
end expected specific egr-svc-label for this 7210 SAS. It must be within the range specified for manu-
ally configured service labels defined on this 7210 SAS. It may be reused for other far end addresses on
this mirror-dest-service-id.
Values 2048 — 18431
tldp — Specifies that the label is obtained through signaling via the LDP.
remote-source
Syntax [no] remote-source
Description This command configures remote devices to mirror traffic to this device for mirror service egress. Option-
ally, deletes all previously defined remote mirror ingress devices.
The remote-source context allows the creation of a ‘sniffer farm’ to consolidate expensive packet capture
and diagnostic tools to a central location. Remote areas of the access network can be monitored via normal
service provisioning techniques.
Specific far-end routers can be specified with the far-end command allowing them to use this router as the
destination for the same mirror-dest-service-id.
The remote-source node allows the source of mirrored packets to be on remote 7210 SAS devices. The
local 7210 SASwill configure its network ports to forward packets associated with the service-id to the des-
tination SAP. When remote-source far-end addresses are configured, an SDP is not allowed as a destina-
tion.
By default, the remote-source context contains no far-end addresses. When no far-end addresses have
been specified, network remote devices will not be allowed to mirror packets to the local 7210 SAS as a mir-
ror destination. Packets received from unspecified far-end addresses will be discarded at network ingress.
The no form of the command restores the service-id to the default condition to not allow a remote 7210 SAS
access to the mirror destination. The far-end addresses are removed without warning.
Default No remote source devices defined

Mirror Services
sap
Syntax sap sap-id [create]
no sap
Description This command creates a service access point (SAP) within a mirror destination service. The SAP is owned
by the mirror destination service ID.
The SAP is defined with port and encapsulation parameters to uniquely identify the (mirror) SAP on the
interface and within the box. The specified SAP must define an Ethernet port with a null SAP or a Dot1q
SAP or a Q1.* SAP. A Q1.Q2 SAP cannot be used when the port encapsulation is set to QinQ or on an
access-uplink port.
NOTE: Before using a Dot1q SAP or a Q1.* SAP, user will need to dedicate a port for use with mirroring
application using the command config> system> loopback-no-svc-port. This is required only for 7210 SAS-
M, 7210 SAS-T, 7210 SAS-X and 7210 SAS-R6. For more information about this command can be found in
the 7210 Interfaces Guide.
Only one SAP can be created within a mirror-dest service ID. If the defined SAP has not been created on
any service within the system, the SAP is created and the context of the CLI will change to the newly cre-
ated SAP. In addition, the port cannot be a member of a multi-link bundle, LAG, APS group or IMA bundle.
If the defined SAP exists in the context of another service ID, mirror-dest or any other type, an error is gen-
erated.
Mirror destination SAPs can be created on Ethernet interfaces that have been defined as an access port or
access-uplink port. If the interface is defined as network, the SAP creation returns an error.
When the no form of this command is used on a SAP created by a mirror destination service ID, the SAP
with the specified port and encapsulation parameters is deleted.
Default No default SAP for the mirror destination service defined.
Parameters sap-id — Specifies the physical port identifier portion of the SAP definition. See Common CLI Command
Descriptions on page 333 for command syntax.
service-name
Syntax service-name service-name
no service-name
Description This command configures an optional service name, up to 64 characters in length, which adds a name
identifier to a given service to then use that service name in configuration references as well as display and
use service names in show commands throughout the system. This helps the service provider/administrator
to identify and manage services within the 7210 SAS platforms.
All services are required to assign a service ID to initially create a service. However, either the service ID or
the service name can be used o identify and reference a given service once it is initially created.

Parameters service-name — Specifies a unique service name to identify the service. Service names may not begin with
an integer (0-9).
spoke-sdp
Syntax spoke-sdp sdp-id:vc-id [create] [no-endpoint]
spoke-sdp sdp-id:vc-id [create] endpoint name
no sdp sdp-id:vc-id
Description This command binds an existing (mirror) service distribution path (SDP) to the mirror destination service
ID.
The operational state of the SDP dictates the operational state of the SDP binding to the mirror destination.
If the SDP is shutdown or operationally down, then SDP binding is down. Once the binding is defined and
the service and SDP are operational, the far-end router defined in the config service sdp sdp-id far-end
parameter is considered part of the service ID.
Only one SDP can be associated with a mirror destination service ID. If a second sdp command is executed
after a successful SDP binding, an error occurs and the command has no effect on the existing configuration.
A no sdp command must be issued before a new SDP binding can be attempted.
An SDP is a logical mechanism that ties a far end router to a specific service without having to define the
far-end SAP. Each SDP represents a method to reach a router.
The other method is Multi-Protocol Label Switching (MPLS) encapsulation. router routers support both sig-
naled and non-signaled LSPs (Label Switched Path) though the network. Non-signaled paths are defined at
each hop through the network. Signaled paths are protocol communicated from end to end using RSVP.
Paths may be manually defined or a constraint based routing protocol (OSPF-TE or CSPF) can be used to
determine the best path with specific constraints.
SDPs are created and then bound to services. Many services can be bound to a single SDP. The operational
and administrative state of the SDP controls the state of the SDP binding to the service.
An egress service label (Martini VC-Label), used by the SDP to differentiate each service bound to the SDP
to the far-end router, must be obtained manually or though signaling with the far end. If manually config-
ured, it must match the ing-svc-label defined for the local router.
The no form of the command removes the SDP binding from the mirror destination service. Once removed,
no packets are forwarded to the far-end (destination) router from that mirror destination service ID.
Default No default SDP ID is bound to a mirror destination service ID. If no SDP is bound to the service, the mirror
destination will be local and cannot be to another router over the core network.
Parameters sdp-id[:vc-id] — A locally unique SDP identification (ID) number. The SDP ID must exist. If the SDP ID
does not exist, an error will occur and the command will not execute.
For mirror services, the vc-id defaults to the service-id. However, there are scenarios where the vc-id is
being used by another service. In this case, the SDP binding cannot be created. So, to avoid this, the
mirror service SDP bindings now accepts vc-ids.
Values 1 — 17407

Mirror Services
endpoint name — specifies the name of the endpoint associated with the SAP.
no endpoint — Removes the association of a SAP or a SDP with an explicit endpoint name.
egress
Syntax egress
Context config>mirror>mirror-dest>spoke-sdp
Description This command enters the context to configure spoke SDP egress parameters.
vc-label
Syntax vc-label egress-vc-label
no vc-label [egress-vc-label]
Context config>mirror>mirror-dest>spoke-sdp>egress
Description This command configures the spoke-SDP egress VC label.
Parameters egress-vc-label — A VC egress value that indicates a specific connection.

Values 16 — 1048575
egress
Syntax egress
Context config> mirror> sap
Description This command provides the context to configure egress policies for this SAP.
qos
Syntax [no] qos policy-id
Context config> mirror> sap> egress
Description NOTE: This command is supported only on 7210 SAS-X.

This command allows user to configure the QoS policy for the mirror destination SAP egress. The SAP
egress QoS policy to use is specified using the policy-id> and must have been configured before associating
this policy with the SAP. The SAP egress policy can be configured using the commands under the context
config> qos> sap-egress.

When a SAP egress policy is associated with the SAP configured as a mirror destination, the queue associ-
ated with FC specified with the CLI command config> mirror> mirror-dest> fc, is used for traffic sent out of
the mirror destination SAP. The policy allows the user to specify the amount of buffers, the WRED policy,
the shaping rate and the marking values to use for the mirrored copy.
The no form of the command associates the default SAP egress QoS policy with the SAP.
Default no qos
Parameters policy-id — Specifies the QoS policy to associated with SAP egress. The QoS policy referred to by the pol-
icy-id is configured using the commands under config> qos> sap-egress.

Mirror Services
Mirror Source Configuration Commands
mirror-source
Syntax [no] mirror-source service-id
Context debug
Description This command configures mirror source parameters for a mirrored service.
The mirror-source command is used to enable mirroring of packets specified by the association of the mir-
ror-source to sources of packets defined within the context of the mirror-dest-service-id. The mirror desti-
nation service must already exist within the system.
A mirrored packet cannot be mirrored to multiple destinations. If a mirrored packet is properly referenced
by multiple mirror sources (for example, a SAP on one mirror-source and a port on another mirror-
source), then the packet is mirrored to a single mirror-dest-service-id based on the following hierarchy:
1. Filter entry
2. Service access port (SAP)
3. Physical port
The hierarchy is structured so the most specific match criteria has precedence over a less specific match. For
example, if a mirror-source defines a port and a SAP on that port, then the SAP mirror-source is accepted
and the mirror-source for the port is ignored because of the hierarchical order of precedence.
The mirror-source configuration is not saved when a configuration is saved. A mirror-source manually
configured within an ASCII configuration file will not be preserved if that file is overwritten by a save com-
mand. Define the mirror-source within a file associated with a config exec command to make a mirror-
source persistent between system reboots.
By default, all mirror-dest service IDs have a mirror-source associated with them. The mirror-source is
not technically created with this command. Instead the service ID provides a contextual node for storing the
current mirroring sources for the associated mirror-dest service ID. The mirror-source is created for the
mirror service when the operator enters the debug>mirror-source svcId for the first time. The mirror-
source is also automatically removed when the mirror-dest service ID is deleted from the system.
The no form of the command deletes all related source commands within the context of the mirror-source
service-id. The command does not remove the service ID from the system.
Default No mirror source match criteria is defined for the mirror destination service.
Parameters service-id — The mirror destination service ID for which match criteria will be defined. The service-id must
already exist within the system.

ip-filter
Syntax ip-filter ip-filter-id entry entry-id [entry-id …]
no ip-filter ip-filter-id entry entry-id
Context debug>mirror-source
Description This command enables mirroring of packets that match specific entries in an existing IP filter.
The ip-filter command directs packets which match the defined list of entry IDs to be mirrored to the mirror
destination referenced by the mirror-dest-service-id of the mirror-source.
The IP filter must already exist in order for the command to execute. Filters are configured in the config>fil-
ter context. If the IP filter does not exist, an error will occur. If the filter exists but has not been associated
with a SAP or IP interface, an error is not generated but mirroring will not be enabled (there are no packets
to mirror). Once the IP filter is defined to a SAP or IP interface, mirroring is enabled.
If the IP filter is defined as ingress, only ingress packets are mirrored. Ingress mirrored packets are mirrored
to the mirror destination prior to any ingress packet modifications.
If the IP filter is defined as egress, only egress packets are mirrored. Egress mirrored packets are mirrored to
the mirror destination after all egress packet modifications.
An entry-id within an IP filter can only be mirrored to a single mirror destination. If the same entry-id is
defined multiple times, an error occurs and only the first mirror-source definition is in effect.
By default, no packets matching any IP filters are mirrored. Mirroring of IP filter entries must be explicitly
defined.
The no ip-filter command, without the entry keyword, removes mirroring on all entry-id’s within the ip-
filter-id.
When the no command is executed with the entry keyword and one or more entry-id’s, mirroring of that list
of entry-id’s is terminated within the ip-filter-id. If an entry-id is listed that does not exist, an error will occur
and the command will not execute. If an entry-id is listed that is not currently being mirrored, no error will
occur for that entry-id and the command will execute normally.
Default IP filter mirroring is not defined.
Parameters ip-filter-id — The IP filter ID whose entries are mirrored. If the ip-filter-id does not exist, an error will occur
and the command will not execute. Mirroring of packets will commence once the ip-filter-id is defined
on a SAP or IP interface.
Values 1 - 65535
entry entry-id [entry-id …] — The IP filter entries to use as match criteria for packet mirroring. The entry
keyword begins a list of entry-id’s for mirroring. Multiple entry-id entries may be specified with a sin-
gle command. Each entry-id must be separated by a space.
If an entry-id does not exist within the IP filter, an error occurs and the command will not execute.
If the filter’s entry-id is renumbered within the IP filter definition, the old entry-id is removed but the
new entry-id must be manually added to the configuration to include the new (renumbered) entry’s cri-
teria.
Values 1 - 65535

Mirror Services
mac-filter
Syntax mac-filter mac-filter-id entry entry-id [entry-id …]
no mac-filter mac-filter-id
no mac-filter mac-filter-id entry entry-id [entry-id …]
Description This command enables mirroring of packets that match specific entries in an existing MAC filter.
The mac-filter command directs packets which match the defined list of entry IDs to be mirrored to the mir-
ror destination referenced by the mirror-dest-service-id of the mirror-source.
The MAC filter must already exist in order for the command to execute. Filters are configured in the con-
fig>filter context. If the MAC filter does not exist, an error will occur. If the filter exists but has not been
associated with a SAP or IP interface, an error is not be generated but mirroring will not be enabled (there
are no packets to mirror). Once the filter is defined to a SAP or MAC interface, mirroring is enabled.
If the MAC filter is defined as ingress, only ingress packets are mirrored. Ingress mirrored packets are mir-
rored to the mirror destination prior to any ingress packet modifications.
The no mac-filter command, without the entry keyword, removes mirroring on all entry-id’s within the
mac-filter-id.
When the no command is executed with the entry keyword and one or more entry-id’s, mirroring of that list
of entry-id’s is terminated within the mac-filter-id. If an entry-id is listed that does not exist, an error will
occur and the command will not execute. If an entry-id is listed that is not currently being mirrored, no error
will occur for that entry-id and the command will execute normally.
Default No MAC filter mirroring defined.
Parameters mac-filter-id — The MAC filter ID whose entries are mirrored. If the mac-filter-id does not exist, an error
will occur and the command will not execute. Mirroring of packets will commence once the mac-filter-
id is defined on a SAP.
Values 1 - 65535
entry entry-id [entry-id …] — The MAC filter entries to use as match criteria for packet mirroring. The
entry keyword begins a list of entry-id’s for mirroring. Multiple entry-id entries may be specified with
a single command. Each entry-id must be separated by a space. Up to 8 entry IDs may be specified in a
single command.
Each entry-id must exist within the mac-filter-id. If the entry-id is renumbered within the MAC filter
definition, the old entry-id is removed from the list and the new entry-id will need to be manually added
to the list if mirroring is still desired.
If no entry-id entries are specified in the command, mirroring will not occur for that MAC filter ID. The
command will have no effect.
Values 1 - 65535

port
Syntax port {port-id | lag lag-id} {[egress] [ingress]}
no port {port-id | lag lag-id} [egress] [ingress]
Description This command enables mirroring of traffic ingressing or egressing a port (Ethernet port, or Link Aggrega-
tion Group (LAG)).
The port command associates a port or LAG to a mirror source. The port is identified by the port-id. The
defined port may be Ethernet, access or access uplink. access. A port may be a single port or a Link Aggre-
gation Group (LAG) ID. When a LAG ID is given as the port-id, mirroring is enabled on all ports making up
the LAG. Either a LAG port member or the LAG port can be mirrored.
The port is only referenced in the mirror source for mirroring purposes. If the port is removed from the sys-
tem, the mirroring association will be removed from the mirror source.
The same port may not be associated with multiple mirror source definitions with the ingress parameter
defined. The same port may not be associated with multiple mirror source definitions with the egress param-
eter defined.
If a SAP is mirrored on an access port, the SAP mirroring will have precedence over the access port mirror-
ing when a packet matches the SAP mirroring criteria. Filter and label mirroring destinations will also pre-
cedence over a port-mirroring destination.
If the port is not associated with a mirror-source, packets on that port will not be mirrored. Mirroring may
still be defined for a SAP or filter entry, which will mirror based on a more specific criteria.
The no port command disables port mirroring for the specified port. Mirroring of packets on the port may
continue due to more specific mirror criteria. If the egress or ingress parameter keywords are specified in
the no command, only the ingress or egress mirroring condition will be removed.
Default No ports are defined.
Parameters port-id — Specifies the port ID.

Values 1 - 12
lag-id — The LAG identifier, expressed as a decimal integer.
egress — Specifies that packets egressing the port should be mirrored. Egress packets are mirrored to the
mirror destination after egress packet modification.
ingress — Specifies that packets ingressing the port should be mirrored. Ingress packets are mirrored to the
mirror destination prior to ingress packet modification.

Mirror Services
sap
Syntax sap sap-id {[ingress]}
no sap sap-id[ingress]
Description This command enables mirroring of traffic ingressing or egressing a service access port (SAP). A SAP that
is defined within a mirror destination cannot be used in a mirror source. The mirror source SAP referenced
by the sap-id is owned by the service ID of the service in which it was created. The SAP is only referenced
in the mirror source name for mirroring purposes. The mirror source association does not need to be
removed before deleting the SAP from its service ID. If the SAP is deleted from its service ID, the mirror
association is removed from the mirror source.
More than one SAP can be associated within a single mirror-source. Each SAP has its own ingress param-
eter keywords to define which packets are mirrored to the mirror destination.
The SAP must be valid and properly configured. If the associated SAP does not exist, an error occurs and
the command will not execute.
The same SAP cannot be associated with multiple mirror source definitions for ingress packets.
The same SAP cannot be associated with multiple mirror source definitions for egress packets.
If a particular SAP is not associated with a mirror source name, then that SAP will not have mirroring
enabled for that mirror source.
The no form of the command disables mirroring for the specified SAP. All mirroring for that SAP on ingress
and egress is terminated. Mirroring of packets on the SAP can continue if more specific mirror criteria is
configured. If the egress or ingress parameter keywords are specified in the no command, only the ingress
or egress mirroring condition is removed.
Default No SAPs are defined by default.
Parameters sap-id — Specifies the physical port identifier portion of the SAP definition. See Common CLI Command
Descriptions on page 333 for command syntax.
ingress — Specifies that packets ingressing the SAP should be mirrored. Ingress packets are mirrored to the
mirror destination prior to ingress packet modification.


Mirror Services
Show Commands
debug
Syntax debug [application]
Context show
Description This command displays set debug points.

Parameters application — Display which debug points have been set.
Values: service, ip, ospf, ospf3, mtrace, isis, mpls, rsvp, ldp, mirror, system, filter, subscriber-mgmt,
radius, lag, oam
Output *A:alu1# show debug
debug
mirror-source 101
port 1/1/1 ingress
no shutdown
exit
mirror-source 102
port 1/1/3 egress
no shutdown
exit
exit
*A:alu1#
service-using
Syntax service-using [mirror]
Context show>service
Description Displays mirror services.
If no optional parameters are specified, all services defined on the system are displayed.
Parameters mirror — Displays mirror services.

Output Show Service-Using Mirror — The following table describes service-using mirror output fields:
Label Description
Service Id The service identifier.
Type Specifies the service type configured for the service ID.
Adm The desired state of the service.
Opr The operating state of the service.

Label Description (Continued)
CustomerID The ID of the customer who owns this service.
Last Mgmt Change The date and time of the most recent management-initiated change to
this service.
Sample Output
A:ALA-48# show service service-using mirror

===============================================================================
Services [mirror]
===============================================================================
ServiceId Type Adm Opr CustomerId Last Mgmt Change
-------------------------------------------------------------------------------
218 Mirror Up Down 1 04/08/2007 13:49:57
318 Mirror Down Down 1 04/08/2007 13:49:57
319 Mirror Up Down 1 04/08/2007 13:49:57
320 Mirror Up Down 1 04/08/2007 13:49:57
1000 Mirror Down Down 1 04/08/2007 13:49:57
1216 Mirror Up Down 1 04/08/2007 13:49:57
1412412 Mirror Down Down 1 04/08/2007 13:49:57
-------------------------------------------------------------------------------
Matching Services : 7
===============================================================================
A:ALA-48#

Mirror Services
mirror
Syntax mirror mirror-dest service-id
Context show
Description This command displays mirror configuration and operation information.
Parameters service-id — Specify the mirror service ID.

Values [1..2147483648]| svc-name:64 char max
Output Mirroring Output — The following table describes the mirroring output fields:
Label Description
Service Id The service ID associated with this mirror destination.
Type Entries in this table have an implied storage type of “volatile”.
The configured mirror source information is not persistent.
Admin State Up — The mirror destination is administratively enabled.
Down — The mirror destination is administratively disabled.

Oper State Up — The mirror destination is operationally enabled.
Down — The mirror destination is operationally disabled.
Forwarding Class The forwarding class for all packets transmitted to the mirror
destination.
Remote Sources Yes — A remote source is configured.
No — A remote source is not configured.
Slice The value of the slice-size, is the maximum portion of the mirrored
frame that will be transmitted to the mirror destination. Any frame
larger than the slice-size will be truncated to this value before
transmission to the mirror destination. A value of 0 indicates that
mirrored packet truncation based on slice size is disabled.
Destination SAP The ID of the access port where the Service Access Point (SAP)
associated with this mirror destination service is defined.
Egr QoS Policy This value indicates the egress QoS policy ID. A value of 0 indicates
that no QoS policy is specified.
Sample Output
*A:7210SAS>config>mirror>mirror-dest$ show mirror mirror-dest
===============================================================================
Mirror Services
===============================================================================

Id Type Adm Opr Destination SDP Lbl/ Slice Mirror
SAP QoS Src
Allowed
-------------------------------------------------------------------------------
1 Ether Down Down None n/a 0 Local
1000 Ether Up Down SDP 400 (1.1.1.1) Pending 0 Local
2000 Ether Up Up SAP 1/1/17:17 1 0 Remote
===============================================================================
*A:7210SAS>config>mirror>mirror-dest$
Sample Output for Network mode
*A:7210SAS>config>mirror>mirror-dest$ show mirror mirror-dest 1
===============================================================================
Mirror Service
===============================================================================
Service Id : 1 Type : Ether
Description : (Not Specified)
Admin State : Down Oper State : Down
Mirror Sources Allowed : Local
Forwarding Class : be Remote Sources: No
Profile : out
Slice : 0
==============================================================
Mirror Services SDP
==============================================================
SdpId IP Addr CfgLabel Signal EgrLabel
--------------------------------------------------------------
No Matching Entries
==============================================================
-------------------------------------------------------------------------------
Local Sources
-------------------------------------------------------------------------------
Admin State : Up
No Mirror Sources configured

===============================================================================
*A:7210SAS>config>mirror>mirror-dest$
Sample Output for Access-Uplink mode
*A:7210SAS# show mirror mirror-dest 1000
===============================================================================
Mirror Service
===============================================================================
Service Id : 1000 Type : Ether
Admin State : Up Oper State : Down
Mirror Sources Allowed : Local
Profile : out
Destination SAP : 1/1/1
-------------------------------------------------------------------------------

Mirror Services
Local Sources
-------------------------------------------------------------------------------
Admin State : Up
-Port 1/1/1 Ing

===============================================================================
*A:7210SAS#

OAM and SAA
In This Chapter
This chapter provides information about the Operations, Administration and
Management (OAM) and Service Assurance Agent (SAA) commands available in the
CLI for troubleshooting services.
• OAM Overview on page 70

→ LSP Diagnostics on page 71
→ SDP Diagnostics on page 72
→ Service Diagnostics on page 73
→ VPLS MAC Diagnostics on page 74
→ VLL Diagnostics on page 78
• Ethernet Connectivity Fault Management (ETH-CFM) on page 103
• Synthetic Loss Measurement (ETH-SL) on page 122
• Service Assurance Agent Overview on page 83
→ SAA Application on page 152

OAM Overview
OAM Overview
Delivery of services requires a number of operations occur properly and at different levels in the
service delivery model. For example, operations such as the association of packets to a service,
must be performed properly in the forwarding plane for the service to function properly. In order to
verify that a service is operational, a set of in-band, packet-based Operation, Administration, and
Maintenance (OAM) tools is required, with the ability to test each of the individual packet
operations.
For in-band testing, the OAM packets closely resemble customer packets to effectively test the
customer's forwarding path, but they are distinguishable from customer packets so they are kept
within the service provider's network and not forwarded to the customer.
The suite of OAM diagnostics supplement the basic IP ping and traceroute operations with
diagnostics specialized for the different levels in the service delivery model. There are
diagnostics for services.The following OAM features are not available on 7210 SAS-M and 7210
SAS-T devices configured in Access uplink mode:
• LSP Diagnostics
• SDP Diagnostics
• Service Diagnostics
• VPLS MAC Diagnostics
• VLL Diagnostics
Two-Way Active Measurement Protocol (TWAMP)

Two-Way Active Measurement Protocol (TWAMP) provides a standards-based method for
measuring the round-trip IP performance (packet loss, delay and jitter) between two devices.
TWAMP uses the methodology and architecture of One-Way Active Measurement Protocol
(OWAMP) to define a way to measure two-way or round-trip metrics.
There are four logical entities in TWAMP:
• The control-client
• The session-sender
• The server
• The session-reflector.
The control-client and session-sender are typically implemented in one physical device (the
“client”) and the server and session-reflector in a second physical device (the “server”) with which
the two-way measurements are being performed. The 7210 SAS acts as the server. The control-

OAM and SAA
client and server establishes a TCP connection and exchange TWAMP-Control messages over this
connection. When the control-client requires to start testing, the client communicates the test
parameters to the server. If the server corresponds to conduct the described tests, the test begins as
soon as the client sends a Start-Sessions message. As part of a test, the sessionsender sends a
stream of UDP-based test packets to the session-reflector, and the session reflector responds to
each received packet with a response UDP-based test packet. When the session-sender receives
the response packets from the session-reflector, the information is used to calculate two-way
delay, packet loss, and packet delay variation between the two devices.
Configuration Notes
The following are the configuration notes:
• Unauthenticated mode is supported. Encrypted and Authenticated modes are not

supported.
• TWAMP is supported only in the base router instance.
• By default, 7210 uses TCP port number 862 to listen for TWAMP control connections and
this is not user configurable.
LSP Diagnostics
The 7210 SAS LSP diagnostics are implementations of LSP ping and LSP traceroute based on
RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures. LSP ping and
LSP traceroute are modeled after the ICMP echo request/reply used by ping and traceroute to
detect and localize faults in IP networks.
For a given FEC, LSP ping verifies whether the packet reaches the egress label edge router (LER),
while in LSP traceroute mode, the packet is sent to the control plane of each transit label switched
router (LSR) which performs various checks to see if it is actually a transit LSR for the path.

OAM Overview
SDP Diagnostics
The 7210 SAS SDP diagnostics are SDP ping and SDP MTU path discovery.
SDP Ping
SDP ping performs in-band uni-directional or round-trip connectivity tests on SDPs. The SDP
ping OAM packets are sent in-band, in the tunnel encapsulation, so it will follow the same path as
traffic within the service. The SDP ping response can be received out-of-band in the control plane,
or in-band using the data plane for a round-trip test.
For a uni-directional test, SDP ping tests:
• Egress SDP ID encapsulation

• Ability to reach the far-end IP address of the SDP ID within the SDP encapsulation
• Path MTU to the far-end IP address over the SDP ID
• Forwarding class mapping between the near-end SDP ID encapsulation and the far-end
tunnel termination
For a round-trip test, SDP ping uses a local egress SDP ID and an expected remote SDP ID. Since
SDPs are uni-directional tunnels, the remote SDP ID must be specified and must exist as a
configured SDP ID on the far-end 7210 SAS M. SDP round trip testing is an extension of SDP
connectivity testing with the additional ability to test:
• Remote SDP ID encapsulation

• Potential service round trip time
• Round trip path MTU
• Round trip forwarding class mapping
SDP MTU Path Discovery

In a large network, network devices can support a variety of packet sizes that are transmitted
across its interfaces. This capability is referred to as the Maximum Transmission Unit (MTU) of
network interfaces. It is important to understand the MTU of the entire path end-to-end when
provisioning services, especially for virtual leased line (VLL) services where the service must
support the ability to transmit the largest customer packet.
The Path MTU discovery tool provides a powerful tool that enables service provider to get the
exact MTU supported by the network's physical links between the service ingress and service
termination points (accurate to one byte).

OAM and SAA
Service Diagnostics
Alcatel-Lucent’s Service ping feature provides end-to-end connectivity testing for an individual
service. Service ping operates at a higher level than the SDP diagnostics in that it verifies an
individual service and not the collection of services carried within an SDP.
Service ping is initiated from a 7210 SAS M router to verify round-trip connectivity and delay to
the far-end of the service. Alcatel-Lucent’s implementation functions for MPLS tunnels and tests
the following from edge-to-edge:
• Tunnel connectivity
• VC label mapping verification
• Service existence
• Service provisioned parameter verification
• Round trip path verification
• Service dynamic configuration verification

OAM Overview
VPLS MAC Diagnostics

While the LSP ping, SDP ping and service ping tools enable transport tunnel testing and verify
whether the correct transport tunnel is used, they do not provide the means to test the learning and
forwarding functions on a per-VPLS-service basis.
It is conceivable, that while tunnels are operational and correctly bound to a service, an incorrect
Forwarding Information Base (FIB) table for a service could cause connectivity issues in the
service and not be detected by the ping tools. Alcatel-Lucent has developed VPLS OAM
functionality to specifically test all the critical functions on a per-service basis. These tools are
based primarily on the IETF document draft-stokes-vkompella-ppvpn-hvpls-oam-xx.txt, Testing
Hierarchical Virtual Private LAN Services.
The VPLS OAM tools are:
• MAC Ping — Provides an end-to-end test to identify the egress customer-facing port
where a customer MAC was learned. MAC ping can also be used with a broadcast MAC
address to identify all egress points of a service for the specified broadcast MAC.
• MAC Trace — Provides the ability to trace a specified MAC address hop-by-hop until the
last node in the service domain. An SAA test with MAC trace is considered successful
when there is a reply from a far-end node indicating that they have the destination MAC
address on an egress SAP or the CPM.
• CPE Ping — Provides the ability to check network connectivity to the specified client
device within the VPLS. CPE ping will return the MAC address of the client, as well as
the SAP and PE at which it was learned.
• MAC Populate — Allows specified MAC addresses to be injected in the VPLS service
domain. This triggers learning of the injected MAC address by all participating nodes in
the service. This tool is generally followed by MAC ping or MAC trace to verify if correct
learning occurred.
• MAC Purge — Allows MAC addresses to be flushed from all nodes in a service domain.
MAC Ping
For a MAC ping test, the destination MAC address (unicast or multicast) to be tested must be
specified. A MAC ping packet can be sent through the control plane or the data plane. When sent
by the control plane, the ping packet goes directly to the destination IP in a UDP/IP OAM packet.
If it is sent by the data plane, the ping packet goes out with the data plane format.
In the control plane, a MAC ping is forwarded along the flooding domain if no MAC address
bindings exist. If MAC address bindings exist, then the packet is forwarded along those paths (if
they are active). Finally, a response is generated only when there is an egress SAP binding to that
MAC address. A control plane request is responded to via a control reply only.

OAM and SAA
In the data plane, a MAC ping is sent with a VC label TTL of 255. This packet traverses each hop
using forwarding plane information for next hop, VC label, etc. The VC label is swapped at each
service-aware hop, and the VC TTL is decremented. If the VC TTL is decremented to 0, the
packet is passed upto the management plane for processing. If the packet reaches an egress node,
and would be forwarded out a customer facing port, it is identified by the OAM label below the
VC label and passed to the management plane.
MAC pings are flooded when they are unknown at an intermediate node. They are responded to
only by the egress nodes that have mappings for that MAC address.
MAC Trace
A MAC trace functions like an LSP trace with some variations. Operations in a MAC trace are
triggered when the VC TTL is decremented to 0.
Like a MAC ping, a MAC trace can be sent either by the control plane or the data plane.
For MAC trace requests sent by the control plane, the destination IP address is determined from
the control plane mapping for the destination MAC. If the destination MAC is known to be at a
specific remote site, then the far-end IP address of that SDP is used. If the destination MAC is not
known, then the packet is sent unicast, to all SDPs in the service with the appropriate squelching.
A control plane MAC traceroute request is sent via UDP/IP. The destination UDP port is the LSP
ping port. The source UDP port is whatever the system gives (note that this source UDP port is
really the demultiplexor that identifies the particular instance that sent the request, when
correlating the reply). The source IP address is the system IP of the sender.
When a traceroute request is sent via the data plane, the data plane format is used. The reply can be
via the data plane or the control plane.
A data plane MAC traceroute request includes the tunnel encapsulation, the VC label, and the
OAM, followed by an Ethernet DLC, a UDP and IP header. If the mapping for the MAC address is
known at the sender, then the data plane request is sent down the known SDP with the appropriate
tunnel encapsulation and VC label. If it is not known, then it is sent down every SDP (with the
appropriate tunnel encapsulation per SDP and appropriate egress VC label per SDP binding).
The tunnel encapsulation TTL is set to 255. The VC label TTL is initially set to the min-ttl (default
is 1). The OAM label TTL is set to 2. The destination IP address is the all-routers multicast
address. The source IP address is the system IP of the sender.
The destination UDP port is the LSP ping port. The source UDP port is whatever the system gives
(note that this source UDP port is really the demultiplexor that identifies the particular instance
that sent the request, when correlating the reply).

OAM Overview
The Reply Mode is either 3 (i.e., reply via the control plane) or 4 (i.e., reply through the data
plane), depending on the reply-control option. By default, the data plane request is sent with Reply
Mode 3 (control plane reply)Reply Mode 4 (data plane reply).
The Ethernet DLC header source MAC address is set to either the system MAC address (if no
source MAC is specified) or to the specified source MAC. The destination MAC address is set to
the specified destination MAC. The EtherType is set to IP.
CPE Ping
The MAC ping OAM tool makes it possible to detect whether a particular MAC address has been
learned in a VPLS.
The cpe-ping command extends this capability to detecting end-station IP addresses inside a
VPLS. A CPE ping for a specific destination IP address within a VPLS will be translated to a
MAC-ping towards a broadcast MAC address. Upon receiving such a MAC ping, each peer PE
within the VPLS context will trigger an ARP request for the specific IP address. The PE receiving
a response to this ARP request will report back to the requesting 7210 SAS M, X. It is encouraged
to use the source IP address of 0.0.0.0 to prevent the provider’s IP address of being learned by the
CE.

OAM and SAA
MAC Populate
MAC populate is used to send a message through the flooding domain to learn a MAC address as
if a customer packet with that source MAC address had flooded the domain from that ingress point
in the service. This allows the provider to craft a learning history and engineer packets in a
particular way to test forwarding plane correctness.
The MAC populate request is sent with a VC TTL of 1, which means that it is received at the
forwarding plane at the first hop and passed directly upto the management plane. The packet is
then responded to by populating the MAC address in the forwarding plane, like a conventional
learn although the MAC will be an OAM-type MAC in the FIB to distinguish it from customer
MAC addresses.
This packet is then taken by the control plane and flooded out the flooding domain (squelching
appropriately, the sender and other paths that would be squelched in a typical flood).
This controlled population of the FIB is very important to manage the expected results of an OAM
test. The same functions are available by sending the OAM packet as a UDP/IP OAM packet. It is
then forwarded to each hop and the management plane has to do the flooding.
Options for MAC populate are to force the MAC in the table to type OAM (in case it already
existed as dynamic or static or an OAM induced learning with some other binding), to prevent
new dynamic learning to over-write the existing OAM MAC entry, to allow customer packets with
this MAC to either ingress or egress the network, while still using the OAM MAC entry.
Finally, an option to flood the MAC populate request causes each upstream node to learn the
MAC, for example, populate the local FIB with an OAM MAC entry, and to flood the request
along the data plane using the flooding domain.
An age can be provided to age a particular OAM MAC after a different interval than other MACs
in a FIB.
MAC Purge
MAC purge is used to clear the FIBs of any learned information for a particular MAC address.
This allows one to do a controlled OAM test without learning induced by customer packets. In
addition to clearing the FIB of a particular MAC address, the purge can also indicate to the control
plane not to allow further learning from customer packets. This allows the FIB to be clean, and be
populated only via a MAC Populate.
MAC purge follows the same flooding mechanism as the MAC populate.
A UDP/IP version of this command is also available that does not follow the forwarding notion of
the flooding domain, but the control plane notion of it.

OAM Overview
VLL Diagnostics
VCCV Ping
VCCV ping is used to check connectivity of a VLL in-band. It checks that the destination (target)
PE is the egress for the Layer 2 FEC. It provides a cross-check between the data plane and the
control plane. It is in-band, meaning that the VCCV ping message is sent using the same
encapsulation and along the same path as user packets in that VLL. This is equivalent to the LSP
ping for a VLL service. VCCV ping reuses an LSP ping message format and can be used to test a
VLL configured over an MPLS SDP.
VCCV-Ping Application
VCCV effectively creates an IP control channel within the pseudowire between PE1 and PE2. PE2
should be able to distinguish on the receive side VCCV control messages from user packets on that
VLL. There are three possible methods of encapsulating a VCCV message in a VLL which
translates into three types of control channels:
1. Use of a Router Alert Label immediately above the VC label. This method has the drawback
that if ECMP is applied to the outer LSP label (for example, transport label), the VCCV
message will not follow the same path as the user packets. This effectively means it will not
troubleshoot the appropriate path. This method is supported by the 7210 SAS M.
2. Use of the OAM control word as illustrated in Figure 7.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 1| FmtID | Reserved | Channel Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: OAM Control Word Format
The first nibble is set to 0x1. The Format ID and the reserved fields are set to 0 and the
channel type is the code point associated with the VCCV IP control channel as specified in
the PWE3 IANA registry (RFC 4446). The channel type value of 0x21 indicates that the
Associated Channel carries an IPv4 packet.
The use of the OAM control word assumes that the draft-martini control word is also used
on the user packets. This means that if the control word is optional for a VLL and is not
configured, the 7210 SAS M, X PE node will only advertise the router alert label as the
CC capability in the Label Mapping message. This method is supported by the 7210 SAS
M.

OAM and SAA
3. Set the TTL in the VC label to 1 to force PE2 control plane to process the VCCV message.
This method is not guaranteed to work under all circumstances. For instance, the draft
mentions some implementations of penultimate hop popping overwrite the TTL field. This
method is not supported by the 7210 SAS M.
When sending the label mapping message for the VLL, PE1 and PE2 must indicate which of the
above OAM packet encapsulation methods (for example, which control channel type) they
support. This is accomplished by including an optional VCCV TLV in the pseudowire FEC
Interface Parameter field. The format of the VCCV TLV is shown in Figure 8.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x0c | 0x04 | CC Types | CV Types |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8: VCCV TLV
Note that the absence of the optional VCCV TLV in the Interface parameters field of the
pseudowire FEC indicates the PE has no VCCV capability.
The Control Channel (CC) Type field is a bitmask used to indicate if the PE supports none, one, or
many control channel types.
• 0x00 None of the following VCCV control channel types are supported
• 0x01 PWE3 OAM control word (see Figure 7)
• 0x02 MPLS Router Alert Label
• 0x04 MPLS inner label TTL = 1
If both PE nodes support more than one of the CC types, then a 7210 SAS M PE will make use of
the one with the lowest type value. For instance, OAM control word will be used in preference to
the MPLS router alert label.
The Connectivity Verification (CV) bitmask field is used to indicate the specific type of VCCV
packets to be sent over the VCCV control channel. The valid values are:
0x00 None of the below VCCV packet type are supported.
0x01 ICMP ping. Not applicable to a VLL over a MPLS SDP and as such is not supported by the
7210 SAS M.
0x02 LSP ping. This is used in VCCV-Ping application and applies to a VLL over an MPLS SDP.
This is supported by the 7210 SAS M.
A VCCV ping is an LSP echo request message as defined in RFC 4379. It contains an L2 FEC
stack TLV which must include within the sub-TLV type 10 “FEC 128 Pseudowire”. It also

OAM Overview
contains a field which indicates to the destination PE which reply mode to use. There are four
reply modes defined in RFC 4379:
Reply mode, meaning:
1. Do not reply. This mode is supported by the 7210 SAS M.

2. Reply via an IPv4/IPv6 UDP packet. This mode is supported by the 7210 SAS M.
3. Reply with an IPv4/IPv6 UDP packet with a router alert. This mode sets the router alert bit in
the IP header and is not be confused with the CC type which makes use of the router alert
label. This mode is not supported by the 7210 SAS M.
4. Reply via application level control channel. This mode sends the reply message inband over
the pseudowire from PE2 to PE1. PE2 will encapsulate the Echo Reply message using the CC
type negotiated with PE1. This mode is supported by the 7210 SAS M.
The reply is an LSP echo reply message as defined in RFC 4379. The message is sent as per the
reply mode requested by PE1. The return codes supported are the same as those supported in the
7210 SAS M LSP ping capability.
The VCCV ping feature is in addition to the service ping OAM feature which can be used to test a
service between 7210 SAS M nodes. The VCCV ping feature can test connectivity of a VLL with
any third party node which is compliant to RFC 5085.
VCCVE cho VCCVE cho

Request Reply
7210 SAS Ethernet PW 7210 SAS

CE 1 [64.47.30.1/30] CE 2 [64.47.30.2/30]
Ethernet SAP Ethernet SAP

1/1/1:100 IP/MPLS 1/1/1:200
MTU-s MTU-s
IPIPE_0107210M
Figure 9: VCCV-Ping Application

OAM and SAA
VCCV-Ping in a Multi-Segment Pseudowire

Pseudowire switching is a method for scaling a large network of VLL or VPLS services by
removing the need for a full mesh of T-LDP sessions between the PE nodes as the number of these
nodes grow over time. Pseudowire switching is also used whenever there is a need to deploy a
VLL service across two separate routing domains.
In the network, a Termination PE (T-PE) is where the pseudowire originates and terminates. The
7210 SAS M supports only T-PE. It does not support S-PE functionality.
VCCV ping is extended to be able to perform the following OAM functions:
1. VCCV ping to a destination PE. A VLL FEC Ping is a message sent by T-PE1 to test the
FEC at T-PE2. The operation at T-PE1 and T-PE2 is the same as in the case of a single-
segment pseudowire. The pseudowire switching node, S-PE1, pops the outer label, swaps the
inner (VC) label, decrements the TTL of the VC label, and pushes a new outer label. The
7210 SAS M PE1 node does not process the VCCV OAM Control Word unless the VC label
TTL expires. In that case, the message is sent to the CPM for further validation and
processing. This is the method described in draft-hart-pwe3-segmented-pw-vccv.
Automated VCCV-Trace Capability for MS-Pseudowire

Although tracing of the MS-pseudowire path is possible using the methods explained in previous
sections, these require multiple manual iterations and that the FEC of the last pseudowire segment
to the target T-PE/S-PE be known a priori at the node originating the echo request message for
each iteration. This mode of operation is referred to as a “ping” mode.
The automated VCCV-trace can trace the entire path of a pseudowire with a single command
issued at the T-PE or at an S-PE. This is equivalent to LSP-trace and is an iterative process by
which the ingress T-PE or T-PE sends successive VCCV-ping messages with incrementing the
TTL value, starting from TTL=1.
The method is described in draft-hart-pwe3-segmented-pw-vccv, VCCV Extensions for Segmented

Pseudo-Wire, and is pending acceptance by the PWE3 working group. In each iteration, the source
T-PE or S-PE builds the MPLS echo request message in a way similar to VCCV Ping on page 78.
The first message with TTL=1 will have the next-hop S-PE T-LDP session source address in the
Remote PE Address field in the pseudowire FEC TLV. Each S-PE which terminates and processes
the message will include in the MPLS echo reply message the FEC 128 TLV corresponding the
pseudowire segment to its downstream node. The inclusion of the FEC TLV in the echo reply
message is allowed in RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane
Failures. The source T-PE or S-PE can then build the next echo reply message with TTL=2 to test
the next-next hop for the MS-pseudowire. It will copy the FEC TLV it received in the echo reply
message into the new echo request message. The process is terminated when the reply is from the

OAM Overview
egress T-PE or when a timeout occurs. If specified, the max-ttl parameter in the vccv-trace
command will stop on SPE before reaching T-PE.
The results VCCV-trace can be displayed for a fewer number of pseudowire segments of the end-
to-end MS-pseudowire path. In this case, the min-ttl and max-ttl parameters are configured
accordingly. However, the T-PE/S-PE node will still probe all hops upto min-ttl in order to
correctly build the FEC of the desired subset of segments.
Note that this method does not require the use of the downstream mapping TLV in the echo request
and echo reply messages.
VCCV for Static Pseudowire Segments

MS pseudowire is supported with a mix of static and signaled pseudowire segments. However,
VCCV ping and VCCV-trace is allowed until at least one segment of the MS pseudowire is static.
Users cannot test a static segment but also, cannot test contiguous signaled segments of the MS-
pseudowire. VCCV ping and VCCV trace is not supported in static-to-dynamic configurations.

OAM and SAA
Detailed VCCV-Trace Operation

In Figure on page 69 a trace can be performed on the MS-pseudowire originating from T-PE1 by
a single operational command. The following process occurs:
1. T-PE1 sends a VCCV echo request with TTL set to 1 and a FEC 128 containing the pseudo-
wire information of the first segment (pseudowire1 between T-PE1 and S-PE) to S-PE for
validation.
2. S-PE validates the echo request with the FEC 128. Since it is a switching point between the
first and second segment it builds an echo reply with a return code of 8 and includes the FEC
128 of the second segment (pseudowire2 between S-PE and T-PE2) and sends the echo reply
back to T-PE1.
3. T-PE1 builds a second VCCV echo request based on the FEC128 in the echo reply from the
S-PE. It increments the TTL and sends the next echo request out to T-PE2. Note that the
VCCV echo request packet is switched at the S-PE datapath and forwarded to the next
downstream segment without any involvement from the control plane.
4. T-PE2 receives and validates the echo request with the FEC 128 of the pseudowire2 from T-
PE1. Since T-PE2 is the destination node or the egress node of the MS-pseudowire it replies
to T-PE1 with an echo reply with a return code of 3 (egress router) and no FEC 128 is
included.
5. T-PE1 receives the echo reply from T-PE2. T-PE1 is made aware that T-PE2 is the
destination of the MS pseudowire because the echo reply does not contain the FEC 128 and
because its return code is 3. The trace process is completed.

OAM Overview
Control Plane Processing of a VCCV Echo Message in a MS-Pseudowire
Sending a VCCV Echo Request

When in the ping mode of operation, the sender of the echo request message requires the FEC of
the last segment to the target S-PE/T-PE node. This information can either be configured manually
or be obtained by inspecting the corresponding sub-TLV's of the pseudowire switching point TLV.
However, the pseudowire switching point TLV is optional and there is no guarantee that all S-PE
nodes will populate it with their system address and the pseudowire-id of the last pseudowire
segment traversed by the label mapping message. Thus the 7210 SAS M implementation will
always make use of the user configuration for these parameters.
Receiving an VCCV Echo Request

Upon receiving a VCCV echo request the control plane on S-PEs (or the target node of each
segment of the MS pseudowire) validates the request and responds to the request with an echo
reply consisting of the FEC 128 of the next downstream segment and a return code of 8 (label
switched at stack-depth) indicating that it is an S-PE and not the egress router for the MS-
pseudowire.
If the node is the T-PE or the egress node of the MS-pseudowire, it responds to the echo request
with an echo reply with a return code of 3 (egress router) and no FEC 128 is included.
Receiving an VCCV Echo Reply

The operation to be taken by the node that receives the echo reply in response to its echo request
depends on its current mode of operation such as ping or trace.
In ping mode, the node may choose to ignore the target FEC 128 in the echo reply and report only
the return code to the operator.

OAM and SAA
MPLS-TP On-Demand OAM Commands (Supported only on 7210

SAS-R6 and 7210 SAS-T)
NOTE: This feature is supported on 7210 SAS-T network mode and 7210 SAS-R6 devices.
Ping and Trace tools for PWs and LSPs are supported with both IP encapsulation and the MPLS-
TP on demand CV channel for non-IP encapsulation (0x025).
MPLS-TP Pseudowires: VCCV-Ping/VCCV-Trace

For vccv-ping and vccv-trace commands:
• Sub-type static must be specified. This indicates to the system that the rest of the
command contains parameters that are applied to a static PW with a static PW FEC.
• Add the ability to specify the non-IP ACH channel type (0x0025). This is known as the
non-ip control-channel. This is the default for type static. GAL is not supported for PWs.
• If the ip-control-channel is specified as the encapsulation, then the IPv4 channel type is
used (0x0021). In this case, a destination IP address in the 127/8 range is used, while the
source address in the UDP/IP packet is set to the system IP address, or may be explicitly
configured by the user with the src-ip-address option. This option is only valid if the IPv4
control-channel is specified.
• The reply mode are always assumed to be the same application level control channel type
for type static.
• Allow an MPLS-TP global-id and node-id specified under the spoke-sdps with a given
sdp-id:vc-id, used for MPLS-TP PW MEPs, or node-id (prefix) only for MIPs.
• The following CLI command description shows the options that are only allowed if the
type static option is configured. All other options are blocked.
• As in the existing implementation, the downstream mapping and detailed downstream
mapping TLVs (DSMAP/DDMAP TLVs) is not supported on PWs.
vccv-ping static <sdp-id:vc-id> [dest-global-id <global-id> dest-node-id <node-id>] [con-
trol-channel ipv4 | non-ip] [fc <fc-name> [profile {in|out}]] [size <octets>] [count
<send-count>] [timeout <timeout>] [interval <interval>] [ttl <vc-label-ttl>][src-ip-
address <ip-address>]
vccv-trace static <sdp-id:vc-id> [size <octets>][min-ttl <min-vc-label-ttl>][max-ttl
<max-vc-label-ttl>][max-fail <no-response-count>][probe-count <probe-count>] [control-
channel ipv4 | non-ip] [timeout <timeout-value>][interval <interval-value>][fc <fc-name>
[profile {in|out}]][src-ip-address <ip-address>] [detail]
If the spoke-sdp referred to by sdp-id:vc-id has an MPLS-TP PW-Path-ID defined, then those
parameters are used to populate the static PW TLV in the target FEC stack of the vccv-ping or
vccv-trace packet. If a Global-ID and Node-ID are specified in the command, then these values are
used to populate the destination node TLV in the vccv-ping or vccv-trace packet.

OAM Overview
The global-id/node-id are only used as the target node identifiers if the vccv-ping is not end-to-end
(for example, a TTL is specified in the vccv-ping/trace command and it is < 255); otherwise, the
value in the PW Path ID is used. For vccv-ping, the dest-node-id may be entered as a 4-octet IP
address <a.b.c.d> or 32-bit integer <1..4294967295>. For vccv-trace, the destination node-id and
global-id are taken form the spoke-sdp context.
The same command syntax is applicable for SAA tests configured under configure saa test a type.
MPLS-TP LSPs: LSP-Ping/LSP Trace

For lsp-ping and lsp-trace commands:
• The sub-type static must be specified. This indicates to the system that the rest of the
command contains parameters specific to a LSP identified by a static LSP FEC.
• The 7210 SAS supports the use of the G-ACh with non-IP encapsulation or labeled
encapsulation with IP de-multiplexing for both the echo request and echo reply for LSP-
Ping and LSP-Trace on LSPs with a static LSP FEC (such as MPLS-TP LSPs).
• It is possible to specify the target MPLS-TP MEP/MIP identifier information for LSP
Ping. If the target global-id and node-id are not included in the lsp-ping command, then
these parameters for the target MEP ID are taken from the context of the LSP. The tunnel-
number <tunnel-num> and lsp-num <lsp-num> for the far-end MEP are always taken
from the context of the path under test.
lsp-ping static <lsp-name>
[force]
[path-type [active|working|protect]]
[fc <fc-name> [profile {in|out}]]
[size <octets>]
[ttl <label-ttl>]
[send-count <send-count>]
[timeout <timeout>]
[interval <interval>]
[src-ip-address <ip-address>]
[dest-global-id <dest-global-id> dest-node-id dest-node-id]
[control-channel none | non-ip][detail]
lsp-trace static <lsp-name>
[force]
[path-type [active|working|protect]
[fc <fc-name> [profile {in|out}]]
[max-fail <no-response-count>]
[probe-count <probes-per-hop>]
[size <octets>]
[min-ttl <min-label-ttl>]
[max-ttl <max-label-ttl>]
[timeout <timeout>]
[interval <interval>]
[src-ip-address <ip-address>]
[control-channel none | non-ip]
[downstream-map-tlv <dsmap|ddmap>]
[detail]

OAM and SAA
The following commands are only valid if the sub-type static option is configured, implying that
lsp-name refers to an MPLS-TP tunnel LSP:
path-type. Values: active, working, protect. Default: active.
dest-global-id <global-id> dest-node-id <node-id>: Default: the to global-id:node-id from the

LSP ID.
control-channel: If this is set to none, then IP encapsulation over an LSP is used with a
destination address in the 127/8 range. The source address is set to the system IP address, unless
the user specifies a source address using the src-ip-address option. If this is set to non-ip, then
non-IP encapsulation over a G-ACh with channel type 0x00025 is used. This is the default for
sub-type static. Note that the encapsulation used for the echo reply is the same as the
encapsulation used for the echo request.
downstream-map-tlv: LSP Trace commands with this option can only be executed if the control-
channel is set to none. The DSMAP/DDMAP TLV is only included in the echo request message if
the egress interface is either a numbered IP interface, or an unnumbered IP interface. The TLV
will not be included if the egress interface is of type unnumbered-mpls-tp.
For lsp-ping, the dest-node-id may be entered as a 4-octet IP address <a.b.c.d> or 32-bit integer
<1..4294967295>. For lsp-trace, the destination node-id and global-id are taken form the spoke-
sdp context.
The send mode and reply mode are always taken to be an application level control channel for
MPLS-TP.
The force parameter causes an LSP ping echo request to be sent on an LSP that has been brought
oper-down by BFD (LSP-Ping echo requests would normally be dropped on oper-down LSPs).
This parameter is not applicable to SAA.
The LSP ID used in the LSP Ping packet is derived from a context lookup based on lsp-name and
path-type (active/working/protect).
Dest-global-id and dest-node-id refer to the target global/node id. They do not need to be entered
for end-to-end ping and trace, and the system will use the destination global id and node id from
the LSP ID.
The same command syntax is applicable for SAA tests configured under configure>saa>test.

OAM Overview
MPLS-TP Show Commands
Static MPLS Labels

The following new commands show the details of the static MPLS labels.
show>router>mpls-labels>label <start-label> [<end-label> [in-use|<label-owner>]]
show>router>mpls-labels>label-range
An example output is as follows:
*A:mlstp-dutA# show router mpls

mpls mpls-labels
*A:mlstp-dutA# show router mpls label
label label-range
*A:mlstp-dutA# show router mpls label-range
===============================================================================
Label Ranges
===============================================================================
Label Type Start Label End Label Aging Total Available
-------------------------------------------------------------------------------
Static-lsp 32 16415 - 16364
Static-svc 16416 32799 - 16376
Dynamic 32800 131071 0 98268
===============================================================================
MPLS-TP Tunnel Configuration

These should show the configuration of a given tunnel.
show>router>mpls>tp-lsp
A sample output is as follows:
*A:mlstp-dutA# show router mpls tp-lsp

- tp-lsp [<lsp-name>] [status {up|down}] [from <ip-address>|to <ip-address>]
[detail]
- tp-lsp [<lsp-name>] path [protect|working] [detail]
- tp-lsp [<lsp-name>] protection
<lsp-name> : [32 chars max] - accepts * as wildcard char

<path> : keyword - Display LSP path information.
<protection> : keyword - Display LSP protection information.
<up|down> : keywords - Specify state of the LSP
<ip-address> : a.b.c.d

OAM and SAA
<detail> : keyword - Display detailed information.

*A:mlstp-dutA# show router mpls tp-lsp
path
protection
to <a.b.c.d>
<lsp-name>
"lsp-32" "lsp-33" "lsp-34" "lsp-35" "lsp-36" "lsp-37" "lsp-38" "lsp-39"
"lsp-40" "lsp-41"
status {up|down}
from <ip-address>
detail
*A:mlstp-dutA# show router mpls tp-lsp "lsp-

"lsp-40" "lsp-41"
*A:mlstp-dutA# show router mpls tp-lsp "lsp-32"
===============================================================================
MPLS MPLS-TP LSPs (Originating)
===============================================================================
LSP Name To Tun Protect Adm Opr
Id Path
-------------------------------------------------------------------------------
lsp-32 0.0.3.234 32 No Up Up
-------------------------------------------------------------------------------
LSPs : 1
===============================================================================
*A:mlstp-dutA# show router mpls tp-lsp "lsp-32" detail
===============================================================================
MPLS MPLS-TP LSPs (Originating) (Detail)
===============================================================================
-------------------------------------------------------------------------------
Type : Originating
-------------------------------------------------------------------------------
LSP Name : lsp-32
LSP Type : MplsTp LSP Tunnel ID : 32
From Node Id: 0.0.3.233+ To Node Id : 0.0.3.234
Adm State : Up Oper State : Up
LSP Up Time : 0d 04:50:47 LSP Down Time : 0d 00:00:00
Transitions : 1 Path Changes : 2
DestGlobalId: 42 DestTunnelNum : 32
MPLS-TP Path configuration.

This can reuse and augment the output of the current show commands for static LSPs. They
should also show if BFD is enabled on a given path. If this referring to a transit path, this should
also display (among others) the path-id (7 parameters) for a given transit-path-name, or the transit-
path-name for a given the path-id (7 parameters)
show>router>mpls>tp-lsp>path

OAM Overview
===============================================================================
*A:mlstp-dutA# show router mpls tp-lsp path
===============================================================================
MPLS-TP LSP Path Information
===============================================================================
LSP Name : lsp-32 To : 0.0.3.234
Admin State : Up Oper State : Up
-------------------------------------------------------------------------------
Path NextHop InLabel OutLabel Out I/F Admin Oper
-------------------------------------------------------------------------------
Working 32 32 AtoB_1 Up Down
Protect 2080 2080 AtoC_1 Up Up
===============================================================================
LSP Name : lsp-33 To : 0.0.3.234
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
===============================================================================
LSP Name : lsp-34 To : 0.0.3.234
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
===============================================================================
LSP Name : lsp-35 To : 0.0.3.234
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
===============================================================================
LSP Name : lsp-36 To : 0.0.3.234
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
===============================================================================
LSP Name : lsp-37 To : 0.0.3.234
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------

OAM and SAA
===============================================================================
LSP Name : lsp-38 To : 0.0.3.234
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
===============================================================================
LSP Name : lsp-39 To : 0.0.3.234
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
===============================================================================
LSP Name : lsp-40 To : 0.0.3.234
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
===============================================================================
LSP Name : lsp-41 To : 0.0.3.234
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
*A:mlstp-dutA# show router mpls tp-lsp "lsp-32" path working
===============================================================================
MPLS-TP LSP Working Path Information
LSP: "lsp-32"
===============================================================================
LSP Name : lsp-32 To : 0.0.3.234
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
===============================================================================
*A:mlstp-dutA# show router mpls tp-lsp "lsp-32" path protect
===============================================================================
MPLS-TP LSP Protect Path Information
LSP: "lsp-32"
===============================================================================
LSP Name : lsp-32 To : 0.0.3.234

OAM Overview
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
===============================================================================
*A:mlstp-dutA# show router mpls tp-lsp "lsp-32" path protect detail
===============================================================================
MPLS-TP LSP Protect Path Information
LSP: "lsp-32" (Detail)
===============================================================================
LSP Name : lsp-32 To : 0.0.3.234
Protect path information

-------------------------------------------------------------------------------
Path Type : Protect LSP Num : 2
Path Admin : Up Path Oper : Up
Out Interface : AtoC_1 Next Hop Addr : n/a
In Label : 2080 Out Label : 2080
Path Up Time : 0d 04:52:17 Path Dn Time : 0d 00:00:00
Active Path : Yes Active Time : 0d 00:52:56
MEP information
MEP State : Up BFD : cc
OAM Templ : privatebed-oam-template CC Status : inService
CV Status : unknown
Protect Templ : privatebed-protection-template WTR Count Down: 0 seconds
RX PDU : SF (1,1) TX PDU : SF (1,1)
Defects :
===============================================================================
*A:mlstp-dutA# show router mpls tp-lsp "lsp-32" path working detail
===============================================================================
MPLS-TP LSP Working Path Information
LSP: "lsp-32" (Detail)
===============================================================================
LSP Name : lsp-32 To : 0.0.3.234
Working path information

-------------------------------------------------------------------------------
Path Type : Working LSP Num : 1
Path Admin : Up Path Oper : Down
Down Reason : ccFault ifDn
Out Interface : AtoB_1 Next Hop Addr : n/a
Path Up Time : 0d 00:00:00 Path Dn Time : 0d 00:53:01
Active Path : No Active Time : n/a
MEP information
MEP State : Up BFD : cc
OAM Templ : privatebed-oam-template CC Status : outOfService
CV Status : unknown
===============================================================================
*A:mlstp-dutA#

OAM and SAA
MPLS-TP Protection.
These should show the protection configuration for a given tunnel, which path in a tunnel is
currently working and which is protect, and whether the working or protect is currently active.
show>router>mpls>tp-lsp>protection
*A:mlstp-dutA# show router mpls tp-lsp protection
===============================================================================
MPLS-TP LSP Protection Information
Legend: W-Working, P-Protect,
===============================================================================
LSP Name Admin Oper Path Ingr/Egr Act. Rx PDU
State State State Label Path Tx PDU
-------------------------------------------------------------------------------
lsp-32 Up Up W Down 32/32 No SF (1,1)
P Up 2080/2080 Yes SF (1,1)
P Up 2082/2082 Yes SF (1,1)
P Up 2084/2084 Yes SF (1,1)
P Up 2086/2086 Yes SF (1,1)
P Up 2088/2088 Yes SF (1,1)
P Up 2090/2090 Yes SF (1,1)
P Up 2092/2092 Yes SF (1,1)
P Up 2094/2094 Yes SF (1,1)
P Up 2096/2096 Yes SF (1,1)
P Up 2098/2098 Yes SF (1,1)
-------------------------------------------------------------------------------
No. of MPLS-TP LSPs: 10
===============================================================================
BFD
The existing show>router>bfd context should be enhanced for MPLS-TP, as follows:
show>router>bfd>mpls-tp-lsp
Displays the MPLS –TP paths for which BFD is enabled.

OAM Overview
show>router>bfd>session [src <ip-address> [dest <ip-address> | detail]]|[mpls-tp-path <lsp-

id…> [detail]]
Should be enhanced to show the details of the BFD session on a particular MPLS-TP path, where
lsp-id is the fully qualified lsp-id to which the BFD session is in associated.
*A:mlstp-dutA# show router bfd

- bfd
bfd-template - Display BFD Template information

interface - Display Interfaces with BFD
session - Display session information
*A:mlstp-dutA# show router bfd bfd-template "privatebed-bfd-template"
===============================================================================
BFD Template privatebed-bfd-template
===============================================================================
Template Name : privatebed-* Template Type : cpmNp
Transmit Timer : 10 msec Receive Timer : 10 msec
CV Transmit Interval : 1000 msec
Template Multiplier : 3 Echo Receive Interval : 100 msec
Mpls-tp Association
privatebed-oam-template
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:mlstp-dutA# show router bfd session
===============================================================================
BFD Session
===============================================================================
Interface/Lsp Name State Tx Intvl Rx Intvl Multipl
Remote Address/Info Protocols Tx Pkts Rx Pkts Type
-------------------------------------------------------------------------------
wp::lsp-32 Down (1) 1000 1000 3
0::0.0.0.0 mplsTp N/A N/A cpm-np
wp::lsp-33 Down (1) 1000 1000 3
wp::lsp-34 Down (1) 1000 1000 3
wp::lsp-35 Down (1) 1000 1000 3
wp::lsp-36 Down (1) 1000 1000 3
wp::lsp-37 Down (1) 1000 1000 3
wp::lsp-38 Down (1) 1000 1000 3
wp::lsp-39 Down (1) 1000 1000 3
wp::lsp-40 Down (1) 1000 1000 3
wp::lsp-41 Down (1) 1000 1000 3

OAM and SAA
pp::lsp-32 Up (3) 1000 1000 3

pp::lsp-33 Up (3) 1000 1000 3
pp::lsp-34 Up (3) 1000 1000 3
pp::lsp-35 Up (3) 1000 1000 3
pp::lsp-36 Up (3) 1000 1000 3
pp::lsp-37 Up (3) 1000 1000 3
pp::lsp-38 Up (3) 1000 1000 3
pp::lsp-39 Up (3) 1000 1000 3
pp::lsp-40 Up (3) 1000 1000 3
pp::lsp-41 Up (3) 1000 1000 3
-------------------------------------------------------------------------------
No. of BFD sessions: 20
-------------------------------------------------------------------------------
wp = Working path pp = Protecting path
===============================================================================
MPLS TP Node Configuration

Displays the Global ID, Node ID and other general MPLS-TP configurations for the node.
show>router>mpls>mpls-tp
*A:mlstp-dutA# show router mpls mpls-tp

- mpls-tp
oam-template - Display MPLS-TP OAM Template information

protection-tem* - Display MPLS-TP Protection Template information
status - Display MPLS-TP system configuration
transit-path - Display MPLS-TP Tunnel information
*A:mlstp-dutA# show router mpls mpls-tp oam-template
===============================================================================
MPLS-TP OAM Templates
===============================================================================
Template Name : privatebed-oam-template Router ID : 1
BFD Template : privatebed-bfd-template Hold-Down Time: 0 centiseconds
Hold-Up Time : 20 deciseconds
===============================================================================
*A:mlstp-dutA# show router mpls mpls-tp protection-template
===============================================================================

OAM Overview
MPLS-TP Protection Templates

===============================================================================
Template Name : privatebed-protection-template Router ID : 1
Protection Mode: one2one Direction : bidirectional
Revertive : revertive Wait-to-Restore: 300sec
Rapid-PSC-Timer: 10ms Slow-PSC-Timer : 5sec
===============================================================================
*A:mlstp-dutA# show router mpls mpls-tp status
===============================================================================
MPLS-TP Status
===============================================================================
Admin Status : Up
Global ID : 42 Node ID : 0.0.3.233
Tunnel Id Min : 1 Tunnel Id Max : 4096
===============================================================================
*A:mlstp-dutA# show router mpls mpls-tp transit-path
- transit-path [<path-name>] [detail]
<path-name> : [32 chars max]

A:mplstp-dutC# show router mpls mpls-tp transit-path

- transit-path [<path-name>] [detail]
<path-name> : [32 chars max]

A:mplstp-dutC# show router mpls mpls-tp transit-path

<path-name>
"tp-32" "tp-33" "tp-34" "tp-35" "tp-36" "tp-37" "tp-38" "tp-39"
"tp-40" "tp-41"
detail
A:mplstp-dutC# show router mpls mpls-tp transit-path "tp-32"
===============================================================================
MPLS-TP Transit tp-32 Path Information
===============================================================================
Path Name : tp-32
------------------------------------------------------------------
Path NextHop InLabel OutLabel Out I/F
------------------------------------------------------------------
FP 2080 2081 CtoB_1
RP 2081 2080 CtoA_1
===============================================================================
A:mplstp-dutC# show router mpls mpls-tp transit-path "tp-32" detail
===============================================================================
MPLS-TP Transit tp-32 Path Information (Detail)
===============================================================================
Path Name : tp-32

OAM and SAA

-------------------------------------------------------------------------------
Path ID configuration
Src Global ID : 42 Dst Global ID : 42
Src Node ID : 0.0.3.234 Dst Node ID : 0.0.3.233
LSP Number : 2 Dst Tunnel Num: 32
Forward Path configuration

Out Interface : CtoB_1 Next Hop Addr : n/a
Reverse Path configuration

Out Interface : CtoA_1 Next Hop Addr : n/a
===============================================================================
A:mplstp-dutC#
MPLS-TP Interfaces
The existing show>router>interface command should be enhanced to display mpls-tp specific
information.
The following is a sample output:
*A:mlstp-dutA# show router interface "AtoB_1"
===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
AtoB_1 Down Down/-- Network 1/2/3:1
Unnumbered If[system] n/a
-------------------------------------------------------------------------------
Interfaces : 1
Services using MPLS-TP PWs

The show>service command should be updated to display MPLS-TP specific information such as
the PW Path ID and control channel status signaling parameters.
*A:mlstp-dutA# show service id 1 all
===============================================================================
Service Detailed Information
===============================================================================
Service Id : 1 Vpn Id : 0

OAM Overview
Service Type : Epipe

Name : (Not Specified)
Customer Id : 1 Creation Origin : manual
Last Status Change: 12/03/2012 15:26:20
Last Mgmt Change : 12/03/2012 15:24:57
MTU : 1514
Vc Switching : False
SAP Count : 1 SDP Bind Count : 1
Per Svc Hashing : Disabled
Force QTag Fwd : Disabled
-------------------------------------------------------------------------------
ETH-CFM service specifics
-------------------------------------------------------------------------------
Tunnel Faults : ignore
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Sdp Id 32:1 -(0.0.3.234:42)
-------------------------------------------------------------------------------
SDP Id : 32:1 Type : Spoke
Spoke Descr : (Not Specified)
VC Type : Ether VC Tag : n/a
Admin Path MTU : 0 Oper Path MTU : 9186
Delivery : MPLS
Far End : 0.0.3.234:42
Tunnel Far End : n/a LSP Types : MPLSTP
Hash Label : Disabled Hash Lbl Sig Cap : Disabled
Oper Hash Label : Disabled

Acct. Pol : None Collect Stats : Disabled
Ingress Label : 16416 Egress Label : 16416
Ingr Mac Fltr-Id : n/a Egr Mac Fltr-Id : n/a
Ingr IP Fltr-Id : n/a Egr IP Fltr-Id : n/a
Ingr IPv6 Fltr-Id : n/a Egr IPv6 Fltr-Id : n/a
Admin ControlWord : Preferred Oper ControlWord : True
Admin BW(Kbps) : 0 Oper BW(Kbps) : 0
Last Status Change : 12/03/2012 15:26:20 Signaling : None
Last Mgmt Change : 12/03/2012 15:24:57 Force Vlan-Vc : Disabled
Endpoint : N/A Precedence : 4
PW Status Sig : Enabled
Class Fwding State : Down
Flags : None
Local Pw Bits : None
Peer Pw Bits : None
Peer Fault Ip : None
Peer Vccv CV Bits : None
Peer Vccv CC Bits : None
Application Profile: None
Standby Sig Slave : False
Block On Peer Fault: False

OAM and SAA
Ingress Qos Policy : (none) Egress Qos Policy : (none)

Ingress FP QGrp : (none) Egress Port QGrp : (none)
Ing FP QGrp Inst : (none) Egr Port QGrp Inst: (none)
Statistics :
I. Fwd. Pkts. : 272969957 I. Dro. Pkts. : 0
E. Fwd. Pkts. : 273017433 E. Fwd. Octets : 16381033352
-------------------------------------------------------------------------------
Control Channel Status
-------------------------------------------------------------------------------
PW Status : enabled Refresh Timer : 66 secs
Peer Status Expire : false Clear On Timeout : true
-------------------------------------------------------------------------------
SDP-BIND PW Path Information
-------------------------------------------------------------------------------
AGI : 1:1
SAII Type2 : 42:0.0.3.234:1
TAII Type2 : 42:0.0.3.233:1
-------------------------------------------------------------------------------
RSVP/Static LSPs
-------------------------------------------------------------------------------
Associated LSP List :
Lsp Name : lsp-32
*A:mlstp-dutA# show service id [1..4] all | match "Control Channel" pre-lines 1 post-lines
5
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
*A:mlstp-dutA# show service id [1..4] all | match SDP-BIND pre-lines 1 post-lines 5

OAM Overview
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
AGI : 1:1
SAII Type2 : 42:0.0.3.234:1
TAII Type2 : 42:0.0.3.233:1
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
AGI : 1:2
SAII Type2 : 42:0.0.3.234:2
TAII Type2 : 42:0.0.3.233:2
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
AGI : 1:3
SAII Type2 : 42:0.0.3.234:3
TAII Type2 : 42:0.0.3.233:3
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
AGI : 1:4
SAII Type2 : 42:0.0.3.234:4
TAII Type2 : 42:0.0.3.233:4
MPLS-TP DEBUG COMMANDS

The following command provides the debug command for an MPLS-TP tunnel:
tools>dump>router>mpls>tp-tunnel <lsp-name> [clear]
A:mlstp-dutA# tools dump router mpls tp-tunnel

- tp-tunnel <lsp-name> [clear]
- tp-tunnel id <tunnel-id> [clear]
<lsp-name> : [32 chars max]
<tunnel-id> : [1..61440]
<clear> : keyword - clear stats after reading
*A:mlstp-dutA# tools dump router mpls tp-tunnel "lsp-
"lsp-40" "lsp-41"
*A:mlstp-dutA# tools dump router mpls tp-tunnel "lsp-32"
Idx: 1-32 (Up/Up): pgId 4, paths 2, operChg 1, Active: Protect
TunnelId: 42::0.0.3.233::32-42::0.0.3.234::32
PgState: Dn, Cnt/Tm: Dn 1/000 04:00:48.160 Up:3/000 00:01:25.840
MplsMsg: tpDn 0/000 00:00:00.000, tunDn 0/000 00:00:00.000
wpDn 0/000 00:00:00.000, ppDn 0/000 00:00:00.000
wpDel 0/000 00:00:00.000, ppDel 0/000 00:00:00.000
tunUp 1/000 00:00:02.070
Paths:
Work (Up/Dn): Lsp 1, Lbl 32/32, If 2/128 (1/2/3 : 0.0.0.0)

OAM and SAA
Tmpl: ptc: , oam: privatebed-oam-template (bfd: privatebed-bfd-template(np)-10 ms)

Bfd: Mode CC state Dn/Up handle 160005/0
Bfd-CC (Cnt/Tm): Dn 1/000 04:00:48.160 Up:1/000 00:01:23.970
State: Admin Up (1::1::1) port Up , if Dn , operChg 2
DnReasons: ccFault ifDn
Protect (Up/Up): Lsp 2, Lbl 2080/2080, If 3/127 (5/1/1 : 0.0.0.0)
Tmpl: ptc: privatebed-protection-template, oam: privatebed-oam-template (bfd: privatebed-
bfd-template(np)-10 ms)
Bfd: Mode CC state Up/Up handle 160006/0
Bfd-CC (Cnt/Tm): Dn 0/000 00:00:00.000 Up:1/000 00:01:25.410
State: Admin Up (1::1::1) port Up , if Up , operChg 1
Aps: Rx - 5, raw 3616, nok 0(), txRaw - 3636, revert Y
Pdu: Rx - 0x1a-21::0101 (SF), Tx - 0x1a-21::0101 (SF)
State: PF:W:L LastEvt pdu (L-SFw/R-SFw)
Tmrs: slow
Defects: None Now: 000 05:02:19.130
Seq Event state TxPdu RxPdu Dir Act Time
=== ====== ======== ========== ========== ===== ==== ================
000 start UA:P:L SF (0,0) NR (0,0) Tx--> Work 000 00:00:02.080
001 pdu UA:P:L SF (0,0) SF (0,0) Rx<-- Work 000 00:01:24.860
002 pdu UA:P:L SF (0,0) NR (0,0) Rx<-- Work 000 00:01:26.860
003 pUp NR NR (0,0) NR (0,0) Tx--> Work 000 00:01:27.440
004 pdu NR NR (0,0) NR (0,0) Rx<-- Work 000 00:01:28.760
005 wDn PF:W:L SF (1,1) NR (0,0) Tx--> Prot 000 04:00:48.160
006 pdu PF:W:L SF (1,1) NR (0,1) Rx<-- Prot 000 04:00:48.160
007 pdu PF:W:L SF (1,1) SF (1,1) Rx<-- Prot 000 04:00:51.080
The following command shows the free MPLS tunnel ID’s
A:SASR1# /tools dump router mpls mpls-tp check-lbl-range

- mpls-tp check-lbl-range <range1> <range2>
<check-lbl-range> : keyword
<range1> : [32..65520]
<range2> : [32..65520]
The following command provides a debug tool to view control-channel-status signaling packets.
*A:7210SAS# /debug service id 700 sdp 200:700 event-type ?{config-change|oper-status-

change|neighbor-discovery|control-channel-status}
*A:7210SAS# /debug service id 700 sdp 200:700 event-type control-channel-status
*A:7210SAS#
1 2012/08/31 09:56:12.09 EST MINOR: DEBUG #2001 Base PW STATUS SIG PKT (RX):
"PW STATUS SIG PKT (RX)::
Sdp Bind 200:700 Instance 3
Version : 0x0
PW OAM Msg Type : 0x27
Refresh Time : 0xa
Total TLV Length : 0x8
Flags : 0x0
TLV Type : 0x96a
TLV Len : 0x4
PW Status Bits : 0x0
"
2 2012/08/31 09:56:22.09 EST MINOR: DEBUG #2001 Base PW STATUS SIG PKT (RX):

OAM Overview
"PW STATUS SIG PKT (RX)::

Version : 0x0
Refresh Time : 0xa
Flags : 0x0
TLV Type : 0x96a
TLV Len : 0x4
"
3 2012/08/31 09:56:29.44 EST MINOR: DEBUG #2001 Base PW STATUS SIG PKT (TX):
"PW STATUS SIG PKT (TX)::
Version : 0x0
Refresh Time : 0x1e
Flags : 0x0
TLV Type : 0x96a
TLV Len : 0x4

OAM and SAA
Ethernet Connectivity Fault Management (ETH-CFM)

The IEEE and the ITU-T have cooperated to define the protocols, procedures and managed objects
to support service based fault management. Both IEEE 802.1ag standard and the ITU-T
Y.1731recommendation support a common set of tools that allow operators to deploy the
necessary administrative constructs, management entities and functionality, Ethernet Connectivity
Fault Management (ETH-CFM). The ITU-T has also implemented a set of advanced ETH-CFM
and performance management functions and features that build on the proactive and on demand
troubleshooting tools.
CFM uses Ethernet frames and is distinguishable by ether-type 0x8902. In certain cases the
different functions will use a reserved multicast address that could also be used to identify specific
functions at the MAC layer. However, the multicast MAC addressing is not used for every
function or in every case. The Operational Code (OpCode) in the common CFM header is used to
identify the type of function carried in the CFM packet. CFM frames are only processed by IEEE
MAC bridges. With CFM, interoperability can be achieved between different vendor equipment in
the service provider network upto and including customer premises bridges. The following table
lists CFM-related acronyms used in this section.
IEEE 802.1ag and ITU-T Y.1731 functions that are implemented are available on the 7210 SAS
platforms.
Acronym Callout
1DM One way Delay Measurement (Y.1731)

AIS Alarm Indication Signal
CCM Continuity check message
CFM Connectivity fault management
DMM Delay Measurement Message (Y.1731)
DMR Delay Measurement Reply (Y.1731)
LBM Loopback message
LBR Loopback reply
LTM Linktrace message
LTR Linktrace reply
ME Maintenance entity
MA Maintenance association

Acronym Callout (Continued)
MA-ID Maintenance association identifier

MD Maintenance domain
MEP Maintenance association end point
MEP-ID Maintenance association end point identifier
MHF MIP half function
MIP Maintenance domain intermediate point
OpCode Operational Code
RDI Remote Defect Indication
TST Ethernet Test (Y.1731)

OAM and SAA
ETH-CFM Building Blocks

The IEEE and the ITU-T use their own nomenclature when describing administrative contexts and
functions. This introduces a level of complexity to configuration, discussion and different vendors
naming conventions. The 7210 SAS OS CLI has chosen to standardize on the IEEE 802.1ag
naming where overlap exists. ITU-T naming is used when no equivalent is available in the IEEE
standard. In the following definitions, both the IEEE name and ITU-T names are provided for
completeness, using the format IEEE Name/ITU-T Name.
Maintenance Domain (MD)/Maintenance Entity (ME) is the administrative container that defines
the scope, reach and boundary for faults. It is typically the area of ownership and management
responsibility. The IEEE allows for various formats to name the domain, allowing upto 45
characters, depending on the format selected. ITU-T supports only a format of “none” and does
not accept the IEEE naming conventions.
0 — Undefined and reserved by the IEEE.

1 — No domain name. It is the only format supported by Y.1731 as the ITU-T
specification does not use the domain name. This is supported in the IEEE 802.1ag
standard but not in currently implemented for 802.1ag defined contexts.
2,3,4 — Provides the ability to input various different textual formats, upto 45 characters.
The string format (2) is the default and therefore the keyword is not shown when looking
at the configuration.
Maintenance Association (MA)/Maintenance Entity Group (MEG) is the construct where the
different management entities will be contained. Each MA is uniquely identified by its MA-ID.
The MA-ID is comprised of the by the MD level and MA name and associated format. This is
another administrative context where the linkage is made between the domain and the service
using the bridging-identifier configuration option. The IEEE and the ITU-T use their own
specific formats. The MA short name formats (0-255) have been divided between the IEEE (0-31,
64-255) and the ITU-T (32-63), with five currently defined (1-4, 32). Even though the different
standards bodies do not have specific support for the others formats a Y.1731 context can be
configured using the IEEE format options.
1 (Primary VID) — Values 0 — 4094

2 (String) — Raw ASCII, excluding 0-31 decimal/0-1F hex (which are control characters)
form the ASCII table
3 (2-octet integer) — 0 — 65535
4 (VPN ID) — Hex value as described in RFC 2685, Virtual Private Networks Identifier
32 (icc-format) — Exactly 13 characters from the ITU-T recommendation T.50.
Note: When a VID is used as the short MA name, 802.1ag will not support VLAN translation
because the MA-ID must match all the MEPs. The default format for a short MA name is an

integer. Integer value 0 means the MA is not attached to a VID. This is useful for VPLS services
on 7210 SAS platforms because the VID is locally significant.
Maintenance Domain Level (MD Level)/Maintenance Entity Group Level (MEG Level) is the
numerical value (0-7) representing the width of the domain. The wider the domain, higher the
numerical value, the farther the ETH-CFM packets can travel. It is important to understand that the
level establishes the processing boundary for the packets. Strict rules control the flow of ETH-
CFM packets and are used to ensure proper handling, forwarding, processing and dropping of
these packets. To keep it simple ETH-CFM packets with higher numerical level values will flow
through MEPs on MIPs on SAPs configured with lower level values. This allows the operator to
implement different areas of responsibility and nest domains within each other. Maintenance
association (MA) includes a set of MEPs, each configured with the same MA-ID and MD level
used verify the integrity of a single service instance.
Maintenance Endpoint (MEP)/MEG Endpoint (MEP) are the workhorses of ETH-CFM. A MEP is
the unique identification within the association (0-8191). Each MEP is uniquely identified by the
MA-ID, MEPID tuple. This management entity is responsible for initiating, processing and
terminating ETH-CFM functions, following the nesting rules. MEPs form the boundaries which
prevent the ETH-CFM packets from flowing beyond the specific scope of responsibility. A MEP
has direction, up or down. Each indicates the directions packets will be generated; UP toward the
switch fabric, down toward the SAP away from the fabric. Each MEP has an active and passive
side. Packets that enter the active point of the MEP will be compared to the existing level and
processed accordingly. Packets that enter the passive side of the MEP are passed transparently
through the MEP. Each MEP contained within the same maintenance association and with the
same level (MA-ID) represents points within a single service. MEP creation on a SAP is allowed
only for Ethernet ports with NULL, q-tags, q-in-q encapsulations. MEPs may also be created on
SDP bindings.
Maintenance Intermediate Point (MIP)/MEG Intermediate Point (MIP) are management entities
between the terminating MEPs along the service path. These provide insight into the service path
connecting the MEPs. MIPs only respond to Loopback Messages (LBM) and Linktrace Messages
(LTM). All other CFM functions are transparent to these entities. Only one MIP is allowed per
SAP or SDP. The creation of the MIPs can be done when the lower level domain is created
(explicit). This is controlled by the use of the mhf-creation mode within the association under the
bridge-identifier. MIP creation is supported on a SAP and SDP, not including Mesh SDP bindings.
By default, no MIPs are created.
NOTE: The 7210 SAS platforms supports either only Ingress MIPs in some services or bi-
directional MIPs (that is, ingress and egress MIPs) in some services. The table below lists the MIP
and MEP support for different services on different platforms.
There are two locations in the configuration where ETH-CFM is defined. The domains,
associations (including linkage to the service id), MIP creation method, common ETH-CFM

OAM and SAA
functions and remote MEPs are defined under the top level eth-cfm command. It is important to
note, when Y.1731 functions are required the context under which the MEPs are configured must
follow the Y.1731 specific formats (domain format of none, MA format icc-format). Once these
parameters have been entered, the MEP and possibly the MIP can be defined within the service
under the SAP or SDP.
This is a general table that indicates the ETH-CFM support for the different services and
endpoints. It is not meant to indicate the services that are supported or the requirements for those
services on the individual platforms.
Table 4: ETH-CFM Support Matrix for 7210 SAS-M Network Mode
Service Ethernet Down MEP UP MEP MIP

Connection
Type
Epipe SAP Yes Yes Ingress MIP and

Egress MIP
SDP Yes Yes Ingress MIP and
Egress MIP
VPLS SAP Yes Yes Ingress MIP
only
Spoke-SDP Yes Yes Ingress MIP
only
Mesh-SDP Yes Yes Not supported
RVPLS SAP Not Supported Not Supported Not Supported
IES IPv4 Not Supported Not Supported Not Supported
interface
PBB Epipe I-SAP Not Supported Yes Not Supported
PBB VPLS I-SAP Not Supported Not Supported Not Supported
PBB B-VPLS B-SAP Not Supported Not Supported Not Supported
IES SAP Not Supported Not Supported Not Supported
VPRN SAP Not Supported Not Supported Not Supported
Table 5: ETH-CFM Support Matrix for 7210 SAS-M Access-Uplink Mode


Connection
Type
Epipe SAP (Access Yes Yes Ingress MIP and

and Access- Egress MIP
uplink SAP)
VPLS SAP (Access Yes Yes Ingress MIP and
uplink SAP)
interface
IES SAP Not Supported Not Supported Not supported
Table 6: ETH-CFM Support Matrix for 7210 SAS-T Access-Uplink Mode

Connection
Type
Epipe SAP (Access Yes Yes Ingress MIP and

uplink SAP)
VPLS SAP (Access Yes Yes Ingress MIP
and Access- only
uplink SAP)
interface
IES SAP Not Supported Not Supported Not supported

OAM and SAA
Table 7: ETH-CFM Support Matrix for 7210 SAS-T Network Mode

Connection
Type

Egress MIP
Egress MIP
only
Spoke-SDP Yes Yes Ingress MIP
only
interface
Table 8: ETH-CFM Support Matrix for 7210 SAS-X

Connection
Type

Egress MIP
Egress MIP

Table 8: ETH-CFM Support Matrix for 7210 SAS-X

only
Spoke-SDP Yes Yes Not Supported
interface

OAM and SAA
Table 9: ETH-CFM Support Matrix for 7210 SAS-R6 devices

Connection
Type

Egress MIP
Egress MIP
VPLS SAP Yes Not Supported Ingress MIP
only
Spoke-SDP Yes Not Supported Ingress MIP
only
Mesh-SDP Not Supported Not Supported Ingress MIP
only
interface
PBB Epipe I-SAP Not Supported Not Supported Not Supported
Notes:
• Ethernet-Rings are not configurable under all service types. Any service restrictions for
MEP direction or MIP support overrides the generic capability of the Ethernet-Tunnel or
Ethernet-Ring MPs. For more information on G.8032 Ethernet-rings, see 7210 SAS
Services Guide.
• An Ingress MIP or a Down MIP refers to an unidirectional MIP. In 7210, MIP (excluding
MIPs under epipe in SAS-M network mode and SAS-X) is uni-directional in that only
CFM OAM packets received in the ingress direction is processed. MIP under Epipe in
7210 SAS-M, 7210 SAS-T (network mode and access-uplink mode), and SAS-X is
bidirectional, and responds to CFM OAM packets received in both ingress and egress
directions.

• On 7210 SAS-M, 7210 SAS-T (network mode and access-uplink mode), and SAS-X,
when two bidirectional MIPs are configured in an Epipe service on both the service
entities/endpoints (For example: on both the SAP and the SDP configured in the Epipe
service), only the MIP ingressing to the direction of linktrace messages responds.
MIP10 MEP3 MA2
MIP1 MIP2 MIP3 MIP4 MIP5 MIP6 MIP7 MIP8

MEP1 MEP4
MIP11
MA1 Bridge
Port
MEP2 MIP12
MIP
MEP
Figure 10: MEP and MIP
Figure 11 shows the detailed IEEE representation of MEPs, MIPs, levels and associations, using
the standards defined icons.

OAM and SAA
CE Operator A Provider Bridges Operator B Provider Bridges CE

1 2 3 4 5 6
p b d e g q
5 Customer MD Level 5
5 5
5 5
Service Provider MD Level
3 3
3 3
3 3
Operator MD level
2 2 2 2
2 2 2 2
2 2 2 2
0 0 0 0
MD Physical Level
Bridge with two

5 Down MEP 2 Up MEP
Bridge Ports
2 Maintenance Logical path
MIP
2 Asscociation of CFM PDUs
Figure 11: MEP, MIP and MD Levels

Loopback
A loopback message is generated by an MEP to its peer MEP (Figure 12). The functions are
similar to an IP ping to verify Ethernet connectivity between the nodes.
MIP10 MEP3
Loopback
Messages

MEP1 MEP4
Loopback MIP11
Reply Messages Bridge
Port
MEP2 MIP12
MIP
MEP
Figure 12: CFM Loopback
The following loopback-related functions are supported:
• Loopback message functionality on an MEP or MIP can be enabled or disabled.

• MEP — Supports generating loopback messages and responding to loopback messages
with loopback reply messages.
• MIP — Supports responding to loopback messages with loopback reply messages when
loopback messages are targeted to self.
• Displays the loopback test results on the originating MEP. There is a limit of ten
outstanding tests per node.

OAM and SAA
Linktrace
A linktrace message is originated by an MEP and targeted to a peer MEP in the same MA and
within the same MD level (Figure 13). Its function is similar to IP traceroute. Traces a specific
MAC address through the service. The peer MEP responds with a linktrace reply message after
successful inspection of the linktrace message. The MIPs along the path also process the linktrace
message and respond with linktrace replies to the originating MEP if the received linktrace
message that has a TTL greater than 1 and forward the linktrace message if a look up of the target
MAC address in the Layer 2 FIB is successful. The originating MEP shall expect to receive
multiple linktrace replies and from processing the linktrace replies, it can put together the route to
the target bridge.
A traced MAC address is carried in the payload of the linktrace message, the target MAC. Each
MIP and MEP receiving the linktrace message checks whether it has learned the target MAC
address. In order to use linktrace the target MAC address must have been learned by the nodes in
the network. If so, a linktrace message is sent back to the originating MEP. Also, a MIP forwards
the linktrace message out of the port where the target MAC address was learned.
The linktrace message itself has a multicast destination address. On a broadcast LAN, it can be
received by multiple nodes connected to that LAN. But, at most, one node will send a reply.
MIP10 MEP3
Linktrace Request
Messages
MEP1 MIP2 MIP3 MIP4 MIP5 MIP6 MIP7 MIP8
MEP1 MEP4
MEP11
Bridge
Linktrace Reply
Port
Messages to MEP2 MIP12
MIP1 MIP
MEP
Fig_13
Figure 13: CFM Linktrace
The following linktrace related functions are supported:
• Enable or disables linktrace functions on an MEP.

• MEP — Supports generating linktrace messages and responding with linktrace reply
messages.
• MIP — Supports responding to linktrace messages with linktrace reply messages when
encoded TTL is greater than 1, and forward the linktrace messages accordingly if a lookup
of the target MAC address in the Layer 2 FIB is successful.
• Displays linktrace test results on the originating MEP. There is a limit of ten outstanding
tests per node. Storage is provided for upto ten MEPs and for the last ten responses. If
more than ten responses are received older entries will be overwritten.

OAM and SAA
Continuity Check (CC)

A Continuity Check Message (CCM) is a multicast frame that is generated by a MEP and
multicast to all other MEPs in the same MA. The CCM does not require a reply message. To
identify faults, the receiving MEP maintains an internal list of remote MEPs it should be receiving
CCM messages from.
This list is based off of the remote-mepid configuration within the association the MEP is created
in. When the local MEP does not receive a CCM from one of the configured remote MEPs within
a pre-configured period, the local MEP raises an alarm.
MIP10 MEP3

MEP1 MEP4
MIP12
Bridge
Port
MEP2 MIP12
MIP
MEP
Figure 14: CFM Continuity Check
MIP10 MEP3
NMS Fault NMS

MEP1 MEP4
MIP11
Bridge
Port
MEP2 MIP12
MIP
MEP
Figure 15: CFM CC Failure Scenario

The following functions are supported:
• Enable and disable CC for an MEP

• Configure and delete the MEP entries in the CC MEP monitoring database manually. It is
only required to provision remote MEPs. Local MEPs shall be automatically put into the
database when they are created.
• CCM transmit interval: 100ms (Supported only on 7210 SAS-M and 7210 SAS-T
devices),1s,10s,60s and 600s. Default: 10s. .
When configuring MEPs with sub-second CCM intervals bandwidth consumption must be
taken into consideration. Each CCM PDU is 100 bytes (800 bits). Taken individually this
is a small value. However, the bandwidth consumption increases rapidly as multiple
MEPs are configured with 10ms timers, 100 packets per second. Sub-second enabled
MEPs are supported on the following:
→ Down MEPs configured on Ethernet SAPs.

→ 210 SAS-M can have sub-second CCM configured on SDP.
→ Lowest MD-level, when multiple MEPs exist on same Ethernet SAP.
→ 7210 SAS-M can have multiple MEPs with sub-second intervals on the same SAP.
• CCM will declare a fault, when:
→ The CCM stops hearing from one of the remote MEPs for 3.5 times CC interval
→ Hears from a MEP with a LOWER MD level
→ Hears from a MEP that is not part of the local MEPs MA
→ Hears from a MEP that is in the same MA but not in the configured MEP list
→ Hears from a MEP in the same MA with the same MEP id as the receiving MEP
→ The CC interval of the remote MEP does not match the local configured CC interval
→ The remote MEP is declaring a fault
• An alarm is raised and a trap is sent if the defect is greater than or equal to the configured
low-priority-defect value.
• Remote Defect Indication (RDI) is supported but by default is not recognized as a defect
condition because the low-priority-defect setting default does not include RDI.

OAM and SAA
Alarm Indication Signal (ETH-AIS Y.1731)

Alarm Indication Signal (AIS) provides an Y.1731 capable MEP the ability to signal a fault
condition in the reverse direction of the MEP, out the passive side. When a fault condition is
detected the MEP will generate AIS packets at the configured client levels and at the specified AIS
interval until the condition is cleared. Currently a MEP configured to generate AIS must do so at a
level higher than its own. The MEP configured on the service receiving the AIS packets is
required to have the active side facing the receipt of the AIS packet and must be at the same level
the AIS, The absence of an AIS packet for 3.5 times the AIS interval set by the sending node will
clear the condition on the receiving MEP.
It is important to note that AIS generation is not supported to an explicitly configured endpoint.
An explicitly configured endpoint is an object that contains multiple individual endpoints, as in
PW redundancy.
Test (ETH-TST Y.1731)

Ethernet test affords operators an Y.1731 capable MEP the ability to send an in service on demand
function to test connectivity between two MEPs. The test is generated on the local MEP and the
results are verified on the destination MEP. Any ETH-TST packet generated that exceeds the
MTU will be silently dropped by the lower level processing of the node.
Y.1731 Time Stamp Capability

Accurate results for one-way and two-way delay measurement tests using Y.1731 messages are
obtained if the nodes are capable of time stamping packets in hardware.
• The 7210 SAS-M and 7210 SAS-X support is as follows:

→ Y.1731 2-DM messages for both Down MEPs and UP MEPs, 1-DM for both Down
MEPs and UP MEPs, and 2-SLM for both Down MEPs and UP MEPs use software
based timestamps on Tx and hardware based timestamp on Rx. It uses the system
clock (free-running or synchronized to NTP) to obtain the timestamps.

• The 7210 SAS-T support is as follows:

→ Y.1731 2-DM messages for Down MEPs uses hardware timestamps for both Rx
(packets received by the node) and Tx (packets sent out of the node). The timestamps
is obtained from a free-running hardware clock. It provides accurate 2-way delay
measurements and it is not recommended to use it for computing 1-way delay.
→ Y.1731 2-DM messages for UP MEPs, 1-DM for both Down MEPs and UP MEPs,
and 2-SLM for both Down MEPs and UP MEPs use software based timestamps on Tx
and hardware based timestamp on Rx. The timestamps are obtained as given below:
• From NTP, when NTP is enabled and PTP is disabled
• From PTP, when PTP is enabled (irrespective of whether NTP is disabled or
enabled)
• From free-running system time, when both NTP and PTP are disabled.
NOTE: After PTP is enabled once, if the user needs to go back to NTP time
scale, or system free-run time scale, a node reboot is required.

OAM and SAA

Synthetic Loss Measurement (ETH-SL)

Alcatel-Lucent applied pre-standard OpCodes 53 (Synthetic Loss Reply) and 54 (Synthetic Loss
Message) for the purpose of measuring loss using synthetic packets.
Notes: These will be changes to the assigned standard values in a future release. This means that
the Release 4.0R6 is pre-standard and will not interoperate with future releases of SLM or SLR
that supports the standard OpCode values.
This synthetic loss measurement approach is a single-ended feature that allows the operator to run
on-demand and proactive tests to determine “in”, “out” loss and “unacknowledged” packets. This
approach can be used between peer MEPs in both point to point and multipoint services. Only
remote MEP peers within the association and matching the unicast destination will respond to the
SLM packet.
The specification uses various sequence numbers in order to determine in which direction the loss
occurred. Alcatel-Lucent has implemented the required counters to determine loss in each
direction. In order to properly use the information that is gathered the following terms are defined;
• Count — The number of probes that are sent when the last frame is not lost. When the last
frame(s) is or are lost, the count and unacknowledged equals the number of probes sent.
• Out-Loss (Far-end) — Packets lost on the way to the remote node, from test initiator to the
test destination.
• In-Loss (Near-end) — Packet loss on the way back from the remote node to the test
initiator.
• Unacknowledged — Number of packets at the end of the test that were not responded to.
The per probe specific loss indicators are available when looking at the on-demand test runs, or the
individual probe information stored in the MIB. When tests are scheduled by Service Assurance
Application (SAA) the per probe data is summarized and per probe information is not maintained.
Any “unacknowledged” packets will be recorded as “in-loss” when summarized.
The on-demand function can be executed from CLI or SNMP. The on demand tests are meant to
provide the carrier a way to perform on the spot testing. However, this approach is not meant as a
method for storing archived data for later processing. The probe count for on demand SLM has a
range of one to 100 with configurable probe spacing between one second and ten seconds. This
means it is possible that a single test run can be upto 1000 seconds in length. Although possible, it
is more likely the majority of on demand case can increase to 100 probes or less at a one second
interval. A node may only initiate and maintain a single active on demand SLM test at any given
time. A maximum of one storage entry per remote MEP is maintained in the results table.
Subsequent runs to the same peer can overwrite the results for that peer. This means, when using
on demand testing the test should be run and the results checked prior to starting another test.
The proactive measurement functions are linked to SAA. This backend provides the
scheduling,storage and summarization capabilities. Scheduling may be either continuous or

OAM and SAA
periodic. It also allows for the interpretation and representation of data that may enhance the
specification. As an example, an optional TVL has been included to allow for the measurement of
both loss and delay or jitter with a single test. The implementation does not cause any
interoperability because the optional TVL is ignored by equipment that does not support this. In
mixed vendor environments loss measurement continues to be tracked but delay and jitter can only
report round trip times. It is important to point out that the round trip times in this mixed vendor
environments include the remote nodes processing time because only two time stamps will be
included in the packet. In an environment where both nodes support the optional TLV to include
time stamps unidirectional and round trip times is reported. Since all four time stamps are included
in the packet the round trip time in this case does not include remote node processing time. Of
course, those operators that wish to run delay measurement and loss measurement at different
frequencies are free to run both ETH-SL and ETH-DM functions. ETH-SL is not replacing ETH-
DM. Service Assurance is only briefly discussed here to provide some background on the basic
functionality. To know more about SAA functions see Service Assurance Agent Overview on page
136.
The ETH-SL packet format contains a test-id that is internally generated and not configurable. The
test-id is visible for the on demand test in the display summary. It is possible for a remote node
processing the SLM frames receives overlapping test-ids as a result of multiple MEPs measuring
loss between the same remote MEP. For this reason, the uniqueness of the test is based on remote
MEP-ID, test-id and Source MAC of the packet.
ETH-SL is applicable to up and down MEPs and as per the recommendation transparent to MIPs.
There is no coordination between various fault conditions that could impact loss measurement.
This is also true for conditions where MEPs are placed in shutdown state as a result of linkage to a
redundancy scheme like MC-LAG. Loss measurement is based on the ETH-SL and not
coordinated across different functional aspects on the network element. ETH-SL is supported on
service based MEPs.
It is possible that two MEPs may be configured with the same MAC on different remote nodes.
This causes various issues in the FDB for multipoint services and is considered a misconfiguration
for most services. It is possible to have a valid configuration where multiple MEPs on the same
remote node have the same MAC. In fact, this is likely to happen. In this release, only the first
responder is used to measure packet loss. The second responder is dropped. Since the same MAC
for multiple MEPs is only truly valid on the same remote node this should is an acceptable
approach
There is no way for the responding node to understand when a test is completed. For this reason a
configurable “inactivity-timer” determines the length of time a test is valid. The timer will
maintain an active test as long as it is receiving packets for that specific test, defined by the test-id,
remote MEP Id and source MAC. When there is a gap between the packets that exceeds the
inactivity-timer the responding node responds with a sequence number of one regardless of what
the sequence number was the instantiating node sent. This means the remote MEP accepts that the
previous test has expired and these probes are part of a new test. The default for the inactivity
timer is 100 second and has a range of 10 to 100 seconds.

The responding node is limited to a fixed number of SLM tests per platform. Any test that attempts
to involve a node that is already actively processing more than the system limit of the SLM tests
shows up as “out loss” or “unacknowledged” packets on the node that instantiated the test because
the packets are silently discarded at the responder. It is important for the operator to understand
this is silent and no log entries or alarms is raised. It is also important to keep in mind that these
packets are ETH-CFM based and the different platforms stated receive rate for ETH-CFM must
not be exceeded. ETH-SL provides a mechanism for operators to pro-actively trend packet loss for
service based MEPs.
Configuration Example
The following illustration, shows the configuration required for proactive SLM test using SAA.
Figure 16: SLM Example
The output from the MIB is shown below as an example of an on-demand test. Node1 is tested for
this example. The SAA configuration does not include the accounting policy required to collect
the statistics before they are overwritten. NODE2 does not have an SAA configuration. NODE2
includes the configuration to build the MEP in the VPLS service context.
config>eth-cfm# info
----------------------------------------------
domain 3 format none level 3
association 1 format icc-based name "03-0000000100"
bridge-identifier 100
exit
ccm-interval 1
remote-mepid 101
exit
exit
----------------------------------------------
*A:7210SAS>config>service>vpls# info
----------------------------------------------
stp
shutdown

OAM and SAA
exit
sap 1/1/3:100.100 create
exit
sap lag-1:100.100 create
eth-cfm
mep 100 domain 3 association 1 direction down
ccm-enable
mac-address d0:0d:1e:00:01:00
no shutdown
exit
exit
exit
no shutdown
----------------------------------------------
*A:7210SAS>config>service>vpls
*A:7210SAS>config>saa# info detail

----------------------------------------------
test "SLM" owner "TiMOS CLI"
no description
type
eth-cfm-two-way-slm 00:01:22:22:33:34 mep 1 domain 1 association 1 size 0
fc "nc" count 100 timeout 1 interval 1
exit
trap-gen
no probe-fail-enable
probe-fail-threshold 1
no test-completion-enable
no test-fail-enable
test-fail-threshold 1
exit
continuous
no shutdown
exit
----------------------------------------------
*A:7210SAS>config>saa#
The following sample output is meant to demonstrate the different loss conditions that an
operator may see. The total number of attempts is “100” is because the final probe in
the test was not acknowledged.
*A:7210SAS# show saa SLM42
===============================================================================
SAA Test Information
===============================================================================
Test name : SLM42
Owner name : TiMOS CLI
Description : N/A
Accounting policy : None
Continuous : Yes
Administrative status : Enabled
Test type : eth-cfm-two-way-slm 00:25:ba:02:a6:50 mep 4
domain 1 association 1 fc "h1" count 100
timeout 1 interval 1
Trap generation : None
Test runs since last clear : 117
Number of failed test runs : 1
Last test result : Success

-------------------------------------------------------------------------------
Threshold
Type Direction Threshold Value Last Event Run #
-------------------------------------------------------------------------------
Jitter-in Rising None None Never None
Falling None None Never None
Jitter-out Rising None None Never None
Jitter-rt Rising None None Never None
Latency-in Rising None None Never None
Latency-out Rising None None Never None
Latency-rt Rising None None Never None
Loss-in Rising None None Never None
Loss-out Rising None None Never None
Loss-rt Rising None None Never None
===============================================================================
Test Run: 116
Total number of attempts: 100
Number of requests that failed to be sent out: 0
Number of responses that were received: 100
Number of requests that did not receive any response: 0
Total number of failures: 0, Percentage: 0
(in ms) Min Max Average Jitter
Outbound : 8.07 8.18 8.10 0.014
Inbound : -7.84 -5.46 -7.77 0.016
Roundtrip : 0.245 2.65 0.334 0.025
Per test packet:
Sequence Outbound Inbound RoundTrip Result
1 8.12 -7.82 0.306 Response Received
===============================================================================
The following is an example of an on demand tests that and the associated output. Only
single test runs are stored and can be viewed after the fact.
#oam eth-cfm two-way-slm-test 00:25:ba:04:39:0c mep 4 domain 1 association 1 send-count
10 interval 1 timeout 1
Sending 10 packets to 00:25:ba:04:39:0c from MEP 4/1/1 (Test-id: 143

OAM and SAA
Sent 10 packets, 10 packets received from MEP ID 3, (Test-id: 143)

(0 out-loss, 0 in-loss, 0 unacknowledged)
*A:7210SAS>show# eth-cfm mep 4 domain 1 association 1 two-way-slm-test
===============================================================================
Eth CFM Two-way SLM Test Result Table (Test-id: 143)
===============================================================================
Peer Mac Addr Remote MEP Count In Loss Out Loss Unack
-------------------------------------------------------------------------------
00:25:ba:04:39:0c 3 10 0 0 0
===============================================================================
*A:7210SAS>show#

OAM Mapping
OAM Mapping
OAM mapping is a mechanism that enables a way of deploying OAM end-to-end in a network
where different OAM tools are used in different segments. For instance, an Epipe service could
span across the network using Ethernet access (CFM used for OAM), pseudowire (T-LDP status
signaling used for OAM), and Ethernet access (CFM used for OAM).
In the 7210 SAS implementation, the Service Manager (SMGR) is used as the central point of
OAM mapping. It receives and processes the events from different OAM components, then
decides the actions to take, including triggering OAM events to remote peers.
Fault propagation for CFM is by default disabled at the MEP level to maintain backward
compatibility. When required, it can be explicitly enabled by configuration.
Fault propagation for a MEP can only be enabled when the MA is comprised of no more than two
MEPs (point-to-point).
CFM Connectivity Fault Conditions

CFM MEP declares a connectivity fault when its defect flag is equal to or higher than its
configured lowest defect priority. The defect can be any of the following depending on
configuration:
• DefRDICCM
• DefMACstatus
• DefRemoteCCM
• DefErrorCCM
• DefXconCCM
The following additional fault condition applies to Y.1731 MEPs:
• Reception of AIS for the local MEP level
Setting the lowest defect priority to allDef may cause problems when fault propagation is enabled
in the MEP. In this scenario, when MEP A sends CCM to MEP B with interface status down, MEP
B will respond with a CCM with RDI set. If MEP A is configured to accept RDI as a fault, then it
gets into a dead lock state, where both MEPs will declare fault and never be able to recover. The
default lowest defect priority is DefMACstatus, which will not be a problem when interface status
TLV is used. It is also very important that different Ethernet OAM strategies should not overlap
the span of each other. In some cases, independent functions attempting to perform their normal
fault handling can negatively impact the other. This interaction can lead to fault propagation in the

OAM and SAA
direction toward the original fault, a false positive, or worse, a deadlock condition that may
require the operator to modify the configuration to escape the condition. For example, overlapping
Link Loss Forwarding (LLF) and ETH-CFM fault propagation could cause these issues.
For the DefRemoteCCM fault, it is raised when any remote MEP is down. So whenever a remote
MEP fails and fault propagation is enabled, a fault is propagated to SMGR.
CFM Fault Propagation Methods

When CFM is the OAM module at the other end, it is required to use any of the following methods
(depending on local configuration) to notify the remote peer:
• Generating AIS for certain MEP levels

• Sending CCM with interface status TLV “down”
• Stopping CCM transmission
NOTE: 7210 platforms expect that the fault notified using interface status TLV, is cleared
explicitly by the remote MEP when the fault is no longer present on the remote node. On 7210
SAS-M, use of CCM with interface status TLV Down is not recommended to be configured with a
Down MEP, unless it is known that the remote MEP clears the fault explicitly.
User can configure UP MEPs to use Interface Status TLV with fault propagation. Special
considerations apply only to Down MEPs.
When a fault is propagated by the service manager, if AIS is enabled on the SAP/SDP-binding,
then AIS messages are generated for all the MEPs configured on the SAP/SDP-binding using the
configured levels.
Note that the existing AIS procedure still applies even when fault propagation is disabled for the
service or the MEP. For example, when a MEP loses connectivity to a configured remote MEP, it
generates AIS if it is enabled. The new procedure that is defined in this document introduces a
new fault condition for AIS generation, fault propagated from SMGR, that is used when fault
propagation is enabled for the service and the MEP.
The transmission of CCM with interface status TLV must be done instantly without waiting for the
next CCM transmit interval. This rule applies to CFM fault notification for all services.
Notifications from SMGR to the CFM MEPs for fault propagation should include a direction for
the propagation (up or down: up means in the direction of coming into the SAP/SDP-binding;
down means in the direction of going out of the SAP/SDP-binding), so that the MEP knows what
method to use. For instance, an up fault propagation notification to a down MEP will trigger an

OAM Mapping
AIS, while a down fault propagation to the same MEP can trigger a CCM with interface TLV with
status down.
For a specific SAP/SDP-binding, CFM and SMGR can only propagate one single fault to each
other for each direction (up or down).
When there are multiple MEPs (at different levels) on a single SAP/SDP-binding, the fault
reported from CFM to SMGR will be the logical OR of results from all MEPs. Basically, the first
fault from any MEP will be reported, and the fault will not be cleared as long as there is a fault in
any local MEP on the SAP/SDP-binding.

OAM and SAA
Epipe Services
Down and up MEPs are supported for Epipe services as well as fault propagation. When there are
both up and down MEPs configured in the same SAP/SDP-binding and both MEPs have fault
propagation enabled, a fault detected by one of them will be propagated to the other, which in turn
will propagate fault in its own direction.
CFM Detected Fault

When a MEP detects a fault and fault propagation is enabled for the MEP, CFM needs to
communicate the fault to SMGR, so SMGR will mark the SAP/SDP-binding faulty but still oper-
up. CFM traffic can still be transmitted to or received from the SAP/SDP-binding to ensure when
the fault is cleared, the SAP will go back to normal operational state. Since the operational status
of the SAP/SDP-binding is not affected by the fault, no fault handling is performed. For example,
applications relying on the operational status are not affected.
If the MEP is an up MEP, the fault is propagated to the OAM components on the same SAP/SDP-
binding; if the MEP is a down MEP, the fault is propagated to the OAM components on the mate
SAP/SDP-binding at the other side of the service.
SAP/SDP-Binding Failure (Including Pseudowire Status)

When a SAP/SDP-binding becomes faulty (oper-down, admin-down, or pseudowire status faulty),
SMGR needs to propagate the fault to up MEP(s) on the same SAP/SDP-bindings about the fault,
as well as to OAM components (such as down MEPs) on the mate SAP/SDP-binding.
Service Down
This section describes procedures for the scenario where an Epipe service is down due to the
following:
• Service is administratively shutdown. When service is administratively shutdown, the

fault is propagated to the SAP/SDP-bindings in the service.
• If the Epipe service is used as a PBB tunnel into a B-VPLS, the Epipe service is also
considered operationally down when the B-VPLS service is administratively shutdown or
operationally down. If this is the case, fault is propagated to the Epipe SAP.
• In addition, one or more SAPs/SDP-bindings in the B-VPLS can be configured to
propagate fault to this Epipe (see fault-propagation-bmac below). If the B-VPLS is
operationally up but all of these entities have detected fault or are down, the fault is
propagated to this Epipe’s SAP.

OAM Mapping
Interaction with Pseudowire Redundancy

When a fault occurs on the SAP side, the pseudowire status bit is set for both active and standby
pseudowires. When only one of the pseudowire is faulty, SMGR does not notify CFM. The
notification occurs only when both pseudowire becomes faulty. The SMGR propagates the fault to
CFM.
Since there is no fault handling in the pipe service, any CFM fault detected on an SDP binding is
not used in the pseudowire redundancy’s algorithm to choose the most suitable SDP binding to
transmit on.

OAM and SAA
LLF and CFM Fault Propagation

LLF and CFM fault propagation are mutually exclusive. CLI protection is in place to prevent
enabling both LLF and CFM fault propagation in the same service, on the same node and at the
same time. However, there are still instances where irresolvable fault loops can occur when the
two schemes are deployed within the same service on different nodes. This is not preventable by
the CLI. At no time should these two fault propagation schemes be enabled within the same
service.
802.3ah EFM OAM Mapping and Interaction with Service Manager

802.3ah EFM OAM declares a link fault when any of the following occurs:
• Loss of OAMPDU for a certain period of time

• Receiving OAMPDU with link fault flags from the peer
When 802.3ah EFM OAM declares a fault, the port goes into operation state down. The SMGR
communicates the fault to CFM MEPs in the service. OAM fault propagation in the opposite
direction (SMGR to EFM OAM) is not supported.
Fault Propagation to access dot1q/QinQ ports in Access-uplink

mode
The Fault on the access uplink port brings down all access ports with services independent of the
encap type of the access port (NULL or dot1q or QinQ), that is, support Link Loss Forwarding
(LLF). The Fault propagated from the access-uplink port to access ports is based on configuration.
The Fault is propagated only in a single direction, that is access-uplink port to access port.
The Fault on access-uplink port is detected using LoS and EFM-OAM.

OAM Mapping
Figure 17: Local Fault Propagation
Configuring Fault propagation:

To allow faults to detected on access-uplink ports and be propagated to all the other interested
access ports irrespective of their encapsulation, the concept of oper-group is used. In 7210, ports
can be associated with oper-groups. Following bullets describe the use of oper-group functionality
for fault-detection on a port and monitor-oper-group to track the status of the oper-group and
propagate fault based on the operational state of the oper-group.
• Create an oper-group (For example: “uplink-to-7210”)

• Configure access-uplink port whose operational state needs to be tracked (For example: 1/
1/20) and associate it with the oper-group created above (that is, uplink-to-7210)
• Configure dot1q access ports whose operational state needs to be driven by operational
state of access-uplink port (For example: 1/1/1 and 1/1/5), as the monitor-oper-group
• To detect fault on access-uplink port and change the operational state, either Loss of
Signal or EFM OAM can be used.
• When the operational state of access-uplink port changes from UP to DOWN changes the
state of all access ports configured to monitor the group to “Down”. Similarly, a change in
state from Down to UP, changes the operational state of the access port to UP. When the
operational state of access port is brought down, the laser of the port is also shutdown. The
command "Hold timers" are supported to avoid flapping of links.
Configuration Example for fault propagation using oper-group

The following example displays an “oper-group” system configuration:
*A:7210SAS>config>system>oper-group# info detail

----------------------------------------------

OAM and SAA
hold-time
group-down 0
group-up 4
exit
----------------------------------------------
*A:7210SAS>config>system>oper-group#
Note: For more details on the CLI, see the “7210 SAS System Basics User Guide”.

Service Assurance Agent Overview

In the last few years, service delivery to customers has drastically changed. Services such as
VPLSand VPRN are offered. The introduction of Broadband Service Termination Architecture
(BSTA) applications such as Voice over IP (VoIP), TV delivery, video and high speed Internet
services force carriers to produce services where the health and quality of Service Level
Agreement (SLA) commitments are verifiable to the customer and internally within the carrier.
SAA is a feature that monitors network operations using statistics such as jitter, latency, response
time, and packet loss. The information can be used to troubleshoot network problems, problem
prevention, and network topology planning.
The results are saved in SNMP tables are queried by either the CLI or a management system.
Threshold monitors allow for both rising and falling threshold events to alert the provider if SLA
performance statistics deviate from the required parameters.
SAA allows two-way timing for several applications. This provides the carrier and their customers
with data to verify that the SLA agreements are being properly enforced.
Traceroute Implementation
The 7210 SAS-M and 7210 SAS-T devices insert the timestamp in software (by control CPU).
When interpreting these timestamps care must be taken that some nodes are not capable of
providing timestamps, as such timestamps must be associated with the same IP-address that is
being returned to the originator to indicate what hop is being measured.
NTP
Because NTP precision can vary (+/- 1.5ms between nodes even under best case conditions), SAA
one-way latency measurements might display negative values, especially when testing network
segments with very low latencies. The one-way time measurement relies on the accuracy of NTP
between the sending and responding nodes.

OAM and SAA
Writing SAA Results to Accounting Files

SAA statistics enables writing statistics to an accounting file. When results are calculated an
accounting record is generated.
In order to write the SAA results to an accounting file in a compressed XML format at the
termination of every test, the results must be collected, and, in addition to creating the entry in the
appropriate MIB table for this SAA test, a record must be generated in the appropriate accounting
file.
Accounting File Management

Because the SAA accounting files have a similar role to existing accounting files that are used for
billing purposes, existing file management information is leveraged for these accounting (billing)
files.
Assigning SAA to an Accounting File ID

Once an accounting file has been created, accounting information can be specified and will be
collected by the config>log>acct-policy> to file log-file-id context.
Continuous Testing
When you configure a test, use the config>saa>test>continuous command to make the test run
continuously. Use the no continuous command to disable continuous testing and shutdown to
disable the test completely. Once you have configured a test as continuous, you cannot start or stop
it by using the saa test-name [owner test-owner] {start | stop} [no-accounting] command.
Configuring SAA Test Parameters

The following example displays an SAA configuration:
*A:Dut-A>config>saa# info
----------------------------------------------------------------------
....
test "Dut-A:1413:1501" owner "TiMOS"
description "Dut-A:1413:1501"
type
vccv-ping 1413:1501 fc "nc" timeout 10 size 200 count 2
exit
loss-event rising-threshold 2
latency-event rising-threshold 100

no jitter-event
no shutdown
exit
....
----------------------------------------------------------------------
*A:Dut-A#

OAM and SAA
Y.1564 Testhead OAM tool

Note: 7210 SAS-R6 does not support Y.1564 testhead OAM tool.
Note: Port loopback with mac-swap and Y.1564 testhead is supported only for Epipe and VPLS
services.
ITU-T Y.1564 defines the out-of-service test methodology to be used and parameters to be
measured to test service SLA conformance during service turn up. It primarily defines 2 test
phases. The first test phase defines service configuration test, which consists of validating whether
the service is configured properly. As part of this test the throughput, Frame Delay, Frame Delay
Variation (FDV), and Frame Loss Ratio (FLR) is measured for each service. This test is typically
run for a short duration. The second test phase consists of validating the quality of services
delivered to the end customer and is referred to as the service performance test. These tests are
typically run for a longer duration and all traffic is generated up to the configured CIR for all the
services simultaneously and the service performance parameters are measured for each the
service.
The 7210 SAS supports service configuration test for user configured rate and measurement of
delay, delay variation and frame loss ratio with the testhead OAM tool. 7210 testhead OAM tool
supports bi-directional measurement and it can generate test traffic for only one service at a given
time. It can validate if the user specified rate is available and compute the delay, delay variation
and frame loss ratio for the service under test at the specified rate. It is capable of generating
traffic upto 1G rate. On some 7210 SAS devices, the user needs to configure the resources of the
front-panel port for use with this feature and some other 7210 SAS platforms resources needed for
this feature is automatically allocated by software from the internal ports. For more information,
see Configuration Guidelines on page 146, below to which 7210 SAS platforms need user
configuration and on which 7210 platforms software allocates it automatically. Additionally, port
loopback with mac-swap must be used at both the ends and if any services/SAPs configured on the
test port need to be shutdown to avoid packets being dropped on the non-test SAP. The frames
generated by the testhead tool will egress the access SAP and ingress back on the same port, using
the resources of the 2 internal loopback ports (one for testhead and another for mac-swap
functionality), before being sent out to the network side (typically an access-uplink SAP) to the
remote end”. At the remote end, it is expected that the frames will egress the SAP under test and
ingress back in again through the same port, going through another loopback (with mac-swap)
before being sent back to the local node where the testhead application is running.
Figure 18 illustrates the remote loopback required and the flow of the frame through the network
generated by the testhead tool.
Figure 18: 7210 acting as traffic generator and traffic analyzer

The tool allows the user to specify the frame payload header parameters independent of the test
SAP configuration parameters to allow the user flexibility to test for different possible frame
header encapsulations. This allows user to specify the appropriate VLAN tags, ethertype, and
dot1p’s, independent of the SAP configuration like with actual service testing. In other words, the
software does not use the parameters (For example: SAP ID, Source MAC, and Destination MAC)
during the invocation of the testhead tool to build the test frames. Instead it uses the parameters
specified using the frame-payload CLI command tree. The software does not verify that the
parameters specified match the service configuration used for testing, for example, software does
not match if the VLAN tags specified matches the SAP tags, the ethertype specified matches the
user configured port ethertype, and so on. It is expected that the user configures the frame-payload
appropriately so that the traffic matches the SAP configuration.
7210 SAS supports Y.1564 testhead for performing CIR or PIR tests in color-aware mode. With
this functionality, users can perform service turn-up tests to validate the performance
characteristics (delay, jitter, and loss) for committed rate (CIR) and excess rate above CIR (that is,
PIR rate). The testhead OAM tool uses the in-profile packet marking value and out-of-profile
packet marking value, to differentiate between committed traffic and PIR traffic in excess of CIR
traffic. Traffic within CIR (that is, committed traffic) is expected to be treated as in-profile traffic
in the network and traffic in excess of CIR (that is, PIR traffic) is expected to be treated as out-of-
profile traffic in the network, allowing the network to prioritize committed traffic over PIR traffic.
The testhead OAM tool allows the user to configure individual thresholds for green or in-profile
packets and out-of-profile or yellow packets. It is used by the testhead OAM tool to compare the
measured value for green or in-profile packets and out-of-profile or yellow packets against the
configured thresholds and report success or failure.
The following functionality is supported by the testhead OAM tool:
• Supports configuration of only access SAPs as the test measurement point.

OAM and SAA
• Supports all port encapsulation supported on all svc-sap-types and platforms.

• Supported for both VPLS and Epipe service.
• Supports two-way measurement of service performance metrics. The tests must measure
throughput, frame delay, frame delay variation, and frame loss ratio.
• For two-way measurement of the service performance metrics, such as frame delay and
frame delay variation, test frames are injected at a low rate at periodic intervals. Frame
delay and Frame delay variation is computed for these frames and used to display the
results. Hardware based timestamps is used for delay computation.
• 7210 SAS supports configuration of PIR rate and provides an option to measure the
performance metrics for the frames. The testhead OAM tool, generates traffic upto the
specified rate and measures service performance metrics such as, delay, jitter, loss for in-
profile, and out-of-profile traffic.
• Testhead tool can generate traffic upto about 1G rate. CIR and PIR rate can be specified
by the user and is rounded off the nearest rate the hardware supports by using the
adaptation rule configured by the user.
• Allows the user to specify the different frame-sizes from 64 bytes - 9212 bytes.
• User can configure the following frame payload types- L2 payload, IP payload, and IP/
TCP/UDP payload. Testhead tool will use the configured values for the IP header fields
and TCP header fields based on the payload type configured. User is provided with an
option to specify the data pattern to used in the payload field of the frame/packet.
• Allows the user to configure the duration of the test upto a maximum of 24 hours, 60
minutes, and 60 seconds. The test performance measurements by are done after the
specified rate is achieved. At any time user can probe the system to know the current
status and progress of the test.
• Supports configuration of the Forwarding Class (FC). The FC specified is used to
determine the queue to enqueue the marker packets generated by testhead application on
the egress of the test SAP on the local node. It is expected that user will define consistent
QoS classification policies to map the packet header fields to the FC specified on the test
SAP ingress on the local node, in the network on the nodes through which the service
transits, and on the SAP ingress in the remote node.
• Allows the user to configure a test-profile, also known as, a policy template that defines
the test configuration parameters. User can start a test using a pre-configured test policy
for a specific SAP and service. The test profile allows the user to configure the acceptance
criteria. The acceptance criteria allows user to configure the thresholds that indicates the
acceptable range for the service performance metrics. An event is generated if the test
results exceed the configured thresholds. For more information, see the CLI section
below. At the end of the test, the measured values for FD, FDV, and FLR are compared
against the configured thresholds to determine the PASS or FAIL criteria and to generate a
trap to the management station. If the acceptance criteria is not configured, the test result
is declared to be PASS, if the throughput is achieved and frame-loss is 0 (zero).

• ITU-T Y.1564 specifies different test procedures as follows. CIR and PIR configuration
tests are supported by the testhead tool.
→ CIR and PIR configuration test (color-aware and non-color aware).
→ Traffic policing test (color-aware and non-color aware) is supported. Traffic policing
tests can be executed by the user by specifying a PIR to be 125% of the desired PIR.
Traffic policing test can be executed in either color-aware mode or color-blind (non-
color-aware) mode.
• ITU-T Y.1564 specifies separate test methodology for color-aware and non-color-aware
tests. The standard requires a single test to provide the capability to generate both green-
color/in-profile traffic for rates within CIR and yellow-color or out-of-profile traffic for
rates above CIR and within EIR. The 7210 SAS testhead marks test packets appropriately
when generating the traffic, as SAP ingress does not support color-aware metering, it is
not possible to support EIR color-aware, and traffic policing color-aware tests end-to-end
in a network (that is, from test SAP to test SAP). It is possible to use the tests to measure
the performance parameters from the other endpoint in the service to the test SAP. It is
also possible to test the network capability to support the traffic at the required SLA.
• The 7210 SAS Y.1564 testhead is applicable only for simple VPLS and Epipe services.

OAM and SAA
Pre-requisites for using the Testhead Tool
This section describes some pre-requisites to use the testhead tool.
• The configuration guidelines and pre-requisites that are to be followed when the port
loopback with mac-swap feature is used standalone, applies to its use along with testhead
tool. For more information, see the description in the “7210 SAS-MX Interfaces User
Guide”.
• User must configure resources for ACL MAC criteria in ingress-internal-tcam using the
command config>system> resource-profile> ingress-internal-tcam> acl-sap-ingress>
mac-match-enable. Additionally they must allocate resources to egress ACL MAC or
IPv4 or IPv6 64-bit criteria (using the command config>system> resource-profile>
egress-internal-tcam> acl-sap-egress> mac-ipv4-match-enable or mac-ipv6-64bit-enable
or mac-ipv4-match-enable). Testhead tool uses resources from these resource pools. If no
resources are allocated to these pools or no resources are available for use in these pools,
then testhead fails to function. Testhead needs a minimum of about 6 entries from the
ingress-internal-tcam pool and 2 entries from the egress-internal-tcam pool. If user
allocates resources to egress ACLs IPv6 128-bit match criteria (using the command
config> system> resource-profile> egress-internal-tcam> acl-sap-egress> ipv6-128bit-
match-enable), then testhead fails to function.
• For both Epipe and VPLS service, the test can be used to perform only a point-to-point
test between the given source and destination MAC address. Port loopback mac-swap
functionality must be used for both Epipe and VPLS services. The configured source and
destination MAC address is associated with the two SAPs configured in the service and
used as the two endpoints. In other words, the user configured source MAC and
destination MAC addresses are used by the testhead tool on the local node to identify the
packets as belonging to testhead application and are processed appropriately at the local
end and at the remote end these packets are processed by the port loopback with mac-
swap application.
• The “static mac” configuration is mandatory only for VPLS service.
• Port loopback must be in use on both the endpoints (that is, the local node, the port on
which the test SAP is configured and the remote node, the port on which the remote SAP
is configured for both Epipe and VPLS services. Port loopback with mac-swap must be
setup by the user on both the local end and the remote end before invoking the testhead
tool. These must match appropriately for traffic to flow, else there will be no traffic flow
and the testhead tool reports a failure at the end of the completion of the test run.
• Use of port loopback is service affecting. It affects all the services configured on the port.
It is not recommended to use configure a SAP, if the port on which they are configured, is
used to transport the service packets towards the core. As, a port loopback is required for
the testhead to function correctly, doing so might result in loss of connectivity to the node
when in-band management is in use. Additionally, all services being transported to the
core will be affected.

• It is expected that the user will configure the appropriate ACL and QoS policies to ensure
that the testhead traffic is processed as desired by the local and remote node/SAP. In
particular, QoS policies in use must ensure that the rate in use for the SAP ingress meters
exceed or are equal to the user configured rate for testhead tests and the classification
policies map the testhead packets to the appropriate FCs/queues (the FC classification
must match the FC specified in the CLI command testhead-test) using the packet header
fields configured in the frame-payload. Similarly, ACL policies must ensure that testhead
traffic is not blocked.
• Testhead tool uses marker packets with special header values. The QoS policies and ACL
policies need to ensure that same treatment as accorded to testhead traffic is given to
marker packets. In this release, Marker packets are IPv4 packet with IP option set and IP
protocol set to 252. It uses the src and dst MAC addresses, Dot1p, IP ToS, IP DSCP, IP
TTL, IP source address and destination address as configured in the frame-payload. It
does not use the IP protocol and TCP/UDP port numbers from the frame-payload
configured. If the payload-type is “l2”, IP addresses are set to 0.0.0.0, IP TTL is set to 0,
IP TOS is set to 0 and DSCP is set to be, if these values are not explicitly configured in the
frame-payload. Ethertype configured in the frame-payload is not used for marker packets,
it is always set to ethertype = 0x0800 (ethertype for IPv4) as marker packets are IPv4
packets. QoS policies applied in the network needs to configured such that the
classification for marker packets is similar to service packets. An easy way to do this is by
using the header fields that are common across marker packets and service packets, such
as MAC (src and dst) addresses, VLAN ID, Dot1p, IPv4 (src and dst) addresses, IP DSCP,
and IP ToS. Use of other fields which are different for marker packets and service packets
is not recommended. ACL policies in the network must ensure that marker packets are not
dropped.
• The testhead software does not check the state of the service or the SAPs on the local
endpoint before initiating the tests. The operator must ensure that the service and SAPs
used for the test are UP before the tests are started. If they are not, the testhead tool will
report a failure.
• The mac-swap loopback port, the testhead loopback port and the uplink port must not be
modified after the testhead tool is invoked. Any modifications can be made only when the
testhead tool is not running.
• Testhead tool can be used to test only unicast traffic flows. It must not be used to test
BUM traffic flows.
• Link-level protocols (For example: LLDP, EFM, and other protocols) must not be enabled
on the port on which the test SAP is configured. In general, no other traffic must be sent
out of the test SAP when the testhead tool is running.
• The frame payload must be configured such that number of tags match the number of SAP
tags. For example: For 0.* SAP, the frame payload must be untagged or priority tagged
and it cannot contain another tag following the priority tag.

OAM and SAA
Port Loopback for Ethernet ports

Note: Port Loopback with mac-swap is not supported on 7210 SAS-R6 devices.
7210 devices support port loopback for ethernet ports. There are two flavors of port loopback
commands - port loopback without mac-swap and port loopback with mac-swap. Both these
commands are helpful for testing the service configuration and measuring performance parameters
such as throughput, delay, and jitter on service turn-up. Typically, a third-party external test device
is used to inject packets at desired rate into the service at a central office location.
For detailed information on port loop back functionality see 7210 SAS-M,X, T and R6 Interfaces
guide .

Configuration Guidelines
This section describes the configuration guidelines for Testhead.
• SAPs configured on LAG cannot be configured for testing with testhead tool. Other than
the test SAP, other service endpoints (For example: SAPs/SDP-Bindings) configured in
the service can be over a LAG.
• The user must configure a front-panel port for use with testhead OAM tool on 7210 SAS-
M, 7210 SAS-T and 7210 SAS-X. On some platforms, example 7210 SAS-T, the internal
port resources could be configured for use with testhead OAM tool. Please read the details
provided in the CLI command config> system> loopback-no-svc-port in the 7210 SAS
Interfaces user guide to know if front-panel port resources are needed and use the
command show>system>internal-loopback-ports [detail] to know if internal port
resources are in use by other applications. The port configured for testhead tool use cannot
be shared with other applications that need the loopback port. The resources of the
loopback port are used by the testhead tool for traffic generation.
• Port loopback with mac-swap is used at both ends and all services and SAPs in the VPLS
service, other than the test SAP should be shutdown or should not receive any traffic.
• The configured CIR/PIR rate is rounded off to the nearest available hardware rates. User is
provided with an option to select the adaptation rule to use (similar to support available for
QoS policies).
• 7210 SAS supports all port speeds (that is, upto 1G rate). User can configure the
appropriate loopback port to achieve a desired rate. For example, user must dedicate the
resources of a 1G port, if intended to test rates to go upto 1G.
• ITU-T Y.1564 recommends to provide an option to configure the CIR step-size and the
step-duration for the service configuration tests. This is not supported directly in 7210
SAS. It can be achieved by SAM or a third-party NMS system or an application with
configuration of the desired rate and duration to correspond to the CIR step-size and step
duration and repeating the test a second time, with a different value of the rate (that is, CIR
step size) and duration (that is, step duration) and so on.
• Testhead waits for about 5 seconds at the end of the configured test duration before
collecting statistics. This allows for all in-flight packets to be received by the node and
accounted for in the test measurements. User cannot start another test during this period.
• When using testhead to test bandwidth available between SAPs configured in a VPLS
service, operators must ensure that no other SAPs in the VPLS service are exchanging any
traffic, particularly BUM traffic and unicast traffic destined to either the local test SAP or
the remote SAP. BUM traffic eats into the network resources which is also used by
testhead traffic.
• It is possible that test packets (both data and marker packets) remain in the loop created
for testing when the tests are killed. This is highly probably when using QoS policies with
very less shaper rates resulting in high latency for packets flowing through the network
loop. User must remove the loop at both ends once the test is complete or when the test is

OAM and SAA
stopped and wait for a suitable time before starting the next test for the same service, to
ensure that packets drain out of the network for that service. If this is not done, then the
subsequent tests might process and account these stale packets, resulting in incorrect
results. Software cannot detect stale packets in the loop as it does not associate or check
each and every packet with a test session
• Traffic received from the remote node and looped back into the test port (where the test
SAP is configured) on the local end (that is, the end where the testhead tool is invoked) is
dropped by hardware after processing (and is not sent back to the remote end). The SAP
ingress QoS policies and SAP ingress filter policies must match the packet header fields
specified by the user in the testhead profile, except that the source/destination MAC
addresses are swapped.
• Latency is not be computed if marker packets are not received by the local node where the
test is generated and printed as 0 (zero), in such cases. If jitter = 0 and latency > 0, it
means that jitter calculated is less than the precision used for measurement. There is also a
small chance that jitter was not actually calculated, that is, only one value of latency has
been computed. This typically indicates a network issue, rather than a testhead issue.
• When the throughput is not met, FLR cannot be calculated. If the measured throughput is
approximately +/-10% of the user configured rate, FLR value is displayed; else software
prints “Not Applicable”. The percentage of variance of measured bandwidth depends on
the packet size in use and the configured rate.
• User must not use the CLI command to clear statistics of the test SAP port, testhead
loopback port and MAC swap loopback port when the testhead tool is running. The port
statistics are used by the tool to determine the Tx/Rx frame count.
• Testhead tool generates traffic at a rate slightly above the CIR. The additional bandwidth
is attributable to the marker packets used for latency measurements. This is not expected
to affect the latency measurement or the test results in a significant way.
• If the operational throughput is 1kbps and is achieved in the test loop, the throughput
computed could still be printed as 0 if it is < 1Kbps (0.99 kbps, for example). Under such
cases, if FLR is PASS, the tool indicates that the throughput has been achieved.
• The testhead tool displays a failure result if the received count of frames is less than the
injected count of frames, even though the FLR might be displayed as 0. This happens due
to truncation of FLR results to 6 decimal places and can happen when the loss is very less.
• As the rate approaches 1Gbps or the maximum bandwidth achievable in the loop, user
needs to account for the marker packet rate and the meter behavior while configuring the
CIR rate. In other words, if the user wants to test 1Gbps for 512 bytes frame size, then
they will need to configure about 962396Kbps, instead of 962406Kbps, the maximum rate
that can be achieved for this frame-size. In general, they would need to configure about
98%-99% (based on packet size) of the maximum possible rate to account for marker
packets when they need to test at rates which are closer to bandwidth available in the
network. The reason for this is that at the maximum rate, injection of marker packets by
CPU will result in drops of either the injected data traffic or the marker packets

themselves, as the net rate exceeds the capacity. These drops cause the testhead to always
report a failure, unless the rate is marginally reduced.
• Testhead works with L2 rate, that is, the rate after subtracting the L1 overhead. The L1
overhead is due to IFG and Preamble added to every Ethernet frame and is typically about
20 bytes (IFG = 12 bytes and Preamble = 8 bytes). Depending on the frame size
configured by the user, testhead tool computes the L2 rate and does not allow the user to
configure a value greater than it. For 512 bytes Ethernet frame, L2 rate is 962406Kbps and
L1 rate is 1Gbps.
• It is not expected that the operator will use the testhead tool to measure the throughput or
other performance parameters of the network during the course of network event. The
network events could be affecting the other SAP/SDP-Binding/PW configured in the
service. Examples are transition of a SAP due to G8032 ring failure, transition of active/
standby SDP-Binding/PW due to link or node failures.
• The 2-way delay (also known as “latency”) values measured by Testhead tool is more
accurate than obtained using OAM tools, as the timestamps are generated in hardware.
• 7210 SAS does not support color-aware metering on access SAP ingress, therefore, any
color-aware packets generated by the testhead is ignored on access SAP ingress. 7210
SAS service access port, access-uplink port, or network port can mark the packets
appropriately on egress to allow the subsequent nodes in the network to differentiate the
in-profile and out-of-profile packets and provide them with appropriate QoS treatment.
7210 SAS access-uplink ingress and network port ingress is capable of providing
appropriate QoS treatment to in-profile and out-of-profile packets.
• The marker packets are sent over and above the configured CIR or PIR rate, the tool
cannot determine the number of green packets injected and the number of yellow packets
injected individually. Therefore, marker packets are not accounted in the injected or
received green or in-profile and yellow or out-of-profile packet counts. They are only
accounted for the Total Injected and the Total Received counts. So, the FLR metric
accounts for marker packet loss (if any), while green or yellow FLR metric does not
account for any marker packet loss.
• Marker packets are used to measure green or in-profile packets latency and jitter and the
yellow or out-of-profile packets latency and jitter. These marker packets are identified as
green or yellow based on the packet marking (Example: dot1p). The latency values can be
different for green and yellow packets based on the treatment allowed to the packets by
the network QoS configuration.
• The following table provides details of SAP encapsulation that are supported for Testhead.
Table 10: SAP Encapsulations supported for testhead

Epipe service configured Test SAP Encapsu-
with svc-sap-type lations

OAM and SAA
Table 10: SAP Encapsulations supported for testhead

null-star Null, :* , 0.* , Q.*
Any Null , :0 , :Q , :Q1.Q2
dot1q-preserve :Q

Configuring testhead tool parameters
The following example displays a port loopback mac-swap using the service and SAP:
configure> system> loopback-no-svc-port testhead <port-id>

*A:7210SAS>config>system# info
----------------------------------------------
.............
resource-profile
ingress-internal-tcam
qos-sap-ingress-resource 5
exit
acl-sap-ingress 5
exit
exit
egress-internal-tcam
exit
exit
loopback-no-svc-port mac-swap 1/1/8 testhead 1/1/11
..............
The following example displays a port loopback with mac-swap on the remote end:
*A:7210SAS# configure system loopback-no-svc-port mac-swap 1/1/8

*A:7210SAS# configure system
*A:7210SAS>config>system# info
----------------------------------------------
alarm-contact-input 1
shutdown
exit
shutdown
exit
shutdown
exit
shutdown
exit
resource-profile
ingress-internal-tcam
qos-sap-ingress-resource 5
exit
acl-sap-ingress 5
exit
exit
egress-internal-tcam
exit
exit
loopback-no-svc-port mac-swap 1/1/8 testhead 1/1/11
.................

OAM and SAA
The following example displays a testhead profile:
*A:7210SAS# configure test-oam testhead-profile 1

*A:7210SAS>config>test-oam>testhd-prof# info
----------------------------------------------
description "Testhead_Profile_1"
frame-size 512
rate cir 100 adaptation-rule max pir 200
dot1p in-profile 2 out-profile 4
frame-payload 1 payload-type tcp-ipv4 create
description "Frame_Payload_1"
dscp "af11"
dst-ip ipv4 2.2.2.2
dst-mac 00:00:00:00:00:02
src-mac 00:00:00:00:00:01
dst-port 50
src-port 40
ip-proto 6
ip-tos 8
ip-ttl 64
src-ip ipv4 1.1.1.1
exit
acceptance-criteria 1 create
jitter-rising-threshold 100
jitter-rising-threshold-in 100
jitter-rising-threshold-out 100
latency-rising-threshold 100
latency-rising-threshold-in 100
latency-rising-threshold-out 100
loss-rising-threshold 100
loss-rising-threshold-in 100
loss-rising-threshold-out 100
cir-threshold 1000
pir-threshold 2000
exit
----------------------------------------------
*A:7210SAS>config>test-oam>testhd-prof#
The following command is used to execute the testhead profile:
*A:7210SAS# oam testhead testhead-profile 1 frame-payload 1 sap 1/1/2 test-me owner own-
erme color-aware enable


OAM and SAA Command Reference
Diagnostics Command Reference

• OAM Commands on page 153
• SAA Commands on page 162
OAM Commands
Base Operational Commands
GLOBAL
— ping [ip-address | dns-name] [rapid | detail] [ttl time-to-live] [tos type-of-service] [size bytes] [pattern
pattern] [source ip-address | dns-name ] [interval seconds] [{next-hop ip-address} | {interface inter-
face-name} | bypass-routing] [count requests] [do-not-fragment] [router router-instance| service-
name service- name] [timeout timeout] [fc fc-name]
— traceroute [ip-address | dns-name] [ttl ttl] [wait milli-seconds] [no-dns][source ip-address] [tos type-of-
service] [router [router-instance | service- name service- name]
— oam
— dns target-addr dns-name name-server ip-address [source ip-address] [count send-count]
[timeout timeout] [interval interval] [record-type {ipv4-a-record|ipv6-aaaa-record}]
— saa test-name [owner test-owner] {start | stop} [no-accounting]
LSP Diagnostics
GLOBAL
— oam
— lsp-ping lsp-name [path path-name]
— lsp-ping prefix ip-prefix/mask [path-destination ip-address [interface if-name | next-hop ip-
address]]
— lsp-ping static lsp-name [assoc-channel ipv4|non-ip|none] [dest-global-id global-id dest-
node-id node-id] [force] [path-type active | working | protect]
— lsp-trace lsp-name [path path-name]
— lsp-trace prefix ip-prefix/mask [path-destination ip-address [interface if-name | next-hop ip-
address]]
— lsp-trace static lsp-name [assoc-channel ipv4|non-ip|none] [path-type active | working |
protect]
TWAMP
GLOBAL
— oam
— oam-test
— twamp
— server
— [no] prefix {ip-prefix | mask}

— [no] description description string

— [no] max-conn-prefix count
— [no] max-sess-prefix count
— [no] shutdown
— [no] inactivity-timeout seconds
— [no] max-conn-server count
— [no] max-sess-servercount
— [no] port number
— [no] shutdown

SDP Diagnostics
Note: SDP diagnostics commands are not applicable for 7210 SAS devices configured in
Access uplink mode.
GLOBAL
— oam
— sdp-mtu orig-sdp-id size-inc start-octets end-octets [step step-size] [timeout timeout] [inter-
val interval]
— sdp-ping orig-sdp-id [resp-sdp resp-sdp-id] [fc fc-name] [timeout seconds] [interval
seconds] [size octets] [count send-count] [interval <interval>]

Common Service Diagnostics

Note: Only DNS command is supported by 7210 SAS devices configured in access uplink
mode.
GLOBAL
— oam
— svc-ping {ip-addr} service service-id [local-sdp] [remote-sdp]
— dns target-addr dns-name name-server ip-address [source ip-address] [count send-count]
[timeout timeout] [interval interval]
— vprn-ping service-id service svc-name source ip-address destination ip-address [fc fc-name
[size size] [ttl vc-label-ttl] [return-control] [interval interval] [count send-count] [timeout
timeout]
— vprn-trace service-id source src-ip destination ip-address [fc fc-name ] [size size] [min-ttl
vc-label-ttl] [max-ttl vc-label-ttl] [return-control] [probe-count sendcount] [interval inter-
val] [timeout timeout]
VLL Diagnostics
Note: VLL diagnostics commands are not applicable for 7210 SAS devices configured in
access uplink mode.
GLOBAL
— oam
— vccv-ping sdp-id:vc-id [src-ip-address ip-addr dst-ip-address ip-addr pw-id pw-id][reply-
mode {ip-routed | control-channel}][fc fc-name [size octets] [send-count send-count] [time-
out timeout] [interval interval][ttl vc-label-ttl]
— vccv-ping spoke-sdp spoke-sdp-id [reply-mode ip-routed| control-channel] [src-ip-address
ip-addr dst-ip-address ip-addr] (Supported on 7210 SAS-X, 7210 SAS-R6 and 7210 SAS-T
network mode)
— vccv-ping static sdp-id:vc-id [assoc-channel ipv4|non-ip][dest-global-id global-id dest-
node-id node-id] [src-ip-address ip-addr]
— vccv-trace sdp-id:vc-id [fc fc-name [profile {in | out}]] [size octets] [reply-mode ip-
routed|countrol-channel] [probe-count probes-count] [timeout timeout] [interval interval]
[min-ttl min-vc-label-ttl] [max-ttl max-vc-label-ttl] [max-fail no-response-count] [detail]
— vccv-trace static sdp-id:vc-id [assoc-channel ipv4|non-ip] [src-ip-address ipv4-address]

Note: VPLS diagnostics commands are not applicable for 7210 SAS devices configured in
Access uplink mode.
GLOBAL
— oam
— cpe-ping service service-id destination ip-address source ip-address [source-mac ieee-
address] [fc fc-name] [ttl vc-label-ttl] [count send-count] [send-control] [return-control]
[interval interval]

— mac-ping service service-id destination dst-ieee-address [source src-ieee-address] [fc fc-

name ] [size octets] [fc fc-name] [ttl vc-label-ttl] [send-count send-count] [send-control]
[return-control] [interval interval] [timeout timeout]
— mac-populate service-id mac ieee-address [flood] [age seconds] [force] [target-sap sap-id]
[send-control]
— mac-purge service-id target ieee-address [flood] [send-control] [register]
— mac-trace service service-id destination ieee-address [source ieee-address] [fc fc-name ]
[size octets] [min-ttl vc-label-ttl] [max-ttl vc-label-ttl] [probe-count send-count] [send-con-
trol] [return-control] [interval interval] [timeout timeout]
Ethernet in the First Mile (EFM) Commands

GLOBAL
— oam
— efm port-id local-loopback {start | stop}
— efm port-id remote-loopback {start | stop}
ETH-CFM OAM Commands

oam
— eth-cfm eth-test mac-address mep mep-id domain md-index association ma-index [priority priority]
[data-length data-length]
— eth-cfm linktrace mac-address mep mep-id domain md-index association ma-index [ttl ttl-value]
— eth-cfm loopback mac-address mep mep-id domain md-index association ma-index [send-count send-
count] [size data-size] [priority priority]
— eth-cfm one-way-delay-test mac-address mep mep-id domain md-index association ma-index [prior-
ity priority]
— eth-cfm two-way-delay-test mac-address mep mep-id domain md-index association ma-index [prior-
ity priority]
— eth-cfm-two-way-slm-test mac-address mep mep-id domain md-index association ma-index [fc {fc-
name} [profile {in|out}]] [count send-count] [size data-size] [timeout timeout] [interval interval]

Y.1564 Testhead OAM commands

config
— test-oam
— testhead-profile profile-id create
— [no] acceptance-criteria acceptance-criteria-id create
— [no] cir-threshold threshold
— [no] jitter-rising-threshold threshold
— [no] jitter-rising-threshold-in threshold
— [no] jitter-rising-threshold-out threshold
— [no] latency-rising-threshold threshold
— [no] latency-rising-threshold-in threshold
— [no] latency-rising-threshold-out threshold
— [no] loss-rising-threshold threshold
— [no] loss-rising-threshold-in threshold
— [no] loss-rising-threshold-out threshold
— [no] pir-threshold threshold
— [no] description description-string
— dot1p in-profile dot1p-value out-profile dot1p-value
— no dot1p
— no frame-payload payload-id [payload-type [l2|tcp-ipv4|udp-ipv4|ipv4] create
— no frame-payload payload
— [no] data-pattern data-pattern
— [no] description description-string
— [no] dscp dscp-name
— [no] dst-ip ipv4 ipv4-address
— [no] dst-mac ieee-address [ieee-address-mask]
— [no] dst-port dst-port-number
— [no] ethertype 0x0600..0xffff
— [no] ip-proto ip-protocol-number
— [no] ip-tos type-of-service
— [no] ip-ttl ttl-value
— [no] src-ip ipv4 ipv4-address
— [no] src-mac ieee-address [ieee-address-mask]
— [no] src-port src-port-number
— [no] vlan-tag-1 vlan-id vlan-id [tpid tpid] [dot1p dot1p-value]
— [no] vlan-tag-2 vlan-id vlan-id [tpid tpid] [dot1p dot1p-value]
— [no] frame-size frame-size
— [no] rate cir cir-rate-in-kbps [cir-adaptation-rule adaptation-rule] [pir cir-rate-i
n-kbp]
— [no] test-completion-trap-enable
— [no] test-duration [hours hours| minutes minutes| seconds seconds]
— [no] test-duration

Y.1564 Testhead OAM Commands

oam
— testhead test-name owner owner-name testhead-profile profile-id [frame-payload frame-payload-id]
sap sap-id [fc fc-name] [acceptance-criteria acceptance-criteria-id] [color-aware enable|disable]
— testhead test-name owner owner-name stop

Show commands
show
— test-oam
— testhead-profile profile-id
show
— testhead [test-name owner owner-name] [detail]

Clear commands
clear
— test-oam
— twamp server
— testhead result [test-name] owner [owner-name]
— testhead testhead-profile profile-id

SAA Commands
Note: The following commands are not supported by 7210 SAS devices configured in Access
uplink mode:
• cpe-ping
• lsp-ping
• lsp-trace
• mac-ping
• mac-trace
• sdp-ping
• vccv-ping
• vccv-trace
• vprn-ping
• vprn-trace
config
— saa
— [no] test test-name [owner test-owner]
— accounting-policy acct-policy-id
— no accounting-policy
— [no] continuous
— no description
— [no] jitter-event rising-threshold threshold [falling-threshold threshold] [direc-
tion]
— [no] latency-event rising-threshold threshold [falling-threshold threshold]
[direction]
— [no] loss-event rising-threshold threshold [falling-threshold threshold] [direction]
— [no] shutdown
— trap-gen
— [no] probe-fail-enable
— [no] probe-fail-threshold 0..15
— [no] test-completion-enable
— [no] test-fail-enable
— [no] test-fail-threshold 0..15
— [no] type
— cpe-ping service service-id destination ip-address source ip-address
[source-mac ieee-address] [fc fc-name ][ttl vc-label-ttl] [send-count
send-count] [send-control] [return-control] [interval interval]

— dns target-addr dns-name name-server ip-address [source ip-address]

[send-count send-count] [timeout timeout] [interval interval]
— eth-cfm-linktrace mac-address mep mep-id domain md-index associa-
tion ma-index [ttl ttl-value] [fc {fc-name} ] [count send-count] [timeout
timeout] [interval interval] [record-type {ipv4-a-record|ipv6-aaaa-
record}]
— eth-cfm-loopback mac-address mep mep-id domain md-index associa-
tion ma-index [size data-size] [fc {fc-name} ] [count send-count ][timeout
timeout] [interval interval]
— eth-cfm-two-way-delay mac-address mep mep-id domain md-index asso-
ciation ma-index [fc {fc-name} ][count send-count ][timeout timeout]
[interval interval]
— eth-cfm-two-way-slm mac-address mep mep-id domain md-index associ-
ation ma-index [fc {fc-name} [profile {in|out}]] [count send-count] [size
data-size] [timeout timeout] [interval interval]
— icmp-ping [ip-address | dns-name] [rapid | detail] [ttl time-to-live] [tos
type-of-service] [size bytes] [pattern pattern] [source ip-address] [inter-
val seconds] [{next-hop ip-address}|{interface interface-name}|bypass-
routing] [count requests] [do-not-fragment] [router-instance | service-
name service- name] [timeout timeout]fc {fc-name}
— icmp-trace [ip-address | dns-name] [ttl time-to-live] [wait milli-seconds]
[source ip-address] [tos type-of-service][router-instance | service- name
service- name]
— lsp-ping {{lsp-name [path path-name]}|{prefix ip-prefix/mask}} [size
octets] [ttl label-ttl] [timeout timeout] [interval interval] [fc fc-name
[profile {in | out}]] [send-count send-count] {lsp-name [path path-
name]} [fc fc-name] [size octets][ttl label-ttl] [send-count send-count]
— lsp-trace {lsp-name [path path-name]} [fc fc-name] [max-fail no-
response-count] [probe-count probes-per-hop] [size octets] [min-ttl min-
label-ttl] [max-ttl max-label-ttl] [timeout timeout] [interval interval]
— mac-ping service service-id destination dst ieee-address [source src-
ieee-address] [fc fc-name] [size octets] [ttl vc-label-ttl] [send-count send-
count] [send-control] [return-control] [interval interval] [timeout time-
out]
— mac-trace service service-id destination ieee-address [source src-ieee-
address] [fc fc-name] [size octets]] [min-ttl min-label-ttl] [max-ttl max-
label-ttl] [send-count send-count] [send-control] [return-control] [inter-
val interval] [timeout timeout]
— sdp-ping orig-sdp-id [resp-sdp resp-sdp-id] [fc fc-name ]] [size octets]
[send-count send-count][timeout seconds] [interval seconds]
— vccv-ping sdp-id:vc-id [src-ip-address ip-addr dst-ip-address ip-addr
pw-id pw-id][reply-mode {ip-routed | control-channel}][fc fc-name
[size octets] [send-count send-count][timeout timeout] [interval inter-
val][ttl vc-label-ttl]
— vccv-trace sdp-id:vc-id [size octets][min-ttl vc-label-ttl] [max-ttl vc-
label-ttl][max-fail no-response-count][probe-count probe-count][reply-
mode ip-routed|control-channel][timeout timeout-value][interval inter-
val-value][fc fc-name ][detail]
— vprn-ping service-id service svc-name [src-ip-address ip-addr dst-ip-
address ip-addr [fc fc-name [profile in | out]] [size size] [ttl vc-label-ttl]
[send-count send-count] [return-control] [timeout timeout] [interval
seconds]

— vprn-trace service-id source src-ip destination dst-ip [fc fc-name [pro-

file in | out]] [size size] [min-ttl vc-label-ttl] [max-ttl vc-label-ttl] [probe-
count send-count] [return-control] [timeout timeout] [interval interval]

Show Commands
show
— eth-cfm
— association [ma-index] [detail]
— cfm-stack-table [port [port-id [vlan qtag[.qtag]]| sdp sdp-id[:vc-id]][level 0..7] [direction
up | down]
— domain [md-index] [association ma-index | all-associations] [detail]
— mep mep-id domain md-index association ma-index [loopback] [linktrace]
— mep mep-id domain md-index association ma-index [remote-mepid mep-id | all-remote-
mepids]
— mep mep-id domain md-index association ma-index eth-test-results [remote-peer mac-
address]
— mep mep-id domain md-index association ma-index one-way-delay-test [remote-peer mac-
address]
— mep mep-id domain md-index association ma-index two-way-delay-test [remote-peer mac-
address]
— mep mep-id domain md-index association ma-index two-way-slm-test [remote-peer mac-
address]
— saa [test-name [owner test-owner]]
— test-oam
— twamp server
— server all
— server prefix ip-prefix/mask
— server
Clear Commands
clear
— saa [test-name [owner test-owner]]
— test-oam
— twamp server
— server


OAM and SAA Command Hierarchies
Operational Commands
shutdown
Context config>saa>test
Description In order to modify an existing test it must first be shut down. When a test is created it will be in shutdown
mode until a no shutdown command is executed.
A shutdown can only be performed if a test is not executing at the time the command is entered.
Use the no form of the command to set the state of the test to operational.
shutdown
Context config>test-oam>ldp-treetrace
config>test-oam>twamp>server
config>test-oam>twamp>server>prefix
Description This command suspends the background process running the LDP ECMP OAM tree discovery and path
probing features. The configuration is not deleted.
Use the no form of the command to enable the background process.
dns
Syntax dns target-addr dns-name name-server ip-address [source ip-address] [count send-count]
Context oam
Description This command performs DNS name resolution. If ipv4-a-record is specified, dns-names are queried for A-
records only.
Parameters send-count send-count — The number of messages to send, expressed as a decimal integer. The send-count
parameter is used to override the default number of message requests sent. Each message request must
either timeout or receive a reply before the next message request is sent. The message interval value
must be expired before the next message request is sent.

Default 1
Values 1 — 100
ip-address — The IP or IPv6 address of the primary DNS server.
Values ipv4-address - a.b.c.d
ipv6-address - x:x:x:x:x:x:x:x (eight 16-bit pieces)
x:x:x:x:x:x:d.d.d.d
x - [0..FFFF]H
d - [0..255]D
timeout timeout — The timeout parameter in seconds, expressed as a decimal integer. This value is used to
override the default timeout value and is the amount of time that the router will wait for a message
reply after sending the message request. Upon the expiration of message timeout, the requesting router
assumes that the message response will not be received. Any response received after the request times
out will be silently discarded.
Default 5
Values 1 — 120
interval interval — The interval parameter in seconds, expressed as a decimal integer. This parameter is
used to override the default request message send interval and defines the minimum amount of time that
must expire before the next message request is sent.
If the interval is set to 1 second, and the timeout value is set to 10 seconds, then the maximum time
between message requests is 10 seconds and the minimum is 1 second. This depends upon the receipt of
a message reply corresponding to the outstanding message request.
Default 1
Values 1 — 10
ping
Syntax ping [ip-address | dns-name] [rapid | detail] [ttl time-to-live] [tos type-of-service] [size bytes]
[pattern pattern] [source ip-address | dns-name] [interval seconds] [{next-hop ip-address} |
{interface interface-name} | bypass-routing] [count requests] [do-not-fragment] [router
router-instance | service-name service-name] [timeout timeout]
Context <GLOBAL>
Description This command verifies the reachability of a remote host.
Parameters ip-address — The far-end IP address to which to send the sve-ping request message in dotted decimal nota-
tion.
Note: IPv6 is supported only for "Management" instance of the router.
Values ipv4-address: a.b.c.d
ipv6-address: x:x:x:x:x:x:x:x (eight 16-bit pieces)
x:x:x:x:x:x:d.d.d.d

x: [0 .. FFFF]H
d: [0 .. 255]D
dns-name — The DNS name of the far-end device to which to send the sve-ping request message, expressed
as a character string.
rapid — Packets will be generated as fast as possible instead of the default 1 per second.
detail — Displays detailed information.
ttl time-to-live — The TTL value for the MPLS label, expressed as a decimal integer.
Values 1 — 128
tos type-of-service — Specifies the service type.
Values 0 — 255
size bytes — The request packet size in bytes, expressed as a decimal integer.
Values 0 — 16384
pattern pattern — The date portion in a ping packet will be filled with the pattern value specified. If not
specified, position info will be filled instead.
Values 0 — 65535
source ip-address — Specifies the IP address to be used.
x:x:x:x:x:x:d.d.d.d
x: [0 .. FFFF]H
d: [0 .. 255]D
router router-instance — Specifies the router name or service ID.
Values router-name: Base , management
Default Base
service-name service-name - Specifies the service name as an integer or string.
bypass-routing — Specifies whether to send the ping request to a host on a directly attached network
bypassing the routing table.
interface interface-name — Specifies the name of an IP interface. The name must already exist in the con-
fig>router>interface context.
next-hop ip-address — Only displays static routes with the specified next hop IP address.
Values ipv4-address: a.b.c.d (host bits must be 0)
x:x:x:x:x:x:d.d.d.d
x: [0 — FFFF]H
d: [0 — 255]

count requests — Specifies the number of times to perform an OAM ping probe operation. Each OAM echo
message request must either timeout or receive a reply before the next message request is sent.
Values 1 — 100000
Default 5
do-not-fragment — Sets the DF (Do Not Fragment) bit in the ICMP ping packet.
timeout seconds — Overrides the default timeout value and is the amount of time that the router will wait
for a message reply after sending the message request. Upon the expiration of message timeout, the
requesting router assumes that the message response will not be received. A ‘request timeout’ message
is displayed by the CLI for each message request sent that expires. Any response received after the
request times out will be silently discarded.
Default 5
Values 1 — 10
traceroute
Syntax traceroute [ip-address |dns-name] [ttl ttl] [wait milli-seconds] [no-dns] [source ip-address] [tos
type-of-service] [router router-instance | service- name service- name]
Context Global
Description The TCP/IP traceroute utility determines the route to a destination address. DNS lookups of the responding
hosts is enabled by default.
*A:ALA-1# traceroute 192.168.xx.xx4
traceroute to 192.168.xx.xx4, 30 hops max, 40 byte packets
1 192.168.xx.xx4 0.000 ms 0.000 ms 0.000 ms
*A:ALA-1#
Parameters ip-address — The far-end IP address to which to send the traceroute request message in dotted decimal nota-
tion.
x:x:x:x:x:x:d.d.d.d
x: [0 .. FFFF]H
d: [0 .. 255]D
dns-name — The DNS name of the far-end device to which to send the traceroute request message,
expressed as a character string.
ttl ttl — The maximum Time-To-Live (TTL) value to include in the traceroute request, expressed as a deci-
mal integer.
Values 1 — 255
wait milliseconds — The time in milliseconds to wait for a response to a probe, expressed as a decimal inte-
ger.

Default 5000
Values 10 — 60000
no-dns — When the no-dns keyword is specified, DNS lookups of the responding hosts will not be per-
formed, only the IP addresses will be printed.
Default DNS lookups are performed
source ip-address — The source IP address to use as the source of the probe packets in dotted decimal nota-
tion. If the IP address is not one of the device’s interfaces, an error is returned.
tos type-of-service — The type-of-service (TOS) bits in the IP header of the probe packets, expressed as a
decimal integer.
Values 0 — 255
router router-name — Specify the alphanumeric character string up to 32 characters.
Values Base, Management
service-name service-name - Specifies the service name as an integer or string.
lsp-ping
Syntax lsp-ping lsp-name [path path-name]
lsp-ping prefix ip-prefix/mask [path-destination ip-address [interface if-name | next-hop ip-
address]]
lsp-ping static lsp-name [assoc-channel ipv4|none|non-ip] [force] [dest-global-id global-id
dest-node-id node-id] [path-type active | working | protect]
NOTE: Options common to all lsp-ping cases: [detail] [fc fc-name [profile in|out]] [interval
interval] [send-count send-count] [size octets] [src-ip-address ip-address] [timeout timeout] [ttl
label-ttl]
Context oam
config>saa>test>type
Description This command, when used with the static option, performs in-band on-demand LSP connectivity verifica-
tion tests for static MPLS-TP LSPs. For other LSP types, the static option should be excluded and these are
described elsewhere in this user guide.
The lsp-ping static command performs an LSP ping using the protocol and data structures defined in the
RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures, as extended by RFC
6426, MPLS On-Demand Connectivity Verification and Route Tracing.
In an LSP ping, the originating device creates an MPLS echo request packet for the LSP and path to be
tested, containing a static LSP target FEC stack TLV for the LSP. The MPLS echo request packet is sent
through the data plane, encapsulated in either the LSP label or the MPLS-TP G-ACh channel, and awaits an
MPLS echo reply packet from the device terminating the LSP. The status of the LSP is displayed when the
MPLS echo reply packet is received.

In MPLS-TP, the echo request and echo reply messages are always sent in-band over the LSP, either in a G-
ACh channel or encapsulated as an IP packet below the LSP label.
Parameters lsp-name — Name that identifies an LSP to ping. The LSP name can be up to 32 characters long.
dest-global-id global-id — The MPLS-TP global ID for the far end node of the LSP under test. If this is not
entered, then the dest-global-id is taken from the LSP context.
dest-node-id node-id — The MPLS-TP global ID for the far end node of the LSP under test. If this is not
entered, then the dest-global-id is taken from the LSP context.
control-channel {none | non-ip} — The encapsulation format to use for the LSP Ping echo request and
echo reply packet.
Values none — IP encapsulation in an MPLS labeled packet
Values non-ip — MPLS-TP encapsulation without UDP/IP headers, in an MPLS-TP G-ACh on
the LSP using channel type 0x025.
Default non-ip
force — Allows LSP Ping to test a path that is operationally down, including cases where MPLS-TP BFD
CC/V is enabled and has taken a path down. This parameter is only allowed in the OAM context; it is
not allowed for a test configured as a part of an SAA.
Default disabled
path-type {active | working | protect} — The LSP path to test.
Default active
Values active — The currently active path. If MPLS-TP linear protection is configured on the
LSP, then this is the path that is selected by by MPLS-TP PSC protocol for sending user
plane traffic. If MPLS-TP linear protection is not configured, then this will be the wokring
path.
Values working — The working path of the MPLS-TP LSP.
Values protect — The protect path of the MPLS-TP LSP.
path path-name — The LSP path name along which to send the LSP ping request.
Values Any path name associated with the LSP.
Default The active LSP path.
src-ip-address ip-addr — Specifies the source IP address. This option is used when an OAM packet must be
generated from a different address than the node’s system interface address. An example is when the
OAM packet is sent over an LDP LSP and the LDP LSR-ID of the corresponding LDP session to the
next-hop is set to an address other than the system interface address.
fc fc-name — The fc and profile parameters are used to indicate the forwarding class and profile of the
MPLS echo request packet.
When an MPLS echo request packet is generated in CPM and is forwarded to the outgoing interface, the
packet is queued in the egress network queue corresponding to the specified fc and profile parameter
values. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing inter-
face.

When the MPLS echo request packet is received on the responding node, The fc and profile parameter
values are dictated by the LSP-EXP mappings of the incoming interface.
When an MPLS echo reply packet is generated in CPM and is forwarded to the outgoing interface, the
packet is queued in the egress network queue corresponding to the fc and profile parameter values deter-
mined by the classification of the echo request packet, which is being replied to, at the incoming inter-
face. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface.
The TOS byte is not modified. The following table summarizes this behavior:
Table 11: Request Packet and Behavior
cpm (sender node) echo request packet:

• packet{tos=1, fc1, profile1}
• fc1 and profile1 are as entered by user in OAM
command or default values
• tos1 as per mapping of {fc1, profile1} to IP
precedence in network egress QoS policy of outgoing
interface
outgoing interface (sender node) echo request packet:

• pkt queued as {fc1, profile1}
• ToS field=tos1 not remarked
• EXP=exp1, as per mapping of {fc1, profile1} to EXP
in network egress QoS policy of outgoing interface
Incoming interface (responder node) echo request packet:

• packet{tos1, exp1}
• exp1 mapped to {fc2, profile2} as per classification
in network QoS policy of incoming interface
cpm (responder node) echo reply packet:

outgoing interface (responder node) echo reply packet:

• ToS filed= tos1 not remarked (reply inband or out-of-
band)
• EXP=exp2, if reply is inband, remarked as per
mapping of {fc2, profile2} to EXP in network egress
QoS policy of outgoing interface
Incoming interface (sender node) echo reply packet:

• exp2 mapped to {fc1, profile1} as per classification
in network QoS policy of incoming interface
The LSP-EXP mappings on the receive network interface controls the mapping of the message reply

back at the originating router.be

Default be
src-ip-address ip-addr — This parameter specifies the source IP address. This parameter is used when an
OAM packet must be generated from a different address than the node's system interface address. For
example, when the OAM packet is sent over an LDP LSP and the LDP LSR-ID of the corresponding
LDP session to the next-hop is set to an address other than the system interface address.
profile {in | out} — The profile state of the MPLS echo request packet.
Default out
size octets — The MPLS echo request packet size in octets, expressed as a decimal integer. The request
payload is padded with zeroes to the specified size.
Values 1 — 9198
Default 1
ttl label-ttl — The TTL value for the MPLS label, expressed as a decimal integer.
Values 1 — 255
Default 255
send-count send-count — The number of messages to send, expressed as a decimal integer. The send-count
Values 1 — 100
Default 1
time-out interval — The time-out parameter in seconds, expressed as a decimal integer. This value is used
to override the default timeout value and is the amount of time that the router will wait for a message
reply after sending the last probe for a particular test. Upon the expiration of timeout the test will be
marked complete and no more packets will be processed for any of those request probes.
Values 1 — 10
Default 5
path-destination ip-address — Specifies the IP address of the path destination from the range 127/8.
interface interface-name — Specifies the name of an IP interface. The name must already exist in the con-
fig>router>interface context.
ipv4-address: a.b.c.d (host bits must be 0)prefix ip-prefix/mask — Specifies the address prefix and sub-
net mask of the target BGP IPv4 label route.

static lsp-name — Specifies an LSP ping route using the RFC 6426, MPLS On-Demand Connectivity Verifi-
cation and Route Tracing, Target FEC Stack code point Static LSP.
assoc-channel ipv4none|non-ip — Specifies the launched echo request’s usage of the Associated Channel
(ACH) mechanism, when testing an MPLS-TP LSP.
Values ipv4 — Use the
none — Use the Associated Channel mechanism described in RFC 6426, Section 3.3.
non-ip — Do not use an Associated Channel, as described in RFC 6426, Section 3.1.
dest-global-id global-id — Indicates the source MPLS-TP global identifier of the replying node. The value
is copied from the reply’s RFC 6426 Source Identifier TLV.
Values 0 — 4294967295
Default 0
dest-node-id node-id — Specifies the target MPLS-TP Node Identifier.
Values a.b.c.d | 1 — 4294967295>
Default 0
path-type active | working | protect — Specifies the type of an MPLS TP path.
Values active - test the currently-active path of the MPLS-TP LSP
working - test the primary path of the MPLS-TP LSP
protect - test the secondary path of the MPLS-TP LSP
Sample Output
A:DUTA# oam lsp-ping prefix 4.4.4.4/32 detail

LSP-PING 4.4.4.4/32: 80 bytes MPLS payload
Seq=1, send from intf dut1_to_dut3, reply from 4.4.4.4
udp-data-len=32 ttl=255 rtt=5.23ms rc=3 (EgressRtr)
---- LSP 4.4.4.4/32 PING Statistics ----

1 packets sent, 1 packets received, 0.00% packet loss
round-trip min = 5.23ms, avg = 5.23ms, max = 5.23ms, stddev = 0.000ms
===============================================================================
LDP LSR ID: 1.1.1.1
===============================================================================
Legend: U - Label In Use, N - Label Not In Use, W - Label Withdrawn
WP - Label Withdraw Pending, BU - Alternate For Fast Re-Route
===============================================================================
LDP Prefix Bindings
===============================================================================
Prefix IngLbl EgrLbl EgrIntf/ EgrNextHop
Peer LspId
-------------------------------------------------------------------------------
4.4.4.4/32 131069N 131067 1/1/1 1.3.1.2
3.3.3.3
4.4.4.4/32 131069U 131064 -- --
6.6.6.6
-------------------------------------------------------------------------------
No. of Prefix Bindings: 2
===============================================================================

A:DUTA#
lsp-trace
Syntax lsp-trace lsp-name [path path-name]
lsp-trace prefix ip-prefix/mask [path-destination ip-address [interface if-name | next-hop ip-
address]]
lsp-trace static lsp-name [assoc-channel ipv4|none|non-ip] [path-type active | working |
protect]
NOTE: Options common to all lsp-trace cases: [detail] [downstream-map-tlv downstream-map-

tlv] [fc fc-name [profile in|out]] [interval interval] [max-fail no-response-count] [max-ttl max-
label-ttl] [min-ttl min-label-ttl] [probe-count probes-per-hop] [size octets] [src-ip-address ip-
address] [timeout timeout]
Context oam
Description This command, when used with the static option, performs in-band on-demand LSP traceroute tests for
static MPLS-TP LSPs. For other LSP types, the static option should be excluded and these are described
elsewhere in this user guide.
The lsp-trace static command performs an LSP trace using the protocol and data structures defined in the
RFC 4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures, as extended by RFC
6426, MPLS On-Demand Connectivity Verification and Route Tracing.
The LSP trace operation is modeled after the IP traceroute utility which uses ICMP echo request and reply
packets with increasing TTL values to determine the hop-by-hop route to a destination IP.
In an LSP trace, the originating device creates an MPLS echo request packet for the LSP to be tested with
increasing values of the TTL in the outermost label. The MPLS echo request packet is sent through the data
plane and awaits a TTL exceeded response or the MPLS echo reply packet from the device terminating the
LSP. The devices that reply to the MPLS echo request packets with the TTL exceeded and the MPLS echo
reply are displayed.
In MPLS-TP, the echo request and echo reply messages are always sent in-band over the LSP, either in a G-
ACh channel or encapsulated as an IP packet below the LSP label.
path path-name — The LSP path name along which to send the LSP trace request.
control-channel {none | non-ip} — The encapsulation format to use for the MPLS echo request and echo

reply packet.
Values none — IP encapsulation in an MPLS labeled packet
Values non-ip — MPLS-TP encapsulation without UDP/IP headers, in an MPLS-TP G-ACh on
the LSP using channel type 0x025.
Default non-ip
size octets — The size in octets, expressed as a decimal integer, of the MPLS echo request packet, including
the IP header but not the label stack. The request pay-load is padded with zeroes to the specified size.
Note that an OAM command is not failed if the user entered a size lower than the minimum required to
build the packet for the echo request message. The payload is automatically padded to meet the mini-
mum size.
Values 1 — 9198
Default 1
src-ip-address ip-addr — Specifies the source IP address. This option is used when an OAM packet must be
generated from a different address than the node’s system interface address. An example is when the
OAM packet is sent over an LDP LSP and the LDP LSR-ID of the corresponding LDP session to the
next-hop is set to an address other than the system interface address.
min-ttl min-label-ttl — The minimum TTL value in the MPLS label for the LSP trace test, expressed as a
decimal integer.
Default 1
Values 1 — 255
max-ttl max-label-ttl — The maximum TTL value in the MPLS label for the LDP treetrace test, expressed
as a decimal integer.
Values 1 — 255
Default 30
max-fail no-response-count — The maximum number of consecutive MPLS echo requests, expressed as a
decimal integer that do not receive a reply before the trace operation fails for a given TTL.
Values 1 — 255
Default 5
Values 1 — 100
Default 1
assumes that the message response will not be received. A ‘request timeout’ message is displayed by the

CLI for each message request sent that expires. Any response received after the request times out will
be silently discarded.
Values 1 — 10
Default 3
Values 1 — 10
Default 1
downstream-map-tlv {ddmap | dsmap} — LSP Trace commands with this option can only be executed if
the control-channel is set to none. The DSMAP/DDMAP TLV is only included in the echo request mes-
sage if the egress interface is either a numbered IP interface, or an unnumbered IP interface. The TLV
will not be included if the egress interface is of type unnumbered-mpls-tp.
fc fc-name — The fc and profile parameters are used to indicate the forwarding class and profile of the
MPLS echo request packet.
When an MPLS echo request packet is generated in CPM and is forwarded to the outgoing interface, the
packet is queued in the egress network queue corresponding to the specified fc and profile parameter
values. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing inter-
face.
When the MPLS echo request packet is received on the responding node, The fc and profile parameter
values are dictated by the LSP-EXP mappings of the incoming interface.
When an MPLS echo reply packet is generated in CPM and is forwarded to the outgoing interface, the
packet is queued in the egress network queue corresponding to the fc and profile parameter values deter-
mined by the classification of the echo request packet, which is being replied to, at the incoming inter-
face. The marking of the packet's EXP is dictated by the LSP-EXP mappings on the outgoing interface.
The TOS byte is not modified. The following table summarizes this behavior:

Table 12: Request Packet and Behavior
cpm (sender node) echo request packet:

• fc1 and profile1 are as entered by user in OAM
command or default values
• tos1 as per mapping of {fc1, profile1} to IP precedence
in network egress QoS policy of outgoing interface
outgoing interface (sender node) echo request packet:

• ToS field=tos1 not remarked
• EXP=exp1, as per mapping of {fc1, profile1} to EXP in
network egress QoS policy of outgoing interface
Incoming interface (responder echo request packet:

node) • packet{tos1, exp1}
• exp1 mapped to {fc2, profile2} as per classification in
network QoS policy of incoming interface
cpm (responder node) echo reply packet:

outgoing interface (responder echo reply packet:

node) • pkt queued as {fc2, profile2}
• ToS filed= tos1 not remarked (reply inband or out-of-
band)
• EXP=exp2, if reply is inband, remarked as per mapping
of {fc2, profile2} to EXP in network egress QoS policy
of outgoing interface
Incoming interface (sender node) echo reply packet:

• exp2 mapped to {fc1, profile1} as per classification in
network QoS policy of incoming interface

Default be
profile {in | out} — The profile state of the MPLS echo request packet.
Default out
path-destination ip-address — Specifies the IP address of the path destination from the range 127/8.
interface interface-name — Specifies the name of an IP interface. The name must already exist in the
con-fig>router>interface context.

downstream-map-tlv {dsmap|ddmap|none} — Specifies which format of the downstream mapping TLV

to use in the LSP trace packet. The DSMAP TLV is the original format in RFC 4379. The DDMAP is
the new enhanced format specified in RFC 6424. The user can also choose not to include the down-
stream mapping TLV by entering the value none.
Default Inherited from global configuration of downstream mapping TLV in option mpls-echo-
request-downstream-map {dsmap | ddmap }.
Sample Output
*A:Dut-A# oam lsp-trace prefix 10.20.1.6/32 downstream-map-tlv ddmap path-destination

127.0.0.1 detail lsp-trace to 10.20.1.6/32: 0 hops min, 0 hops max, 152 byte packets
1 10.20.1.2 rtt=3.44ms rc=8(DSRtrMatchLabel) rsc=1
DS 1: ipaddr=127.0.0.1 ifaddr=0 iftype=ipv4Unnumbered MRU=1500
label[1]=131070 protocol=3(LDP)
3 10.20.1.6 rtt=7.63ms rc=3(EgressRtr) rsc=1 *A:Dut-A#
*A:Dut-C# oam lsp-trace "p_1" detail

lsp-trace to p_1: 0 hops min, 0 hops max, 116 byte packets
1 10.20.1.2 rtt=3.46ms rc=8(DSRtrMatchLabel)
DS 1: ipaddr 10.20.1.4 ifaddr 3 iftype 'ipv4Unnumbered' MRU=1500 label=131071
proto=4(RSVP-TE)
DS 1: ipaddr 10.20.1.6 ifaddr 3 iftype 'ipv4Unnumbered' MRU=1500 label=131071
proto=4(RSVP-TE)
3 10.20.1.6 rtt=5.68ms rc=3(EgressRtr)
*A:Dut-C#
lsp-trace over a numbered IP interface
A:DUTA#
A:DUTA# oam lsp-trace prefix 5.5.5.5/32 detail
lsp-trace to 5.5.5.5/32: 0 hops min, 0 hops max, 104 byte packets
DS 1: ipaddr=5.6.5.1 ifaddr=5.6.5.1 iftype=ipv4Numbered MRU=1564 label=131071
proto=3(LDP)
2 5.5.5.5 rtt=4.77ms rc=3(EgressRtr)
A:DUTA#
lsp-trace over an unnumbered IP interface
*A:Dut-A# oam lsp-trace prefix 10.20.1.6/32 downstream-map-tlv ddmap path-destination

127.0.0.1 detail lsp-trace to 10.20.1.6/32: 0 hops min, 0 hops max, 152 byte packets
3 10.20.1.6 rtt=7.63ms rc=3(EgressRtr) rsc=1 *A:Dut-A#

*A:Dut-A# oam ldp-treetrace prefix 10.20.1.6/32
ldp-treetrace for Prefix 10.20.1.6/32:
127.0.0.1, ttl = 3 dst = 127.1.0.255 rc = EgressRtr status = Done

Hops: 127.0.0.1 127.0.0.1
127.0.0.1, ttl = 3 dst = 127.2.0.255 rc = EgressRtr status = Done

Hops: 127.0.0.1 127.0.0.1
ldp-treetrace discovery state: Done

ldp-treetrace discovery status: ' OK '
Total number of discovered paths: 2
Total number of failed traces: 0

Service Diagnostics
sdp-mtu
Note: This command is not supported on 7210 SAS-M and 7210 SAS-T devices configured in Access uplink
mode.
Syntax sdp-mtu orig-sdp-id size-inc start-octets end-octets [step step-size] [timeout timeout] [interval
interval]
Context oam
Description Performs MTU Path tests on an SDP to determine the largest path-mtu supported on an SDP. The size-inc
parameter can be used to easily determine the path-mtu of a given SDP-ID. The forwarding class is
assumed to be Best-Effort Out-of-Profile. The message reply is returned with IP encapsulation from the far-
end 7210 SAS M. OAM request messages sent within an IP SDP must have the ‘DF’ IP header bit set to 1 to
prevent message fragmentation.
To terminate an sdp-mtu in progress, use the CLI break sequence <Ctrl-C>.
Special Cases SDP Path MTU Tests — SDP Path MTU tests can be performed using the sdp-mtu size-inc keyword to
easily determine the path-mtu of a given SDP-ID. The forwarding class is assumed to be Best-Effort Out-
of-Profile. The message reply is returned with IP encapsulation from the far-end 7210 SAS M.
With each OAM Echo Request sent using the size-inc parameter, a response line is displayed as message
output. The path MTU test displays incrementing packet sizes, the number sent at each size until a reply is
received and the response message.
As the request message is sent, its size value is displayed followed by a period for each request sent of that
size. Up to three requests will be sent unless a valid response is received for one of the requests at that size.
Once a response is received, the next size message is sent.
The response message indicates the result of the message request.
After the last reply has been received or response timeout, the maximum size message replied to indicates
the largest size OAM Request message that received a valid reply.
Parameters orig-sdp-id — The sdp-id to be used by sdp-ping, expressed as a decimal integer. The far-end address of the
specified sdp-id is the expected responder-id within each reply received. The specified sdp-id defines
the encapsulation of the SDP tunnel encapsulation used to reach the far end. This can be IP MPLS. If
orig-sdp-id is invalid or administratively down or unavailable for some reason, the SDP echo request
message is not sent and an appropriate error message is displayed (once the interval timer expires, sdp-
ping will attempt to send the next request if required).
Values 1 — 17407
size-inc start-octets end-octets — Indicates an incremental path MTU test will be performed with by send-
ing a series of message requests with increasing MTU sizes. The start-octets and end-octets parameters
are described below.
start-octets — The beginning size in octets of the first message sent for an incremental MTU test, expressed
Values 40 — 9198

end-octets — The ending size in octets of the last message sent for an incremental MTU test, expressed as a
decimal integer. The specified value must be greater than start-octets.
Values 40 — 9198
step step-size — The number of octets to increment the message size request for each message sent for an
incremental MTU test, expressed as a decimal integer. The next size message will not be sent until a
reply is received or three messages have timed out at the current size.
If the incremented size exceeds the end-octets value, no more messages will be sent.
Default 32
Values 1 — 512
Default 5
Values 1 — 10
Default 1
Values 1 — 10
Output Sample SDP MTU Path Test Sample Output
*A:Dut-A# oam sdp-mtu 1201 size-inc 512 3072 step 256

Size Sent Response
----------------------------
512 . Success
768 . Success
1024 . Success
1280 . Success
1536 . Success
1792 . Success
2048 . Success
2304 . Success
2560 . Success
2816 . Success
3072 . Success
Maximum Response Size: 3072

*A:Dut-A#

svc-ping
mode.
Syntax svc-ping ip-address [service service-id] [local-sdp] [remote-sdp]
Context <GLOBAL>
Description Tests a service ID for correct and consistent provisioning between two service end points.
The svc-ping command accepts a far-end IP address and a service-id for local and remote service testing.
The following information can be determined from svc-ping:
1. Local and remote service existence
2. Local and remote service state
3. Local and remote service type correlation
4. Local and remote customer association
5. Local and remote service-to-SDP bindings and state
6. Local and remote ingress and egress service label association
Unlike sdp-ping, only a single message will be sent per command; no count nor interval parameter is sup-
ported and round trip time is not calculated. A timeout value of 10 seconds is used before failing the request.
The forwarding class is assumed to be Best-Effort Out-of-Profile
If no request is sent or a reply is not received, all remote information will be shown as N/A.
To terminate a svc-ping in progress, use the CLI break sequence <Ctrl-C>.
Upon request timeout, message response, request termination, or request error the following local and
remote information will be displayed. Local and remote information will be dependent upon service exis-
tence and reception of reply.
Field Description Values
Request Result The result of the svc-ping request message. Sent - Request Timeout
Sent - Request Terminated
Sent - Reply Received
Not Sent - Non-Existent
Service-ID
SDP for Service
Not Sent - SDP For Service
Down
Not Sent - Non-existent
Service Egress Label
Service-ID The ID of the service being tested. service-id

Field Description Values (Continued)
Local Service Type The type of service being tested. If service-id does not exist Epipe
locally, N/A is displayed.
TLS
IES
Mirror-Dest
N/A
Local Service Admin The local administrative state of service-id. If the service does Admin-Up
State not exist locally, the administrative state will be Non-Existent.
Admin-Down
Non-Existent
Local Service Oper State The local operational state of service-id. If the service does not Oper-Up
exist locally, the state will be N/A.
Oper-Down
N/A
Remote Service Type The remote type of service being tested. If service-id does not Epipe, Ipipe
exist remotely, N/A is displayed.
TLS
IES
Mirror-Dest
N/A
Remote Service Admin The remote administrative state of service-id. If the service does Up
State not exist remotely, the administrative state is Non-Existent.
Down
Non-Existent
Local Service MTU The local service-mtu for service-id. If the service does not service-mtu
exist, N/A is displayed.
N/A
Remote Service MTU The remote service-mtu for service-id. If the service does not remote-service-mtu
exist remotely, N/A is displayed.
N/A
Local Customer ID The local customer-id associated with service-id. If the service customer-id
does not exist locally, N/A is displayed.
N/A
Remote Customer ID The remote customer-id associated with service-id. If the service customer-id
does not exist remotely, N/A is displayed.
N/A
Local Service IP The local system IP address used to terminate remotely config- system-ip-address
Address ured SDP-ID (as the far-end address). If an IP interface has not
N/A
been configured to be the system IP address, N/A is displayed.
Local Service IP Inter- The name of the local system IP interface. If the local system IP system-interface-name
face Name interface has not been created, N/A is displayed.
N/A

Local Service IP Inter- The state of the local system IP interface. If the local system IP Up
face State interface has not been created, Non-Existent is displayed.
Down
Non-Existent
Expected Far-end The expected IP address for the remote system IP interface. This orig-sdp-far-end-addr
Address must be the far-end address entered for the svc-ping command.
dest-ip-addr
N/A
Actual Far-end Address The returned remote IP address. If a response is not received, the resp-ip-addr
displayed value is N/A. If the far-end service IP interface is
N/A
down or non-existent, a message reply is not expected. sdp-ping
should also fail.
Responders Expected The expected source of the originator’s sdp-id from the perspec- resp-rec-tunnel-far-end-
Far-end Address tive of the remote router terminating the sdp-id. If the far-end address
cannot detect the expected source of the ingress sdp-id or the
N/A
request is transmitted outside the sdp-id, N/A is displayed.
Originating SDP-ID The sdp-id used to reach the far-end IP address if sdp-path is orig-sdp-id
defined. The originating sdp-id must be bound to the service-id
Non-Existent
and terminate on the far-end IP address. If an appropriate origi-
nating sdp-id is not found, Non-Existent is displayed.
Originating SDP-ID Whether the Originating router used the originating sdp-id to Yes
Path Used send the svc-ping request. If a valid originating sdp-id is found,
No
operational and has a valid egress service label, the originating
router should use the sdp-id as the requesting path if sdp-path N/A
has been defined. If the originating router uses the originating
sdp-id as the request path, Yes is displayed. If the originating
router does not use the originating sdp-id as the request path, No
is displayed. If the originating sdp-id is non-existent, N/A is dis-
played.
Originating SDP-ID The local administrative state of the originating sdp-id. If the Admin-Up
Administrative State sdp-id has been shutdown, Admin-Down is displayed. If the
Admin-Up
originating sdp-id is in the no shutdown state, Admin-Up is dis-
played. If an originating sdp-id is not found, N/A is displayed. N/A
Originating SDP-ID The local operational state of the originating sdp-id. If an origi- Oper-Up
Operating State nating sdp-id is not found, N/A is displayed.
Oper-Down
N/A
Originating SDP-ID The local administrative state of the originating sdp-ids binding Admin-Up
Binding Admin State to service-id. If an sdp-id is not bound to the service, N/A is dis-
Admin-Up
played.
N/A

Originating SDP-ID The local operational state of the originating sdp-ids binding to Oper-Up
Binding Oper State service-id. If an sdp-id is not bound to the service, N/A is dis-
Oper-Down
played.
N/A
Responding SDP-ID The sdp-id used by the far end to respond to the svc-ping resp-sdp-id
request. If the request was received without the sdp-path param-
Non-Existent
eter, the responding router will not use an sdp-id as the return
path, but the appropriate responding sdp-id will be displayed. If
a valid sdp-id return path is not found to the originating router
that is bound to the service-id, Non-Existent is displayed.
Responding SDP-ID Whether the responding router used the responding sdp-id to Yes
Path Used respond to the svc-ping request. If the request was received via
No
the originating sdp-id and a valid return sdp-id is found, opera-
tional and has a valid egress service label, the far-end router N/A
should use the sdp-id as the return sdp-id. If the far end uses the
responding sdp-id as the return path, Yes is displayed. If the far
end does not use the responding sdp-id as the return path, No is
displayed. If the responding sdp-id is non-existent, N/A is dis-
played.
Responding SDP-ID The administrative state of the far-end sdp-id associated with the Admin-Up
Administrative State return path for service-id. When a return path is administratively
Admin-Up
down, Admin-Down is displayed. If the return sdp-id is adminis-
tratively up, Admin-Up is displayed. If the responding sdp-id is N/A
non-existent, N/A is displayed.
Responding SDP-ID The operational state of the far-end sdp-id associated with the Oper-Up
Operational State return path for service-id. When a return path is operationally
Oper-Down
down, Oper-Down is displayed. If the return sdp-id is operation-
ally up, Oper-Up is displayed. If the responding sdp-id is non- N/A
existent, N/A is displayed.
Responding SDP-ID The local administrative state of the responder’s sdp-id binding Admin-Up
Binding Admin State to service-id. If an sdp-id is not bound to the service, N/A is dis-
Admin-Down
played.
N/A
Responding SDP-ID The local operational state of the responder’s sdp-id binding to Oper-Up
Binding Oper State service-id. If an sdp-id is not bound to the service, N/A is dis-
Oper-Down
played.
N/A
Originating VC-ID The originator’s VC-ID associated with the sdp-id to the far-end originator-vc-id
address that is bound to service-id. If the sdp-id signaling is off,
N/A
originator-vc-id is 0. If the originator-vc-id does not exist, N/A
is displayed.

Responding VC-ID The responder’s VC-ID associated with the sdp-id to originator- responder-vc-id
id that is bound to service-id. If the sdp-id signaling is off or the
N/A
service binding to sdp-id does not exist, responder-vc-id is 0. If a
response is not received, N/A is displayed.
Originating Egress Ser- The originating service label (VC-Label) associated with the egress-vc-label
vice Label service-id for the originating sdp-id. If service-id does not exist
N/A
locally, N/A is displayed. If service-id exists, but the egress ser-
vice label has not been assigned, Non-Existent is displayed. Non-Existent
Originating Egress Ser- The originating egress service label source. If the displayed Manual
vice Label Source egress service label is manually defined, Manual is displayed. If
Signaled
the egress service label is dynamically signaled, Signaled is dis-
played. If the service-id does not exist or the egress service label N/A
is non-existent, N/A is displayed.
Originating Egress Ser- The originating egress service label state. If the originating Up
vice Label State router considers the displayed egress service label operational,
Down
Up is displayed. If the originating router considers the egress
service label inoperative, Down is displayed. If the service-id N/A
does not exist or the egress service label is non-existent, N/A is
displayed.
Responding Service The actual responding service label in use by the far-end router rec-vc-label
Label for this service-id to the originating router. If service-id does not
N/A
exist in the remote router, N/A is displayed. If service-id does
exist remotely but the remote egress service label has not been Non-Existent
assigned, Non-Existent is displayed.
Responding Egress Ser- The responder’s egress service label source. If the responder’s Manual
vice Label Source egress service label is manually defined, Manual is displayed. If
Signaled
the responder’s egress service label is dynamically signaled, Sig-
naled is displayed. If the service-id does not exist on the N/A
responder or the responder’s egress service label is non-existent,
N/A is displayed.
Responding Service The responding egress service label state. If the responding Up
Label State router considers it is an egress service label operational, Up is
Down
displayed. If the responding router considers it is an egress ser-
vice label inoperative, Down is displayed. If the service-id does N/A
not exist or the responder’s egress service label is non-existent,
N/A is displayed.
Expected Ingress Ser- The locally assigned ingress service label. This is the service ingress-vc-label
vice Label label that the far-end is expected to use for service-id when send-
N/A
ing to the originating router. If service-id does not exist locally,
N/A is displayed. If service-id exists but an ingress service label Non-Existent
has not been assigned, Non-Existent is displayed.

Expected Ingress Label The originator’s ingress service label source. If the originator’s Manual
Source ingress service label is manually defined, Manual is displayed. If
Signaled
the originator’s ingress service label is dynamically signaled,
Signaled is displayed. If the service-id does not exist on the orig- N/A
inator or the originators ingress service label has not been
assigned, N/A is displayed.
Expected Ingress Ser- The originator’s ingress service label state. If the originating Up
vice Label State router considers it as an ingress service label operational, Up is
Down
displayed. If the originating router considers it as an ingress ser-
vice label inoperative, Down is displayed. If the service-id does N/A
not exist locally, N/A is displayed.
Responders Ingress Ser- The assigned ingress service label on the remote router. This is resp-ingress-vc-label
vice Label the service label that the far end is expecting to receive for
N/A
service-id when sending to the originating router. If service-id
does not exist in the remote router, N/A is displayed. If service- Non-Existent
id exists, but an ingress service label has not been assigned in the
remote router, Non-Existent is displayed.
Responders Ingress The assigned ingress service label source on the remote router. If Manual
Label Source the ingress service label is manually defined on the remote
Signaled
router, Manual is displayed. If the ingress service label is
dynamically signaled on the remote router, Signaled is dis- N/A
played. If the service-id does not exist on the remote router, N/A
is displayed.
Responders Ingress Ser- The assigned ingress service label state on the remote router. If Up
vice Label State the remote router considers it as an ingress service label opera-
Down
tional, Up is displayed. If the remote router considers it as an
ingress service label inoperative, Down is displayed. If the N/A
service-id does not exist on the remote router or the ingress ser-
vice label has not been assigned on the remote router, N/A is dis-
played.
Parameters ip-address — The far-end IP address to which to send the svc-ping request message in dotted decimal nota-
tion.
service service-id — The service ID of the service being tested must be indicated with this parameter. The
service ID need not exist on the local to receive a reply message.
Values 1 — 2147483647
local-sdp — Specifies the svc-ping request message should be sent using the same service tunnel encapsu-
lation labeling as service traffic. If local-sdp is specified, the command attempts to use an egress sdp-id
bound to the service with the specified far-end IP address with the VC-Label for the service. The far-
end address of the specified sdp-id is the expected responder-id within the reply received. The sdp-id
defines the encapsulation of the SDP tunnel encapsulation used to reach the far end; this can be IP or
MPLS. On originator egress, the service-ID must have an associated VC-Label to reach the far-end
address of the sdp-id and the sdp-id must be operational for the message to be sent.

If local-sdp is not specified, the svc-ping request message is sent with encapsulation with the OAM
label.
The following table indicates whether a message is sent and how the message is encapsulated based on
the state of the service ID.
Local Service State local-sdp Not Specified local-sdp Specified

Message Message Message Message
Sent Encapsulation Sent Encapsulation
Invalid Local Service Yes Generic IP/OAM (PLP) No None
No Valid SDP-ID Bound Yes Generic IP/OAM (PLP) No None
SDP-ID Valid But Down Yes Generic IP/OAM (PLP) No None
SDP-ID Valid and Up, But No Service Yes Generic IP/OAM (PLP) No None
Label
SDP-ID Valid, Up and Egress Service Yes Generic IP/OAM (PLP) Yes SDP Encapsulation
Label with Egress Service
Label (SLP)
remote-sdp — Specifies svc-ping reply message from the far-end should be sent using the same service
tunnel encapsulation labeling as service traffic.
If remote-sdp is specified, the far-end responder attempts to use an egress sdp-id bound to the service
with the message originator as the destination IP address with the VC-Label for the service. The sdp-id
defines the encapsulation of the SDP tunnel encapsulation used to reply to the originator; this can be IP
or MPLS. On responder egress, the service-ID must have an associated VC-Label to reach the originator
address of the sdp-id and the sdp-id must be operational for the message to be sent.
The following table indicates how the message response is encapsulated based on the state of the remote
service ID.

Remote Service State Message Encapsulation

remote-sdp remote-sdp
Not Specified Specified
Invalid Ingress Service Label Generic IP/GRE OAM (PLP) Generic IP/GRE OAM (PLP)
Invalid Service-ID Generic IP/GRE OAM (PLP) Generic IP/GRE OAM (PLP)
No Valid SDP-ID Bound on Service-ID Generic IP/GRE OAM (PLP) Generic IP/GRE OAM (PLP)
SDP-ID Valid But Down Generic IP/GRE OAM (PLP) Generic IP/GRE OAM (PLP)
SDP-ID Valid and Up, but No Service Label Generic IP/GRE OAM (PLP) Generic IP/GRE OAM (PLP)
SDP-ID Valid and Up, Egress Service Label, but Generic IP/GRE OAM (PLP) Generic IP/GRE OAM (PLP)
VC-ID Mismatch
SDP-ID Valid and Up, Egress Service Label, but Generic IP/GRE OAM (PLP) SDP Encapsulation with Egress
VC-ID Match Service Label (SLP)
Sample Output
A:ALU_G7X1>config# oam svc-ping 10.20.1.3 service 1

Service-ID: 1
Err Info Local Remote

-----------------------------------------------------
Type: EPIPE EPIPE
Admin State: Up Up
==> Oper State: Down Down
Service-MTU: 1514 1514
Customer ID: 1 1
IP Interface State: Up
Actual IP Addr: 10.20.1.1 10.20.1.3
Expected Peer IP: 10.20.1.3 10.20.1.1
SDP Path Used: No No

SDP-ID: 1 2
Admin State: Up Up
Operative State: Up Up
Binding Admin State:Up Up
Binding Oper State: Up Up
Binding VC ID: 10 10
Binding Type: Spoke Spoke
Binding Vc-type: Ether Ether
Binding Vlan-vc-tag:N/A N/A
Egress Label: 131070 131068

Ingress Label: 131068 131070
Egress Label Type: Signaled Signaled
Ingress Label Type: Signaled Signaled
Request Result: Send - Reply Received: Responder Service ID Oper-Down

A:ALU_G7X1>config#

vprn-ping
Syntax vprn-ping service-id source ip-address destination ip-address [fc fc-name [profile [in |
out]][size size] [ttl vc-label-ttl] [return-control] [interval interval] [send-count send-count]
[timeout timeout]
Context <GLOBAL>
Description This command performs a VPRN ping.
Parameters service service-id — The VPRN service ID to diagnose or manage.

source ip-address — The IP prefix for the source IP address in dotted decimal notation.
Values ipv4-address: 0.0.0.0 — 255.255.255.255
destination ip-address — The IP prefix for the destination IP address in dotted decimal notation.
Values 0.0.0.0 — 255.255.255.255
size octets — The OAM request packet size in octets, expressed as a decimal integer.
Values 1 — 9198
ttl vc-label-ttl — The TTL value in the VC label for the OAM request, expressed as a decimal integer.
Default 255
Values 1 — 255
return-control — Specifies the response to come on the control plane.
If the interval is set to 1 second where the timeout value is set to 10 seconds, then the maximum time
Default 1
Values 1 — 10 seconds
send-count send-count — The number of messages to send, expressed as a decimal integer. The count
Default 1
Values 1 — 100
override the default timeout value and is the amount of time that the router will wait for a message reply
after sending the message request. Upon the expiration of message timeout, the requesting router assumes

that the message response will not be received. Any response received after the request times out will be
silently discarded.
Default 5
Values 1 — 100
fc-name — The forwarding class of the MPLS echo request encapsulation.
Default be
profile {in | out} — The profile state of the MPLS echo request encapsulation.
Default out
Sample Output
A:PE_1# oam vprn-ping 25 source 10.4.128.1 destination 10.16.128.0

Sequence Node-id Reply-Path Size RTT
----------------------------------------------------------------------------
[Send request Seq. 1.]
1 10.128.0.3:cpm In-Band 100 0ms
----------------------------------------------------------------------------
...
A:PE_1#
----------------------------------------------------------------------------
A:PE_1#
vprn-trace
Syntax vprn-trace service-id source src-ip destination ip-address [fc fc-name [profile [in | out]] [size
size] [min-ttl vc-label-ttl] [max-ttl vc-label-ttl] [return-control] [probe-count probes-per-hop]
[interval seconds] [timeout timeout]
Context <GLOBAL>
Description Performs VPRN trace.
Parameters service service-id — The VPRN service ID to diagnose or manage.

source src-ip — The IP prefix for the source IP address in dotted decimal notation.
Values ipv4-address: 0.0.0.0 — 255.255.255.255
destination dst-ip — The IP prefix for the destination IP address in dotted decimal notation.
Values 0.0.0.0 — 255.255.255.255
size octets — The OAM request packet size in octets, expressed as a decimal integer.
min-ttl vc-label-ttl — The minimum TTL value in the VC label for the trace test, expressed as a decimal

integer.
Default 1
Values 1 — 255
max-ttl vc-label-ttl — The maximum TTL value in the VC label for the trace test, expressed as a decimal
integer.
Default 4
Values 1 — 255
return-control — Specifies the OAM reply to a data plane OAM request be sent using the control plane
instead of the data plane.
Default OAM reply sent using the data plane.
probe-count sendcount — The number of OAM requests sent for a particular TTL value, expressed as a
decimal integer.
Default 1
Values 1 — 10
interval seconds — The interval parameter in seconds, expressed as a decimal integer. This parameter is
Default 1
Values 1 — 10 seconds
Default 3
Values 1 — 60
Default be
profile {in | out} — The profile state of the MPLS echo request encapsulation.
Default out
Sample Output
A:PE_1# oam vprn-trace 25 source 10.4.128.1 destination 10.16.128.0

TTL Seq Reply Node-id Rcvd-on Reply-Path RTT

----------------------------------------------------------------------------
[Send request TTL: 1, Seq. 1.]
1 1 1 10.128.0.4 cpm In-Band 0ms
Requestor 10.128.0.1 Route: 0.0.0.0/0
Vpn Label: 131071 Metrics 0 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:65100:1
Responder 10.128.0.4 Route: 10.16.128.0/24

2 1 1 10.128.0.3 cpm In-Band 0ms
Requestor 10.128.0.1 Route: 0.0.0.0/0
Responder 10.128.0.3 Route: 10.16.128.0/24
Vpn Label: 0 Metrics 0 Pref 0 Owner local
Next Hops: [1] ifIdx 2 nextHopIp 10.16.128.0

...
----------------------------------------------------------------------------
A:PE_1#


Note: VPLS MAC diagnostics commands are not supported on 7210 SAS-M and 7210 SAS-T devices con-
figured in Access uplink mode.
cpe-ping
Syntax cpe-ping service service-id destination ip-address source ip-address [ttl vc-label-ttl] [return-
control] [source-mac ieee-address] [fc fc-name] [interval interval] [count send-count] [send-
control]
Context oam
Description This ping utility determines the IP connectivity to a CPE within a specified VPLS service.
Parameters service service-id — The service ID of the service to diagnose or manage.

destination ip-address — Specifies the IP address to be used as the destination for performing an OAM
ping operations.
source ip-address — Specify an unused IP address in the same network that is associated with the VPLS.
ttl vc-label-ttl — The TTL value in the VC label for the OAM MAC request, expressed as a decimal integer.
Default 255
Values 1 — 255
return-control — Specifies the MAC OAM reply to a data plane MAC OAM request be sent using the con-
trol plane instead of the data plane.
Default MAC OAM reply sent using the data plane.
source-mac ieee-address — Specify the source MAC address that will be sent to the CPE. If not specified
or set to 0, the MAC address configured for the CPM is used.
Default be

Default 1
Values 1 — 10
count send-count — The number of messages to send, expressed as a decimal integer. The count parameter
is used to override the default number of message requests sent. Each message request must either time-
out or receive a reply before the next message request is sent. The message interval value must be
expired before the next message request is sent.
Default 1
Values 1 — 100
send-control — Specifies the MAC OAM request be sent using the control plane instead of the data plane.
Default MAC OAM request sent using the data plane.
mac-populate
Syntax mac-populate service-id mac ieee-address [flood] [age seconds] [force] [target-sap sap-id]
[send-control]
Context oam
Description This command populates the FIB with an OAM-type MAC entry indicating the node is the egress node for
the MAC address and optionally floods the OAM MAC association throughout the service. The mac-popu-
late command installs an OAM MAC into the service FIB indicating the device is the egress node for a par-
ticular MAC address. The MAC address can be bound to a particular SAP (the target-sap) or can be
associated with the control plane in that any data destined to the MAC address is forwarded to the control
plane (cpm). As a result, if the service on the node has neither a FIB nor an egress SAP, then it is not allowed
to initiate a mac-populate.
The MAC address that is populated in the FIBs in the provider network is given a type OAM, so that it can
be treated distinctly from regular dynamically learned or statically configured MACs. Note that OAM MAC
addresses are operational MAC addresses and are not saved in the device configuration. An exec file can be
used to define OAM MACs after system initialization.
The force option in mac-populate forces the MAC in the table to be type OAM in the case it already exists
as a dynamic, static or an OAM induced learned MAC with some other type binding.
An OAM-type MAC cannot be overwritten by dynamic learning and allows customer packets with the MAC
to either ingress or egress the network while still using the OAM MAC entry.
The flood option causes each upstream node to learn the MAC (that is, populate the local FIB with an OAM
MAC entry) and to flood the request along the data plane using the flooding domain.The flooded mac-pop-
ulate request can be sent via the data plane or the control plane. The send-control option specifies the
request be sent using the control plane. If send-control is not specified, the request is sent using the data
plane.
An age can be provided to age a particular OAM MAC using a specific interval. By default, OAM MAC
addresses are not aged and can be removed with a mac-purge or with an FDB clear operation.
When split horizon group (SHG) is configured, the flooding domain depends on which SHG the packet orig-
inates from. The target-sap sap-id value dictates the originating SHG information.

Parameters service service-id — The Service ID of the service to diagnose or manage.

Values 1 — 2147483647
destination ieee-address — The MAC address to be populated.
flood — Sends the OAM MAC populate to all upstream nodes.
Default MAC populate only the local FIB.
age seconds — The age for the OAM MAC, expressed as a decimal integer.
Default The OAM MAC does not age.
Values 1 — 65535
force — Converts the MAC to an OAM MAC even if it currently another type of MAC.
Default Do not overwrite type.
target-sap sap-id — The local target SAP bound to a service on which to associate the OAM MAC. By
default, the OAM MAC is associated with the control place, that is, it is associated with the CPU on the
router.
When the target-sap sap-id value is not specified the MAC is bound to the CPM. The originating SHG
is 0 (zero). When the target-sap sap-id value is specified, the originating SHG is the SHG of the target-
sap.
Default Associate OAM MAC with the control plane (CPU).
mac-purge
Syntax mac-purge service-id target ieee-address [flood] [send-control] [register]
Context oam
Description This command removes an OAM-type MAC entry from the FIB and optionally floods the OAM MAC
removal throughout the service. A mac-purge can be sent via the forwarding path or via the control plane.
When sending the MAC purge using the data plane, the TTL in the VC label is set to 1. When sending the
MAC purge using the control plane, the packet is sent directly to the system IP address of the next hop.
A MAC address is purged only if it is marked as OAM. A mac-purge request is an HVPLS OAM packet,
with the following fields. The Reply Flags is set to 0 (since no reply is expected), the Reply Mode and
Reserved fields are set to 0. The Ethernet header has source set to the (system) MAC address, the destination
set to the broadcast MAC address. There is a VPN TLV in the FEC Stack TLV to identify the service
domain.
If the register option is provided, the R bit in the Address Delete flags is turned on.
The flood option causes each upstream node to be sent the OAM MAC delete request and to flood the
request along the data plane using the flooding domain. The flooded mac-purge request can be sent via the
data plane or the control plane. The send-control option specifies the request be sent using the control plane.
If send-control is not specified, the request is sent using the data plane.
The register option reserves the MAC for OAM testing where it is no longer an active MAC in the FIB for
forwarding, but it is retained in the FIB as a registered OAM MAC. Registering an OAM MAC prevents

relearns for the MAC based on customer packets. Relearning a registered MAC can only be done through a
mac-populate request. The originating SHG is always 0 (zero).

Values 1 — 2147483647
target ieee-address — The MAC address to be purged.
flood — Sends the OAM MAC purge to all upstream nodes.
Default MAC purge only the local FIB.
send-control — Send the mac-purge request using the control plane.
Default Request is sent using the data plane.
register — Reserve the MAC for OAM testing.
Default Do not register OAM MAC.
mac-ping
Syntax mac-ping service service-id destination dst-ieee-address [source src-ieee-address] [fc fc-
name] [size octets] [ttl vc-label-ttl] [count send-count] [send-control] [return-control] [interval
interval] [timeout timeout]
Context oam
Description The mac-ping utility is used to determine the existence of an egress SAP binding of a given MAC within a
VPLS service.
A mac-ping packet can be sent via the control plane or the data plane. The send-control option specifies the
plane.
A mac-ping is forwarded along the flooding domain if no MAC address bindings exist. If MAC address
bindings exist, then the packet is forwarded along those paths, provided they are active. A response is gener-
ated only when there is an egress SAP binding for that MAC address or if the MAC address is a “local”
OAM MAC address associated with the device’s control plan.
A mac-ping reply can be sent using the data plane or the control plane. The return-control option specifies
the reply be sent using the control plane. If return-control is not specified, the request is sent using the data
plane.
A mac-ping with data plane reply can only be initiated on nodes that can have an egress MAC address bind-
ing. A node without a FIB and without any SAPs cannot have an egress MAC address binding, so it is not a
node where replies in the data plane will be trapped and sent up to the control plane.
A control plane request is responded to via a control plane reply only.
By default, MAC OAM requests are sent with the system or chassis MAC address as the source MAC. The
source option allows overriding of the default source MAC for the request with a specific MAC address.
When a source ieee-address value is specified and the source MAC address is locally registered within a
split horizon group (SHG), then this SHG membership will be used as if the packet originated from this

SHG. In all other cases, SHG 0 (zero) will be used. Note that if the mac-trace is originated from a non-zero
SHG, such packets will not go out to the same SHG.
If EMG is enabled, mac-ping will return only the first SAP in each chain.

Values 1 — 2147483647
destination ieee-address — The destination MAC address for the OAM MAC request.
size octets — The MAC OAM request packet size in octets, expressed as a decimal integer. The request
payload is padded to the specified size with a 6 byte PAD header and a byte payload of 0xAA as necessary.
If the octet size specified is less than the minimum packet, the minimum sized packet necessary to send the
request is used.
Default No OAM packet padding.
Values 1 — 9198
Default 255
Values 1 — 255
source src-ieee-address — The source MAC address from which the OAM MAC request originates. By
default, the system MAC address for the chassis is used.
Default The system MAC address.
Values Any unicast MAC value.
fc fc-name — The fc parameter is used to test the forwarding class of the MPLS echo request packets. The
actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
Default 1
Values 1 — 10

Default 1
Values 1 — 100
Default 5
Values 1 — 10
mac-trace
Syntax mac-trace service service-id destination ieee-address [size octets] [min-ttl vc-label-ttl] [max-ttl
vc-label-ttl] [send-control] [return-control] [source ieee-address] [z-count probes-per-hop]
[interval interval] [timeout timeout]
Context oam
Description This command displays the hop-by-hop path for a destination MAC address within a VPLS.
The MAC traceroute operation is modeled after the IP traceroute utility which uses ICMP echo request and
reply packets with increasing TTL values to determine the hop-by-hop route to a destination IP. The MAC
traceroute command uses Alcatel-Lucent OAM packets with increasing TTL values to determine the hop-
by-hop route to a destination MAC.
In a MAC traceroute, the originating device creates a MAC ping echo request packet for the MAC to be
tested with increasing values of the TTL. The echo request packet is sent through the control plane or data
plane and awaits a TTL exceeded response or the echo reply packet from the device with the destination
MAC. The devices that reply to the echo request packets with the TTL exceeded and the echo reply are dis-
played.
SHG. In all other cases, SHG 0 (zero) will be used. Note that if the mac-ping is originated from a non-zero
If EMG is enabled, mac-trace will return only the first SAP in each chain.
Parameters service service-id — The Service ID of the service to diagnose or manage.

Values 1 — 2147483647
destination ieee-address — The destination MAC address to be traced.

request is used.
Values 1 — 9198
min-ttl vc-label-ttl — The minimum TTL value in the VC label for the MAC trace test, expressed as a deci-
mal integer.
Default 1
Values 1 — 255
max-ttl vc-label-ttl — The maximum TTL value in the VC label for the MAC trace test, expressed as a dec-
imal integer.
Default 4
Values 1 — 255
source ieee-address — The source MAC address from which the OAM MAC request originates. By default,
the system MAC address for the chassis is used.
send-count send-count — The number of MAC OAM requests sent for a particular TTL value, expressed as
a decimal integer.
Default 1
Values 1 — 10
Default 1
Values 1 — 10

Default 5
Values 1 — 60

EFM Commands
efm
Syntax port-id
Context oam>efm
Description This command enables Ethernet in the First Mile (EFM) OAM tests loopback tests on the specified port. The
EFM OAM remote loopback OAMPDU will be sent to the peering device to trigger remote loopback.
Parameters port-id — Specify the port ID in the slot/mda/port format.
local-loopback
Syntax local-loopback {start | stop}
Context oam>efm
Description This command enables local loopback tests on the specified port.
remote-loopback
Syntax remote-loopback {start | stop}
Context oam>efm
Description This command enables remote Ethernet in the First Mile (EFM) OAM loopback tests on the specified port.
The EFM OAM remote loopback OAMPDU will be sent to the peering device to trigger remote loopback.

ETH-CFM OAM Commands
linktrace
Syntax linktrace mac-address mep mep-id domain md-index association ma-index [ttl ttl-value]
Context oam>eth-cfm
Default The command specifies to initiate a linktrace test.
Parameters mac-address — Specifies a unicast destination MAC address.

mep mep-id — Specifies the target MAC address.
Values 1 — 8191
domain md-index — Specifies the MD index.
Values 1 — 4294967295
association ma-index — Specifies the MA index.
Values 1 — 4294967295
ttl ttl-value — Specifies the TTL for a returned linktrace.
Values 0 — 255
Default 64
loopback
Syntax loopback mac-address mep mep-id domain md-index association ma-index [send-count send-
count] [size data-size] [priority priority]
Context oam>eth-cfm
Default The command specifies to initiate a loopback test.

Parameters mac-address — Specifies a unicast MAC address.
mep mep-id — Specifies target MAC address.
Values 1 — 8191
Values 1 — 4294967295
Values 1 — 4294967295
send-count send-count — Specifies the number of messages to send, expressed as a decimal integer. Loop-
back messages are sent back to back, with no delay between the transmissions.

Default 1
Values 1—5
size data-size — This is the size of the data portion of the data TLV. If 0 is specified no data TLV is added to
the packet.
Values 0 — 1500
priority priority — Specifies a 3-bit value to be used in the VLAN tag, if present, in the transmitted frame.
Values 0—7
eth-test
Syntax mac-address mep mep-id domain md-index association ma-index [priority priority] [data-length
data-length]
Context oam>eth-cfm
Description This command issues an ETH-CFM test.

Values 1 — 8191
Values 1 — 4294967295
Values 1 — 4294967295
data-length data-length — Indicates the UDP data length of the echo reply, the length starting after the IP
header of the echo reply.
Values 64 — 1500
Default 64
priority priority — Specifies the priority.
Values 0— 7
Default The CCM and LTM priority of the MEP

one-way-delay-test
Syntax one-way-delay-test mac-address mep mep-id domain md-index association ma-index [priority
priority]
Context oam>eth-cfm
Description This command issues an ETH-CFM one-way delay test.

Values 1 — 8191
Values 1 — 4294967295
Values 1 — 4294967295
Values 0—7
Default The CCM and LTM priority of the MEP.
two-way-delay-test
Syntax two-way-delay-test mac-address mep mep-id domain md-index association ma-index [priority
priority]
Context oam>eth-cfm
Description This command issues an ETH-CFM two-way delay test.

Values 1 — 8191
Values 1 — 4294967295
Values 1 — 4294967295
Values 0—7
Default The CCM and LTM priority of the MEP.

two-way-slm-test
Syntax two-way-slm-test mac-address mep mep-id domain md-index association ma-index [fc {fc-
name} [profile {in|out}]] [send-count send-count] [size data-size] [timeout timeout] [interval
interval]
Context oam>eth-cfm
Description This command configures an Ethernet CFM two-way SLM test in SAA.
mac-address — Specifies a unicast destination MAC address.
Values 1 — 8191
Values 1 — 4294967295
Values 1 — 4294967295
fc fc-name — Specifies the forwarding class of the MPLS echo request packets.
Default nc
profile {in | out} — Specifies the profile value to be used with the forwarding class specified in the fc-name
parameter.
Default in
Default 1
Values 1 — 100
the packet.
Default 0
Values 0 — 1500
override the default timeout value and is the amount of time that the router waits for a reply message
after sending the message request. Upon the expiration of message timeout, the requesting router
assumes that the message response is not received. Any response received after the request times out is
silently discarded.

Default 5
Values 1 — 10
Default 5
Values [0.1, 0.2, .. 0.9] | [1, 2, .. 10]

Testhead Commands
test-oam
Syntax test-oam
Context config
Description This command enables the context to configure Operations, Administration, and Maintenance test parame-
ters
testhead-profile
Syntax testhead-profile profile-id create
Context config> test-oam
Description Provides the context to the create service testhead profiles which is used by the Y.1564/RFC 2544 testhead
(also known as, traffic generator) OAM tool. A service testhead profile allows user to configure the parme-
ters such as contents of the frame payload that is generated by traffic generator, the size of the frame, test
duration, test acceptance criteria, and other criteria to be used by the testhead tool.
The profile is used the testhead OAM tool to generate the appropriate frame at the configured rate and mea-
sure the performance parameters (FD, FDV, and loss). At the end of the test run, the tool compares the mea-
sured values against the test acceptance criteria that is configured in the profile to determine if the service is
within bounds of the acceptance criteria or not.
The no form the command removes user created profile from the system.
Default none
Parameters profile-id — Identifies the profile.

Values 1-10
description
Syntax description profile-description
Context config> test-oam>testhead-profile
Description Allows user to associate a description with profile.

The no form the command removes description.
Default none

Parameters profile-description — Provides a way to add a description to the profile based on it use or as per user choice.
Values ASCII string
rate cir
Syntax [no] rate cir-rate-in-kbps [cir-adaptation-rule adaptation-rule] [pir cir-rate-in-kbps]
Description The testhead tool generates traffic up to the configured CIR rate, if the PIR rate is not specified. In other
words, CIR rate specifies the bandwidth or throughput the user needs to validate. User can specify the
optional PIR rate. If the PIR rate is specified, it needs to be greater than or equal to the CIR rate and the tes-
thead generates traffic up to the configured PIR rate.
The cir-adaptation-rule parameter rule can be specified to let the system derive the operational hardware
rate for both the CIR and PIR rate. This allows the software to find the best operational rate based on the
user specified constraint and the hardware based rate steps supported on the platform. For more information
about the hardware rate steps supported for meters on different platforms, see the “7210 SAS QoS User
Guide”.
The no form of the command sets the CIR to default and PIR is not set. If the test is run after executing no
rate command, the test generates traffic up to CIR rate. If PIR rate is specified, it must be greater than or
equal to the CIR rate.
Default rate cir 1000kbps adaptation-rule closest
Parameters cir-rate — The cir parameter overrides the default administrative CIR to use. When the rate command has
not been executed or the cir parameter is not explicitly specified, the default CIR is assumed. Fractional
values are not allowed and must be given as a positive integer. The actual CIR rate is dependent on the
meter’s adaptation-rule parameters and the hardware. It is specified in kilo-bits per second (kbps).
Values 0 — 10000000, max
adaptation-rule — Defines the constraints enforced when adapting the CIR and PIR rate defined with the
rate command to the hardware rates supported by the platform. This parameter requires a qualifier that
defines the constraint used when deriving the operational CIR and PIR value. If this parameter is not
specified then the default adaptation-rule closest is applied.
Values [closest|max|min]
max - The max (maximum) option is mutually exclusive with the min and closest options.
When max is defined, the operational CIR will be the next multiple of the hardware step-
size that is equal to or lesser than the specified rate. The hardware step-size is determined
by the configured administrative CIR and varies based on the platform.
min - The min (minimum) option is mutually exclusive with the max and closest options.
When min is defined, the operational PIR will be the next multiple of the hardware step-
size that is equal to or lesser than the specified rate. The hardware step-size is determined
by the configured administrative CIR and varies based on the platform.
closest - The closest parameter is mutually exclusive with the min and max parameter.

When closest is defined, the operational CIR will be the next multiple of the hardware
step-size that is equal to or lesser than the specified rate. The hardware step-size is
determined by the configured administrative CIR and varies based on the platform.
pir-rate — The pir parameter overrides the default administrative PIR to use. When the rate command has
not been executed or the PIR parameter is not explicitly specified, the default PIR is assumed. Frac-
tional values are not allowed and must be given as a positive integer. The actual PIR rate is dependent
on the meter’s adaptation-rule parameters and the hardware. The value is specified in kilo-bits per sec-
ond (kbps).
Values 0 — 10000000, max
test-duration
Syntax test-duration [hours 0 - 24] [minutes 0 — 60] [seconds 0 — 60]

Description This command allows the user to specify the total test duration to be used for throughput measurement. The
CLI parameters, hours, minutes, and seconds, allows the user to specify the number of hours, number of
minutes and number of seconds to used for throughput measurement. User can specify all the parameters
together. If all the parameters are specified together then the total test duration is set to the sum of the values
specified for hours, minutes and seconds.
The no form of the command sets the value to the default value
Default no test-duration (sets the test duration for 3 minutes).

Parameters hours — The total number of hours to run the test. The total test duration is determined by the sum of the
hours, minutes and seconds specified by the user.
Values 0 - 24
minutes — The total number of minutes to run the test. The total test duration is determined by the sum of
the hours, minutes and seconds specified by the user.
Values 0 — 60
seconds — The total number of seconds to run the test. The total test duration is determined by the sum of
the hours, minutes and seconds specified by the user.
Values 0 — 60

frame-size
Syntax [no] frame-size [64..9212]
Description This command allows the user to specify the frame size of the packets generated by the testhead tool. Any
frame size in the given range can be specified.
The no form of the command sets the value to the default value
Default no frame-size - set to a default value of 1514 bytes.
Parameters frame-size — The size of the frame generated by the testhead tool. Choose from among the value allowed in
the available range.
Values 64 … 9212
acceptance-criteria
Syntax [no] acceptance-criteria acceptance-criteria-id create
Context configure> test-oam> testhead-profile

Description This command provides the context to specify the test acceptance criteria to be used by the testhead OAM
tool to declare the PASS/FAIL result at the completion of the test.
User can create upto 4 different acceptance criteria per profile to measure different SLA needs. User has an
option to specify only one of the acceptance criteria to be specified with the testhead OAM tool during the
invocation of the test.
The no form of the command removes the test acceptance criteria.
Default no defaults
Parameters acceptance-criteria-id — A number to identify the test acceptance criteria. It is a decimal number used to
identify the test acceptance criteria and to use when starting the throughput test.
Values 1- 4
cir-threshold
Syntax [no] cir-threshold cir-threshold
Context configure> test-oam> testhead-profile> acceptance-criteria
Description The specified value for the CIR rate is compared with the measured CIR rate at the end of the test to declare
the test result. If the measured value is greater than the specified value the test is declared as ‘PASS’, else it
is considered to be ‘FAIL’.

The no form of the command disables the comparison of the parameter with the measured value at the end of
the test. Basically, the threshold value is ignored and not considered for declaring the test result.
Default no cir-threshold
Parameters threshold — Specifies the value for comparison with measured value
Values 0 – 1000000kbps
pir-threshold
Syntax [no] pir-threshold pir-threshold
Description The specified value for the PIR rate is compared with the measured PIR rate at the end of the test to declare
the test result. If the measured value is greater than the specified value the test is declared as ‘PASS’, else it
is considered to be ‘FAIL’.
Default no pir-threshold
Parameters threshold — Specifies the value for comparison with measured value
Values 0 – 1000000kbps
latency-rising-threshold
Syntax [no] latency-rising-threshold threshold
Description The specified value for the latency is compared with the measured latency at the end of the test to declare the
test result. If the measured value is greater than the specified value the test is declared as ‘FAIL’, else it is
considered to be ‘PASS’.
Default no latency-rising-threshold
Parameters threshold — Specifies the value for comparison with measured value.
Values [0..2147483000], Specified in microseconds.

latency-rising-threshold-in
Syntax [no] latency-rising-threshold-in in-profile-threshold
Description The specified value for the latency is compared with the measured latency for green/in-profile packets at the
end of the test to declare the test result. If the measured value is greater than the specified value the test is
declared as ‘FAIL’, else it is considered to be ‘PASS’.
Default no latency-rising-threshold-in
Parameters In-profile-threshold — Specifies the value for comparison with measured value
latency-rising-threshold-out
Syntax [no] latency-rising-threshold out-profile-threshold

Description The specified value for the latency is compared with the measured latency of yellow or out-of-profile pack-
ets at the end of the test to declare the test result. If the measured value is greater than the specified value the
test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
Default no latency-rising-threshold-out
Parameters out-profile-threshold — Specifies the value for comparison with measured value
jitter-rising-threshold
Syntax [no] jitter-rising-threshold threshold

Description The specified value for the jitter is compared with the measured jitter at the end of the test to declare the test
result. If the measured value is greater than the specified value the test is declared as ‘FAIL’, else it is consid-
ered to be ‘PASS’.

Default no jitter-rising-threshold
jitter-rising-threshold-in
Syntax [no] jitter-rising-threshold-in in-profile-threshold
Description The specified value for the jitter is compared with the measured jitter for green/in-profile packets at the end
of the test to declare the test result. If the measured value is greater than the specified value the test is
Default no jitter-rising-threshold-in
Parameters In-profile-threshold — Specifies the value for comparison with measured value
jitter-rising-threshold-out
Syntax [no] jitter-rising-threshold-out out-profile-threshold

Description The specified value for the jitter is compared with the measured jitter for yellow/out-of-profile packets at the
end of the test to declare the test result. If the measured value is greater than the specified value the test is
Default no jitter-rising-threshold-out

loss-rising-threshold
Syntax [no] loss-rising-threshold threshold
Description The specified value for the Frame Loss Ratio (FLR) is compared with the measured FLR at the end of the
test to declare the test result. If the measured value is greater than the specified value the test is declared as
‘FAIL’, else it is considered to be ‘PASS’.
Frame Loss Ratio is computed as a ratio of the difference of number of received frames to number of
injected or sent frames divided by the number of sent frames.
Default no loss-rising-threshold
Values 1 – 1000000, Loss-rising-threshold is specified as a number which denotes one ten-
thousandth (1/10000) of a percent. For example, specifying a value of 1 is equivalent to
0.0001%, and specifying a value of 10000 is equivalent to 1%.
loss-rising-threshold-in
Syntax [no] loss-rising-threshold-in in-profile-threshold
Description The specified value for the frame loss ratio (FLR) is compared with the measured FLR for green or in-pro-
file packets at the end of the test to declare the test result. If the measured value is greater than the specified
value the test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
Frame Loss Ratio for green/in-profile packets is computed as a ratio of the difference of number of received
green or in-profile frames to number of injected/sent green/in-profile frames divided by the number of sent
green frames.
Default no loss-rising-threshold-in
Parameters in-profile-threshold — Specifies the value for comparison with measured value

loss-rising-threshold-out
Syntax [no] loss-rising-threshold-out out-profile-threshold
Description The specified value for the frame loss ratio (FLR) is compared with the measured FLR for yellow/out-of-
profile packets at the end of the test to declare the test result. If the measured value is greater than the speci-
fied value the test is declared as ‘FAIL’, else it is considered to be ‘PASS’.
Frame Loss ratio for yellow/out-of-profile packets is computed as a ratio of the difference of number of
received yellow frames to number of injected/sent yellow frames divided by the number of sent yellow
frames.
Default no loss-rising-threshold
test-completion-trap-enable
Syntax [no] test-completion-trap-enable
Description Executing this command allows the user to specify that the test completion trap needs to be generated after
the completion of the test or if the test is stopped. The trap contains the details of test configuration, the mea-
sured values, test completion status and PASS/FAIL result.
The no form of the command disables the generation of the event/log/trap after test completion.
Default no test-completion-trap-enable – that is, trap is not generated on completion of the test.
dot1p
Syntax [no] dot1p in-profile dot1p-value out-of-profile dot1p-value

Description This command allows the user to configure the Dot1p values to identify the in-profile or green packets and
out-of-profile or yellow packets. The values configured using this command are used by the testhead tool on
the local end (that is, the node on which the testhead tool is executed) to match the dot1p values received in
the packet header and identify green and yellow packets and appropriately account the packets. These values
are used only when the testhead tool is invoked with the parameter color-aware is set to ‘enable’.

The dot1p in-profile value (that is, packets with dot1p values in the L2 header equal to the dot1p-in-profile
value configured is considered to be in-profile or green packet) is used to count the number of in-profile
packets and measure the latency, jitter, and FLR for in-profile packets. Similarly, the dot1p out-profile is
used to count the total out-of-profile or yellow packets and measure latency, jitter, and FLR for out-of-pro-
file or yellow packets.
While the testhead tool is initiated, if color-aware is set to enable and no values are specified (that is, the no
form of the command is used in the profile), the CLI gives an error. If values are specified, then the config-
ured values are used to match and identify in-profile and out-of-profile packets.
The no form of the command disables the use of dot1p to identify a green or yellow packet.
Note: Testhead OAM tool does not mark the packets below CIR as in-profile packets and packets above CIR
and below PIR as out-of-profile packets using the Dot1p or DSCP or other packet header bits to indicate the
color of the packet (for example: DEI bit), as the 7210 SAS access SAP ingress does not support color-aware
metering. It is used to only identify green and yellow packets and maintain a count of received green and
yellow packets when the tests are run in color-aware mode.
Default The no form of this command is the default. There are no defaults for the dot1p values.
Parameters in-profile dot1p-value — Specifies the dot1p value used to identify green or in-profile packets. It must be
different than the value configured for yellow or out-of-profile packets.
Values 0-7
out-profile dot1p-value — Specifies the dot1p value used to identify green or out-of-profile packets. It must
be different than the value configured for green or in-profile packets.
Values 0-7
frame-payload
Syntax [no] frame-payload frame-payload-id [payload-type [l2|tcp-ipv4|udp-ipv4|ipv4] create
Description This command provides the context to specify the packet header values to be used in frames generated by
testhead tool.
User can create up to 4 different types of frame payload representing different kinds of traffic, within a pro-
file. User chooses one among these when starting the throughput test.
The parameter payload-type determines the packet header fields that are used to populate the frame gener-
ated by the testhead OAM tool. The packet header fields use the value from the parameters configured under
the frame-payload. For example, when the payload-type is configured as “l2”, software uses the parameters
src-mac, dst-mac, vlan-tag-1 (if configured), vlan-tag-2 (if configured), ethertype, and data-pattern. See
below for parameters used when other values are specified with payload-type.
The no form of the command removes the frame payload context.
Default no defaults – no frame payload is created by default.

Parameters frame-payload-id — A number to identify the frame-payload. it is an integer used to identify the frame type
to use when starting the throughput test.
Values 1-4
frame-payload-type — IIdentifies whether the frame payload is L2 traffic, IP traffic, TCP/IP traffic or UDP/
IP traffic and uses appropriate parameters to build the frame to be generated by the testhead OAM tool. It
defaults to tcp-ipv4, if the user does not specify the value during creation of the new frame-payload.
Values l2|tcp-ipv4|udp-ipv4|ipv4
If l2 is specified, use src-mac+dst-mac+vlan-tag-1(if available)+vlan-tag-2 (if
available)+ethertype+data-pattern.
If tcp-ipv4 or udp-ipv4 is specified, use src-mac+dst-mac+vlan-tag-1(if available)+vlan-
tag-2 (if available)+ethertype=0x0800+src-ipv4+dst-ipv4+ip-ttl+ip-dscp or ip-tos+TCP/
UDP Protocol Number+src-port+dst-port+data-pattern.
If ipv4 is specified, use src-mac+dst-mac+vlan-tag-1(if available)+vlan-tag-2 (if
available)+ethertype=0x0800+src-ipv4+dst-ipv4+ip-ttl+ip-dscp or ip-tos+ip-proto+data-
pattern.
description
Syntax [no] description frame-description
Context configure> test-oam> testhead-profile> frame-payload
Description This command allows user to add some description to the frame type created to describe the purpose or iden-
tify the usage or any other such purpose.
The no form of the command removes the description.
Default no description
Parameters frame-description — it is an ASCII string used to describe the frame.

Values ASCII string
src-mac
Syntax [no] src-mac mac-address
Description Specifies the value of source MAC address to use in the frame generated by the testhead OAM tool. Only
unicast MAC address must be specified.
This value must be specified for all possible values of payload-type.
The no form of the command indicates that the field is not to be used in the frame generated by the tool.
Default no src-mac

Parameters mac-address — Specify the unicast source MAC address.

Values It is specified as a hexadecimal string using the notation xx:xx:xx:xx:xx:xx. The values for
xx can be in the range 0-9 and a-f.
dst-mac
Syntax [no] dst-mac mac-address
Description Specifies the value of source MAC address to use in the frame generated by the testhead OAM tool. Only
unicast MAC address must be specified.
This value must be specified for all possible values of payload-type.
Default no dst-mac
Parameters mac-address — Specify the unicast source MAC address.

Values It is specified as a hexadecimal string using the notation xx:xx:xx:xx:xx:xx. The values for
xx can be in the range 0-9 and a-f.
vlan-tag-1
Syntax [no] vlan-tag-1 vlan-id vlan-id-value [tpid tpid value] [dot1p dot1p-value]

Description This command allows the user to specify the values to be used for the outermost vlan-tag (often called the
outer vlan) in the frame generated by the testhead OAM tool. The tool uses the values specified for VLAN
ID, dot1p bits and TPID in populating the outermost VLAN tag in the frame generated.
Configuration of this parameter is optional and it is used for all possible values of payload-type, if config-
ured.
NOTES:
• User must ensure that TPID/ethertype configured with this command matches the QinQ ethertype
value in use on the port on which the test SAP is configured or must match 0x8100 if the test SAP
is configured on a Dot1q encapsulation port, for the frame generated by the tool to be processed
successfully on SAP ingress. If this value does not match the one configured under the port, frames
generated by the testhead will be dropped by the node on SAP ingress due to ethertype mismatch.
• User must ensure that VLAN ID configured with this command matches the outermost VLAN tag
of the QinQ SAP or the Dot1q SAP used for the test SAP for the frame generated by the tool to be
processed successfully on SAP ingress. If this value does not match the one configured for the SAP,

frames generated by the testhead will be dropped by the node on SAP ingress due to VLAN ID
mismatch.
• The Dot1p bits specified for the outermost tag can be used for SAP ingress QoS classification.
Default no vlan-tag-1
Parameters vlan-id-value — Specify the VLAN ID to use to populate the VLAN ID value of the VLAN tag. No defaults
are chosen and user has to specify a value to use, if they configure this command.
Values Values can be in the range 0-4094.
tpid-value — Specify the TPID (also known as, ethertype) to use for the VLAN tag addition. It defaults to
0x8100 if user does not specify it.
Values Values can be any of the valid ethertype values allowed for use with VLAN tags in the
range 0x0600..0xffff.
Dot1p-value — Specify the Dot1p value to use to populate the Dot1p bits in the VLAN tag. It defaults to 0,
if the user does not specify it.
Values Values can be in the range of 0 – 7.
vlan-tag-2
Syntax [no] vlan-tag-2 vlan-id vlan-id-value [tpid tpid value] [dot1p dot1p-value]

Description This command allows the user to specify the values to be used for the second vlan-tag (often called the inner
vlan or the C-vlan) in the frame generated by the testhead OAM tool. The tool uses the values specified for
VLAN ID, dot1p bits and TPID in populating the second VLAN tag in the frame generated.
Configuration of this parameter is optional and it is used for all possible values of payload-type, if config-
ured.
NOTES:
• User must ensure that TPID/ethertype configured with this command is 0x8100 for the frame
generated by the tool to be processed successfully on SAP ingress. If this value does not match
0x8100, frames generated by the testhead will be dropped by the node on SAP ingress due to
ethertype mismatch (7210 supports only 0x8100 as the ethertype value for the inner vlan tag).
• User must ensure that VLAN ID configured with this command matches the outermost VLAN tag
of the QinQ SAP or the Dot1q SAP used for the test SAP for the frame generated by the tool to be
processed successfully on SAP ingress. If this value does not match the one configured for the SAP,
frames generated by the testhead will be dropped by the node on SAP ingress due to VLAN ID
mismatch.
• The Dot1p bits specified for the outermost tag can be used for SAP ingress QoS classification.
Default no vlan-tag-2

Parameters vlan-id-value — Specify the VLAN ID to use to populate the VLAN ID value of the VLAN tag. No defaults
are chosen and user has to specify a value to use, if they configure this command.
Values Values can be in the range 0-4094.
tpid-value — Specify the TPID (also knows as, ethertype) to use for the VLAN tag addition. It defaults to
0x8100 if user does not specify it.
Values Values can be any of the valid ethertype values allowed for use with VLAN tags in the
range 0x0600..0xffff.
Dot1p-value — Specify the Dot1p value to use to populate the Dot1p bits in the VLAN tag. It defaults to 0,
if the user does not specify it.
Values Values can be in the range of 0 – 7
ethertype
Syntax [no] ethertype ethertype-value
Description This command allows the user to specify the ethertype of the frame generated by the testhead tool.
This value must be specified if the payload-type is “l2”. The testhead tool uses the value specified with this
command only if the payload-type is “l2”. For all other values of payload-type, the ethertype value used in
the frame generated by the testhead tool uses specific value based on the payload-type. See the frame-pay-
load CLI description for more information.
Default no ethertype, if the payload-type is set to l2, else the values used depends on the payload-type specified.
Parameters ethertype-value — Specify the frame payload ethertype value.

Values Valid ethertype values specified in the range 0x0600..0xffff, as hexadecimal string.
src-ip
Syntax [no] src-ip ipv4 ipv4-address

Description This command allows the user to specify the source IPv4 address to use in the IP header for the frame gener-
ated by the testhead tool.
This value must be specified if the payload-type is configured as ipv4 or tcp-ipv4 or udp-ipv4. The testhead
tool does not use the value specified with this command if the payload-type is “l2”.
Default no src-ip, if the payload-type is set to ipv4, tcp-ipv4, udp-ipv4.

Parameters ipv4-address — Specify the IPv4 source IP address to use in the IP header
Values Valid IPv4 address specified in dotted decimal format (that is, a.b.c.d) where a, b, c, d are
decimal values in the range1-255
dst-ip
Syntax [no] dst-ip ipv4 ipv4-address
Description This command allows the user to specify the destination IPv4 address to use in the IP header for the frame
This value must be specified if the payload-type is configured as ipv4 or tcp-ipv4 or udp-ipv4. The testhead
tool does not use the value specified with this command if the payload-type is “l2”.
Default no dst-ip, if the payload-type is set to ipv4, tcp-ipv4, udp-ipv4.

Parameters ipv4-address — Specify the IPv4 destination IP address to use in the IP header
Values Valid IPv4 address specified in dotted decimal format (that is, a.b.c.d) where a, b, c, d are
decimal values in the range1-255.
ip-proto
Syntax [no] ip-proto ip-protocol-number

Description This command allows the user to specify the IP protocol value to use in the IP header for the frame payload
This value must be specified if the payload-type is configured as ipv4. If the payload-type is specified as tcp-
ipv4 or udp-ipv4, the appropriate standard defined values are used. The testhead tool does not use the value
specified with this command if the payload-type is “l2”.
Default no ip-proto
Parameters ip-protocol-number — Specify the IP-protocol number to use in the IP header.

Values Valid IP protocol number specified as a decimal number in the range 0-255.

dscp
Syntax [no] dscp dscp-name
Description This command allows the user to specify the IP DSCP value to use in the IP header for the frame generated
by the testhead tool.
This value can be specified if the payload-type is configured as ipv4 or tcp-ipv4 or udp-ipv4 and if config-
ured is used by the testhead tool to populate the IP DSCP field of the IP header. If it is not specified it
defaults to 0 when the payload type is ipv4, tcp-ipv4, and udp-ipv4. The testhead tool does not use the value
Default no dscp
Parameters dscp-name — Specify the IPv4 DSCP value to use in the IP header.
Values Valid values from the list of DSCP names.
be|ef|cp1|cp2|cp3|cp4|cp5|cp6|cp7|cp9|cs1|cs2|cs3|cs4|cs5|nc1|nc2|af11|af12|af13|af21|af22
|af23|af31|af32|af33|af41|af42|af43|cp11|cp13|cp15|cp17|cp19|cp21|cp23|cp25|cp27|cp29|c
p31|cp33|cp35|cp37|cp39|cp41|cp42|cp43|cp44|cp45|cp47|cp49|cp50|cp51|cp52|cp53|cp54|
cp55|cp57|cp58|cp59|cp60|cp61|cp62|cp63
ip-ttl
Syntax [no] ip-ttl ttl-value
Description This command allows the user to specify the IP TTL (Time-to-Live) value to use in the IP header for the
frame generated by the testhead tool.
ured is used by the testhead tool to populate the IP TTL field of the IP header. If it is not specified it defaults
to 1 when the payload type is ipv4, tcp-ipv4, and udp-ipv4. The testhead tool does not use the value speci-
fied with this command if the payload-type is “l2”.
Default no ip-ttl
Parameters ttl-value — Specify the IP TTL value to use in the IP header.

Values Specified as a decimal number in the range 1-255.

ip-tos
Syntax [no] ip-tos type-of-service
Description This command allows the user to specify the IP TOS (Type of Service) value to use in the IP header for the
ured is used by the testhead tool to populate the IP DSCP field of the IP header. If it is not specified it
defaults to 0 when the payload type is ipv4, tcp-ipv4, and udp-ipv4. The testhead tool does not use the value
Default no ip-tos
Parameters type-of-service — Specify the value of ToS bits to use in the IP header.
Values Valid number in the range 0-8.
src-port
Syntax [no] src-port src-port-number
Description This command allows the user to specify the source port to use in the TCP header for the frame generated by
the testhead tool.
This value must be specified if the payload-type is configured as tcp-ipv4 or udp-ipv4. The testhead tool
does not use the value specified with this command if the payload-type is l2 or ipv4.
Default no src-port, if the payload-type is set to tcp-ipv4 or udp-ipv4
Parameters src-port-number — Specify the source TCP/UDP port number to use in the frame’s TCP/UDP header.
Values Valid TCP/UDP port number specified in decimal or hexadecimal in the range 0-65535.
dst-port
Syntax [no] dst-port
Description This command allows the user to specify the destination port to use in the TCP header for the frame gener-
This value must be specified if the payload-type is configured as tcp-ipv4 or udp-ipv4. The testhead tool
does not use the value specified with this command if the payload-type is l2 or ipv4.

Default no dst-port, if the payload-type is set to tcp-ipv4 or udp-ipv4
Parameters dst-port-number — Specify the destination TCP/UDP port number to use in the frame’s TCP/UDP header.
Values Valid TCP/UDP port number specified in decimal or hexadecimal in the range 0-65535.
data-pattern
Syntax [no] data-pattern data-pattern
Description This command allows the user to specify the data pattern to populate the payload portion of the frame gener-
This value can be specified if the payload-type is configured as l2 or ipv4 or tcp-ipv4 or udp-ipv4. For all
these payload types, the frame with the appropriate headers is created and the payload portion of the frame,
is filled up with the data-pattern-value specified with this command, repeating it as many times as required
to fill up the remaining length of the payload.
The no form of the command uses the default data-pattern value of 0xa1b2c3d4e5f6.
Default no data-pattern
Parameters data-pattern — Used to specify the data-pattern to fill the payload data.
Values A string of decimal or hexadecimal numbers of length in the range 1-64.

OAM testhead commands
testhead
Syntax testhead test-name owner owner-name testhead-profile profile-id [frame-payload frame-
payload-id] [acceptance-criteria acceptance-criteria-id] [color-aware enable|disable] sap sap-id
[fc fc-name]
Context oam
Description This command allows the user to execute the throughput test by generating the traffic up to the configured
rate (CIR or PIR) and measures the delay, delay-variation and frame-loss ratio. At the end of the test run the
testhead command compares the measured values against the test acceptance criteria that is specified to
determine if the service is within bounds of the acceptance criteria or not. It declares the test to have
PASSED if the configured rate thresholds are achieved and the measured performance parameters (that is,
latency, jitter, and FLR) values are lesser than the thresholds configured in the acceptance criteria. It reports
a FAILURE, if the configured rate thresholds are not achieved or if any of the measured values for the per-
formance parameters exceeds the thresholds configured in the acceptance criteria.
The user must specify the testhead-profile parameter to use. This profile parameter determines the rate at
which traffic is generated and the content of the frames used for traffic generation. If both CIR and PIR is
specified or if only PIR is specified (by setting CIR to zero), the tool generates traffic up to the configured
PIR rate. If only CIR is specified the tool generates traffic up to the configured CIR rate.
If the acceptance-criteria parameter is not specified and color-aware is set to disable, then by default soft-
ware will display the test result as “PASS”, if the frame loss is zero and desired rate is achieved. For compar-
ison with measured rate, the test uses the configured CIR rate, if only CIR is configured or it uses the PIR
rate, if either only PIR rate is specified or if both CIR and PIR rates are set to non-zero values. Measured
value of latency, jitter and delay variation is not compared.
If the acceptance-criteria parameter is not specified and color-aware is set to enable, then the test is declared
to be pass, if the measured CIR and PIR rates matches the configured CIR and PIR values and frame loss is
zero OR if one of the following is true:
• If the measured throughput rate (CIR + PIR) is equal to the configured CIR rate and if no PIR rate
is configured.
• If the measured throughput rate (CIR + PIR) is equal to the configured PIR rate and if either no CIR
rate is configured or if CIR rate is configured.
The test is declared to ‘FAIL’ otherwise. Measured value of latency, jitter, and delay variation is not com-
pared.
If acceptance-criteria is specified and color-aware is set to enable, the test will use the configured packet
header marking values (that is, dot1p) to identify the color of the packet and classify it as green (in-profile)
or yellow (out-of-profile). It measures the green packet (that is, CIR rate) and the green/in-profile packet
performance parameter values and the yellow packet rate (that is, PIR rate) and the yellow/out-of-profile
packet performance parameter values individually based on the packet markings. In addition to comparing
the measured performance parameter values against the normal performance parameter threshold values (if
enabled), if user has enabled in/out thresholds for performance parameters in the acceptance-criteria, the tool
will use these values to compare against the measured values and declare a pass/fail result. The tool uses the

cir-threshold and pir-threshold to compare against the measured CIR and PIR throughput rates and declare
PASS/FAIL, if the thresholds specified by the cir-threshold and pir-threshold are achieved.
NOTE: When color-aware mode is set to enable, the marking values used to identify both in-profile/green
packet and out-of-profile/yellow packet must be configured. If either of the packet header marking values
(For example: dot1p) are not configured by the user, then the CLI displays an error.
If acceptance-criteria is specified and color-aware is set to disable, the tests are color blind (not color-aware).
The tool does not use the configured packet header marking values to identify the color of the packet and
treats all packets the same. The tool uses the normal thresholds configured in the acceptance-criteria (i.e. the
threshold values other than the in/out profile thresholds) to compare the measured values and declare a pass/
fail result. The tool will not make any attempt to compare the in/out thresholds against measured values. The
tool uses the cir-threshold and pir-threshold as follows:
• If no PIR rate is configured and if the measured throughput rate is equal to the configured cir-
threshold rate, the desired rate is said to have been achieved and the tests continue to compare the
measured performance parameter thresholds with the configured performance parameter thresholds
(if any).
• If PIR rate is configured and no CIR rate is configured and if the measured throughput rate is equal
to the configured pir-threshold rate, the desired rate is said to have been achieved and the tests
continue to compare the measured performance parameter thresholds with the configured
performance parameter thresholds (if any).
• If PIR rate is configured and CIR rate is configured and if the measured throughput rate is equal to
the configured pir-threshold rate, the desired rate is said to have been achieved and the tests
continue to compare the measured performance parameter thresholds with the configured
performance parameter thresholds (if any).
The test-name and owner-name together identify a particular testhead invocation/session uniquely. The
results of the testhead session are associated with the test-name and owner-name. These parameters must be
used if the user needs to display the results of the testhead tool and to clear the results of a completed run.
Multiple invocations of the testhead tool with the same test-name and owner-name is not allowed if the
results of the old run using the same pair of test-name and owner-name are present. In other words, the
results are not overwritten when the testhead is invoked again with the same values for test-name and owner-
name. The results needs to be cleared explicitly using the clear command before invoking the testhead tool
with the same test-name and owner-name. Results for up to 100 unique sessions each using a different test-
name and owner-name is saved in memory (in other words, the results are not available for use after a
reboot).
NOTE: This command is not saved in the configuration file across a reboot.
Following are some of the pre-requisites before the testhead tool can be used:
• The user needs to setup the port loopback with the mac-swap on the local node using the sap-id
used with this command and the src-mac and dst-mac used in the frame-payload. Port loopback
with mac-swap on remote node needs to be setup by user to match the local configuration.
• User must configure resources for ACL MAC criteria in ingress-internal-tcam using the command
config>system> resource-profile> ingress-internal-tcam> acl-sap-ingress> mac-match-enable.
Additionally, they must allocate resources to egress ACL MAC or IPv4 or IPv6 64-bit criteria
(using the command config>system> resource-profile> egress-internal-tcam> acl-sap-egress>
mac-ipv4-match-enable or mac-ipv6-64bit-enable or mac-ipv4-match-enable). Testhead tool uses
resources from these resource pools. If no resources are allocated to these pools or no resources are
available for use in these pools, then testhead will fail to function. Testhead needs a minimum of

about 4 entries from the ingress-internal-tcam pool and 2 entries from the egress-internal-tcam
pool. If user allocates resources to egress ACLs IPv6 128-bit match criteria (using the command
config> system> resource-profile> egress-internal-tcam> acl-sap-egress> ipv6-128bit-match-
enable), then the testhead fails to function.
• The user can specify only CIR (PIR == 0 or not configured) and execute a color-aware test. The
user can specify only PIR (by setting CIR == 0) and execute a color-aware test. In both these cases,
the measured value of CIR and PIR is compared against the respective rate thresholds configured in
the acceptance criteria and the results are declared to pass, if the measured CIR/PIR rate is greater
than the configured thresholds.
• Testhead OAM tool does not mark the packets below CIR as in-profile packets and packets above
CIR and below PIR as out-of-profile packets using the Dot1p/DSCP or other packet header bits to
indicate the color of the packet (For example: DEI bit), since 7210 SAS access SAP ingress does
not support color-aware metering. In release 7210 SAS 6.0R3, the injected/transmitted count of in-
profile packets and out-of-profile packets is maintained when the tests are run in color-aware mode.
• The MAC addresses must be learnt on the appropriate SAPs before the test can be started. It is
recommended to configure static-mac etnry for the source MAC address configured with the port-
loopback command (or the source MAC address configured in the frame-payload in the testhead
profile). The source MAC address must be learnt on a SAP/SDP which carries traffic towards the
core network.
• While the test is running user must not modify the SAP configuration. If need be, they must stop
the test, remove the port loopback with mac-swap configuration, modify the SAP configuration and
SAP parameters and then add back the port loopback with mac-swap configuration and run the test.
Default no defaults
Parameters test-name — Name of the test

Values ASCII string upto 32 characters in length
owner test-owner — Specifies the owner of an testhead operation.
testhead-profile profile-id — Specifies the testhead profile ID to use with this run/session of testhead invoca-
tion. Testhead profile must be configured beforehand using the commands under config> test-oam> test-
head-profile>.
Values 1- 10
frame-payload frame-payload-id — Optional parameter used to specify the frame payload ID to use for this
run. It identifies the parameters used to construct the frame generated by the testhead tool.
Values 1 – 4, if this parameter is not specified, then by default parameters configured under
frame-payload-id 1 is used by this run.
acceptance-criteria acceptance-criteria-id — Optional parameter used to specify the test acceptance criteria
parameters to use. for this run. It identifies the parameters used to compare the measured performance values
against the configured thresholds configured in the acceptance criteria.
Values 1 – 4. If this parameter is not specified then the run is declared pass if the throughput
configured in the testhead-profile is achieved without any loss.
color-aware — Optional parameter that specifies if color aware tests need to be executed. If set to enable,
then color-aware test enabled. If set to disable, which is the default, then non-color-ware test is enabled.

sap sap-id — Identifies the test SAP. Must be specified by the user.
Values null - <port-id|lag-id>
dot1q - <port-id|lag-id>:qtag1
qinq - <port-id|lag-id>:qtag1.qtag2
port-id - slot/mda/port
lag-id - lag-<id>
lag - keyword
id - [1..200]
qtag1 - [0..4094]
qtag2 - [*|1..4094]
For more information, see “SAP configuration guidelines”.
fc fc-name — Optional parameter that specifies the forwarding class (FC) to use to send the frames gener-
testhead
Syntax testhead test-name owner owner-name stop
Context oam
Description The currently running test, if any will be stopped. All performance results based on the data available upto
the time the test is stopped is used determine the pass/fail criteria. Additionally, the test-status will display
“Stopped” and Test completion status will be marked “Incomplete or No”.
Parameters test-name — Name of the test
owner test-owner — Specifies the owner of an testhead operation.

Service Assurance Agent (SAA) Commands
saa
Syntax saa
Context config
Description This command creates the context to configure the Service Assurance Agent (SAA) tests.
test
Syntax test name [owner test-owner]
no test name
Context config>saa
Description This command identifies a test and create/modify the context to provide the test parameters for the named
test. Subsequent to the creation of the test instance the test can be started in the OAM context.
A test can only be modified while it is shut down.
The no form of this command removes the test from the configuration. In order to remove a test it can not be
active at the time.
Parameters name — Identify the saa test name to be created or edited.
owner test-owner — Specifies the owner of an SAA operation upto 32 characters in length.
Values If a test-owner value is not specified, tests created by the CLI have a default owner
“TiMOS CLI”.
accounting-policy
Syntax accounting-policy acct-policy-id
no accounting-policy
Description This command associates an accounting policy to the SAA test. The accounting policy must already be
defined before it can be associated else an error message is generated.
A notification (trap) when a test is completed is issued whenever a test terminates.
The no form of this command removes the accounting policy association.
Default none

Parameters acct-policy-id — Enter the accounting policy-id as configured in the config>log>accounting-policy

context.
Values 1 — 99
description
Syntax description description-string
no description
Description This command creates a text description stored in the configuration file for a configuration context.
The description command associates a text string with a configuration context to help identify the content in
the configuration file.
The no form of this command removes the string from the configuration.
Default No description associated with the configuration context.
Parameters string — The description character string. Allowed values are any string up to 80 characters long composed
of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the
entire string must be enclosed within double quotes.
continuous
Syntax [no] continuous
Description This command specifies whether the SAA test is continuous. Once the test is configured as continuous, it
cannot be started or stopped by using the saa command.
The no form of the command disables the continuous running of the test. Use the shutdown command to
disable the test.
jitter-event
Syntax jitter-event rising-threshold threshold [falling-threshold threshold] [direction]
no jitter-event
Description Specifies that at the termination of an SAA test probe, the calculated jitter value is evaluated against the con-
figured rising and falling jitter thresholds. SAA threshold events are generated as required.
Once the threshold (rising/falling) is crossed, it is disabled from generating additional events until the oppo-
site threshold is crossed. If a falling-threshold is not supplied, the rising threshold will be re-enabled when it
falls below the threshold after the initial crossing that generate the event.

The configuration of jitter event thresholds is optional.
Parameters rising-threshold threshold — Specifies a rising threshold jitter value. When the test run is completed, the
calculated jitter value is compared to the configured jitter rising threshold. If the test run jitter value is
greater than the configured rising threshold value then an SAA threshold event is generated. The SAA
threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.
Default 0
Values 0 — 2147483 milliseconds
falling-threshold threshold — Specifies a falling threshold jitter value. When the test run is completed, the
calculated jitter value is compared to the configured jitter falling threshold. If the test run jitter value is
greater than the configured falling threshold value then an SAA threshold event is generated. The SAA
threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.
Default 0
direction — Specifies the direction for OAM ping responses received for an OAM ping test run.
Values inbound — Monitor the value of jitter calculated for the inbound, one-way, OAM ping
responses received for an OAM ping test run.
outbound — Monitor the value of jitter calculated for the outbound, one-way, OAM ping
requests sent for an OAM ping test run.
roundtrip — Monitor the value of jitter calculated for the round trip, two-way, OAM ping
requests and replies for an OAM ping test run.
Default roundtrip
latency-event
Syntax latency-event rising-threshold threshold [falling-threshold threshold] [direction]
no latency-event
Description Specifies that at the termination of an SAA test probe, the calculated latency event value is evaluated against
the configured rising and falling latency event thresholds. SAA threshold events are generated as required.
Once the threshold (rising/falling) is crossed, it is disabled from generating additional events until the oppo-
site threshold is crossed. If a falling-threshold is not supplied, the rising threshold will be re-enabled when it
falls below the threshold after the initial crossing that generate the event.
The configuration of latency event thresholds is optional.
Parameters rising-threshold threshold — Specifies a rising threshold latency value. When the test run is completed, the
calculated latency value is compared to the configured latency rising threshold. If the test run latency
value is greater than the configured rising threshold value then an SAA threshold event is generated.
The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.
Default 0

falling-threshold threshold — Specifies a falling threshold latency value. When the test run is completed,
the calculated latency value is compared to the configured latency falling threshold. If the test run
latency value is greater than the configured falling threshold value then an SAA threshold event is gen-
erated. The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.
Default 0
Default roundtrip
loss-event
Syntax loss-event rising-threshold threshold [falling-threshold threshold] [direction]
no loss-event
Description Specifies that at the termination of an SAA testrun, the calculated loss event value is evaluated against the
configured rising and falling loss event thresholds. SAA threshold events are generated as required.
The configuration of loss event thresholds is optional.
Parameters rising-threshold threshold — Specifies a rising threshold loss event value. When the test run is completed,
the calculated loss event value is compared to the configured loss event rising threshold. If the test run
loss event value is greater than the configured rising threshold value then an SAA threshold event is
generated. The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event #2101.
Default 0
Values 0 — 2147483647 packets
falling-threshold threshold — Specifies a falling threshold loss event value. When the test run is com-
pleted, the calculated loss event value is compared to the configured loss event falling threshold. If the
test run loss event value is greater than the configured falling threshold value then an SAA threshold
event is generated. The SAA threshold event is tmnxOamSaaThreshold, logger application OAM, event
#2101.
Default 0
Values 0 — 2147483647 packets

Default roundtrip
trap-gen
Syntax trap-gen
Description This command enables the context to configure trap generation for the SAA test.
probe-fail-enable
Syntax [no] probe-fail-enable
Context config>saa>test>trap-gen
Description This command enables the generation of an SNMP trap when probe-fail-threshold consecutive probes fail
during the execution of the SAA ping test. This command is not applicable to SAA trace route tests.
The no form of the command disables the generation of an SNMP trap.
probe-fail-threshold
Syntax [no] probe-fail-threshold 0..15
Description This command has no effect when probe-fail-enable is disabled. This command is not applicable to SAA
trace route tests.
The probe-fail-enable command enables the generation of an SNMP trap when the probe-fail-threshold
consecutive probes fail during the execution of the SAA ping test. This command is not applicable to SAA
trace route tests.
The no form of the command returns the threshold value to the default.
Default 1

test-completion-enable
Syntax [no] test-completion-enable
Description This command enables the generation of a trap when an SAA test completes.
The no form of the command disables the trap generation.
test-fail-enable
Syntax [no] test-fail-enable
Description This command enables the generation of a trap when a test fails. In the case of a ping test, the test is consid-
ered failed (for the purpose of trap generation) if the number of failed probes is at least the value of the test-
fail-threshold parameter.
The no form of the command disables the trap generation.
test-fail-threshold
Syntax [no] test-fail-threshold 0..15
Description This command configures the threshold for trap generation on test failure.
This command has no effect when test-fail-enable is disabled. This command is not applicable to SAA trace
route tests.
The no form of the command returns the threshold value to the default.
Default 1
type
Syntax type
no type
Description This command creates the context to provide the test type for the named test. Only a single test type can be
configured.
A test can only be modified while the test is in shut down mode.

Once a test type has been configured the command can be modified by re-entering the command, the test
type must be the same as the previously entered test type.
To change the test type, the old command must be removed using the config>saa>test>no type command.
cpe-ping
Note: This command is not supported on 7210 SAS-M devices configured in Access uplink mode.
Syntax cpe-ping service service-id destination ip-address source ip-address [ttl vc-label-ttl] [return-
control] [source-mac ieee-address] [fc fc-name] [interval interval] [send-count send-count]
[send-control]
Context oam
Description This ping utility determines the IP connectivity to a CPE within a specified VPLS service.

svc-name: 64 characters maximum
destination ip-address — Specifies the IP address to be used as the destination for performing an OAM
ping operations.
source ip-address — Specify an unused IP address in the same network that is associated with the VPLS.
Default 255
Values 1 — 255
source-mac ieee-address — Specify the source MAC address that will be sent to the CPE. If not specified
or set to 0, the MAC address configured for the CPMCFM is used.
Default be

Default 1
Values 1 — 10
Default 1
Values 1 — 255
dns
Syntax dns target-addr dns-name name-server ip-address [source ip-address] [count send-count]
[timeout timeout] [interval interval] [record-type {ipv4-a-record | ipv6-aaaa-record}]
Context <GLOBAL>
Description This command configures a DNS name resolution test.
Parameters target-addr — The IP host address to be used as the destination for performing an OAM ping opera-
tion.dns-name — The DNS name to be resolved to an IP address.
name-server ip-address — Specifies the server connected to a network that resolves network names into
network addresses.
x:x:x:x:x:x:d.d.d.d
x - [0..FFFF]H
d - [0..255]D
source ip-address — Specifies the IP address to be used as the source for performing an OAM ping opera-
tion.
x:x:x:x:x:x:d.d.d.d
x - [0..FFFF]H
d - [0..255]D

Default 1
Values 1 — 100
Default 5
Values 1 — 120
Default 1
Values 1 — 10
record-type — Specifies a record type.

Values ipv4-a-record - A record specific mapping a host name to an IPv4 address.
ipv6-aaaa-record - A record specific to the Internet class that stores a single IPv6
address.
eth-cfm-linktrace
Syntax eth-cfm-linktrace mac-address mep mep-id domain md-index association ma-index [ttl ttlvalue]
[fc {fc-name} ] [count send-count] [timeout timeout] [interval interval]
Context config>saa>test>type
Description This command configures a CFM linktrace test in SAA.
Parameters- mac-address — Specifies a unicast destination MAC address.

Values 1 — 8191
Values 1 — 4294967295
Values 1 — 4294967295
ttl ttl-value — Specifies the maximum number of hops traversed in the linktrace.

Default 64
Values 1— 255
fc fc-name — The fc parameter is used to indicate the forwarding class of the CFM Linktrace request
messages.
The actual forwarding class encoding is controlled by the network egress mappings.
Default nc
is used to override the default number of message requests sent. Each message request must either timeout
or receive a reply before the next message request is sent. The message interval value must be expired
before the next message request is sent.
Default 1
Values 1 — 10
silently discarded. The timeout value must be less than the interval.
Default 5
Values 1 — 10
If the interval is set to “1” second, and the timeout value is set to “10” seconds, then the maximum time
between message requests is “10” seconds and the minimum is “1” second. This depends upon the receipt of
a message reply corresponding to the outstanding message request. The timeout value must be less than
the interval.
Default 5
Values 1 — 10
eth-cfm-loopback
Syntax eth-cfm-loopback mac-address mep mep-id domain md-index association ma-index [size
datasize] [fc {fc-name} ] [count send-count ][timeout timeout] [interval interval]
Description This command configures an Ethernet CFM loopback test in SAA.



Values 1 — 8191
Values 1 — 4294967295
Values 1 — 4294967295
size data-size — The packet size in bytes, expressed as a decimal integer.
Default 0
Values 0 — 1500
fc fc-name — The fc parameter is used to indicate the forwarding class of the CFM Loopback request
messages.
Default nc
Default 1
Values 1 — 100
Default 5
Values 1 — 10
the interval.
Default 5
Values 1 — 10

eth-cfm-two-way-delay
Syntax eth-cfm-two-way-delay mac-address mep mep-id domain md-index association ma-index [fc
{fc-name} ] [count send-count] [timeout timeout] [interval interval]
Description- This command configures an Ethernet CFM two-way delay test in SAA.
Values 1 — 8191
Values 1 — 4294967295
Values 1 — 4294967295
ttl ttl-value — Specifies the maximum number of hops traversed in the linktrace.
Default 64
Values 1— 255
fc fc-name — The fc parameter is used to indicate the forwarding class of the CFM two-delay request
messages.
Default nc
Default 1
Values 1 — 100
Default 5
Values 1 — 10

the interval.
Default 5
Values [0.1, 0.2, .. 0.9] | [1, 2, .. 10]
eth-cfm-two-way-slm
Syntax eth-cfm-two-way-delay mac-address mep mep-id domain md-index association ma-index [fc
{fc-name}] [send-count send-count] [size data-size] [timeout timeout] [interval interval]
Description This command configures an Ethernet CFM two-way SLM test in SAA.
Values 1 — 8191
Values 1 — 4294967295
Values 1 — 4294967295
fc fc-name — The fc parameter is used to indicate the forwarding class of the CFM SLM request messages.
Default nc
profile {in | out} — The profile state of the CFM SLM request messages.
Default in
parameter is used to override the default number of message requests sent. Each message request must either
timeout or receive a reply before the next message request is sent. The message interval value must be
Default 1
Values 1 — 100
the packet.

Default 0
Values 0 — 1500
override the default timeout value and is the amount of time that the router waits for a message reply after
sending the message request. Upon the expiration of message timeout, the requesting router assumes that the
message response is not received. Any response received after the request times out is silently discarded.
The timeout value must be less than the interval.
Default 5
Values 1 — 10
interval interval — The interval parameter in seconds, expressed as a decimal integer. This parameter is used
to override the default request message send interval and defines the minimum amount of time that must
expire before the next message request is sent. If the interval is set to 1 second, and the timeout value is set
to 10 seconds, then the maximum time between message requests is 10 seconds and the minimum is 1 sec-
ond. This depends upon the receipt of a message reply corresponding to the outstanding message request.
The timeout value must be less than the interval.
Default 5
Values [0.1, 0.2, .. 0.9] | [1, 2, .. 10]
icmp-ping
Syntax icmp-ping [ip-address | dns-name] [rapid | detail] [ttl time-to-live] [tos type-of-service] [size
bytes] [pattern pattern] [source ip-address | dns-name] [interval seconds] [{next-hop ip-address}
| {interface interface-name} | bypass-routing] [count requests] [do-not-fragment] [router router-
instance | service-name service-name] [timeout timeout]
Description This command configures an ICMP ping test.

tion.
x:x:x:x:x:x:d.d.d.d
x: [0 .. FFFF]H
d: [0 .. 255]D
dns-name — The DNS name of the far-end device to which to send the svc-ping request message, expressed
as a character string up to 63 characters maximum.
rapid — Packets will be generated as fast as possible instead of the default 1 per second.
ttl time-to-live — The TTL value for the IP packet, expressed as a decimal integer.
Values 1 — 128


Values 0 — 255
size bytes — The request packet size in bytes, expressed as a decimal integer.
Values 0 — 16384
pattern pattern — The date portion in a ping packet will be filled with the pattern value specified. If not
specified, position info will be filled instead.
Values 0 — 65535
source ip-address|dns-name — Specifies the IP address to be used.
Values ipv4-address: a.b.c.ddns-name: 128 characters max
interval seconds — This parameter is used to override the default request message send interval and defines
the minimum amount of time that must expire before the next message request is sent.
Default 1
Values 1 — 10
Values ipv4-address: a.b.c.d (host bits must be 0)
interface interface-name — The name used to refer to the interface. The name must already exist in the
config>router>interface context.
bypass-routing — Specifies whether to send the ping request to a host on a directly attached network
bypassing the routing table.
count requests — Specifies the number of times to perform an OAM ping probe operation. Each OAM echo
message request must either timeout or receive a reply before the next message request is sent.
Values 1 — 100000
Default 5
do-not-fragment — Sets the DF (Do Not Fragment) bit in the ICMP ping packet.
Values router-name: Base , management
service-id: 1 — 2147483647
Default Base
service-name service-name — Specifies the service name as an integer.
timeout timeout — Overrides the default timeout value and is the amount of time that the router will wait
for a message reply after sending the message request. Upon the expiration of message timeout, the
requesting router assumes that the message response will not be received. Any response received after
the request times out will be silently discarded.

Default 5
Values 1 — 10
icmp-trace
Syntax icmp-trace [ip-address | dns-name] [ttl time-to-live] [wait milli-seconds] [tos type-of-service]
[source ip-address] [tos type-of-service] [router router-instance | service-name service-name]
Description This command configures an ICMP traceroute test.
tion.
x:x:x:x:x:x:d.d.d.d
x: [0 .. FFFF]H
d: [0 .. 255]D
dns-name — The DNS name of the far-end device to which to send the svc-ping request message, expressed
as a character string to 63 characters maximum.
ttl time-to-live — The TTL value for the MPLS label, expressed as a decimal integer.
Values 1 — 255
wait milliseconds — The time in milliseconds to wait for a response to a probe, expressed as a decimal inte-
ger.
Default 5000
Values 1 — 60000
Values 0 — 255
source ip-address — Specifies the IP address to be used.
x:x:x:x:x:x:d.d.d.d
x: [0 .. FFFF]H
d: [0 .. 255]D
Values router-name: Base, management
service-id: 1 — 2147483647
Default Base

lsp-ping
mode.
Syntax lsp-ping {lsp-name [path path-name]} [fc fc-name] [size octets][ttl label-ttl] [send-count send-
count] [timeout timeout] [interval
interval]
Context oam
Description This command performs in-band LSP connectivity tests.

The lsp-ping command performs an LSP ping using the protocol and data structures defined in the RFC
4379, Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures.
The LSP ping operation is modeled after the IP ping utility which uses ICMP echo request and reply packets
to determine IP connectivity.
In an LSP ping, the originating device creates an MPLS echo request packet for the LSP and path to be
tested. The MPLS echo request packet is sent through the data plane and awaits an MPLS echo reply packet
from the device terminating the LSP. The status of the LSP is displayed when the MPLS echo reply packet is
received.
path path-name — The LSP path name along which to send the LSP ping request.
fc fc-name — The fc parameter is used to indicate the forwarding class of the MPLS echo request packets.
The actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
The LSP-EXP mappings on the receive network interface controls the mapping back to the internal for-
warding class used by the far-end 7210 SAS M that receives the message request. The egress mappings
of the egress network interface on the far-end 7210 SAS M controls the forwarding class markings on
the return reply message.
back at the originating router.
Default be
size octets — The MPLS echo request packet size in octets, expressed as a decimal integer. The request
payload is padded with zeroes to the specified size.
Default 68 — The system sends the minimum packet size, depending on the type of LSP. No pad-
ding is added.
Values 84 — 65535
ttl label-ttl — The TTL value for the MPLS label, expressed as a decimal integer.

Default 255
Values 1 — 255
Default 1
Values 1 — 100
Default 5
Values 1 — 10
Default 1
Values 1 — 10
lsp-trace
mode.
Syntax lsp-trace {lsp-name [path path-name]} [fc fc-name] [max-fail no-response-count] [probe-count
probes-per-hop] [size octets] [min-ttl min-label-ttl] [max-ttl max-label-ttl] [timeout timeout]
[interval interval]
Context oam
Description This command displays the hop-by-hop path for an LSP.
The lsp-trace command performs an LSP traceroute using the protocol and data structures defined in the
IETF draft (draft-ietf-mpls-lsp-ping-02.txt).
The LSP traceroute operation is modeled after the IP traceroute utility which uses ICMP echo request and
reply packets with increasing TTL values to determine the hop-by-hop route to a destination IP.

In an LSP traceroute, the originating device creates an MPLS echo request packet for the LSP to be tested
with increasing values of the TTL in the outermost label. The MPLS echo request packet is sent through the
data plane and awaits a TTL exceeded response or the MPLS echo reply packet from the device terminating
the LSP. The devices that reply to the MPLS echo request packets with the TTL exceeded and the MPLS
echo reply are displayed.
path path-name — The LSP pathname along which to send the LSP trace request.
min-ttl min-label-ttl — The minimum TTL value in the MPLS label for the LSP trace test, expressed as a
decimal integer.
Default 1
Values 1 — 255
max-ttl max-label-ttl — The maximum TTL value in the MPLS label for the LDP treetrace test, expressed
Default 30
Values 1 — 255
max-fail no-response-count — The maximum number of consecutive MPLS echo requests, expressed as a
decimal integer that do not receive a reply before the trace operation fails for a given TTL.
Default 5
Values 1 — 255
override the default timeout value and is the amount of time that the 7210 SAS M will wait for a mes-
sage reply after sending the message request. Upon the expiration of message timeout, the requesting
router assumes that the message response will not be received. A ‘request timeout’ message is displayed
by the CLI for each message request sent that expires. Any response received after the request times out
will be silently discarded.
Default 3
Values 1 — 10
Default 1
Values 1 — 10

of the egress network interface on the far-end 7210 SAS M controls the forwarding class markings on
the return reply message.
back at the originating 7210 SAS M.
Default be
mac-ping
mode.
Syntax mac-ping service service-id destination dst-ieee-address [source src-ieee-address] [fc fc-
name] [size octets] [ttl vc-label-ttl] [send-count send-count] [send-control] [return-control]
[interval interval] [timeout timeout]
Context oam
Description The mac-ping utility is used to determine the existence of an egress SAP binding of a given MAC within a
VPLS service.
A mac-ping packet can be sent via the control plane or the data plane. The send-control option specifies the
plane.
A mac-ping is forwarded along the flooding domain if no MAC address bindings exist. If MAC address
bindings exist, then the packet is forwarded along those paths, provided they are active. A response is gener-
ated only when there is an egress SAP binding for that MAC address or if the MAC address is a “local”
OAM MAC address associated with the device’s control plan.
A mac-ping reply can be sent using the data plane or the control plane. The return-control option specifies
the reply be sent using the control plane. If return-control is not specified, the request is sent using the data
plane.
A mac-ping with data plane reply can only be initiated on nodes that can have an egress MAC address bind-
ing. A node without a FIB and without any SAPs cannot have an egress MAC address binding, so it is not a
node where replies in the data plane will be trapped and sent up to the control plane.
A control plane request is responded to via a control plane reply only.
By default, MAC OAM requests are sent with the system or chassis MAC address as the source MAC. The
source option allows overriding of the default source MAC for the request with a specific MAC address.
SHG. In all other cases, SHG 0 (zero) will be used. Note that if the mac-trace is originated from a non-zero
If EMG is enabled, mac-ping will return only the first SAP in each chain.


destination ieee-address — The destination MAC address for the OAM MAC request.
request is used.
Values 1 — 65535
Default 255
Values 1 — 255
source src-ieee-address — The source MAC address from which the OAM MAC request originates. By
default, the system MAC address for the chassis is used.
fc fc-name — The fc parameter is used to test the forwarding class of the MPLS echo request packets. The
actual forwarding class encoding is controlled by the network egress LSP-EXP mappings.
Default 1
Values 1 — 10

Default 1
Values 1 — 100
Default 5
Values 1 — 10
Sample Output
oam mac-ping service 1 destination 00:bb:bb:bb:bb:bb

Seq Node-id Path RTT
----------------------------------------------------------------------------
[Send request Seq. 1, Size 126]
1 2.2.2.2:sap1/1/1:1 In-Band 960ms
----------------------------------------------------------------------------
sdp-ping
mode.
Syntax sdp-ping orig-sdp-id [resp-sdp resp-sdp-id] [fc fc-name [profile {in | out}]] [timeout seconds]
[interval seconds] [size octets] [count send-count] [interval <interval>]
Context oam
Description This command tests SDPs for uni-directional or round trip connectivity and performs SDP MTU Path tests.
The sdp-ping command accepts an originating SDP-ID and an optional responding SDP-ID. The size, num-
ber of requests sent, message time-out and message send interval can be specified. All sdp-ping requests
and replies are sent with PLP OAM-Label encapsulation, as a service-id is not specified.
For round trip connectivity testing, the resp-sdp keyword must be specified. If resp-sdp is not specified, a
uni-directional SDP test is performed.
To terminate an sdp-ping in progress, use the CLI break sequence <Ctrl-C>.
An sdp-ping response message indicates the result of the sdp-ping message request. When multiple
response messages apply to a single SDP echo request/reply sequence, the response message with the high-
est precedence will be displayed. The following table displays the response messages sorted by precedence.

Result of Request Displayed Response Message Precedence
Request timeout without reply Request Timeout 1

Request not sent due to non-existent orig-sdp-id Orig-SDP Non-Existent 2
Request not sent due to administratively down orig- Orig-SDP Admin-Down 3
sdp-id
Request not sent due to operationally down orig-sdp-id Orig-SDP Oper-Down 4
Request terminated by user before reply or timeout Request Terminated 5
Reply received, invalid origination-id Far End: Originator-ID Invalid 6
Reply received, invalid responder-id Far End: Responder-ID Error 7
Reply received, non-existent resp-sdp-id Far End: Resp-SDP Non-Existent 8
Reply received, invalid resp-sdp-id Far End: Resp-SDP Invalid 9
Reply received, resp-sdp-id down (admin or oper) Far-end: Resp-SDP Down 10
Reply received, No Error Success 11
Parameters orig-sdp-id — The SDP-ID to be used by sdp-ping, expressed as a decimal integer. The far-end address of
the specified SDP-ID is the expected responder-id within each reply received. The specified SDP-ID
defines the encapsulation of the SDP tunnel encapsulation used to reach the far end. This can be IP or
MPLS. If orig-sdp-id is invalid or administratively down or unavailable for some reason, the SDP Echo
Request message is not sent and an appropriate error message is displayed (once the interval timer
expires, sdp-ping will attempt to send the next request if required).
Values 1 — 17407
resp-sdp resp-sdp-id — Optional parameter is used to specify the return SDP-ID to be used by the far-end
7210 SAS M for the message reply for round trip SDP connectivity testing. If resp-sdp-id does not exist
on the far-end 7210 SAS M, terminates on another 7210 SAS M different than the originating 7210 SAS
M, or another issue prevents the far-end router from using resp-sdp-id, the SDP echo reply will be sent
using generic IP/OAM encapsulation. The received forwarding class (as mapped on the ingress network
interface for the far end) defines the forwarding class encapsulation for the reply message.
Default null. Use the non-SDP return path for message reply.
Values 1 — 17407
fc fc-name — The fc parameter is used to indicate the forwarding class of the SDP encapsulation. The
actual forwarding class encoding is controlled by the network egress DSCP or LSP-EXP mappings.
The DSCP or LSP-EXP mappings on the receive network interface controls the mapping back to the
internal forwarding class used by the far-end 7210 SAS M that receives the message request. The egress
mappings of the egress network interface on the far-end 7210 SAS M controls the forwarding class
markings on the return reply message.
The DSCP or LSP-EXP mappings on the receive network interface controls the mapping of the message
reply back at the originating 7210 SAS M. This is displayed in the response message output upon

receipt of the message reply.

Default be
timeout seconds — The timeout parameter in seconds, expressed as a decimal integer. This value is used to
Default 5
Values 1 — 10
Default 1
Values 1 — 10
size octets — The size parameter in octets, expressed as a decimal integer. This parameter is used to over-
ride the default message size for the sdp-ping request. Changing the message size is a method of check-
ing the ability of an SDP to support a path-mtu. The size of the message does not include the SDP
encapsulation, VC-Label (if applied) or any DLC headers or trailers.
When the OAM message request is encapsulated in an IP/ SDP, the IP ‘DF’ (Do Not Fragment) bit is
set. If any segment of the path between the sender and receiver cannot handle the message size, the mes-
sage is discarded. MPLS LSPs are not expected to fragment the message either, as the message con-
tained in the LSP is not an IP packet.
Default 72
Values 72 — 9198
Default 1
Values 1 — 100
Special Cases Single Response Connectivity Tests — A single response sdp-ping test provides detailed test results.
Upon request timeout, message response, request termination, or request error the following local and
remote information will be displayed. Local and remote information will be dependent upon SDP-ID exis-
tence and reception of reply.


Request Result The result of the sdp-ping request message. Sent - Request Timeout
Sent - Request Terminated
Sent - Reply Received
Local SDP-ID
Not Sent - Local SDP-ID
Down
Originating SDP-ID The originating SDP-ID specified by orig-sdp. orig-sdp-id
Originating SDP-ID The local administrative state of the originating SDP-ID. If the Admin-Up
Administrative State SDP-ID has been shutdown, Admin-Down is displayed. If the
Admin-Down
originating SDP-ID is in the no shutdown state, Admin-Up is
displayed. If the orig-sdp-id does not exist, Non-Existent is dis- Non-Existent
played.
Originating SDP-ID The local operational state of the originating SDP-ID. If orig- Oper-Up
Operating State sdp-id does not exist, N/A will be displayed.
Oper-Down
N/A
Originating SDP-ID The local path-mtu for orig-sdp-id. If orig-sdp-id does not exist orig-path-mtu
Path MTU locally, N/A is displayed.
N/A
Responding SDP-ID The SDP-ID requested as the far-end path to respond to the sdp- resp-sdp-id
ping request. If resp-sdp is not specified, the responding router
N/A
will not use an SDP-ID as the return path and N/A will be dis-
played.
Responding SDP-ID Displays whether the responding 7210 SAS M used the respond- Yes
Path Used ing sdp-id to respond to the sdp-ping request. If resp-sdp-id is a
No
valid, operational SDP-ID, it must be used for the SDP echo
reply message. If the far-end uses the responding sdp-id as the N/A
return path, Yes will be displayed. If the far-end does not use the
responding sdp-id as the return path, No will be displayed. If
resp-sdp is not specified, N/A will be displayed.
Responding SDP-ID The administrative state of the responding sdp-id. When resp- Admin-Down
Administrative State sdp-id is administratively down, Admin-Down will be dis-
Admin-Up
played. When resp-sdp-id is administratively up, Admin-Up will
be displayed. When resp-sdp-id exists on the far-end 7210 SAS Invalid
M but is not valid for the originating router, Invalid is displayed.
Non-Existent
When resp-sdp-id does not exist on the far-end router, Non-Exis-
tent is displayed. When resp-sdp is not specified, N/A is dis- N/A
played.

Responding SDP-ID The operational state of the far-end sdp-id associated with the Oper-Up
Operational State return path for service-id. When a return path is operationally
Oper-Down
down, Oper-Down is displayed. If the return sdp-id is operation-
ally up, Oper-Up is displayed. If the responding sdp-id is non- N/A
existent, N/A is displayed.
Responding SDP-ID The remote path-mtu for resp-sdp-id. If resp-sdp-id does not resp-path-mtu
Path MTU exist remotely, N/A is displayed
N/A
Local Service IP The local system IP address used to terminate remotely config- system-ip-addr
Address ured sdp-ids (as the sdp-id far-end address). If an IP address has
N/A
not been configured to be the system IP address, N/A is dis-
played.
Local Service IP Inter- The name of the local system IP interface. If the local system IP system-interface-name
face Name interface has not been created, N/A is displayed.
N/A
Local Service IP Inter- The state of the local system IP interface. If the local system IP Up
face State interface has not been created, Non-Existent is displayed.
Down
Non-Existent
Expected Far End The expected IP address for the remote system IP interface. This orig-sdp-far-end-addr
Address must be the far-end address configured for the orig-sdp-id.
dest-ip-addr
N/A
Actual Far End Address The returned remote IP address. If a response is not received, the resp-ip-addr
displayed value is N/A. If the far-end service IP interface is
N/A
down or non-existent, a message reply is not expected.
Responders Expected The expected source of the originators sdp-id from the perspec- resp-rec-tunnel-far-end-
Far End Address tive of the remote terminating the sdp-id. If the far-end cannot addr
detect the expected source of the ingress sdp-id, N/A is dis-
N/A
played.
Round Trip Time The round trip time between SDP echo request and the SDP delta-request-reply
echo reply. If the request is not sent, times out or is terminated,
N/A
N/A is displayed.
Multiple Response Connectivity Tests — When the connectivity test count is greater than one (1), a single
line is displayed per SDP echo request send attempt.
The request number is a sequential number starting with 1 and ending with the last request sent, increment-
ing by one (1) for each request. This should not be confused with the message-id contained in each request
and reply message.
A response message indicates the result of the message request. Following the response message is the
round trip time value. If any reply is received, the round trip time is displayed.

After the last reply has been received or response timed out, a total is displayed for all messages sent and all
replies received. A maximum, minimum and average round trip time is also displayed. Error response and
timed out requests do not apply towards the average round trip time.
Multiple Response Round Trip Connectivity Test Sample Output
*A:DUT-A# oam sdp-ping 101 resp-sdp 102

Err SDP-ID Info Local Remote
--------------------------------------------------
SDP-ID: 101 102
Administrative State: Up Up
Operative State: Up Up
Path MTU: 9186 N/A
Response SDP Used: Yes
IP Interface State: Up
Actual IP Address: 10.20.1.1 10.20.1.2
Expected Peer IP: 10.20.1.2 10.20.1.1
Forwarding Class be be
Profile Out Out
Request Result: Sent - Reply Received

RTT: 10(ms)
*A:DUT-A# oam sdp-ping 101 resp-sdp 102 count 10

Request Response RTT
-----------------------------------------------------
1 Success 10ms
2 Success 0ms
3 Success 0ms
4 Success 0ms
5 Success 0ms
6 Success 0ms
7 Success 0ms
8 Success 0ms
9 Success 0ms
10 Success 0ms
Sent: 10 Received: 10
Min: 0ms Max: 10ms Avg: 1ms
*A:DUT-A#
vccv-ping
Note: This command is not supported on 7210 SAS devices configured in Access uplink mode.

Syntax vccv-ping sdp-id:vc-id [src-ip-address ip-addr dst-ip-address ip-addr pw-id pw-id][reply-mode

{ip-routed|control-channel}] [fc fc-name] [size octets] [send-count send-count] [timeout
timeout] [interval interval] [ttl vc-label-ttl]
Context oam
config>saa>test
Description This command configures a Virtual Circuit Connectivity Verification (VCCV) ping test. A vccv-ping test
checks connectivity of a VLL inband. It checks to verify that the destination (target) PE is the egress for the
Layer 2 FEC. It provides for a cross-check between the dataplane and the control plane. It is inband which
means that the vccv-ping message is sent using the same encapsulation and along the same path as user
packets in that VLL. The vccv-ping test is the equivalent of the lsp-ping test for a VLL service. The vccv-
ping reuses an lsp-ping message format and can be used to test a VLL configured over an MPLS.
Note that VCCV ping can be initiated on TPE or SPE. If initiated on the SPE, the reply-mode parameter
must be used with the ip-routed value The ping from the TPE can have either values or can be omitted, in
which case the default value is used.
If a VCCV ping is initiated from TPE to neighboring a SPE (one segment only) it is sufficient to only use the
sdpid:vcid parameter. However, if the ping is across two or more segments, at least the sdpId:vcId, src-ip-
address ip-addr, dst-ip-address ip-addr, ttl vc-label-ttland pw-id pw-id parameters are used where:
• The src-ip-address is system IP address of the router preceding the destination router.
• The pwid is actually the VC ID of the last pseudowire segment.
• The vc-label-ttl must have a value equal or higher than the number of pseudowire segments.
Note that VCCV ping is a multi-segment pseudowire. For a single-hop pseudowire, only the peer VCCV CC
bit of the control word is advertised when the control word is enabled on the pseudowire. VCCV ping on
multi-segment pseudowires require that the control word be enabled in all segments of the VLL.
If the control word is not enabled on spoke SDP it will not be signaled peer VCCV CC bits to the far end,
consequently VCCV ping cannot be successfully initiated on that specific spoke SDP.
Parameters sdp-id:vc-id — The VC ID of the pseudowire being tested must be indicated with this parameter. The VC ID
needs to exist on the local router and the far-end peer needs to indicate that it supports VCCV to allow
the user to send vccv-ping message.
Values 1 — 17407:1 — 4294967295
src-ip-address ip-addr — Specifies the source IP address.
dst-ip-address ip-address — Specifies the destination IP address.
pw-id pw-id — Specifies the pseudowire ID to be used for performing a vccv-ping operation. The pseudow-
ire ID is a non-zero 32-bit connection ID required by the FEC 128, as defined in RFC 4379, Detecting
Multi-Protocol Label Switched (MPLS) Data Plane Failures.
reply-mode {ip-routed | control-channel} — The reply-mode parameter indicates to the far-end how to
send the reply message.The option control-channel indicates a reply mode in-band using vccv control
channel.
Default control-channel

of the egress network interface on the far-end router controls the forwarding class markings on the
return reply message. The LSP-EXP mappings on the receive network interface controls the mapping of
the message reply back at the originating SR.
Default be
timeout seconds — The timeout parameter, in seconds, expressed as a decimal integer. This value is used to
Default 5
Values 1 — 10
Default 1
Values 1 — 10
size octets — The VCCV ping echo request packet size in octets, expressed as a decimal integer. The
request payload is padded with zeroes to the specified size.
Default 88
Values 88 — 9198
Default 1
Values 1 — 100
ttl vc-label-ttl — Specifies the time-to-live value for the vc-label of the echo request message. The outer
label TTL is still set to the default of 255 regardless of this value.

vccv-trace
Syntax vccv-trace sdp-id:vc-id [fc fc-name [profile {in | out}]] [size octets] [reply-mode ip-routed|control-
channel] [probe-count probe-count] [timeout timeout] [interval interval] [min-ttl min-vc-label-ttl]
[max-ttl max-vc-label-ttl] [max-fail no-response-count] [detail]
Context oam
Description This command configures a Virtual Circuit Connectivity Verification (VCCV) automated trace test. The
automated VCCV-trace can trace the entire path of a PW with a single command issued at the T-PE or at an
S-PE. This is equivalent to LSP-Trace and is an iterative process by which the source T-PE or S-PE node
sends successive VCCV-Ping messages with incrementing the TTL value, starting from TTL=1.
In each iteration, the T-PE builds the MPLS echo request message in a way similar to vccv-ping. The first
message with TTL=1 will have the next-hop S-PE T-LDP session source address in the Remote PE Addressí
field in the PW FEC TLV. Each S-PE which terminates and processes the message will include in the MPLS
echo reply message the FEC 128 TLV corresponding the PW segment to its downstream node. The source T-
PE or S-PE node can then build the next echo reply message with TTL=2 to test the next-next hop for the
MS-PW. It will copy the FEC TLV it received in the echo reply message into the new echo request message.
The process is terminated when the reply is from the egress T-PE or when a timeout occurs.
The user can specify to display the result of the VCCV-trace for a fewer number of PW segments of the end-
to-end MS-PW path. In this case, the min-ttl and max-ttl parameters are configured accordingly. However,
the T-PE/S-PE node will still probe all hops up to min-ttl in order to correctly build the FEC of the desired
subset of segments.
Parameters sdpid:vcid — The VC ID of the pseudowire being tested must be indicated with this parameter. The VC ID
needs to exist on the local 7210 SAS M and the far-end peer needs to indicate that it supports VCCV to
allow the user to send vccv-ping message.
Values 1-17407:1 — 4294967295
reply-mode {ip-routed | control-channel} — The reply-mode parameter indicates to the far-end how to
send the reply message. The option control-channel indicates a reply mode in-band using vccv control
channel.
Note that when a VCCV trace message is originated from an S-PE node, the user should used the IPv4
reply mode as the replying node does not know how to set the TTL to reach the sending S-PE node. If
the user attempts this, a warning is issued to use the ipv4 reply mode.
Default control-channel
fc fc-name [profile {in | out} — The fc and profile parameters are used to indicate the forwarding class of
the VCCV trace echo request packets. The actual forwarding class encoding is controlled by the net-
work egress LSP-EXP mappings.
warding class used by the far-end router that receives the message request. The egress mappings of the
egress network interface on the far-end router controls the forwarding class markings on the return reply
message. The LSP-EXP mappings on the receive network interface controls the mapping of the mes-
sage reply back at the originating router.
fc-name — The forwarding class of the VCCV trace echo request encapsulation.

Default be
profile {in | out} — The profile state of the VCCV trace echo request encapsulation.
Default out
size octets — The VCCV ping echo request packet size in octets, expressed as a decimal integer. The
request payload is padded with zeroes to the specified size.
Default 88
Values 88 — 9198
probe-count probe-count — The number of VCCV trace echo request messages to send per TTL value.
Default 1
Values 1 — 10
assumes that the message response will not be received. A request timeout message is displayed by the
Default 3
Values 1 — 60
Default 1
Values 1 — 255
min-ttl min-vc-label-ttl — The TTL value for the VC label of the echo request message for the first hop of
the MS-PW for which the results are to be displayed. This is expressed as a decimal integer. Note that
the outer label TTL is still set to the default of 255 regardless of the value of the VC label.
Default 1
Values 1 — 255
max-ttl max-vc-label-ttl — The TTL value for the VC label of the echo request message for the last hop of
the MS-PW for which the results are to be displayed. This is expressed as a decimal integer. Note that
the outer label TTL is still set to the default of 255 regardless of the value of the VC label.
Default 8
Values 1 — 255
max-fail no-response-count — The maximum number of consecutive VCCV trace echo requests, expressed

as a decimal integer that do not receive a reply before the trace operation fails for a given TTL value.
Default 5
Values 1 — 255

OAM SAA Commands
saa
Syntax saa test-name [owner test-owner] {start | stop} [no-accounting]
Context oam
Description Use this command to start or stop an SAA test.
test-name — Name of the SAA test. The test name must already be configured in the config>saa>test con-
text.
owner test-owner — Specifies the owner of an SAA operation up to 32 characters in length.
Values If a test-owner value is not specified, tests created by the CLI have a default owner
“TiMOS CLI”.
start — This keyword starts the test. A test cannot be started if the same test is still running.
A test cannot be started if it is in a shut-down state. An error message and log event will be generated to
indicate a failed attempt to start an SAA test run. A test cannot be started if it is in a continous state.
stop — This keyword stops a test in progress. A test cannot be stopped if it is not in progress. A log message
will be generated to indicate that an SAA test run has been aborted. A test cannot be stopped if it is in a
continous state.
no-accounting — This parameter disables the recording results in the accounting policy. If no-accounting
is specified, the MIB record produced at the end of the test will not be added to the accounting file. It
will however use up one of the three MIB rows available for the accounting module to be collected.

Twamp commands
twamp
Syntax twamp
Context config>oam-test
Description This command enables TWAMP functionality.
Default TWAMP is disabled.
server
Syntax retry-count retry-count
Context config>test-oam>twamp
Description This command configures the node for TWAMP server functionality.
Default TWAMP is disabled.
prefix
Syntax prefix {ip-prefix | mask}
no prefix
Context config>test-oam>twamp>server
Description This command configures an IP address prefix containing one or more TWAMP clients. In order for a
TWAMP client to connect to the TWAMP server (and subsequently conduct tests) it must establish the con-
trol connection using an IP address that is part of a configured prefix.
Default no prefix
Parameters prefix ip-prefix/mask — Specifies the address prefix and subnet mask of the destination node.
ip-prefix — An IPv4 address in dotted decimal notation.
Values a.b.c.d
Default none
mask — The prefix length.
Values 0—32
Default none

max-conn-prefix
Syntax max-conn-prefix count
no max-conn-prefix
Context config>test-oam>twamp>server>prefix
Description This command configures the maximum number of TWAMP control connections by clients with an IP
address in a specific prefix. A new control connection is rejected if accepting it would cause either the prefix
limit defined by this command or the server limit (max-conn-server) to be exceeded.
The no form of the command sets the default value.
Default no max-conn-prefix
Parameters count — The maximum number of control connections.

Values for 7210 SAS-M.
Values 0—16
Default 8
Values for 7210 SAS-X.
Values 0—64
Default 32
max-conn-server
Syntax max-conn-server count
no max-conn-server
Description This command configures the maximum number of TWAMP control connections from all TWAMP clients.
A new control connection is rejected if accepting it would cause either this limit or a prefix limit (max-conn-
prefix) to be exceeded.
The no form of the command sets the default value.
Default no max-conn-server
Parameters count — The maximum number of control connections.

Values 0—16
Default 8
Values 0—48
Default 24

inactivity-timeout
Syntax inactivity-timeout seconds
no inactivity-timeout
Description This command configures the inactivity timeout for all TWAMP-control connections. If no TWAMP control
message is exchanged over the TCP connection for this duration of time the connection is closed and all
inprogress tests are terminated.
The no form of the command instructs the system to go with the default value.
Default no inactivity-timeout
Parameters retry-count — The duration of the inactivity timeout.
Values 60— 3600
Default 900
max-sess-prefix
Syntax max-sess-prefix count
no max-sess-prefix
Context config>test-oam>twamp>server>prefix
Description This command configures the maximum number of concurrent TWAMP-Test sessions by clients with an IP
address in a specific prefix. A new test session (described by a Request-TW-Session message) is rejected if
accepting it would cause either the limit defined by this command or the server limit (max-sess-server) to be
exceeded.
Default no max-sess-prefix
Parameters count — The maximum number of concurrent test sessions.
Values 0—16
Default 8
Values 0—64
Default 32

max-sess-server
Syntax max-sess-server count
no max-sess-server
Description This command configures the maximum number of concurrent TWAMP-Test sessions across all allowed cli-
ents.
A new test session (described by a Request-TW-Session message) is rejected if accepting it would cause
either the limit defined by this command or a prefix limit (max-sess-prefix) to be exceeded.
Default no max-sessions
Parameters count — The maximum number of concurrent test sessions.

Values 0— 16
Default 8
Values 0— 48
Default 24
port
Syntax port number
no port
Description This command configures the TCP port number used by the TWAMP server to listen for incoming connec-
tion requests from TWAMP clients.
The port number can be changed only when the server has been shutdown.
The no form of this command means to go with the default of 862.
Default no port
Parameters number — The TCP port number.
Values 1 — 65535
Default 862

Show Commands
saa
Syntax saa [test-name] [owner test-owner]
Context show>saa
Description Use this command to display information about the SAA test.
If no specific test is specified a summary of all configured tests is displayed.
If a specific test is specified then detailed test results for that test are displayed for the last three occurrences
that this test has been executed, or since the last time the counters have been reset via a system reboot or
clear command.
Parameters test-name — Enter the name of the SAA test for which the information needs to be displayed. The test name
must already be configured in the config>saa>test context.
This is an optional parameter.
Values 32 characters maximum.
Default If a test-owner value is not specified, tests created by the CLI have a default owner
“TiMOS CLI”.
Output SAA Output — The following table provides SAA field descriptions.
Label Description
Test Name Specifies the name of the test.
Owner Name Specifies the owner of the test.
Description Specifies the description for the test type.
Accounting pol- Specifies the associated accounting policy ID.
icy
Administrative Specifies whether the administrative status is enabled or disabled.
status
Test type Specifies the type of test configured.
Trap generation Specifies the trap generation for the SAA test.
Test runs since Specifies the total number of tests performed since the last time the
last clear tests were cleared.
Number of failed Specifies the total number of tests that failed.
tests run


Last test run Specifies the last time a test was run.
Threshold type Indicates the type of threshold event being tested, jitter-event, latency-
event, or loss-event, and the direction of the test responses received for
a test run:
in — inbound
out — outbound
rt — roundtrip
Direction Indicates the direction of the event threshold, rising or falling.
Threshold Displays the configured threshold value.
Value Displays the measured crossing value that triggered the threshold
crossing event.
Last event Indicates the time that the threshold crossing event occurred.
Run # Indicates what test run produced the specified values.
test-oam
Syntax test-oam
Context show
Description This command enables the context to display Operations, Administration, and Maintenance test parameters
Sample Output
*A:Dut-A# show saa "Dut-A:1413:1501" owner "TiMOS"

===============================================================================
SAA Test Information
===============================================================================
Test name : Dut-A:1413:1501
Owner name : TiMOS
Administrative status : Enabled
Test type : vccv-ping 1413:1501 fc "nc" timeout 10 size 200
count 2
Test runs since last clear : 1
Number of failed test runs : 0
Last test result : Success
-------------------------------------------------------------------------------
Threshold
Type Direction Threshold Value Last Event Run #
-------------------------------------------------------------------------------
Jitter-in Rising None None Never None
Jitter-out Rising None None Never None
Jitter-rt Rising None None Never None


Latency-in Rising None None Never None
Latency-out Rising None None Never None
Latency-rt Rising 100 None Never None
Loss-in Rising None None Never None
Loss-out Rising None None Never None
Loss-rt Rising 2 None Never None
===============================================================================
Test Run: 144
Total number of attempts: 2
Number of requests that failed to be sent out: 0
Number of responses that were received: 2
Number of requests that did not receive any response: 0
Total number of failures: 0, Percentage: 0
(in ms) Min Max Average Jitter
Outbound : 0 0 0 0
Inbound : 10 20 15 0
Roundtrip : 10 20 15 0
Per test packet:
Sequence Outbound Inbound RoundTrip Result
1 0 20 20 EgressRtr(10.20.1.4)
2 0 10 10 EgressRtr(10.20.1.4)
===============================================================================
*A:Dut-A#
eth-cfm
Syntax eth-cfm
Context show
Description This command enables the context to display CFM information.
association
Syntax association [ma-index] [detail]
Context show>eth-cfm
Description This command displays eth-cfm association information.

Parameters ma-index — Specifies the MA index.
Values 1— 4294967295
detail — Displays detailed information for the eth-cfm association.

Sample Output
A:dut-b# show eth-cfm association
======================================================================
CFM Association Table
======================================================================
Md-index Ma-index Name CCM-interval Bridge-id
----------------------------------------------------------------------
1 1 a1 1 1
1 2 a2 1 2
2 1 a1 1 2
2 2 a2 1 1
======================================================================
A:dut-b#
cfm-stack-table
Syntax up | down[port [port-id [vlan vlan-id]]|sdp sdp-id[:vc-id]] [level 0..7] [direction up | down]
Description This command displays stack-table information. This stack-table is used to display the various management
points MEPs and MIPs that are configured on the system. These can be Service based or facility based. The
various option allow the operator to be specific. If no parameters are include then the entire stack-table will
be displayed.
Parameters port port-id — Displays the bridge port or aggregated port on which MEPs or MHFs are configured.
vlan vlan-id — Displays the associated VLAN ID.
Values 0 — 4094
level — Display the MD level of the maintenance point.
Values 0—7
direction up | down — Displays the direction in which the MP faces on the bridge port.
Sample Output
A:dut-b# show eth-cfm cfm-stack-table
========================================================================
CFM SAP Stack Table
========================================================================
Sap Level Dir Md-index Ma-index Mep-id Mac-address
------------------------------------------------------------------------
1/1/9:1 6 Down 1 1 1 00:25:ba:01:c3:6a
1/1/9:1 7 Down 2 2 1 00:25:ba:01:c3:6a
1/1/9:2 6 Down 1 2 1 00:25:ba:01:c3:6a

1/1/9:2 7 Down 2 1 1 00:25:ba:01:c3:6a

========================================================================
========================================================================
CFM Ethernet Tunnel Stack Table
========================================================================
Eth-tunnel Level Dir Md-index Ma-index Mep-id Mac-address
------------------------------------------------------------------------
========================================================================
========================================================================
CFM SDP Stack Table
========================================================================
Sdp Level Dir Md-index Ma-index Mep-id Mac-address
------------------------------------------------------------------------
No Matching Entries
========================================================================
========================================================================
CFM Virtual Stack Table
========================================================================
Service Level Dir Md-index Ma-index Mep-id Mac-address
------------------------------------------------------------------------
No Matching Entries
========================================================================
A:dut-b#
domain
Syntax domain [md-index] [association ma-index | all-associations] [detail]
Description This command displays domain information.

Parameters md-index — Displays the index of the MD to which the MP is associated, or 0, if none.
association ma-index — Displays the index to which the MP is associated, or 0, if none.
all-associations — Displays all associations to the MD.
detail — Displays detailed domain information.
Sample Output
A:dut-b# show eth-cfm domain

==============================================================================
CFM Domain Table
==============================================================================
Md-index Level Name Format
------------------------------------------------------------------------------
1 6 d1 charString
2 7 d2 charString
==============================================================================
A:dut-b#
mep
Syntax mep mep-id domain md-index association ma-index [loopback] [linktrace]
mep mep-id domain md-index association ma-index [remote-mepid mep-id | all-remote-
mepids]
mep mep-id domain md-index association ma-index eth-test-results [remote-peer mac-
address]
mep mep-id domain md-index association ma-index one-way-delay-test [remote-peer mac-
address]
mep mep-id domain md-index association ma-index two-way-delay-test [remote-peer mac-
address]
mep mep-id domain md-index association ma-index two-way-slm-test [remote-peer mac-
address]
Description This command displays Maintenance Endpoint (MEP) information.
Parameters domain md-index — Displays the index of the MD to which the MP is associated, or 0, if none.
association ma-index — Displays the index to which the MP is associated, or 0, if none.
loopback — Displays loopback information for the specified MEP.
linktrace — Displays linktrace information for the specified MEP.
two-way-slm-test — Includes specified MEP information for two-way-slm-test.Sample Output
A:dut-b# show eth-cfm mep 1 domain 1 association 1 linktrace

-------------------------------------------------------------------------------
Mep Information
-------------------------------------------------------------------------------
Md-index : 1 Direction : Down
Ma-index : 1 Admin : Enabled
MepId : 1 CCM-Enable : Enabled
IfIndex : 35946496 PrimaryVid : 1
FngState : fngReset ControlMep : False
LowestDefectPri : macRemErrXcon HighestDefect : none
Defect Flags : None
Mac Address : 00:25:ba:01:c3:6a CcmLtmPriority : 7
CcmTx : 0 CcmSequenceErr : 0
Eth-1Dm Threshold : 3(sec)
Eth-Ais: : Disabled
Eth-Tst: : Disabled

CcmLastFailure Frame:
None
XconCcmFailure Frame:
None
-------------------------------------------------------------------------------
Mep Linktrace Message Information
-------------------------------------------------------------------------------
LtRxUnexplained : 0 LtNextSequence : 2
LtStatus : False LtResult : False
TargIsMepId : False TargMepId : 0
TargMac : 00:00:00:00:00:00 TTL : 64
EgressId : 00:00:00:25:ba:01:c3:6a SequenceNum : 1
LtFlags : useFDBonly
-------------------------------------------------------------------------------
Mep Linktrace Replies
-------------------------------------------------------------------------------
SequenceNum : 1 ReceiveOrder : 1
Ttl : 63 Forwarded : False
LastEgressId : 00:00:00:25:ba:01:c3:6a TerminalMep : True
NextEgressId : 00:00:00:25:ba:00:5e:bf Relay : rlyHit
ChassisIdSubType : unknown value (0)
ChassisId:
None
ManAddressDomain:
None
ManAddress:
None
IngressMac : 00:25:ba:00:5e:bf Ingress Action : ingOk
IngrPortIdSubType : unknown value (0)
IngressPortId:
None
EgressMac : 00:00:00:00:00:00 Egress Action : egrNoTlv
EgrPortIdSubType : unknown value (0)
EgressPortId:
None
Org Specific TLV:
None
A:dut-b#
A:dut-b#
A:dut-b# show eth-cfm mep 1 domain 1 association 1 loopback

-------------------------------------------------------------------------------
Mep Information
-------------------------------------------------------------------------------
Md-index : 1 Direction : Down
Ma-index : 1 Admin : Enabled
MepId : 1 CCM-Enable : Enabled
IfIndex : 35946496 PrimaryVid : 1
FngState : fngReset ControlMep : False
LowestDefectPri : macRemErrXcon HighestDefect : none
Defect Flags : None
Mac Address : 00:25:ba:01:c3:6a CcmLtmPriority : 7
CcmTx : 0 CcmSequenceErr : 0
Eth-1Dm Threshold : 3(sec)
Eth-Ais: : Disabled
Eth-Tst: : Disabled
CcmLastFailure Frame:
None
XconCcmFailure Frame:

None
-------------------------------------------------------------------------------
Mep Loopback Information
-------------------------------------------------------------------------------
LbRxReply : 1 LbRxBadOrder : 0
LbRxBadMsdu : 0 LbTxReply : 0
LbSequence : 2 LbNextSequence : 2
LbStatus : False LbResultOk : True
DestIsMepId : False DestMepId : 0
DestMac : 00:00:00:00:00:00 SendCount : 0
VlanDropEnable : True VlanPriority : 7
Data TLV:
None
A:dut-b#
*A:dut-b# show eth-cfm mep 1 domain 4 association 4 two-way-delay-test remote-peer

00:25:ba:00:5e:bf
==================================================================
Eth CFM Two-way Delay Test Result Table
==================================================================
Peer Mac Addr Delay (us) Delay Variation (us)
------------------------------------------------------------------
00:25:ba:00:5e:bf 507 507
==================================================================
*A:dut-b#
*A:dut-b# show eth-cfm mep 1 domain 4 association 4 two-way-delay-test
==================================================================
Eth CFM Two-way Delay Test Result Table
==================================================================
------------------------------------------------------------------
00:25:ba:00:5e:bf 507 507
==================================================================
*A:dut-b#
*A:dut-a# show eth-cfm mep 2 domain 4 association 4 eth-test-results remote-peer
00:25:ba:01:c3:6a
==============================================================
Eth CFM ETH-Test Result Table
==============================================================
Current Accumulate
FrameCount ErrBits ErrBits
Peer Mac Addr ByteCount CrcErrs CrcErrs
--------------------------------------------------------------
00:25:ba:01:c3:6a 6 0 0
384 0 0
==============================================================
*A:dut-a#
*A:dut-a# show eth-cfm mep 2 domain 4 association 4 eth-test-results
==============================================================
Eth CFM ETH-Test Result Table
==============================================================
Current Accumulate
FrameCount ErrBits ErrBits
Peer Mac Addr ByteCount CrcErrs CrcErrs
--------------------------------------------------------------

00:25:ba:01:c3:6a 6 0 0
384 0 0
==============================================================
*A:dut-a# show eth-cfm mep 2 domain 4 association 4 one-way-delay-test remote-peer
00:25:ba:01:c3:6a
==================================================================
Eth CFM One-way Delay Test Result Table
==================================================================
------------------------------------------------------------------
00:25:ba:01:c3:6a 402 402
==================================================================
*A:dut-a#
*A:dut-a# show eth-cfm mep 2 domain 4 association 4 one-way-delay-test
==================================================================
Eth CFM One-way Delay Test Result Table
==================================================================
------------------------------------------------------------------
00:25:ba:01:c3:6a 402 402
==================================================================
*A:dut-a#
twamp server
Syntax twamp server
Context show>test-oam
Description Used to obtain information about the TWAMP server. It displays summary information for the ip-prefix in
use.
Sample Output
*A:Dut-G>show>test-oam# twamp server
===============================================================================
TWAMP Server
===============================================================================
Admin State : Down Operational State : Down
Up Time : 0d 00:00:00
Current Connections : 0 Max Connections : 8
Connections Rejected : 0 Inactivity Time Out : 900 seconds
Current Sessions : 0 Max Sessions : 8
Sessions Rejected : 0 Sessions Aborted : 0
Sessions Completed : 0
Test Packets Rx : 0 Test Packets Tx : 0
===============================================================================

===============================================================================
TWAMP Server Prefix Summary
===============================================================================
Prefix Current Current Description
Connections Sessions
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
No. of TWAMP Server Prefixes: 0
===============================================================================
*A:Dut-G>show>test-oam#
server all
Syntax server all
Context show>test-oam twamp server

Description Used to display detailed information about the TWAMP server and TWAMP clients using different IP pre-
fix.
Sample Output
7210SASM# show test-oam twamp server all
===============================================================================
TWAMP Server
===============================================================================
Admin State : Up Operational State : Up
Up Time : 0d 08:17:34
Connections Rejected : 0 Inactivity Time Out : 900 seconds
===============================================================================
===============================================================================
TWAMP Server Prefix 30.1.1.0/24
===============================================================================
Connections Rejected : 0
===============================================================================
===============================================================================
Connection information for TWAMP server prefix 30.1.1.0/24
===============================================================================
Client State Curr Sessions Sessions Rejected Sessions Completed
Idle Time (s) Test Packets Rx Test Packets Tx

-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
No. of TWAMP Server Connections for Prefix 30.1.1.0/24: 0
===============================================================================
===============================================================================
===============================================================================
===============================================================================
===============================================================================
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
===============================================================================
===============================================================================
No. of TWAMP Server Prefixes: 2
===============================================================================
server prefix
Syntax server prefix ip-prefix/mask
Context show>test-oam twamp server
Description Display information about the TWAMP clients using the specified prefix.
Sample output
*A:7210SAS# show test-oam twamp server prefix 60.1.1.0/24
===============================================================================
===============================================================================
===============================================================================

===============================================================================
===============================================================================
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
===============================================================================
Parameters ip-prefix — The destination address of the static route.

Values [18 chars max]
mask — The prefix length.
testhead-profile
Syntax testhead-profile profile-id
Context show>test-oam
Description Specifies the testhead profile ID to use with this run/session of testhead invocation. Testhead profile must be
configure beforehand using the commands under config> test-oam> testhead-profile>.
Output Testhead-profile Output — The following table provides testhead-profile field descriptions.
Label Description
Description Displays the description configured by the user for the test.
Profile Id Displays the profile identifier.
CIR Configured Displays the value of the CIR configured.
PIR Configured Displays the value of the PIR configured.
Frame Size Displays the size of the frame.
CIR Operational Displays the value of the CIR operational rate configured.
PIR Operational Displays the value of the PIR operational rate configured.
CIR Rule Displays the adaptation rule configured by the user.
InPrf Dot1p Displays the dot1p value used to identify green or in-profile packets.
Ref. Count Displays the total number of testhead (completed or running) sessions
pointing to a profile or acceptance criteria or a frame payload.
OutPrf Dot1p Displays the dot1p value used to identify green or out-of-profile pack-
ets.


Duration Hrs, Displays the test duration in hours, minutes, and seconds.
mins, and secs
Loss TH Displays the user configured loss threshold value for comparison with
measured value.
Jitter TH Displays the user configured jitter threshold value for comparison with
measured value.
InProf Loss TH Displays the user configured in-profile loss threshold value for com-
parison with measured value.
OutProf Loss TH Displays the user configured out-of-profile loss threshold value for
comparison with measured value.
Latency TH Displays the user configured latency threshold value for comparison
with measured value.
InProf Latency Displays the user configured in-profile latency threshold value for
TH comparison with measured value.
OutProf Latency Displays the user configured out-of-profile latency threshold value for
InProf Jitter TH Displays the user configured in-profile jitter threshold value for com-
parison with measured value.
OutProf Jitter Displays the user configured out-of-profile jitter threshold value for
CIR TH Displays the user configured CIR threshold value for comparison with
measured value.
PIR TH Displays the user configured PIR threshold value for comparison with
measured value.
Payload Type Identifies the type of the payload.
Dst Mac Displays the value of destination MAC configured by the user to use in
the frame generated by the testhead tool
Src Mac Displays the value of source MAC configured by the user to use in the
frame generated by the testhead tool
Vlan Tag 1 Displays the values of the outermost vlan-tag configured by the user to
use in the frame generated by the testhead tool.
Vlan Tag 2 Displays the values of the second vlan-tag configured by the user to
Ethertype Displays the values of the ethertype configured by the user to use in the


TOS Displays the values of the IP TOS (Type of Service) configured by the
user to use in the frame generated by the testhead tool.
Src. IP Displays the values of the source IPv4 address configured by the user
to use in the frame generated by the testhead tool.
L4 Dst Port Displays the values of the TCP header configured by the user to use in
the frame generated by the testhead tool.
Protocol Displays the values of the IP protocol value configured by the user to
Data Pattern Displays the values of the data pattern configured by the user to use in
DSCP Displays the values of the DSCP configured by the user to use in the
TTL Displays the values of the IP TTL (Time-to-Live) value configured by
the user to use in the frame generated by the testhead tool.
Dst. IP Displays the values of the destination IPv4 address configured by the
user to use in the frame generated by the testhead tool.
L4 Src Port Displays the values of the source port configured by the user to use in
Sample Output
*A:7210SAS>config>test-oam># show test-oam testhead-profile 1
===============================================================================
Y.1564 Testhead Profile
===============================================================================
Description : Testhead_Profile_1
Profile Id : 1 Frame Size : 512
CIR Configured : 100 CIR Operational : 96
PIR Configured : 200 PIR Operational : 200
CIR Rule : max Ref. Count : 0
InPrf Dot1p : 2 OutPrf Dot1p : 4
Duration Hrs : 0
Duration Mins : 3
Duration Secs : 0
-------------------------------------------------------------------------------
Acceptance Criteria Id 1
-------------------------------------------------------------------------------
Loss TH : 0.000100 Jitter TH : 100
InProf Loss TH : 0.000100 InProf Jitter TH : 100
OutProf Loss TH : 0.000100 OutProf Jitter TH : 100

Latency TH : 100 Ref. Count : 0

InProf Latency TH : 100 CIR TH : 1000
OutProf Latency TH : 100 PIR TH : 200
-------------------------------------------------------------------------------
Frame Payload Id 1
-------------------------------------------------------------------------------
Payload Type : tcp-ipv4
Description : Frame_Payload_1
Dst Mac : 00:00:00:00:00:02
Src Mac : 00:00:00:00:00:01
Vlan Tag 1 : Not configured
Vlan Tag 2 : Not configured
Ethertype : 0x0800 DSCP : af11
TOS : 8 TTL : 64
Src. IP : 1.1.1.1 Dst. IP : 2.2.2.2
L4 Dst Port : 50 L4 Src Port : 40
Protocol : 6 Ref. Count : 0
Data Pattern : a1b2c3d4e5f6
===============================================================================
*A:7210SAS>config>test-oam>#
testhead
Syntax testhead test-name owner test-owner
Context show
Parameters test-name — Name of the SAA test. The test name must already be configured in the config>saa>test con-
text.
“TiMOS CLI”.
Output Testhead Output — The following table provides “testhead test-me owner owner-me” field descriptions.
Label Description
Owner Displays the owner of the test.

Name Displays the name of the test.
Description Displays the description for the test type.
Profile Id Displays the associated profile ID.

Accept. Crit. Id Displays the test acceptance criteria ID to be used by the testhead
OAM tool to declare the PASS/FAIL result at the completion of the
test.

Frame Payload Id Displays frame payload ID, that determines the frame content of the
frames generated by the tool.
Frame Payload Displays the type of frame payload to be used in frames generated by
Type testhead tool.
Color Aware Test Displays if color aware tests need to be executed.
SAP Displays the SAP ID configured.
Completed Displays if the test has been completed.
Stopped Displays if the test has been stopped.
FC Displays the forwarding class (FC) to use to send the frames generated
by the testhead tool.
Start Time Displays the start time of the test.
End Time Displays the end time of the test.
Total time taken Displayes the total time taken to execute the test.
total pkts in us Displays the total packets in microseconds.
OutPrf pkts in Displays the out-of-profile packets in microseconds.

us
InPrf pkts in us Displays the in-profile packets in microseconds.
Total Injected Displays the running count of total injected packets, including marker
packets.
Total Received Displays the running count of total received packets, including marker
packets.
OutPrf Injected Displays the running count of total out-of-profile packets, excluding
marker packets.
OutPrf Received Displays the running count of total out-of-profile packets received,
including marker packets.
InPrf Injected Displays the running count of total in-profile packets, excluding
marker packets.
InPrf Received Displays the running count of total in-profile packets received, includ-
ing marker packets.
Throughput Con- Displays the CIR Throughput rate Threshold Configured (in Kbps).
figd

Throughput Oper Displays the operational rate used for the configured rate. Operational
rate is arrived considering the adaptation rule configured by the user
and supported hardware rate.
Throughput Mea- Displays the CIR Throughput Measured Value (in Kbps).
surd
PIR Tput Displays the PIR Throughput rate Threshold Configured (in Kbps).
Threshld
PIR Tput Meas Displays the PIR Throughput rate Measured Value (in Kbps).
FLR Configured Displays the Frame Loss Ratio Threshold Configured (in-profile).
FLR Measurd Displays the Frame Loss Ratio Measured (in-profile).
FLR Acceptance Displays Pass, Fail, or Not Applicable. It displays Pass, if the mea-
sured value is less than or equal to the configured threshold and dis-
plays "Fail" otherwise, and displays "Not Applicable", if the FLR
criteria is not used to determine whether the test is in Passed or Failed
status.
OutPrf FLR Conf Displays the out-of-profile Frame Loss Ratio configured.
OutPrf FLR Meas Displays the out-of-profile Frame Loss Ratio measured.
OutPrf FLR Acep Displays Pass, Fail, or Not Applicable. It displays Pass, if the mea-
plays "Fail" otherwise, and displays "Not Applicable", if the out-of-
profile FLR criteria is not used to determine whether the test is in
Passed or Failed status.
InPrf FLR Conf Displays the in-profile Frame Loss Ratio configured.
InPrf FLR Meas Displays the in-profile Frame Loss Ratio measured.
InPrf FLR Acep Displays Pass, Fail, or Not Applicable. It displays Pass, if the mea-
plays "Fail" otherwise, and displays "Not Applicable", if the in-profile
FLR criteria is not used to determine whether the test is in Passed or
Failed status.
Latency Con- Displays the Latency Threshold configured (in microseconds)

figd(us)
Latency Mea- Displays the Average Latency measured (in microseconds)

surd(us)

Latency Accep- Displays Pass, Fail, or Not Applicable. It displays Pass, if the mea-
tance sured value is less than or equal to the configured threshold and dis-
plays "Fail" otherwise, and displays "Not Applicable", if the latency
status.
OutPrf Lat Displays the out-of-profile latency configured.

Conf(us)
OutPrf Lat Displays the out-of-profile latency measured.

Meas(us)
OutPrf Lat Acep Displays Pass, Fail, or Not Applicable. It displays Pass, if the mea-
profile latency criteria is not used to determine whether the test is in
InPrf Lat Displays the in-profile latency configured.

Conf(us)
InPrf Lat Displays the in-profile latency measured.

Meas(us)
InPrf Lat Acep Displays Pass, Fail, or Not Applicable. It displays Pass, if the mea-
latency criteria is not used to determine whether the test is in Passed or
Failed status.
Jitter Con- Displays the Jitter Threshold Configured (in microseconds).

figd(us)
Jitter Mea- Displays the Jitter Measured (in microseconds).

surd(us)
Jitter Accep- Displays Pass, Fail, or Not Applicable. It displays Pass, if the mea-
tance sured value is less than or equal to the configured threshold and dis-
plays "Fail" otherwise, and displays "Not Applicable", if the jitter
status.
OutPrf Jit Displays the out-of-profile Jitter configured.

Conf(us)
OutPrf Jit Displays the out-of-profile Jitter measured.

Meas(us)

OutPrf Jit Acep Displays Pass, Fail, or Not Applicable. It displays Pass, if the mea-
profile jitter criteria is not used to determine whether the test is in
InPrf Jit Displays the in-profile Jitter configured.

Conf(us)
InPrf Jit Displays the in-profile Jitter measured.

Meas(us)
InPrf Jit Acep Displays Pass, Fail, or Not Applicable. It displays Pass, if the mea-
jitter criteria is not used to determine whether the test is in Passed or
Failed status.
Total Pkts. Tx. Total number of packets ( that is, data and marker) transmitted by the
testhead session for the duration of the test.
OutPrf Latency Total number of out-of-profile marker packets received by the testhead
Pkt* session for the duration of the test.
Total Tx. Fail Total number of failed transmission attempts by the testhead session
for the duration of the test.
Latency Pkts. Tx Total number of marker packets transmitted by the testhead session for
the duration of the test.
InPrf Latency Total number of in-profile marker packets received by the testhead ses-
Pkt* sion for the duration of the test.
Sample output
*A:7210SAS# show testhead test-me owner owner-me
===============================================================================
Y.1564 Testhead Session
===============================================================================
Owner : owner-me
Test : test-me
Profile Id : 1 SAP : 1/1/2:100
Accept. Crit. Id : 0 Completed : Yes
Frame Payload Id : 1 Stopped : No
Frame Payload Type : tcp-ipv4 FC : be
Color Aware Test : Yes
Start Time : 08/08/2001 19:37:11
End Time : 08/08/2001 19:40:16
Total time taken : 0d 00:03:05
-------------------------------------------------------------------------------

Latency Results
-------------------------------------------------------------------------------
(total pkts in us): Min Max Average Jitter
Roundtrip : 0 0 0 0
(OutPrf pkts in us): Min Max Average Jitter

Roundtrip : 0 0 0 0
(InPrf pkts in us): Min Max Average Jitter

Roundtrip : 0 0 0 0
-------------------------------------------------------------------------------
Packet Count
-------------------------------------------------------------------------------
Total Injected : 42273637
Total Received : 0
OutPrf Injected : 16898179

OutPrf Received : 0
InPrf Injected : 25375450

InPrf Received : 0
-------------------------------------------------------------------------------
Test Compliance Report
-------------------------------------------------------------------------------
Throughput Configd : 962388
Throughput Oper : 962384
Throughput Measurd : 0
PIR Tput Threshld : Not configured

PIR Tput Meas : 0
CIR Tput Threshld : Not configured

CIR Tput Meas : 0
FLR Configured : None

FLR Measurd : Not Applicable
FLR Acceptance : Fail
OutPrf FLR Conf : None

OutPrf FLR Meas : Not Applicable
OutPrf FLR Acep : Not Applicable
InPrf FLR Conf : None

InPrf FLR Meas : Not Applicable
InPrf FLR Acep : Not Applicable
Latency Configd(us): None

Latency Measurd(us): None
Latency Acceptance : Not Applicable
OutPrf Lat Conf(us): None

OutPrf Lat Meas(us): None
OutPrf Lat Acep : Not Applicable
InPrf Lat Conf(us) : None

InPrf Lat Meas(us) : None
InPrf Lat Acep : Not Applicable

Jitter Configd(us) : None

Jitter Measurd(us) : None
Jitter Acceptance : Not Applicable
OutPrf Jit Conf(us): None

OutPrf Jit Meas(us): None
OutPrf Jit Acep : Not Applicable
InPrf Jit Conf(us) : None

InPrf Jit Meas(us) : None
InPrf Jit Acep : Not Applicable
Total Pkts. Tx. : 13 Latency Pkts. Tx. : 8

OutPrf Latency Pkt*: 0 InPrf Latency Pkt*: 0
Total Tx. Fail : 0
===============================================================================
*A:7210SAS# show testhead test-me owner owner-me

Clear Commands
saa
Syntax saa-test [test-name [owner test-owner]]
Context clear
Description Clear the SAA results for the latest and the history for this test. If the test name is omitted, all the results for
all tests are cleared.
Parameters test-name — Name of the SAA test. The test name must already be configured in the config>saa>test con-
text.
“TiMOS CLI”.
test-oam
Syntax test-oam
Context clear
Description Clears the Operations, Administration, and Maintenance test parameters
twamp server
Syntax twamp server
Context clear>test-oam
Description Clear TWAMP server statistics.
testhead
Syntax testhead result [ test-name ] [owner test-owner]
Context oam>clear
Description Clear the testhead results identified by the test-name and test-owner.

Parameters result — Clears the test results from the latest history for the test.
test-name — Name of the test
owner test-owner — Specifies the owner of a testhead operation.
testhead
Syntax testhead testhead-profile profile-id
Context oam>clear
Description Clear the testhead results identified by the testhead-profile.

Parameters testhead-profile profile-id — Clears the testhead profile ID to use with this run/session of testhead invoca-
tion.
Values [1..10]


Tools
Tools Command Reference
Command Hierarchies
• Tools Dump Commands on page 293
• Tools Perform Commands on page 295
Tools Dump Commands
tools
— dump
—Tools Dump Commands
— accounting-policy acct-policy-id flash-write-count [clear]

— eth-ring ring-index [clear]
— eth-ring control-sap-tag port-id [list-in-use|next-available] (Supported only on 7210 SAS-
X)
— lag lag-id lag-id
— redundancy
— multi-chassis
— mc-endpoint peer ip-address
— sync-database [peer ip-address] [port port-id | lag-id] [sync-tag sync-
tag] [application application] [detail] [type type]
— router router-instance
— dintf [ip-address]
— filter-info [verbose]
— l3-info
— l3-stats [clear]
— ldp
— fec prefix ip-prefix/mask
— fec vc-type {vc-type} agi agi
— fec vc-type {ethernet|vlan} vc-id vc-id
— instance
— interface [ip-int-name | ip-address]
— memory-usage
— peer ip-address
— session [ip-addr[:label-space] [connection|peer|adjacency]
— sockets
— timers
— mpls
— cspf to ip-addr [from ip-addr] [strict-srlg] [srlg-group grp-id...(up to 8
max)] [bandwidth bandwidth] [include-bitmap bitmap] [exclude-bit-
map bitmap] [hop-limit limit] [exclude-address excl-addr [excl-
addr...(upto 8 max)]] [use-te-metric] [exclude-node excl-node-id [excl-
node-id...(upto 8 max)]] [skip-interface interface-name]
— force-switch-path lsp lsp-name path path-name
— no force-switch-path lsp lsp-name

— ftn [endpoint endpoint | sender sender | nexthop nexthop | lsp-id lsp-id |

tunnel-id tunnel-id | label start-label end-label]
— ilm [endpoint endpoint | sender sender | nexthop nexthop | lsp-id lsp-id |
tunnel-id tunnel-id | label start-label end-label]
— lspinfo [lsp-name] [detail]
— memory-usage
— resignal lsp lsp-name path path-name delay minutes
— resignal {p2mp-lsp p2mp-lsp-name p2mp-instance p2mp-instance-
name | p2mp-delay p2mp-minutes}
— te-lspinfo [endpoint ip-address] [sender ip-address] [lspid lsp-id]
[detail]
— te-lspinfo [endpoint ip-address] [sender ip-address] [lspid lsp-id]
[detail] switch-path lsp lsp-name path path-name
— tp-tunnel
— clear {lsp-name | id tunnel-id}
— force {lsp-name | id tunnel-id}
— manual {lsp-name | id tunnel-id}
— lockout {lsp-name | id tunnel-id}
— trap-suppress number-of-traps time-interval
— update-path lsp lsp-name path path-name new-path path-name
— ospf ospf-instance
— abr [detail]
— asbr [detail]
— bad-packet interface-name
— leaked-routes [summary | detail]
— memory-usage [detail]
— request-list [neighbor ip-address] [detail]
— request-list virtual-neighbor ip-address area-id area-id [detail]
— retransmission-list [neighbor ip-address] [detail]
— retransmission-list virtual-neighbor ip-address area-id area-id [detail]
— route-summary
— route-table ip-prefix/mask [type] [detail]
— ospf3
— rsvp
— psb [endpoint endpoint-address] [sender sender-address] [tunnelid tun-
nel-id] [lspid lsp-id]
— rsb [endpoint endpoint-address] [sender sender-address] [tunnelid tun-
— tcsb[endpoint endpoint-address] [sender sender-address] [tunnelid tun-
— neighbor [ip-address] [detail]
— service
— base-stats [clear]
— dpipe service-id
— dtls service-id
— iom-stats [clear]
— l2pt-diags
— l2pt-diags clear
— l2pt-diags detail
— vpls-fdb-stats [clear]
— vpls-mfib-stats [clear]
— system
— cpu-pkt-stats
— system-resources slot-number
— system-resources sap-ingress-qos

Tools
Tools Perform Commands

tools
— perform
—Tools Perform Commands
— cron
— action
— stop [action-name] [owner action-owner] [all]
— tod
— re-evaluate
— customer customer-id [site customer-site-name]
— filter ip-filter [filter-id]
— filter ipv6-filter [filter-id]
— filter mac-filter [filter-id]
— service id service-id [sap sap-id]
— tod-suite tod-suite-name
— eth-ring
— clear ring-index
— force ring-index path {a|b}
— manual ring-index path {a|b}
— lag
— clear-force all-mc
— clear-force lag-id lag-id [sub-group sub-group-id]
— clear-force peer-mc ip-address
— force all-mc {active | standby}
— force lag-id lag-id [sub-group sub-group-id] {active | standby}
— force peer-mc peer-ip-address {active | standby}
— log
— test-eventrouter [router-instance]
— isis (Not supported on 7210 SAS-M device configured in Access uplink mode)
— mpls (Not supported on 7210 SAS-M device configured in Access uplink mode)
— cspf to ip-addr [from ip-addr] [bandwidth bandwidth] [include-bitmap
bitmap] [exclude-bitmap bitmap] [hop-limit limit] [exclude-address
excl-addr [excl-addr...(up to 8 max)]] [use-te-metric] [skip-interface
interface-name]
— resignal lsp lsp-name path path-name delay minutes
— trap-suppress number-of-traps time-interval
— ospf [ospf-instance] (Not supported on 7210 SAS-M device configured in Access
uplink mode)
— ospf3
— ldp-sync-exit
— refresh-lsas
— run-manual-spf
— service
— id service-id
— endpoint endpoint-name
— force-switchover sdp-id:vc-id
— no force-switchover


Tools
Tools Configuration Commands
Generic Commands
tools
Syntax tools
Context root
Description This command enables the context to enable useful tools for debugging purposes.
Default none
Parameters dump — Enables dump tools for the various protocols.

perform — Enables tools to perform specific tasks.

Dump Commands
Dump Commands
dump
Syntax dump router-name
Context tools
Description The context to display information for debugging purposes.

Default none
Parameters router-name — Specify a router name, up to 32 characters in length.

Default Base
accounting-policy
Syntax accounting-policy acct-policy-id flash-write-count [clear]
Context tools>dump
Description The above command dumps the total count of flash writes for the accounting policy specified by the user.
The 'clear' option allows the user to clear the count maintained per accounting policy and starts the counter
afresh.
Parameters flash-write-count — This is a keyword used to dump the total number of flash writes up to the present for the
accounting policy specified by accounting-policy 'id'.
acct-policy-id — Identifies the Accounting policy.
Values 1 - 99
clear — This keyword clears statistics.
eth-ring
Syntax eth-ring ring-index [clear]
eth-ring control-sap-tag port-id [list-in-use|next-available] (Supported only on 7210 SAS-X)
Context tools>dump
Description The command displays Ethernet-ring information.
Parameters ring-index — Specify ring index.

Values 1 —128
clear — This keyword clears statistics.

Tools
eth-ring
Syntax eth-ring control-sap-tag port-id [list-in-use|next-available] (Supported only on 7210 SAS-X)
Context tools>dump
Description This command allows the user to list the VLAN IDs on the given port in use as G.8032 control SAP tags
using the 'list-in-use' option. These VLAN IDs cannot be used with any other SAP on the same port (even
the Default SAP, will not receive packets with this VLAN ID).
User can obtain the next available VLAN ID to use as a control SAP tag using the 'next-available' option.
This option returns a VLAN ID, after ensuring the following:
• The VLAN ID is in the range of VLAN IDs reserved for G.8032 control SAP tags.
• The VLAN ID is not being used by any service SAP on the same port.
• This VLAN ID is not being used as a control-sap-tag on any other eth-ring instance configured on the
same port.
Parameters port-id — Specify the port ID.

Values slot/mda/port
list-in-use — Lists the in-use control SAP VLAN IDs on the port.
next-available — Lists the next available VLAN ID which can be used as control SAP TAG.
lag
Syntax lag lag-id lag-id
Context tools>dump
Description This tool displays LAG information.
Parameters lag-id — Specify an existing LAG id.

Values 1 — 12
*A:kiran3>tools>dump# lag lag-id 1

Port state : Up
Selected subgrp : 1
NumActivePorts : 2
ThresholdRising : 2
ThresholdFalling: 0
IOM bitmask : 2
Config MTU : 1522
Oper. MTU : 1522
Bandwidth : 200000
multi-chassis : NO
------------------------------------------------------------------------------------
Indx PortId RX pkts TX pkts State Active Port Cfg Oper Speed BW AP CS
Pri Mtu Mtu
------------------------------------------------------------------------------------
0 1/1/1 1 1 Up yes 32768 1522 1522 1000 100000 0 2

Dump Commands
1 1/1/2 0 0 Up yes 32768 1522 1522 1000 100000 0 2
eth-ring
Syntax eth-ring ring-index [clear]
Context tools>dump
Description This tool displays eth-ring information.
Parameters ring-index — Specifies the ring index.

Values 1 — 128
clear — Clears the eth-ring statistics.
redundancy
Syntax redundancy
Context tools>dump
Description This command enables the context to dump tools for redundancy.
multi-chassis
Syntax multi-chassis
Context tools>dump>redundancy>multi-chassis
Description This command enables the context to dump tools for multi-chassis redundancy.
mc-endpoint
Syntax multi-chassis
Description This command dumps multi-chassis endpoint information.
Parameters peer ip-address — Specifies the peer’s IP address.

Tools
sync-database
Syntax sync-database [peer ip-address] [port port-id | lag-id] [sync-tag sync-tag] [application
application] [detail] [type type]
Description This command dumps MCS database information.

peer ip-address — Specifies the peer’s IP address.
port port-id | lag-id — Indicates the port or LAG ID to be synchronized with the multi-chassis peer.
Values slot/mda/port or lag-lag-id
sync-tag sync-tag — Specifies a synchronization tag to be used while synchronizing this port with the
multi-chassis peer.
application application — Specifies a particular multi-chassis peer synchronization protocol application.
Values igmp-snooping: igmp-snooping
mc-ring: multi-chassis ring
sub-host-trk: subscriber host tracking
type type — Indicates the locally deleted or alarmed deleted entries in the MCS database per multi-chassis
peer.
Values alarm-deleted, local-deleted
system
Syntax cpu-pkt-stats
Context tools>dump>system
Description This command dumps tools for system information.
cpu-pkt-stats
Syntax cpu-pkt-stats
Context tools>dump>system
Description This command dumps statistics for CPU traffic.

Dump Commands
system-resources
Syntax system-resources slot-number
system-resources sap-ingress-qos
Context tools>dump
Description This command displays system resource information.
Default none
Parameters slot-number — Specify a specific slot to view system resources information.
Values 1
sap-ingress-qos — This command provides details on usage of resources allocated for QoS classification
and different match criteria under QoS classification.
Sample Output
tools dump system-resources sap-ingress-qos — The following table describes tools dump sys-
tem-resource sap-ingress-qos output fields:
Table 13: Output fieldstools dump system-resource sap-ingress-qos

Labels Descriptions
Total Chunks Configured Displays the total number of chunks configured

for use by SAP ingress QoS classification across
all the match criteria.
Total Chunks Available Displays the total number of chunks alloted by

software for use by SAP ingress QoS classification
across all the match criteria.
Number of Chunks in Use Displays the total number of chunks in use by SAP
for SAP ingress QoS classification.
Number of Free Chunks Displays the total number of chunks available for
use by SAP for SAP ingress QoS classification.
Number of Chunks in use for IP Displays the total number of chunks in use for by
match SAP that use IP classification match criteria in the
SAP ingress QoS policy.
Number of Chunks in use for Displays the total number of chunks in use for by
IPv6 match SAP that use IPv6 classification match criteria in
the SAP ingress QoS policy.

Tools
Table 13: Output fieldstools dump system-resource sap-ingress-qos

Labels Descriptions
Number of Chunks in use for Displays the total number of chunks in use for by
MAC match SAP that use MAC classification match criteria in
the SAP ingress QoS policy.
Classification Entries The total number of Classification entries that are

available/allocated/free per chunk. Information is
displayed only for chunks that are in use.
Meters - The total number of Meters that are
available/allocated/free per chunk. Information is
displayed only for chunks that are in use.
Number of Chunks available for Displays the total number of chunks in use for by
use with IP match criteria SAP that use IP classification match criteria in the
SAP ingress QoS policy. This assumes all of the
free chunks are alloted to IP classification match
criteria.
use with IPv6 match criteria SAP that use IPv6 classification match criteria in
the SAP ingress QoS policy. This assumes all of
the free chunks are alloted to IPv6 classification
match criteria.
use with MAC match criteria SAP that use MAC classification match criteria in
the SAP ingress QoS policy. This assumes all of
the free chunks are alloted to MAC classification
match criteria.
*A:7210-SAS>tools>dump# system-resources tools dump system-resources sap-ingress-qos

Sap Resource Manager info at 001 d 10/11/12 04:42:00.043:
Sap Ingress Resource Usage for Slot #1, Cmplx #0:
Total Chunks Configured : 6

Total Chunks Available : 6
Number of Chunks in Use : 1
Number of Free Chunks : 5
Number of Chunks in use for IP match :0
Number of Chunks in use for IPv6 match :0
Number of Chunks in use for MAC match :1
| Classification Entries | Meters
Chunk | Type | Total |Allocated| Free | Total |Allocated| Free
--------+------+--------+---------+--------+--------+---------+---------
0| Mac| 512| 2| 510| 256| 1| 255
Number of Chunks available for use with IP match* : 5

Number of Chunks available for use with IPv6 match* : 0
Number of Chunks available for use with MAC match* : 5
* - Assumes all remaining chunks are used

Dump Commands
*A:Dut-A>tools>dump#

Tools
Service Commands
service
Syntax service
Context tools>dump
Description Use this command to configure tools to display service dump information.
base-stats
Syntax base-stats [clear]
Context tools>dump>service
Description Use this command to display internal service statistics.
Default none
Parameters clear — Clears stats after reading.
dpipe
Syntax dpipe service-id
Description This command displays debug information for specified service.
Parameters service-id — Displays specified service ID details.

Values 1 - 2147483647
dtls
Syntax dtls service-id
Description Use this command to display TLS service statistics.
Default none
Parameters service-id — Displays specified service ID details.

Service Commands
iom-stats
Syntax iom-stats [clear]
Description Use this command to display IOM message statistics.
Default none
l2pt-diags
Syntax l2pt-diags
l2pt-diags clear
l2pt-diags detail
Description Use this command to display L2pt diagnostics.

Default none
Parameters clear — Clears the diags after reading.

Sample Output
A:ALA-48>tools>dump>service# l2pt-diags
[ l2pt/bpdu error diagnostics ]
Error Name | Occurence | Event log
-----------------+-------------+-----------------------------
[ l2pt/bpdu forwarding diagnostics ]
Rx Frames | Tx Frames | Frame Type

------------+-------------+----------------------------------
A:ALA-48>tools>dump>service#
A:ALA-48>tools>dump>service# l2pt-diags detail

[ l2pt/bpdu error diagnostics ]
Error Name | Occurence | Event log
-----------------+-------------+-----------------------------
[ l2pt/bpdu forwarding diagnostics ]
Rx Frames | Tx Frames | Frame Type

------------+-------------+----------------------------------
[ l2pt/bpdu config diagnostics ]
WARNING - service 700 has l2pt termination enabled on all access points :
consider translating further down the chain or turning it off.

Tools

A:ALA-48>tools>dump>service#
vpls-fdb-stats
Syntax vpls-fdb-stats [clear]
Description Use this command to display VPLS FDB statistics.

Default none
vpls-mfib-stats
Syntax vpls-mfib-stats [clear]
Description Use this command to display VPLS MFIB statistics.
Default none

Router Commands
Router Commands
router
Syntax router router-instance
Context tools>dump
tools>perform
Description This command enables tools for the router instance.
Default none
Parameters router router-instance — Specifies the router name or service ID.
Values router-name: Base, management
Default Base
dintf
Syntax dintf [ip-address]
Context tools>dump>router
Description This command displays the internal IP interface details.
Parameters ip-address — Only displays the internal IP interface details.
filter-info
Syntax filter-info [verbose]
Description This command dumps the hardware-specific filter information.
Parameters verbose — Displays the hardware information of the filter.
l3-info
Syntax lag
Description This command dumps the hardware-specific L3 information.

Tools
l3-stats
Syntax l3-stats [clear]
Description This command dumps the hardware-specific L3 statistics.
Parameters clear — Clears the hardware information of the filter.
eth-ring
Syntax eth-ring
Context tools>perform
Description This command configures tools to control Ethernet rings.
clear
Syntax clear ring-index
Context tools>perform>eth-ring
Description This command removes all switching operational commands. The clear command is used for the following
operations:
• Clears an active local administrative command (for example the Force switch or Manual switch com-
mands).
• Triggers reversion before the WTR or WTB timer expires in case of revertive operation.
• Triggers reversion in case of non-revertive operation.
Parameters ring-index — Specifies the ring index of the Ethernet ring.

Values 1—128
force
Syntax force ring-index path {a|b}
Description This command forces the specified path into a blocked state.
Values 1—128
path {a|b} — Specifies the path of the Ethernet ring.

Router Commands
manual
Syntax manual ring-index path {a|b}
Description This command sets the specified eth-ring path into a blocked state.

Values 1—128
path {a|b} — Specifies the path of the Ethernet ring.
lag
Syntax lag
Description This command configures tools to control LAG.
clear-force
Syntax clear-force lag-id lag-id [sub-group sub-group-id]
clear-force all-mc
clear-force peer-mc ip-address
Context tools>perform>lag
Description This command clears a forced status.
Parameters lag-id lag-id — Specify an existing LAG id.

Values 1-200
all-mc — Clears all multi-chassis LAG information.
force
Syntax force lag-id lag-id [sub-group sub-group-id] {active | standby}
force all-mc {active | standby}
force peer-mc peer-ip-address {active | standby}
Context tools>perform>lag
Description This command forces an active or standy status.
Parameters active — If active is selected, then all drives on the active CPM are forced.
all-mc — Clears all multi-chassis LAG information.

Tools
peer-mc — Clears mutichassis LAG peer information.

standby — If standby is selected, then all drives on the standby CPM are forced.
lag-id lag-id — Specify an existing LAG id.
Values 1—6
log
Syntax log
Description Tools for event logging.
test-event
Syntax test-event
Context tools>perform>log
Description This command causes a test event to be generated. The test event is LOGGER event #2011 and maps to the
tmnxEventSNMP trap in the TIMETRA-LOG-MIB.
interface
Syntax interface [ip-int-name | ip-address]
Context tools>dump>router>ldp
Description This command displays information for an LDP interface.
Default none
Parameters ip-int-name — Specifies the interface name.

ip-address — Specifies the IP address.
ldp
Syntax ldp
Description This command enables dump tools for LDP.
Default none

Router Commands
peer
Syntax peer ip-address
Description This command displays information for an LDP peer.
Default none
Parameters ip-address — Specifies the IP address.
fec
Syntax fec prefix [ip-prefix/mask]
fec vc-type {ethernet | vlan} vc-id vc-id
Description This command displays information for an LDP FEC.

Default none
Parameters ip-prefix/mask — Specifies the IP prefix and host bits.

Values host bits: must be 0
mask: 0 — 32
vc-type — Specifies the VC type signaled for the spoke or mesh binding to the far end of an SDP. The VC
type is a 15 bit-quantity containing a value which represents the type of VC. The actual signaling of the
VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type
command can still be used to define the Dot1q value expected by the far-end provider equipment. A
change of the binding’s VC type causes the binding to signal the new VC type to the far end when
signaling is enabled.
VC types are derived according to IETF draft-martini-l2circuit-trans-mpls.
• Ethernet — The VC type value for Ethernet is 0x0005.
• VLAN — The VC type value for an Ethernet VLAN is 0x0004.
vc-id — Specifies the virtual circuit identifier.
Values 1 — 4294967295
instance
Syntax instance
Description This command displays information for an LDP instance.

Tools
memory-usage
Syntax memory-usage
Description This command displays memory usage information for LDP.
Default none
session
Syntax session [ip-address |:label space ] [connection | peer | adjacency ]
Description This command displays information for an LDP session.
Default none
Parameters ip-address — Specifies the IP address of the LDP peer.
label-space — Specifies the label space identifier that the router is advertising on the interface.
connection — Displays connection information.
peer — Displays peer information.
adjacency — Displays hello adjacency information.
sockets
Syntax sockets
Description This command displays information for all sockets being used by the LDP protocol.
Default none
timers
Syntax timers
Description This command displays timer information for LDP.
Default none

Router Commands
mpls
Syntax mpls
Description This command enables the context to display MPLS information.
Default none
ftn
Syntax ftn
Context tools>dump>router>mpls
Description This command displays FEC-to-NHLFE (FTN) dump information for MPLS. (NHLFE is the acronym for
Next Hop Label Forwarding Entry.)
Default none
ilm
Syntax ilm
Description This command displays incoming label map (ILM) information for MPLS.
Default none
lspinfo
Syntax lspinfo [lsp-name] [detail]
Description This command displays label-switched path (LSP) information for MPLS.
Default none
Parameters lsp-name — Specifies the name that identifies the LSP. The LSP name can be up to 32 characters long and
must be unique.
detail — Displays detailed information about the LSP.
cspf

Tools
Syntax cspf to ip-addr [from ip-addr] [strict-srlg] [srlg-group grp-id...(up to 8 max)] [bandwidth
bandwidth] [include-bitmap bitmap] [exclude-bitmap bitmap] [hop-limit limit] [exclude-address
excl-addr [excl-addr...(upto 8 max)]] [use-te-metric] [exclude-node excl-node-id [excl-node-
id...(upto 8 max)]] [skip-interface interface-name]
Context tools>perform>router>mpls
Description This command computes a CSPF path with specified user constraints.
Default none
Parameters to ip-addr — Specify the destination IP address.

from ip-addr — Specify the originating IP address.
srlg-group grp-id — Specify the
bandwidth bandwidth — Specifies the amount of bandwidth in mega-bits per second (Mbps) to be
reserved.
include-bitmap bitmap — Specifies to include a bit-map that specifies a list of admin groups that should be
included during setup.
exclude-bitmap bitmap — Specifies to exclude a bit-map that specifies a list of admin groups that should
be included during setup.
hop-limit limit — Specifies the total number of hops a detour LSP can take before merging back onto the
main LSP path.
exclude-address ip-addr — Specifies an IP address to exclude from the operation.
use-te-metric — Specifies whether the TE metric would be used for the purpose of the LSP path
computation by CSPF.
skip-interface interface-name — Specifies a local interface name, instead of the interface address, to be
excluded from the CSPF computation.
force-switch-path
Syntax force-switch-path lsp lsp-name path path-name
no force-switch-path lsp lsp-name
Description
resignal
Syntax resignal lsp lsp-name path path-name delay minutes

Router Commands
resignal {p2mp-lsp p2mp-lsp-name p2mp-instance p2mp-instance-name | p2mp-delay p2mp-

minutes}
Description Use this command to resignal a specific LSP path.

Default none
Parameters lsp lsp-name — Specifies the name that identifies the LSP. The LSP name can be up to 32 characters
longand must be unique.
path path-name — Specifies the name for the LSP path up, to 32 characters in length.
delay minutes — Specifies the resignal delay in minutes.
Values 0 — 30
p2mp-lsp p2mp-lsp-name — Specifies an existing point-to-multipoint LSP name.
p2mp-instance p2mp-instance-name — Specifies a name that identifies the P2MP LSP instance
p2mp-delay p2mp-minutes — Specifies the delay time, in minutes.
Values 0 — 60
switch-path
Syntax switch-path lsp lsp-name path path-name
Description
trap-suppress
Syntax trap-suppress [number-of-traps] [time-interval]
Description This command modifies thresholds for trap suppression.
Default none
Parameters number-of-traps — Specify the number of traps in multiples of 100. An error messages is generated if an
invalid value is entered.
Values 100 to 1000
time-interval — Specify the timer interval in seconds.
Values 1 — 300

Tools
tp-tunnel
Syntax tp-tunnel
Description This command enables the context to perform Linear Protection operations on an MPLS-TP LSP.
clear
Syntax clear {lsp-name | id tunnel-id}
Context tools>perform>router>mpls>tp-tunnel
Description Clears all the MPLS-TP linear protection operational commands for the specified LSP that are currently
active.
Parameters lsp-name — Specifies the name of the MPLS-TP LSP.

Values up to 32 characters in text
id tunnel-id — Specifies the tunnel number of the MPLS-TP LSP
Values 1 — 61440
force
Syntax force {lsp-name | id tunnel-id}
Description Performs a force switchover of the MPLS-TP LSP from the active path to the protect path.

Values 1 — 61440
manual
Syntax manual {lsp-name | id tunnel-id}
Description Performs a manual switchover of the MPLS-TP LSP from the active path to the protect path.


Router Commands

Values 1 — 61440
lockout
Syntax lockout {lsp-name | id tunnel-id}
Description Performs a lockout of protection for an MPLS-TP LSP. This prevents a switchover to the protect path.

Values 1 — 61440
update-path
Syntax update-path lsp lsp-name path path-name new-path path-name
Description
memory-usage
Syntax memory-usage
Description This command displays memory usage information for MPLS.
Default none
te-lspinfo
Syntax te-lspinfo [endpoint ip-address] [sender ip-address] [lspid lsp-id] [detail]
te-lspinfo [endpoint ip-address] [sender ip-address] [lspid lsp-id] [detail]
Description This command displays TE LSP information for MPLS.

Default none

Tools
ospf
Syntax ospf [ospf-instance]
Description This command enables the context to display tools information for OSPF. 7210 supports only a single
instance of OSPF.
Default none
Parameters ospf-instance — OSPF instance.
Values 1 — 4294967295
abr
Syntax abr [detail]
Context tools>dump>router>ospf
Description This command displays area border router (ABR) information for OSPF.
Default none
Parameters detail — Displays detailed information about the ABR.
asbr
Syntax asbr [detail]
Description This command displays autonoumous system border router (ASBR) information for OSPF.
Default none
Parameters detail — Displays detailed information about the ASBR.
bad-packet
Syntax bad-packet [interface-name]
Description This command displays information about bad packets for OSPF.
Default none
Parameters interface-name — Display only the bad packets identified by this interface name.

Router Commands
leaked-routes
Syntax leaked-routes [summary | detail}
Description This command displays information about leaked routes for OSPF.
Default summary
Parameters summary — Display a summary of information about leaked routes for OSPF.
detail — Display detailed information about leaked routes for OSPF.
memory-usage
Syntax memory-usage [detail]
Description This command displays memory usage information for OSPF.
Default none
Parameters detail — Displays detailed information about memory usage for OSPF.
request-list
Syntax request-list [neighbor ip-address] [detail]
request-list virtual-neighbor ip-address area-id area-id [detail]
Description This command displays request list information for OSPF.
Default none
Parameters neighbor ip-address — Display neighbor information only for neighbor identified by the IP address.
detail — Displays detailed information about the neighbor.
virtual-neighbor ip-address — Displays information about the virtual neighbor identified by the IP
address.
area-id area-id — The OSPF area ID expressed in dotted decimal notation or as a 32-bit decimal integer.

Tools
retransmission-list
Syntax retransmission-list [neighbor ip-address] [detail]
retransmission-list virtual-neighbor ip-address area-id area-id [detail]
Description This command displays dump retransmission list information for OSPF.
Default none
Parameters neighbor ip-address — Display neighbor information only for neighbor identified by the IP address.
detail — Displays detailed information about the neighbor.
virtual-neighbor ip-address — Displays information about the virtual neighbor identified by the IP
address.
area-id area-id — The OSPF area ID expressed in dotted decimal notation or as a 32-bit decimal integer.
route-summary
Syntax route-summary
Description This command displays dump route summary information for OSPF.
Default none
route-table
Syntax route-table ip-prefix/mask [type] [detail]
Description This command displays dump information about routes learned through OSPF.
Default none
Parameters ip-prefix/mask — Specifies the IP prefix and host bits.
type — Specify the type of route table to display information.

Values intra-area, inter-area, external-1, external-2, nssa-1, nssa-2
detail — Displays detailed information about learned routes.

Router Commands
ospf3
Syntax ospf3
Description This command enables the context to display tools information for OSPF3.
Default none
refresh-lsas
Syntax refresh-lsas [lsa-type] [area-id]
Context tools>perform>router>ospf
tools>perform>router>ospf3
Description This command refreshes LSAs for OSPF.
Default none
Parameters lsa-type — Specify the LSA type using allow keywords.

Values router, network, summary, asbr, extern, nssa, opaque
area-id — The OSPF area ID expressed in dotted decimal notation or as a 32-bit decimal integer.
Values 0 — 4294967295
run-manual-spf
Syntax run-manual-spf externals-only
Context tools>perform>router>ospf
tools>perform>router>ospf3
Description This command runs the Shortest Path First (SPF) algorithm.
Default none
Parameters externals-only — Specify the route preference for OSPF external routes.
rsvp
Syntax rsvp
Description This command enables the context to display RSVP information.

Tools
Default none
psb
Syntax psb [endpoint endpoint-address] [sender sender-address] [tunnelid tunnel-id] [lspid lsp-id]
Context tools>dump>router>rsvp
Description This command displays path state block (PSB) information for RSVP.
When a PATH message arrives at an LSR, the LSR stores the label request in the local PSB for the LSP. If a
label range is specified, the label allocation process must assign a label from that range.
The PSB contains the IP address of the previous hop, the session, the sender, and the TSPEC. This informa-
tion is used to route the corresponding RESV message back to LSR 1.
Default none
Parameters endpoint endpoint-address — Specifies the IP address of the last hop.

sender sender-address — Specifies the IP address of the sender.
tunnelid tunnel-id — Specifies the SDP ID.
Values 0 — 4294967295
lspid lsp-id — Specifies the label switched path that is signaled for this entry.
Values 1 — 65535
rsb
Syntax rsb [endpoint endpoint-address] [sender sender-address] [tunnelid tunnel-id] [lspid lsp-id]
Description This command displays RSVP Reservation State Block (RSB) information.
Default none
Parameters endpoint endpoint-address — Specifies the IP address of the last hop.

sender sender-address — Specifies the IP address of the sender.
tunnelid tunnel-id — Specifies the SDP ID.
Values 0 — 4294967295
Values 1 — 65535

Router Commands
tcsb
Syntax tcsb [endpoint endpoint-address] [sender sender-address] [tunnelid tunnel-id] [lspid lsp-id]
Description This command displays RSVP traffic control state block (TCSB) information.
Default none
Parameters endpoint endpoint-address — Specifies the IP address of the egress node for the tunnel supporting this
session.
sender sender-address — Specifies the IP address of the sender node for the tunnel supporting this session.
It is derived from the source address of the associated MPLS LSP definition.
tunnelid tunnel-id — Specifies the IP address of the ingress node of the tunnel supporting this RSVP
session.
Values 0 — 4294967295
Values 1 — 65535
static-route
Syntax static-route ldp-sync-status
Description This command displays the sync status of LDP interfaces that static-route keeps track of.

Tools
Performance Tools
perform
Syntax perform
Context tools
Description This command enables the context to enable tools to perform specific tasks.
Default none
cron
Syntax cron
Description This command enables the context to perform CRON (scheduling) control operations.
Default none
action
Syntax action
Context tools>perform>cron
Description This command enables the context to stop the execution of a script started by CRON action. See the stop
command.
stop
Syntax stop [action-name] [owner action-owner] [all]
Context tools>perform>cron>action
Description This command stops execution of a script started by CRON action.
Parameters action-name — Specifies the action name.

Values Maximum 32 characters.
owner action-owner — Specifies the owner name.
Default TiMOS CLI
all — Specifies to stop all CRON scripts.

Performance Tools
tod
Syntax tod
Context tools>perform>cron
Description This command enables the context for tools for controlling time-of-day actions.
Default none
re-evaluate
Syntax re-evaluate
Context tools>perform>cron>tod
Description This command enables the context to re-evaluate the time-of-day state.
Default none
customer
Syntax customer customer-id [site customer-site-name]
Context tools>perform>cron>tod>re-eval
Description This command re-evaluates the time-of-day state of a multi-service site.

Parameters customer-id — Specify an existing customer ID.
Values 1 — 2147483647
site customer-site-name — Specify an existing customer site name.
filter
Syntax filter ip-filter [filter-id]
filter ipv6-filter [filter-id]
filter mac-filter [filter-id]
Description This command re-evaluates the time-of-day state of a filter entry.
Parameters filter-type — Specify the filter type.

Values ip-filter, mac-filter
filter-id — Specify an existing filter ID.
Values 1 — 65535

Tools
service
Syntax service id service-id [sap sap-id]
Description This command re-evaluates the time-of-day state of a SAP.
Parameters r service-id — Specify the an existing service ID.

Values 1 — 2147483647
sap sap-id — Specifies the physical port identifier portion of the SAP definition. See Common CLI Com-
mand Descriptions on page 333 for CLI command syntax.
tod-suite
Syntax tod-suite tod-suite-name
Description This command re-evaluates the time-of-day state for the objects referring to a tod-suite.
Parameters tod-suite-name — Specify an existing TOD nfame.
ldp-sync-exit
Syntax [no] ldp-sync-exit
Context tools>perform>router>isis
tools>perform>router>ospf
Description This command restores the actual cost of an interface at any time. When this command is executed, IGP
immediately advertises the actual value of the link cost for all interfaces which have the IGP-LDP synchro-
nization enabled if the currently advertised cost is different.
run-manual-spf
Syntax run-manual-spf
Description This command runs the Shortest Path First (SPF) algorithm or OSPF or ISIS.

Performance Tools
isis
Note : This command is not supported on 7210 SAS-M and 7210 SAS-T devices configured in Access
uplink mode
Syntax isis
Context tools>perform>router
Description This command enables the context to configure tools to perform certain ISIS tasks.
mpls
uplink mode
Syntax mpls
Description This command enables the context to perform specific MPLS tasks.
Default none
cspf
Syntax cspf to ip-addr [from ip-addr] [bandwidth bandwidth] [include-bitmap bitmap] [exclude-bitmap
bitmap] [hop-limit limit] [exclude-address excl-addr [excl-addr...(up to 8 max)]] [use-te-metric]
[skip-interface interface-name] [ds-class-type class-type] [cspf-reqtype req-type]
Description This command computes a CSPF path with specified user constraints.
Default none
Parameters to ip-addr — Specify the destination IP address.

from ip-addr — Specify the originating IP address.
bandwidth bandwidth — Specifies the amount of bandwidth in mega-bits per second (Mbps) to be
reserved.
Values 1 - 100000 in Mbps
include-bitmap bitmap — Specifies to include a bit-map that specifies a list of admin groups that should be
included during setup.
Values 0 - 4294967295 - accepted in decimal, hex(0x) or binary(0b)
exclude-bitmap bitmap — Specifies to exclude a bit-map that specifies a list of admin groups that should
be included during setup.
Values 0 - 4294967295 - accepted in decimal, hex(0x) or binary(0b)

Tools
hop-limit limit — Specifies the total number of hops a detour LSP can take before merging back onto the
main LSP path.
Values 1- 255
exclude-address ip-addr — Specifies an IP address to exclude from the operation.
use-te-metric — Specifies whether the TE metric would be used for the purpose of the LSP path
computation by CSPF.
skip-interface interface-name — Specifies a local interface name, instead of the interface address, to be
excluded from the CSPF computation.
resignal
Syntax resignal lsp lsp-name path path-name delay minutes
Description Use this command to resignal a specific LSP path.

Default none
Parameters lsp lsp-name — Specifies the name that identifies the LSP. The LSP name can be up to 32 characters
longand must be unique.
path path-name — Specifies the name for the LSP path up, to 32 characters in length.
delay minutes — Specifies the resignal delay in minutes.
Values 0 — 30
trap-suppress
Syntax trap-suppress [number-of-traps] [time-interval]
Description This command modifies thresholds for trap suppression.
Default none
Parameters number-of-traps — Specify the number of traps in multiples of 100. An error messages is generated if an
invalid value is entered.
Values 100 to 1000
time-interval — Specify the timer interval in seconds.
Values 1 — 300

Performance Tools
ospf
uplink mode
Syntax ospf
Description This command enables the context to perform specific OSPF tasks.
Default none
ldp-sync-exit
Syntax [no] ldp-sync-exit
Description This command restores the actual cost of an interface at any time. When this command is executed, IGP
immediately advertises the actual value of the link cost for all interfaces which have the IGP-LDP synchro-
nization enabled if the currently advertised cost is different.
service
Syntax services
Description This command enables the context to configure tools for services.
id
Syntax id service-id
Context tools>perform>service
Description This command enables the context to configure tools for a specific service.
Parameters service-id — Specify an existing service ID.
Values 1 — 2147483647

Tools
endpoint
Syntax endpoint endpoint-name
Context tools>perform>service>id
Description This command enables the context to configure tools for a specific VLL service endpoint.
Parameters endpoint-name — Specify an existing VLL service endpoint name.
force-switchover
Syntax force-switchover sdp-id:vc-id
no force-switchover
Context tools>perform>service>id
Description This command forces a switch of the active spoke SDP for the specified service.
Parameters sdp-id:vc-id — Specify an existing spoke SDP for the service.
Sample Output
A:Dut-B# tools perform service id 1 endpoint mcep-t1 force-switchover 221:1

*A:Dut-B# show service id 1 endpoint
===============================================================================
Service 1 endpoints
===============================================================================
Endpoint name : mcep-t1
Revert time : 0
Act Hold Delay : 0
Ignore Standby Signaling : false
Suppress Standby Signaling : false
Block On Mesh Fail : true
Multi-Chassis Endpoint : 1
MC Endpoint Peer Addr : 3.1.1.3
Psv Mode Active : No
Tx Active : 221:1(forced)
Tx Active Up Time : 0d 00:00:17
Revert Time Count Down : N/A
Tx Active Change Count : 6
Last Tx Active Change : 02/14/2009 00:17:32
-------------------------------------------------------------------------------
Members
-------------------------------------------------------------------------------
Spoke-sdp: 221:1 Prec:1 Oper Status: Up
Spoke-sdp: 231:1 Prec:2 Oper Status: Up
================================================================================
*A:Dut-B#

Performance Tools

Common CLI Command
Descriptions
In This Chapter
This chapter provides CLI syntax and command descriptions for SAP and port commands.
• SAP Syntax on page 334

• Port Syntax on page 202

Common Service Commands
Common Service Commands

SAP Syntax
sap
Syntax [no] sap sap-id
Description This command specifies the physical port identifier portion of the SAP definition.
Parameters sap-id — Specifies the physical port identifier portion of the SAP definition.
The sap-id can be configured in one of the following formats:
Type Syntax Example
port-id slot/mda/port[.channel] 1/1/5
null [port-id | lag-id ] port-id: 1/1/3

lag-id: lag-3
dot1q [port-id | lag-id]:qtag1 port-id:qtag1: 1/1/3:100

lag-id:qtag1:lag-3:102
qinq [port-id | lag-id]:qtag1.qtag2 port-id:qtag1.qtag2: 1/1/3:100.10

lag-id:qtag1.qtag2: lag-10:
port
Syntax port port-id
Description This command specifies a port identifier.
Parameters port-id — The port-id can be configured in one of the following formats.
Values port-id slot/mda/port[.channel]
lag-id lag-id
lag keyword
id 1— 200
Page 334 7210 SAS-M, T, X, and R6 OS OAM and Diagnostic

Guide
Standards and Protocol Support
NOTE: The capabilities available when operating in access-uplink mode/L2 mode and
network mode/MPLS mode are different. Correspondingly, not all the standards and protocols
listed below are applicable to access-uplink mode and network mode.
Standards Compliance RFC 2439 BGP Route Flap Dampening RFC 3046 DHCP Relay Agent
IEEE 802.1ab-REV/D3 Station and RFC 2547bis BGP/MPLS VPNs Information Option (Option 82)
Media Access Control Connectivity draft-ietf-idr-rfc2858bis-09.txt.
Discovery RFC 2918 Route Refresh Capability for DIFFERENTIATED SERVICES
IEEE 802.1D Bridging BGP-4 RFC 2474 Definition of the DS Field the
RFC 3107 Carrying Label Information in IPv4 and IPv6 Headers (Rev)
IEEE 802.1p/Q VLAN Tagging
BGP-4 RFC 2597 Assured Forwarding PHB
IEEE 802.1s Multiple Spanning Tree
RFC 3392 Capabilities Advertisement Group (rev3260)
IEEE 802.1w Rapid Spanning Tree
with BGP-4 RFC 2598 An Expedited Forwarding
Protocol
RFC 4271 BGP-4 (previously RFC 1771) PHB
IEEE 802.1X Port Based Network
RFC 4360 BGP Extended Communities RFC 2697 A Single Rate Three Color
Access Control
Attribute Marker
IEEE 802.1ad Provider Bridges
RFC 4364 BGP/MPLS IP Virtual Private RFC 2698 A Two Rate Three Color
IEEE 802.1ah Provider Backbone
Networks (VPNs) (previously RFC Marker
Bridges (Not Available on 7210
2547bis BGP/MPLS VPNs) RFC 4115 A Differentiated Service Two-
SAS-R6)
RFC 4760 Multi-protocol Extensions for Rate, Three-Color Marker with
IEEE 802.1ag Service Layer OAM
BGP Efficient Handling of in-Profile
IEEE 802.3ah Ethernet in the First Mile Traffic
RFC 4893 BGP Support for Four-octet
IEEE 802.3 10BaseT
AS Number Space
IEEE 802.3ad Link Aggregation IPv6 (7210 SAS-M and 7210 SAS-X
RFC 5291 Outbound Route Filtering
IEEE 802.3ae 10Gbps Ethernet only)
RFC 5668 4-Octet AS Specific BGP
IEEE 802.3u 100BaseTX RFC 2460 Internet Protocol, Version 6
Extended Community Capability
IEEE 802.3z 1000BaseSX/LX (IPv6) Specification
for BGP-4
ITU-T Y.1731 OAM functions and RFC 2461 Neighbor Discovery for IPv6
mechanisms for Ethernet based RFC 2462 IPv6 Stateless Address Auto
CIRCUIT EMULATION (7210 SAS-M
networks configuration
Only)
draft-ietf-disman-alarm-mib-04.txt RFC 2463 Internet Control Message
RFC 4553 Structure-Agnostic Time
IANA-IFType-MIB Protocol (ICMPv6) for the Internet
Division Multiplexing (TDM) over
IEEE8023-LAG-MIB Packet (SAToP) Protocol Version 6 Specification
ITU-T G.8032 Ethernet Ring Protection RFC 5086 Structure-Aware Time RFC 2464 Transmission of IPv6 Packets
Switching (version 2) Division Multiplexed (TDM) Circuit over Ethernet Networks
Emulation Service over Packet RFC 2740 OSPF for IPv6
Protocol Support Switched Network (CESoPSN) RFC 3587 IPv6 Global Unicast Address
RFC 5287 Control Protocol Extensions Format
BGP for the Setup of Time-Division RFC 4007 IPv6 Scoped Address
RFC 1397 BGP Default Route Multiplexing (TDM) Pseudowires in Architecture
Advertisement MPLS Networks RFC 4193 Unique Local IPv6 Unicast
RFC 1772 Application of BGP in the Addresses
Internet DHCP RFC 4291 IPv6 Addressing Architecture
RFC 1997 BGP Communities Attribute RFC 2131 Dynamic Host Configuration RFC 4552 Authentication/Confidentiality
RFC 2385 Protection of BGP Sessions Protocol for OSPFv3
via MD5
Standards and Protocols Page 335

Standards and Protocols
RFC 5095 Deprecation of Type 0 Routing MPLS - RSVP-TE RFC 4601 Protocol Independent
Headers in IPv6 RFC 2430 A Provider Architecture Multicast - Sparse Mode (PIM-SM):
draft-ietf-isis-ipv6-05 DiffServ & TE Protocol Specification (Revised)
draft-ietf-isis-wg-multi-topology-xx.txt RFC 2702 Requirements for Traffic RFC 4604 Using IGMPv3 and MLDv2
Engineering over MPLS for Source-Specific Multicast
IS-IS RFC2747 RSVP Cryptographic RFC 4607 Source-Specific Multicast for
RFC 1142 OSI IS-IS Intra-domain Authentication IP
Routing Protocol (ISO 10589) RFC3097 RSVP Cryptographic RFC 4608 Source-Specific Protocol
RFC 1195 Use of OSI IS-IS for routing in Authentication Independent Multicast in 232/8
TCP/IP & dual environments RFC 3209 Extensions to RSVP for draft-ietf-pim-sm-bsr-06.txt
RFC 2763 Dynamic Hostname Exchange Tunnels
for IS-IS RFC 4090 Fast reroute Extensions to NETWORK MANAGEMENT
RFC 2966 Domain-wide Prefix RSVP-TE for LSP Tunnels ITU-T X.721: Information technology-
Distribution with Two-Level IS-IS RFC 5817 Graceful Shutdown in MPLS OSI-Structure of Management
RFC 2973 IS-IS Mesh Groups and GMPLS Traffic Engineering Information
RFC 3373 Three-Way Handshake for Networks ITU-T X.734: Information technology-
Intermediate System to Intermediate OSI-Systems Management: Event
System (IS-IS) Point-to-Point MPLS-TP (Transport Profile) [ 7210 Report Management Function
Adjacencies SAS-T and 7210 SAS-R6 in M.3100/3120 Equipment and Connection
RFC 3567 Intermediate System to network mode only] Models
Intermediate System (ISIS) RFC 5586 MPLS Generic Associated TMF 509/613 Network Connectivity
Cryptographic Authentication Channel Model
RFC 3719 Recommendations for RFC 5921 A Framework for MPLS in RFC 1157 SNMPv1
Interoperable Networks using IS-IS Transport Networks RFC 1215 A Convention for Defining
RFC 3784 Intermediate System to RFC 5960 MPLS Transport Profile Data Traps for use with the SNMP
Intermediate System (IS-IS) Plane Architecture RFC 1907 SNMPv2-MIB
Extensions for Traffic Engineering RFC 6370 MPLS-TP Identifiers RFC 2011 IP-MIB
(TE) RFC 6378 MPLS-TP Linear Protection RFC 2012 TCP-MIB
RFC 3787 Recommendations for RFC 6428 Proactive Connectivity RFC 2013 UDP-MIB
Interoperable IP Networks Verification, Continuity Check and RFC 2096 IP-FORWARD-MIB
RFC 3847 Restart Signaling for IS-IS – Remote Defect indication for MPLS RFC 2138 RADIUS
GR helper Transport Profile RFC 2206 RSVP-MIB
RFC 4205 for Shared Risk Link Group RFC 6426 MPLS On-Demand RFC 2571 SNMP-FRAMEWORKMIB
(SRLG) TLV Connectivity and Route Tracing
RFC 2572 SNMP-MPD-MIB
RFC 6478 Pseudowire Status for Static
RFC 2573 SNMP-TARGET-&-
MPLS - General Pseudowires
NOTIFICATION-MIB
RFC 3031 MPLS Architecture draft-ietf-mpls-tp-ethernet-addressing-02
RFC 2574 SNMP-USER-
RFC 3032 MPLS Label Stack Encoding MPLS-TP Next-Hop Ethernet
BASEDSMMIB
RFC 4379 Detecting Multi-Protocol Addressing
RFC 2575 SNMP-VIEW-BASEDACM-
Label Switched (MPLS) Data Plane MIB
Failures Multicast
RFC 2576 SNMP-COMMUNITY-MIB
RFC 4182 Removing a Restriction on the RFC 1112 Host Extensions for IP
RFC 2665 EtherLike-MIB
use of MPLS Explicit NULL Multicasting (Snooping)
RFC 2819 RMON-MIB
RFC 2236 Internet Group Management
RFC 2863 IF-MIB
MPLS - LDP Protocol, (Snooping)
RFC 2864 INVERTED-STACK-MIB
RFC 5036 LDP Specification RFC 3376 Internet Group Management
RFC 3014 NOTIFICATION-LOGMIB
RFC 3037 LDP Applicability Protocol, Version 3 (Snooping) [ Only in
7210 SAS-M and 7210 SAS-T RFC 3164 Syslog
RFC 3478 Graceful Restart Mechanism
access-uplink mode and supported RFC 3273 HCRMON-MI
for LDP — GR helper
with IPv4 Multicast in network RFC 3411 An Architecture for
RFC 5283 LDP extension for Inter-Area
mode ] Describing Simple Network
LSP
RFC 2362 Protocol Independent Management Protocol (SNMP)
RFC 5443 LDP IGP Synchronization Management Frameworks
Multicast Sparse Mode (PIMSM)
Page 336 Standards and Protocols

RFC 3412 - Message Processing and RFC 5085, Pseudowire Virtual Circuit RFC 2347 TFTP option Extension
Dispatching for the Simple Network Connectivity Verification RFC 2328 TFTP Blocksize Option
Management Protocol (SNMP) (VCCV): A Control Channel for RFC 2349 TFTP Timeout Interval and
RFC 3413 - Simple Network Pseudowires Transfer Size option
Management Protocol (SNMP) RFC 5659 An Architecture for Multi- draft-ietf-bfd-mib-00.txt Bidirectional
Applications Segment Pseudowire Emulation Forwarding Detection Management
RFC 3414 - User-based Security Model Edge-to-Edge Information Base
(USM) for version 3 of the Simple RFC6073, Segmented Pseudowire (draft- RFC 5880 Bidirectional Forwarding
Network Management Protocol ietf-pwe3-segmented-pw-18.txt) Detection
(SNMPv3) draft-ietf-l2vpn-vpws-iw-oam-02.txt, RFC 5881 BFD IPv4 (Single Hop)
RFC 3418 - SNMP MIB OAM Procedures for VPWS RFC 5883 BFD for Multihop Paths (7210
draft-ietf-mpls-lsr-mib-06.txt Interworking SAS-M only)
draft-ietf-mpls-te-mib-04.txt draft-ietf-pwe3-oam-msg-map-14-txt,
draft-ietf-mpls-ldp-mib-07.txt Pseudowire (PW) OAM Message Timing
Mapping
ITU-T G.781 Telecommunication
OSPF draft-muley-dutta-pwe3-redundancy-bit- Standardization Section of ITU,
RFC 1765 OSPF Database Overflow 03.txt, Pseudowire Preferential Synchronization layer functions,
Forwarding Status bit definition issued 09/2008
RFC 2328 OSPF Version 2
draft-pwe3-redundancy-02.txt, ITU-T G.813 Telecommunication
RFC 2370 Opaque LSA Support
Pseudowire (PW) Redundancy Standardization Section of ITU,
RFC 3101 OSPF NSSA Option
RFC 3137 OSPF Stub Router Timing characteristics of SDH
RADIUS equipment slave clocks (SEC),
Advertisement
RFC 2865 Remote Authentication Dial In issued 03/2003.
RFC 3623 Graceful OSPF Restart – GR
User Service GR-1244-CORE Clocks for the
helper
RFC 2866 RADIUS Accounting Synchronized Network: Common
RFC 3630 Traffic Engineering (TE)
Extensions to OSPF Version 2 Generic Criteria, Issue 3,May 2005
RFC 2740 OSPF for IPv6 (OSPFv3) SSH ITU-T G.8261 Telecommunication
draft-ietf-ospf-ospfv3-update-14.txt draft-ietf-secsh-architecture.txt SSH Standardization Section of ITU,
Protocol Architecture Timing and synchronization aspects
RFC 4203 Shared Risk Link Group
draft-ietf-secsh-userauth.txt SSH in packet networks, issued 04/2008.
(SRLG) sub-TLV
Authentication Protocol (Not available on 7210 SAS-R6)
RFC 4577 OSPF as the Provider/
draft-ietf-secsh-transport.txt SSH ITU-T G.8262 Telecommunication
Customer Edge Protocol for BGP/
Transport Layer Protocol Standardization Section of ITU,
MPLS IP Virtual Private Networks
draft-ietf-secsh-connection.txt SSH Timing characteristics of
(VPNs)
Connection Protocol synchronous Ethernet equipment
draft-ietf-secsh- newmodes.txt SSH slave clock (EEC), issued 08/2007.
PSEUDO-WIRE
Transport Layer Encryption Modes ITU-T G.8264 Telecommunication
RFC 3985 Pseudo Wire Emulation Edge- Standardization Section of ITU,
to-Edge (PWE3) Distribution of timing information
RFC 4385 Pseudo Wire Emulation Edge- TACACS+
through packet networks, issued 10/
to-Edge (PWE3) Control Word for draft-grant-tacacs-02.txt
2008.
Use over an MPLS PSN IEEE Std 1588™-2008, IEEE Standard
RFC 3916 Requirements for Pseudo- TCP/IP for a Precision Clock
Wire Emulation Edge-to-Edge RFC 768 UDP Synchronization Protocol for
(PWE3) RFC 1350 The TFTP Protocol Networked Measurement and
RFC 4448 Encapsulation Methods for RFC 791 IP Control Systems. (Not available on
Transport of Ethernet over MPLS RFC 792 ICMP 7210 SAS-R6)
Networks (draft-ietf-pwe3-ethernet- RFC 793 TCP
encap-11.txt) RFC 826 ARP VPLS
RFC 4446 IANA Allocations for PWE3 RFC 854 Telnet RFC 4762 Virtual Private LAN Services
RFC 4447 Pseudowire Setup and RFC 1519 CIDR Using LDP (previously draft-ietf-
Maintenance Using LDP (draft-ietf- l2vpn-vpls-ldp-08.txt)
RFC 1812 Requirements for IPv4
pwe3-control-protocol-17.txt)
Routers

VRRP TIMETRA-MPLS-MIB.mib
RFC 2787 Definitions of Managed TIMETRA-RSVP-MIB.mib
Objects for the Virtual Router TIMETRA-LDP-MIB.mib
Redundancy Protocol TIMETRA-VRRP-MIB.mib
RFC 3768 Virtual Router Redundancy TIMETRA-VRTR-MIB.mib
Protocol
Proprietary MIBs
ALCATEL-IGMP-SNOOPING-
MIB.mib
TIMETRA-CAPABILITY-7210-SAS-M-
V5v0.mib (7210 SAS-M Only)
TIMETRA-CAPABILITY-7210-SAS-X-
V5v0.mib (7210 SAS-X Only)
TIMETRA-CHASSIS-MIB.mib
TIMETRA-CLEAR-MIB.mib
TIMETRA-DOT3-OAM-MIB.mib
TIMETRA-FILTER-MIB.mib
TIMETRA-GLOBAL-MIB.mib
TIMETRA-IEEE8021-CFM-MIB.mib
TIMETRA-LAG-MIB.mib
TIMETRA-LOG-MIB.mib
TIMETRA-MIRROR-MIB.mib
TIMETRA-NTP-MIB.mib
TIMETRA-OAM-TEST-MIB.mib
TIMETRA-PORT-MIB.mib
TIMETRA-QOS-MIB.mib
TIMETRA-SAS-ALARM-INPUT-
MIB.mib
TIMETRA-SAS-FILTER-MIB.mib
TIMETRA-SAS-IEEE8021-CFM-
MIB.mib
TIMETRA-SAS-IEEE8021-PAE-
MIB.mib
TIMETRA-SAS-GLOBAL-MIB.mib
TIMETRA-SAS-LOG-MIB.mib.mib
TIMETRA-SAS-MIRROR-MIB.mib
TIMETRA-SAS-MPOINT-MGMT-
MIB.mib (Only for 7210 SAS-X)
TIMETRA-SAS-PORT-MIB.mib
TIMETRA-SAS-QOS-MIB.mib
TIMETRA-SAS-SDP-MIB.mib
TIMETRA-SAS-SYSTEM-MIB.mib
TIMETRA-SAS-SERV-MIB.mib
TIMETRA-SAS-VRTR-MIB.mib
TIMETRA-SCHEDULER-MIB.mib
TIMETRA-SECURITY-MIB.mib
TIMETRA-SERV-MIB.mib
TIMETRA-SYSTEM-MIB.mib
TIMETRA-TC-MIB.mib
TIMETRA-ISIS-MIB.mib
TIMETRA-ROUTE-POLICY-MIB.mib



Index
C VCCV 78
continuity check 117
CPE ping 76 S
SAA test parameters 137
E SDP diagnostics 72
Ethernet CFM 103 SDP ping 72
service assurance agent 136, 139
L service diagnostics 73
linktrace 115
loopback 114 T
LSP diagnostics 71 Tools 293
M V
MAC ping 74 VCCV ping 78
MAC populate 77 VLL diagnostics 78
MAC purge 77 VPLS MAC diagnostics 74
MAC trace 75
Mirror
overview 14
implementation 15
source and destination 16
configuring
basic 27
classification rules 28
IP filter 29
MAC filter 29
port 28
SAP 28
command reference 43
local mirror service 31
management tasks 37
overview 26
remote mirror service 33
O
OAM 70
overview 70
configuring
command reference 153
P
ping


3he09527aaaa - v1 - 7210 Sas M, T, X, r6 Oam A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3he09527aaaa - v1 - 7210 Sas M, T, X, r6 Oam A

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent

Service Access Switch| Release 7.0 Rev.01

Copyright 2013 Alcatel-Lucent. All rights reserved.

OAM and SAA

7210 SAS-M, T, X, R6 OS OAM and Diagnostic Guide Page 3

Automated VCCV-Trace Capability for MS-Pseudowire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Common CLI Command Descriptions

Standards and Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335

Page 4 7210 SAS-M, T, X, R6 OS OAM and Diagnostic

OAM and SAA

Common CLI Command Descriptions

7210 SAS-M, T, X, R6 OS OAM and Diagnostic Guide Page 5

OAM and SAA

Common CLI Command Descriptions

Page 6 7210 SAS-M, T, X, R6 OS OAM and Diagnostic

About This Guide

7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide Page 7

Page 8 7210 SAS-M, T, X, and R6 OS OAM and Diag-

List of Technical Publications

• 7210-SAS-M, T, X, R6 OS Basic System Configuration Guide

7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide Page 9

Page 10 7210 SAS-M, T, X, and R6 OS OAM and Diag-

Alcatel-Lucent 7210 SAS-Series Services Configuration Process

Table 1: Configuration Process

Diagnostics/ Mirroring Mirror Services on page 13

7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide Page 11

Page 12 7210 SAS-M, T, X, and R6 OS OAM and Diag-

Topics in this chapter include:

• Service Mirroring on page 14

7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide Page 13

Customer Traffic Customer Traffic

IP/MPLS Core Sniffer

Figure 1: Service Mirroring

Page 14 7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide

Alcatel-Lucent’s implementation of packet mirroring is based on the following assumptions:

7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide Page 15

Mirror Source and Destinations

Page 16 7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide

Local Port Ingress NULL SAP

7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide Page 17

Local and Remote Mirroring

Page 18 7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide

• Port (ingress and egress)

7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide Page 19

• Mirror source — The traffic on a specific point(s) to mirror.

Figure 2 depicts a local mirror service configured on ALA-A.

1/1/1 1/1/2 1/1/3

Configure a mirror service specifying

Figure 2: Local Mirroring Example

Page 20 7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide

Mirror Destination Mirror Source

Configure a mirror service specifying

Figure 3: Remote Mirroring Example

7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide Page 21

Configuration Process Overview

CONFIGURE MIRROR DESTINATION MIRROR DESTINATION

CONFIGURE MIRROR SOURCE MIRROR SOURCE

Figure 4: Mirror Configuration and Implementation Flow

Page 22 7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide

7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide Page 23

Page 24 7210 SAS-M, T, X, and R6 OS OAM and Diagnostic Guide

Configuring Service Mirroring with CLI

Topics in this section include: