GT v7 0 X Performance Element User Manual

GT Performance Element
UserManual
Firmware Release 7.0
Published
March 31, 2015

Document Revision Number: 1
Released on March 31, 2015.
Accedian, Accedian Networks, the Accedian Networks logo, R-FLO, SkyLIGHT, antMODULE, moduleDOCK, Vision
EMS, Vision Suite, VisionMETRIX, V-NID, Plug & Go, Network State+, Traffic-Meter and FlowMETER are
trademarks or registered trademarks of Accedian Networks Inc.
All other company and product names may be trademarks of their respective companies. Accedian Networks
may, from time to time, make changes to the products or specifications contained herein without notice. Some
certifications may be pending final approval; please contact Accedian Networks for current certifications.
Accedians products are protected by patents as indicated on Accedians website at

http://www.accedian.com/en/legal.html
The mention of any product does not constitute an endorsement by Accedian Networks Inc.
The content of this publication is provided for informational use only, is subject to change without notice and
should not be construed as a commitment by Accedian Networks Inc. Accedian Networks Inc. assumes no
responsibility or liability for any errors or inaccuracies that may appear in this document.
Except as permitted by such lease agreement, no part of this publication may be reproduced, stored in any
retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise,
without the prior written consent of Accedian Networks Inc.
Changes are periodically made to the information herein; these changes will be incorporated into new editions
of this publication. Accedian Networks Inc. may make improvements and/or changes in the products and/or
software programs described in this publication at any time.
If you have comments regarding this manual or the products it describes, address them to:
Accedian Networks Inc.

Attention: Technical Publications
2351 Alfred-Nobel Boulevard, Suite N-410
Saint-Laurent, Qubec
Canada H4S 2A9
Tel: 514-331-6181
Fax: 514-331-2210
Toll free: 1-866-685-8181
support@accedian.com
accedian.com
Accedian Networks Inc. may use or distribute whatever information you provide in any way it believes
appropriate without incurring any obligation to you.
Copyright 2005-2015 Accedian Networks Inc. All rights reserved, including those to reproduce this publication
or parts thereof in any form without permission in writing from Accedian Networks Inc.
GT Performance Element User Manual Firmware Release 7.0
Contents
1 About This Manual 1

1.1 Organization 2
1.2 Conventions 3
1.3 References 4
2 Introduction to the GT Performance Element 5

2.1 Applications 6
2.1.1 Mobile Backhaul 7
2.1.2 Assured Business Services 8
2.1.3 Carrier Ethernet Exchange Services 9
2.1.4 Carrier Ethernet Global Interconnect 10
2.1.5 Enterprise WAN QoS 11
2.1.6 Ethernet Service Creation 12
2.2 Features 13
2.2.1 Service Assurance 13
2.2.2 Service Creation 17
3 Managing the Unit 21

3.1 About the Management Web Interface 22
3.2 Starting the Management Web Interface 24
3.2.1 Physically Connecting to the Unit 24
3.2.2 Logging In 24
3.2.3 Working in the Home Page 25
3.2.4 Modifying the Unit Identifier 26
3.2.5 Managing SSL Certificates 28
3.3 Configuring the Logical Interfaces 31
3.3.1 Adding or Editing a Logical Interface 34
3.3.2 Setting Up a Beacon Instance at Layer 3 40
3.3.3 Adding or Editing an IPv4 Route 40
3.3.4 Adding or Editing an IPv6 Route 41
3.4 Finding a Host (Ping and Traceroute) 43
3.5 Using the Serial Console 44
3.6 Managing the Link Layer Discovery Protocol (LLDP) 46
3.7 Managing Sessions 49
3.7.1 Terminating a User Session 50
3.7.2 Locking or Unlocking User Sessions 50
3.7.3 Configuring Session Options 51
3.8 Managing Users and Privileges 54
3.8.1 Setting Up the Administrator Account 54
Document revision 1|March 2015 v

Firmware Release 7.0 GT Performance Element User Manual
3.8.2 Defining Permissions for a Group of Users 54

3.8.3 Adding or Editing User Accounts 58
3.8.4 Administering User Account Privileges 58
3.8.5 Changing Passwords 59
3.9 Using a RADIUS Server for Authentication 60
3.9.1 RADIUS Server Configuration Examples 61
3.10 Using a TACACS+ Server for Authentication 62
3.10.1 TACACS+ Server Configuration Examples 63
3.11 Managing Access Control Lists 65
3.11.1 Setting Up an ACL 66
3.11.2 Deleting an ACL 67
3.11.3 Viewing ACL Statistics 68
4 Configuring Plug & Go 69

4.1 Understanding Plug & Go 70
4.1.1 Beacon and Advertisement Frames 70
4.1.2 ACP Level 71
4.2 Configuring a Unit for Beacon 72
4.2.1 Setting Up a Beacon Instance at Layer2 72
4.2.2 Setting Up a Beacon Instance at Layer3 73
4.2.3 Deleting a Beacon Instance at Layer3 76
4.2.4 Modifying a Beacon Instance at Layer3 76
4.3 Configuring the Forwarding Settings of Intermediate Units 77
4.4 Managing Network Inventory 78
4.4.1 Viewing Network Inventory 78
4.4.2 Logging In to a Remote Unit 80
4.4.3 Sending a Beacon Frame 81
5 Configuring the Unit 83

5.1 Configuring General System Settings 84
5.1.1 Setting the S-VLAN Ethertype 84
5.1.2 Regulating Management Traffic 84
5.2 Configuring IPv4 Settings 85
5.2.1 Setting the IGMP Version 85
5.3 Setting Dry-Contact Inputs 86
5.4 Setting the System Date and Time 88
5.4.1 Setting Date and Time Manually 88
5.4.2 Setting Date and Time Automatically 88
5.5 Setting Up SyncE 95
5.6 Viewing SyncE/ESMC Port Statistics 99
5.7 Setting Up DNS 103
5.8 Configuring Traffic 104
5.8.1 Setting the Working Rate 104
5.8.2 Selecting VLAN or VLAN-in-VLAN Filtering 104
5.9 Upgrading the Firmware 106
5.10 Importing/Exporting the Units Configuration 110
5.11 Viewing CPU Usage 112
Document revision 1|March 2015 vi

5.12 Rebooting the Unit 113

5.13 Restarting the Unit 114
5.14 Restoring Factory Default Settings 115
6 Managing Ports 117

6.1 Setting Up Ports 118
6.1.1 Using the Force TX On Parameter 124
6.2 Setting Up Fault Propagation 126
6.3 Network Requirements TCP/UDP Ports 127
6.4 Viewing Port Statistics 130
6.5 Setting Up Port PHY Parameters 138
6.6 Viewing SFP Information 141
6.7 Testing a Cable 145
7 Setting Up Protection 147

7.1 Setting Up LAGPort Protection 148
7.1.1 Setting Up Port Protection 148
7.1.2 Switching to the Standby Port 149
7.1.3 Viewing LACP Status 150
7.1.4 Viewing LACP Statistics 152
7.2 Setting Up ERPProtection 154
7.2.1 Viewing ERP Status 156
7.2.2 Forcing a Switch to the Standby Port 158
7.2.3 Clearing a Forced Switch 158
7.2.4 Switching Manually to the Standby Port 158
7.2.5 Viewing ERP Statistics 159
7.2.6 Viewing the ERP VLAN Learning Table 160
8 Managing Traffic 163

8.1 Understanding the Creation of Ethernet Services 164
8.2 Defining Filters 167
8.2.1 Configuring a Layer-2 Filter 167
8.2.2 Configuring an IPv4 Filter 170
8.3 Setting Up Ethernet Services 176
8.3.1 Setting Up VID Sets 176
8.3.2 Setting Up Bandwidth Regulators 181
8.3.3 Setting Up Bandwidth Regulator Sets 183
8.3.4 Setting Up CoS Profiles 184
8.3.5 Setting Up Port CoS-to-PCP Mapping 186
8.3.6 Setting Up Traffic Policies 188
8.3.7 Viewing Traffic Regulator Statistics 198
8.4 Setting Up Traffic Shaping 201
8.5 Understanding Traffic Shaping via H-QoS 202
8.5.1 Setting Up H-QoS 203
8.5.2 Understanding BLUE 204
8.5.3 Configuring Queues for H-QoS 204
8.5.4 Viewing Traffic Shaping Queue Statistics 207
8.5.5 Configuring H-QoSQueuing Profiles 211
Document revision 1|March 2015 vii

8.5.6 Creating a Shaping Envelope 212

8.5.7 Configuring a Port Shaper 214
8.5.8 Viewing Traffic Shaping OAM Queue Statistics 215
8.5.9 Configuring Default Queuing Profiles 218
8.6 Using Layer-2 Protocol Tunneling 220
8.6.1 Viewing Statistics for L2 Tunnel Rules 221
8.6.2 Setting Up a Layer-2 Tunnel 222
8.7 Monitoring Traffic 228
9 Monitoring Network Performance with Ethernet OAM 231

9.1 Setting Up an OAM Instance 232
9.2 Viewing OAM Events 235
9.3 Viewing OAM Status 236
9.4 Viewing OAM Statistics 239
10 Monitoring Network Performance with Service OAM 245

10.1 Using the Performance Assurance Agent 246
10.1.1 Setting Up a Probe 246
10.1.2 Deleting a Probe 255
10.1.3 Viewing Probe Status 255
10.1.4 Viewing Probe Results 256
10.2 Using Service OAM 262
10.2.1 Setting Up CFM 263
10.2.2 Setting Up Link Trace Messages 277
10.2.3 Viewing Link Trace Messages Information 278
10.2.4 Setting Up Loopback Messages 278
10.2.5 Viewing Loopback Message Information 281
10.2.6 Setting Up Delay Measurements 281
10.2.7 Deleting a Delay Measurement Instance 284
10.2.8 Viewing Delay Measurement Results 285
10.2.9 Setting Up Packet Loss Measurement 288
10.2.10 Deleting a Packet Loss Instance 289
10.2.11 Viewing Packet Loss Results 289
10.2.12 Setting Up Synthetic Loss Measurements 290
10.2.13 Deleting a Synthetic Loss Measurement Instance 292
10.2.14 Viewing Synthetic Loss Measurement Results 292
10.2.15 Managing CFM Interfaces 293
10.2.16 Assigning a CFMInterface 294
10.2.17 Unassigning a CFMInterface 294
10.2.18 Setting Up VSP 295
10.2.19 Viewing VSP Statistics 296
10.2.20 Setting Up CFM Defaults 296
10.3 Using Service Availability 298
10.3.1 Setting Up Service Availability 299
10.3.2 Deleting an SA Instance 300
10.3.3 Setting Up an SA Metric 300
10.3.4 Deleting an SA Metric 302
10.3.5 Putting an SA Instance into Service 302
10.3.6 Viewing SA Counters 303
Document revision 1|March 2015 viii

10.4 Using the Two-Way Active Measurement Protocol (TWAMP) 306

10.5 Setting Up TWAMP Generator Measurements 307
10.5.1 Deleting a TWAMP Generator Instance 311
10.6 Viewing TWAMPGenerator Session Results 312
10.7 Viewing the TWAMPGenerator Session Status 316
10.8 Setting Up a TWAMP Reflector 318
10.9 Viewing TWAMP Reflector Statistics 319
11 Testing Network Performance 321

11.1 Setting Up SAT Reporting 322
11.2 Testing Locally-Created Services 324
11.3 Using RFC-2544 for Traffic Generation and Analysis 326
11.3.1 Setting Up the Traffic Generator 326
11.3.2 Starting the Traffic Generator and Viewing Test Results 332
11.3.3 Setting Up the Traffic Analyzer 334
11.3.4 Viewing Traffic Analyzer Test Results 337
11.3.5 Setting Up a Test Suite 339
11.3.6 Running a Test Suite and Viewing Test Reports 348
11.4 Using Y.1564 for Service Activation Testing 350
11.4.1 Setting Up a Y.1564 Test 350
11.4.2 Setting Up a Y.1564 Service 353
11.4.3 Running a Y.1564 Test and Viewing Test Results 360
11.5 Using the SATProtocol 362
11.5.1 Setting Up the SAT Protocol 362
11.5.2 Viewing SATProtocol Statistics 363
11.5.3 Viewing SATProtocol Sessions 364
12 Managing Loopbacks 365

12.1 Understanding Loopback Testing 366
12.2 Setting Up and Enabling Loopbacks 367
13 Managing Alarms and System Messages 371

13.1 Managing Alarms 372
13.1.1 Setting General Alarms 372
13.1.2 Customizing Alarms 373
13.1.3 Viewing Alarms 374
13.1.4 Viewing Chassis Alarms 383
13.2 Viewing Dry-Contact Alarms 385
13.3 Managing Syslog Messages 386
13.3.1 Defining Syslog Parameters 386
13.3.2 Sending Syslog Messages to a Remote Location 387
13.4 Managing the SNMP Agent 388
13.4.1 Enabling the SNMP Agent 388
13.4.2 Setting Up the SNMP Trap Receivers 389
13.5 Managing History Files 390
13.5.1 Creating History Files 390
13.5.2 Transferring History Files 392
Document revision 1|March 2015 ix

1 About This Manual

This document provides information about the technologies and standards used in
Accedian Networks equipment and procedures to help wireless operators, service
providers and cable MSO personnel to provide service assurance and service creation
solutions to their clients.
Intended for network designers and network administrators, this document will help in
the design, configuration and use of Accedians network devices such as the GT
Performance Element. The term unit in this document refers to any one of these
network devices. The term management Web interface refers to the Web-based
interface that comes with the unit.
Document revision 1|March 2015 1

1.1 Organization
This document contains an introduction, as well as several chapters of detailed
procedures and examples.
The Introduction chapter provides information about technologies and standards used in
Accedians equipment.
The various chapters containing information and procedures for configuring the
equipment are as follows:
"Managing the Unit"
"Configuring Plug & Go"
"Configuring the Unit"
"Managing Ports"
"Setting Up Protection"
"Managing Traffic"
"Monitoring Network Performance with Ethernet OAM"
"Monitoring Network Performance with Service OAM"
"Testing Network Performance"
"Managing Loopbacks"
"Managing Alarms and System Messages"

Tables of parameters are provided to help you understand the function of each
parameter that is available for a particular feature. Whenever possible, parameters are
listed in the order in which they appear in the interface.
Typographical standards for this document are provided in "Conventions" on page 3.

1.2 Conventions
This manual uses certain types of document conventions to help you distinguish between
commands, keywords and language elements. Furthermore, special formatting elements
have been added to draw your attention to certain types of information.
The conventions described below appear throughout this manual:
Commands and keywords are presented in bold.
Menu options when navigating in the Web interface's menu system are shown as follows:
SOAM CFM DMM Configuration
Brackets [] are used when several options are available and you need to select a specific
option. For example, in the following line you need to select a specific port name when
you reach the PHY page: Port PHY [Port name]
Alarm numbers are composed of three parts: x.yyyy.zz. The first number (x) refers to a
general category. The second number (yyyy) refers to the specific component. The third
number (z) is the specific alarm code. For example, in 2.0001.01, the 2 refers to SFP
modules, 0001 is for SFP-1 and 01 means temperature high alarm. So, 2.0001.01 means
SFP-1 temperature high alarm. In the alarm descriptions, <SFP module> can refer to any
SFP module, depending on the value of the component number yyyy.
Note: Information that emphasizes or supplements points within the
main text. Notes often provide details that only apply in certain
situations.
Tip: A suggestion or hint concerning the procedure being described. Tips
may suggest an alternative method or clarify product capabilities.
CAUTION: Describes a situation where failure to take or avoid a specified

action could result in damage to equipment.

1.3 References
The use of equipment such as the GT Performance Element involves the understanding of
different networking standards, technical specifications and technologies. This document
provides basic information on the standards and technologies. For more information
about the standards and technical specifications, refer to the following:
IEEE 802.1ag Connectivity Fault Management
IEEE 802.3ah Ethernet in the First Mile (EFM)
IEEE 802.3ax Link Aggregation
ITU-T Y.1731 OAM functions and mechanisms for Ethernet-based networks
ITU-T Y.1564 Ethernet Service Activation Test Methodology
RFC-2544 Benchmarking Methodology for Network Interconnect Devices
RFC-5357 Two-Way Active Measurement Protocol
Technical Specification MEF 17 Service OAM Requirements & Framework Phase 1
Technical Specification MEF 6.1 Ethernet Services Definitions Phase 2
Technical Specification MEF 9 Abstract Test Suite for Ethernet Services

at the UNI
Technical Specification MEF 10.2 Ethernet Services Attributes Phase 2
Technical Specification MEF 14 Abstract Test Suite for Traffic

Management Phase 1
Technical Specification MEF 22 Mobile Backhaul Implementation Agreement,

Phase 1
Technical Specification MEF 26 External Network Network Interface

(ENNI) Phase1

2 Introduction to the GT Performance Element

The GT Performance Element is a 1 GbE platform based on Accedians all-hardware Fast-
PAAs processing enginewith a proven feature set for high capacity MEF User Network
Interface (UNI) and External Network-to-Network Interfaces (ENNI), to support a variety of
mobile backhaul and business services applications.
The GT Performance Element is based on the same innovative hardware as Accedian
Networks' award-winning TE and 10GE Performance Element units, which have been
successfully deployed since 2005 by hundreds of service providers worldwide. Accedian
leveraged its Fast-PAAs processing engine to provide a wire-speed 1-Gig high-performance
service assurance node with the rich service creation, service assurance and a test
generation feature set that carriers have come to rely on. Like all Accedian units, the GT
Performance Element offers near-zero pass-through delay and delay variation, making it
ideal for performance-critical 1-Gig hand-offs and SLA monitoring applications.
By sharing a common Fast-PAAs engine with Accedians GigE NIDs, the GT Performance
Element can be used to aggregate them to provide centralized coverage for all locations
throughout the network, providing end-to-end performance assurance and visibility.
Complementing the TE Performance Element by offering advanced functionality for
aggregation and critical enterprise locations, the GT Performance Element fits into MSC,
co-location hand-offs and demanding 1-Gig business customer sites: assuring QoS
without impacting it in any way.
For more information about any platform, visit Accedians website at www.accedian.com.

2.1 Applications
Accedian Networks is the leading provider of high-performance service-assurance
solutions which enable service providers to deploy, monitor and maintain high
performance, low delay and delay variation, real-time services over Ethernet, IP/MPLS
and converged networks.
High-performance 3G, 4G / LTE wireless backhaul, real-time business and carrier hand-off
applications require ultra-low delay and delay variation, guaranteed throughput and
carrier-grade reliabilityas well as operational efficiency that reflects todays competitive
telecom marketplace.
Services created and assured by Accedian Networks High Performance Service Assurance
Platform benefit from real-time service mapping, traffic conditioning, in-service
monitoring, loopback testing, service management and demarcation that enable you to
establish end-to-end operational control, revenue-driving SLAs and dependable
performance.
For more information about the possible applications of Accedians GT Performance
Element platform, refer to Accedians website at www.accedian.com.

2.1.1 Mobile Backhaul

Accedian provides the industrys most accurate high performance backhaul assurance
with micro-second delay and delay variation measurement, hitless throughput and
remote loopback testing, mesh-network support and advanced traffic control edge-to-
edge. The worlds leading 4G/LTE deployments rely on Accedian Networks to deliver
unparalleled real-time performance, enabling Carrier Ethernet to be used effectively for
backhauling mobile broadband applications.

2.1.2 Assured Business Services

Accedian enables and assures SLA-backed business services, including transparent LAN
access, VoIP, video conferencing, data center interconnection, remote storage and
transactional services with carrier-grade availability. Use our products to securely
establish end-to-end OAM, QoS performance and real-time visibility.

2.1.3 Carrier Ethernet Exchange Services

High performance service assurance enables wholesale providers to offer reliable Ethernet
services wholesale to generate new revenue by extending Ethernet services to off-net
locations with fully-assured, QoS-optimized EVCs. GT Performance Element units
effectively establish ENNI handoffs and reach remote customer sites with complete
control and visibility, assuring end-to-end SLA performance while providing individual
performance metrics for each Operator Virtual Connection (OVC).

2.1.4 Carrier Ethernet Global Interconnect

Deploying Accedians GT Performance Element units at the ENNIs joining multiple
operator networks enables performance assurance for services spanning multiple
carriers, peering fabrics, technologies and manufacturersin-line and in real-time
without affecting customer traffic. Accedian Networks delay-free and delay-variation-free
demarcation solutions bridge segments and monitor network boundaries, providing end-
to-end control over real-time applications.

2.1.5 Enterprise WAN QoS

Accedians applications for the Enterprise optimize WAN performance and accelerate
critical business applications with traffic shaping, filtering and switch-free aggregation for
each Class-of-Service. The same high-performance service-assurance platform used by
service providers can be used to continuously monitor and optimize the performance of
every applications data flow, with Accedian Networks' SLA-Meter.

2.1.6 Ethernet Service Creation

Create fully transparent Ethernet Virtual Connections (EVC) over any networkwithout
replacing or configuring network elements. Optimize service and core network
performance with hardware-based rate limiting, traffic shaping, and filtering directly at the
demarcation point.

2.2 Features
2.2.1 Service Assurance

Accedian Networks' high-performance service-assurance platform provides standards-
based in-service monitoring, loopback testing, remote troubleshooting, service
management and network demarcation for high-performance mobile backhaul, business
services and carrier interconnect and exchange applications.
Accedian provides the highest performance network monitoring, troubleshooting, and
network management tools that maintain and assure carrier-grade Ethernet. The
industry's first SLA-Meter has a comprehensive suite of active and passive in-service
performance testing, intelligent Layer14 loopback functionality and per-flow traffic
monitoring.
Establish complete, end-to-end control of your services, Map-out the Health of your
Network, and increase the dollar value of every packet flowing through it with Accedian
Networks' service assurance solutions.
For more information about service-assurance features for Accedians GT Performance
Element, refer to Accedians website at www.accedian.com.
Service Demarcation
Define the boundaries of your network and services with intelligent demarcation between
your network and those of your customers and third-party network operators. Accedian
GT Performance Element high-performance service-assurance demarcation units establish
end-to-end OAM, enable in-service loopback and performance testing and let you create
and assure carrier-grade SLAs.

Layer14 Loopback Testing with Test Set Support

Establish Layer14 loopbacks from your existing test set, monitoring system or other GT
Performance Element units. Loop traffic by multiple packet-filtering criteria, including
VLAN, service level, destination and source MAC / IP addresses without interrupting
customer traffic.
For more information about Loopback testing, refer to the chapter "Managing
Loopbacks" on page 365.

Traffic Generation and Analysis

Perform in-line Traffic Generation and Analysis, throughput and performance testing with
the GT Performance Element. Measure delay, delay variation and frame loss in order to
troubleshoot, provision and validate Ethernet services and SLAs.
For more information about Traffic Generation and Analysis, refer to the chapter "Testing
Network Performance" on page 321.
Performance Monitoring
Accedian Networks Performance Assurance Agent (PAA) keeps continuous watch over
the critical services on the network with one-way-delay and delay-variation
measurements, frame loss and availability monitoring. Test up to 300 sites from a single
GT Performance Element demarcation unit.
For more information about PAA, refer to the chapter "Monitoring Network Performance
with Service OAM" on page 245.

SLA Performance Assurance

Establish end-to-end transparent LAN services with EVC service creation functionality and
monitor them in real-time with the industrys only SLA-Meter. Performance is fully
transparent over multi-manufacturer, multi-carrier, multi-technology networks.
For more information about SLA Assurance, refer to the chapter "Managing Traffic" on
page 163.

2.2.2 Service Creation

Accedians high-performance demarcation devices provide a uniform network interface
for creating MEF-compliant Ethernet Virtual Connections (EVC) services over any network
topology, media or protocol. GT Performance Element units provide advanced traffic
classification at wire-speed to identify individual services and add the provisioned EVC
service tags and CoS markings without adding delay to the service flows as they enter the
Carrier Ethernet network. Optimize service and core network performance with wire-
speed traffic conditioning and flexible rate limiting, traffic shaping, filtering and switch-free
aggregation at the intelligent access edge.
Accedian Networks high-performance service-assurance platform helps you create
services by deploying end-to-end Ethernet transparent LAN services with guaranteed
performance and availability over any networkwithout disturbing your switches or your
customers.
Quickly create Ethernet Virtual Connections (EVCs) for E-Line, E-LAN and E-Tree services
with EVC service mapping: advanced networking functionality is built right into GT
Performance Element units designed for customer, cell, aggregation and head-end sites.
Multi-technology networks EVC service mapping functionality transparently creates
Ethernet LAN services and avoids interoperability issues.
Create, accelerate, optimize and manage Ethernet services with per-flow service mapping,
traffic shaping, filtering and bandwidth policing directly at the demarcation point and
bypass costly switch upgrades. Leverage real-time multi-port aggregation and bypass
switches altogether.
Accedians unique Fast-PAAs engine, the industrys only wire-speed performance
assurance agent, enables the units to maintain EVCs at GbE and 1-GbE speeds without
introducing delay or delay variation to critical, real-time traffic. Easily configured remotely,
building EVCs is as simple as installing GT Performance Element units at the demarcation
points and provisioning services from the Web.
For more information about service creation features of Accedians GT Performance
Element, refer to Accedians website at www.accedian.com.

Ethernet Service Mapping

Accedian GT Performance Element demarcation devices establish, identify, classify and
mark individual traffic flows into provisioned Ethernet Virtual Connections over any
network. With a variety of EVC service creation capabilities, service providers can use any
Ethernet, IP or transport layer header information to steer traffic into specific service EVC,
at wire-speed. Once created, each EVC is conditioned with bandwidth profiles and class-
of-service markings that deliver high-performance SLA-backed E-Line, E-LAN and E-Tree
services.
For more information about Ethernet Service Mapping, refer to the chapter "Managing
Traffic" on page 163.

Bandwidth Profile Regulators

Accedian assures SLA compliance by protecting the network from congestion by providing
continuous bandwidth regulation of the committed information rate (CIR) and excess
information rate (EIR) flows in the network. Bi-direction per-EVC throughput management
enables service providers to enforce admission control policies that assure network
performance integrity and guarantee the delivery of CIRs even during network
congestion.
For more information about Bandwidth Policing, refer to the chapter "Managing Traffic"
on page 163.
Traffic Filtering
Accedians advanced comprehensive traffic filters help preserve network security and
prevent broadcast messages and malicious traffic from flooding your network. They
provide wire-speed traffic filtering by VLAN, Ethernet/IP address, Ethertype, service class
or TCP/UDP port.
For more information about Traffic Filtering, refer to the chapter "Managing Traffic" on
page 163.

Traffic Shaping
Accelerate low delay services, reduce network overhead, and economize bandwidth with
advanced, hardware-based traffic shaping that passes critical, real-time traffic at wire-
speed using the Fast-PAAs zero-delay cut-through queue, while standard traffic is priority-
queued, shaped and forwarded.

3 Managing the Unit

This chapter contains the following sections:
3.1 About the Management Web Interface 22
3.2 Starting the Management Web Interface 24
3.3 Configuring the Logical Interfaces 31
3.4 Finding a Host (Ping and Traceroute) 43
3.5 Using the Serial Console 44
3.6 Managing the Link Layer Discovery Protocol (LLDP) 46
3.7 Managing Sessions 49
3.8 Managing Users and Privileges 54
3.9 Using a RADIUS Server for Authentication 60
3.10 Using a TACACS+ Server for Authentication 62
3.11 Managing Access Control Lists 65

3.1 About the Management Web Interface

The Web-based management interface provides secure access, via an SSL client, to all
system control, management and monitoring functions.
The management station is the computer that you use to connect to the management
Web interface; it must be equipped with a JavaScript-enabled Web browser (such as
Mozilla Firefox, Google Chrome or Microsoft Internet Explorer v6.0 or later) installed.
The elements of a typical user interface screen are shown below. Help is available for each
page of the interface by clicking the question mark icon (?)to the right of the section title
bar.
Typical Screen
Date and time: The date and time configured on for this unit. To set the date and time,
access the page System Configuration Time.
Alarms: Indicates alarms that have been triggered. For more information on alarms, refer
to the chapter "Managing Alarms and System Messages" on page 371. Beside the alarms,
the username of the currently-logged in user along with the unit's serial number appears.
Working area: This is where you view information and configure system parameters.
First-, second- and third-level menus: The top row presents the first-level menu, and is
always visible. The second row presents a menu of second-level options based on the
item selected from the first-level menu. The third-level items are dependent on the option
selected from the second-level menu.
To navigate to the various functions, click an item from the first-level menu, then click a
second-level menu item until you access the function you want to use. Each menu item
you select will be highlighted. For example, in the figure above, the selected menu item is
System Session Management.

Selecting a third-level menu option often displays a summary of the information

requested. If you then click one of the elements listed in the summary, you will obtain
detailed information on that element. The parameters present on both the summary and
detailed pages are described within one table in this manual. For example, the table for
System Session Permissions describes all parameters present on both the summary
page for all sessions and the detailed page for a specific session. The parameters are listed
in the tables in the order in which they appear on the screen, wherever possible.
Writelock button: Use this button to toggle between yes and no for Writelock. For more
information about this function, refer to the section on "Locking or Unlocking User
Sessions" on page 50.
Logout button: Use this button to logout from the current session.
Reset: Use this button to reset the value of a page, before you apply the change. This is
useful when you are not sure precisely which values you changed and want to start over
using the previous configuration. This action has the same effect as leaving this page to
view another page and then returning to this page. Available on some pages only.
Apply: Use this button to apply the changes made on the page to the equipment. This
action changes the equipment configuration immediately. Available on some pages only.
Search: Use this button to filter any list shown on a page to narrow down the list to
elements you have specified on the drop-down list. Once you have the desired list shown
on the page, you can also click this button to refresh the status and values of each field.
For example, this can be useful in a Results page, helping you to view the changing results
while a test is performed.
Note: Using your browsers Refresh command does not simply refresh the
values or list shown on one page; it reloads the page completely, thereby
eliminating any filter that you had previously applied.

3.2 Starting the Management Web Interface
3.2.1 Physically Connecting to the Unit

The first time you connect to the unit, before logging in you must connect the LAN port
on the management station to the management port on the front of the unit. This allows
you to login and configure the unit for the first time. For example, you can set the units
time and date and create other logical interfaces so you can connect through a LAN or
WAN (refer to "Configuring the Logical Interfaces" on page 31.
The default management port for the GT Performance Element is the Management port.
3.2.2 Logging In
Once you have a physical connection to the equipment, you can login. Depending on the
configuration of the unit, you may login in different ways. You would usually connect to
the unit for the first time using the Management port. Normally you would then configure
another interface, e.g. Network, for in-band management through the network.
When logging in for the first time

1. Assign the unit a static IP address belonging to the same subnet as the equipment to
which you want to log in. The address 192.168.1.2 is used in this procedure.
2. Start your Web browser and enter the following in the address bar:
https://192.168.1.254.
Note: This is the factory default IP address of each unit. If you are using
static IP addresses, you should then modify the units IP address to be
unique, thereby avoiding duplicate IP addresses with other factory
default units. As an alternative, you can also configure the unit to use
DHCP.
For more information on modifying IP addresses, using DHCP and other
options for logical interfaces, refer to "Configuring the Logical Interfaces"
on page 31.
3. The login page for the unit opens. Login as admin with the password admin.
Note: This is the default password for the user "admin", which is a special
user account that has been granted full read/write access to all the unit's
settings. It is strongly recommended to change the default admin
password after your first login; doing so ensures that only the admin user
can perform admin functions and control access to the unit. To change
the password, refer to the section "Changing Passwords" on page 59.

When logging in for the first time (if you have already configured another
logical interface)
1. Ensure your management station has a route to the equipment.
2. Launch your Web browser and enter the equipment address in the address bar, e.g.
https://192.168.1.252 (or host_name.domain_name if you are using a DNS).
Note: The unit uses TCP port number 443 (HTTPS) for connecting with the
Management Web Interface. If your network blocks this port number,
you can change it to another number using the CLI interface. Refer to
"Using the Serial Console" on page 44 to enable the console port, as well
as to the CLI Help or the CLICommand Guide for information on the CLI
command.
3. The login page opens. Login using the admin username and account password.
3.2.3 Working in the Home Page

The home page provides general information about the unit.
To view the home page shown in the figure below, access the page Home.
Home Page
For information on specific parameters displayed on the home page, refer to the following
table.
Home Page Parameters (Home)
Parameter Description
MAC Base Address The base MAC address of the unit. For a line card with multiple
ports, the base address is the address of the first port, and then
the address is incremented for the second port, etc.

Unit Identifier The name that identifies the unit on the network
Firmware Version The firmware version of the unit. Access the page System
Maintenance Firmware to upgrade the firmware.
Serial Number The serial number assigned to the unit
Assembly The hardware version of the unit
HW Options The hardware option of this card, e.g. GPS or SyncE
Board Info
System Uptime The period of time that has elapsed since the unit was last
restarted, whether it be following a firmware upgrade, a manual
reboot or a power cycle
System Started The time when the unit was last powered on, as reported by the
system clock. To set the system clock, see System
Configuration Time.
Note:This value is reset when a power cycle is performed on
the unit.
3.2.4 Modifying the Unit Identifier

The default host name (or unit identifier) is the serial number of the unit; it is displayed in
the banner at the top of the screen after logging in. You can change the host name to a
name more meaningful to your organization or use other DHCP host name options. The
Host Name identifies the unit on the network and can be used when you login to the unit,
as shown in the figure in the section "About the Management Web Interface" on page 22.
Note: The host name is also used in the CLI prompt and is added to
system log entries to help you identify the unit more clearly.
To modify the unit identifier

1. Access the page System Configuration DNS.
2. Enter the new unit identifier in the Host Name field.
3. Click Apply to save your changes.

For information on specific parameters, refer to the following table.
DNS Parameters (System Configuration DNS)
Use DHCP Results Enables use of DNS settings obtained via DHCP. You can then
select the interface to use for obtaining DHCP information using

From Interface.
Use DHCP6 Results Enables use of DNS settings obtained via DHCPv6. You can then
select the interface to use for obtaining DHCPv6 information
using From Interface (DHCP6).
Host Name The name that identifies the unit on the network. A maximum
of nine alphanumeric characters is supported.
This parameter is only valid when DHCP host name is set to
Current Hostname.
DHCP Host Name The source of the DHCP host name
The available options are:
Current Hostname: The host name is the string entered in
the Host Name field.
Serial Number (DHCP option 12): The host name is the

serial number of the unit.
Custom Hostname (DHCP option 12): The host name is the

text string you enter in the field to the right of the DHCP
Host Name.
Field to the right of This field is only used when the DHCP host name is set to
DHCP host name Custom Hostname.
DHCP Client ID This corresponds to DHCP option 61. It allows you to enter a
text string for use as the units unique identifier when
communicating with the DHCPhost. When the text box is
empty, the MAC address is used as the units client ID.
From Interface The interface used for obtaining DHCP information
Note:This field is only available when the Use DHCP Results
option is enabled.
From Interface The interface used for obtaining DHCP information

(DHCP6) Note:This field is only available when the Use DHCP6 Results
option is enabled.
DNS Server1 The address of DNS server 1 is available only when Use DHCP
Results is not selected.
DNS Server2 The address of DNS server 2 is available only when Use DHCP
Results is not selected.

Domain The local domain name associated with the DNS is available only
when Use DHCP Results is not selected.
3.2.5 Managing SSL Certificates

The SSL protocol is used to secure the communication over the Internet between the
management station and the unit. You must load a valid SSL certificate, from a certificate
authority, into the unit, to provide secure communication. To learn more about
certificates, refer to the certificate authority and ITU-T Recommendation X.509.
Note: You may install the SSL certificate in each browser you want to use
to connect to the unit.
In other cases, you may want the unit to communicate with other applications such as an
FTP server. You can configure the unit for secure communication with these applications
by using Application Management, therefore managing the validation of certificate use.
Access the page System Maintenance Certificates to manage SSL certificates.
System Maintenance Certificates
You can view the SSL certificates installed on the unit in the Certificate Management
section. To view the details of the installed certificates, click the View button.
To delete a certificate, click the Delete button.
To import a new certificate, select the certificate by using Browse in the Certificate Import
section, complete the other fields and click Upload when ready. The certificate will be
loaded into the unit and will appear in the Certificate Management section.
To assign a certificate to a specific application such as an FTP server, select it from the
Common Name drop-down list in the Application Management section. Complete the
other parameters as required, then click Submit to assign it to the application.
Note:If you submitted a certificate for Web Management (the one you
are using right now), you must restart the Web GUIinterface session by

clicking Restart. As the interface's web server restarts, a message will be

briefly displayed before the login page appears.
For information on specific parameters, refer to the following three tables.
Certificate Parameters (System Maintenance Certificates)
Common Name For a certificate authority (CA), this is the name of the
organization that issued the certificate.
For a server, this is the Fully Qualified Domain name of the
service using the certificate (only the Web server at this time).
For a client, this may be the name of the application.
Valid Until The date when the certificate expires. It may still be valid if the
peer has disabled checking.
Function Describes how the certificate can be used in the unit.
CA: Used to validate peer certificates; provided as part of
the certificate chain for server applications
Client/Server: These certificates were imported with a

private key. It is possible for a CA certificate imported with a
private key to be used for this function. In this case, it does
not show up as a CA.
Application Management (System Maintenance Certificates)

Application The available options are:
Web Management: This is the application you are currently
using.
File Transfers: All applications sending or receiving files

through a secure channel (HTTPS or FTPS). For example
firmware upgrades and configuration import/export using
the CLI.
Common Name For a certificate authority (CA), this is the name of the
organization that issued the certificate.
For a server, this is the Fully Qualified Domain name of the
service using the certificate (only the Web server at this time).
For a client, this may be the name of the application.
Validate CA For client applications, perform peer certificate validation. This
includes expiration date, hostname and CA chain.

Enable Client For client applications, enable or disable the use of the selected
client certificate.
Certificate Import (System Maintenance Certificates)

Type The following certificate file types are supported:
pkcs12: For importing client certificates, including the
private key and the CA chain of certificates
pkcs7: For importing multiple CA certificates
x509-PEM For importing either:
A client or server certificate and its private key
A single or multiple CA certificate
x509-DER: For importing single CA certificates

Note:Importing a private key separately from its certificate is
not supported.
Passcode Applies to pkcs12 or PEM encoded private keys, which use a
pass code. The pass code is only used once for importing.
Import Certificate The name of the selected certificate appears here before you
upload it.

3.3 Configuring the Logical Interfaces

You can define one or more logical interfaces for managing the unit. This includes
defining interface types such as standard IPv4 or IPv6, bridges and VLANs. Once the
interface is defined, you can also define a route to access the unit from outside the unit's
subnet.
You can configure interfaces for dual homing by specifying a second IP address (IP
address alias). When specifying an alias, only the address, network mask and gateway
parameters can be defined. An alias interface is always set up as a static IP address (no
DHCP).
You may also consider configuring an interface for advertisement settings, which will allow
you to view a network inventory of all Accedian units that have this option enabled. For
more information on viewing the network inventory, refer to "Managing Network
Inventory" on page 78.
Note: An interface can also be used for other purposes. For example, you
can use an interface for loopback or for test set interaction.
The following types of logical interface are available:
Standard: This interface type is associated with a single port. You would use a
standard interface to manage the unit from one defined port.
Bridge: This interface type is used to connect two or more interfaces as one logical
interface. You would do this when you want to connect to the unit through your LAN
or WAN without having to know which physical port connects your management
station to the unit. With a bridge interface, you have the option of using a spanning
tree protocol and the option of an IP address override for subinterfaces.
VLAN: This interface type is associated, as with the standard interface, with a single
port. An example of when you would use a VLAN interface would be if you want to
separate the management traffic from the client traffic. In this example, you would
create a VLAN for the management and another VLAN for the customer traffic. Using
filters and policies, you would drop the management traffic and permit the
customer traffic to flow through the unit. For more information on filters and
policies, refer to the chapter "Managing Traffic" on page 163.
Note: This does not prevent the Management VLAN traffic from
communicating with the unit.
VLAN-in-VLAN (.1q in .1q): This interface type is also associated with a single port.
You can use this interface type when you want to use sub-VLAN. With a VLAN-in-VLAN
interface, you can assign priority and choose the Ethertype.

Auto: This interface type is listening for beacons on all ports. Once it receives a
beacon, an interface is automatically configured for the port on which the beacon
was received.
Access the page System Configuration Interface to view the existing logical interfaces
and to configure new and existing logical interfaces.
By default, the following logical interfaces are defined:
Management: The default interface (type Standard) that enables access to the
management Web interface via the management port
Auto: The default interface (type Auto) that listens for beacons on all ports
CAUTION: If you modify an interface, you or another user may lose access
to the management Web interface.

System Configuration Interface
For information on specific parameters, refer to the table "Interface Settings (System
Configuration Interface)" on page 34.

3.3.1 Adding or Editing a Logical Interface

After a factory default reset, a logical interface named Management is bound to a port.
For details, refer to "Physically Connecting to the Unit" on page 24. You can add and edit
more logical interfaces to provide the unit with multiple management options.
To add or edit a logical interface

1. Access the page System Configuration Interface.
2. Click Add to create a new interface or click the Interface Name of an existing interface
to edit its settings.
3. Complete the required fields, then click Apply.

Note: The fields displayed will vary, depending on the Interface type you
select.
Note: You can set the IP address for an interface to 0.0.0.0 when the
interface is not required to be an IP interface, such as when the interface is
used for loopback or test set interaction.
For more information on specific parameters, refer to the following table.
Interface Settings (System Configuration Interface)
All Interface Types
State Enabled or disabled
Interface Name A name to identify the interface
Interface Type Standard: Standard IP interface associated with a single
port
Bridge: Bridged interface that connects two or more ports
VLAN: VLAN interface associated with a single port
VLANinVLAN: VLAN-in-VLAN (.1q in .1q) interface

associated with a single port
Auto: You can set up only one Auto interface for each
device. This option cannot be selected on any other
interfaces.
On Port(s) The port on which the interface is active

IPv4
Automatic IP (DHCP) Allows the interface to act as a DHCP client and automatically
obtain its IP address, DNS server and gateway settings from a
DHCP server
Use DHCP Route Allows the unit to get the routing information from the DHCP
Information server
Use Static IP Until Uses the manually configured IP address on the interface until
DHCP Response an address is resolved by DHCP
Available only when using Automatic IP (DHCP) mode. Not
available with Auto interface.
Manual Manual configuration of IP address settings
Configuration
IP Address IP address assigned to the interface, if required
Network Mask The network mask associated with the IP address, if required
Default Gateway A default gateway address provides a shortcut to creating a
default gateway through the route configuration. Only one
default gateway can be set per unit.
IP Address Alias A second IP address that you may assign to the interface if dual
homing is required. This address must belong to a different
subnet than the primary IP address.
Network Mask Alias The network mask associated with the IP address alias, if
required
Default Gateway Alias The default gateway associated with the IP address alias, if
required
Info A brief description of the interface that appears on the network
summary page, e.g. VLAN number, auto interface
IPv6
IPv6 Enable Enable or disable IPv6 on the interface.
DHCPv6 Enable or disable DHCPv6 (used if IPv6 is enabled).
Static Address Enable or disable IPv6 static addresses (used if IPv6 is enabled).
Router Enable or disable IPv6 router advertisement autoconfiguration
Advertisement Prefix (used if IPv6 is enabled).
Static IPv6 Address / Static interface IPv6 addresses (used if IPv6 and IPv6 static
Prefix Length addresses are enabled)

Note: Can be reset by setting the value to :: /0
IPv6 Default Gateway IPv6 default gateway addresses (used if IPv6 and IPv6 static
addresses are enabled)
Note: Can be reset by setting the value to :: .
Bridge Interface Type Only
On Interfaces In the case of a bridge, select multiple interfaces by holding
down the control key when you click interface names in the list.
Enable Spanning-Tree The Spanning Tree Protocol (STP) may be enabled or disabled.
Protocol
Enable Subinterface This option disables DHCP and resets the IP address of each
IP Override subinterface to 0.0.0.0. This action is necessary when adding
subinterfaces to a management bridge.
For example, if the Management interface is assigned address
192.168.1.254 and the Network interface (in-band) is assigned
address 192.168.2.100 and you configured a bridge between
them, enabling the subinterface IP override would reset all
subinterface addresses to 0.0.0.0.
You then would be able to assign an IP address to the bridge.
The Management and Network interfaces would be part of the
bridge and the unit would be accessible via any port that is part
of the bridge, using the bridge's IP address (192.168.2.200).
VLAN Settings (VLAN and VLANinVLAN Interface Types Only)
VLAN ID VLAN ID (Management VLAN) assigned to the interface
VLAN Priority VLAN priority of 07
Ethertype Ethertype for the first and second VLAN IDs. The Ethertype may
vary, depending on the equipment to which the unit is
connected:
C-VLAN: 0x8100
S-VLAN: 0x88A8
T-VLAN: 0x9100
Beacon Settings (All Interface Types Except Auto)

State Enable or disable the transmission of beacon frames using the
interface.
Beacon Rate The interval at which the beacon frames will be sent:

3 seconds
1 minute
10 minutes
60 minutes
The default interval is 1 minute.
Domain ID In the discovery process, the domain ID can be matched by
remote devices to select which beacons it should process.
See the Domain ID and ID Matching parameters in the
Discovery Settings parameters.
IP Config Mode Indicates which IP configuration mode the receiver should use:
Local: Use the receiver interface settings.
Auto: Instruct the remote device to compute an IP

address, given the subnet, gateway and mask.
Auto Static: Behavior is similar to that of Auto

configuration mode; however, in the case of a power reset,
this mode preserves the IP address, gateway and mask
values if an IP address (other than 0.0.0.0) is already
configured.
DHCP: Use DHCP to obtain an IP address for the AUTO

interface.
IP Subnet Subnet used by the receiver when the Auto or Auto Static IP
Config Mode is selected
Mask Mask used by the remote device when the Auto or Auto Static
IP Config Mode is selected
Gateway Gateway used by the remote device when the Auto or Auto
Static IP Config Mode is selected
Authorize ID When enabled, it tells the receiver to accept beacon frames
Mismatch even if the beacon's domain ID does not match the local
domain ID when ID matching is enabled at the receiver. Useful
for troubleshooting Domain entry errors.
DHCP Host Name Possible values are:
Current hostname

Serial number
Custom hostname
DHCP Client ID Possible values are:

Serial number
Custom client ID
IP Exclusion List In Auto and Auto IP Static configuration modes, this list of IP
addresses is excluded from the remote units.
You can specify both single IP addresses and ranges of
addresses, each separated by commas. For example, a range of
172.16.1.2-172.16.1.5 spans four IPaddresses.
A total of 100 IP addresses can be specified here, including both
address ranges and single IPaddresses.
One-Shot Beacon When you press Send, the system sends a single beacon frame
with the information that has previously been configured and
applied. If changes to the beacon settings were made without
clicking Apply, they would not be effective in the beacon frame.
Discovery Settings (Auto Interface Only)
Beacon Discovery Processing of beacon frames upon reception. When enabled,
State the discovery ports listen for beacon frames and configure the
Auto interface.
Last Effective If the unit was configured with the Plug & Go feature, this field
Beaconer MAC shows the source MAC address of the beacon used for
configuring the auto interface. In other words, this MAC
address identifies the beaconer (the remote unit that sent the
beacon).
ID Matching Tells the receiver to accept beacons only if the beacon's domain
ID matches the local domain ID
Domain ID The domain ID to use in the discovery process. The domain ID
can be matched with the incoming beacon domain ID to
determine if the beacon should be processed.
Discovery Ports A list of ports enabled to listen for incoming beacon frames
Forwarding Settings (Auto Interface Only)
Level The ACP frames level. This level is used in transmitted
advertisement and beacon frames. A unit receiving a beacon

frame will automatically set its system ACP level to the one
included in the beacon frame.
07: For a specific level. The ACP frames level defines how
far the ACP frames can go. A unit requires a higher level to
be used to run above a lower level. For example, a unit
using ACP frames level 3 will be able to reach another unit if
the other units in between have an ACP frame level of 2 or
below.
All: All ACP frames will go through this unit without

processing.
Forward on Bridge When enabled, beacons and advertisement frames are

forwarded using the bridge associated with this interface, if a
bridge exists.
When enabled, the forwarding ports on match are not effective.
Forwarding Ports on A list of ports to forward beacons and advertisement frames to
Match when the domain ID of these frames matches the configured
domain ID
Forwarding Ports on A list of ports to forward beacons and advertisement frames to
Mismatch when the domain ID of these frames does not match the
configured domain ID
Advertisement Settings (All Interface Types)
L2 State The advertisement of information frames may be enabled or
disabled. Information frames are used to advertise to a central
unit.
Default for Auto Interface: Enable
Default for Other Interfaces: Disable
L3 State The advertisement of Layer-3 information frames may be
enabled or disabled.
Default (all interfaces): Disabled
Advertisement IP The destination IP address to be used in Layer-3 advertisement
frames
Use Rate from When enabled, the advertisement transmission rate matches
Beacon the rate that is configured in the beacon settings.
Transmission Rate The advertisement transmission rate to use when the beacon

rate option is disabled
Advertisement The frame format to use when sending information frames
Format ACP: Accedian's proprietary format
ACL Settings (All Interface Types)
ACL State Enable or disable the use of ACLfor this interface
ACL The ACLassigned to this interface
ACL Types Enable or disable the use of ACL for each management type:
CLI: SSH and Telnet
WEB
SNMP
3.3.2 Setting Up a Beacon Instance at Layer 3

You can configure a logical interface to send beacon frames. A frame is sent by the central
unit (or another unit configured as the beaconer) to all remote units that are used by the
auto interface for auto-provisioning. This can be done at Layer2 or Layer3. Configure the
unit to send beacon frames at Layer2 if the remote units are within the same subnet.
Configure the unit to send beacon frames at Layer3 if the remote units are outside the
beaconer's subnet.
Only configure one unit on your network either the central unit or a separate beaconer
for sending beacon frames. Configure the auto interface of the remote units to listen
for beacon frames by modifying the Discovery Settings parameters.
To set up a beacon interface at Layer3, see "Setting Up a Beacon Instance at Layer3" on
page 73.
To set up a beacon interface at Layer2, see "Configuring the Logical Interfaces" on page
31.
3.3.3 Adding or Editing an IPv4 Route

You can define an IPv4 route that is outside the subnet defined by each interface in order
to access a unit that is not in the management stations subnet.
Access the page System Configuration Interface to view the existing, active IPv4
routes and update their settings.

To add or edit an IPv4 route

2. In the IPV4 Routes section of the screen, click the Add button to add a new route or
click the route Name to edit an existing route.

IPv4 Route (System Configuration Interface)
Name The name to assign to the route. It can also be a brief
description of the route, such as Default Route.
Type The route type may be either Network (for a range of addresses)
or Host (for a specific IP address).
Interface The interface with which the route is associated. This field is
optional if a matching active route is already associated with the
interface.
Destination The route's network or host address. The default IPv4
destination is 0.0.0.0.
Network Mask / The mask assigned to the route
Netmask Note:Only used for Network routes.
Gateway The gateway associated with this route
3.3.4 Adding or Editing an IPv6 Route

You can define an IPv6 route that is outside the subnet defined by each interface to
access a unit outside of the management stations subnet.
Access the page System Configuration Interface to view the existing, active IPv6
routes and update their settings.
To add or edit an IPv6 route

2. In the IPV6 Routes section of the screen, click the Add button to add a new route or
click the route Name to edit an existing route.


IPv6 Route (System Configuration Interface)

Name The name of the IPv6 route. It can be a brief description of the
route, e.g. Default.
Type Route type may either be Network for a range of addresses or
Host for a specific IP address.
Interface The interface with which the route is associated. This is only for
specific situations when a target exists on a different network
for that interface. In most situations, the interface is
determined automatically.
Destination The route's network or host address. Use ::/0 to indicate the
default route.
Network Mask / The mask assigned to the route.
Netmask Note:Only used for network routes.
Gateway The gateway address associated with this route or default
gateway address
Next Hop For a direct delivery (in which the destination is on a local link),
the next hop address is the destination address.
For an indirect delivery (in which the destination is not on a local
link), the next hop address is typically the link-local address of a
neighboring router.
Flags Possible values are:
X Disable
A Active
D Dynamic
S Static
C Connect
U Unreachable
Metric The preference of the route. The lowest metric is the preferred
route. The metric is used to select the route between multiple
routes with the same prefix.

3.4 Finding a Host (Ping and Traceroute)

The equipment provides ping and traceroute functions to help administrators
troubleshoot network problems.
Use the ping function to verify whether a specific host (IP address) is reachable.
Use the traceroute function to identify the route used by an IP packet to traverse the
network and reach a specific destination.
To ping a remote host

1. Access the page System Maintenance System Tools.
2. Enter the host IP address and the timeout and click the Ping IPv4 or Ping IPv6
button.
To trace a route to a remote host

1. Access the page System Maintenance System Tools.
2. Enter the host IP address and the maximum number of Hops , then click the
Traceroute IPv4 or Traceroute IPv6 button.
For more information on specific parameters, refer to the following two tables.
Ping (System Maintenance System Tools)
IP Address The IP address to which to send a ping message
Timeout The number of ping messages to send before timing out
Acceptable values range from 1 to 10.
Ping IPv4 Executes an IPv4 ping
Ping IPv6 Executes an IPv6 ping
Traceroute (System Maintenance System Tools)

IP Address The IP address to traceroute
Hops The number of hops to attempt
Traceroute IPv4 Executes an IPv4 traceroute
Traceroute IPv6 Executes an IPv6 traceroute

3.5 Using the Serial Console

The unit provides a serial (RS232) console port (RJ45) to manage the equipment using a
serial port on a management station. After logging in, you can enable or disable the
console port.
To enable or disable the console port

1. Access the page System Configuration Console.
2. Verify the current state of the console port in the Console State field.
3. Click Enable Console or Disable Console as required.

The console port provides a CLI interface to the unit. Refer to the CLI Command Manual
for information on how to use the CLI.
To use the console port, you must use a terminal emulation program with the following
settings:
Terminal Emulation Settings
Parameter Setting
Protocol Serial
Port COM 1 to 8
Baud Rate 115200
Data Bits 8
Parity None
Stop Bits 1
Flow Control None
You can connect the serial port on the management station to the RJ45 console port on
the unit using the following diagrams and table.

Serial Console Cable Connectors
Console Port Cable Pinouts

Unit Console Port (RJ45) Management Station Serial Port (DB9)
Pin Signal Pin Signal
1 DC1 (dry-contact 1 input)
2 Not connected
3 Tx data 2 Rx data
4 Ground 5 Ground
5 Ground 5 Ground
6 Rx data 3 Tx data
7 Not connected

3.6 Managing the Link Layer Discovery Protocol (LLDP)

Link Layer Discovery Protocol (LLDP) is a protocol that allows stations attached to an IEEE
802 LAN to advertise to one another. Three types of information are advertised: the major
capabilities provided by the system incorporating that station, the corresponding
management addresses , and the identification of the stations point of attachment to
the IEEE 802 LAN required by those management entities.
The unit uses LLDP to advertise connectivity and management information about the unit
to adjacent stations, and to receive and display network management information from
adjacent stations, all on the same IEEE 802 LAN.
To view LLDP information, access the page Show LLDP. For more information on
specific parameters, refer to the table at the end of this section.
Show LLDP
To view detailed LLDP information of a specific port, click the port name in the LLDP
Neighbors or LLDPConfiguration sections. For more information on specific parameters,
refer to the table at the end of this section.
To enable or disable LLDP frame transmission on a specific port

1. Access the page Show LLDP.
2. Click the port name for which you want to enable or disable the LLDP frame
transmission.
3. Set the Enable and Rate parameters of the LLDPConfiguration section.


LLDP (Show LLDP)
LLDP Neighbors
Timestamp Date and time of the last update
Source MAC MAC address of the remote system connected to this
port
System Name Name of the remote system connected to this port
System Description Description of the remote system connected to this port
Port ID Remote system port identifier
Mgt Address # IP address for remote system management
Note:There may be more than one such address.
If index # The interface index value used to identify the port
associated with this management IP address
TTL Time To Live (TTL) of the last received LLDPDU frame
LLDP Statistics
Ageouts The number of age-outs that occurred on a given port. An
age-out is the number of times the complete set of
information advertised by a particular MSAP has been
deleted because the information timeliness interval has
expired.
Input Frames Discarded The number of LLDP frames received by this LLDP agent
on the indicated port, and then discarded for any reason
Input Frames Errors The number of invalid LLDP frames received by this LLDP
agent on the indicated port, while this LLDP agent is
enabled
Input Frames Total The number of valid LLDP frames received by this LLDP
agent on the indicated port, while this LLDP agent is
enabled
Input TLVs Discarded The number of LLDP TLVs discarded for any reason by this
LLDP agent on the indicated port
Input TLVs Unrecognized The number of LLDP TLVs received on the selected port
that are not recognized by this LLDP agent
Output Frames Total A count of all LLDP frames sent on the indicated port
Output Length Errors The number of LLDPDU Length Errors recorded for the

indicated port
LLDP Local-info
Source MAC Address MAC address of the local port
System Name Name of the local system connected to this port, as
defined by the host name in the DNS settings. By default,
it is the unit's serial number.
System Description Description of the local system
Port ID Port identifier
Mgt Address # IP address for local system management (there may be
more than one)
If index # The interface index value used to identify the port
associated with this management IP address
TTL Time To Live (TTL) of the LLDPDU frames transmitted on
this port. This value is automatically set by the system to
[4 x Tx Rate + 1 second].
LLDP Local-info
Enable Enable or disable LLDP (Link Layer Discovery Protocol)
frame transmission on the selected port.
Rate The LLDP frame transmission rate, expressed in seconds,
on the selected port
Range: 1 to 3600

3.7 Managing Sessions

The units management system provides multiple configurable management sessions to
allow multiple users to control the unit. There is a writelock mechanism to avoid two
users writing to the unit at the same time.
To view current sessions, access the page System Session Management.
System Session Management
For more information on specific values, refer to the following table.

Current Sessions (System Session Management)
Session ID Session identification number
Type Interface the session is using
Host IP address of the management station for that session
Username The user account that is currently logged in. An asterisk (*)
appears beside your own session.
Uptime How long the session has been active
Writelock Indicates which session has the ability to make configuration
changes
Terminate Selecting one or more sessions then clicking Terminate forces a
log out

3.7.1 Terminating a User Session

It may be sometimes necessary to terminate one or more sessions.
Note: You need the right privileges to terminate a session. Refer to
"Managing Users and Privileges" on page 54.
To terminate a session, access the page System Session Management, select the
session you want to terminate by checking the Terminate check box and the Terminate
button. The session is immediately terminated and the current user is logged out.
3.7.2 Locking or Unlocking User Sessions

The administrators communicate with the equipment within a particular session. Users
open their own sessions to administer the equipment. Since the Web interface supports
concurrent sessions, to maintain the integrity of the configuration settings, only one user
at a time has the ability to make changes.
To lock a session for write access, access the page System Session Management and
click the Writelock button. Only you will have access to modify parameters of the unit.
The other users will only be able to view the units configuration.
To unlock a session for write access so other users can lock it, access the page System
Session Management and click the Writeunlock button. You will no longer be able to
modify parameters on the unit.
Writelock (System Session Management)
Writelock Locks your session so that only you have write access
Writeunlock Unlocks write access so that is available to other users
Note:You can also control the locking and unlocking of your session using
the Writelock button located at the upper-right corner of the Web
interface.

3.7.3 Configuring Session Options

Use this page to configure the following session-related parameters:
The maximum number of CLI sessions allowed
The maximum number of web interface sessions allowed
The maximum number total sessions (CLIand web combined)
The CLI timeout value
The web interface timeout value
Whether or not a telnet server is enabled
The authentication order when users log in to the system
To configure session parameters

1. Access the page System Session Configuration.
2. Update the various session configurations parameters, then click Apply.
System Session Configuration

Session Configuration (System Session Configuration)

General
Max CLI Sessions The maximum number of concurrent CLI sessions that can be
supported
Max WEB Session The maximum number of concurrent management tool
sessions that can be supported
Max Total Sessions The total number of CLI and WEB sessions that can be
supported
CLI Timeout The maximum number of seconds that a CLI session can remain
idle before it is automatically logged out
File Transfer Timeout The maximum number of seconds that must elapse before a file
transfer (firmware upgrade, history data file transfers, etc.) is
automatically terminated
Minimum value is 900 (15 minutes); maximum value is 3600 (60
minutes). Default value is 1800 (30 minutes).
WEB Timeout The maximum number of seconds that a management tool
session can remain idle before it is automatically logged out
Telnet Server The telnet server on the unit may be enabled or disabled
Authentication
Order The authentication method to use, in order of availability. The
available options are:
Local: Validate locally only.
Radius: Validate on the RADIUS server only.
Local-Radius: Validate locally first; if the validation does not

succeed, then validate on the RADIUS server.
Radius-Local: Validate on the RADIUS server first, and if the

validation does not succeed, then validate on local server.
Strict Radius-Local: Validate on the RADIUS server first. If

the authentication fails, access is denied. The fall back to
local only occurs when the RADIUS authentication times
out.
TACACS+:Validate on the TACACS+ server only.

Local-TACACS+:Validate locally first; if the validation does

not succeed, then validate on the TACACS+ server.
TACACS+-Local:Validate on the TACACS+ server first, and if

the validation does not succeed, then validate on the local
server.
Strict TACACS+-Local:Validate on the TACACS+ server(s)

first. If the authentication fails, access is denied. The fall
back to local only occurs when the TACACS+ authentication
process times out.

3.8 Managing Users and Privileges

With Vision EMS,you can configure each unit to be managed by several users, each with
different privileges. Privileges, also referred to as permissions, are used to grant precise
levels of access to different user groups. You may choose to limit certain users to only
specific configuration options, such as firmware updates, OAM, ports or traffic, while
others have full access to all features.
Note: You must define the permissions to assign to user groups before
defining the user accounts.
3.8.1 Setting Up the Administrator Account

One administrator account is created by default with username and password both set to
admin. The username and password are case-sensitive. It is recommended that you
change the default password immediately after installation to safeguard the system (refer
to "Changing Passwords" on page 59). The administrator account provides access to all
features.
Note: To prevent losing administrator access to the unit, you cannot
modify the administrator account privileges or delete the administrator
account.
CAUTION: If you, as the administrator, forget your username or

password the only way to regain access to the management Web
interface is to perform a factory reset. Refer to "Restoring Factory Default
Settings" on page 115.
3.8.2 Defining Permissions for a Group of Users

You must first define group permissions before you can assign users to groups.
To define permissions for a group of users

1. Access the page System Sessions Permissions.
2. Click Add or click the Group Name that you want to edit.
3. Select the Privileges to assign to the selected user group, then click Apply.
Note: You cannot change the privileges of user group Admin. This user
group has full access to all functions.

Group Privileges (System Session Permissions)

Group Name The name of the user permission group
Privileges The privileges given to the user permission group allow its
members to edit, add or enable within these sections.
The following commands can be used by all users regardless of
their privileges:
board
date
exit
help
ping
quit
sfp
syntax
tcp-connect
traceroute
version
ACL: Edit/Enable ACL settings.
Alarms: Edit/Add/Enable alarm reporting configurations.
All-add: Permission to add in all sections that are viewable
All-edit: Permission to edit in all sections that are viewable
All-enable: Permission to enable in all sections that are viewable
CFM: Edit/Add the SOAM CFM feature.
Config: Import/Export configuration files through CLI.
Filters: Edit/Add Layer-2 filters, IPv4 filters and VLAN:
filter
vid-set
Firmware: Upgrade the firmware.
History: Edit the history bucket statistics.

L2PT: Edit/Add L2 protocol tunneling rules.
Log: Edit syslog configuration and view logged entries.
Management: Edit/Add management access to the unit:
bridge
console
dns
interface
inventory
mode
motd
mtr
ntp
route
sfp
snmp
snmp-trap
OAM: Edit/Add/Enable OAM and loopback:
loopback
oam
PAA: Add/Edit/Enable the performance assurance agent
instances.
Policies: Edit/Add/Enable policies for filtering traffic.
Port: Edit/Add/Enable port configurations:
cable-test
media-selection
port
statistics

fault-propagation
Protection: Add/Edit/Enable protection:
LACP
ERP
RFC-2544: Add/Edit/Enable the RFC-2544 menu.
SAT-Protocol: Edit/Add/Enable Service Activation Testing
protocol.
SAT-Reporting: Edit/Enable Service Activation Testing reporting.
Service Availability: Add/Edit/Enable the service availability
instances.
Service Mapping: Add/Edit CoS profiles and bandwidth
regulator sets:
bandwidth-regulator
cos-profile
regulator-set
Sessions: Manage sessions and edit session configuration:
RADIUS
reboot
session
Traffic: Edit/Enable VLAN encapsulation settings:
forwarding
TWAMP: Edit/Enable TWAMP settings.
Users: Edit/Add and manage user accounts and permissions:
permission-group
user
Y.1564: Edit/Add/Enable Y.1564 test methodology.

3.8.3 Adding or Editing User Accounts

To add or edit a user account
1. Access the page System Sessions Users.
A list of all user accounts that exist for the unit is displayed.
2. Click Add or click a User Name if you want to edit a user account.
3. In the [User name] user settings page, complete the fields, then click Apply.
User Settings (System Session Users)
User Name The login name for the account
First Name The account holder's first name
Last Name The account holder's last name
Phone Number The account holder's phone number
Email Address / Email The account holder's email address
Password Enter the password for this account
Confirm Password Re-enter the password for this account
3.8.4 Administering User Account Privileges

You can grant different privileges or permissions to each user account, if you have already
defined both the user account and permission groups.
To give privileges to a user account

2. Click the user name that you want to edit.
3. In the [User Name] user settings page, click the Permission button.
The user's User Permission page is displayed. All available user permission groups are
listed.
Note:You can create more groups in the Session Permissions page.
4. Select the user groups that you want to assign to this user, then click Apply.

CAUTION: Modifying or reassigning the user groups for your account

may result in you being unable to perform some tasks.
3.8.5 Changing Passwords

To change a user's password
2. Click the user name that you want to edit.
3. Enter the user's new password in both the Password and Confirm Password fields,
then click Apply.
Note: If you forget your username or password, contact your
Administrator for a password reset.
For more information on specific parameters, refer to the table "User Settings (System
Session Users)" on page 58.

3.9 Using a RADIUS Server for Authentication

You can use a RADIUS server for authenticating users. When RADIUS authentication is
enabled, the unit supports Authentication and Authorization as configured on the
RADIUS server. A RADIUS server can be useful if you want to centrally manage user
accounts instead of managing them on each unit. The unit can be connected to up to two
RADIUS servers allowing for RADIUS server redundancy.
To configure session parameters

1. Access the page System Session RADIUS.
2. Enter the various RADIUS configuration parameters, then click Apply.

RADIUS Configuration (System Session RADIUS)
General
Authentication The authentication method to use. The only option available is:
Method PAP: Password Authentication Protocol
RADIUS Timeout How long the RADIUS server will wait before retrying the
connection. After the number of retries has been exhausted, a
connection to the next configured server will be attempted, in
which the same timeout and retry scheme apply.
RADIUS Retry The number of times to retry the server before trying the next
server configured
Realm The string to append to the user's name using the
username@realm method
Vendor-Specific Enable this box to include vendor-specific information as part of
attribute in Access- the RADIUSaccess request. Sending this information enables
Request the RADIUSserver to better identify the type of equipment
requesting access.
Server-1 / Server-2
Host The RADIUS server host-name or IPv4 address
Port The RADIUS server UDP port to which to connect
Secret The shared secret for this RADIUS server
Source Address The optional bind address for the RADIUS server

3.9.1 RADIUS Server Configuration Examples

The following examples are configurations for the RADIUS server, and not for the unit.
Two methods are supported by RADIUS servers for providing authorization using
standard RADIUS attributes:
Callback-Id (id=20): Provides a fine-grained permissions mechanism. The
permissions are the same as those that can be configured locally on the unit. The list
of tokens is separated by commas. They can be a mix of locally-defined user
permission groups and individual privileges. See also "Managing Users and
Privileges" on page 54.
Service-Type (id=6): Provides for full admin privileges if attribute is set to

"Administrative-User".
Notes: You cannot view RADIUS assigned permissions with the CLI or Web-
based interface. The permissions tokens are case sensitive.
The following are a few configuration examples for the RADIUS Server using these
attributes:
To assign a user to the built-in Admin group: Callback-Id = "Admin"
To grant a user full administration privileges (same as first example): Service-Type =

"Administrative-User"
To give a user a list of individual privileges: Callback-Id = "Config, Firmware, Log,

Management, Users"
If a user is authenticated by RADIUS but no attributes are specified in the server
configuration, the permissions will be set as follows:
Local permissions (i.e. as configured in the unit), if the username exists locally
Viewer-only permission, if the username does not exist locally

3.10 Using a TACACS+ Server for Authentication

You can use a TACACS+ server for authenticating users. When TACACS+ authentication is
enabled, the unit supports Authentication and Authorization as configured on the
TACACS+ server. A TACACS+ server can be useful if you want to centrally manage user
accounts instead of managing them on each unit individually. The unit can be configured
to connect to a second TACACS+ server, allowing for TACACS+ server redundancy.
To configure TACACS+session parameters

1. Access the page System Session TACACS+.

TACACS+ Configuration (System Session TACACS+)
General
Authentication The authentication method to be used by the TACACS+ server
Method The only option available is:
PAP : Password Authentication Protocol
TACACS+ Timeout The lapse of time that the TACACS+ client will wait before
retrying the connection, expressed in seconds
After the specified number of retries has been exhausted, a
connection to the next configured server will be attempted, for
which the same timeout and retry scheme apply.
TACACS+ Retry The number of times to retry the server before attempting to
connect to the next configured TACACS+ server
TACACS+ Service The name of the service to pass to TACACS+ for authorization
Name The default value is shell.
TACACS+ Privilege The attribute to extract from the authorization response in
Attribute order to determine the privilege level of the user requesting
authentication
The default value is priv-lvl.
Server-1 / Server-2
Host The TACACS+ server's host-name or IPV4 address
Note:to disable this server, enter 0.0.0.0 or :: as the address.

Port The TCP port on the TACACS+ server to which to connect
Secret The shared secret for this TACACS+ server
Source Address The optional bind address associated with this TACACS+ client
Note:This parameter is only used when the TACACS+ server
validates the address of the unit.
3.10.1 TACACS+ Server Configuration Examples

The following examples are configurations for the TACACS+ server, not for the unit. They
apply to a tac_plus server; configuration values may differ for other servers.
Logging in is a two-part process. First, the user is authenticated. Once authenticated, the
user may be authorized to gain rights on the system. The server should return AV
(attribute-value) pairs for the requested service name.
The first attribute, the privilege level (usually priv-lvl), is evaluated first. This attribute is a
numerical value that should be between 0 and 15. On this system, an attribute value of 15
grants Admin rights (All-show, All-Add, All-edit), and all other attribute values grant Viewer
rights (All-show). If the specified attribute value is not found, the login attempt is refused
because the AV pair was not supplied by the server.
The second attribute, the privilege list (accedian-priv-list), is subsequently evaluated. This
attribute is an optional attribute, and is ignored if the privilege level is already set to 15
(Admin). The purpose of this attribute is to provide a fine-grained permissions
mechanism. The permissions are the same as those that can be configured locally on the
unit. The list of tokens is separated by commas. The tokens you indicate can be a mix of
locally-defined user permission groups and individual privileges.
Note: You cannot view TACACS+ assigned permissions with the CLI or
Web-based interface.
Note:Permission tokens are case-sensitive.
Selected configuration examples for the TACACS+ Server using these attributes are given
below.

To assign a user to the built-in Admin group

user = tacadmin {
login = cleartext tacadmin
pap = cleartext tacadmin
name = "Test Admin"
# 'shell' service referred to as 'exec'
# in the config
service = exec {
priv-lvl = 15
}
}
To assign a user viewer-only privileges

user = tacviewer {
login = cleartext tacviewer
pap = cleartext tacviewer
name = "Test Tac Viewer"
# in the config
service = exec {
priv-lvl = 1
}
}
To assign a user a customized set of privileges

user = taccfm {
login = cleartext taccfm
pap = cleartext taccfm
name = "Test Tac User CFM"
# in the config
service = exec {
priv-lvl = 1
accedian-priv-list = CFM,PAA
}
}
If a user is authenticated by TACACS+, but no attributes are specified in the server

configuration, the permissions will be set as follows:
If the username exists locally:Local permissions, as configured on the unit
If the username does not exist locally:Viewer-only permissions

3.11 Managing Access Control Lists

You may use an Access Control List (ACL), which is a network access control mechanism,
to prevent or allow specific MAC or IP addresses to access the unit for management
purposes.
You can create up to 10 lists, and each list can contain up to 20 rules. Each rule allows or
blocks addresses. Rules are prioritized using the Priority field, with the rule configured
with the highest priority applied first.
It is recommended to set the priorities so the most restrictive rules are performed first.
For example, a high-priority rule could grant access to a specific IP address within a
subnet, and the next rule could deny access to the whole subnet, thus blocking all
remaining IP addresses from that subnet. Another example: First deny access to subnet
10.10.10.0/26, then allow access to subnet 10.10.0.0/16.
Note: Once all rules have executed, all remaining frames are dropped (this
is the default rule). You must therefore ensure the addresses you want to
allow are accepted by at least one rule of the ACL.
Once the ACL is created, you can then assign it to one or more interfaces. On each
interface you can also select the type of protocol (CLI [SSH and Telnet], WEB, SNMP) to
which the ACL applies. Refer to the section "Configuring the Logical Interfaces" on page
31.
CAUTION: If you assign a rule to an interface, you or another user may

lose access to the unit.
Note: Assigning an ACL to a subinterface that belongs to a bridge is not

supported. The ACL must be assigned to the bridge itself.
Note: You can assign an ACL to an interface that is active on an SFP port,
even when this SFP port is protected by a LAG port. However, you must
assign the ACL to the interface that is active on the LAG port protecting
the SFPs, and not to its members. For example, assign the ACL to the
interface active on LAG-1, but not to the interface active on the PORT-1 or
PORT-2.

3.11.1 Setting Up an ACL

To set up an ACL
1. Access the page System ACL.
A summary of all lists that have been configured is displayed. For more information
on specific parameters, refer to the table at the end of this procedure.
2. Click Add to add a new ACL, or click the Name of an existing ACL to edit its settings.

ACLDefinition Summary (System ACL)
Name The name of the ACLlist
State State of the list:
Assigned:The list is used by at least one interface.
Unassigned: The list is not currently used by an interface.
Interface List Names of the interfaces using this list

Clicking on an interface name will open the ACL statistics,
showing the number of packets hit, on a per-rule basis, for this
specific interface
ACL Definition
Type The type of ACLlist:
ipsrc: IPv4and IPv6 address values are filtered
macsrc:MAC address values are filtered
Value The source addresses (IP or MAC) to filter. IP addresses can be

entered using a subnet mask.
If the Type is ipsrc:
Unique IPv4 address (ex: 192.168.0.100)
Unique IPv6 address (ex: 2011:db8::1212)
IPv4 subnet (ex: 192.168.0.0/24)
IPv6 subnet (ex: 2011:db8:1212::/48)

Note:The IPv4 subnet limit is /32; the IPv6 subnet limit is/128.
If Type is macsrc:
Unique MAC address
Action The filter action to take:

Drop: This rule drops CPU-destined frames/packets coming
from the address specified in the field Value.
Accept: This rule accepts CPU-destined frames/packets

coming from the address specified in the Value field.
Note: Frames/packets that are dropped from a higher-priority
rule cannot be recovered with an Accept rule.
Name The name of the rule
Priority The priority of the rule
Range:1-255, with 1 being the highest priority
State Enable or disable the rule.
Packets The number of packets that have been intercepted by the rule;
If the Action is set to accept for this rule, the number of
packets accepted and sent to the CPU for processing.
If the Action is set to drop for this rule, the number of

packets dropped.
3.11.2 Deleting an ACL

To delete an ACL
2. Click the ACL Name to delete.
3. Click Delete.

3.11.3 Viewing ACL Statistics

To view ACL statistics for each interface
2. Click the name of the interface in the Interface List.

A count of Packets for each ACL rule defined is displayed. The Default Dropped
Packets statistic (i.e., associated with the default rule) is displayed at the top of the
page. For more information on specific parameters, refer to the table "ACLDefinition
Summary (System ACL)".
3. To clear the statistics, click the Clear button.
4. To update the statistics, click the Refresh button.

4 Configuring Plug & Go

4.1 Understanding Plug & Go 70
4.2 Configuring a Unit for Beacon 72
4.3 Configuring the Forwarding Settings of Intermediate Units 77
4.4 Managing Network Inventory 78

4.1 Understanding Plug & Go

Plug & Go enables you to quickly install a factory-reset Performance Element unit on
the network and remotely manage it without requiring further unit configuration. The
unit discovers and configures its own service ports, automatically configures its
management settings and then adds itself to a centralized inventory-tracking database
(the inventory-tracking unit). The purpose of the inventory-tracking unit is to view a
network inventory of all Accedian units that have advertisement settings enabled.
Plug & Go is supported on both Layer-2 and Layer-3 networks.
This section explains the general steps required to enable the automatic configuration of
factory-reset units on the network. These steps are as follows:
Enable the beaconer and set its ACP level.
Enable units in the path so that they will forward beacon and advertisement frames.
The required configuration will vary, depending on whether the intermediate units
are running firmware release 5.2 and higher or 5.1 and lower.
Configure an inventory-tracking unit.
4.1.1 Beacon and Advertisement Frames

Plug & Go uses multicast frames with the Accedian Ethertype (0x88fc), referred to as
beacon frames. You need to configure one unit to be the beaconer to send the
beacon frames to all remote units that are used by the auto interface for auto-
provisioning. You only need to configure one beaconer on your network.
The beacon frame needs to reach the final destination: the remote unit. The remote unit
responds by sending an advertisement a frame of the same type as the beacon
back to the beaconer. Both beacon frames and advertisement frames must be
transmitted in each direction. If there are any Accedian units in the path of the beacon on
its way to the remote unit, you must configure each unit to be able to forward beacon
and advertisement frames.

4.1.2 ACP Level

Complying with Service OAM standards, Plug & Go is based on a common multi-domain
network model. This model accommodates services delivered by multiple providers at
different levels. It is used to ensure that networks using ACP (Accedian Control Protocol)
are maintained within defined maintenance levels.
The ACP level is used in transmitting beacon and advertisement frames. A unit receiving a
beacon frame will automatically set its system ACP level to the one included in the beacon
frame.
The ACP level defines how far the ACP frames can go. A unit requires a higher level to be
able to transmit frames through a unit with a lower level. For example, a unit using ACP
frames level 3 will be able to reach another unit if each unit in between has an ACP frame
level of 2 or lower.

4.2 Configuring a Unit for Beacon

You can configure a logical interface to send beacon frames. A frame is sent by the central
unit (or another unit configured as the beaconer) to all remote units that are used by the
auto interface for auto-provisioning. This can be done at Layer2 or Layer3. Configure the
unit to send beacon frames at Layer2 if the remote units are within the same subnet.
Configure the unit to send beacon frames at Layer3 if the remote units are outside the
beaconer's subnet.
Only configure one unit on your network either the central unit or a separate beaconer
for sending beacon frames. Configure the auto interface of the remote units to listen
for beacon frames by modifying the Discovery Settings parameters.
"Managing the Unit"
"Managing Alarms and System Messages"
4.2.1 Setting Up a Beacon Instance at Layer2

When the beaconer is configured at Layer 2, a frame is sent by the beaconer unit to all
remote units that have the auto interface enabled for auto-provisioning.
Note: if the interface configured for beacon is part of a bridge, be sure to
disable the advertisement frame filtering on the Plug & Go Inventory
page if you want to be able to see the inventory of all units advertising on
this interface. Refer to "Managing Network Inventory" on page 78.
To configure a logical interface for sending beacon frames at Layer2

2. Click an Interface Name to edit it.
3. Complete the required fields in the Beacon Settings section, then click Apply.
For more information on specific parameters, refer to the table "Interface Settings
(System Configuration Interface)" on page 34.

4.2.2 Setting Up a Beacon Instance at Layer3

There are two ways to set up a beacon at Layer 3:
Use Interface Settings to specify the interface on which to send the beacons. This
method can be used, for example, when units to be configured with Plug & Go are on
the same subnet as the interface used to send the beacons (e.g. a network interface
with IP of 192.168.10.10/24 and units to be configured on the subnet
192.168.10.0/24).
Use DHCPRelay to send the beacons via a DHCPrelay (e.g. a router). This method
can be used when the units to be configured with Plug & Go are on other subnets (no
interface in the unit is in this subnet). If this method is used, the beacons will be sent
using the interface that has a predefined route leading to the DHCP Relay IP address.
If no predefined route leads to this IP address, the default gateway address is used. If
this method is used with the Use interface settings option, the beacon frames are
sent using this specific interface.
To set up a beacon instance for sending beacon frames at Layer 3

1. Access the page Plug & Go Layer-3.
2. Click Add to add a new Layer-3 Beaconer or click the Layer-3 Beaconer Name to edit
an existing beaconer.

Beacon Layer-3 Configuration (Plug & Go Layer-3)
Name A name to identify the Layer-3 beacon instance
State Enable or disable the transmission of beacon frames for this
instance.
Beacon Rate The interval at which the beacon frames will be sent:
3 seconds
1 minute
10 minutes
60 minutes
The default interval is 1 minute.

Transmission Settings
Destination IP When neither the Use Interface Settings nor the Use DHCP
Relay option is selected, the beacon frames are sent to the
address you specify here.
The value you enter is typically a directed-broadcast address
that enables all remote devices to receive the beacon frame.
When remote devices are not directly connected to the
beaconing device, all intermediate network devices (e.g.
routers) must be configured to allow directed-broadcast IP
addresses to pass through to the destination subnet.
Furthermore, it is up to the operator of the beaconing device to
locally configure the necessary route for the beacon frames to
be transmitted out from the appropriate physical port.
Use Interface Settings Enables or disables the use of a specific interface for sending the
beacon frames.
Interface Specify which interface to use for sending beacon frames by
making a selection in the drop-down list.
Note:Only available when Use Interface Settings is enabled.
Use DHCP Relay Enable or disable the use of a DHCPrelay (e.g. a router) for
sending the beacon frames.
Note: You can also enable the use of the interface settings if
you want to send the beacon from a specific interface.
DHCP Relay IP The IP address of the DHCP relay toward which beacon frames
are sent.
Note:Only available when Use DHCP Relay Only is enabled
and Use Interface Settings is disabled.
DHCP Relay The subnet of the DHCP relay interface that faces the client
Destination Subnet network
Beacon Settings
See the Domain ID and ID Matching parameters in the
Discovery Settings parameters.
IP Config Mode Indicates which IP configuration mode the receiver should use:

Auto: Instruct the remote device to compute an IP

address, given the subnet, gateway and mask.
Auto Static: Behavior is similar to that of Auto

configuration mode; however, in the case of a power reset,
this mode preserves the IP address, gateway and mask
values if an IP address (other than 0.0.0.0) is already
configured.
DHCP: Use DHCP to obtain an IP address for the AUTO

interface.
Advertisement IP Instructs the remote device to send Layer-3 advertisement

frames to this destination IP address
IPSubnet The IPsubnet used by the units receiving the beacon frames
Note:Only applies to the Auto and Auto-StaticIPconfig modes.
Mask The subnet mask used by the units receiving the beacon frames
Gateway The gateway used by the units receiving the beacon frames
IPExclusion List Indicate a list of IP addresses, if any, to be excluded from the
remote units
You can specify both single IP addresses and ranges of
addresses, each separated by commas. For example, a range of
172.16.1.2-172.16.1.5 spans four IPaddresses.
A total of 100 IP addresses can be specified here, including both
address ranges and single IPaddresses.
DHCP Host Name Possible values are:
Current hostname
Serial number
Custom hostname

Note:Only applies to the DHCPIPconfig mode.
Field to the right of Enter the DHCPhostname or serial number value here after
the DHCP Host Name making a selection in the DHCPHost Name drop-down list.
DHCP Client ID Possible values are:
Serial number
Custom client ID
Field to the right of Enter the DHCPclient's serial number or custom client IDvalue
the DHCP Client ID here after making a selection in the DHCPClient ID drop-down
list.
One-Shot Beacon When you press Send, the system sends a single beacon frame
with the information that has previously been configured and
applied. If changes to the beacon settings were made without
clicking Apply, they would not be effective in the beacon frame.
4.2.3 Deleting a Beacon Instance at Layer3

To delete a beacon instance at Layer 3
2. Select the beacon instance to delete by clicking its name in the list.
The Beacon Layer-3 configuration page opens.
3. Click Delete.
4.2.4 Modifying a Beacon Instance at Layer3

To modify a beacon instance at Layer 3
2. Select the beacon instance to modify by clicking its name in the list.
The Beacon Layer-3 configuration page opens.
3. Update the beacon's setting as required.
4. Click Apply to save your changes.

4.3 Configuring the Forwarding Settings of Intermediate Units

To configure the forwarding settings of each intermediate unit
2. Click the Auto interface to edit its settings.
3. In Forwarding Settings, set the level to All or to a value lower than the one set in the
beaconer. Doing so allows beacon and advertisement frames to pass through this
unit.
4. Set all other fields as required, then click Apply.

For more information on specific parameters, refer to the table "Interface Settings
(System Configuration Interface)" on page 34.

4.4 Managing Network Inventory
4.4.1 Viewing Network Inventory

You can view the network inventory of all Accedian units having advertisement settings
enabled (for more information about advertisement settings, refer to "Configuring the
Logical Interfaces" on page 31).
To view the network inventory

1. Access the page Plug & Go Inventory.
2. Click Enable Inventory Tracking, then click Apply.

Discovery Config and Inventory (Plug & Go Inventory)
Enable Inventory Enables the gathering of discovery inventory
Tracking A table of all units that have advertisement enabled to send an
information frame on the network is displayed.
Enable Filters advertisement frames based on the beacon configuration
Advertisement Frame state of the unit interfaces. The advertisement frames are
Filtering added to inventory only if they are received on a port that has
an interface with the beacon state enabled.
Note:If the interface configured for beacon is part of a bridge,
you must disable the advertisement frame in order to see the
inventory of all units advertising on this interface.
Inventory
Remote NID IP The IP address assigned to the remote unit
System Description The type of remote equipment, such as AMN-1000-GT
Serial Number The serial number assigned to the remote unit
FW Version The firmware version of the remote unit
Hostname The hostname of the remote unit
IP Interfaces The list of enabled IP interfaces configured on the remote
equipment
Domain ID The domain ID that was used in the discovery process to
configure this unit

Base MAC Address The MAC address associated with the unit, as displayed in the
Home tab
Interface MAC The MAC address of the remote unit port that sends
Address advertisement frames
Remote Port The name of the remote unit port that sends advertisement
frames
Local Port The name of the local unit port that receives advertisement
frames
SNMP Port The UDP port of the SNMP agent for the remote unit, if
configured
Web Server Port The remote unit Web port used
Config Status Indicates whether the remote unit is running with the Default
configuration or is User configured
Last Update Last time the information for this remote unit was updated
Unicast Beacon Configuration
IP Config Mode Tells the receiver the IP configuration mode that the receiver
should use:
Auto: Tell the remote device to compute an IP address,

given the subnet, gateway and mask.
Auto Static: Behaves like Auto, but in the case of a power

reset preserves the IP address, gateway and mask if an IP is
already configured (different from 0.0.0.0)
DHCP: Use DHCP to get an IP address for the AUTO

interface.
IP Subnet Subnet used by the receiver when Auto or Auto Static IP

config mode is selected
Mask Mask used by the remote device when Auto or Auto Static IP
config mode is selected
Gateway Gateway used by the remote device when Auto or Auto Static
IP config mode is selected

Beacon Type The only choice is Renew config. It renews the configuration of
all remote units that have the advertisement settings set to
enable.
Send Beacon When you press Send beacon, the system sends a single
beacon frame with the information that has previously been
configured.
You can also view more information on a specific unit by clicking on the link in the Serial
Number column.
For more information on specific parameters, refer to the table "Discovery Config and
Inventory (Plug & Go Inventory)" on page 78.
4.4.2 Logging In to a Remote Unit

You can connect and manage a remote unit by logging in to the Web server of the remote
unit.
To connect to the remote unit

2. Click the hyperlink in the Remote NID IP column.

The login page for the remote unit is displayed.
3. Enter your user name and password to start managing the remote unit.
For more information on specific parameters, refer to the table "Discovery Config and
Inventory (Plug & Go Inventory)" on page 78.

4.4.3 Sending a Beacon Frame

To send one beacon configuration frame to the remote units
2. Click Send Beacon.

For more information, refer to the table "Discovery Config and Inventory (Plug & Go
Inventory)" on page 78.
You can also configure a logical interface for beacon on the Interface Settings page. Refer
to "Configuring the Logical Interfaces" on page 31.

5 Configuring the Unit

5.1 Configuring General System Settings 84
5.2 Configuring IPv4 Settings 85
5.3 Setting Dry-Contact Inputs 86
5.4 Setting the System Date and Time 88
5.5 Setting Up SyncE 95
5.6 Viewing SyncE/ESMC Port Statistics 99
5.7 Setting Up DNS 103
5.8 Configuring Traffic 104
5.9 Upgrading the Firmware 106
5.10 Importing/Exporting the Units Configuration 110
5.11 Viewing CPU Usage 112
5.12 Rebooting the Unit 113
5.13 Restarting the Unit 114
5.14 Restoring Factory Default Settings 115

5.1 Configuring General System Settings

For more information on specific parameters, refer to the table "General System Settings
(System Configuration Mode)" on page 84.
5.1.1 Setting the S-VLAN Ethertype

The Ethertype that is associated with the Service VLAN (S-VLAN) is set globally for the unit.
Its value is set to 0x88A8 for the GT Performance Element.
5.1.2 Regulating Management Traffic

As with other traffic types, it can be useful to regulate management traffic.
To set up the management traffic regulation (MTR)

1. Access the page System Configuration Mode.
2. Enable the MTR State box.
3. Complete the other parameters, then click Apply.

General System Settings (System Configuration Mode)
S-VLAN Ethertype This affects all elements that make use of the S-VLAN Ethertype,
i.e. interfaces, filters, RFC-2544. This parameter is set to 0x88A8.
Management Traffic Regulation (MTR)

State Enable/Disable the regulation of management traffic.
Rate The average data rate, expressed in kbps
Latency The transmit queue size, expressed in milliseconds
Burst The maximum burst size, expressed in bytes

5.2 Configuring IPv4 Settings
5.2.1 Setting the IGMP Version

Internet Group Management Protocol (IGMP) is a Layer-3 communication protocol used
by networking equipment to more efficiently manage multicast traffic.
You must select the units IGMP version, which applies to all interfaces of the unit.
To set the unit's IGMP version

1. Access the page System IPv4.
2. Make a selection from the IGMPVersion drop-down list, then click Apply.
IPv4 Settings (System IPv4)
IGMP Version The IGMP version for the unit. This affects the IGMP
configuration of all interfaces on the unit.
System default
V2
V3
Note:It is recommended to select V3 unless you require V2 due
to compatibility issues.

5.3 Setting Dry-Contact Inputs

Units with the dry-contact hardware option enabled are equipped with two dry-contact
inputs, which enable you to monitor and report the status of external devices.
The reporting of the current state of each dry-contact input is given in the page System
Alarm Chassis.
Console Connector Pinout for Dry-Contact Inputs
Pin Signal
2 Not connected
3 Tx Data
4 Ground
5 Ground
6 Rx Data
7 Not connected
To set dry-contact inputs

1. Access the page System Configuration Dry-Contact.
2. Select Enable for each dry-contact input you wish to monitor.
3. Enter values for each of the parameters, then click Apply.

Dry-Contact Input Parameters (System Configuration Dry-Contact)
Enable Enable/Disable the use of the dry-contact input. When enabled,
the alarm point for this input is created and the input is
monitored.
Normal Input State Select the normal state of the input. An alarm will be raised
when the input state of the dry-contact is different from the
normal state for more than three consecutive samples.
Closed

Opened
Input Sampling The time, expressed in milliseconds, between two consecutive

Period readings of the input state
Range: 100 to 1000 milliseconds, expressed in steps of 100
milliseconds
Name The name to assign to the dry-contact input
Range: 1 to 127 characters; numbers and special characters are
supported

5.4 Setting the System Date and Time

Accurate, precise date and time value are important when managing and troubleshooting
a network. They allow, among other useful functions, time-stamping of alarms.
The system date and time can be set manually, or automatically controlled using either an
NTP server or a PTP server. A unit can also act as an NTP server if you select the NTP
Server Enable option.
Note: To avoid conflicts, only one NTP server can be used in a network.
Instructions for manually or automatically setting the date and time follow.
5.4.1 Setting Date and Time Manually

To set the date and time manually
1. Access the page System Configuration Time.
2. Specify the current date and time in the provided fields.
3. Select the Change to entered date and time if possible when applied box to allow a
single manual update to the system date and time.
Note:When you click Apply, this box is reset to the unselected state.
4. Click Apply.
For more information on specific parameters, refer to the table on page 90.
5.4.2 Setting Date and Time Automatically

To update the date and time automatically using Network Time Protocol
Note: You can enable up to two NTP servers for NTP synchronization.
2. Select the NTP Enable option.
3. Verify that the NTP server you want to use appears in the NTPService List.
If not, add a new server by specifying its name or IP address in the NTP Server box
then clicking Add.
4. Select a time server from the list, then click Apply.

To delete an NTP server

2. Select the NTPserver's line from the NTPService List by clicking its name or
IPaddress. Do not click the check box.
3. Click Delete.
To update the date and time automatically using a PTP server

Refer to IEEE Std. 1588-2008 for more information about the Precision Clock
Synchronization Protocol.
Note: You can enter up to two PTP servers for PTP synchronization.
Note:Communication with the grandmaster clock is only supported via
unicast negotiation (as defined in clause 16.1 of IEEE 1588-2008). Multicast
negotiation is not supported.
1. Access the page System Configuration Time
2. Select the PTP Enable option.
3. Verify whether the PTP server you want to use appears in the NTPService List. If not,
add a new server by specifying its name or IP address in the PTP Server box and its
domain number in the Domain Number box then clicking Add.
4. If needed, check the UTC Offset for Master Enable box to get the UTC offset from
the master clock, set the Unicast Negotiation parametersand then click Apply.
To delete a PTP server

2. Select the PTPserver's line from the PTPService List by clicking its name or
IPaddress. Do not click the check box.
3. Click Delete.
Setting the System Date and Time Automatically using a GPS

To automatically set the system date and time using a GPS
2. Ensure your unit supports the GPS feature, then select GPS Enable and click Apply.
Note: If you enable the GPS without having it locked to a GPS signal (GPS
fix) and attempt to use the unit as an NTP server, the unit will set the LI bit
in the NTP packet identifying the NTP clock as "not synchronized".

Setting Time Zones and Daylight Saving Time

The unit also provides for time zones and daylight saving time. For a list of time zones and
rules for daylight saving time, refer to: http://www.worldtimezone.com/.
To set the time zone and the daylight saving function

2. Select Daylight Saving Time Enable.

For more information, refer to the following table.
Date and Time Parameters (System Configuration Time)
Set Time, NTP and PTP
NTP Enable Sets the system time automatically by polling an NTP server.
Select a server from the list or add your own.
PTP Enable Sets the system time automatically by polling a PTP server. The
unit uses the servers from the list according to the Precision
Clock Synchronization Protocol.
NTP Server Enable Starts the NTP server service. The unit becomes an NTP server
and can be used by other units as the NTP server.
TAI Offset The offset to add to UTC time to convert to Temps Atomique
International (TAI) atomic international time
In early 1972, TAI was exactly 10 seconds ahead of UTC. From
1972 until June 30, 2012, 25 leap seconds were added to the
difference. Since the last second was added on June 30, 2012,
TAI has been exactly 35 seconds ahead of UTC.

Synchronization The status of the synchronization.
Status Note:This parameter is only available for PTP or NTP servers.
Date and Time If you are not using NTP, PTP or a GPS, the date and time can be
set manually by entering values here.
Select the Change to entered date and time if possible when
applied box to allow a single manual update to the system date
and time. When you click Apply, this box is reset to the
unselected state.
You cannot manually change the system date and time if the
GPS enable box is selected because the GPS will override any
manual updates.
If you have the NTP Server Enable box selected, and you
manually update the system date and time, your changes will
be pushed to all client devices immediately.
High-Resolution Sync Uses high-resolution hardware synchronization. In this mode,
the NTP server is queried multiple times and the resulting time
is derived from an averaging process based on a hardware
clock. If unchecked, the NTP server is queried only every
30minutes and the system time is set accordingly, without
further processing.
NTP Server List One or two NTP servers can be enabled simultaneously. The
unit will automatically update its date and time from one of the
enabled NTP servers. If the NTP server being checked is down,
the unit will then try the other enabled NTP server.
NTP Server When using NTP, the name or the IP address of the NTP server
to add
Time Interval When using NTP, the interval of time after which the unit
synchronizes with the NTP server. Expressed in seconds.
Number of Messages When using NTP, the number of synchronization messages
exchanged with the NTPserver during each time interval
DSCP When using NTP, the priority can be set in the Differentiated
Services Code Point.
VLAN Priority When using NTP, the priority of the VLANframes can be set in
the VLAN priority bits if the link is through a VLAN.
PTPServer List When using PTP, the unit will automatically update its date and
time from the one or two PTP servers on this list.

PTPServer When using PTP, the name or the IP address of the PTP server
to add
Note: A maximum of two PTP servers can be configured.
Domain Number When using PTP, the domain number of the PTPserver to add
UTC Offset for Master When using PTP, enable the use of UTC offset from the master
Enable clock.
Announce Interval When using PTP, the announce interval for unicast negotiation.
The interval, expressed in seconds, is the base 2 logarithm of
the Announce Interval. For example, if -1 is selected, the
announce interval is 0.5 seconds.
Possible values are:
-3: 125 milliseconds
0: 1 second
1: 2 seconds
2: 4 seconds
3: 8 seconds
Sync Interval When using PTP, the synchronization interval for unicast
negotiation. The interval, expressed in seconds, is the base 2
logarithm of the Sync Interval. For example, if -3 is selected, the
announce interval is 0.125 seconds.
-4: 62.5 milliseconds
0: 1 second
1: 2 seconds
2: 4 seconds

3: 8 seconds
Set GPS
GPS Enable Use the GPS receiver to set the system time automatically.
Satellite SNR The Signal-to-Noise ratio, expressed in dB Hz, of each satellite
in view
GPS Fix Shows whether the GPS receiver is locked to a GPS signal
Latitude / Longitude The current location of the unit, according to its GPS receiver
Set Time Zone
UTC Offset The offset from Coordinated Universal Time:
North America has negative values.
Eastern Europe has positive values.

Range: -12 to +14
Daylight Saving Use daylight saving time (DST).
Enable Note:syslog and other services that timestamp events with the
current time and date are affected during DST transitions. As
such, you may observe 60-minute gaps or duplicate time
stamps around the time when the clock was changed.
Daylight Saving The time adjustment to apply to the GMT offset during the
Offset daylight saving period
This value is typically one hour.
DST Start and DST The period during which daylight saving time is in effect
End DST start and end times are defined using values for the month,
week, day, hour and minute.
Note:To specify the last day of the month, enter "week=5".
Examples of Setting the System Time

Setting the System Time for Montreal, Canada
Parameter Value
UTC Offset -5
DST Enable Check
DST Offset 1

Parameter Value
DST Start Month=March, Week=2, Day=Sunday, Hour=2, Min=0
DST End Month=November, Week=1, Day=Sunday, Hour=2, Min=0
Setting the System Time for Wellington, New Zealand

Parameter Value
UTC Offset 12
DST Enable Check
DST Offset 1
DST Start Month=September, Week=5, Day=Sunday, Hour=2, Min=0
DST End Month=April, Week=1, Day=Sunday, Hour=3, Min=0

5.5 Setting Up SyncE

If your equipment has this optional hardware feature, you can use the synchronous
Ethernet (SyncE) feature to synchronize the unit and all its outputs over Ethernet
networks. SyncE takes the clock signal from the selected clock reference port and
transmits it to all other ports. You also have the option to define a Secondary Clock
Source on another physical port.
Note: When the SyncE option is enabled, the Ethernet Synchronous
Message Channel (ESMC) may be used to receive and transmit clock
signals via a Quality Link (QL).
To set up SyncE
1. Access the page Port SyncE.
2. Select Enable SyncE.

SyncE/ESMC Parameters (Port SyncE)
Enable SyncE Enables or disables the synchronous Ethernet feature.
When disabled, all ports on the system operate as clock
master. When enabled, the clock reference port(s) operate
as clock slave(s) and all the other ports on the system
operate as masters, transmitting the clock signal from the
clock reference port.
When enabled, clock status information is also displayed.
Options
Primary Clock Source The port from which the Primary Reference Clock is recovered
Secondary Clock The port from which the Secondary Reference Clock is
Source recovered.
This is parameter optional and may be set to none if only a
single reference clock is preferred.
Revertive Enables or disables the revertive clock selection feature.
When enabled, the clock selector is allowed to switch back
to a higher-priority clock source that previously failed,

when it become available again.
When disabled, the clock selector is allowed to revert to a

lower priority clock source, but only if the currently-
selected source becomes unavailable. In this mode, the
selector cannot revert to a clock that previously failed
unless ESMC QL mode is enabled.
Wait-to-Restore The system will wait for this many seconds before reverting to a
Delay (sec) clock available after a failure.
Note: This feature only applies when ESMC QL Mode is
enabled.
Manual Clock Source This sets the clock selector to use a specific clock source,
regardless of priority.
Note: The system will not switch to an invalid clock and it will
not switch to a clock of inferior quality (if ESMC QL mode is
enabled). If none is specified, the clock source is selected
automatically.
ESMC QL Mode Enable or disable the ESMC QL mode. ESMC QL messages
containing clock quality information can be sent and received
only if this is enabled. If enabled, clock quality information can
then be used to automatically select the best clock reference
available.
ESMC Forward ESMC messages may contain type-length-values (TLV) other
extended TLV than the mandatory QL TLV. These are referred to as extended
TLVs. Their content is not used in the system. When enabled,
extended TLVs will be forwarded from incoming SyncE ports to
all outgoing SyncE ports; otherwise, they are stripped out.
Note:This feature only applies when ESMC QL Mode is
enabled.
Status
Clock Selector The clock source that is currently in use by the SyncE hardware.
Primary: The primary reference clock is in use.
Secondary: The secondary reference clock is in use.
FreeRun: The selected reference clocks are no longer

available and the system is in free-running mode, using a
frequency based on the computed average of the last

known good reference clock.
Local: The local oscillator is in use. This should only happen

when SyncE is disabled.
Primary Clock Status The current status of the primary reference clock
Secondary Clock The current status of the secondary reference clock
Status
Clock Selection The number of times the clock reference was changed.
Change Count
Current QL State The current QL status
Note:This feature is not available if ESMC QL Mode is disabled.
Previous QL State The previous QL status with the time elapsed in seconds (with
millisecond resolution) since the change occurred
Note:This feature is not available if ESMC QL Mode is disabled.
Previous Clock The previous clock selector with the time elapsed in seconds
Selector (with millisecond resolution) since the change occurred
Port Statistics Summary (only available if ESMC QL mode is enabled)
Status The following colors indicate SyncE port status:
Green: The port is up and running.
Blue: The port is enabled and a signal is detected.
Red: The port is enabled but the physical link is down and
no signal is detected.
Yellow: The port is not totally functional.
Gray: The port is disabled.
Port Name The name that identifies the port. A link can be clicked to access
detailed SyncE/ESMC port statistics. For the case where no link
is available, it means the port has an SFP module with an
unsupported SyncE device (copper type SFP).
Tx QL Last transmitted clock QL on the port
Rx QL Last received clock QL on the port
QL State Current QL receive status used for selection process if the port is
a reference clock

Note: The QL-FAILED state indicates that the port is in a failed
condition.
State Duration Time elapsed in seconds since QL state was last changed

5.6 Viewing SyncE/ESMC Port Statistics

You can view a summary and/or detailed SyncE/ESMC port statistics for each port.
To view a summary of SyncE/ESMC statistics for all ports

1. Access the page Port SyncE.
2. To view the detailed SyncE/ESMC port statistics, select a port name.

SyncE/ESMC Port Statistics (Port SyncE)
Current QL to Clock The current QL used for the clock selection process with the
Selection Process time elapsed in seconds (with millisecond resolution) since the
last change occurred
Last QL Received Indicates the last QL received on the port with the time elapsed
in seconds (with millisecond resolution) since it was last received
Last QL Sent Indicates the last QL sent to the port with the time elapsed in
seconds (with millisecond resolution) since it was last sent
Wait-to-restore Indicates the remaining wait-to-restore period, expressed in
Remaining seconds
Minimum QL Indicates the minimum time between any two consecutively-
Received Inter-Arrival received QL for ESMC PDU of type informational
Time
Maximum QL Indicates the maximum time between any two consecutively-
Time
Averaged QL Indicates the averaged time between any two consecutively-
Time
Count of ESMC PDU Indicates the number of ESMC PDU that have been received
Received
Count of ESMC PDU Indicates the number of ESMC PDU Malformed that have been
Malformed Received received
of Type Event with the type event (event flag set to 1)
Received

Received with Valid with valid QL and extended TLVs
QL and Extended
TLVs
Received with QL- with the Quality Level STU/UNK:
STU/UNK
(Option 2) QL-STU: Synchronized Traceability unknown
(Option 3) QL-UNK: This synchronization trail transports a

timing quality generated by an unknown clock source. It is
at least of quality SSU.
Received with QL-PRS with the Quality Level PRS:
(Option 1) QL-PRS: Primary reference source traceable
[ITU-T G.811]
Received with QL-PRC with the Quality Level PRC:
(Option 1) QL-PRC: This synchronization trail transports a
timing quality generated by a primary reference clock that
is defined in [ITU-T G.811].
Received with QL- with Quality Level Invalid Code 3
INV3
Received with QL- with the Quality Level SSU-A/TNC:
SSU-A/TNC
(Option 1) QL-SSU-A: This synchronization trail transports
a timing quality generated by a type I or V slave clock that is
defined in [ITU-T G.812].
(Option 2) QL-TNC: Traceable to transit node clock ([ITU-T

G.812], type V)
INV5
Count of ESMC PDU Indicates the number of ESMC PDU received with Quality Level
Received with QL- Invalid Code 6
INV6

Received with QL-ST2 with the Quality Level ST2:
(Option 2) QL-ST2: Traceable to stratum 2 (ITU-T G.812],
type V)
Received with QL- with the Quality Level SSU-B:
SSU-B
(Option 1) QL-SSU-B: This synchronization trail transports
a timing quality generated by a type VI slave clock that is
defined in [ITU-T G.812].
INV9
Received with QL- with the Quality Level EEC2/ST3:
EEC2/ST3
(G.8264) QL-EEC2: Synchronous Ethernet equipment clock
option 2. This clock option is treated like an ITU-T G.812
type IV clock [i.e., QL-SEC and QL-ST3, respectively]).
(Option 2) QL-ST3: Traceable to stratum 3 ([ITU-T G.812],

type IV)
Received with QL- with the Quality Level EEC1/SEC:
EEC1/SEC
(G.8264) QL-EEC2: Synchronous Ethernet equipment clock
option 1 (is treated as a ITU-T G.813 option 1)
(Option 3) QL-SEC: This synchronization trail transports a

timing quality generated by a synchronous equipment
clock (SEC) that is defined in [ITU-T G.813] or [ITU-T G.8262],
option I.
Received with QL- with the Quality Level SMC:
SMC
(Option 2) QL-SMC: Traceable to SONET clock self-timed
([ITU-T G.813] or [ITU-T G.8262], option II)
Received with QL- with the Quality Level ST3E:.
ST3E
(Option 2) QL-ST3E: Traceable to stratum 3 ([ITU-T G.812],

type IV)
Received with QL- with the Quality Level PROV:
PROV
(Option 2) QL-PROV: Provisionable by the network
operator
Received with QL- with the Quality Level DNU-DUS:
DNU-DUS
(Option 1) QL-DNU: This signal should not be used for
synchronization.
(Option 2) QL-DUS: This signal should not be used for

synchronization.
Count of ESMC PDU Indicates the number of ESMC PDU that have been sent
Sent
Count of ESMC PDU Indicates the number of ESMC PDU that have been sent with
of Type Event Sent the type event (event flag set to 1)
Count of ESMC PDU Indicates the number of ESMC PDU that have been sent with
Sent with Extended extended TLV forwarded
TLVs
Count of ESMC Indicates the number of times an ESMC failure was detected (no
Failure Detection QL for five-second timeout)
Count of Signal Indicates the number of times a signal failure was detected
Failure Detection

5.7 Setting Up DNS

You can use the DHCP to automatically configure the units IP parameters. When the unit
uses DHCP, it can be configured to use the DNS settings from the DHCP. If the unit does
not use DHCP, you can manually specify the address for each DNS server. Two DNS
servers can be used for redundancy.
To use DHCP to specify the address of DNS servers

2. Enable the Use DHCP Results box.
3. Use From Interface to select the interface from which to obtain DHCP information.
For more information on specific parameters, refer to the table "DNS Parameters (System
Configuration DNS)" on page 26.
To manually specify the address of DNS servers

2. Remove the check mark from the Use DHCP results box.
3. Manually specify the address of DNS server 1 and DNS server 2 (if required),
4. Specify the Domain, then click Apply.

For more information on specific parameters, refer to the table "DNS Parameters (System
Configuration DNS)" on page 26.

5.8 Configuring Traffic
5.8.1 Setting the Working Rate

You must select the layer (Layer1 or Layer2) used by the unit to determine the rate for
the traffic generators, traffic regulators and traffic shapers. For example, if you setup a
traffic regulator with a CIR of 20,000 kbps, you want to tell the unit which bytes are used
in the calculation of the CIR: Layer-1 bytes or Layer-2 bytes. The working rate options are:
Layer-1: Layer-1 Ethernet frames contain all Ethernet frame fields plus the Inter-
Frame Gap (IFG), Preamble and Start-Frame Delimiter (SFD).
Layer-2: Layer-2 Ethernet frames contain all Ethernet frame fields. This does not
include the Inter-Frame Gap (IFG), Preamble and Start-Frame Delimiter (SFD).
Note: Exercise caution when setting up the working rate. You should
ensure that you set the different working rates to the same layer when
they work together in a particular setup. For example, when using a traffic
generator with an in-service flow type, you must ensure the Regulator
working rate and the Generator working rate are both set to the same
layer (Layer1 or Layer2) in order to have accurate tests.
To set the working rate

1. Access the page Traffic Configuration.
2. Select the working rate to be applied to all entities, then click Apply.
For more information on specific parameters, refer to the table in "Selecting VLAN or
VLAN-in-VLAN Filtering" on page 104.
5.8.2 Selecting VLAN or VLAN-in-VLAN Filtering

You must select to filter on either the inner or the outer VLAN for each policy list when
using traffic policies with VLAN sets. When filtering on the inner VLAN, the outer VLAN is
ignored.
To select the VLAN filtering option

2. Select the VLAN on which you want to filter for each policy list, then click Apply.

Traffic Configuration (Traffic Configuration)

VLAN Level Settings
Traffic-1 Select a policy list to inspect the inner or the outer VLAN.
Traffic-2 Default: Outer
Traffic-3
Traffic-4
Rate Settings
Generator Working The layer used by the unit to determine the working rate:
Rate
Layer-1:Layer-1 Ethernet frames contain all Ethernet frame
Regulator Working fields plus the Inter-Frame Gap (IFG), Preamble and Start-
Rate Frame Delimiter (SFD).
Shaper Working Rate
Layer-2:Layer-2 Ethernet frames contain all Ethernet frame
fields. This does not include the Inter-Frame Gap (IFG),
Preamble and Start-Frame Delimiter (SFD).

5.9 Upgrading the Firmware

New firmware versions typically provide:
Additional functionality
Enhancements to the existing feature set
Defect corrections
To verify the current software version, see the Current version field of the Firmware
Maintenance section in the System Maintenance Firmware page.
You can upgrade the unit's firmware by downloading the firmware directly from your
computer or network. If using the Command Line Interface (CLI), you can also upgrade
the unit's firmware via an SFTP, HTTP, FTP or SCP server for a file transfer.
There are two ways to upgrade a unit's firmware:
One-step firmware upgrade: Use this method when you want the upgrade to take
effect immediately.
Two-step firmware upgrade: Use this method when you to want to download the
firmware file now, then activate it on the unit at a later time (such as during an
upcoming maintenance window).
Note: If you download a firmware file as part of a two-step firmware
upgrade, it will overwrite the rollback firmware file in the One-Step tab (if
any) that is currently stored on the unit. You cannot concurrently store
both a rollback firmware file and a pending two-step upgrade download
on the unit.
To perform a one-step firmware upgrade

1. Access the page System Maintenance Firmware.
The Firmware Maintenance window is displayed; the One-Step tab is visible by
default.
2. Click the Browse button next to the New firmware field.
3. In the dialog box that appears, select the firmware file from your computer or
network, then click Open.
Note: The firmware is distributed in a binary file with the filename
extension .afl.

4. Click the Upgrade button.

The firmware begins loading. Once it has finished, the unit restarts to activate the new
firmware.
To verify that the upgrade was successful, access the page Home and examine value
of the Firmware version field.
To perform a two-step firmware upgrade

Note:It is possible in most cases to perform a two-step firmware
downgrade to a firmware version earlier than 6.4.2. You must, however,
perform a factory reset of the unit first. For details, see "Restoring Factory
Default Settings" on page 115. If a firmware downgrade fails using the
two-step procedure, repeat the downgrade as a one-step procedure.
default.
2. Click the Two-Step tab.
The screen refreshes to display the tab contents.
3. Click the Browse button next to the New firmware field.
4. In the dialog box that appears, select the firmware file on your computer
or network, then click Open.
Note: The firmware is distributed in a binary file with the filename
extension .afl.
5. Click the Download button.
The firmware is loaded onto the unit, pending activation as described below. The
Rollback Version field in the One-Step tab is updated to "No rollback available".
To activate the downloaded firmware file

default.
3. Ensure that the version number displayed next to the Downloaded version is the
correct version to activate on the unit.
4. Click the Activate button.

The unit restarts to activate the new firmware. You are not prompted to confirm your
actions.

To verify that the upgrade was successful, access the page Home and examine value
of the Firmware version field.
To delete the downloaded firmware file

Note:This feature is provided for your convenience only; deleting a
downloaded firmware file once it has been applied is optional.
Furthermore, downloading a new firmware file will automatically
overwrite the existing file (if any) on the unit.
default.
3. Click the Clear Download button.
The firmware file is permanently removed from the unit. You are not prompted to
confirm your actions. The value of the Downloaded version is updated to None.
To revert to the previous firmware version

default.
2. Ensure that the version number displayed next to the Rollback version is the correct
version to which to revert.
3. Click Rollback.
Firmware Parameters (System Maintenance Firmware)
Firmware Maintenance, One-Step Tab
Current Version The current version of the firmware
New Firmware The firmware version that is applied when you click Upgrade
Browse Button Click to navigate to the firmware file to which you want to
upgrade the unit
Rollback Version The previous firmware version to which you can revert
Rollback Button Click to revert the unit's firmware to the version indicated in
Rollback Version

Reboot Button Click to reboot the unit and activate the new configuration
Firmware Maintenance, Two-Step Tab
Current Version The current version of the firmware
New Firmware The firmware version that is downloaded when you click
Download
Browse Button Click to navigate to the firmware file to which you want to
upgrade the unit
Download Button Click to begin downloading the selected firmware file
Downloaded Version The firmware file that has been previously downloaded on this
unit
Activate Button Click to upgrade the unit's firmware to the version indicated in
Downloaded version
Clear Download Click to remove the previously-downloaded firmware file from
Button the unit
CAUTION: Reverting to an older firmware version is advisable ONLY

through the Rollback feature. With Rollback, compatible configuration
settings are loaded with the previous firmware. A simple firmware
downgrade is NOT advisable because the older firmware may not match
the existing (newer) configuration. Attempting a firmware downgrade
using the Upgrade button may corrupt the configuration.
If you need to downgrade to a previous firmware version, a factory default reset is the
mandatory first step.
To reset the unit to factory values while performing a firmware downgrade

default.
2. Click the Factory Default button.
3. Click the Browse button next to the New firmware field and select the new firmware
file.
4. Click the Upgrade button.

The unit will restart with a factory default configuration after downgrading the
firmware.

5.10 Importing/Exporting the Units Configuration

If you need multiple units in your network to have the same configuration, you can
configure your first unit and then export these configuration values to a file. You will then
be able to import this configuration file into other units to configure them in the same
way. You can export and import configuration files either directly from your computer or
network, or using an SFTP, HTTP, FTP or SCP server for a file transfer.
CAUTION: When using the import/export function, be careful with the

DNS settings. The IP connectivity to each unit might be at risk if you are
using a static IP address configuration in the Management interface. The
use of DHCP is therefore recommended when importing a configuration to
multiple units.
Each configuration file provides an identifier to help prevent importing a wrong file.
CAUTION: Although you can edit a configuration file, you risk corrupting
its data! The file is in a UNIX text format, and should not be opened with a
Windows text editor such as Notepad.
CAUTION: After making configuration changes, it is recommended to wait

at least 30 seconds before exporting the configuration file. This ensures
that the latest changes have been written to the file, and that it is ready
to be exported.
To export a configuration file

2. Enter a configuration filename or enter the URL of the SFTP server plus the
configuration file name (e.g. sftp://username:password@domain.com/config) in the
Config Export Filename text box.
3. Click Export.
For more information on the other parameters, refer to the following table.
To import a configuration file

2. Click the Factory Default button.

Note:This step is optional if you are importing a configuration file of the
same version as the currently running firmware. If you are importing a
configuration from an older firmware version, you must reset the current
configuration (factory default) before importing the older version.

3. Click the Browse button next to the Config Import File field.
4. Select the firmware file on your computer or network, or enter the URL of the SFTP
server plus configuration file name (e.g.
sftp://username:password@domain.com/config), then click OK.
5. Click the Import button.
6. Once the file is uploaded, click Reboot to activate the new configuration.
Configuration Import/Export Parameters (System Maintenance Firmware)
Config Import File After you click Browse and navigate to a new configuration file
to import, its name appears here.
Config Export Enter a configuration file name here, then click Export to export
Filename the current configuration for later use.
Factory Default Click to apply the factory default settings to this unit.
Button
Cancel Changes The factory default and rollback actions require a system
Button reboot. You can cancel these actions if needed simply by clicking
Cancel Changes.
Rollback Button Click to revert the unit's configuration to the version from the
last time it rebooted.

5.11 Viewing CPU Usage

Viewing CPU usage can be useful when managing the unit.
CPU usage has no impact on customer traffic. However, intense PAA processing or a large
number of SNMP get operations could increase CPU usage.
To view the units CPU usage

1. Access the page Show CPU Usage.
2. (Optional) Select the Poll Every Seconds box and enter the number of seconds
between each time the data is automatically refreshed.
3. Refresh the CPU usage data by clicking the Refresh button.

CPU Usage (Show CPU Usage)
Poll Every n Seconds Enter a number representing the frequency with which the CPU
usage data will be refreshed.
Current The CPU usage over the last second
15 Seconds Average The CPU usage average from the last completed 15-second
period
period
period
5 Minutes Average The CPU usage average from the last completed five-minute
period
CPU Usage History The CPU usage from the last 100seconds, presented as a graph

5.12 Rebooting the Unit

Rebooting the unit is required in order to apply certain types of modifications made to
the unit's configuration. You must also reboot after importing new configuration values.
For details, refer to "Importing/Exporting the Units Configuration" on page 110.
CAUTION: Rebooting a unit is disruptive. It applies changes in the units

configuration and affects current operations.
To reboot the unit

2. Click the Reboot button.

5.13 Restarting the Unit

CAUTION: Restarting a unit may affect current operations.
To restart the unit, press then immediately release the RST button on the front panel of
the unit.
CAUTION: Pressing the RST button for 5 seconds or longer resets the unit
to the factory default values.

5.14 Restoring Factory Default Settings

You can reset the unit to its factory default settings either by using the button on the
front panel of the unit or by using the management Web interface. Each way is described
below.
Note: Only complete a HARD RESET when the management Web
interface is not responding properly.
CAUTION: Resetting to factory default settings affects current operations.
To reset the unit to factory default settings via the Web interface
2. Click the Factory default button.
3. Click the Reboot button.
To reset the unit to factory default settings from the units front panel
1. Press and hold the RST button on the front panel.
2. Keep holding the RST button until the LEDs for Minor, Major, Critical and Power
flash at the same time.
3. Release the RST button.

6 Managing Ports
This chapter describes how to manage the ports, which are physical interfaces on the
unit; it contains the following sections:
6.1 Setting Up Ports 118
6.2 Setting Up Fault Propagation 126
6.3 Network Requirements TCP/UDP Ports 127
6.4 Viewing Port Statistics 130
6.5 Setting Up Port PHY Parameters 138
6.6 Viewing SFP Information 141
6.7 Testing a Cable 145

6.1 Setting Up Ports

You can configure the parameters for each port on the unit to manage options such as
protection (when available), link speed (auto-negotiation) and flow control.
The GT Performance Element is available in two models with the following physical traffic
ports:
Connector Configuration
Model Name and Connector Type
Port Name
GT GT-S
PORT-1 SFP-1 SFP-1
PORT-2 SFP-2 SFP-2
PORT-3 RJ45-3 SFP-3
PORT-4 RJ45-4 SFP-4
See "Setting Up Traffic Policies" on page 188 for a listing of all incoming-to-outgoing port
mapping combinations available on the GT Performance Element.
In addition to its physical ports, the unit also provides two LAG ports for protecting the
physical ports. Each LAG port protects SFP/RJ45 ports in the following way:
LAG-1 protects PORT-1 and PORT-2. Traffic is mapped to Traffic-1.
LAG-2 protects PORT-3 and PORT-4. Traffic is mapped to Traffic-3.
To view or configure port settings

1. Access the page Port Configuration.
A list of all ports and their current status is displayed.
Note: The information displayed will vary, depending on the model you
are using (the GT or GT-S Performance Element).
2. To update a port's settings, click its name under the Port Name heading.
The Port Configuration page is displayed.
3. Enter values in the required fields, then click Apply.
CAUTION: If you set the Port MTU to a value smaller than 1518 bytes on a
port used for management, you or another user may lose access to the
management Web interface.

Port Configuration (Port Configuration)
Status The following colors in the summary page indicate the port
status:
Green: The port is up and running
Blue: The port is enabled and a signal is detected
Red: The port is enabled, but the physical link is down and
no signal is detected
Yellow: The port is not totally functional
Gray: The port is disabled
Port State The port may be either enabled or disabled.

Enable
Port Name The name that identifies the port
Name By default, ports are named as follows: PORT-1, PORT-2,
PORT-3, PORT-4, Management, LAG-1 and LAG-2.
Alias The port's assigned alias name, as specified by a network
manager
Port MTU The maximum transmission unit that a port can receive and
forward, including all headers. Expressed in bytes.
When a LAG port is enabled, the physical ports enslaved by the
LAG port must have the same MTU settings to ensure error-free
transmission.
Supported values: 64 to 10240
Default value: 2000
Note: Setting the MTU to a value smaller than 1518 bytes on a
port used for management may cause a loss of access to the
unit.
Large Packet Packets above this threshold will be classified as Large Packets.
Threshold The Large Packets count can be viewed on the Port Statistics
page.
MAC Address The MAC address of the port
Connector The type of physical connector associated with the port:SFP,
RJ45 or Management

Enable Fault Enables the propagation of link faults (or LACP status) between
Propagation the ports specified in the field Propagate Fault on Port
Fault Propagation One-Way Link: Propagate faults in one direction based on the
Mode link status (or LACP) of the opposite port.
One-Way EVC: Propagate faults in one direction based on the
link status (or LACP) of the opposite port or based on the EVC
status.
Propagate From Port The port for fault propagation may be one of the following:
PORT-1 or PORT-2: The unit propagates the fault from any
port other than itself, or from the LAG-2 port.
PORT-3 or PORT-4: The unit propagates the fault from any

port other than itself, or from the LAG-1 port.
LAG-1: The unit propagates the fault from PORT-3, PORT-4

or LAG-2.
LAG-2: The unit propagates the fault from PORT-1, PORT-2

or LAG-1.
Note:In the case of a LAG, you must first enable the Fault
Propagation box, then click Apply. The Propagate From Port
drop-down list will then be displayed.
Media Dependent Auto MDI means that the unit automatically adapts the
Interface configuration of the connector to the cabling plant and type of
link partner.
(Copper ports only) If Auto MDI is not in use, you can manually define port settings
as follows:
MDI: Typical setting for an Ethernet station. Link partner
must be set to MDIX or a cross-over cable must be used.
MDIX: Typical setting for an Ethernet switch. Link partner

must be set to MDI or a cross-over cable must be used.
Speed Sets the port speed and duplex type

Link Speed Auto-Negotiation: The unit automatically negotiates port speed
and duplex type with the device to which it is connected. For
auto-negotiation to be successful, the other device must also be
set up for auto-negotiation.
If Auto-Negotiation is not in use, you can manually define port
speed:

10Mbps
100Mbps
1Gbps
If Auto-Negotiation is not in use, you can manually define
duplex type:
Half-Duplex: Transmission in one direction at a time
Full-Duplex: Transmission in both directions at the same

time
Note: Unsupported options, if any, are disabled.
In 1G mode, auto-negotiation may be selected (advertises 1000
Mbps, full-duplex only).
Note: Auto-negotiation is mandatory for 1000BASE-T.
Note: If you are using a LAG port with the protection mode set
to link status, you must enable auto-negotiation on the
physical port associated with the LAG port, for example, enable
auto-negotiation on PORT-1.
PHYMode Enable this box to improve link stability for SFP fiber ports, in
1000BASE-X mode in the presence of long transmission delays.
The Force TX On feature maintains the SFP's laser active on the
transmit side, which allows both ends of the communication
path to keep their link status in a stable state.
Note:See "Using the Force TX On Parameter" below for
guidelines and limitations on how to implement this
parameter.
Link Loss Return (LLR) This option determines how the unit notifies its link partner
when a valid receive signal is absent on the link.
(SFP fiber ports only) If LLR is disabled, then:

For 1000BASE-X links, a Remote Fault Indicator (RFI) using
auto-negotiation advertisement is sent to the link partner.
For 100BASE-FX links, the Far End Fault Indication (FEFI)

idle pattern is sent to the link partner.
If LLR is enabled, the unit turns off its transmitter for the lapse
of time defined in the LLR Period, after which it is re-enabled.
This cycle is repeated until the link is re-established.
Entering a value of 0 puts the laser into a disabled state waiting

for the opposite side to send a light pulse to re-establish the
link. Consequently, a value of 0 should not be configured on
both sides, otherwise the link will never be re-established.
Internal Loopback Click this box to enable or disable the internal loopback mode.
Enable Enabling the system loopback mode redirects the transmitted
frames to the receive path.
Protection Enable Enable protection for this port. The protecting port is reserved
by the protection mechanism and cannot be used for
monitoring purposes as long as the protection is enabled.
Note:This parameter is only available on LAG ports. When
using Fault propagation with LAG port protection, you must
enable the protection on both LAG ports for the fault
propagation to work correctly.
Protection Mode Switching protection to a standby port can be based on link
status, LACP status or ERP status.
If you select LACP status, you must create an L2PT rule with an
operation mode of Peer and protocol LACP on this port in order
to terminate LACP frames.
Note:Only one LAG port can be configured in ERPstatus
protection mode.
If you select LACP status, you must also set up LAG protection in
the page Protection LACP Configuration.
If you select link status for a LAG port, you must enable auto-
negotiation on the physical port associated with the LAG port,
e.g. enable auto-negotiation on PORT-1.
If you select ERP status, you must also set up ERP protection in
the page Protection ERP Configuration.
Note:This parameter is only available on LAG ports.
Working Connector The working physical port for the specified LAG port. Choosing
the port allows you to perform a manual switchover operation.
Note:This parameter is only available on LAG ports with the
Protection Mode set to link status or LACP status.
Revertive When enabled, the traffic is switched back to the main port
after the reversion period has expired.
Note:This parameter is only available on LAG ports with
protection mode set to link status or LACP status.
Revertive Period The time, expressed in seconds, that the system must
continuously detect a valid signal on the main port in order to

switch back to this port
Note:The timer is restarted if a signal loss is detected during
this period.
Note:This parameter is only available on LAG ports with
protection mode set to Link Status or LACP Status.
Link Time Out The time, expressed in seconds, to wait for the link to come up
after switching to the standby port. If the timer expires and the
link stays down, the system switches back to the working port.
Note:This parameter applies to only link status and is available
only on LAG ports.
Version The G.8032 protocol version used. Supported options are:
1: ERP version 1. Only one instance of ERPis supported per
LAG port.
2: ERP version 2. Multiple instances of ERPcan be set up

per LAG port.
Note:It is recommended to always use ERPversion 2, unless
the unit needs to interoperate with another unit that only
supports version 1.
Note:This parameter only applies to ERP status and is only
available on LAG ports.
Flow Control Supported options are:
Disable: Pause frames are disabled.
Local: Pause frames are processed locally.

Note: This parameter is not available on LAG ports.
LLDP Enable Enable or disable LLDP (Link Layer Discovery Protocol) frame
transmission on the port.
Note: This parameter is not available on LAG ports.
Rate The LLDP frame transmission rate on the port, expressed in
seconds
Range: 1 to 3600
Note:This parameter is not available on LAG ports.
TTL The Time To Live (TTL) of the LLDPDU frames transmitted on the
port. This value is automatically set by the system to [4 x Tx Rate
+ 1 second].
Note:This parameter is not available on LAG ports.

Current Status The current link speed and duplex type when Auto-Negotiation
Enable is selected:
Current Connector Configuration: If the link partner is also
using Auto MDI, the resulting connector configuration is
correct but random. A cross-over cable present on the
cabling plant results in both partners using the same
connector configuration.
Mastership Mode: On 1-Gbps copper ports, this reports

the clock mastership mode. In auto mode, the clock master
is determined by the auto-negotiation process. In forced
mode, usually when using SyncE, the clock is forced into
slave if the port is a clock reference for the system,
otherwise it is master.
6.1.1 Using the Force TX On Parameter

The Force TXOn feature (see the PHYMode parameter in the table above) is a port setting
that improves link stability for SFP fiber ports subjected to long transmission delays while
in 1000BASE-X mode. By keeping the laser active on the transmit side, both ends of the
communication path are better able to maintain their link status in a stable state.
The Force TXOn feature is supported on ports 1-4, as well as ports 9-12.
The following guidelines and limitations must be considered when implementing Force
TXOn.
Port Auto-Negotiation
Because Force TXOn applies to the PHY layer, port auto-negotiation must be disabled for
this feature to be effective.
Port Protection (LAG)

A port with the Force TX On feature enabled can be part of a LAG.
Do not use the Link Status to control the LAG protection, however, because part of the
Link Status mechanism involves manipulating the auto-negotiation setting of the
underlying ports (which interferes with the Force TX On setting).
The unit's Web management interface does not prevent you from controling the LAG
protection via the Link Status, and no alarm will be generated. The level of protection
achieved by this configuration will be unreliable.
Instead, it is recommended to use LACP to control the LAG protection, since LACP does
not interfere with the Force TX On mechanism. When setting up LAG protection using a
port with Force TX On enabled, configure the port with Force TX On before setting up the
LAG protection as a way of ensuring that auto-negotiation will be disabled for the port.

Note: These considerations also apply to LAG protection when used as

part of ERP protection.
Changing Media Types

The Force TX On feature is ignored when enabled in the event that a copper SFP is
inserted in a port designated as a 1-Gbps optical port with the Force TXOn feature
enabled.

6.2 Setting Up Fault Propagation

You can set up the unit to propagate a fault detected on one port to another port, such
as from PORT-1 to PORT-3.
Fault propagation can be used to propagate one of the following:
Link status only
EVC status (link status is included)

If you are using link status, only a link that is down on one port can bring the other port
down.
If you are using EVC status, the status of PAA probe(s) and/or CFM MEP(s) are
propagated to the other port. For more information on PAA and CFM MEP, refer to the
chapter See "Monitoring Network Performance with Service OAM" on page 245.
At least one PAA probe or CFM MEP should be free of connectivity errors in order to
enable fault propagation on EVC status to the specified port. If there is no PAA probe and
no CFM MEP set up in EVC fault propagation mode for the specified port, the port
selected for fault propagation will remain down.
Note: When using Fault propagation with LAG port protection, you must
enable the protection on both LAG ports for the fault propagation to work
correctly.
To set up port fault propagation

2. Click the Port Name to edit its settings.
3. Define port parameters as required by your setup, then click Apply.

For more information on specific parameters, refer to the table See "Port Configuration
(Port Configuration)" on page 119.

6.3 Network Requirements TCP/UDP Ports

Accedians demarcation devices, including the GT Performance Element, rely on a large
number of Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) ports
in order to support their various features and protocols.
The following table lists the TCP and UDP ports used by Accedian demarcation devices.
This information will prove useful when configuring firewalls on a network.
TCP/UDPPort Usage by Accedian Devices
Dest. Service
Protocol Applications Direction
Port Name
TCP 443 HTTPS Web Interface User station to Device
TCP 22 SSH Command Line Interface User station to Device
(CLI)
TCP 23 Telnet Command Line Interface User station to Device
(CLI)
UDP 161 SNMP SNMP Polling Server to Device
TCP 49 TACACS+ User authentication and Device to Server
authorization
TCP 14040 Vision Performance Counters Device to Server
Collect Transmission
UDP 162 SNMP SNMP Trap Sending Device to Server
UDP 1812 RADIUS User authentication and Device to Server
authorization
UDP 514 Syslog Remote Syslog Device to Server
UDP 123 NTP Network Time Protocol Device to Server
Synchronization
UDP 320 PTP Precision Time Protocol Device to Server
Synchronization
TCP 21 FTP File Transfers: Device to Server; Server
to Device
Configuration exports
Configuration imports
Firmware upgrades

Dest. Service
Port Name
SAT reporting
RFC-2544 report
uploads
History file transfers
UDP 69 TFTP File Transfers: Device to Server

Firmware upgrades
SAT reporting
RFC-2544 report
uploads
TCP 990 FTPS File Transfers: Device to Server

Firmware upgrades
TCP 22 SCP File Transfers: Device to Server

Firmware upgrades
TCP 22 SFTP File Transfers: Device to Server

Firmware upgrades
SAT reporting
RFC-2544 report

Dest. Service
Port Name
uploads
TCP 80 HTTP File Transfers: Device to Server

Firmware upgrades
History file transfer
UDP 6000 TWAMP Two-Way Active Device to Server

(see Measurement Protocol
note)
UDP 8000 SAT Y.1564 One-Way Test Device to Device
(see Communication
note)
UDP 9000 SAT Y.1564 One-Way Test Traffic Device to Device
(see
note)
UDP, TCP 53 DNS Domain Name System Device to Server
UDP 67 DHCP Automatic IP Assignment Device to Server
UDP 68 DHCP Automatic IP Assignment Device to Server
UDP 67 Plug & Go Layer-3 Beacon Device to Device
UDP 68 Plug & Go Layer-3 Beacon Device to Device
UDP 9065 Plug & Go Layer-3 Advertisement Device to Device
Note:The indicated destination port is the default value; you can

configure this value as needed.

6.4 Viewing Port Statistics

You can view a summary and a detailed port statistics for each port. The ports statistics
are sampled once per second.
Note: Bandwidth utilization Statistics are provided for physical ports only
(i.e., traffic and Management), not for Monitor ports or LAG ports.
To view a summary of statistics for all ports

1. Access the page Port Statistics.
To view the detailed port statistics

1. Access the page Port Statistics.
2. Select a port name by clicking it.

The <port name> Port Statistics page appears. Transmit and Receive statistics for the
selected port are displayed.
3. (Optional) Select the Poll Every Seconds box and enter the number of seconds
between each time the data is automatically refreshed. You can also refresh the port
statistics by clicking the Refresh button.
Port Statistics (Port Statistics)
Summary Page
Port Name Ports for which statistics are displayed
Txm Packets The count of the total number (i.e., both good and bad) of
frames/packets transmitted by the port. Bad frames include
normal collisions, late collisions and FIFO underflows.
Txm Errors Number of transmission errors
Rcv Packets The count of the total number (i.e., both good and bad) of
frames/packets received by the port. Bad frames include short
frames (less than 64 bytes), long frames (greater than the port's
configured MTU), frames with bad CRC, frames with PHY errors
and frames with receive FIFO errors.
Rcv Errors Number of errors received

Transmit Statistics
Bytes Good The count of the total number of bytes transmitted by the port
in good frames. The count includes the four CRC bytes but does
not include the preamble or SFD bytes. A good frame is one that
has been transmitted successfully (not aborted) with a valid
CRC.
It is assumed that all transmitted frames are properly sized:
from 64bytes (after any padding) up to the maximum size.
Bytes Total The count of the total number (i.e., both good and bad) of
frames/packets transmitted by the port. Bad frames include
normal collisions, late collisions and FIFO underflows.
Unicast Packets The count of the good (i.e., not dropped and having a valid CRC)
unicast frames transmitted by this port
Unicast frames are identified by having a 0 in the least significant
bit of the first byte of the destination address (i.e. the first bit
transmitted is a 0).
Multicast Packets The count of the good (i.e., not dropped and having a valid CRC)
multicast frames transmitted by this port
Multicast frames are identified by having a 1 in the least
significant bit of the first byte of the destination address (i.e. the
first bit transmitted is a 1).
Broadcast frames are not included in this count.
Broadcast Packets The count of the good (i.e., not dropped and having a valid CRC)
broadcast frames transmitted by this port
Broadcast frames are identified by a destination address of all
1s.
Pause Frames The count of the good (i.e., not dropped and having a valid CRC)
flow control pause frames transmitted by this port
Flow control pause frames are identified by a type of 88-08 and
an OpCode field of 00-01.
Tagged Frames The count of the good (i.e., not dropped and having a valid CRC)
VLAN frames transmitted by this port
VLAN frames are identified by a type field equal to 8100h, 88A8h
or 9100h, set in the outer VLAN tag.
CRC Errors The count of the transmitted frames with an invalid non-
appended CRC field. This count does not include frames with an
invalid CRC resulting from a FIFO underflow.

Deferred The count of the number of frames that were deferred on the
first transmit attempt due to the medium being busy. Frames
with subsequent deferrals (for instance, after a collision back
off) are not counted. Whether or not the frame is eventually
transmitted successfully is irrelevant to this counter.
Frames dropped due to excess deferral during the initial
transmit attempt are not counted.
Excessive Deferrals The count of the number of frames dropped by this port due to
excessive deferral. The deferral time starts at the beginning of
each transmission attempt and ends when the transmission
starts (regardless of collisions).
The deferral is excessive if more than 3036byte times have
passed without the transmission starting.
Single Collisions The count of the number of times a frame is successfully
transmitted from this port after experiencing a single collision
This count does not include erroneous (dropped) frames.
Multiple Collisions The count of the number of times a frame is successfully
transmitted from this port after experiencing multiple collisions
This count does not include erroneous (dropped) frames or
frames dropped due to excess collisions.
Excessive Collisions The count of the number of frames dropped by this port due to
excess collisions (number of collisions equals MaxRetry+1)
This count does not include frames dropped due to FIFO
underflow or late collisions (even if the late collision is also an
excessive collision).
Late Collisions The count of the number of frames dropped by this port due to
late collisions. A late collision is a impact that occurs after the
collision window delay (typically 512-bit times). The collision
window time is measured from the rising edge of TX_EN to COL
asserted at the MII interface.
Note:This value count does not include frames dropped due to
FIFO underflow. Late collisions are not retried.
Normal Collisions The count of the total number of normal collisions that have
occurred on this port during all transmission attempts. FIFO
underflows, late collisions and collisions that occur while this
port is not attempting to transmit are not counted.
This count does not include collisions during half-duplex back
pressure.

FIFO Errors The count of the number of packets dropped by this port due
to an underflow in the transmit FIFO. When an underflow is
detected, transmission is immediately aborted after sending a
known invalid (inverted) CRC sequence.
The FIFO underflow error takes precedence over all other errors
if this counter is incremented; consequently, none of the other
frame type counters is incremented.
Packets 64 The total number of frames, good or bad, transmitted by this
port that were exactly 64 bytes in length (excluding the
preamble and SFD, but including the CRC)
Packets 65127 The total number of frames, good or bad, transmitted by this
Packets 128255 port, that were of the length listed in the parameter column
Packets 256511 This frame length value excludes the preamble and SFD but
includes the CRC.
Packets 512 1023
Note:Frames with a length of 1024 and above are only
Packets 10241518 available on certain types of units.
Packets 15192047
Packets 20484095
Packets 40968191
Packets 8192 and up
Large Packets The total number of large frames transmitted by this port. You
can define the size of large frames via the Large Packet
Threshold parameter of the Port Configuration [port
name] page.
L1 Bandwidth The bandwidth currently used for the transmission of outgoing
Utilization (%) traffic on the selected port, expressed as a percentage of the
line rate
Note: Bandwidth utilization statistics are provided with one-
second granularity for both Layer-1 and Layer-2; however, the
value expressed as a percentage of the line rate is available for
Layer-1 only.
Note: Statistics will be accurate to 1% at data rates above 100
Mbps.
L1 Rate (Mbps) The rate at which outgoing traffic is currently circulating at
Layer-1 for the selected port, expressed in Mbps
L2 Rate (Mbps) The rate at which outgoing traffic is currently circulating at

Receive Statistics
Bytes Good The count of the total number of bytes received by the port in
good frames. The count includes the four CRC bytes but does
not include the preamble or SFD bytes.
A good frame is a well-formed normally-sized frame (64 to MTU
configured on the port) with good CRC and no PHY or FIFO
errors. Octets in otherwise good frames with a dribble nibble
are included in this count.
Bytes Total The count of the total number (i.e., both good and bad) of
frames/packets received by the port. Bad frames include short
frames (less than 64 bytes), long frames (greater than the port's
configured MTU), frames with bad CRC, frames with PHY errors
and frames with receive FIFO errors.
Short OK The count of error-free frames shorter than 64 bytes that are
received on this port
A frame is considered error-free if it has a valid CRC, no PHY
errors and no FIFO errors.
Short Bad The count of frames received on this port that are shorter than
64bytes and have an invalid CRC. Frames with PHY or FIFO
errors are not counted
Long OK The count of error-free frames received that are longer than
MTU configured on the port
A frame is considered error-free if it has a valid CRC, no PHY
errors and no FIFO errors.
Long Bad The count of frames received that are longer than MTU
configured on the port and have an invalid CRC. Frames with
PHY or FIFO errors are not counted.
Unicast Packets The count of the good unicast frames received by this port. A
good unicast frame is a normally-sized frame (64 to MTU
configured on the port) that is not dropped and has a good
CRC.
Unicast frames are identified by having a 0 in the least significant
bit of the first byte of the destination address (i.e. the first bit
received is a 0).
Multicast Packets The count of the good multicast frames received by this port. A
good multicast frame is a normally-sized frame (64 to MTU
CRC.

Multicast frames are identified by having a 1 in the least
significant bit of the first byte of the destination address (i.e. the
first bit received is a 1). Broadcast frames are not included in this
count.
Broadcast Packets The count of the good broadcast frames received by this port. A
good broadcast frame is a normal-sized frame (64 to MTU
CRC. Broadcast frames are identified by a destination address of
all 1s.
Pause Frames The count of the good flow control pause frames received by
this port (good CRC, no PHY or FIFO errors, normal size). Flow
control pause frames are identified by a type of 88-08 and an
OpCode field of 00-01.
Tagged Frames The count of the good VLAN frames received by this port (good
CRC, no PHY or FIFO errors, normally sized)
VLAN frames are identified by a type field equal to 8100h set in
the outer VLAN tag.
CRC Errors The count of normally-sized frames (64 to MTU configured on
the port) received by this port with a CRC error but not a
dribbling nibble (frame length is an integral number of bytes)
Frames with FIFO or PHY errors are not counted.
Align Errors The count of normally-sized frames (64 to MTU configured on
the port) received by this port with a CRC error and a dribbling
nibble (frame length is not an integral number of bytes)
Frames with PHY or FIFO errors are not counted.
Runt Frames The count of the number of receive frames (or events) detected
by this port without SFD detection but with carrier assertion.
Frames with valid SFD but no data bytes are also counted as
runts.
After detecting a runt frame, the update of the RxRunts counter
is suspended until the next valid frame is received. If multiple
runt frames occur between valid frames, the RxRunts counter is
incremented only once.
Length Errors The count of the number of good frames received by this port
with an error in the length field
A length error occurs when the value in the length field is within
the valid range for data length (461500 bytes) but does not
match the actual data length of the frame.

Field lengths less than 46 bytes (smaller than the minimum legal
frame size of 64 bytes) are not checked, due to padding.
False CRS The count of the number of received frames (or events)
detected by this port with a false carrier (SSD1 not followed by
SSD2)
After detecting a false carrier, updating the RxFalseCRS counter
is suspended until the next valid frame is received. If multiple
false carrier events occur between valid frames, the RxFalseCRS
counter is incremented only once.
PHY Errors The count of the number of frames received by this port with
RX_ER asserted during reception (while RX_DV is asserted)
Frames with a FIFO error are not counted.
FIFO Errors The count of the number of received frames dropped or
aborted due to receiving a FIFO overflow
The FIFO overflow error takes precedence over all other errors:
if this counter is incremented, then none of the other frame
counters is incremented.
Ignored The count of the number of received frames that have been
ignored by this port
A frame is ignored if it violates the programmed preamble rules
or if it violates the minimum data gap. The preamble rules
include long preamble enforcement (greater than 23nibbles)
and pure preamble enforcement (only 55h bytes).
The minimum data gap is the time between frame data
transfers and is measured from immediately after the last CRC
byte of the previous frame to the SFD field of the current frame.
The normal data gap is 20bytes long (12bytes of IFG and
8bytes of preamble/SFD). The enforcement limit is set to
10bytes (half the normal gap length).
Bad OpCode The count of the good control frames received by this port
(good CRC, no PHY or FIFO errors, normally sized) with an
unknown OpCode
Unknown control frames are identified by a type field of 88-08
and an OpCode field not equal to 00-01.
Packets 64 The total number of frames, good or bad, received by this port,
that were exactly 64bytes in length (excluding preamble and
SFD but including CRC)
Packets 65127 The total number of frames, good or bad, received by this port,

Packets 128255 that were 65 to 127bytes (or the other length) in length
Packets 256511 inclusive (excluding the preamble and SFD, but including the
CRC)
Packets 5121023
Frames 1024 and higher are available on only certain types of
Packets 10241518 units.
Packets 15192047
Packets 20484095
Packets 40968191
Packets 8192 and up
Large Packets The total number of large frames received by this port
The size of large packets is defined in the Port Configuration
[port name] page.
L1 Bandwidth The bandwidth currently used for the reception of incoming
Utilization (%) traffic on the selected port, expressed as a percentage of the
line rate
Note: Bandwidth utilization statistics are provided with one-
second granularity for both Layer-1 and Layer-2; however, the
value expressed as a percentage of the line rate is available for
Layer-1 only.
Note: Statistics will be accurate to 1% at data rates above 100
Mbps.
L1 Rate (Mbps) The rate at which incoming traffic is currently circulating at
L2 Rate (Mbps) The rate at which incoming traffic is currently circulating at

6.5 Setting Up Port PHY Parameters

You can view both SFP and copper ports and can set up PHY parameters for each copper
port. The PHY parameters are used to set the abilities that are advertised to the link
partner.
To view PHY parameters, access the page Port PHY. A list of PHY configuration and
status for all ports is displayed. For more information on specific parameters, refer to the
following table.
Port Configuration (Port PHY)
Status Port status may be one of the following:
Green: The port is up and running.
Blue: The port is enabled and a signal is detected.
Red: The port is enabled but the physical link is down and
no signal is detected.
Yellow: The port is not totally functional.
Gray: The port is disabled.
Connector The physical connector the port is using

Port Name The logical name assigned to the port
Auto-Nego Indicates whether the auto-negotiation feature is enabled or
disabled
If enabled, the unit automatically negotiates port speed and
duplex type with the device to which it is connected. For auto-
negotiation to be successful, the device and its partner must
both be configured to support auto-negotiation (Port
Configuration).
State The current auto-negotiation state of the port
To set up a ports PHY parameters

1. Access the page Port PHY.
A list of PHY configuration and status for all copper ports is displayed.
2. Click the Port name to edit its settings.
Note: You can only set up port PHY for the Management and RJ45 ports.

3. Define port PHY parameters as required by your setup, then click Apply.
PHY Configuration (Port PHY [Port name])
Advertisement The abilities that are advertised to the link partner
Configuration Possible options include:
10Mbps Half
100Mbps Half
1Gbps Half
10Gbps Half
10Mbps Full
100Mbps Full
1Gbps Full
10Gbps Full
Pause Symmetric (can receive and transmit pause frames )
Pause Asymmetric (can either receive or transmit pause

frames)
Link Partner Ability The abilities of the link partner
Possible options include:
10Mbps Half
100Mbps Half
1Gbps Half
10Gbps Half
10Mbps Full
100Mbps Full
1Gbps Full
10Gbps Full

Pause Symmetric (can receive and transmit pause frames)
Pause Asymmetric (can either receive or transmit pause

frames)
State The state field corresponds to ifMauAutoNegConfig and
ifMauAutoNegRemoteSignaling from RFC3636.
The state disabled indicates that auto-negotiation is not
supported by the media or is disabled by the configuration.
Other
Configuring
Complete
Disabled
Parallel Detect Fail

Each of the above values may be configured With Auto or
Without Auto.

6.6 Viewing SFP Information

Use this page to view both summary and detailed information about all currently-
detected SFPs.
To view a summary of all SFPs

1. Access the page Port SFP.
Summary information for all SFPs currently detected by the unit is displayed.
To view detailed information for all SFPs

1. Access the page Port SFP.
Summary information for all SFPs currently detected by the unit is displayed.
2. In the Connector column of the table, click the SFP for which you want to view
detailed information.
The details pertaining to the selected SFP are displayed.
For more information on specific parameters, refer to the following tables.
SFP Information (Port SFP)
Present Green: the SFP is present.
Red: the SFP is not present.
Part Number The manufacturers part number or product name
Serial Number The manufacturers serial number for the transceiver
Wavelength The nominal transmitter wavelength at room temperature,
expressed in nanometers
Speed The speed supported by the SFP, such as 1 Gbps
SFP Information
Connector Type The external cable connector provided as the media interface
Vendor The manufacturer name
This is a 16-character field that contains ASCII characters padded
on the right with ASCII spaces (20h).
Wave Length Indicates the nominal transmitter wavelength at room
temperature, expressed in nanometers

Part Number The manufacturer part number or product name
This is a 16-byte field that contains ASCII characters padded on
the right with ASCII spaces (20h).
Serial Number The manufacturer serial number for the transceiver
Revision The manufacturers product revision
SFP Present Indicates the presence of a recognized SFP
Diagnostics Supported or unsupported
A value of supported indicates that diagnostic information is
provided in the SFP memory section.
Calibration Internal: The values are calibrated to absolute measurements,
which should be interpreted according to the Internal
Calibration convention.
External: The values are A/D counts, which are converted into
real units according to the External Calibration convention.
Thresholds Indicates whether alarm and warning thresholds are supported
Speed The speed supported by the SFP, such as 1 Gbps
Monitoring Information
Temperature Transceiver temperature, measured internally
Temperature accuracy is manufacturer-specific, but must be
better than 3degrees Celsius for the specified operating
temperature and voltage.
Laser Bias Current Coupled TX output power, measured internally
Accuracy is manufacturer-specific but must be better than 3dB
for the specified operating temperature and voltage. Data is
assumed to be based on measurement of a laser monitor
photodiode current. Data is not valid when the transmitter is
disabled.
Transmit Power Coupled TX output power, measured internally
Accuracy is manufacturer-specific but must be better than 3dB
for the specified operating temperature and voltage. Data is
assumed to be based on measurement of a laser monitor

photodiode current. Data is not valid when the transmitter is
disabled.
Receive Power Received optical power, measured internally
Accuracy depends on the exact optical wavelength. For the
manufacturers specified wavelength, accuracy should be better
than 3dB for the specified temperature and voltage.
This accuracy should be maintained for input power levels up to
the lesser of maximum transmitted or maximum received
optical power per the appropriate standard. It should be
maintained down to the minimum transmitted power minus
cable plant loss (insertion loss or passive loss) per the
appropriate standard. Accuracy beyond this minimum required
received input optical power range is manufacturer specific.
Supply Voltage Transceiver supply voltage, measured internally
Note: Transmitter supply voltage and receiver supply voltage
are isolated in some transceivers. In that case, only one supply
is monitored. Refer to the device specifications for details.
SFP Thresholds (Port SFP [connector])

SFP Thresholds
Temperature High Alarm: High-temperature alarm for the transceiver
Low Alarm: Low-temperature alarm for the transceiver
High Warning: High-temperature warning for the transceiver
Low Warning: Low-temperature warning for the transceiver
Vcc High Alarm:High-supply voltage alarm for the transceiver
Low Alarm: Low-supply voltage alarm for the transceiver
High Warning: High-supply voltage warning for the transceiver
Low Warning: Low-supply voltage warning for the transceiver
Laser Bias Current High Alarm: High-laser bias current alarm for the TX (micro-
Amps)
Low Alarm: Low-laser bias current alarm for the TX
(micro-Amps)
High Warning: High-laser bias current warning for the TX (micro-
Amps)

Low Warning: Low-laser bias current warning for the TX (micro-
Amps)
Tx Power High Alarm: High-output power alarm for the TX
(~ -40 to +8.2 dBm)
Low Alarm: Low-output power alarm for the TX
(~ -40 to +8.2 dBm)
High Warning: High-output power warning for the TX
(~ -40 to +8.2 dBm)
Low Warning: Low-output power warning for the TX
(~ -40 to +8.2 dBm)
Rx Power High Alarm: High-input power alarm for the Rx
(~ -40 to +8.2 dBm)
Low Alarm: Low-input power alarm for the Rx
(~ -40 to +8.2 dBm)
High Warning: High-input power warning for the Rx
(~ -40 to +8.2 dBm)
Low Warning: Low-input power warning for the Rx
(~ -40 to +8.2 dBm)
SFP Memory (Port SFP [connector])

The SFP memory field provides access to sophisticated identification information that
describes the transceivers capabilities, standard interfaces, manufacturer and other
information. Refer to INF-8074 for detailed descriptions of the individual data fields.

6.7 Testing a Cable

You can test the quality of copper cables, connectors and terminations attached to each
unit. For this, the unit uses Time-Domain Reflectometry (TDR). You can quickly find opens,
shorts, cable impedance mismatches, bad connectors and termination mismatches. If no
problem in the cable is found, this test reports the cable length. If a problem is found, the
test reports the distance at which the problem is detected.
Note: You can only test cables in use on RJ45 ports. SFPs (optical or
electrical) are not supported.
To test the quality of a cable and view results

1. Access the page Port Cable.
A summary of all cable test results for all available copper ports is displayed. For more
information on specific parameters, refer to the following table.
2. Click the Connector to test a cable.
3. Click the Perform test button to start the test.

The test should last only a few seconds and the status of each channel is updated as
the tests are run.
Cable Verification (Port Cable)
Channel A The results for each pair in a four-pair cable are presented in
Channel B these four columns.
Channel C
Channel D
Length If no problem in the cable is found, this test reports the cable
length.
If a problem in the cable is found, this test gives the
approximate distance at which the problem is detected.
Status The current status of the cable:
GOOD: Normal cable
SHORT: The positive and negative lines of the same pair are
touching. The possible causes are:
Line of the RJ-45 cable may be touching the wire closet

patch panel.
Line of the RJ-45 cable may be worn from constant use

and positive and negative lines may be touching.
OPEN: There is a cut on a pair. The possible causes are:
Line of the RJ-45 cable may be left unconnected at the

wiring closet patch panel.
Line of the RJ-45 cable may have been cut

unintentionally.
The other end of the RJ-45 cable may be simply

unconnected.
FORCED: A persistent noise in the channel. This can be

caused by a link partner running in forced 10/100Mbps.
Cable length is not available in the FORCED state.
FAIL: The test failed. The link partner must lose the link in
order to start the test. If the PHY receives a continuous
signal during 125ms, it reports the test result as FAIL.
Impedance Mismatch Status: Whenever the effective

impedance is not 100Ohms. The possible causes are:
Different quality cables are connecting through a cable

extender.
A cable with the wrong quality is being used.

7 Setting Up Protection
This chapter describes how to set up protection on the unit; it contains the following
sections:
7.1 Setting Up LAGPort Protection 148
7.2 Setting Up ERPProtection 154

7.1 Setting Up LAGPort Protection

The LAG port protection is a mechanism used to switch the traffic to a standby port if an
inactive link is detected on the main port.
Each LAG port protects the physical ports as described below:
LAG-1 protects PORT-1 and PORT-2. The traffic policies are mapped to Traffic-1.
LAG-2 protects PORT-3 and PORT-4. The traffic policies are mapped to Traffic-3.
The GT Performance Element's port protection mechanism is shown below.
7.1.1 Setting Up Port Protection

To set up LAG port protection
2. Click the LAG Port Name to edit its settings.
3. Define LAG port protection parameters as required by your setup, then click Apply.
For more information on specific parameters, refer to the table "Port Configuration (Port
Configuration)" on page 119.
Note: When using fault propagation with LAG port protection, you must
enable the protection on both LAG ports for the fault propagation to work
correctly.
For LACP protection, you must also set up the LAG parameters.
To configure LAGparameters
1. Access the page Protection LACP Configuration.
2. Click the Aggregator Name to edit its settings.
3. Define LAG parameters as required by your setup, then click Apply.


LACP Configuration (Protection LACP Configuration)

Aggregator Name The name of the LAGgroup
Mode The mode of the LACPprotection. The only supported option is:
Active/Standby: Allow for a working and a protection port.
Activity The LACP activity flag. The only supported option is:
Active: The LACPparticipant sends LACPDUs to maintain
the LAG.
Timeout The time to wait before sending LACPDU

Long: The 802.3ax Long Timeout
Short: The 802.3ax Short Timeout
Custom: Accedian Custom timeout allowing for sub-50

millisecond protection switching
System Priority The priority of the LACP system. It defines which end of the
LACP link has the highest priority to determine which link is
active. The higher the number, the lower the priority.
Supported values range from 1 to 65535
Port Name The name of the port
Port Priority The port in the LAG that should be active for the LACP system.
The priority can change dynamically depending on the revertive
mode configuration.
Port Number The number of the port
7.1.2 Switching to the Standby Port

To switch to the standby port
2. Click the LAG Port Name to which you want to switch.
3. Select the Working Connector to which you want to switch, then click Apply.

7.1.3 Viewing LACP Status

You can view a summary or the detailed of the status of each LACP instance. The statuses,
given for the LACP actor and partner, are provided for debugging purposes for a
knowledgeable user. Refer to IEEE802.1ax for more information.
To view a summary of the status for all LACP

1. Access the page Protection LACP Status.
2. To view the detailed status of an LACP, select an Aggregator Name.

To view the detailed status of an LACP

1. Access the page Protection LACP Status.
2. Select an Aggregator Name.

LACP Status (Protection LACP Status)
System The MAC address of the port set as working (actor) in the LACP
system
System Priority The priority of the LACP system. It defines which end of the
LACP link has the highest priority and is therefore active.
The higher the number, the lower the priority.
Possible values: 1 to 65535
Key The IEEE aggregation key assigned to the port
Port ID The LACP port identifier
Port MAC Address The port MAC address
Port Priority The port in the LAG that should be active for the LACP system.
The priority can change, depending on the revertive mode
configuration.
Port State The current state of the port
The port state is expressed as a hexadecimal value, where
individual bits within a single octet represent different state
elements.
The actor and partner can have one or more of the following

states:
LACP Activity: The Activity control value of this link,
encoded in bit 0
Active LACP = 1
Passive LACP = 0
LACP Timeout: The Timeout control value of this link,

encoded in bit 1
Short Timeout = 1
Long Timeout = 0
Aggregation: Encoded in bit 2
When Aggregation = 1, the system considers this link to

be Aggregatable, i.e. a potential candidate for
aggregation.
When Aggregation = 0, the link is considered to be

Individual, i.e. this link can be operated only as an
individual link.
Port State (con't) Synchronization: Encoded in bit 3
When Synchronization = 1, the system considers this

link to be IN Sync, i.e. it has been allocated to the
correct Link Aggregation Group, the group has been
associated with a compatible Aggregator, and the
identity of the Link Aggregation Group is consistent
with the System ID and operational key information
transmitted.
When Synchronization = 0, this link is currently Out of

Sync, i.e. it is not in the right Aggregation Group or it is
not properly aggregated.
Collecting: Encoded in bit 4. When Collecting = 1, the

collection of incoming frames on this link is definitely
enabled, i.e. is not expected to be disabled in the absence
of administrative changes or changes in received protocol
information.

Distributing: Encoded in bit 5. When Distributing = 0,

distribution of outgoing frames on this link is definitely
disabled, i.e. is not expected to be enabled in the absence
of administrative changes or changes in received protocol
information.
Defaulted: Encoded in bit 6
When Defaulted = 1, the Actor Receive machine is using

Defaulted operational Partner information, configured
for the Partner.
When Defaulted = 0, the operational Partner

information in use has been received in a LACPDU.
Expired: Encoded in bit 7
When Expired = 1, the Actor Receive machine is in the

Expired state.
When Expired = 0, the Actor Receive machine is not in

the Expired state.
7.1.4 Viewing LACP Statistics

You can view a summary and/or details of the statistics related to each LACP instance.
To view a summary of the statistics for all LACP

1. Access the page Protection LACP Statistics.
2. To view the detailed statistics of an LACP, select an Aggregator Name.
To view the detailed statistics of an LACP

1. Access the page Protection LACP Statistics.
2. Select an Aggregator Name.


LACP Statistics (Protection LACP Statistics)

Port Name The name of the port
Tx LACPDU The number of LACPDU packets that were transmitted
LACPDUSent
Rx LACPDU The number of LACPDU packets that were received
LACPDU Received
Bad Rx LACPDU The number of invalid LACPDU packets that were received
Bad
LACPDUReceived
Marker Information The number of marker information packets that were received
Received
Marker Response The number of marker response packets that were transmitted
Sent
Marker Information The number of marker information packets that were
Sent transmitted
Marker Response The number of marker response packets that were received
Received
Bad Marker Received The number of invalid marker packets that were received

7.2 Setting Up ERPProtection

ERP is a protection mechanism that maintains high availability of Ethernet services for ring
topology networks. ERP is based on the ITU-T G.8032 specification.
An ERP ring consists of at least two units: one unit is configured as the owner and a
second adjacent unit as the neighbor. Similar to Spanning Tree Protocol (xSTP), ERP
implements a mechanism to prevent loops. Thus, although the physical topology is ring,
traffic on one of the links is blocked and therefore the actual logical topology is linear. In
ERP, the blocked link is the one between the owner and neighbor and is referred to as the
Ring Protection Link (RPL). During normal operation, customer traffic does not travel on
the RPL. During a failure, the RPL is unblocked and traffic can move between the owner
and neighbor; the failed link thus becomes the new RPL.
Switchover to protection is triggered by link failure, which can be based on link status or
Connectivity Fault Management (802.1ag CFM). ERP protection allows switchover within
50 milliseconds.
You must set up LAG port protection, as described in "Setting Up LAGPort Protection" on
page 148 before setting up ERP protection.
After setting up LAG port protection, you are ready to set up ERP protection.
To set up ERP protection

1. Access the page Protection ERP Configuration.
A summary of all ERP instances currently set up in the system is displayed.
2. Click the Add button to add a new ERP instance or click the Index of an existing ERP
instance to edit its settings.

ERP Configuration (Protection ERP Configuration)
Index The unique identifier assigned to the ERPinstance once it has
been created. You cannot modify this value.
Note:The system supports up to eight ERP instances.
Name The name of the ERPinstance
Version The version number assigned to the ERPinstance once it has
been created. You cannot modify this value.

Port Configuration
LAG Port The LAG port used by this ERPinstance. You must first set this
LAG port to ERPstatus protection mode in the page Port
Configuration.
Port 0 The name of the physical port 0 (PORT-1 or PORT-3, depending
on which LAG port is selected) used in the ERP
MEP0-idx The MEP index used for detecting a failure on ring port 0
Port 1 The name of the physical port 1 (PORT-2 or PORT-4 depending
on which LAG port is selected) used in the ERP
MEP1-idx The MEP index used for detecting failure on ring port 1.
RPL Configuration
RPL-Role The ring protection link role:
None:This unit is neither the RPL Owner nor the RPL
Neighbor of this ERPinstance.
Owner: This unit is the RPL Owner for this ERP instance.
Only one unit can be set to Owner for an ERPring.
Neighbor: This unit is the RPL Neighbor for this ERP

instance. Only one unit can be set to Neighbor for an
ERPring.
RPL-Port The physical port for the ring protection link

It is useful to know which port to connect between the owner
and its neighbor.
0:Port 0
1:Port 1
Hold-Off Timer The time, expressed in milliseconds, to wait before ERP

protection initiates a switch. Waiting before switching may give
another protection mechanism time to repair the defect.
Revertive Select this box to enable the revertive mode of operation.
Note: Only applies when the RPL-Role is set to Owner.
Guard Timer The guard timer duration, expressed in milliseconds
WTR Timer The duration of the Wait To Restore timer, expressed in minutes

Note: Only applies when the RPL-Role is set to Owner.
ERP Configuration
MD Level The MD level of the ERPmessages
Sub-Ring without Enable this box when the unit is used in a sub-ring without a
Virtual Channel virtual channel. When this box is enabled, flush logic is
performed on the sub-rings forwarding database, as defined in
the G.8032 Corrigendum 1 (10/2010).
Note: Leave this box disabled if the unit is part of a main ring or
a sub-ring with virtual channel.
VLAN Type The VLAN Type may be one of the following:
C-VLAN
S-VLAN
T-VLAN
APS-VID The VLAN used by the APS protocol. Each ERP instance uses a
different VLAN.
Range: 1 to 4095
Note:This VLANmust be reserved solely for the APSprotocol,
otherwise an error will be raised. Furthermore, the VLANmust
not be used for any type of customer traffic.
VID Set The list of VLAN IDs protected by this ERPinstance. Only these
VID-List VLANs can be sent on this ring.
7.2.1 Viewing ERP Status

You can view a summary of all ERP status, or the details of the status of each ERP
instance.
To view a summary of the status for all ERP instances

1. Access the page Protection ERP Status.
To view a summary of the status for all ERP instances

2. To view the detailed status of an ERP, select an ERP Index.


ERP Status (Protection ERP Status)

Index The unique identifier assigned to the ERPinstance. You cannot
modify this value.
Name The name of the ERP instance
Node ID The MAC address of this unit
State The state of the ERP instance:
Idle: No request, normal condition and ring path
Protection: Switched to the protection path
Manual Switch: Manual switch requested
Forced Switch: Forced switch requested
Pending: In WTR state; it is waiting before reverting to idle
RPL Node ID The MAC address for the ring protection link port
Alarms
Version Mismatch The ERP version of the units in the ring match (Inactive) or do
not match (Active).
Force Switch Forced switching of a ring port (Active or Inactive)
Manual Switch Manual switching of a ring port (Active or Inactive)
Signal Failed Signal failure is present (Active) or absent (Inactive). A signal
failure triggers a protection switch.
Latest Top Priority Request
Request Node ID The MAC address of the requested node
Request The last top priority request that was processed
Port X
Port X The name of the physical port used in the ERP
Status The status of the ring protection link port
State The state of the port, i.e. Blocked or Forwarding
Force Switch Click this button to force switching of the ring port.
Manual Switch Click this button to perform a manual switch of the ring port.
Clear Click this button to clear a switch you forced previously.

7.2.2 Forcing a Switch to the Standby Port

A forced switch forces the traffic to the standby port. You may need a forced switch in
various situations, for example, when you want to add a unit to the ring, or when you
want to perform maintenance on the other side of the ring, or for testing purposes.
CAUTION: Forcing a switch to a port that is in "Protection" state may

result in a loss of traffic.
To force a switch to the standby port

2. Click the ERP Index of the ring you want to switch.
3. Click the Port x Force Switch button to force a switch from this port to the standby
port.
7.2.3 Clearing a Forced Switch

You need to clear a forced switched before forcing another switch on the same unit. So,
you cannot force a switch on port 0 and on port 1 at the same time.
To clear a forced switch

2. Click the ERP Index of the ring for which you want to clear the forced switch.
3. Click the Clear button to clear the forced switch.
7.2.4 Switching Manually to the Standby Port

Traffic can be manually switched to the standby port if the state of the standby port
allows the traffic to switch. A manual switch may be required in various situations, for
example, for maintenance. The difference from a forced switch is that a signal failure in the
ring will override the manual switch. This is to avoid losing traffic when doing some kind of
maintenance.
To manually switch to the standby port

2. Click the ERP Index of the ring you want to switch.
3. Click the Port x Manual Switch button to manually switch from this port to the
standby port.

7.2.5 Viewing ERP Statistics

You can view a summary and details of the statistics for each ERP instance.
To view a summary of the statistics for all ERP instances

1. Access the page Protection ERP Statistics.
To view the detailed statistics of a specific ERP instance

1. Access the page Protection ERP Statistics.
2. Select an ERP Index.

ERP Results (Protection ERP Statistics)
Index The unique identifier assigned to the ERPinstance. You cannot
change this value.
Node ID The MAC address of this unit
Port X (The results for each port)
Local Clear The state of the ERP instance
Local FS The number of local forced switches performed
Local SF The number of local signal failures
Local MS The number of local manual switches performed
RX APS(Event) The number of APS events received (all events of type received)
RX APS(FS) The number of forced-switch events received
RX APS(SF) The number of signal-failed events received
Rx APS(MS) The number of manual-switch events received
RX APS(NR,RB) The number of no-requests and RPL blockages received
RX APS(NR) The number of no-requests received
TX APS(Event) The number of APS events transmitted
TX APS(FS) The number of forced switches transmitted

TX APS(SF) The number of signal failures transmitted
TX APS(MS) The number of manual switches transmitted
TX APS(NR,RB) The number of no-requests and RPL blockages transmitted
TX APS(NR) The number of no-requests transmitted
Discarded RX APS
GuardTimer The number of APS messages blocked by the guard timer
The guard timer blocks outdated APS messages, which prevents
the system from acting upon outdated Rx APS messages
Unknown Request Unknown request code received
Code
Version Mismatch The number of events received with an ERP version that do not
match the local version.
7.2.6 Viewing the ERP VLAN Learning Table

You can view a summary or the details of the VLAN database (or VLAN learning table) for
each ERP instance. Doing so allows you to see on which port each VLAN is forwarded.
To view a summary of the VLAN database for all ERP

1. Access the page Protection ERP VLAN fdb.
2. To view an ERP's detailed VLAN database, select its Index value from the list.
Tip:Click Refresh to update the on-screen values. To force updates at a
pre-determined interval, enable the Poll every X seconds box and enter a
value.
ERP VLAN Forwarding Table (Protection ERP VLAN fdb)
Index The unique identifier assigned to the ERPinstance
Ports The ports in use and the Flooding VIDs and Flapping VIDs
Each port lists the learned VLAN IDs on this port. VIDs listed for
a port are transmitted over this port.
The Flooding VIDs list the VLAN IDs that are not presently

learned. VIDs listed here are transmitted over the two ports of
the ring.
The Flapping VIDs list the VLAN IDs that are received too
frequently over each port alternatively. This indicates a possible
configuration issue for these VLAN IDs.
VIDs The list of VIDs for each port, Flooding VIDs and Flapping VIDs

8 Managing Traffic
This chapter describes how to create and manage Ethernet services; it contains the
following sections:
8.1 Understanding the Creation of Ethernet Services 164
8.2 Defining Filters 167
8.3 Setting Up Ethernet Services 176
8.4 Setting Up Traffic Shaping 201
8.5 Understanding Traffic Shaping via H-QoS 202
8.6 Using Layer-2 Protocol Tunneling 220
8.7 Monitoring Traffic 228

8.1 Understanding the Creation of Ethernet Services

This section presents the creation of E-Line, E-LAN and E-Tree services as described in
MEF6.1. It also explains how to configure some of the service attributes for the created
services, such as bandwidth profiles, CoS mapping and Layer-2 control protocol
processing options. For information on monitoring performance, refer to the following
chapters:
"Monitoring Network Performance with Ethernet OAM" on page 231
"Monitoring Network Performance with Service OAM" on page 245

The services you can create are:
Ethernet Service Mapping: Create E-Line, E-LAN and E-Tree services by mapping traffic to
an Ethernet Virtual Connection (EVC). You can also specify, per-circuit, any combination of
the following:
VLAN tagging: adds a C-VLAN, T-VLAN or S-VLAN tag to the frame (selective push)
CoS mapping: sets PCP (C-, S- or T-VLAN priority) value based on DSCP, IP Precedence
or PCP
Bandwidth policing: sets rate limiting based on the bandwidth profile defined for the
selected flow (CIR, EIR, CBS or EBS)
Bandwidth Policing (also referred to as Rate Enforcement or Bandwidth Regulation):
Bandwidth profiles, which are defined by the values of their associated parameters (CIR,
CBS, EIR, EBS, CM and CF), are enforced via a token bucket algorithm according to
Technical Specification MEF10.2. Bandwidth profiles can be used to offer bandwidth to
your client according to predefined SLAs. The Bandwidth policing assures SLAs by
regulating committed and excess information throughput, per flow: upstream and down.

Token Bucket Algorithm for Bandwidth Profile
Bandwidth profiles can be specified as follows:

Bandwidth Profiles Per Ingress UNI
Bandwidth Profiles Per EVC
Bandwidth Profiles Per CoS ID
Bandwidth Profile Types

Traffic Filtering: Filters can be defined to classify traffic based on any combination of the
following frame characteristics:
VLAN ID
PCP value
DSCP value
IP precedence value
The filtered traffic can be either dropped, or sent for service mapping, CoS mapping
and/or bandwidth policing.

8.2 Defining Filters

You can set up a specific filter (Layer-2 or IPv4) for use with loopbacks or traffic policies.
This way, you can loop back traffic or set up a traffic policy based on specific
characteristics such as Ethernet Header settings, VLAN settings and DSCP for Layer-2
filters, or based on IPv4 Header settings, ICMP settings and VLAN settings. You can also
use the preconfigured Layer-2 or IPv4 filters.
Note: The maximum number of traffic policies using a specific filter (L2
filter or IPv4 filter) is limited by the type of unit you use. Refer to your
units datasheet for the maximum number of specific filters possible for
traffic policies.
8.2.1 Configuring a Layer-2 Filter

To set up a Layer-2 filter
1. Access the page Traffic Filters L2 Filters.
A summary of all Layer-2 filters that are currently set up is displayed. For more
information on specific parameters, refer to the table at the end of this procedure.
Note: Commonly-used filters have been predefined for your convenience.
2. Click Add to add a new filter or click the Filter Name of an existing Layer-2 filter to edit
its settings.
Note: When you edit an existing Layer-2 filter, the changes that you make
are not applied to loopbacks in use when you click Add. If you want those
loopbacks to use the modified Layer-2 filter, you need to disable the
loopback and re-enable it (See "Setting Up and Enabling Loopbacks" on
page 367). For traffic policies, the changes you make are applied
immediately when you click Add.
3. Check the appropriate check box to enable this field, complete the required fields,
then click Add.
Note: For all fields, check the box to enable the field. If the check box is not
checked, the value will be ignored.
Note: You can specify several VLAN fields for the first VLAN (VLAN 1) as well
as for the second level VLAN (VLAN 2).
Layer-2 Filters (Traffic Filters L2 Filters)
L2 Filter Name / Unique name to identify the filter

Filter Name
Ethernet Header Settings
MAC Destination / The destination MAC address and mask. Only the bits specified
Mask by the mask are used. The other bits are ignored.
Address Format: six pairs of hexadecimal digits separated by
colons (xx:xx:xx:xx:xx:xx).
MAC Source / Mask The source MAC address and mask. Only the bits specified by
the mask are used. The other bits are ignored.
Address Format: six pairs of hexadecimal digits separated by
colons (xx:xx:xx:xx:xx:xx).
Encapsulated Protocol may be selected or entered manually (hexadecimal):
Ethertype
IPv4 (0x0800)
X.25 Layer3 (0x0805)
ARP (0x0806)
REVARP (0x8035)
IPX (0x8137)
VLAN (0x8100)
SNMP (0x814C)
WCP (0x80FF)
IPv6 (0x86DD)
MAC Control (0x8808)
MAC Protocol (0x22E2)
PPP (0x880B)
MPLS (0x8847)
MPLS Multicast (0x8848)
PPPOE Discovery (08863x)
PPPOE Session (0x8864)
S-VLAN (0x88A8)

T-VLAN (0x9100)
LLDP (0x88CC)
3GPP2 (0x88d2)
LOOP
VLAN Stack Size Enable this box, then make a selection in the drop-down list to
indicate the number of VLAN tags that packets must have in
order to match this filter.
VLAN and VLAN-in-VLAN Settings
Ethertype The VLAN Ethernet Type may be one of the following:
C-VLAN:Customer VLAN (typically inner tag)
S-VLAN:Service VLAN (typically outer tag)
T-VLAN:TunnelVLAN (inner or outer tag)
Both: Choose this option so filters will allow frames with C-

VLAN or S-VLAN tags through.
Any: Choose this option so filters will allow frames with C-

VLAN, S-VLAN or T-VLAN tags through.
CFI/DEI The Canonical Format Indicator (CFI) or the Drop Eligibility

Indicator (DEI). This value should always be set to zero for
connections to Ethernet switches.
CFI is used to ensure compatibility between Ethernet type
networks and Token Ring type networks. If a frame received at
an Ethernet port has a CFI set to 1, the frame should not be
forwarded "as-is" to an untagged port.
In the context of bandwidth regulation, DEI can be used to carry
the frame color. When set to 0, the frame is green; when set to
1 the frame is yellow.
Priority VLAN priority allows provisioning CoS prioritization using the
standard 802.1Q priority tag. Interpreting the priorities is based
on the carrier's equipment and administrative policies. The valid
operator types are:
Greater than
Less than

Equal to
Range (inclusive range)

The possible values for each operator are: 0 to 7.
Note: You can set only one VLAN (VLAN or VLAN-in-VLAN) to a
range; the other must be set to Equal to. For instance, if you
select a range for the second VLAN (VLAN-in-VLAN), you must
select Equal to for the first VLAN (VLAN).
VLAN ID The VLAN ID used to filter traffic. The valid operator types are:
Greater than
Less than
Equal to

DSCP/IP Precedence
DSCP/IP Precedence The DSCP/IP precedence operator may be one of the following:
Greater than
Less than
Equal to
8.2.2 Configuring an IPv4 Filter

To set up an IPv4 filter
1. Access the page Traffic Filters IPv4 Filters.
A summary of all IPv4 filters that have been set up is displayed. For more information
Note: Commonly-used filters have been predefined for your convenience.

2. Click the Add button to add a new filter, or click the Filter Name of an existing IPv4
filter to edit its settings.
Note: When you edit an existing IPv4 filter, the changes that you make
are not applied to loopbacks in use when you click Add. If you want those
loopbacks to use the modified IPv4 filter, you need to disable the
loopback and re-enable it (See "Setting Up and Enabling Loopbacks" on
page 367). For traffic policies, the changes you make are applied
immediately when you click Add.
3. Check the appropriate check box to enable this field, complete the required fields,
then click Add.
Note: For all fields, check the box to enable the field. If the check box is not
checked, the value will be ignored.
Note: You can specify several VLAN fields for the first VLAN (VLAN 1), as well
as for the second-level VLAN (VLAN 2).
IPv4 Filters (Traffic Filters IPv4 Filters)
IPv4 Filter Name A unique name used to identify the filter
Filter Name
IPv4 Header Settings
IPv4 Source / Mask The source address and mask. Only the bits specified by the
IP Source mask are used; the other bits are ignored.
Note: Filtering source or destination IP addresses that are
assigned by Dynamic Host Control Protocol (DHCP) can be
problematic. It is recommended to only specify static or
reserved IP addresses in a filter, otherwise the filter must be
updated manually whenever the addresses change.
IPv4 Destination / The destination address and mask. Only the bits specified by
Mask the mask are used; the other bits are ignored.
IP Destination Note: Filtering source or destination IP addresses that are
assigned by Dynamic Host Control Protocol (DHCP) can be
problematic. It is recommended to only specify static or
reserved IP addresses in a filter, otherwise the filter must be
updated manually whenever the addresses change.
TTL The time-to-live value
ECN Explicit Congestion Notification. Specify either 0 or 3.
Header Length The header length, expressed in 32-bit words. Specify a value in
the range of 515.

Protocol Either select a protocol from the list below or enter a port
number (decimal) manually.
Common protocols are TCP (6), UDP (17) and ICMP (1). TCP is
used by HTTP, FTP, Telnet and SMTP. UDP is used by DNS,
SNMP and RIP. ICMP is used by Ping.
The available protocols, expressed in the format of protocol
name (port number), are:
ICMP (1)
ICMP (2)
IP (4)
TCP (6)
EGP (8)
IGP (9)
UDP (17)
IPv6 (41)
SDRP (42)
IPv6-Route (43)
IPv6-Frag (44)
IDRP (45)
RSVP (46)
GRE (47)
MHRP (48)
ESP (50)
AH (51)
MOBILE (55)
SKIP (57)
EIGRP (88)

OSPFIG (89)
IPComp (108)
VRRP (112)
UDP/TCP Port Settings

Source Port Specify the UDP or TCP port number used by the IPv4 source
port field.
This setting is valid only when the Protocol is set to TCP (6) or
UDP (17).
Destination Port Specify the UDP or TCP port number used by the IPv4
destination port fields.
This setting is valid only when the Protocol is set to TCP (6) or
UDP (17).
ICMP Settings
ICMP Type Enables the use of ICMP. You must specify the ICMP message
type to be matched by this filter.
Note:These settings are only valid when the "Protocol"
parameter is set to ICMP (1).
Some well-known ICMP types are:
Echo Reply (0)
Destination Unreachable (3)
Redirect (5)
Echo (8)
Time Exceeded (11)

Other ICMP Codes: See www.iana.org/
ICMP Code Enables the use of ICMP code
Ethernet Header Settings
VLANStack Size Enable this box, then make a selection in the drop-down list to
indicate the number of VLAN tags that packets must have in
order to match this filter.
VLAN and VLAN-in-VLAN Settings
Ethertype The VLAN Ethernet Type may be one of the following:

C-VLAN:Customer VLAN (typically inner tag)
S-VLAN:Service VLAN (typically outer tag)
T-VLAN:TunnelVLAN (inner or outer tag)
Both: Choose this option so filters will allow frames with C-

VLAN or S-VLAN tags through.
Any: Choose this option so filters will allow frames with C-

VLAN, S-VLAN or T-VLAN tags through.
CFI/DEI The Canonical Format Indicator (CFI) or the Drop Eligibility

Indicator (DEI). This value should always be set to zero for
connections to Ethernet switches.
CFI is used to ensure compatibility between Ethernet type
networks and Token Ring type networks. If a frame received at
an Ethernet port has a CFI set to 1, the frame should not be
forwarded "as-is" to an untagged port.
In the context of bandwidth regulation, DEI can be used to carry
the frame color. When set to 0, the frame is green; when set to
1 the frame is yellow.
Priority VLAN priority allows provisioning CoS prioritization using the
standard 802.1Q priority tag. Interpreting the priorities is based
on the carrier's equipment and administrative policies. The valid
operator types are:
Greater than
Less than
Equal to

The possible values for each operator are: 0 to 7.
VLAN ID The VLAN ID used to filter traffic. The valid operator types are:
Greater than
Less than

Equal to

DSCP/IP Precedence
DSCP/IP Precedence The DSCP/IP precedence operator may be one of the following:
Greater than
Less than
Equal to

8.3 Setting Up Ethernet Services

You can create and manage Ethernet services through the Traffic menus.
The major steps required to create or manage services are:
1. Define Filters (Classify Traffic): The system is designed in a way that the traffic must
first be classified before sending it to any service creation function (Service mapping,
bandwidth profile or filters). Three different types of filters can be defined:
Layer-2 filters and IPv4 filters. See "Defining Filters" on page 167.
VID Sets. See "Setting Up VID Sets" on page 176.
2. Define Service Attributes:
Define bandwidth profiles. See "Setting Up Bandwidth Regulators" on page 181.
Define CoS mapping: Sets VLAN priority based on DSCP, IP Precedence or PCP
values of the ingress frame. See "Setting Up CoS Profiles" on page 184.
Define bandwidth regulator sets. See "Setting Up Bandwidth Regulator Sets" on

page 183.
3. Create the Service (See "Setting Up Traffic Policies" on page 188):
Select the filter that you defined in the first step.
Select the action to be applied to the traffic flow defined by the filter (Drop or
Permit Traffic)
Assign or select one or more of the following characteristics:
EVC Mapping (encapsulation, Ethertype, VLAN ID)
CoS Mapping (PCP action, Type, CoS profile or default mapping)
Bandwidth profile (Regulator set if CoS Mapping is Preserve or Map, single

Regulator (bandwidth profile) for default mapping or direct CoS mapping
Access the page Traffic Policies to view a summary of the policy configurations.
8.3.1 Setting Up VID Sets

A VID set comprises one or more VLANs grouped in a logical entity. You can define VID
sets for each traffic stream (Traffic-1, Traffic-2, Traffic-3 and Traffic-4) to classify the
incoming traffic before sending it to the service creation function.
You can define up to 101 VID sets for each traffic stream.

Traffic VLAN VID Sets
Once a VID set is created, you can apply it to traffic policies as a filter (See "Setting Up
Ethernet Services" on page 176).
VLAN Filtering
You can create VLAN filters using the VLAN type field (S-VLAN, T-VLAN or C-VLAN) and
VLAN ID or Range.
When using VLAN filtering, you also need to select the VLAN (inner or outer VLAN) for
filtering the traffic for each policy list, e.g. Traffic-4.
To enable VLAN filtering

2. Select which VLAN you want to filter on for each policy list, then click Apply.
For more information on specific parameters, refer to the table "Traffic Configuration
(Traffic Configuration)" on page 105.
Viewing VID Sets

To view all current VID sets
1. Access the page Traffic VLAN VID Sets.
The VIDsets are displayed in a grid, grouped by policy list.
Note:No VID sets are defined by default.
2. Click the name of a policy list to view its associated VIDsets in the bottom half of the
page.
3. To filter the VIDsets for a given policy list results on the name, type, state, policy or
size, use the VLANType and Filter controls, then click Search. The use of wildcards is
supported.

VID Sets (Traffic VLAN VID Sets)

Policy Lists
Name The name assigned to the policy list
Incoming Port The port name
Number of VID The number of VID sets that are currently used by this policy list
sets
VID Sets
Name The name assigned to the VID set
Type The VLAN Ethertype of the VID set:
VLAN Type C-VLAN
S-VLAN
T-VLAN
State The state of the VID set, according to its use in the traffic policy
lists:
Free:The VID set is not assigned to a policy.
Mapped:The VID set is assigned to a policy.
Policy The name of the policy index used by this VID set.
Size The number of VLANs contained in the VID set
Adding or Editing VID Sets

To add or edit a VID set
1. Access the page Traffic VLAN VID Sets.
2. Click Add to add a new VID set or click the Name of an existing VID set to edit its
settings.
The VIDSet page appears.
3. Complete or update the required fields, then click Apply.

Adding or Editing VID Sets (Traffic VLAN VID Sets)

Name The name to assign to the policy list
Policy List Assigned when the VIDset is created, the policy list indicates the
traffic policy to which the VIDset applies. The value here is the
policy list on which the VID set will be active.
VLANLevel This field indicates whether the inner or the outer VLAN will be
inspected by this policy list, as set in the Traffic Configuration
page.
State Note:Does not apply when creating a new VIDset.
State of the VID set, according to its use in the traffic policy lists:
Free:Not assigned to a policy
Mapped:Assigned to a policy)
Policy Note:Does not apply when creating a new VIDset.

The name of the policy index used by this VID set.
Type The VLAN Ethertype of the VID set:
VLAN Type C-VLAN
S-VLAN
T-VLAN
VIDs Specify a list of VIDs in the following format: [- ], [- ] ... (e.g. 1,2,100-
200 will include VIDs 1,2,100,101,102,103 ... 200).
Note: With a catch-all filter, you must assign VID 04095. For
untagged frames, assign VID 0.
Outer VLAN
VLAN Type The VLANEthertype for the outer VLAN (when dual VLANis used)
This field is only applicable if the VLANLevel for this traffic policy is
set to Inner in the Traffic Configuration page.
VID Specify a VIDfor the outer VLAN.
This field is only applicable if the VLANLevel for this traffic policy is
set to Inner in the Traffic Configuration page.
Viewing VLAN IDs

To view the VLAN IDs mapping state
1. Access the page Traffic VLAN VLAN IDs.

The mapping stage of all VLANIDs is displayed.

Note:No VLAN IDs are assigned to VID sets by default.
Traffic VLAN VLAN IDs

VLAN IDs (Traffic VLAN VLAN IDs)
Policy Lists
Name The name assigned to the policy list
Incoming Port The incoming port's name
Number of VIDs Used The number of VLAN that are currently used by this policy list
VLAN IDs
VLAN ID The VLAN ID number
Type The VLAN Ethertype of the VLAN:
C-VLAN

S-VLAN
T-VLAN
State Indicates the state of a specific VLAN:

Free:Not assigned to any VID set
Assigned:Assigned to a VID set
Mapped:VID set to which the VLAN is assigned and used in

a traffic policy
Policy The policy index number to which this VLAN ID is mapped

VID Set If the VLAN is assigned to a VID set, this value indicates to which
VID set (Name)
8.3.2 Setting Up Bandwidth Regulators

You can set up bandwidth profiles (and the corresponding bandwidth regulators to
enforce them) through the Traffic Regulators Configuration page. Compared to
shaping, traffic regulation can easily scale to a high number of services per port.
The regulators you define are used to share token between services. The number of traffic
regulators that can be defined varies, depending on the model you are using. Once a
bandwidth regulator has been created, you can apply it to traffic policies (See "Setting Up
Ethernet Services" on page 176).
Note:Disabling then re-enabling a regulator resets the CBS and EBS token
buckets.
To set up a bandwidth regulator

1. Access the page Traffic Regulators Configuration.
A summary of all existing bandwidth regulators is displayed.
Note:No bandwidth regulators are defined by default.
2. Click Add to add a new bandwidth regulator or click the Name of an existing
bandwidth regulator to edit its settings.
The New Regulator Configuration page is displayed.
3. Complete the required fields, then click Add.

Regulator Configuration (Traffic Regulators Configuration)

Traffic Regulator A name identifying the bandwidth regulator
Name
Name
Committed The average rate up to which service frames are delivered by the
Information Rate bandwidth regulator.
(CIR) CIR-conformant frames are colored green.
CIR Range: 0 to maximum port speed (steps of 125 kbps)
Committed The maximum number of kilobytes available for a burst of frames
Burst Size that are sent at the port's speed and remain CIR-conformant
CBS Note:The burst size must be greater than the port's Maximum
Transfer Unit (MTU).
Range:1 kB to 2015 kB (steps of 1 kB)
Excess The average rate up to which excess service frames are delivered by
Information Rate the bandwidth regulator.
(EIR) EIR-conformant frames are colored yellow.
EIR Yellow traffic in excess of this maximum is declared red by the
regulator then dropped.
Range: 0 to maximum port speed (steps of 125 kbps)
Excess Burst Size The maximum number of kilobytes available for a burst of frames
EBS that are sent at the port's speed and remain EIR-conformant
Note:The burst size must be greater than the port's MTU.
Range:1 kB to 2015 kB (steps of 1 kB)
Color Mode Make a selection from the drop-down list to indicate how the
bandwidth profile should handle the color of the regulator's
incoming traffic:
Color-Aware: The pre-determined level of bandwidth profile
compliance for each frame is taken into account when
evaluating its level of compliance.
Color-Blind: All incoming traffic is colored green when it initially

enters the bandwidth regulator.
Coupling Flag Make a selection from the drop-down list to indicate how the
regulator processes yellow traffic via the coupling flag:
False: Yellow data is limited according to the Excess Information
Rate.

True: Yellow data is limited according to a combination of the

Committed Information Rate and the Excess Information Rate.
8.3.3 Setting Up Bandwidth Regulator Sets

A bandwidth regulator set is used to regulate traffic bandwidth based on the value of the
following information of the incoming frames:
PCP: p-bits in 802.1Q / 802.1Q-in-Q tags
IP Precedence: IP precedence bits in the IPv4 ToS byte
DSCP: DSCP bits in the IPv4 DSCP byte

Once a bandwidth regulator set has been created, you can assign it to traffic policies for
rate enforcement based on the map type being used. (See "Setting Up Ethernet Services"
on page 176).
Before configuring a bandwidth regulator set, you must first set up a number of traffic
regulators (refer to "Setting Up Bandwidth Regulators").
To configure the bandwidth regulator set, you must assign in the mapping table, a traffic
regulator (to a specific PCP, IP precedence or DSCP value. This table has N rows, where N
depends on the type of the regulator set. If the type is PCP or IP precedence, then N=8. If
the type is DSCP, N=64.
To configure a bandwidth regulator set

1. Access the page Traffic Mapping Bandwidth Regulator Sets.
A listing of the existing bandwidth regulator sets is displayed. For more information
2. Click the Add button to add a new bandwidth regulator sets or click the name of an
existing bandwidth regulator set to edit its settings.

BWR Set Configuration (Traffic Mapping Bandwidth Regulator Sets)
Index The unique identifier assigned to the bandwidth regulator set
Name Name of the bandwidth regulator set
Type Specifies the type of priority upon which the bandwidth
regulator set is based. The type you choose may be one of the

following:
PCP: Priority Code Point mapping
IP Precedence: IP precedence mapping
DSCP: Differentiated Services Code Point mapping
Reference Count The number of policies that are currently using this bandwidth
regulator set
Note:This parameter is only visible for existing sets.
PCP or IP Precedence PCP, IP precedence or DSCP value of the incoming frame
or DSCP [IN]
Bandwidth Regulator The bandwidth regulator to use when regulating the traffic flow
with this PCP, IP precedence or DSCP value
Enable Regulator Enable or disable traffic regulation for this PCP, IP precedence or
DSCP value.
8.3.4 Setting Up CoS Profiles

A CoS profile is used to map an input frame to a Layer-2 class of service based on the
conformance level (Green/Yellow) of the incoming traffic and on the value of the following
information of the incoming frames:
PCP: p-bits in 802.1Q / 802.1Q-in-Q tags
DSCP: DSCP bits in the IPv4 ToS byte

Once a CoS profile is created, you can apply it to traffic policies for CoS mapping and
bandwidth policing. See "Setting Up Ethernet Services" on page 176.
To set up the CoS profile, you need to assign in the mapping table, a class of service value
(0-7) to the outgoing traffic based on the conformance level (Green/Yellow) of the
incoming traffic and on the mapping entry. The mapping table has N rows, where N
depends on the type of the CoS profile. If the CoS profile type is PCP or IP precedence
then N=8. If the CoS profile is a DSCP, N=64.
To set up a CoS profile

1. Access the page Traffic Mapping CoS Profiles.
A list of existing CoS profiles is displayed. Four commonly-used profiles have been
preconfigured for your convenience.

2. Click the Add button to add a new CoS profile or click the Name of an existing CoS
profile to edit its settings.

CoS Profile Configuration (Traffic Mapping CoS Profiles)
Name The name identifying the CoS profile
Type Specifies the type of priority the CoS profile will use when
mapping incoming frames to a Layer-2 class of service. The type
you choose may be one of the following:
PCP: Priority Code Point mapping
IP Precedence: IP precedence mapping
DSCP: Differentiated Services Code Point mapping
Decode DEI Enable this check box to make the unit decode the pre-marking
color from the DEI bit (Drop Eligible Indicator). Otherwise, the
user-defined pre-color is used.
This parameter is only available when the PCP CoS profile type is
selected.
Encode Using DEI Enable this check box to make the unit control the DEI bit in an
S-VLAN tag. If this field is checked and the outgoing frame is
marked yellow, then the DEI bit is set to 1; otherwise, the DEI bit
is set to 0.
Reference Count The number of policies that are currently using this CoS profile
This parameter is only visible on existing profiles.
PCP or IP Precedence The input value of the incoming frame for PCP, IP precedence or
or DSCP [IN] DSCP type frames
Pre-Marking Color The pre-marking color to assign to the input frame that has this
PCP, IP precedence or DSCP value
Green [OUT] The CoS value for use with outgoing green frames. This value is
selected if either of the following is true:
The result of the bandwidth regulator assigned to this entry
is green.
The pre-marking color is green, and no bandwidth

regulator is assigned to this entry.

Yellow [OUT] The CoS value for use with outgoing yellow frames. This value is
selected if any of the following is true:
The result of the bandwidth regulator assigned to this entry
is yellow.
The pre-marking color is yellow, and no bandwidth

regulator is assigned to this entry.
The frame has passed through a color-aware bandwidth

policer and has been marked as yellow(due to the
depletion of its CIR bucket).
8.3.5 Setting Up Port CoS-to-PCP Mapping

A port CoS mapping is used to control the class of service assigned to the outer VLAN tag
of input frames on which a dual VLAN tag action (e.g. push-push or push-replace) was
applied in the unit. There is one configurable port CoS mapping for each physical or logical
(LAG) port in the system.
The Port CoS mapping defines how to map the PCP (Priority Code Point) value of the
outer VLAN tag based on the conformance level (Green/Yellow) of the outgoing frame and
on the PCP value of its inner VLAN tag.
Simply put, the mapping configuration is a translation table from one Service Provider's
priority scheme to another's. Consequently, if you are not putting traffic through multiple
Service Providers' networks, you do not need to modify the values in this page.
To configure port CoS mapping values

1. Access the page Traffic Mapping Port CoS Mappings.
The Port CoS Mapping Configuration page opens. All the units physical ports and
logical (LAG) ports are listed in a grid.
2. Click a port or LAG from the list to select it and configure its port CoS mapping.
The ports CoS-to-PCP mapping details are displayed.

3. Use the information in the table below to configure the ports CoS-to-PCP mapping
details, then click Apply.
The system returns to the listing of ports in the previous page.
Port CoS-to-PCP Mappings (Traffic Mapping Port CoS Mappings)
Port Name The outgoing port (physical or LAG) to which this CoS mapping
applies. This value corresponds to the port you selected in the
previous page.
Encode Using DEI Select this box to instruct the unit to control the DEI (Drop Eligible
Indicator) bit in the outer S-VLAN or T-VLAN tag.
If this field is checked and the outgoing frame is marked yellow,
then the DEI bit is set to 1; otherwise, the DEI bit is set to 0.
Note: If your network supports this feature, it is recommended
that you enable this box.
CoS PCP Mappings Table
CoS [INNER] All possible PCP values for the inner VLAN tag of the outgoing
frame are listed in this column of the mapping table.
These values are determined by the CoS profile configuration in
the traffic policy applied to the incoming traffic. You cannot modify
these values.
Green [OUT] For each row in the mapping table, make a selection from the
drop-down list to assign a CoS-to-PCP value (0-7) for use in the
outer VLAN tag of outgoing green frames.
This value is selected if either of the following are true:
The result of the bandwidth regulator assigned to this entry is
green.
The pre-marking color is green and no bandwidth regulator is

assigned to this entry.
Yellow [OUT] For each row in the mapping table, make a selection from the
drop-down list to assign a CoS-to-PCP value (0-7)for use in the
outer VLAN tag of outgoing yellow frames.
This value is selected if any of the following are true:
The result of the bandwidth regulator assigned to this entry is
yellow.
The pre-marking color is yellow and no bandwidth regulator is

assigned to this entry.

The frame has passed through a color-aware bandwidth

policer and has been marked as yellow due to the depletion of
its CIR bucket.
8.3.6 Setting Up Traffic Policies

Once you have set up the filters, bandwidth regulators, CoS profiles, queues, queuing
profiles, envelopes and bandwidth regulator sets, you are ready to assign them to a traffic
policy so they can become a service.
Note: On the GT Performance Element, default policies are pre-configured
to pass traffic transparently between PORT-1 and PORT-2, as well as
between PORT-3 and PORT-4. You can disable or reconfigure these policies
as needed for your application.
To set up a traffic policy

1. Access the page Traffic Policies.
The Policy Lists page opens. The configuration and statistics for the selected traffic
flow are displayed.
2. Select the appropriate traffic flow from the Policy Lists frame by clicking its name.
The configuration and statistics information is refreshed onscreen. The details for
Traffic-1 pertain to Port-1; the details for Traffic-n pertain to Port-n.
Note:If you have configured LAG-1 for protection, you cannot configure
details for Traffic-2.
3. Click a policy index number from the Policy Configuration Traffic-n frame.
The Traffic-n [n-x] Policy Configuration page opens.
4. Use the information in the table "Policy Configuration (Traffic Policies)" on page 190
to configure the traffic policy, then click Apply.
Note: The fields available for configuration vary, depending on the
Encapsulation and the PCP action you select.

Traffic Policies
1. Enable the policy, then select the outgoing port and queuing profile to which the
policy applies by making a selection in each of the drop-down lists.
2. Select the filter to classify traffic and the required action.

Note: Only the traffic matching the filter will have the rules applied to it.
The maximum number of traffic policies using a specific filter (L2 filter or
IPv4 filter) or a specific VID set is limited by the type of unit you use. Refer
to your units datasheet for the maximum number of specific filters
possible for traffic policies.
3. Select the EVC mapping encapsulation option and the required EVC mapping
parameters. Refer to "EVC Encapsulation Options" on page 193.

4. Select the PCP action for CoS mapping to perform if required. Refer to "PCP Action
Options" on page 195.
5. If you selected the PCP action MAP or Preserve, enable one or two traffic mapping
choices, select the Type of traffic mapping to perform, select the CoS Profile to apply
and select the bandwidth Regulator Set to apply.
6. If you selected the PCP action Direct, complete the Direct mapping parameters.
7. Choose the Outgoing Port and Queuing Profile assigned to this policy by making a
selection from the drop-down lists.
8. Enable the Monitoring port, if required, then choose the port to which traffic is
forwarded for monitoring from the drop-down list.
Policy Configuration (Traffic Policies)
Enable Policy Activates the policy
Outgoing Port The egress port assigned to this policy
Queuing Profile The queuing profile associated with this outgoing port
Filter Type The filter type (Layer-2 filter, IPv4 filter or VID set) used to
classify traffic
Filter The name of the filter. By default, a catch-all filter is defined.
This enables you to monitor all traffic on a port.
Action The action applied to traffic that matches the filter. Make a
selection from the drop-down list:
Drop Traffic: The traffic matching the filter is dropped.
Policy statistics are collected as part of this policy.
Permit Traffic: The traffic matching the filter is counted in

the statistics then forwarded. Policy statistics are collected
as part of this policy.
MGMT-OAM: The traffic matching the filter is forwarded to

the CPU so that it can be processed. No policy statistics are
collected as part of this policy.
MGMT-OAM & Drop: The traffic matching the filter is

forwarded to the CPU so that it can be processed, then it is
dropped. Policy statistics are collected as part of this policy.
MGMT-OAM & Forward: The traffic matching the filter is

forwarded to the CPU so that it can be processed and

forwarded. Policy statistics are collected as part of this
policy.
None: No action will be taken when matching traffic is

detected. However, other parameters still apply, such as
monitoring. Policy statistics are collected as part of this
policy.
Note: The None, MGMT-OAM, MGMT-OAM & Drop and
MGMT-OAM & Forward actions are not supported when the
filter type is VID set.
Enable Monitoring Enable or disable the monitoring port.
Monitor Port The port to which traffic is forwarded for monitoring
EVC Mapping
Encapsulation Select one of the following encapsulation methods:
None: Regulate traffic based on PCP, IP precedence or
DSCP values.
Push: Add a VLAN tag.
Pop: Remove the outer VLAN tag, if any.
Replace: Perform an action similar to Push, but rather than

adding a new VLAN tag, replace the VLAN tag with the
information provided by the Ethertype and VLAN ID. Note:
This action requires a filter that checks for the presence of
at least one VLAN tag.
Preserve VLAN - New CFI/PCP: Keep the VLAN tag while

allowing the CFI/PCP values to be modified.
Push & Preserve: Add a new VLAN tag using the VLAN ID of
the inner VLAN, if any.
Push & Push: Add two VLANtags (Q-in-Q).
Push & Replace: Add a new outer VLAN tag and replace the
inner VLAN tag with the information provided by the
Ethertype and VLAN ID.
Pop & Replace: Pop the outer VLAN tag and replace the
inner VLAN tag with the information provided by the

Ethertype and VLAN ID. Note: This action requires a filter

that checks for the presence of two VLAN tags.
Pop & Pop: Pop both the inner and the outer VLAN tags (Q-
in-Q).
Note: The details of this option will vary, depending on the
available PCP actions.
Ethertype The Ethertype of the VLANs to be added (if any)
Possible values:
C-VLAN: 0x8100
S-VLAN: 0x88A8
T-VLAN: 0x9100
VLAN ID VLAN ID of the VLANs to be added (if any)

Possible values range between 0 and 4095.
CoS Mapping
PCP Action The PCP (Priority Code Point) action to perform
Preserve: Keep the PCP value or gather its value from the
CoS profile.
Direct: Use the direct mapping options.
Map: Map the PCP/DEI values according to the selected

CoS Profile.
For each PCP action, there may be one or two traffic mapping
choices. If the frame does not match the first or the second
choice, default PCP values are used.
Note: The choices may vary, depending on the Encapsulation
option and on the PCP action you selected.
Enable Enable or disable the first and second traffic mapping choices.
Type The type of Layer-2 traffic mapping to perform for the first and
second choices
PCP VLAN: Priority Code Point (p-bits) in 802.1Q tags

PCP VLANinVLAN: Priority Code Point (p-bits) in 802.1Q-in-

Q tags
DSCP: DSCP bits in the IPv4 DSCP bytes
CoS Profile CoS profile to apply from the list. The list includes the default
CoS profile and the ones you created.
Regulator Set The bandwidth regulator set to apply from the list. The list
includes the bandwidth regulator sets you created.
Default/Direct Bandwidth Regulator
Enable Bandwidth Activates a default bandwidth regulator. If the PCP action is
Regulation Map and the traffic does not match the configured maps, direct
default mapping is used.
Pre-Marking Color Pre-mark, with a specific color, the traffic that does not match
the first and second traffic mapping choices. This option has no
effect if the enabled bandwidth regulator is color-blind. In
addition, if no bandwidth regulator has been enabled, this
option selects the default green/yellow CFI & PCP values to be
used in the outgoing frames.
Green traffic uses tokens from the CIR bucket until
depleted, at which time it will be tagged as Yellow data.
Yellow traffic uses tokens from either the CIR + EIR buckets
or just the EIR bucket, depending on how the coupling flag
is set in the regulator. Once the CIR + EIR tokens are
depleted, this traffic will be tagged as Red data(red traffic is
dropped).
Note: Data cannot be pre-marked as Red if its bandwidth
regulator has been disabled. In such circumstances, using
"Drop Traffic" instead may be advisable.
The traffic color affects how the regulator handles the traffic.
Bandwidth Regulator The bandwidth regulator associated with the traffic matched by
this policy
CFI/DEI The default CFI and PCP values to be applied if the traffic does
PCP not match the first and second traffic mapping choices.
EVC Encapsulation Options

Use the encapsulation options to perform EVC mapping actions.

None
Use this option when no VLAN ID manipulation is required for the selected traffic flow and
you need to regulate bandwidth based on PCP, IP precedence or DSCP values.
The table below shows the valid configurations of the first and second choices.
Options for an Encapsulation of NONE
Parameter First Choice Second Choice
Type PCP VLANinVLAN PCP VLAN, IP precedence, DSCP
PCP VLAN IP precedence, DSCP
IP precedence, DSCP PCP VLAN, PCP VLANinVLAN
CoS Profile CoS profile CoS profile
BWR Set BWR set BWR set
Preserve VLAN New CFI/PCP

Use this option to keep the VLAN tag and permit modification of the CFI/PCP values. The
PCP action Preserve is not supported by this encapsulation option.
When using this option, you may select a PCP action for CoS mapping if required.
Note: This action requires a filter that checks for the presence of at least
one VLAN tag.
Refer to "PCP Action Options".
Push
Use this option to push (add) a VLAN tag onto an untagged frame or push an outer tag (Q-
in-Q) onto a tagged frame. When using the Push option, you may select a PCP action for
CoS mapping if required.
Refer to "PCP Action Options" on page 195.
Push & Preserve

Use this option to push the specified VLAN tag onto an untagged frame. If the frame is
already tagged, the VLAN ID in the outer tag of the frame is passed on to the tag that is
added on top of it. When using the Push & Preserve option, you may select a PCP action
for CoS mapping if required.
Refer to "PCP Action Options" on page 195.
Push & Push

Use this option to push the specified VLAN tags (Q-in-Q) onto a tagged or untagged frame.
When using the Push & Push option, you may select the PCP action for CoS mapping if
required.

Push & Replace

Add a new outer VLAN tag and replace the inner VLAN tag with the information provided
by the Ethertype and VLAN ID. When using the Push & Replace option, you may select
the PCP action for CoS mapping if required.
Replace
This action is similar to the Push action but rather than adding a new VLAN tag, it replaces
the VLAN tag with the information provided by Ethertype and VLAN ID parameters. The
PCP action Preserve is not supported by this encapsulation option. However, the user can
use the PCP action Map and the default 8P0D-8P0D CoS profile to preserve the incoming
PCP value.
Note: This action requires a filter that checks the presence of at least one
VLAN tag.
Pop
Use this option to remove the outer VLAN tag.
The table below shows the valid configurations of the first and second choices for this
encapsulation option.
Options for Pop Encapsulation
CoS Profile Ignored Ignored
BWR Set BWR set BWR set
Pop & Replace

Use this option to pop the outer VLAN tag and replace the inner VLAN tag with the
information provided by Ethertype and VLAN ID parameters. The PCP action Preserve is
not supported by this encapsulation option. However, the user can use the PCP action
Map and the default 8P0D-8P0D CoS Profile to preserve the incoming PCP value.
Note: This action requires a filter that checks the presence of two VLAN
tags (Q-in-Q).
Pop & Pop

Use this option to remove two VLAN tags (Q-in-Q). When using the Pop & Pop option,
you may select a PCP action for CoS mapping if required.
PCP Action Options

Use the PCP action options to perform different Priority Code Point actions.

Preserve
Use this option to copy the PCP values from the first VLAN (if any) to the pushed VLAN tag.
If the frame is not tagged, you may map the PCP values from an IP precedence / DSCP
CoS profile. It is also possible to select a bandwidth regulator set for bandwidth policing.
The table below shows the valid configurations of the first and second choices for this
encapsulation option.
Options for the PCP Action PRESERVE
Type IP Precedence / DSCP N/A
CoS Profile CoS profile N/A
BWR Set Optional N/A
Direct
Use this option to force PCP values to the default green or yellow values, based on the
result of the bandwidth regulator or the pre-marking color. The pre-marking color red is
ignored if the default bandwidth regulator is disabled.
Note: The first and second choices are ignored.
Map
Use this option to map and regulate traffic based on PCP, IP precedence or DSCP values.
The first and second choices can be used.
The table below shows the valid configurations of the first and second choices.
Options for the PCP Action MAP
CoS Profile CoS profile CoS profile
BWR Set Optional Optional
Viewing a Summary of the Policy Configurations

Access the page Traffic Policies to view a summary of the policy configurations. Click
the name in the Policy lists to view the summary of the policy configurations of a
particular port.

Filters based on VID sets use direct access to identify the corresponding policy for an
incoming frame. Each frames VLAN ID is analyzed and the value of the VLAN ID is used to
directly access the appropriate policy to apply.
Policy (Traffic Policies)
Name Name of the traffic policy
Incoming Port Name of the port of the traffic policies
Number of Policies Number of policies
Index The position of the rule in the policy list
State The policy may be enabled or disabled. Disabled policies are
ignored when the rules are applied to incoming data.
Action Action that the policy applies to data that it matches
Filter Name Name of the filter assigned to the policy
Policy Configuration
Type The filter type (L2 - IPv4 or VID set) used to classify traffic
Monitor The name of the active monitoring port associated with this
policy
Regulator The name of the bandwidth regulator assigned to this policy
Policy Statistics
Packets Good Number of good frames that matched the policy. A good frame
is an error-free frame that has a length between 64 bytes and
the maximum frame length.
Bytes Good Total number of bytes in good frames that matched the policy
Packets Bad Number of invalid frames that matched the policy. An inavlid
frame is a packet whose framing is valid but contains an error
within the frame, has an invalid CRC, is shorter than 64 bytes or
is longer than the maximum frame length.

8.3.7 Viewing Traffic Regulator Statistics

You can view a summary and detailed traffic regulator statistics for each traffic regulator,
including accepted bytes, dropped bytes, and counters that break down CIR and EIR
traffic.
To view traffic regulator statistics

1. Access the page Traffic Regulators Statistics to view the statistics summary of all
traffic regulators.
2. Click the Regulator name to view detailed statistics of the selected traffic regulator.
Bandwidth Regulator Statistics (Traffic Regulators Statistics)
Name The name assigned to the regulator
Accept Bytes The total number of bytes accepted by this regulator since its
creation
Accept Packets The total number of frames accepted by this regulator since its
creation
Accept L1 Rate The rate of accepted Layer-1 data, expressed in Mbps
(Mbps) This is the number of megabits of Layer-1 traffic accepted in the
last second of transmission.
Accept L2 Rate The rate of accepted Layer-2 data, expressed in Mbps
(Mbps) This is the number of megabits of Layer-2 traffic accepted in the
last second of transmission.
Drop Bytes Total dropped bytes by this regulator since the statistical count
started
Drop Packets Total dropped frames by this regulator since its creation
Drop L1 Rate (Mbps) The rate of dropped Layer-1 data, expressed in Mbps
Note:Only applies if the Regulator Working Rate parameter in
the Traffic Configuration page has been set to "Layer-1".
Drop L2 Rate (Mbps) The rate of dropped Layer-2 data, expressed in Mbps
Green Bytes The total number of green bytes handled by this regulator since
its creation

Traffic that is declared green and complies with the CIR is
allowed to pass through the policer without rate limitation.
Green traffic in excess of this maximum is declared yellow by the
regulator and is subject to EIR regulation.
Green Packets The total number of green frames handled by this regulator
since its creation
Traffic that is declared green and complies with the CIR is
allowed to pass through the policer without rate limitation.
Green traffic in excess of this maximum is declared yellow by the
regulator and is subject to EIR regulation.
Green L1 Rate (Mbps) The rate of green Layer-1 data, expressed in Mbps
Green L2 Rate (Mbps) The rate of green Layer-2 data, expressed in Mbps
Yellow Bytes The total number of yellow bytes handled by this regulator
since its creation
Yellow traffic in excess of this maximum is declared red by the
regulator, then dropped.
Yellow Packets The total number of yellow frames handled by this regulator
since its creation
Yellow traffic in excess of this maximum is declared red by the
regulator, then dropped.
Yellow L1 Rate The rate of yellow Layer-1 data, expressed in Mbps
(Mbps) Note:Only applies if the Regulator Working Rate parameter in
Yellow L2 Rate The rate of yellow Layer-2 data, expressed in Mbps
(Mbps) Note:Only applies if the Regulator Working Rate parameter in
Red Bytes The total number of red bytes handled by this regulator since its
creation
Red Packets The total number of red frames handled by this regulator since
its creation
Red L1 Rate (Mbps) The rate of red Layer-1 data, expressed in Mbps

Red L2 Rate (Mbps) The rate of red Layer-2 data, expressed in Mbps

8.4 Setting Up Traffic Shaping

Shaping is a technique which delays some or all packets as a way to bring them into
compliance with a desired bandwidth profile.
The shaping provides a means to control the volume of traffic being sent into a network in
a specified period (bandwidth throttling), or the maximum rate at which the traffic is sent
(rate limiting).
Traffic shaping is commonly applied at the network edges to control traffic entering the
network.

8.5 Understanding Traffic Shaping via H-QoS

Traffic shaping is used to reduce traffic burstiness for an outgoing interface by delaying
some or all frames. It is commonly applied at the network edges to control traffic entering
the network. With shaping, you can control the volume of traffic being sent into a
network during a specified period (bandwidth throttling) or the maximum rate at which
the traffic is sent (rate limiting). Traffic shaping can be performed in both directions: from
the UNI to the network and from the network to the UNI. For details, see "Setting Up
Traffic Shaping" on page 201.
With the GT Performance Element, traffic shaping is achieved through Hierarchical Quality
of Service. Quality of Service (QoS) is a way to optimize and/or guarantee traffic
performance by differentiating between high- and lower-priority traffic and treating each
differently. Traffic is differentiated by means of its assigned Class of Service, based on the
value of the PCP field in its Ethernet frames. With QoS, the latency of high-priority traffic is
improved through accelerated transmission to the network.
Hierarchical QoS (H-QoS) is an extension of traditional QoS because it increases the usable
bandwidth for lower classes of services by recycling the unused bandwidth (tokens) left
over from higher classes of service.
Multiple levels of Class of Service can be created:
The first level is quality of service per Class of Service for a single customer service.
The second level is quality of service for all Classes of Service for a single customer
service.
Because of the possibility to share bandwidth between classes of services, H-QoS is the
preferred approach over traditional QoS. The GT Performance Element includes an MEF
10.3 H-QoS bandwidth sharing implementation.
In the figure below, three classes of service share the same total bandwidth. Bandwidth
sharing enables bandwidth to be handed down from higher classes of service to lower
classes of service.

CIR 3
EIR 3
1
3 CF 3
CBS
0 3
EBS
CIR 2
EIR 2
1
2 CF 2
CBS
0 2
EBS
CIR 1
EIR 1
1
1 CF 1
CBS
0 1
EBS
0 1
CF 0
In this example of MEF token sharing, a coupling flag (CF) is used to share unused
bandwidth (shown as a dotted line) from either Excess Information Rate (EIR) traffic or
Committed Information Rate (CIR) traffic with a lower Class of Service.
The bandwidth profile algorithm that enables sharing unused bandwidth between flows
inside an EVC is defined by the MEF 10.3 (the MEF uses the term envelope).
8.5.1 Setting Up H-QoS

Implementing H-QoS involves multiple configuration tasks, as listed below:
Configure queues to handle the units H-QoS traffic, as described in "Configuring
Queues for H-QoS" on page 204.
Create queuing profiles for each port or LAG on the unit, as described in "Configuring
H-QoSQueuing Profiles" on page 211.
Create envelopes (EVC), which define MEF 10.3 token sharing between flows, as
described in "Creating a Shaping Envelope" on page 212.
Create a policy to refer to a queue profile that maps traffic on a queue, as described
in "Setting Up Ethernet Services" on page 176.
Note: Before you begin, you must ensure that you have pre-determined
how many queues you plan to implement, as well as the parameters of
each.

8.5.2 Understanding BLUE

Each shaper uses BLUE to manage queues based on link use. It maintains a marking
probability (pm) that is used to either mark or drop the frames. If the queue is continually
dropping the frames, pm is increased by the factor d1. If the queue is empty or link is idle,
pm is decreased by the factor d2.
Note: The value of d1 should be set significantly larger than that of d2.
This is because link is underused when congestion management is either
too aggressive or too conservative, but frame loss occurs only when
congestion management is too conservative.
BLUE uses also freeze_time, which determines the time interval between two successive
updates of pm. It allows the changes in the marking probability to take effect before the
value is updated again. The BLUE algorithm is as follows:
Upon Qlen > L1) event:
if ( ( now - last_update) > freeze_time )
pm := pm + d1
last_update := now
Upon Qlen < L2event:
if ( ( now - last_update) > freeze_time)
pm := pm - d2
last_update := now
To disable the BLUE algorithm

You might need to disable BLUE if your test equipment does not support it.
1. Access the page Traffic Shaping Port Shaper.
The Traffic Shaping Port Shaper Configuration page is displayed.
2. Click the traffic shaper Name to edit its settings.
3. Remove the check mark from the Enable box, then click Apply.
8.5.3 Configuring Queues for H-QoS

The GT Performance Element has six dedicated queues per port, as well as 12 user-
assignable queues. When in LAG mode, the queues dedicated to the LAGs ports are
unavailable because the LAGs own queues are used instead.
Note: You do not have to configure a queue for H-QoS if you do not plan
to use the queue.
To configure queues for H-QoS

1. Access the page Traffic Shaping Queue Configuration.

The Traffic Shaping Queue Configuration page opens. All the units queues are listed
in a grid.
2. Select a queue from the list to configure by clicking it.
The queues details are displayed.
3. Use the information in the table below to configure the queue for H-QoS, then click
Apply.
The system returns to the listing of queues in the previous page.
Queue Settings (Traffic Shaping Queue Configuration)
Outgoing Port Traffic from this queue will egress on the port specified here.
Type The type of queue is displayed here (user-assignable, dedicated
or logical).
Name The name assigned to this shaper
Queue Scheduling
Priority (0 to 7) Make a selection from the drop-down list to assign a strict
scheduling priority to this queue: 7 is the highest and 0 the
lowest priority.
Note:When several queues have the same priority, scheduling
is done in a round-robin fashion.
Color Queues without an enabled shaper can have a CIR or EIR
priority. When the queue scheduling color is set to green, the
queue priority is configured for CIR scheduling; when the queue
scheduling color is set to yellow, the queue priority is configured
for EIR scheduling.
Make a selection from the drop-down list to assign a queue
scheduling color to this queue.
Bandwidth Profile Parameters
Shaping State Make a selection from the drop-down list to enable or disable
the shaper. The rate information you provide in this page is
applied to control traffic flow.
Note:The BLUEand queue scheduling features remain
functional when the shaper is disabled.
Shaping Mode The shaping mode determines whether the queue's bandwidth
profile action is performed on the frames as they enter the unit
(ingress) or after an EVC mapping action is applied by a traffic
policy (egress).

For example, if a traffic policy is configured to push a VLAN tag,
setting the shaping mode to Ingress will apply the bandwidth
profile before the VLAN tag is pushed. Setting the shaping mode
to Egress will apply the bandwidth profile to the traffic after the
VLAN tag is pushed.
Make a selection from the drop-down list to indicate either
ingress or egress shaping.
CIR The average shaping rate of green frames, expressed as a
Committed multiple of 125 kbps
Information Rate This is the shaper's average output rate.
Maximum CIR The maximum CIR, expressed in kbps, that the shaper can
achieve by using the shared tokens from its envelope
CBS The shaping burst of green frames, expressed as a multiple of 1
Committed Burst Size kB
Acceptable values range from 1 to 2047 kB.
EIR The average shaping rate of yellow frames, expressed as a
Excess Information multiple of 125 kbps
Rate This is the shaper's average output rate.
Maximum EIR The maximum EIR, expressed in kbps, that the shaper can
achieve by using the shared tokens from its envelope
EBS The shaping burst of yellow frames, expressed as a multiple of 1
Excess Burst Size kB
Acceptable values range from 1 to 2047 kB.
Coupling Flag Enable this check box to allow overflow tokens not used for
Service Frames declared Green can be used as Yellow tokens.
Queue Management Parameters
Maximum Queue The buffer's size, expressed in KB
Size The buffer is used to queue frames for later transmission. If the
BLUE state is enabled, congestion management is ruled
primarily by the BLUE queue management algorithm.
Otherwise, it is managed through simple tail-drops.
Acceptable values range from 16 kB to 1920 kB.
Yellow Threshold When the queue length reaches this threshold, tail-dropping is
performed on new packets with yellow marking.
Acceptable values range from 16 kB to 1800 kB.

BLUE State Select to enable the BLUEqueue management algorithm.
BLUE Queue Full Once the queue fills to the specified percentage, the marking
Threshold probability will be increased.
BLUE Queue Empty Once the queue empties to the specified percentage, the
Threshold marking probability will be decreased.
BLUEMarking This value determines the minimum interval time, expressed in
Probability Freeze microseconds (in increments of 10), between two successive
Time updates of marking probability.
Maximum of 655350 s
BLUEMarking The marking probability is incremented by this value (expressed
Probability as a step percentage) in the event of a buffer overflow.
Increment Note:If this parameter is set to 0, the BLUE algorithm is
disabled.
Note: The percentage value you enter here is only an
approximation; the actual configured value appears to the
right of this field.
Maximum of 25%
BLUE Marking The marking probability is decremented by this value
Probability (expressed as a step percentage) if the link is idle.
Decrement Note: The percentage value you enter here is only an
approximation; the actual configured value appears to the
right of this field.
Maximum of 25%
8.5.4 Viewing Traffic Shaping Queue Statistics

You can view a summary and detailed statistics for each traffic-shaping queue.
To view a summary of statistics for all traffic-shaping queues

1. Access the page Traffic Shaping Queue Statistics.
The Traffic Shaping Queue Statistics page opens. All the units queues are listed in a
grid. For more information on specific parameters, refer to the following table.
Tip:To edit a specific queue or view its details, select the queue from the
list by clicking it.
Tip:To clear the statistics in the Traffic Shaping Queue Statistics page,
click the icon on the right side of the table header.

Traffic Shaping Queue Statistics (Traffic Shaping Queue Statistics)

Name The name assigned to this shaping queue.
Port The name of the port associated with this queue.
Forward The total number of frames that have been forwarded by this
queue.
For details on the frame types, refer to "Traffic Shaping Queue
Detailed Statistics (Traffic Shaping Queue Statistics)".
This value includes frames counted as:
Green forward no delay
Yellow forward no delay
Green forward with delay
Yellow forward with delay
Discard The total number of frames that have been discarded by this
queue.
For details on the frame types, see "Traffic Shaping Queue
Detailed Statistics (Traffic Shaping Queue Statistics)".
Green Discard full
Yellow Discard full
Discard-BLUE The total number of frames that have been discarded by the
queue management algorithm, BLUE. For details on the frame
types, refer to "Traffic Shaping Queue Detailed Statistics (Traffic
Shaping Queue Statistics)".
Green Discard BLUE
Yellow Discard BLUE
CIR Compliant The total number of frames that have been forwarded by this
shaper using the CIR bucket
EIR Compliant The total number of frames that have been forwarded by this
shaper using the EIR bucket
You can view a summary and detailed statistics for each traffic-shaping queue.

To view detailed statistics for a traffic-shaping queue

1. Access the page Traffic Shaping Queue Statistics.
The Traffic Shaping Queue Statistics page opens. All the units queues are listed in a
grid.
2. Select the queue from the list whose statistics you wish to view by clicking it.
The queues details are displayed. For more information on specific parameters, refer
to the following table.
click the Clear button located above the queue details.
Tip:To obtain the latest statistics from the unit, click the Refresh button
located beside the Clear button.
Tip:Select the Poll Every Seconds box and enter the number of seconds
between each time the statistics are automatically refreshed.
Traffic Shaping Queue Detailed Statistics (Traffic Shaping Queue Statistics)
Name The name assigned to this shaping queue
Port Name of the port associated with this queue
Green Forward No The total number of green frames/bytes in the queue when the
Delay queue is near empty, i.e. the green frames/bytes that can be
dropped from the queue without delay
Yellow Forward No The total number of yellow frames/bytes in the queue when the
Delay queue is near empty, i.e. the yellow frames/bytes that can be
dropped from the queue without delay
Green Forward With The total number of green frames/bytes in the queue when the
Delay queue is not empty, i.e. the green frames/bytes that will be
dropped from the queue with delay
Yellow Forward With The total number of yellow frames/bytes in the queue when the
Delay queue is not empty, i.e. the yellow frames/bytes that will be
dropped from the queue with delay
Green Discard Full The total number of green frames/bytes that have been
discarded by this queue
Yellow Discard Full The total number of yellow frames/bytes that have been
discarded by this queue
Green Discard BLUE The total number of green frames/bytes that have been
discarded by the queue management algorithm, BLUE

Yellow Discard BLUE The total number of yellow frames/bytes that have been
discarded by the queue management algorithm, BLUE
CIR Compliant The total number of frames that have been forwarded by this
EIR Compliant The total number of frames that have been forwarded by this

8.5.5 Configuring H-QoSQueuing Profiles

To configure an H-QoS queuing profile
1. Access the page Traffic Shaping Queuing Profile.
The Traffic Shaping Queuing Profile page opens. All profiles created for this unit are
listed in a grid.
2. Do one of these actions:
Select an existing profile from the list by clicking it.
Click Add to create a new profile.

The queuing profiles details are displayed.
Tip: To only display the profiles associated with a single port or LAG, make
a selection in the Port drop-down list at the upper-left corner of the page.
3. Use the information in the table below to configure the H-QoS queuing profile, then
click Apply.
The system returns to the listing of queuing profiles in the previous page.
Queuing Profile Settings (Traffic Shaping Queuing Profile)
Name The name assigned to the queuing profile. The name you enter
can contain alphanumeric characters or special characters such
as underscores and asterisks. Spaces and accented characters
are not supported.
Port Indicate the port or LAG (for ring mode) to which this queuing
profile applies by making a selection in the drop-down list.
Note: You cannot modify this value once the queuing profile
has been saved.
Tip: LAG- 1 is always used in SFP mode for both the GT and GT-S
Performance Elements.
PCP-0 to PCP-7 PCP refers to the Class of Service (CoS) or priority associated
with traffic. There are eight defined CoS, with PCP-0 being the
lowest priority traffic and PCP-7 being the highest.
Specify the queue to which you wish to send traffic assigned to
each CoS by making a selection in the drop-down list. This way,
you indicate the mapping between the queues and the port or
LAG.
Each user-assignable queue is assigned to a single port or LAG.

An error is raised if you attempt to assign queues belonging to
different ports or LAGs. Similarly, an error is raised if the
queuing profile and the set of queues you are assigning do not
have the same port number.
To delete a queuing profile

1. Access the page Traffic Shaping Queuing Profile.
The Traffic Shaping Queuing Profile page opens. All profiles created for this unit are
listed in a grid.
2. Select the profile to delete from the list by clicking it.
3. Click Delete.
The selected queuing profile is permanently deleted; you are not prompted to
confirm your actions.
8.5.6 Creating a Shaping Envelope

To create a shaping envelope
You can create from one to six bandwidth profile envelopes using the six dedicated port
queues that belong to each port. For example, you can create one bandwidth profile
envelope with six queues, six bandwidth profile envelopes with one queue each, or any
combination in between.
The same logic applies to the pool of 12 user-assignable queues. You can create
combinations ranging from 12 bandwidth profile envelopes of one queue, to a single
bandwidth profile envelope of 12 queues.
1. Access the page Traffic Shaping Envelope.
The Traffic Shaping Envelope Configuration page opens. All envelopes created for this
unit are listed in a grid.
2. Do one of these actions:
Select an existing envelope from the list by clicking it.
Click Add to create a new envelope.

The envelopes details are displayed.
Tip: To only display the envelopes associated with a single port, make a
selection in the Port drop-down list at the upper-left corner of the page.
3. Use the information in the table below to configure the envelope, then click Apply.

Traffic Shaping Envelope Settings (Traffic Shaping Envelope)

Name The name assigned to the queuing profile. Acceptable values are
between 1 and 31 characters in length.
The name you enter can contain alphanumeric characters or
special characters such as underscores and asterisks. Spaces
and accented characters are not supported.
Port Indicate the port or LAG (for ring mode) to which this queuing
profile applies by making a selection in the drop-down list.
Note: You cannot modify this value once the queuing profile
has been saved.
Tip: LAG-1 is always used in SFP mode for both the GT and GT-S
Performance Elements.
Type The type of envelope is displayed here (user-assignable,
dedicated or logical) once the envelope has been populated
with queues.
Shaping Mode Make a selection from the drop-down list to indicate either
ingress or egress shaping.
Coupling Flag Enable this check box to share the tokens in this envelope in the
EIR.
Note:All queues in an envelope must have the same coupling
flag value, otherwise an error is raised.
Note: If you do not enable this check box, no bandwidth will be
transferred between the Committed Information Rate (CIR)
and Excess Information Rate (EIR) flows.
Available Queues and Select and rank the queues you wish to include in this envelope.
Ranking List You can assign a maximum of 12 queues to an envelope.
Select the queues according to the ranking you wish to apply,
starting with the first queue is assigned the highest rank, etc.
Note:Queues from different types cannot be added to the
same envelope; only one type per envelope is permitted. In
addition, a queue cannot be added to more than one
envelope.
Note: You can only add queues with an active shaper to an
envelope.
To delete an envelope
1. Access the page Traffic Shaping Envelope.
The Traffic Shaping Envelope Configuration page opens. All envelopes created for this
unit are listed in a grid.

2. Select the envelope to delete from the list by clicking it.

The envelopes details are displayed.
3. Click Delete.
The selected envelope is permanently deleted; you are not prompted to confirm your
actions. The system returns to the listing of envelopes in the previous page.
8.5.7 Configuring a Port Shaper

Use the Traffic Shaping Port Shaper page to view and configure the shaping
parameters assigned to outgoing ports.
To view a summary of the outgoing ports' shaping parameters

The Traffic Shaping Port Shaper Configuration page opens. All the units outgoing
ports are listed in a grid. For more information on specific parameters, refer to the
following table.
Tip:To edit a specific port's bandwidth profile parameters or view its
details, select the port from the list by clicking it.
Traffic Shaping Port Statistics (Traffic Shaping Port Shaper)
Name The name assigned to this outgoing port
State The current state of this outgoing port:enabled or disabled
CIR (kbps) The shaping rate of green frames, expressed as a multiple of 125
kbps
Range:0 to port speed
CBS (KBytes) The shaping burst of green frames, expressed in kilobytes
Range:1 kB to 2047 kB
Use the Traffic Shaping Port Shaper page to view and configure the shaping
parameters of outgoing ports.
To configure a traffic-shaping port shaper

The Traffic Shaping Port Shaper Configuration page opens. All the units outgoing
ports are listed in a grid.
2. Select the outgoing port from the list that you wish to configure by clicking it.
The outgoing ports details are displayed.

3. Make your changes, then click Apply.

Traffic Shaping Port Shaper Configuration (Traffic Shaping Port Shaper)
Enable Click this box to change the current state of this outgoing
port:enabled or disabled.
Port The name assigned to this outgoing port. You cannot modify
this value.
Bandwidth Profile Parameters
Committed The shaping rate of green frames, expressed as a multiple of 125
Information Rate kbps
(kbps) Range:0 to port speed
Committed Burst Size The shaping burst of green frames, expressed in kilobytes with 1
(kBytes) kilobyte granularity
Range:1 kB to 2047 kB
CPU Traffic Debited CPU traffic is never shaped. However, you can check this box to
from CIR have the system debit CPUtraffic from the outgoing ports CIR
bucket.
Note: If you check this box, the bucket value could become
negative.
8.5.8 Viewing Traffic Shaping OAM Queue Statistics

Each outgoing port has five queues reserved for specific Operation, Administration and
Maintenance (OAM) usage. The OAM queues are as follows:
CPU
Monitor1
Monitor2
Packet Generator
Loopback
You can view a summary and detailed statistics for each traffic-shaping OAM queue.
To view a summary of statistics for all traffic-shaping OAM queues

1. Access the page Traffic Shaping Port OAM Queue Statistics.

The Traffic Shaping OAM Queue Statistics page opens. All the units OAM queues are
listed in a grid. For more information on specific parameters, refer to the following
table.
Note: For each column in the table, the number of frames, bytes and the
bit rate (expressed in Mbps) are displayed. The average CIR and EIR bit
rates (expressed in Mbps) that you configured are also shown.
Tip:To edit a specific queue or view its details, select the queue from the
list by clicking it.
Tip:To clear the statistics in the Traffic Shaping OAM Queue Statistics
page, click the icon on the right side of the table header.
Traffic Shaping OAM Queue Statistics (Traffic Shaping Port OAMQueue
Statistics)
Name The name assigned to this shaping OAM queue
Port The name of the port associated with this OAM queue
Forward The total number of packets that have been forwarded by this
OAM queue. For details on the packet types, see "Traffic
Shaping Queue Detailed Statistics (Traffic Shaping Queue
Statistics)".
This value includes packets counted as:
Green forward no delay
Yellow forward no delay
Green forward with delay
Yellow forward with delay
Discard The total number of packets that have been discarded by this
OAM queue. For details on the packet types, see "Traffic
Shaping Queue Detailed Statistics (Traffic Shaping Queue
Statistics)".
This value includes packets counted as:
Green Discard full
Yellow Discard full
CIR Compliant The total number of packets that have been forwarded by this
EIR Compliant The total number of packets that have been forwarded by this

To view detailed statistics for a traffic-shaping queue

1. Access the page Traffic Shaping Port OAMQueue Statistics.
The Traffic Shaping OAM Queue Statistics page opens. All the units queues are listed
in a grid.
2. Select the queue from the list whose statistics you wish to view by clicking it.
The queues details are displayed. For more information on specific parameters, refer
to the following table.
click the Clear button located above the queue details.
Tip:To obtain the latest statistics from the unit, click the Refresh button
located beside the Clear button.
Tip:Select the Poll Every Seconds box and enter the number of seconds
between each time the statistics are automatically refreshed.
Traffic Shaping OAMQueue Detailed Statistics (Traffic Shaping Port OAMQueue
Statistics)
Name The name assigned to this shaping OAM queue
Port Name of the port associated with this OAM queue
Green Forward No The total number of green frames/bytes in the OAM queue
Delay when the queue is near empty, i.e. the green frames/bytes that
can be dropped from the queue without delay
Yellow Forward No The total number of yellow frames/bytes in the OAM queue
Delay when the queue is near empty, i.e. the yellow frames/bytes that
can be dropped from the queue without delay
Green Forward With The total number of green frames/bytes in the OAM queue
Delay when the queue is not empty, i.e. the green frames/bytes that
will be dropped from the queue with delay
Yellow Forward With The total number of yellow frames/bytes in the OAM queue
Delay when the queue is not empty, i.e. the yellow frames/bytes that
will be dropped from the queue with delay
Green Discard Full The total number of green frames/bytes that have been
discarded by this OAM queue
Yellow Discard Full The total number of yellow frames/bytes that have been
discarded by this OAM queue
CIR Compliant The total number of packets that have been forwarded by this

EIR Compliant The total number of packets that have been forwarded by this
8.5.9 Configuring Default Queuing Profiles

The default queuing profiles are used to map traffic to a queue, based on the internal CoS
value assigned to the data frames. Each default queuing profile is associated with an
output port and contains a map of all possible CoS values (0-7) to either one or several
queues.
To edit a default queuing profile

1. Access the page Traffic Shaping Port Default Queuing Profile.
The Traffic Shaping Default Queuing Profile page opens. All default profiles for this
unit are listed in a grid. For more information on specific parameters, refer to the
following table.
2. Select the default queuing profile from the list that you wish to edit by clicking it.
3. Use the information in the table to configure the default queuing profile, then click
Apply.
Traffic Shaping Default Queuing Profile (Traffic Shaping Port Default Queuing
Profile)
Port Indicates the port or LAG (for ring mode) to which this default
queuing profile applies
Note: You cannot modify this value, since default queuing
profiles are fixed.
Tip: LAG- 1 is always used in SFP mode for both the GT and GT-S
Performance Element.
CoS Mappings
PCP-0 to PCP-7 PCP refers to the Class of Service (CoS) or priority associated
with traffic. There are eight defined CoS, with PCP-0 being the
lowest priority traffic and PCP-7 being the highest.
Specify the queue to which you wish to send traffic assigned to
each CoS by making a selection in the drop-down list. This way,
you indicate the mapping between the queues and the port or

LAG.
Each dedicated queue is assigned to a single port or LAG.

8.6 Using Layer-2 Protocol Tunneling

You can use the Layer-2 Protocol Tunneling function to allow the clients Layer-2 Control
Protocol (L2CP) frames to be transparently transported (or to perform other actions such
as dropping and/or forwarding traffic) across an EVC without interfering with the
carrier/operator network and equipment.
For example, the protocol tunneling operates by replacing the protocol's specific
destination MAC address with a multicast address that is transparently transported by
the transit equipment and reinserted in the original destination MAC when the traffic
reaches the destination equipment.
Accedian and the MEF do not use the term tunneling to refer to the same concept:
For the MEF, tunneling means that frames are transparently passed to a given EVC
for transport across the MEN to the destination UNI port(s). This concept is referred
to as forwarding within the framework of Accedians L2CP terminology.
At Accedian, tunneling occurs when the destination MAC is replaced with the well-
known Cisco MAC (or Accedian's equivalent). This concept is not covered by the MEF,
and thus no equivalent exists.
The Protocol Tunneling function works with rules to filter traffic being processed. Each
incoming frame is tested against each rule in order until it finds a match. When there is a
match, the frame is processed according to the mode of operation (Drop, Forwarding,
Tunneling or Peering). If there is no match with any rule, the frame is discarded.
In tunneling mode, tags are unconditionally pushed to processed frames, with user-
configurable fields for Ethertype, VLAN tags and PCP/CFI. When the unit is in forwarding
mode, you can set it to perform VLAN tagging on the processed frames. In forwarding
mode, the following operations are supported:
None: frames are forwarded unmodified.
Push: frames are forwarded with an extra VLAN tag added. The tag is defined by the
VLAN ID, PCP and CFI fields and the Ethernet type is set to the value specified by the
VLAN Ethertype field.
Pop: frames are forwarded, with the VLAN tag stripped. This mode is only available
when VLAN Filtering is enabled, as tags cannot be removed from non-tagged frames.
Replace: frames are forwarded with their VLAN tag replaced. The replacement tag is
defined by the VLAN ID, PCP and CFI fields and the Ethernet type is set to the value
specified by the VLAN Ethertype field. This mode is only available when VLAN Filtering
is enabled, as tags cannot be replaced in non-tagged frames.
To view a list of all existing L2PT rules access the page Traffic L2PT Configuration. For
an example of the display, see the figure below. For more information on specific

parameters, refer to the table "L2PT Configuration (Traffic L2PT Configuration) " on
page 223.
Traffic L2PT Configuration
8.6.1 Viewing Statistics for L2 Tunnel Rules

To view statistics for all L2PT rules
1. Access the page Traffic L2PT Statistics.
Layer-2 Protocol Tunneling Frame Statistics (Traffic L2PT Statistics)
Name The unique name assigned to the rule
Dropped The total number of dropped frames by this rule since its
creation. This counter is incremented under the following
circumstances:
The rule is set for drop operation mode and a matching frame
was received.
The rule is set for tunnel operation mode and a matching frame
was received, but there was a VLAN ID mismatch, i.e. the VLAN
tags in the frame could not be matched to any of the VLAN
groups in the rule's list.
Tunneled The total number of tunneled frames by this rule since its
circumstance:
The rule is set for tunnel operation mode and a matching frame

was received on the incoming port and tunneled (had its
destination MAC replaced, had the required VLAN tags added
and was sent to the outgoing port).
Note: If there are multiple VLAN groups in the VLAN list, this
counter is incremented for each frame transmitted on the
outgoing port.
De-tunneled The total number of de-tunneled frames by this rule since its
creation. This counter is incremented when the following event
occurs:
The rule is set for tunnel operation, and a matching frame was
received on the outgoing port then de-tunneled (i.e., restored
to its original state and sent to the incoming port).
Forwarded The total number of frames forwarded by this rule since its
circumstance:
The rule is set for forward operation and a matching frame was
received on the incoming port and forwarded, unmodified, to
the outgoing port.
Peered The total number of frames peered by this rule since its
circumstance:
The rule is set for peer operation and a matching frame was
received on the incoming port and sent to the software layers
for further processing.
8.6.2 Setting Up a Layer-2 Tunnel

You can define up to 254 Layer-2 Protocol Tunneling (L2PT) rules. L2PT is configurable on a
per-port basis, as described below.
L2PT frames are transported transparently if the unit does not have a Tunneling rule for
the service. If an L2PT rule with the Operation Mode set to Tunnel has been created, the
L2PT frames entering the unit via the rules Outgoing Port (using the VID configured in the
rule) will be terminated and forwarded for processing as described in the rule. Otherwise,
these frames are treated as service traffic.
To specify the ports to which L2PT applies

1. Access the page Traffic L2PT Configuration.
The L2PT Configuration page appears. All ports are listed in the Layer-2 Protocol
Tunneling Port States frame at the top of the page.

2. For each port on which you want to enable L2PT, select its corresponding box by
clicking it.
Note:You can select both traffic ports and management ports.
3. Click Apply.
To add or edit an L2PT rule

1. Access the page Traffic L2PT Configuration.
The tunneling rules are displayed in a grid.
2. Click the Add button to add a new L2PT rule or click the Name of an existing rule to
edit its settings.
The L2PT Configuration page appears.
3. Complete all required fields, then click Apply.
L2PT Configuration (Traffic L2PT Configuration)
Enable L2PT Rule Select this box to enable the processing of the Layer-2 Control
Protocols according to L2PT rules. Use this field to enable or
disable a rule without actually deleting it.
Catchall Rule Select this box to make this L2PTrule a catchall rule.
Catchall rules operate on all frames that were not matched by a
specific rule, and can be set for either the Forward or Drop
operation modes.
L2PT Rule Name The name assigned to the L2PT rule
Operation Mode This parameter controls how the L2PT rule handles traffic
associated with the specified protocol. The operation mode you
select can be one of the following:
Drop: Frames matching the specific rule are dropped.
Forward: Frames are sent unaltered from the incoming to

the outgoing port. Optionally, EVC mapping can be enabled
on forwarding rules (see "EVC Mapping " below).
Tunnel: When received on the specified client port, frames

matching the specific rule have their destination MAC
address replaced by the MAC address supplied in the rule's
parameters. When received on the specified network port,
frames matching the specific rule have their original
destination MAC address replaced.

Peer: The frames are sent to software layers for further

processing.
L2PT frames are transported transparently if the unit does not
have a Tunneling rule for the service. If an L2PT rule with the
Operation Mode set to Tunnel has been created, the L2PT
frames entering the unit via the rules Outgoing Port (using the
VID configured in the rule) will be terminated and forwarded for
processing as described in the rule. Otherwise, these frames are
treated as service traffic.
Protocol Indicate the Layer-2 Control Protocol to be processed by a
specific rule by making a selection from the drop-down list
Replacement MAC The multicast MAC address to use as a replacement when
protocol tunneling is performed
The following replacement MAC addresses can be used:
Cisco: A replacement MAC address of 01:00:0C:CD:CD:D0 is
used. Because this MACaddress is unique, it can only be
used once per protocol.
Accedian: A replacement MAC address of

01:15:AD:CC:xx:yy is used. Because this replacement MAC
address has variable elements, it can be used on multiple
rules. The variable elements allow matching to a specific
rule when a tunneled frame is received on the network
port.
The variables in the MACaddresses are set as follows:
xx: The unique ID specified in the configuration (see the
Unique ID parameter below). When creating a tunnel
between two units, the unique ID is used to match the
replacement frames going both ways on the network port.
As such, it is important that the matching rules on both
endpoints be assigned the same unique ID.
yy: The protocol ID. This value is automatically generated

depending on the Layer-2 control protocol handled by the
rule.
Incoming Port Indicate which incoming port the rule will use by making a
selection in the drop-down list.
The incoming port is considered to be the port where the
Layer-2 control protocols will be received.

Outgoing Port Indicate which outgoing port the rule will use by making a
The outgoing port is considered to be the port where the
tunneled frames, containing a replacement destination MAC
address, will be transmitted.
Unique ID Select the ID of a rule to use when performing tunneling by
making a selection in the drop-down list. This value is used
when building the replacement destination MAC address if the
Accedian multicast address is used.
Note: The same ID value must be used on both sides when
performing tunneling between a pair of units.
VLAN Filtering
Enable Select this box to enable the filtering of incoming frames with
matching VLAN ID and Ethertype for this L2PT rule.
Only the frames with a VLAN ID and Ethertype matching the
ones specified in the VLAN ID range, PCP, CFI and Ethertype are
accepted.
Ethertype The VLANEthertype accepted by this specific rule in the inbound
Layer-2 Control Protocol frames
VLAN ID Range Indicate the VLAN IDs that this specific rule accepts in the
inbound Layer-2 Control Protocol frames.
If you want to filter on a single VID, enter the same value in both
the From and To fields.
PCP Indicate the Priority Code Point that this rule accepts in the
inbound Layer-2 Control Protocol frames by making a selection
in the drop-down list.
07: For a specific priority
All: To accept any PCP value
CFI Indicate the Canonical Format Indicator that this rule accepts in
the inbound Layer-2 Control Protocol frames by making a
01: For a specific priority
All: To accept any CFI value

EVC Mapping
EVC Mapping Mode Note:Only applies to the "Forward" operation mode.

Select a mapping mode by making a selection in the drop-down
list:
None: Frames are forwarded unmodified.
Push: Frames are forwarded with an extra VLAN tag added.

This tag is defined by the VLAN ID, PCP and CFI fields; the
Ethernet type is set to the value specified by the VLAN
Ethertype field.
Pop: Frames are forwarded with the VLAN tag stripped. This
mode is only available when VLAN Filtering is enabled, as
tags cannot be removed from non-tagged frames.
Replace: Frames are forwarded with their VLAN tag

replaced. The replacement tag is defined by the VLAN ID,
PCP and CFI fields and the Ethernet type is set to the value
specified by the VLAN Ethertype field. This mode is only
available when VLAN Filtering is enabled, as tags cannot be
replaced in non-tagged frames.
VLAN Ethertype Note:Only applies to the "Forward" operation mode.

Select the Ethertype of the tag inserted in the forwarded frame
by making a selection in the drop-down list.
VLAN 1 Ethertype Note:Only applies to the "Tunnel" operation mode.
Select the Ethertype of the first tag inserted in the tunneled
frame by making a selection in the drop-down list.
VLAN 2 Ethertype Note:Only applies to the "Tunnel" operation mode.
Select the Ethertype of the second tag inserted in the tunneled
frame (for Q-in-Q) by making a selection in the drop-down list.
VLAN List Note:Only applies to the "Tunnel" operation mode.
Indicate the VLAN tags to insert in the tunneled frames. The
syntax is a list of comma-separated groups formatted as
vlan1:vlan2.
Entry of the second tag (Q-in-Q) is optional. For example, if you
wanted to single-tag tunneled frames with VLAN ID 3, and
double-tag frames with VLAN IDs 56 and 2288, you would
specify: 3, 5:6, 22:88.
Note: The frames are duplicated for each entry in the VLAN list.
In the example above, three frames would be transmitted on

the network port for each incoming frame matching the rule on
the client port.
Note:There should be at least one entry in the list, as tunneling
untagged frames is currently not supported.
VLAN ID Note:Only applies to the "Forward" operation mode.
The VLAN tags to insert in the forwarded frames when the mode
is set to Pop or Replace.
CoSMapping
Mode Note:Only applies to the "Tunnel" operation mode, or to the
"Forward" operation mode when the EVCmapping mode is set
to "Push".
This field allows you to control the PCP and CFI fields of the
forwarding and tunneling rules.
The following operations are supported:
Map: The PCP and CFI fields of the processed frame are
replaced by the ones specified in the PCP and CFI fields. The
Map operation is available when the forwarding mode is
set to either Push or Replace, and is mandatory when using
tunneling mode.
Preserve: The PCP and CFI fields of the processed frame are
copied from the ones in the incoming frame. This mode is
only available when the forwarding mode is set to Replace.
PCP Note:Only applies to the "Tunnel" operation mode, or to the

to "Push".
Indicate the Priority Code Point (PCP) mapped to the processed
frame in CoS Map mode by making a selection in the drop-
down list.
Range: 07.
CFI Note:Only applies to the "Tunnel" operation mode, or to the
to "Push".
Indicate the Canonical Format Indicator (CFI) mapped to the
processed frame in CoS Map mode by making a selection in the
drop-down list.
The CFI is defined by 1 bit in the Ethernet frame.

8.7 Monitoring Traffic

This section describes how to set up the GT Performance Element for monitoring pass-
through traffic using the monitor ports. The units have a versatile monitoring capability
that can be tailored to the specific troubleshooting you may need. The GT Performance
Elementcan use up to two monitor ports. Any of the four traffic ports on the unit can be
defined as a monitor port.
There are two basic modes of monitoring:
Separate monitor port for each traffic direction: One monitor port is used for the
client-side port, while the other is used for the network-side port. This mode is used
when a fixed relative timing monitoring is required, i.e. the receive time on the user
traffic port being monitored and the transmit time on the monitor port is fixed and
very small (0.8s at 1000Mbps).
Combined traffic mode using a single monitor port: In this mode, the traffic from
both directions is monitored on the same monitor port. It is used for analyzing
bidirectional communication.
You can select and direct the traffic to monitor by using filter rules. In many cases, the
ability to select the traffic to monitor is essential when the frame analyzer is not able to
sustain the complete traffic bandwidth present on the user connection. This is even more
important with 1000Mbps link. However, in situations where the traffic is known to not
exceed the capability of the frame analyzer, all the traffic can be directed to a monitor port
by using a catch-all filter rule.
To set up a monitor port

1. Access the page Traffic Monitors.
2. Click a monitor Name to edit its settings.
3. Select the Enable check box.
4. Select the Destination port to assign to this monitor, then click Apply.
5. Repeat all previous steps to set up a second monitor port, if needed.

Name Name of the monitor
Enabled Enable or disable this monitor.
Destination Destination port associated to this monitor, i.e. physical port to
which the monitored traffic will be sent

To set up the unit for monitoring traffic using the monitor ports
1. Access either Traffic Filters L2 Filters, Traffic Filters IPv4 Filters or Traffic
VLAN VID Sets.
2. Add a new filter or select an existing filter to catch the type of traffic you want to
monitor. Refer to "Defining Filters" on page 167 for more information on how to
setup L2, IPv4 or VIDSet filters.
3. Access the page Traffic Policies and click the entry in the list corresponding to the
port for which you want to monitor traffic (it is the incoming traffic for that port that
will be monitored).
4. Set the policy for monitoring the traffic caught with the filter you configured above:
(Enable policy, Filter type to L2 Filter , Filter you defined in the previous steps,
Permit traffic, Enable monitoring, Monitor port to Monitor-1 or to Monitor-2), then
click Apply. Refer to the table "Policy Configuration (Traffic Policies)" on page 190
for more information on how to set up the policy.

9 Monitoring Network Performance with

Ethernet OAM
The unit allows for monitoring network performance using the Ethernet OAM standard
protocol. This monitoring technique is presented in the following sections:
9.1 Setting Up an OAM Instance 232
9.2 Viewing OAM Events 235
9.3 Viewing OAM Status 236
9.4 Viewing OAM Statistics 239

9.1 Setting Up an OAM Instance

Before using Ethernet OAM functions or enabling a loopback, you must create an OAM
instance, upon which the loopback is created.
Note: You do not have to enable L2PT rules in order to forward untagged
OAM frames directly to the CPU for processing, provided that an OAM
instance has been created on the incoming port.
To set up an OAM instance

1. Access the page OAM Configuration.
A summary of all OAM instances that have been set up is displayed.
2. Click the Add button to add a new OAM instance or click the Name of an existing
OAM instance to edit its settings.
3. Select the Loopback Enable box to enable this loopback instance.
4. Complete the other required fields, then click Apply.

OAM Instances (OAM Configuration)
Name The name given to the OAM instance
OAM Instance Name
OAM State Enables the passive or active OAM 802.3ah protocol for this
Enable OAM Protocol OAM instance. An active instance immediately starts sending
information OAMPDUs associated with the discovery process.
Note:This field does not indicate that an OAM peer has been
successfully discovered.
OAM Mode Passive: Listens for OAMPDUs and replies once it starts
Active Mode / receiving them
Passive Mode Active: Immediately searches for an OAM peer by sending
OAMPDUs
Port Name The port used by this OAM instance
Port
Max OAM PDU Size Maximum frame size for the OAM instance, expressed in bytes.
This value enables you to limit the impact of the extra OAM
traffic on a link that is already heavily loaded.

This Unit Supports When enabled, the unit responds to loopback requests from
Loopback the OAM peer.
This Unit Supports When enabled, the unit issues event OAMPDUs when needed.
Events
This Unit Supports When enabled, the unit responds to OAMPDUs requests.
Variable Responses
Number of Events The number of times an event is re-transmitted to ensure its
Re-transmitted reception by the peer
Note:This setting is valid only if This Unit Supports Events is
enabled.
Errored Frame Event The threshold setting that defines the number of frame errors
(EFE) that must be detected in a given period to trigger the
Threshold and transmission of an event
Window The window setting defines the time of the period. Expressed in
seconds.
A frame error is an error detected at Layer2 or at the MAC level.
This can be caused by various types of errors including, but not
limited to the following: CRC errors, short frames, long frames,
etc.
Errored Frame Period The threshold setting that defines the number of frame errors
Event (EFPE) that must be detected in a given period to trigger the
Threshold and transmission of an event
Window The window setting defines the number of frames that make up
a period. Using a number of frames instead of a time period, as
in EFE, means that this event is generated based on the ratio of
bad frames versus good frames.
limited to: CRC errors, short frames and long frames.
Errored Frame The threshold setting that defines the number of frame errors
Seconds Summary that must be detected in a given period to trigger the
Event (EFSSE) transmission of an event
Threshold and An errored frame second is a one-second period in which at
Window least one frame was bad. In other words, this event is generated
when the number of seconds with any number of bad frames is
greater than or equal to the threshold during a period defined
by the window.
The window setting defines the time, in seconds, of the period.

limited to the following: CRC errors, short frames, long frames,
etc.

9.2 Viewing OAM Events

To view a summary of all event exchanges on an OAM connection
1. Access the page OAM Events.
2. For complete details on transmitted and received events, click the OAM instance
Name in the list.
OAM Events (OAM Events)
Name The name of the OAM instance
Txm Event The number of OAM events transmitted
Txm Duplicate The number of transmitted OAM events that were duplicated
Rcv Event The number of OAM events received
Rcv Duplicate The number of received OAM events that were duplicated
Transmitted Event Shows details of the transmitted event notification:
Notifications
Event number
Transmit time
Sequence number
Event type
Received Event Shows details of the received event notification:

Notifications
Event number
Receive time
Sequence number
Event type: EFE, EFPE, EFSSE
Event values: EFE, EFPE or EFSSE fields

9.3 Viewing OAM Status

To view a summary of the status of each OAM instance
1. Access the page OAM Status.
2. For details OAM status information, click the OAM instance Name in the list.
For more information on specific parameters, refer to the following table. As an additional
reference, see IEEE802.3ah.
OAM Status (OAM Status)
Name The name of the OAM instance
Discovery The current state of the OAM Discovery function. The states
listed correspond to those within the discovery state diagram
(see Figure 57-5 of IEEE802.3).
LINK_FAULT
ACTIVE_SEND_LOCAL
PASSIVE_WAIT
SEND_LOCAL_REMOTE
SEND_LOCAL_REMOTE_OK
SEND_ANY
Local
Local Flags A string of seven bits corresponding to the Flags field in the
Flags most recently transmitted OAMPDU
The seven LSB bits are expressed as a hexadecimal value. For
example, a hexadecimal value of 0x0004 converted to binary is
0000100: first bit = 0, second bit = 0, third bit = 1, etc.
The first bit corresponds to the Link Fault bit in the Flags
field.
The second bit corresponds to the Dying Gasp bit in the

Flags field.
The third bit corresponds to the Critical Event bit in the

Flags field.

The fourth bit corresponds to the Local Evaluating bit in

the Flags field.
The fifth bit corresponds to the Local Stable bit in the Flags
field.
The sixth bit corresponds to the Remote Evaluating bit in

the Flags field.
The seventh bit corresponds to the Remote Stable bit in

the Flags field.
Local Revision The value of the Revision field in the Local Information TLV of
Info TLV Revision the most recently transmitted information OAMPDU
Note: The revision number indicates the number of times that
the configuration for the local OAM instance has been
modified.
Parser State / Mux A string of three bits corresponding to the State field of the
State most recently transmitted Information OAMPDU. The first and
second bits correspond to the Parser Action bits in the State
field. The third bit corresponds to the Multiplexer Action bit in
the State field.
Note: These states will change when a loopback is enabled.
Vendor OUI The value of the OUI variable in the Vendor Identifier field of the
most recently transmitted information OAMPDU. This value is
updated upon reception of a valid frame.
Vendor-Specific Info The value of the Vendor-Specific Information field of the most
recently received information OAMPDU. This value is updated
upon reception of a valid frame with the following:
Destination field value equal to the reserved multicast
address for Slow_Protocols
Length or Type field value equal to the reserved Type for

Slow_Protocols
A Slow_Protocols subtype value equal to the subtype

reserved for OAM
The OAMPDU code equal to the Information code
The frame contains a Local Information TLV.

Remote
Remote Flags A string of seven bits corresponding to the Flags field in the
Flags most recently received OAMPDU
The seven LSB bits are expressed as a hexadecimal value. For
example, a hexadecimal value of 0x0004 converted to binary is
0000100: first bit = 0, second bit = 0, third bit = 1, etc.
The first bit corresponds to the Link Fault bit in the Flags
field.
The second bit corresponds to the Dying Gasp bit in the

Flags field.
The third bit corresponds to the Critical Event bit in the

Flags field.
The fourth bit corresponds to the Local Evaluating bit in

the Flags field.
The fifth bit corresponds to the Local Stable bit in the Flags
field.
The sixth bit corresponds to the Remote Evaluating bit in

the Flags field.
The seventh bit corresponds to the Remote Stable bit in

the Flags field.
Remote Revision The value of the Revision field in the Local Information TLV of
Info TLV Revision the most recently received information OAMPDU. This value is
updated upon reception of a valid frame.
Parser State / Mux A string of three bits corresponding to the State field of the
State most recently received information OAMPDU. The first and
second bits correspond to the Parser Action bits in the State
field. The third bit corresponds to the Multiplexer Action bit in
the State field.
Note: These states will change when a loopback is enabled.
Vendor OUI The value of the OUI variable in the Vendor Identifier field of the
most recently received information OAMPDU
Vendor-Specific Info The value of the Vendor Specific Information field of the most
recently received information OAMPDU

9.4 Viewing OAM Statistics

To view a summary of the statistics of each OAM instance
1. Access the page OAM Statistics.
2. For detailed OAM statistics, click the OAM instance Name in the list.
OAM Statistics (OAM Statistics)
Name The name given to the OAM instance
Rcv OAMPDU The number of OAMPDUs received by this instance, all types
combined: info, var request, var response, loopback etc.
Txm OAMPDU The number of OAMPDUs transmitted by this instance, all types
combined: info, var request, var response, loopback etc.
Rcv Info OAMPDUs The number of Info OAMPDUs received by this instance
Txm Info OAMPDUs The number of Info OAMPDUs transmitted by this instance
Receive
Unsupported Codes A count of OAMPDUs received that contain an OAM code that is
not supported by the device. This counter is incremented upon
reception of a valid frame with the following:
address for slow protocols
Length Or Type field value equal to the reserved Type for

slow protocols
A slow protocols subtype equal to the subtype reserved for

OAM
An OAMPDU code for a function that is not supported by

the device
Generalized and non-resettable, this counter has a maximum
increment rate for slow protocol frames: no more than 10
frames are transmitted in any one-second period.
Information A count of OAMPDUs received that contain the OAM
Information code. This counter is incremented upon reception
of a valid frame with the following:



slow protocols

OAM
The OAMPDU code equals the OAM Information code and

is supported by the device.
Unique Event A count of the OAMPDUs received that contain the Event
Notification code. This counter is incremented upon reception

slow protocols

OAM
The OAMPDU code equals the Event Notification code.
The Sequence Number is equal to the Sequence Number of

the last received Event Notification OAMPDU.
Duplicate Event A count of the OAMPDUs received that contain the Event
Notification code. This counter is incremented upon reception

slow protocols


OAM

the last received Event Notification OAMPDU.
Loopback Control A count of OAMPDUs received that contain the Loopback
Control code. This counter is incremented upon reception of a
valid frame with the following:

slow protocols

OAM
The OAMPDU code equals the Loopback Control code and

Variable Request A count of OAMPDUs received that contain the Variable
Request code. This counter is incremented upon reception of a
valid frame with the following:
DestinationField equal to the reserved multicast address
for slow protocols
LengthOrType value equal to the reserved Type for slow

protocols

OAM
The OAMPDU code equals the Variable Request code and is

supported by the device.

Variable Response A count of OAMPDUs received that contain the Variable
Response code. This counter is incremented upon reception of
a valid frame with the following:

slow protocols

OAM
The OAMPDU code equals the Variable Response code and

Organization Specific A count of OAMPDUs received that contain the Organization
Specific code. This counter is incremented upon reception of a
valid frame, with:

slow protocols

OAM
The OAMPDU code equals the Organization Specific code

and is supported by the device.
Transmit
Unsupported Codes A count of transmitted OAMPDUs that have unsupported
codes. This counter is incremented when a request service
primitive is generated within the OAM sublayer with an OAM

code for a function that is not supported by the device.
Information A count of transmitted OAMPDUs containing the OAM
Information code. This counter is incremented when a request
service primitive is generated within the OAM sublayer with an
OAMPDU code indicating an Information OAMPDU.
Unique Event A count of transmitted OAMPDUs containing the OAM Unique
Event code. This counter is incremented when a request service
primitive is generated within the OAM sublayer.
A Slow_Protocols subtype equal to the subtype reserved
for OAM
The Sequence Number is not equal to the Sequence

Number of the last transmitted Event Notification
OAMPDU.
Duplicate Event A count of transmitted OAMPDUs containing the OAM
Duplicate Event code. This counter is incremented when a
request service primitive is generated within the OAM sublayer.

the last transmitted Event Notification OAMPDU.
frames shall be transmitted in any one-second period.
Loopback Control A count of transmitted OAMPDUs containing the Loopback
Control code. This counter is incremented when a request
OAM code indicating a Loopback Control OAMPDU.

Variable Request A count of transmitted OAMPDUs containing the Variable
Request code. This counter is incremented when a request
OAM code indicating a Variable Request OAMPDU.
Variable Response A count of transmitted OAMPDUs containing the Variable
Response code. This counter is incremented when a request
OAM code indicating a Variable Response OAMPDU.
Organization Specific A count of transmitted OAMPDUs containing the Organization
Specific code. This counter is incremented when a request
OAM code indicating an Organization Specific OAMPDU.

10 Monitoring Network Performance with

Service OAM
The unit allows for monitoring network performance using a proprietary Service OAM
technology and a standard Service OAM protocol (IEEE 802.1ag). These monitoring
techniques are presented in the following sections:
10.1 Using the Performance Assurance Agent 246
10.2 Using Service OAM 262
10.3 Using Service Availability 298
10.4 Using the Two-Way Active Measurement Protocol (TWAMP) 306
10.5 Setting Up TWAMP Generator Measurements 307
10.6 Viewing TWAMPGenerator Session Results 312
10.7 Viewing the TWAMPGenerator Session Status 316
10.8 Setting Up a TWAMP Reflector 318
10.9 Viewing TWAMP Reflector Statistics 319

10.1 Using the Performance Assurance Agent

The Performance Assurance Agent (PAA) is a hardware-assisted active-measurement
function that computes Layer-2 or Layer-3 (IPv4 UDP and IPv6 UDP) network delay
(latency), delay variation (jitter), frame/packet loss and continuity checks.
Two units with matching settings communicate with each other using measurement
samples to collect data and measure system performance. A measurement sample is a
frame/packet containing timing and sequence information. When such a frame/packet
arrives at its destination, measurements (delay, delay variation and frame/packet loss)
can be taken. The PAA operates continuously.
The PAA is capable of concurrently testing and maintaining multiple flows of active
probes. The characteristics of the test frames/packets for each flow are set to match the
Layer-2 (PCP value of the VLAN tag) or Layer-3 (IP ToS/DSCP value) characteristics of the
services being monitored. These frames/packets may be independently directed to
different peers or to the same peer, using a different class of service (CoS) and/or VLAN ID
as appropriate. Up to two VLAN tags can be specified (.1Q-in.1Q).
The PAA can be configured in a point-to-point or point-to-multi-point fashion. In other
words, you can enable a single PAA instance to exchange data with another PAA instance,
or enable it to communicate with several PAA instances simultaneously. Typically, the PAA
instance would be configured between the network-side port of the first unit and the
network-side port of the second unit (point-to-point) in order to get live latency, jitter and
frame/packet loss measurements. It is also possible to select a client-side port on a given
unit for PAA measurements when it is directly connected to another unit, or through a
network device in the same point-to-point fashion.
10.1.1 Setting Up a Probe

To configure a PAAprobe
1. Access the page SOAM PAA Configuration.
A summary of all PAA probes is displayed.
2. Click Add to create a new probe or click the probe name to edit an existing probe.

Note: The fields available for configuration vary depending on the probe
type and operation mode you select.

PAA Configuration (SOAM PAA Configuration)

General
Index The unique identifier assigned to the probe
Name The name assigned to the PAA probe
Type The type of probe:
Layer-2: The probe operates at Layer2.
UDP_IPv4: The probe operates using UDP over IPv4.
UDP_IPv6: The probe operates using UDP over IPv6.
Operation Mode Specifies whether a probe generates (Source) PAA samples,

Mode collects PAAsamples (Sink) or does both operations (Bi-Dir)
Packet Size The size of PAA samples to take

Note:The size value indicated here does not include protocol
headers (VLAN tags, UDP, IP or Ethernet) or the four FCS bytes.
Minimum value: 66
Layer-2 maximum value: 1500
Maximum value for UDP over IPv4: 1472
Maximum value for UDP over IPv6: 1452
Sampling Period The time period to elapse between each issuing of PAA samples
Sampling Range: 50 to 600,000 (steps of 1 millisecond)
Enable PAA Probe PAA probe may be enabled or disabled.
State The probe's current state:
Enabled: Enabled by configuration
Disabled: Disabled by configuration
Associating: Enabled and looking for peer
Associated: Enabled peer index resolved
Local and Peer Indexes

Local Index The probe's local identifier
Acceptable index values range between 1 and 300. .
Note:To automatically allocate the next sequentially-available

local identifier to the PAA instance, enter "0" for the local
identifier or simply leave the field blank.
Remote Index The remote peer identifier
When 0 is specified, the remote peer identifier is discovered
dynamically based on the probe name in the association phase.
Layer-2 Parameters (Layer-2 Probes Only)
Destination MAC The peer MAC address
Address When set to FF:FF:FF:FF:FF:FF, the unit is in auto-discovery
Destination mode and will automatically determine the peer MAC address
based on the PAA name (provided the PAA name is the same on
both units).
Port Name The outgoing port used by this probe
VLAN 1 Encapsulation Encapsulates Layer-2 PAA frames into a VLAN
VLAN 2 Encapsulation Encapsulates Layer-2 PAA frames into a VLAN-in-VLAN. VLAN2
represents the inner VLAN.
Note:Only applies when VLAN1 encapsulation is enabled.
VLAN 1 ID The first VLAN ID
When enabled, Layer-2 PAA frames are encapsulated into the
specified VLAN.
VLAN 2 ID The second VLAN ID. When enabled, Layer-2 PAA frames are
encapsulated into a second VLAN.
Note:Only applies when VLAN1 encapsulation is enabled.
VLAN 1 Type The Ethertype of the first VLAN: C-VLAN, T-VLAN or S-VLAN
VLAN 2 Type The second VLAN Ethertype: C-VLAN, T-VLAN or S-VLAN
Note:Only applies when VLAN 2 encapsulation is enabled.
VLAN 1 Priority The first VLAN's priority bits
VLAN 2 Priority The second VLAN's priority bits
Layer-2 Parameter Validation (Layer-2 Probes Only)
Validate Tx/Rx Validate Tx/Rx VLAN 1 ID enables validating the transmitted
VLAN 1 ID VLAN 1 ID with the IDvalue that was received.
Couple Tx/Rx If you expect the transmitted and received values to be equal,

VLAN 1 ID enable Couple Tx/Rx VLAN 1 ID.
Rx VLAN 1 ID If you expect a different received value, enter the value in the
Rx VLAN 1 ID field. Range:0-4095
Validate Tx/Rx Validate Tx/Rx VLAN 1 priority enables validating the
VLAN 1 Priority transmitted VLAN 1 priority with the priority that was received.
VLAN 1 Priority enable Couple Tx/Rx VLAN 1 priority.
Rx VLAN 1 Priority If you expect a different received value, enter the value in the
RxVLAN 1 priority field. Range:0-7
Validate Tx/Rx Validate Tx/Rx VLAN 2 ID enables validating the transmitted
VLAN 2 ID VLAN 2 ID with the IDthat was received.
VLAN 2 ID enable Couple Tx/Rx VLAN 2 ID.
Rx VLAN 2 ID If you expect a different received value, enter the value in the
RxVLAN 2 ID field. Range:0-4095
Validate Tx/Rx Validate Tx/Rx VLAN 2 priority enables validating the
VLAN 2 Priority enable Couple Tx/Rx VLAN 2 priority.
RxVLAN 2 priority field. Range:0-7
EVC Fault Propagation (Layer-2 Probes Only)
Enable Fault Use this PAA probe's status in fault propagation.
Propagation The port configuration's Fault Propagation value must be
Enabled and set to One-Way EVC mode for the fault to be
propagated to the opposite port.
Propagate on Port The EVC client port to which the MEP status should be
propagated
Note:This parameter is ignored if the port you select has not
been set up to perform EVC fault propagation.
UDP Parameters (Probes with UDP over IPv4 or IPv6 Only)
Destination IP Peer IPv4 or IPv6 Destination address
Address
Destination
Source UDP Port The source UDP port. The default value is 8793.

Destination UDP Port The destination UDP port. The default value is 8793.
A port cannot be defined as the UDPport here if it is already
being used for any of the following features:
A Layer-3 PAA instance
TWAMP
Layer-3 RFC-2544 Generator
Layer-3 RFC-2544 Test Suite
Layer-3 Y.1564
SAT Protocol
Diff-Serv CodePoint The DSCP class selector. The expected length is 6 bits.
(DSCP)
Explicit Congestion The ECN value. You can associate an ECN value with the PAA
Notification (ECN) packets, thereby simulating ECN in the customer network.
The ECN bits are the last two bits of the IP ToS field.
Range: 0-3
VLAN 1 Priority First VLAN priority bits. This can be used to associate a priority
value for the first VLAN.
Range: 0-7
UDP and UDP IPv6 Parameter Validation (Probes with UDP over IPv4 and over IPv6
Only)
Validate Tx/Rx DSCP Validate Tx/Rx DSCP enables validating the transmitted DSCP
Couple Tx/Rx DSCP value with the value that was received.
Expected RX DSCP If you expect the transmit and receives values to be equal,
enable Couple Tx/Rx DSCP.
If you expect a different received value, enter this value in the
Expected RX DSCP field.
Range:0-63
Validate Tx/Rx Traffic Validate Tx/Rx Traffic Class enables the validation of
Class transmitted traffic class value versus the received value.
Couple Tx/Rx If you expect the transmit and receives values to be equal,
Traffic Class enable Couple Tx/Rx Traffic Class.
Rx Traffic Class (DSCP) If you expect a different received value, enter the value in the
RXTraffic Class DSCP field.

Range:0-63
Validate Tx/Rx Validate Tx/Rx VLAN 1 Priority enables validating the
Couple Tx/Rx If you expect the transmit and receives values to be equal,
VLAN 1 Priority enable Couple Tx/Rx VLAN 1 Priority.
RxVLAN 1 Priority field.
Range:0-7
Continuity
Packet Loss The reference period, expressed in milliseconds, for the
Reference Period continuity measurements
This value must be at least 10 times the value of the Sampling
Period.
Packet Loss The threshold, expressed as a percentage, at which an Excessive
Threshold Packet Loss (EPL) alarm is triggered
Continuity Check The number of consecutive sampling periods without receiving
Threshold any peer samples that must occur before declaring a Continuity
Loss alarm
Minimum value: 4
Maximum value: 50% of the total number of samples in the
reference period
Default value:4
One-Way
Reference Period The reference period, expressed in milliseconds, for one-way
measurements
Period.
Maximum Delay The one-way delay allowed for each sample in the Reference
Period
This value is used in conjunction with the Delay Threshold
(samples) value to trigger the alarm PAA_OW_DELAY_ALERT.
Delay Threshold The number of consecutive samples exceeding the Maximum
(Samples) Delay that are allowed before declaring the one-way delay alarm
for this Reference Period
Average Delay The average one-way delay is calculated for the samples during

Threshold the reference period. For example, for a reference period of
10seconds, the average is calculated from samples taken during
the last 10seconds.
Exceeding the threshold triggers the alarm PAA_OW_AVG_
DELAY_ALERT.
Maximum Delay The maximum one-way delay variation threshold to monitor
Variation during a test period
This value is used in conjunction with the Delay Variation
Threshold (samples) value to trigger the alarm PAA_OW_DV_
ALERT.
Delay Variation The number of consecutive samples exceeding the Maximum
Threshold (Samples) Delay Variation that are allowed before triggering the one-way
delay variation alarm for this Reference Period
Average Delay The average one-way delay variation is calculated for the
Variation Threshold samples during the reference period.
Exceeding the threshold triggers the alarm PAA_OW_AVG_DV_
ALERT.
Two-Way
Reference Period The reference period, expressed in milliseconds, for two-way
measurements
Period.
Maximum Delay The two-way delay allowed for each sample in the Reference
Period
This value is used in conjunction with the Delay Threshold to
trigger the alarm PAA_TW_DELAY_ALERT.
Delay that are allowed before triggering the two-way delay
alarm for this Reference Period
Average Delay The average two-way delay is calculated from samples during
Threshold the reference period.
Exceeding the threshold triggers the alarm PAA_TW_AVG_
DELAY_ALERT.
Maximum Delay The maximum two-way delay variation threshold to monitor

Threshold to trigger the alarm PAA_TW_DV_ALERT.
Threshold Delay Variation that are allowed before triggering the two-way
Average Delay The average two-way delay variation is calculated from samples
Variation Threshold during the reference period.
Exceeding the threshold triggers the alarm PAA_TW_AVG_DV_
ALERT.
IGMP (These parameters are valid only for a sink probe with UDP-over-IPv4 configured
with a multicast destination address.)
Reference Period The reference period for IGMP measurements. This period must
(msec) be a multiple of the One-Way Reference Period value.
This parameter is valid only if the One-Way Join Period is not 0.
Possible values, expressed in milliseconds:
0 (default): No IGMP measurements
Minimum: One-way reference period x 10
Maximum: One-way reference period x 9000
One-Way Join Period If this parameter is not set to 0, IGMP join and leave delay
(msec) measurements are performed for this period (during which one-
way and packet loss samples are collected).
This value should represent how long measurements are to be
collected before issuing an IGMP Leave for each period.
0 (default): Constant, no join and leave measurements
Minimum: 10 x sampling period
Maximum: One-way reference period (5 x sampling

period)
Maximum Join Delay The maximum join delay objective

Minimum: 100milliseconds
Maximum: One-way join period
Join Delay Threshold This value is the maximum number of consecutive join delay

samples allowed, over and above the maximum join delay.
Once this value is exceeded, the Join Delay Nbr Threshold
value is incremented.
Possible values, expressed in number of samples:
Minimum: 1
Maximum: (One-way join period) / (Sampling period)
Join Average Delay The maximum join average delay

Threshold Possible values, expressed in milliseconds:
Maximum: One-way join period
Maximum Leave The maximum leave delay objective

Delay Possible values, expressed in milliseconds:
0 (default): No IGMP measurements
Maximum: (One-way reference period) (One-way join

period)
Leave Delay This value is the maximum number of consecutive leave delay
Threshold samples allowed, over and above the maximum leave delay.
Once this value is exceeded, the Leave Delay Nbr Threshold
value is incremented.
Possible values, expressed in number of samples:
Minimum: 1
Maximum: (One-way reference period One-way join

period) / (Sampling period)
Leave Average Delay The maximum leave average delay

Threshold Possible values, expressed in milliseconds:
Maximum: (One-way reference period) (One-way join

period)

10.1.2 Deleting a Probe

To delete a PAAprobe
1. Access the page SOAM PAA Configuration.
2. Click the name of the probe you want to delete.
3. Click Delete.
CAUTION: Deleting a PAA probe instance will also delete all SA metrics
that use this PAA probe instance as the metric source.
10.1.3 Viewing Probe Status

To view the status of all PAA probes
1. Access the page SOAM PAA Status.
2. Click a probe name to view its detailed information.

PAA Status (SOAM PAA Status)
Name The name of the probe
Probe Name
State The probe's current state. Possible values are:
Disabled: Disabled by configuration.
Associating: Enabled and looking for peer.
Associated: Enabled peer index resolved.

It also gives detailed state information about local and remote
clock synchronization status that is used for one-way
measurements.
Peer Address The address of its peer PAA probe (L2 and L3)
Status Codes The current state (active or inactive) for all PAA alarms for the
following status codes:
CC: Continuity Check

EPL: Excessive Packet Loss
OD: One-Way Delay
OAD: One-Way Average Delay
ODV: One-Way Delay Variation
OAV: One-Way Average Delay Variation
TD: Two-Way Delay
TAD: Two-Way Average Delay
TDV: Two-Way Delay Variation
TAV: Two-Way Average Delay Variation
10.1.4 Viewing Probe Results

To view a summary of all PAA probe results
1. Access the page SOAM PAA Results.
2. Click a probe name to view detailed results of a probe.

PAA Results (SOAM PAA Results)
Current Results for The name of the probe
Probe
Probe Name
State The probe's current state. Possible values are:
Disabled: Disabled by configuration
Associating: Enabled and looking for peer
Associated: Enabled peer index resolved

It also gives detailed state information about local and remote
clock synchronization status that is used for one-way
measurements.

Period The number of periods that have elapsed since the probe was
enabled
Results Codes A summary of the results for the following parameters:
PL: Packet Loss Ratio
OADV: One-Way Average Delay Variation
TADV: Two-Way Average Delay Variation
Packet Loss
Period Provides the results for the previous and current periods
The current period is indicated to the right of Packet Loss.
Number of Samples The total number of samples taken during the period
Loss Ratio The percentage of samples that were lost during the period
Number of Gaps The total number of gaps that have been detected from the
sequence of packets (or frames) that were received during the
period
Largest Gap Size The total number of gaps that have been detected from the
sequence of packets (or frames) that were received during the
period
One-Way Delay
Instantaneous Delay The one-way instantaneous delay value, expressed in
microseconds. This is the latest one-way delay value measured
when the window was last refreshed.
The current period is indicated to the right of the One-Way
Delay.
Nbr Samples The total number of samples taken during the period
Minimum Delay The one-way delay of the fastest sample over the period,
expressed in microseconds
Maximum Delay The one-way delay of the slowest sample taken over the period,
Average Delay The average delay of the samples taken during the reference

period, expressed in microseconds
Nbr Threshold The number of times the one-way delay has exceeded the value
Exceeded of the Maximum Delay parameter
One-Way Delay Variation
Instantaneous DV The one-way instantaneous delay variation value, expressed in
microseconds. This is the latest one-way delay variation
measured when the window was last refreshed.
The current period is indicated to the right of the One-Way
Delay Variation.
Minimum DV The one-way delay variation of the samples with the smallest
delay skew over the period, expressed in microseconds
Maximum DV The one-way delay of the samples with the highest delay skew
over the period, expressed in microseconds
Average DV The average one-way delay variation of the samples during the
reference period, expressed in microseconds
Nbr Threshold The number of times the one-way delay variation has exceeded
Exceeded the value of the Maximum DV parameter
Two-Way Delay
Instantaneous Delay Two-way instantaneous delay, expressed in microseconds. This
is the latest two-way delay measured when the window was last
refreshed.
The current period is indicated to the right of the Two-Way
Delay.
Minimum Delay The two-way delay of the fastest samples over the period,
Maximum Delay The two-way delay of the slowest samples over the period,
Average Delay The average two-way delay of the samples during the reference
Nbr Threshold The number of times the two-way delay has exceeded the value

Two-Way Delay Variation
Instantaneous DV The two-way instantaneous delay variation, expressed in
microseconds
The current period is indicated to the right of the Two-Way
Delay Variation.
Minimum DV The two-way delay variation of the samples with the smallest
Maximum DV The two-way delay of the samples with the highest delay skew
Average DV The average two-way delay variation of the samples during the
Nbr Threshold The number of times the two-way delay variation has exceeded
Exceeded the value of the Maximum DV parameter
IGMP Join Delay
Instantaneous Delay The latest IGMP join delay value, expressed in microseconds,
that was measured when the window was last refreshed
Period Gives the results for the previous and current periods
The current period is to the right of the IGMP Join Delay.
Nbr Samples The total number of samples contained in the period
Minimum Delay The IGMP join delay of the fastest sample over the period,
Maximum Delay The IGMP join delay of the slowest sample over the period,
Average Delay The average delay over the period, expressed in microseconds
Nbr Threshold The number of times the IGMP join delay has exceeded the
Exceeded value of the Maximum Join Delay
IGMP Leave Delay
Instantaneous Delay The latest IGMP leave delay value, expressed in microseconds,
that was measured when the window was last refreshed

The current period is to the right of the IGMP Leave Delay.
Minimum Delay The IGMP leave delay of the fastest sample over the period,
Maximum Delay The IGMP leave delay of the slowest sample over the period,
Average Delay The average delay over the period, expressed in microseconds
Nbr Threshold The number of times the IGMP leave delay has exceeded the
Exceeded value of the Maximum Leave Delay
VLAN 1
ID Mismatch 0: The VLAN 1 ID received is equal to the expected value.
1:The VLAN 1 ID received is different from the expected value.
ID Expected In the event of an IDmismatch, the VLAN 1 ID that was expected
ID Received In the event of an IDmismatch, the VLAN 1 ID that was received
Priority Mismatch 0: The VLAN 1 priority received is equal to the expected value.
1:The VLAN 1 priority received is different from the expected
value.
Priority Expected In the event of a priority mismatch, the VLAN 1 priority that was
expected
Priority Received In the event of a priority mismatch, the VLAN 1 priority that was
received
VLAN 2 (Layer-2 Probes Only)
ID Mismatch 0: The VLAN 2 ID received is equal to the expected value.
1:The VLAN 2 ID received is different from the expected value.
ID Expected In the event of an IDmismatch, the VLAN 2 ID that was expected
ID Received In the event of an IDmismatch, the VLAN 2 ID that was received
Priority Mismatch 0: The VLAN 2 priority received is equal to the expected value.
1:The VLAN 2 priority received is different from the expected
value.
Priority Expected In the event of a priority mismatch, the VLAN 2 priority that was
expected
Priority Received In the event of a priority mismatch, the VLAN 2 priority that was

received
DSCP (Probes with UDP-over-IPv4 Only)
DSCP Mismatch 0: The DSCP value received is equal to the expected value.
1:The DSCP value received is different from the expected value.
DSCP Expected In the event of a DSCP mismatch, the DSCP value that was
expected
DSCP Received In the event of a DSCP mismatch, the DSCP value that was
received
Traffic Class (Probes with UDP-over-IPv6 Only)
Traffic Class 0: The traffic class value received is equal to the expected value.
Mismatch 1:The traffic class value received is different from the expected
value.
Traffic Class Expected In the event of a traffic class mismatch, the traffic class value
that was expected
Traffic Class Received In the event of a traffic class mismatch, the traffic class value
that was received

10.2 Using Service OAM

This section describes the IEEE 802.1ag Service OAM function and how to set it up in
your Metro Ethernet Network to perform end-to-end monitoring.
Service OAM (or CFM Connectivity Fault Management) encompasses fault management
and performance management capabilities of the GT Performance Element.
The following figure shows an overview of Service OAM.
Overview of Service OAM
The diagram below shows a typical setup scenario for Service OAM.
Typical Setup Scenario for Service OAM

10.2.1 Setting Up CFM

The steps required to set up Connectivity Fault Management (CFM) are:
Set up Maintenance Domains (MD).
Set up Maintenance Associations (MA), also known as Maintenance Entity Groups

(MEG).
Set up Maintenance Endpoints (MEP).

Once these are set up, you can use Service OAM for performing the following fault
management functions:
Link Trace Messages. See "Setting Up Link Trace Messages" on page 277.
Loopback Messages. See "Setting Up Loopback Messages" on page 278.

For viewing MEP information, see also "Viewing MEP Status" on page 271, "Viewing the
MEP Database" on page 273 and "Viewing MEP Statistics" on page 275. You can also set
up delay measurements, packet loss measurements and synthetic loss measurements.
If required, you can set up CFM defaults. See "Setting Up CFM Defaults" on page 296.
If required, you can configure the unit as a VSP reflector. See "Setting Up VSP" on page
295.
Viewing CFM Instances

To view CFM instances
1. Access the page SOAM CFM Stack.
A list of all CFM instances and their settings is displayed. For more information on
specific parameters, refer to the following table.
CFM Stack (SOAM CFM Stack)
Port The port on which MEPs have been configured
VID The VLAN ID to which the Maintenance Point is attached, or 0, if
there is no VLANID
Level The MD level (or MEG level) of the Maintenance Point
Possible values: 0-7
Dir The direction in which the MEP faces on the port
MD idx The index of the Maintenance Domain with which the MEP is
associated

MA idx The index of the MA (or MEG) with which the MEP is associated
MEPID The MEPID of the MEP
MAC Address The MAC address of the Maintenance Point
Setting Up Maintenance Domains (MD)

There are eight pseudo MDs defined by default, one for each level, named Y.1731 level 0
to Y.1731 level 7. These MDs exist only to simplify the integration of MEGs for Y.1731 with
the CFM MIB which requires MDs. Y.1731 uses MEG-IDs which are MAIDs without an MD
name. User interfaces show the pseudo MD name, but this name is not included in Y.1731
CCM's MEG-ID. It is not possible to delete pseudo MDs.
To set up a Maintenance Domain

1. Access the page SOAM CFM MD.
A listing of all existing Maintenance Domains is displayed.
2. Click the Add button to add a new Maintenance Domain or click the name of an
existing Maintenance Domain to edit its settings.

Maintenance Domain (SOAM CFM MD)
Index Unique index assigned to the Maintenance Domain
Name Format The format of the Maintenance Domain name
Character String: RFC-2579 display string, except that the
character codes 031 (decimal) are not used
DNS-Like Name: Domain Name-like string, a globally-

unique text string derived from a DNS name
The name format must be the same for the other endpoints.
Name Unique name for the Maintenance Domain
MD Name
Level Maintenance Level of the Maintenance Domain
MHF Creation Indicates whether the management entity can create MHFs for

VIDs on which no Up MEP is configured. Possible values are:
None: No MHFs can be created.
Default: Create MHFs if there is no lower active MD level; or

if there is a MEP at the next active MD level on the port.
Explicit: Create MHFs only if there is an MEP at the next

active MD level on the port.
Sender ID Permission What, if anything, is to be included in the Sender ID TLV

transmitted in CCMs, LBMs, LTMs and LTRs
The available values are:
None: None
Chassis: Chassis ID and chassis subtype
Manage: Management Address
Chassis and Manage: Chassis ID, subtype and Mgmt

Address
Deleting a Maintenance Domain (MD)

To delete a maintenance domain
1. Access the page SOAM CFM MD.
2. Click the name of the MD instance to delete.
3. Click Delete.
CAUTION: Deleting an MD will also delete all instances

(e.g. MA/MEG) that use this MD.
Setting Up Maintenance Associations (Maintenance Entity Groups)

Before setting up an MA (also referred to as a MEG), you must first set up the MD to
which you want the MA/MEG to belong. Maintenance Associations (MA) are discussed in
IEEE 802.1ag. Maintenance Entity Groups (MEG) are discussed in ITU-Y Y.1731.
To set up a Maintenance Association or Maintenance Entity Group

1. Access the page SOAM CFM MA/MEG.
A listing of all Maintenance Associations / Maintenance Entity Groups is displayed.

2. Click the Add button to add a new Maintenance Association or Maintenance Entity
Group or click the name of an existing Maintenance Association or Maintenance
Entity Group to edit its settings.

Maintenance Association (SOAM CFM MA/MEG)
MA/MEG Index Unique index value assigned to the Maintenance Association or
Index Maintenance Entity Group
MD Index Unique index value assigned to the Maintenance Domain

MD Maintenance Domain for this Maintenance Association or
Maintenance Entity Group
Name Format The format of the Maintenance Association or Maintenance
Entity Group name
String: RFC-2579 display string
ICC-Based: ITU Carrier Code format
Name Name of this Maintenance Association or Maintenance Entity

MA/MEG Name Group
Note:To comply with ICC standards, the MEG name you enter
should contain a maximum of 13 characters. The system
supports MEG names up to 45 characters in length, however. If
the MEG's name exceeds 13 characters, the CCM is generated
with a non-compliant MEG ID field.
Level Maintenance Level of the Maintenance Association or
CCM Interval Required time interval between Continuity Check Messages
(CCM). Expressed in milliseconds.
Default:1000 milliseconds
MHF Creation Indicates whether the management entity can create MHFs for
VIDs on which no Up MEP has been configured


Explicit: Create MHFs only if there is a MEP at the next

Defer: Use the Maintenance Domain parameter to

determine MHF creation.
Sender ID Permission What, if anything, is to be included in the Sender ID TLV

transmitted in CCMs, LBMs, LTMs and LTRs
None: None
Manage: Management address
Chassis & Manage: Chassis ID, subtype and management

address
Defer: Determined by the domain configuration or system

configuration
VLAN Type VLAN type associated with this Maintenance Association or

None: The association is not attached to a VLAN and the
content of the VLAN ID list is ignored
C-VLAN: Customer VLAN (typically inner tag)
S-VLAN: Service VLAN (typically outer tag)
T-VLAN: Tunnel VLAN (inner or outer tag)
VLAN ID List Alist of the VLANs associated with this Maintenance Association
or Maintenance Entity Group
If you leave the VLAN ID field empty, the association is not
attached to a VLAN and the VLAN type is set to None implicitly.
MEPID List A comma-separated list of all the MEPs that are associated with
this Maintenance Association or Maintenance Entity Group
If this Maintenance Association or Maintenance Entity Group

has a MEPwith CSF enabled (see SOAM CFM MEP
Configuration), a maximum of only two MEPIDare permitted in
the list, since ETH-CSFis point-to-point. Consequently, the
MA/MEG MEPID list can only be edited if ETH-CSF is disabled.
To delete a Maintenance Association (Maintenance Entity Groups)

1. Access the page SOAM CFM MA/MEG.
2. Click the name of the Maintenance Association or Maintenance Entity Group name
to delete.
3. Click Delete.
CAUTION: Deleting a MA/MEG will also delete all instances (e.g. MEP) that
use this MA/MEG.
Setting Up Maintenance Endpoints

Before setting up a MEP, you must first set up its MA/MEG. Maintenance Endpoints
(MEP) are discussed in IEEE 802.1ag.
To set up a Maintenance Endpoint

1. Access the page SOAM CFM MEP Configuration.
A listing of all existing maintenance association endpoints is displayed.
2. Click the Add button to add a new MEP or click the MEPID of an existing MEP to edit
its settings.
3. Complete the required fields, then click Apply to start the CCM.
Note: Although the local MEP will start sending CCM frames immediately,
continuity errors will be raised. You must configure the other endpoint for
valid results to be displayed.
Maintenance Endpoint (SOAM CFM MEP Configuration)
Index The index automatically assigned to the Maintenance
association End Point
MA/MEG Name The name of the maintenance association (or MEG)
MEPID Maintenance association End Point Identifier (MEPID) for this
Maintenance association
This value is an integer, unique to each MA, that identifies a

specific MEP in CCM frames.
Port The port or CFM interface used by this MEP
Direction The direction in which the MEP faces on the Bridge port. Refer
to IEEE802.1ag for more information.
Up: The MEP resides in a Bridge that transmits CFM PDUs
toward and from the direction of the Bridge Relay Entity.
Down: The MEP resides in a Bridge that receives CFM PDUs

and transmits them toward the LAN.
MEPName The name of the Maintenance association End Point

Active The administrative state of the MEP:
Checked (Yes): The MEP is to function normally.
Unchecked (No): The MEP is to cease functioning.

Note:When deactivating a MEP, you must also deactivate all
DMM, SLM and Frame Loss instances that use this MEP. Doing
so will stop the unit from sending DMM and SLM frames and
prevent the units from detecting unwanted alarms, such as
CCM alarms.
CCI Enable Indicates whether or not the MEP generates CCM messages:
Checked (Enabled): The MEP generates CCM messages.
Unchecked (Disabled): The MEP does not generate CCM

messages.
CCM Sequence When enabled, a MEP transmits CCMs with a sequence number
Number that increases by one for each CCM. When disabled, a MEP
transmits CCMs with a sequence number set to zero.
Note:A peer MEP should have the sequence number enabled
to allow a local MEP to perform CCM-based frame loss
measurements.
Primary VID The Primary VLAN ID of the MEP. This is always one of the VLAN
VLAN IDs assigned to the MEP's MA/MEG. The value 0 indicates that
either the Primary VLAN ID is that of the MEP's MA/MEG, or
that the MEP's MA/MEG is not associated with a VLAN ID.
CCM, LTM and CSF Priority parameter for CCMs, LTMs and CSFs transmitted by the
Priority MEP. The possible values are 0-7, with 7 being the highest value
allowed to pass through the Bridge Port for any of this MEP's

VLAN IDs.
Default value: 7 (highest priority)
Lowest Priority Lowest priority defect that is allowed to generate a CFM Fault
Defect Alarm Alarm
Fault Notification The period of time, expressed in milliseconds, for which defects
Alarm Time must be present before a Fault Alarm is issued
Fault Notification The period of time, expressed in milliseconds, for which defects
Reset Time must be absent before resetting a Fault Alarm
EVC Client Interface (The EVC client is the client of a service.)
Interface Status Enables or disables the interface status TLV on a MEP.
TLVEnable
For a down MEP, the client interface status is used for this
TLV.
For an up MEP, the status is obtained from the port on

which the MEP was created.
CSF Enable Enables this MEP to transmit Ethernet Client Signal Failure (ETH-
CSF) to its peer MEP upon the detection of a failure or defect
event in the Ethernet client signal. That port should also be set
up to perform EVC fault propagation and that MEP must also be
enabled for fault propagation for this parameter to take effect.
Note: A MA/MEG with more than two endpoints cannot be
used and will raise an error.
Enable Fault Enables the use of this MEP's status in fault propagation
Propagation
Client Interface The EVC client port to which the MEP status should be
propagated
Note:This parameter is ignored if the port you select has not
been set up to perform EVC fault propagation.
To delete a Maintenance Endpoint

1. Access the page SOAM CFM MEP.
2. Click the name of the MEP to delete.
3. Click Delete.
CAUTION: Deleting a MEP will also delete all instances (e.g. LTM, LBM)
that use this MEP.

Viewing MEP Status

To view maintenance association end point (MEP) status
1. Access the page SOAM CFM MEP Status to view the status summary of all
MEPs.
2. Click any MEPID to view detailed status of this MEP.

MEP Status (SOAM CFM MEP Status)
Index Index assigned to the Maintenance association End Point
MEPID Identifier for the Maintenance association End Point
DB Link to this MEP's database.
Next LBM Sequence Next sequence number/transaction identifier to be sent in a
Number loopback message
Note: The sequence number restarts at zero once the counter
has reached its limit.
Next LTM Sequence Next sequence number/transaction identifier to be sent in a link
Number trace message
Note: The sequence number restarts at zero once the counter
has reached its limit.
Fault Notifications The possible values are:
State
Reset
Defect
Report defect
Defect reported
Defect clearing
Highest Defect The highest defect priority sent. The possible values are:
Priority
None
RDI CCM
MAC status
Remote CCM

Error CCM
Xcon CCM
AIS
Defect
RDI The latest CCM received by this MEP from a remote MEP
CCM RDI containing the Remote Defect Indication (RDI) bit
Active (A) or Inactive (I)
MAC The last CCM received by this MEP from a remote MEP indicates
MAC Status that the transmitting MEP's associated MAC is reporting an
error status via the Port Status TLV or Interface Status TLV.
R-CCM Indicates whether the MEP is not receiving CCMs from a MEP in
Remote CCM its configured list. Active (A) or Inactive (I).
E-CCM Indicates whether the MEP is receiving invalid CCMs

Errored CCM Active (A) or Inactive (I)
X-CCM Indicates whether the MEP is receiving CCMs that could be from
Cross-Connect CCM some other MA
AIS Indicates whether Y.1731 Alarm Indication Signal (AIS) PDUs are
Received AIS received
EPL Indicates whether some packet loss measurement defect is
Excessive Packet Loss active (A) or inactive (I) for that MEP
EDM Indicates whether some delay measurement defect is active (A)
Excessive Delay or inactive (I) for that MEP
C-LOS Indicates whether Y.1731 Client Signal Fail (CSF) LOS PDUs are
Received C-LOS received
C-FDI Indicates whether Y.1731 Client Signal Fail (CSF) FDI PDUs are
Received C-FDI received
C-RDI Indicates whether Y.1731 Client Signal Fail (CSF) RDI PDUs are

Received C-RDI received
N-SLM Indicates whether near-end synthetic loss messages is active (A)
or inactive (I) for that MEP
F-SLM Indicates whether far-end synthetic loss messages is active (A)
or inactive (I) for that MEP
Loopback (The status of the latest loopback request initiated from that MEP)
Loopback Request Indicates whether the loopback request process is active for
that MEP
Latest Start Time Indicates the time at which the latest loopback request was
initiated from that MEP
Latest End Time Indicates the time at which the latest loopback request from
that MEP was completed or was stopped
Nbr LBM Requested Indicates the number of loopback messages requested
Nbr LBM Sent Indicates the number of loopback messages transmitted
Nbr LBR Received Indicates the number of loopback replies received
LBR with Bad MSDU Indicates the number of loopback replies received whose
content did not match the corresponding LBM
Nbr LBR Duplicated Indicates the number of loopback replies received with a
duplicate LBR sequence number
Packet Loss Ratio Indicates the packet loss ratio evaluated during the latest
request
Nbr Packets Lost Indicates the number of loopback replies missing
Nbr Gaps Indicates the number of gaps evaluated inside the LBR stream
Largest Gap Size Indicates the number of missing frames for the largest gap
Nbr LBR Out of Order Indicates the number of LBRs received whose sequence number
did not match the expected value
Viewing the MEP Database

The MEPdatabase gives you information about remote MEPs.
To view database information for MEPs

1. Access the page SOAM CFM MEP Status.
2. Click the MEP database identifier for which you want to view a summary.

3. Click any MEPID to view detailed database information.

MEP Database (SOAM CFM MEP Status [Database])
MEP Index Maintenance association End Point index of the local unit
MEPID Maintenance association End Point identifier of the remote
Remote MEPID MEP whose information from the MEP Database is to be
returned
State The operational state of the remote MEP IFF state machines
Remote MEP State Possible values are:
Idle
Start
Failed
OK
RDI The state of the RDI bit in the last received CCM. Possible values
Latest CCM RDI are:
True: The RDI bit was set.
False: If no CCM message was received.
Mac Address The MAC address of the remote MEP

Latest Failed-OK Time The time at which the IFF Remote MEP state machine last
entered either the failed or OK state
Port Status TLV The value of the port status TLV received in the last CCM from
the remote MEP (see section 21.5.4 Port Status TLV of 802.1ag
for details)
--- (none 0): No CCM was received or no port status TLV
was received in the last CCM.
Blocked (1)
Up (2)
Interface Status TLV The value of the interface status TLV received in the last CCM
from the remote MEP (see section 21.5.5 Interface Status TLV of
802.1ag for details)

--- (0): No CCM was received or no interface status TLV was
received in the last CCM.
Up (1)
Down (2)
Testing (3)
Unknown (4)
Dormant (5)
Not Present (6)
Lower Layer Down (7)
Viewing MEP Statistics

To view MEP statistics
1. Access the page SOAM CFM MEP Statistics.
A summary of statistics of all MEPs is displayed.
2. Click any MEPID to view detailed statistics of this MEP.
MEP Statistics (SOAM CFM MEP Statistics)
Index Index assigned to the Maintenance association End Point
MEP Index
MEPID Maintenance association End Point Identifier
CCM Sent Indicates the number of connectivity check messages sent by
CCM this MEP
CCM Received Indicates the number of connectivity check messages received

CCM by this MEP
RDI Sent Indicates the number of connectivity check messages sent by

CCM with RDI this MEP with the RDI bit set
RDI Received Indicates the number of connectivity check messages received

CCM with RDI by this MEP with the RDI bit set
CCM Seq Error Indicates the total number of out-of-sequence CCMs received
CCM Received from all remote MEPs
Sequence Errors
LBM Indicates the number of loopback messages sent and received
by this MEP
LBR Indicates the number of loopback responses sent and received
by this MEP
LTM Indicates the number of linktrace messages sent and received
by this MEP
LTR Indicates the number of linktrace responses sent and received
by this MEP
CSF Indicates the number of client signal failure messages sent and
received by this MEP
DMM Indicates the number of delay measurement messages sent and
received by this MEP per VLAN priority
DMR Indicates the number of delay measurement responses sent
and received by this MEP per VLAN priority
SLM Indicates the number of synthetic loss messages sent and
SLR Indicates the number of synthetic loss responses sent and
Unexpected LBR Indicates the total number of LBRs received when no loopback
request is active for that MEP
LBR Out of Order Indicates the total number of valid, out-of-order loopback
replies received
LBR with Bad MSDU Indicates the total number of LBRs received whose Mac Service
Data Unit did not match (except for the OpCode) that of the
corresponding LBM
Unexpected LTR Indicates the total number of LTRs received when no linktrace
request is active for that MEP
LTR Dropped Bad Indicates the total number of link trace replies that were
MAC dropped because of an invalid MAC address

10.2.2 Setting Up Link Trace Messages

Link Trace Messages (LTM) are multicast frames transmitted by a MEP to track the path
(hop-by-hop) to a destination MEP. Each receiving MEP sends a trace route reply directly
to the originating MEP, and regenerates the trace route message. LTM are discussed in
IEEE 802.1ag.
To start the link trace messages

1. Access the page SOAM CFM MEP LTM.
All existing link trace information for maintenance association endpoints is displayed.
2. Click the MEPID of the MEP for which you want to start the LTM.
3. Complete the required fields, then click Start.

MEP Link Trace (SOAM CFM MEP LTM)
MEP Index Index of the Maintenance association End Point
Index
Target Type Link trace target by remote MEPID or MAC address.
Remote MEPID Targeted remote MEPID. The remote MEP MAC address is
R-MEPID resolved into the local MEP database.
LTR Received The number of link trace responses received by this MEP
MAC Address Target MAC address. Only unicast MAC addresses are valid for
link trace target address.
TTL Link trace time to live.
Range: 0255
If it is initially set to 0, no response should be received.
Set FDB Only Flag Enables the LTM to set the flag "UseFDBonly" (IEEE 802.1ag) or
the flag "HWonly" (Y.1731)
Bottom of Table
LTM Sequence Sequence number used by the latest link trace request initiated
Number from that MEP
Next Seq. #

Target MAC Address Target MAC address used by the latest link trace request
Target MAC
TTL Link trace time to live received in link trace responses.
F Forwarded. Indicates that the responder maintenance point did
forward the LTM.
T Terminal MEP. Indicates that the responder maintenance point
is a MEP.
Action Indicates how the responder system processes frames targeted
for the destination address specified by the LTM
RlyHit: The LTM reached a maintenance point whose MAC
address matches the target MAC address.
RlyFDB: The Egress Port was determined by consulting the

Filtering Database.
RlyMPDB: The Egress Port was determined by consulting

the MIP CCM Database.
TLV Type Indicates which Type Length Values (TLVs) are included in link
trace responses
TLV Value The TLV values included in link trace responses
10.2.3 Viewing Link Trace Messages Information

To view the link trace message information
1. Access the page SOAM CFM MEP LTM.
2. Click the MEPID of the MEP for which you want to view LTM information.
For more information on specific parameters, refer to the "MEP Link Trace (SOAM CFM
MEP LTM)" table above.
10.2.4 Setting Up Loopback Messages

Loopback messages are unicast frames transmitted by a MEP. Sending a high volume of
loopback messages can test the bandwidth, reliability or jitter of a service. A MEP can
send a loopback to any MEP or MIP in the service. Loopback messages are discussed in
IEEE 802.1ag.

To start the loopback messages

1. Access the page SOAM CFM MEP LBM.
All existing loopback messages for maintenance association endpoints are displayed.
2. Click the MEPID of the MEP for which you want to start the LBM.
3. Complete the required fields, then click Start.

MEP Loopback (SOAM CFM MEP LBM)
MEP Index Index assigned to the Maintenance association End Point
Index
Active Indicates whether a loopback request is active for that MEP
Target Type Loopback target by remote MEPID or MAC address
Remote MEPID Target remote MEPID. The remote MEP MAC address is
resolved into the local MEP database.
MAC Address Target MAC address. Only Unicast MAC address are valid for link
trace target address.
VLAN Priority Indicates how to determine the LBM VLAN priority value:
CCM Priority: Use the same priority that MEP CCMs.
Specific: Use a specific value specified by the Priority field.
Priority The value assigned to the LBM VLAN priority

Range: 0-7
VLAN Drop Eligibility Value for LBM VLAN drop eligibility bit. Checking this box sets
the DEI bit to 1.
Nbr Message Number of LBMs to send
Interval The interval, expressed in milliseconds, between LBMs
Range: 1005000
Data TLV Indicates whether LBMs should include a Data Type Length
Value (TLV)
None: No Data TLV included
Incremental: A Data TLV with incremental byte values is

included.
Pattern: A Data TLV based on a user data pattern is

included.
Length Amount of data, expressed in bytes, inside the data TLV

Range: 11488 bytes
Pattern User data pattern for the Data TLV
Format: ASCII characters
Bottom of Table
Loopback Request Indicates whether a loopback request is active or inactive for
that MEP
Target MAC Address The target MAC address used for the latest loopback request
Latest Start Time The time the latest loopback request was initiated for that MEP
Latest End Time The time the latest loopback request has completed or was
stopped for that MEP
Next Seq. # The sequence number for the next LBM initiated from that MEP
Nbr LBM Requested The number of LBM requested for the latest loopback request
LBM Requested
Nbr LBM Sent The number of LBM sent for the latest loopback request. When
the loopback is not active, this number should be the same as
the number of LBM requested. If not, this implies the loopback
request was stopped by a management command.
Nbr LBR Received The number of loopback replies (LBR) received for the latest
LBM Received loopback request
LBR with Bad MSDU The number of LBR received with a content that did not match
the corresponding LBM for the latest loopback request
Nbr LBR Duplicated The number of LBR received with a sequence number already
received for the latest loopback request
Packet loss ratio The computed packet loss ratio for the latest loopback request
Nbr Packets Lost The number of missing LBR for the latest loopback request
Nbr Gaps The number of times a sequence of LBRs went missing during
the latest loopback request
Largest Gap Size The longest uninterrupted sequence of missing packets that

was detected during the most recent loopback request
Nbr LBR Out of Order The number of times an LBR was received during the latest
loopback request whose sequence number did not match the
expected value
10.2.5 Viewing Loopback Message Information

To view the loopback message information
1. Access the page SOAM CFM MEP LBM.
2. Click the MEPID of the MEP for which you want to view LBM information.
For more information on specific parameters, refer to the "MEP Loopback (SOAM CFM
MEP LBM)" table above.
10.2.6 Setting Up Delay Measurements

DMM measurements (delay and delay variation) work as follows.
A DMM frame is sent from the originating unit to the remote unit. When the DMM frame
is received by the remote unit, it sends a DMR to the originating unit. The reception of the
DMM frame by the remote unit and the transmission of the DMR also involve some
processing time that may or may not be accounted for.
DMM measurements are measurements of network delay and network delay variation.
The unit needs to eliminate the processing time in order to get a true measurement of the
network delay and delay variation. This is accomplished by the use of four time stamps:
a = Time that the DMM frame is transmitted by the originating unit
b = Time that the DMM frame is received by the remote unit
c = Time that the DMR frame (DMM response) is transmitted by the remote unit
d = Time that the DMR frame is received by the originating unit

Using these time stamps, the originating unit calculates one-way and two-way delay as
follows:
One-Way Network Delay = d c
Two-Way Network Delay = d a (c b)

This is the two-way delay (including remote processing time) minus the remote
processing time.

To configure DMM instances

1. Access the page SOAM CFM DMM Configuration.
All existing Delay Measurement Instances are displayed.
2. Click Add to create a DMM instance or click the DMM instance index to edit an
existing DMM instance.
Note: One-way delay measurements require time synchronization, via
NTP, on units at each probe end.
DMM Configuration (SOAM CFM DMM Configuration)
Index The index of the Delay measurement instance
DMM Name The name of the Delay Measurement instance
Name
MEP Index The index assigned to the Maintenance association End Point
MEP idx
MEPID The local Maintenance association End Point Identifier
Remote MEPID The remote Maintenance association End Point Identifier
R-MEPID
Priority Priority value used in VLAN tags, if present, in the transmitted
frame
Enable Enables sending DMM frames at the specified interval
Sampling Interval The time at which this Delay measurement instance issues
Interval DMM frames. Expressed in milliseconds
Reference Period Reference period in minutes for the Delay measurements

One-Way Delay
Enable Enables one-way delay measurement for this DMM instance
Maximum Allowed Maximum one-way delay in the Reference Period. Expressed in
Value milliseconds.
If a certain number (set by next field value) of consecutive
measurements exceeds this value, an alarm is triggered.
Instantaneous The number of consecutive measurements exceeding the

Threshold Maximum Allowed value that triggers a one-way delay alarm
Average Threshold One-way average delay threshold, expressed in milliseconds,
that triggers the average one-way delay alarm for this Reference
Period
Note:The threshold is expressed in milliseconds, but with
microsecond granularity. Consequently, values such as 1.001
milliseconds are acceptable.
Enable Select to enable One-way delay variation measurements for this
DMM instance.
Maximum Allowed Maximum one-way delay variation, expressed in milliseconds,
Value to monitor in the Reference Period
Instantaneous Number of consecutive measurements exceeding the
Threshold Maximum Allowed Value that triggers a one-way delay
variation alarm for this Reference Period
Average Threshold One-way average delay variation threshold, expressed in
milliseconds, that triggers the average one-way delay variation
ms are acceptable.
Two-Way Delay
Enable Select to enable Two-way delay measurement for this DMM
instance.
Maximum Allowed Maximum two-way delay, expressed in milliseconds, to monitor
Value in the Reference Period
Instantaneous Number of consecutive measurements exceeding the
Threshold Maximum Allowed Value that triggers a two-way delay alarm
Average Threshold Two-way average delay threshold, expressed in milliseconds,
that triggers the average two-way delay alarm for this Reference

Period
ms are acceptable.
Enable Indicates whether the Two-way delay variation is computed by
this DMM instance
Maximum Allowed Maximum two-way delay variation, expressed in milliseconds,
Value to monitor in the Reference Period
Instantaneous Specify the number of consecutive measurements exceeding
Threshold the Maximum Allowed Value that triggers a two-way delay
variation alarm for this Reference Period.
Average Threshold Specify the two-way average delay variation threshold,
expressed in milliseconds, that triggers the average two-way
delay variation alarm for this Reference Period.
ms are acceptable.
10.2.7 Deleting a Delay Measurement Instance

To delete a delay measurement instance
1. Access the page SOAM CFM DMM Configuration.
2. Click the index of the DMM instance to delete.
3. Click Delete.
CAUTION: Deleting a DMM instance will also delete all SA metrics that use
this DMM instance as the metric source.

10.2.8 Viewing Delay Measurement Results

To view delay measurement results details
Note: For more information on how delay measurements results are
calculated, refer to "Setting Up Delay Measurements" on page 281.
1. Access the page SOAM CFM DMM Results.
The results for all Delay Measurement Instances are displayed.
2. Click the Index of the DMM instance you want to view the DMM results.
DMM Results (SOAM CFM DMM Results)
Index The index of the Delay measurement instance
Name The name of the Delay measurement instance
MEP idx
MEPID The local MEP's Maintenance association End Point Identifier
Remote MEPID The remote MEP's Maintenance association End Point Identifier
R-MEPID
Priority The priority value used in VLAN tags, if present, in the transmitted
frame
Period The number of periods that elapsed since measurement started
Period Time The time when the previous period was completed
Result Codes The current value, expressed in microseconds, for DMM results:
OADV: One-Way Average Delay Variation
TADV: Two-Way Average Delay Variation
One-Way Delay
Average Alarm Indicates whether an alarm is raised (Active) because the current
average one-way delay is greater than or equal to the average
threshold

Instantaneous Indicates if an alarm has been raised (Active) because the
Alarm instantaneous threshold has been reached. This threshold is the
consecutive number of times the one-way delay was greater than or
equal to the maximum value.
Instantaneous The one-way instantaneous delay, expressed in microseconds
Delay
The previous period is indicated in Period Time.
Nbr Samples Total number of samples in the period
Minimum Delay The minimum delay, expressed in microseconds, over one period
Maximum Delay The maximum delay, expressed in microseconds, over one period
Average Delay The average delay, expressed in microseconds, over one period
Nbr Threshold Number of times the one-way delay exceeded the value of the
Exceeded Maximum Delay parameter
Average Alarm Indicates if an alarm has been raised (Active) because the current
average one-way delay variation is greater than or equal to the
average threshold
consecutive number of times the one-way delay variation was greater
than or equal to the maximum value.
Instantaneous The one-way instantaneous delay variation, expressed in
DV microseconds
Minimum DV The minimum delay variation in microseconds over one period
Maximum DV The maximum delay variation in microseconds over one period
Average DV The average delay variation in microseconds over one period
Nbr Threshold Number of times the one-way delay variation exceeded the value of
Exceeded the Maximum DV parameter

Two-Way Delay
Average Alarm Indicates if an alarm is raised (Active) because the current average
two-way delay is greater than or equal to the average threshold
consecutive number of times the two-way delay was greater than or
equal to the maximum value.
Instantaneous The two-way instantaneous delay, expressed in microseconds
Delay
Minimum Delay The minimum delay, expressed in microseconds, over one period
Maximum Delay The maximum delay, expressed in microseconds, over one period
Average Delay The average delay in microseconds over one period
Nbr Threshold Number of times the two-way delay exceeded the value of the
Exceeded Maximum Delayparameter
Average Alarm Indicates if an alarm is raised (Active) because the current average
two-way delay variation is greater than or equal to the average
threshold
consecutive number of times the two-way delay variation was greater
than or equal to the maximum value.
Instantaneous The two-way instantaneous delay variation, expressed in
DV microseconds
Minimum DV The minimum delay variation in microseconds over one period
Maximum DV The maximum delay variation in microseconds over one period
Average DV The average delay variation in microseconds over one period

Nbr Threshold Number of times the two-way delay variation exceeded the value of
Exceeded the Maximum DVparameter
10.2.9 Setting Up Packet Loss Measurement

To set up packet loss instances
1. Access the page SOAM CFM Packet Loss Configuration.
A listing of all existing packet loss instances is displayed.
2. Click Add to create a packet loss instance or click the packet loss instance index to
edit an existing packet loss instance.

Packet Loss Configuration (SOAM CFM Packet Loss Configuration)
Index The packet loss instance unique identifier
PL Name The name of the packet loss instance
Name
MEP idx
R-MEPID Note: A peer MEP should have the sequence number enabled
to allow a local MEP to perform CCM-based packet loss
measurements.
Priority The Priority value to be used in VLAN tags, if present, in the
transmitted frame. Same as MEP's CCM priority.
Interval The Interval between packet loss measurements. This is the
same as the MEP's CCM interval.
Note: Packet loss measurement is not available with a CCM
interval of 3.33 milliseconds.
Enable Enables packet loss measurements
Reference Period Specify the reference period in minutes.

Threshold Specify (as a percentage) the maximum ratio of packets lost
allowed before issuing an alarm during the reference period.
10.2.10 Deleting a Packet Loss Instance

To delete a packet loss instance
1. Access the page SOAM CFM Packet Loss Configuration.
2. Click the index of the packet loss instance to delete.
3. Click Delete.
CAUTION: Deleting a PL instance will also delete all SA metrics that use
this PL instance as the metric source.
10.2.11 Viewing Packet Loss Results

Packet loss results are calculated with the received CCM during the reference period.
To view details of packet loss results

1. Access the page SOAM CFM Packet Loss Results.
A summary of results for all packet loss instances is displayed.
2. Click the Index of the packet loss instance you want to view the packet loss results.
Packet Loss Results (SOAM CFM Packet Loss Results)
Index The packet loss instance unique identifier
Name The name of the packet loss instance
MEP idx
R-MEPID Note: A peer MEP should have the sequence number enabled
to allow a local MEP to perform CCM-based packet loss
measurements.

Priority The priority value to be used in VLAN tags, if present, in the
transmitted frame. Same as MEP's CCM priority.
Period The number of periods that have elapsed since measurement
started
Continuous Results in the section below gives the packet loss
since the last time the statistics were cleared.
Period Time The time when the current period results were moved to the
previous period results.
Packet Loss Alarm Indicates if an alarm is raised (Active) because the number of
packets lost, for the current period, is greater that the packet
loss threshold
Packet Loss Ratio Packet loss ratio expressed as a percentage
Loss %
Nbr Packets Number of expected packets during the reference period. This
should normally correspond to the reference period divided by
the interval unless the period is incomplete.
Nbr Packets Lost Number of packets lost during the period. For the current
period, it is a continuous value that is not set to zero at the
beginning of the period. The current period counter is organized
as FIFO where a new packet loss result is put into the start and
the oldest packet loss result is removed at each interval.
Nbr Gaps The total number of gaps that have been detected from the
sequence of packets that were received during the interval
This counter is reset to zero at the beginning of each period.
Largest Gap was detected during the period
This counter is reset to zero at the beginning of each period.
10.2.12 Setting Up Synthetic Loss Measurements

Synthetic loss measurement is used to measure the frame loss ratios (near-end and far-
end) between two MEPs. Measurements and calculations are performed at one end only.
You have to set up the SLM instance on the unit that you want to perform and display the
SLM measurements.
Note: You must set up a MEP on the remote unit; setting up an SLM
instance is optional.

To set up or modify an SLMinstance

1. Access the page SOAM CFM SLM Configuration.
All the existing Synthetic Loss Measurement Instances are displayed.
2. Click Add to create an SLM instance or click the SLM instance index to edit an existing
SLM instance.
Note: If you plan to use one-way delay measurements, you must enable
time synchronization on the units at each end of the probe.
Synthetic Loss Message Configuration (SOAM CFM SLM Configuration)
Index The index of the SLM instance
SLM Name The name of the SLM instance
MEP Index The index assigned to the MEP
MEP idx
R-MEPID
Priority Priority value used in VLAN tags, if present, in the transmitted
frame
Interval The time, expressed in milliseconds, at which this SLM instance
issues SLM frames
Possible values are: 10 , 100, 1000 and 10000 milliseconds.
Default: 1000 milliseconds
Enable The state of the SLM instance. When enabled, SLM frames are
State sent at the specified interval. Disabled by default.
Reference Period Reference period, expressed in minutes, for the SLM instance
Range: 1 to 1440 minutes; default: 15 minutes
Near-End Threshold The frame loss threshold for near-end packet loss, expressed as
a percentage
Far-End Threshold The frame loss threshold for far-end packet loss, expressed as a
percentage

10.2.13 Deleting a Synthetic Loss Measurement Instance

To delete a synthetic loss measurement instance
1. Access the page SOAM CFM SLM Configuration.
2. Click the SLM instance index to delete.
3. Click Delete.
CAUTION: Deleting an SLM instance will also delete all SA metrics that use
this SLM instance as the metric source.
10.2.14 Viewing Synthetic Loss Measurement Results

To view synthetic loss measurement results details
1. Access the page SOAM CFM SLM Results.
A summary of results for all SLM instances is displayed.
2. Click the Index of the SLM instance for which you want to view the synthetic loss
measurements.
SLM results (SOAM CFM SLM Results)
Index The index of the SLM instance
Name The name of the SLM instance
MEP Index The index assigned with the Maintenance association End Point
MEP idx
R-MEPID Note:A peer MEP should have the sequence number enabled
to allow a local MEP to perform CCM-based SLM
measurements.
Priority The priority value to be used in VLAN tags, if present, in the
transmitted frame
Period The number of periods that have elapsed since measurement
started

Continuous Results in the section below gives the packet loss
since the last time the statistics were cleared.
Period Time The time when the current period results were moved to the
previous period results
A Near-End Alarm The state of the near-end SLM alarm
A Far-End Alarm The state of the far-end SLM alarm
SLM Sent The number of synthetic loss messages sent
SLR Received The number of synthetic loss replies received
Remote SLM The number of synthetic loss messages received by the remote
Received MEP
Near-End Packets The number of packets lost at the near end
Lost
Far-End Packets Lost The number of packets lost at the far end
Near-End Pkt-Loss Near-end loss ratio
Ratio The ratio of packets lost in a near-end network
NE Loss %
Far-End Pkt-Loss Far-end loss ratio
Ratio The ratio of packets lost in a far-end network
FE Loss %
Number of Gaps The total number of gaps that have been detected from the
Nbr Gaps sequence of packets that were received during the interval
Note:This counter is reset to zero at the beginning of each
period.
Largest Gap was detected during the period. Expressed in packets
Note:This counter is reset to zero at the beginning of each
period.
10.2.15 Managing CFM Interfaces

Use this page to view a summary of all CFM interfaces or manage the details related to a
selected interface.

To view CFM interface information

1. Access the page SOAM CFM Interface.
The CFMInterfaces page opens. All available CFMinterfaces are listed along with their
assigned port name.
2. To view detailed information about a specific interface, select its name from the
Interface Name column.
The CFMInterface-n Configuration page is displayed. For more information on
specific parameters, refer to the following table.
Note:To create a new interface, access the page System Configuration
Interface.
Interface Summary (SOAM CFM Interface)
Interface Name The name of the interface
Port The physical port associated with this interface
Interface Index The global system index referring to this interface
Ethertype The Ethertype used by the interface
VLAN ID The VLAN ID used by the interface
10.2.16 Assigning a CFMInterface

To assign a new interface to CFM
assigned port name.
2. Select the interface to assign from the Interface Name drop-down list.
3. Click Assign to assign the interface to CFM.

Note: You can only assign single tagged VLAN interfaces to CFM.
Standard, Q-in-Q, bridge or management interfaces are not allowed.
10.2.17 Unassigning a CFMInterface

To unassign a CFM interface

assigned port name.
2. Select the interface from which you wish to unassign a CFMinterface from the
Interface Name column.
The CFMInterface-n Configuration page is displayed.
3. Click Unassign to unassign the selected interface from CFM.
The system returns to the CFMInterfaces page. The name of the interface you
unassigned is now listed in the Interface Name drop-down list beside the Assign
button.
CAUTION: Interfaces currently in use by a MEP instance cannot be

unassigned.
10.2.18 Setting Up VSP

The VSP function is used to reflect VSP frames to the sender.
Note: This function is to be used only with VSP when connecting to Layer-2
VSP actuator devices.
To set up the VSP function

1. Access the page SOAM CFM VSP Configuration.

VSP Configuration (SOAM CFM VSP Configuration)
Enable The state of the instance (disabled by default)
MEG Level The MEG level of the reflector:
Frames with the MEG level equal to this setting are
reflected
Frames with the MEG level higher than this setting are
forwarded
Range:All, 0-7
Note:When All is selected, all frames are reflected.

10.2.19 Viewing VSP Statistics

To view VSPResults
1. Access the page SOAM CFM VSP Results.
Current VSP results are displayed.
VSP Results (SOAM CFM VSP Results)
Index The index assigned to the VSP instance
Src Mac The MAC address for the remote unit (the source)
Dst Mac The MAC address for this unit's reception port (the destination)
VLANID The VLANIDof the VSP frames received
MEG Level The MEGlevel of the VSPframes received
RX Count The number of VSP frames received
TX Count The number of VSP frames reflected
10.2.20 Setting Up CFM Defaults

The MIP Half-Function (MHF) default parameters control the MHF creation for VIDs that
are not attached to a Maintenance Association. For each port, a VID is attached to a
Maintenance Association at a specific MD level, if at this level a MEP exists on that port or
if an Up MEP exists on some other port.
For a given VID, the default MHF MD level plus the set of Maintenance Associations which
include that VID define the VID's active MD levels. The MD level at which MHFs could be
created on a port for a given VID is the VID's lowest active MD level that is higher than any
MEP configured on that port. If at this level the VID is attached to a Maintenance
Association, the Maintenance Association parameters control the MHF creation,
otherwise the MHF default parameters control the MHF creation.
To set up CFM defaults

1. Access the page SOAM CFM Defaults.
A listing of all existing packet loss instances is displayed.
2. Click Add to create a packet loss instance or click a packet loss instance name to edit
an existing packet loss instance.


CFM Defaults (SOAM CFM Defaults)

MHF MD Level The default active MD level used by the MHF creation algorithm
when no other lower active MD level applies
MHF Creation Indicates if the management entity can create MHFs for VIDs on
which no Up MEP is configured

Explicit: Create MHFs only if there is a MEP at the next

Defer: Use the Maintenance Domain parameter to

determine whether MHFs can be created.
MHF Sender ID Indicates what, if anything, is to be included in the Sender ID

Permission TLV transmitted in CCMs, LBMs, LTMs and LTRs
None: No sender ID TLV included
Manage: Management address
Chassis and Manage: Chassis ID, subtype and

management address

10.3 Using Service Availability

This section describes the Service Availability (SA) function and how to set it up in your
Metro Ethernet Network. The SA function is used to determine the number of unavailable
seconds and other counters for a specific service. You can use the SAfunction to verify,
with the help of your EMS, if the service sold to a client meets a specific SLA.
You can define Service Availability instances with one or more SA metrics (criteria) that will
be used to determine unavailable seconds. Each criterion has its own threshold. The basic
criteria (SA metric) for determining unavailable seconds, as defined in the MEF 10.2
Technical Specification, is the CFM frame loss. The unit supports the following SA metrics:
CFM frame loss
DMM one- way delay
DMM one-way delay variation
DMM two-way delay
DMM two-way delay variation
PAA packet loss
PAA one-way delay
PAA one-way delay variation
PAA two-way delay
PAA two-way delay variation
SLM near-end frame loss
SLM far-end frame loss

Follow these steps to set up Service Availability:
Add a Service Availability instance: See "Setting Up Service Availability" on page 299.
Add one or more SA metrics: See "Setting Up an SA Metric" on page 300.
Put a Service Availability instance into service: See "Putting an SA Instance into
Service" on page 302.

10.3.1 Setting Up Service Availability

To configure service availability
1. Access the page SOAM SA Configuration.
A summary of all SA instances is displayed.
2. Click Add to create a new SAinstance or click the SAinstance name to edit an existing
SA instance.

Note: You must add an SA Metric before being able to put the SA instance
into service. See "Setting Up an SA Metric" on page 300.
SA Configuration (SOAM SA Configuration)
Index Unique identifier assigned to the SA instance
Name Unique name assigned to the SA instance
Administrative State The SA instance's administrative state:
/ In Service: The SA instance is operational. The Uptime and
State Unavailable counters are working.
Out of Service: The SA instance is not operational. The

Maintenance counter is incremented.
Default value is Out of Service.
Operational State The operational state of the SA instance:
In Service: The SA instance is operational. At least one SA
metric is enabled and the Uptime and Unavailable counters
are working.
Out of Service: The SA instance is not operational. The

Maintenance counter is incremented.
Out of Service AU: The SA instance is operational but all

metrics are disabled. The Maintenance counter is
incremented.
Number of Metrics The number of metrics associated with the SA instance

Reporting Period The time over which availability counters are evaluated in

(min) addition to the monotonic counters
Possible values: 1 to 1440 minutes
Default value is 15.
Availability Window The number of consecutive Time Intervals (see below) used to
Size (Interval) assess Service Availability for this instance. Unavailable seconds
start to be counted when at least one SA metric threshold is
crossed for the Availability window size.
Default value is 10.
HLI Window Size The number of consecutive Time Intervals (see below) used to
(Interval) assess High Loss Intervals for this instance. HLI count starts
when at least one SA metric threshold is crossed for the HLI
window size.
Default value is 3.
Time Interval The interval of time during which the metrics are evaluated
(Seconds) Supported values are 1, 5, 10, 20 or 60 seconds.
Default value is 1 second.
Note:When the SA Metric type is set to SLM, the Time Interval
must be set to a minimum value of 20 seconds because the
SLM module updates its statistic every 10 seconds. It is
recommended not to configure a Time Interval of 10 seconds or
less for the SLM.
10.3.2 Deleting an SA Instance

To delete aService Availability instance
2. Click the SA instance Name to delete.
3. Click Delete.
Note: This also deletes all SAmetrics associated with this SA instance.
10.3.3 Setting Up an SA Metric

An SA metric defines the criteria used to assess any unavailable seconds. You must add
one or more SA metrics for each SA instance. SA metrics are valid only for a specific

SAinstance. You must first create the CFM instance, DMM instance or PAA probe in its
corresponding page before setting up the SA metric.
CAUTION: Once an SA metric has been set up with a metric source (a CFM
DMM instance, a CFM Packet Loss instance, or a PAA probe), then
deleting the metric source will also delete all SA metrics using it. For more
information about deleting a CFM DMM instance, a CFM Packet Loss
instance or a PAA probe, refer to "Deleting a Packet Loss Instance" on
page 289, "Deleting a Delay Measurement Instance" on page 284, and to
"Deleting a Probe" on page 255.
To set up a Service Availability metric

2. Click the SA instance Name of the SA instance you want to add or edit the SA metric.
3. At the bottom of the page, click Add to create a new SAmetric or click the SAmetric
Index to edit an existing SA metric.

SA Metric (SOAM SA Configuration [SA instance] [SA metric index])
Index The unique identifier assigned to the SA metric
Metric Index
Name The unique name assigned to the SA metric
Type The SA metric type
Metric Type The available options are:
CFM packet loss
DMM on- way delay
DMM one-way delay variation
DMM two-way delay
DMM two-way delay variation
PAA packet loss
PAA one-way delay

PAA one-way delay variation
PAA two-way delay
PAA two-way delay variation
SLM near-end packet loss
SLM far-end packet loss
Src name The name of the metric source. For example, if the Metric type
Metric Source Name is a PAA packet loss, the Metric source name must be the name
of an existing PAA probe.
Src index The unique identifier assigned to the metric source
Metric Source Index
Threshold The threshold above which the metric will be declared
unavailable for the associated SA time interval. Value is
expressed as either a percentage or in microseconds.
For a packet loss metric, the threshold (expressed as a
percentage) represents the percentage of lost packets that is
tolerated during the SA time interval.
For a delay or delay variation metric, the threshold (expressed
in microseconds) represents the maximum value that is
tolerated during the SA time interval.
10.3.4 Deleting an SA Metric

To delete a Service Availability metric
A summary of all SA instances is displayed. For more information on specific
parameters, refer to the table above.
2. Click the SA instance Name of the SA instance you want to delete the SA metric.
3. Click the SA metric Index you want to delete.
4. Click Delete.
10.3.5 Putting an SA Instance into Service

Once you have configured the SA Metrics, the SA instance must be put into service.

To put an SAinstance into service

2. Click the Name of the SA instance you want to put into service.
3. Select In Service from the State drop-down list.
4. Click Apply.
10.3.6 Viewing SA Counters

Two sets of SA counters are available:
Periodic: This set of counters provides the results for the current period. The periodic
counters are stored in the history file for every reporting period when the history file
for SA is enabled.
Monotonic: This set of counters provides the results since the SA instance was
created or since the last reset.
To eliminate transient results or reset the counters, click one of the Clear Statistics
buttons.
To view a summary of all Service Availability counters

1. Access the page SOAM SA Counters.
2. Click an SA instance Name to view the detailed counters for this SA instance and its
metrics.
For more information on specific parameters, refer to the following two tables.
SA Counters (SOAM SA Counters)
Index Unique identifier assigned to the SA instance
Name Unique name assigned to the SA instance
Uptime Elapsed time since the SA instance was created
Maintenance Time The total period of time during which the state was either Out of
Service or Out of Service-Autonomous
Availability Service Availability =
(1 - (number of unavailable t / number of t)) * 100
where t is Time Interval. Expressed as a percentage
Period The current reference period number

Period Time The starting time of the current reference period
Validity The SA counters validity can have four values:
Valid: The SA counters are valid.
Invalid: Only used for the history file counters, it indicates

an incomplete period was stored.
Adjusted: A change occurred in the configuration of a

reporting period, which may impact the service availability
calculation.
Pending: The counters were reset in the middle of a time

interval.
Uptime This counter increments during the maintenance interval. This

counter is reset to zero when one of the following conditions
occur:
Device reboot
Counter reset (you clear the statistics)
Unavailable This counter increments for every unavailable second, and only
when the SA instance state is IS. Unavailable seconds start to be
counted when at least one SA metric threshold is crossed for
the Availability window size. This counter is reset to zero when
one of the following conditions occur:
Device reboot
Maintenance This counter increments for every second the SA instance is in

the state Out of Service or Out of Service - Autonomous.
Number of Gaps The number of times the SA instance changed from available to
unavailable
Largest Gap The longest interval of time during which the SA instance was
unavailable
CHLI Time This counter increments for every second for which the SA
instance is in the high loss interval state.
This counter is reset to zero when one of the following
conditions occur:
Device reboot

CHLI The ratio (expressed as a percentage) of high-loss intervals

divided by the uptime minus the sum of maintenance time and
unavailable time
CHLI = Number of High-loss intervals / (Uptime - Maintenance -
Unavailable)
Metric Counters (SOAM SA Counters)

Index Unique identifier assigned to the SA metric
Name Unique name assigned to the SA metric.
Unavailable This counter increments for every unavailable second. The
count starts when at least one SA metric threshold is crossed for
the Availability window size. This counter is reset to zero when
one of the following conditions occur:
Device reboot
HLI This counter increments for every high loss interval. This
counter is reset to zero when one of the following conditions
occur:
Device reboot
Validity The SA counters validity may have one of the following four
values:
Valid: The SA counters are valid.
Invalid: Only used for the history file counters, it indicates

an incomplete period was stored.
Adjusted: A change occurred in the configuration of a

reporting period, which may impact the service availability
calculation.
Pending: The counters were reset in the middle of a time

interval.

10.4 Using the Two-Way Active Measurement Protocol (TWAMP)

This section describes the Two-Way Active Measurement Protocol (TWAMP) function and
how to set it up in your Metro Ethernet network. TWAMP packet generation provides the
ability to perform one- and two-way delay and delay variation in a Layer-3 network, as
well as packet loss measurements. TWAMP packets are reflected back to the sender.
TWAMP defines two protocols:
TWAMP control protocol (not supported by Accedian)
TWAMP test protocol (supported by Accedian)

TWAMP light, which only includes the test protocol, allows test sessions to be configured
without the control protocol. The Accedian implementation of TWAMP also enhances this
functionality by providing the ability to perform near-end and far-end one-way delay and
delay variation measurements.
Note: This function is only to be used with TWAMPwhen connecting to
Layer-3 TWAMP session sender devices.

10.5 Setting Up TWAMP Generator Measurements

TWAMP generator instances are used to calculate delay measurements between two end
points. Measurements and calculations are performed at the generating end only.
Note: You must enable TWAMP reflection at the end point.
To set up or modify a TWAMPgenerator instance

1. Access the page SOAM TWAMP Generator Configuration.
A listing of all existing TWAMP generator instances is displayed.
2. Click Add to create a TWAMP generator session or click the TWAMP session index to
edit an existing TWAMP generator session.
Note: If you plan to use one-way delay measurements, you must enable
time synchronization on the units at each end of the probe.
TWAMP Generator (SOAM TWAMP Generator Configuration)
Index The index assigned to the TWAMP instance
Session Name The name assigned to the TWAMP instance
Maximum length:31 characters
Enable The state of the TWAMP instance. When enabled, TWAMP
packets are sent at the specified interval.
Note:This parameter is disabled by default. Click to enable.
Interval The time at which this TWAMP instance transmits packets,
expressed in milliseconds
Reference Period The reference period for the TWAMP instance, expressed in
minutes
Range: 1 to 1440 minutes
Default: 15 minutes
Note:This value must be at least 10 times the value of the
Interval parameter.
Packet Size The size of TWAMP samples, expressed in bytes
Note:The size value indicated here does not include protocol
headers (VLAN tags, UDP, IP, Ethernet) or the four FCS bytes.

Minimum value: 14 bytes
Maximum value: 1472 bytes
Default value:41 bytes
Note:If you choose to use a packet size smaller than 41 bytes,
you must ensure that the reflector being used supports frame
padding, as defined by RFC5357. Similarly, if you observe that
packets are not being reflected, try increasing the packet size
to at least 41 bytes.
UDPParameters
Destination IP The remote IP address
Address
Source UDP Port The UDP source port
Destination UDP Port The UDP destination port
Diff-Serv CodePoint The DSCP class selector setting for the transmitted packets
(DSCP) Expected length: 6 bits
Explicit Congestion The ECN value. This value can be used to associate an ECN value
Notification (ECN) with the TWAMP packets, thereby simulating ECN in the
customer network.
Note:The ECN bits are the last two bits of the IP ToS field.
Range: 0-3
VLAN 1 Priority The priority bits of the first VLAN. This value can be used to
associate a priority value with the first VLAN.
Range: 0-7
Packet Loss
Continuity Check The number of consecutive sampling periods that can be lost
Threshold before triggering the Continuity Loss alarm. The alarm status is
rounded up to the next full second.
Range: 2-200
Default value:10
Packet Loss Rate The threshold, expressed as a percentage, at which an Excessive
Packet Loss (EPL) alarm is triggered
Range: 0-100 %
Two-Way Measurements
Maximum Delay The two-way delay allowed for each sample in the Reference

Period
trigger the alarm TWAMP_TW_MAX_DELAY_ALERT.
Delay that are allowed before triggering the two-way delay
Average Delay The average two-way delay is calculated from samples taken
Threshold during the reference period.
Exceeding this threshold triggers the alarm TWAMP_AVG_
DELAY_ALERT.
Maximum Delay The maximum two-way delay variation threshold to monitor
Threshold to trigger the alarm TWAMP_MAX_DV_ALERT.
Threshold Delay Variation that are allowed before declaring the two-way
Average Delay The average two-way delay variation is calculated from samples
Variation Threshold taken during the reference period.
Exceeding this threshold triggers the alarm TWAMP_AVG_DV_
ALERT.
One-Way Near End Measurements
Maximum Delay The one-way near-end delay allowed for each sample in the
Reference Period
trigger the alarm TWAMP_NE_OW_MAX_DELAY_ALERT.
Delay that are allowed before declaring the one-way near-end
delay alarm for this Reference Period
Average Delay The average one-way near-end delay is calculated using the
Threshold samples taken during the reference period.
Exceeding this threshold triggers the alarm TWAMP_NE_OW_
AVG_DELAY_ALERT.
Maximum Delay The maximum one-way near-end delay variation threshold to
Variation monitor during a test period

Threshold to trigger the alarm TWAMP_NE_OW_MAX_DV_
ALERT.
Threshold Delay Variation that are allowed before declaring the one-way
near-end delay variation alarm for this Reference Period
Average Delay The average one-way near-end delay variation is calculated
Variation Threshold using the samples taken during the reference period.
Exceeding this threshold triggers the alarm TWAMP_NE_OW_
AVG_DV_ALERT.
One-Way Far-End Measurements
Maximum Delay The one-way far-end delay allowed for each sample in the
Reference Period
trigger the alarm TWAMP_FE_OW_MAX_DELAY_ALERT.
Delay that are allowed before triggering the one-way far-end
delay alarm for this Reference Period
Average Delay The average one-way far-end delay is calculated using samples
Threshold taken during the reference period.
Exceeding this threshold triggers the alarm TWAMP_FE_OW_
AVG_DELAY_ALERT.
Maximum Delay The maximum one-way far-end delay variation threshold to
Variation monitor during a test period
Threshold to trigger the alarm TWAMP_FE_OW_MAX_DV_
ALERT.
Threshold Delay Variation that are allowed before triggering the one-way
far-end delay variation alarm for this Reference Period
Average Delay The average one-way far-end delay variation is calculated using
Variation Threshold samples taken during the reference period.
Exceeding the threshold triggers the alarm TWAMP_FE_OW_
AVG_DV_ALERT.

10.5.1 Deleting a TWAMP Generator Instance

To delete a TWAMP generator instance
1. Access the page SOAM TWAMP Generator Configuration.
2. Select the TWAMP instance index you wish to delete by clicking it.
3. Click Delete.

10.6 Viewing TWAMPGenerator Session Results

To view a summary of all TWAMP generator session results
1. Access the page SOAM TWAMP Generator Results.
2. Click a session index to view its detailed results.

Tip:Select the Poll Every n Seconds box, then enter a number
representing the frequency with which the TWAMPgenerator results will
be refreshed.
TWAMP Generator Session Results (SOAM TWAMP Generator Results)
TWAMP Generator Results
Local Sync Indicates whether or not the local clock is in synch with its
configured reference clock (PTP, NTP or GPS)
Remote Sync Indicates whether or not the remote clock is in synch with its
Protocol The protocol used by this session's protocol
UDP/IPv4
Period The number of periods that have elapsed since the session was
first enabled
Period Time The start time of the current period
Packet Statistics
Tx Count The number of TWAMP packets that have been sent, for the
previous period and the current period
Rx Count The number of TWAMP packets that have been received, for
the previous period and the current period
Packet Loss
Nbr Samples The total number of samples included in the period
Nbr Lost Packets The total number of packets during the period that were not

received by the other end
Loss Ratio The ratio between the number of packets that were lost during
the period and the total number of packets that were sent,
expressed as a percentage
Nbr Out of Order The total number of packets during the period that were
received in a different order than what they were sent in
Nbr Duplicate The total number of packets during the period that were
received more than once
Nbr Gaps The total number of gaps that have been detected from the
sequence of packets that were received during the period
This value is calculated based on the Sequence Number field of
the TWAMP packet header of the received packets.
Largest Gap The longest uninterrupted sequence of missing packets that
was detected from the sequence of packets that were received
during the period
This value is calculated based on the Sequence Number field of
the TWAMP packet header of the received packets.
Two-Way Delay
Instantaneous Delay The two-way instantaneous delay value, expressed in
microseconds. This is the latest two-way delay value measured
Minimum Delay The two-way delay of the fastest sample collected over the
Maximum Delay The two-way delay of the slowest sample collected over the
Average Delay The average delay of the samples during the reference period,
Nbr Threshold The number of times the two-way delay has exceeded the value
Instantaneous DV The two-way instantaneous delay variation value, expressed in
microseconds. This is the latest two-way delay variation

Minimum DV The two-way delay variation, expressed in microseconds, of the
samples with the smallest delay skew over the period
Maximum DV The two-way delay of the samples with the highest delay skew
Average DV The average two-way delay variation of the samples during the
Nbr Threshold The number of times the two-way delay variation exceeded the
Exceeded value of the parameter Maximum DV
One-Way Near-End Delay
Nbr Samples The total number of one-way near-end samples included in the
period
Minimum Delay The one-way delay of the fastest sample collected over the
Maximum Delay The one-way delay of the slowest sample collected over the
Average Delay The average one-way near-end delay of the samples during the
Nbr Threshold The number of times the one-way near-end delay has exceeded
Exceeded the value of the Maximum Delay parameter
One-Way Near-End Delay Variation
Nbr Samples The total number of one-way near-end delay variation samples
included in the period
Minimum DV The one-way near-end delay variation, expressed in
microseconds, of the samples with the smallest delay skew over
the period
Maximum DV The one-way near-end delay of the samples with the highest
Average DV The average one-way near-end delay variation of the samples

during the reference period, expressed in microseconds
Nbr Threshold The number of times the one-way near-end delay variation
Exceeded exceeded the value of the parameter Maximum DV
One-Way Far-End Delay
Nbr Samples The total number of one-way far-end samples included in the
period
Minimum Delay The one-way far-end delay of the fastest sample collected over
the period, expressed in microseconds
Maximum Delay The one-way far-end delay of the slowest sample collected over
the period, expressed in microseconds
Average Delay The average one-way far-end delay of the samples during the
Nbr Threshold The number of times the one-way far-end delay has exceeded
Exceeded the value of the Maximum Delay parameter
One-Way Far-End Delay Variation
Nbr Samples The total number of one-way far-end delay variation samples
included in the period
Minimum DV The one-way far-end delay variation, expressed in
microseconds, of the samples with the smallest delay skew over
the period
Maximum DV The one-way far-end delay of the samples with the highest delay
skew over the period, expressed in microseconds
Average DV The average one-way far-end delay variation of the samples
during the reference period, expressed in microseconds
Nbr Threshold The number of times the one-way far-end delay variation
Exceeded exceeded the value of the parameter Maximum DV

10.7 Viewing the TWAMPGenerator Session Status

To view the TWAMP generator session status
1. Access the page SOAM TWAMP Generator Status.
2. Click a session index to view its detailed results.

Tip:Select the Poll Every n Seconds box, then enter a number
representing the frequency with which the TWAMPgenerator status data
will be refreshed.
TWAMP Generator Session Status (SOAM TWAMP Generator Status)
Probe Name
Local Sync Indicates whether or not the local clock is in synch with its
Remote Sync Indicates whether or not the remote clock is in synch with its
Status Codes The current state (active or inactive) for all TWAMP alarms for
the following status codes:
CC: Continuity Check
EPL: Excessive Packet Loss
TD: Two-Way Delay
TDV: Two-Way Delay Variation
TAV: Two-Way Average Delay Variation
OD-NE: One-Way Delay, Near End
OAD-NE: One-Way Average Delay , Near End
ODV-NE: One-Way Delay Variation, Near End

OAV-NE: One-Way Average Delay Variation, Near End
OD-FE: One-Way Delay, Far End
OAD-FE: One-Way Average Delay , Far End
ODV-FE: One-Way Delay Variation, Far End
OAV-FE: One-Way Average Delay, Far End

10.8 Setting Up a TWAMP Reflector

To set up a TWAMP reflector
1. Access the page SOAM TWAMP Reflector Configuration.

TWAMP Configuration (SOAM TWAMP Reflector Configuration)
Enable The state of the instance (disabled by default)
UDP Port The UDP port of the reflector. The default value is 6000.
TWAMP
Layer-3 Y.1564
SAT Protocol

10.9 Viewing TWAMP Reflector Statistics

To view TWAMPreflector statistics
1. Access the page SOAM TWAMP Reflector Statistics.
TWAMP Reflector Statistics (SOAM TWAMP Reflector Statistics)
Index Index assigned to the TWAMP instance
Protocol The protocol used by the test session
Dst Port Destination UDP port (used by session-reflector)
IP Src IP address of session-sender
Src Port Source UDP port (used by session-sender)
RX Packets Number of TWAMP packets received from the session-sender
TX Packets Number of TWAMP packets transmitted back to the session-
sender

11 Testing Network Performance

The unit allows for testing network performance using traffic generation and analysis, as
specified in RFC-2544, and using Service Activation Testing (SAT), as specified in standard
ITU-T Y.1564.
These test methodologies allow you to pinpoint device or network problems, or to
measure current throughput, packet delay and packet-delay variation on a specific
network segment. Y.1564 allows you to determine the conformance of a network section
or a specific device to a service level agreement (SLA) and/or to Ethernet standards.
These testing techniques are presented in the following sections:
11.1 Setting Up SAT Reporting 322
11.2 Testing Locally-Created Services 324
11.3 Using RFC-2544 for Traffic Generation and Analysis 326
11.4 Using Y.1564 for Service Activation Testing 350
11.5 Using the SATProtocol 362

11.1 Setting Up SAT Reporting

You can set up the unit to enable the transfer of SAT test reports to a server. Once
enabled, test reports are automatically transferred to the server each time a test is
completed.
Test reports are available for RFC-2544 and Y.1564. All reports are available in text or XML
format.
To set up SATreporting
1. Access the page SAT Reporting.

SATReporting (SAT Reporting)
RFC-2544 Settings
Enable Reporting Enables or disables the transfer of RFC-2544 reports to the
specified server.
Enable TXT File Enables or disables the transfer of RFC-2544 reports in text
Transfer format to the specified server.
Enable XML File Enables or disables the transfer of RFC-2544 reports in XML
Transfer format to the specified server.
Y.1564 Settings
Enable Reporting Enables or disables the transfer of Y.1564 reports to the
specified server.
Enable TXT File Enables or disables the transfer of Y.1564 reports in text format
Transfer to the specified server.
Enable XML File Enables or disables the transfer of Y.1564 reports in XML format
Transfer to the specified server.
File Server Configuration
Server URL The full URL of the server to which to send test reports
Examples:
ftp://username:password@domain.com
sftp://username@192.168.10.10
tftp://192.168.1.5

scp://username@192.168.10.10:/target_directory
SCP Password Enter the password required for SCP and SFTP transfers.

11.2 Testing Locally-Created Services

Services that have been created locally on the unit can be included in a Y.1564 or RFC-2544
test by enabling an internal loopback on one of the units UNI ports to redirect the test
traffic through the traffic policies.
A test where an internal loopback in enabled on both UNI ports (i.e., near-end and far-
end), thus enabling services to be tested from end to end, is shown below.
UNI-to-UNI (End-to-End) Testing
The traffic in this end-to-end test moves seamlessly between the two units:
The test traffic is generated toward the local UNI port on Unit 1.
The internal loopback on Unit 1 redirects the traffic to the policies stage, then toward
the NNI port.
The test traffic enters Unit 2 and goes through the policies before reaching the UNI
port.
Another internal loopback is used on Unit 2's UNI port to loop the traffic and send it
back to Unit 1.
In both units, the traffic goes to the policing stages for the ingress direction as well as
for the egress direction.
The units can also be configured to perform UNI-to-NNI testing, as well as NNI-to-UNI
testing, as shown below.

UNI-to-NNI Testing
NNI-to-UNI Testing
Note: The Internal Loopback functionality only supports Layer-2 and

Layer-2 Accedian test frames in conjunction with two-way tests. Other
types of test traffic, such as Layer-2 Generic, Layer-3, are not supported.
Note: When using an internal loopback, the maximum throughput is
limited to 50% of the line rate.
To enable an internal loopback, access the Port Configuration menu. For details, see
"Setting Up Ports" on page 118.

11.3 Using RFC-2544 for Traffic Generation and Analysis

This section presents traffic generation and analysis as specified in the RFC-2544. It
describes how to set this up in your Metro Ethernet network and perform end-to-end
testing and monitoring. This allows you to pinpoint devices or network problems or to
measure current throughput, frame delay and frame-delay variation on a specific network
segment.
Advanced traffic generation and analysis capabilities allow you to perform fully
automated and documented turn-up tests. The test capabilities also include out-of-
service tests.
For out-of-service tests, you must pair the traffic generator with another device that loops
the traffic back. The GT Performance Element contains pre-programmed RFC-2544
loopbacks for certain types of Layer-2 frames. When testing with Layer-2 generic frames or
Layer-3/Layer-3 generic packets (UDP), you must configure the peer unit with a loopback
that matches the test traffic, and with a swapping action on the source/destination MAC
addresses, IP addresses and UDP port numbers. For IP multicast traffic you must use the
RFC monitor in the remote unit.
The next figure illustrates a typical network for traffic generation and analysis tests.
The test results provide information on the packets sent and received, transmission rates,
delay and delay variation.
You may use the traffic generator to generate one or two flows of test traffic and provide
separate results for each flow. Each flow has specific characteristics, such as traffic type
and bit rate. You have the following choices when setting up each flow:
Layer 2 (three types), Layer 3 (two types) and IP multicast traffic
VLAN or VLAN-in-VLAN encapsulation of test traffic
Different traffic types, frame/packet sizes and payload patterns
11.3.1 Setting Up the Traffic Generator

You can set up the traffic generator to send one or two traffic flows, each having a
different traffic type, VLAN and patterns. To view the complete list of elements that can be
configured for each traffic flow, refer to the table "RFC-2544 Generator Configuration (SAT
RFC-2544 Generator Configuration)"

Note: The GT Performance Element contains pre-programmed RFC-2544

and Y.1564 loopbacks for Layer-2 or Layer-2 Accedian frames. For Layer-2
generic traffic or Layer-3 testing with UDP segments, you need to program
the peer unit to have a manual loopback to match the test traffic, with a
swapping action on the MAC addresses, IP addresses and port numbers.
You can do this using the OAM menu.
SAT Reporting is a system feature that enables you to have RFC-2544 or Y.1564 test
reports automatically pushed from the unit to a designated remote server (FTP, SFTP,
TFTP or SCP). Automatically pushing test reports to the server means you can view the
test results more quickly, since you do not have to manually poll the remote server to
determine whether or not the test has completed execution.
For details on how to automate report uploads to a remote server, see "Setting Up SAT
Reporting" on page 322.
Note: All reports are available in text or XML format.
To set up the RFC-2544 generator

1. Access the page SAT RFC-2544 Generator Configuration. An example of the
display is shown in the figure below.

Note: The page content varies, depending on the traffic type you select.

SAT RFC-2544 Generator Configuration
RFC-2544 Generator Configuration (SAT RFC-2544 Generator Configuration)

Outgoing Port The port on which to send the flow(s)
Enable Flow The flow(s) included in the test
First and Second Packet Header Settings
Type The type of test traffic:
Layer-2: Y.1731 LBM frames
Layer-2 Accedian: Y.1731 LBM frames marked with the

Accedian Ethertype
Layer-2 Generic: Special Y.1731 OpCode frames to be used

only with loopback devices based on the MAC-address
swap
Layer-3: UDP segments to perform a test across a multi-

layered network

IP Multicast: IP multicast packets to test multiple receiving

points
Layer-3 Generic: Layer-2 frames with a generic Layer-3

(UDP) payload. Only to be used with loopback devices
based on the MAC-address swap.
MAC Destination The peer MAC address. Applies to Layer-2 and Layer-3 generic
traffic only.
Note: Layer-3 generic traffic is available for the RFC-2544 traffic
generator and test suite. It is unavailable for Y.1564 SAT.
Y.1731 MEG Level The Maintenance Entity Group level
Range: 07
Note:Applies to Layer-2 traffic only. For details, refer to ITU-T
Y.1731.
Destination IP The IP address of the remote unit interface. Applies to Layer-3
Address traffic only.
DSCP The DiffServ Code Point to set in the generated packets. Applies
to Layer-3 traffic only.
Source IP Address The source IP address used for the IP header. Applies to Layer-3
generic and IP multicast traffic only.
Note: IP multicast traffic is available for the RFC-2544 traffic
generator. It is unavailable for the RFC-2544 test suite and
Y.1564 SAT.
Source Port The source UDP port number used to generate the UDP
segment
Note:Applies to Layer-3 traffic only.
Destination Port The destination UDP port number that is used to generate the
UDP segment
Note: You cannot set the destination port value to 8793, since
this is Accedian's proprietary port number.

TWAMP
Layer-3 Y.1564
SAT Protocol
Enable VLAN 1 This encapsulates all frames with one VLAN header.
Header Note: If frames with more than three VLAN tags are received by
the destination NID, these frames will be discarded and frame
losses will be recorded.
When enabled, all test frames are encapsulated with the
specified VLAN ID.
VLAN 1 Ethernet Type The first VLAN Ethernet type
S-VLAN
T-VLAN
C-VLAN
Note: Applies only when the VLAN 1 header is enabled.
VLAN 1 Priority The first VLAN priority bits
VLAN 1 CFI The first VLAN Canonical Format Indicator (CFI)
Enable VLAN 2 Encapsulates all frames with two VLAN headers (as in QinQ)
Header VLAN1 must be enabled to use two VLAN headers.
Note: If frames with more than three VLAN tags are received by
VLAN 2 ID The second VLAN ID. When enabled, all test frames are
encapsulated with the second specified VLAN ID (inner VLAN).
Note:Applies only when the VLAN 2 header is enabled.

VLAN 2 Ethernet Type The second VLAN Ethernet type
S-VLAN
T-VLAN
C-VLAN
VLAN 2 Priority The second VLAN priority bits
VLAN 2 CFI The second VLAN Canonical Format Indicator (CFI)
First and Second Flow Profile Settings
Flow Name The name assigned to the flow. For reference in the Results
section.
Flow Description A description to identify the flow and its characteristics. For
reference in the Results section.
Traffic Type The type of traffic may be one of the following:
Constant: To send frames at a specific bit rate (kbps). You
need to specify the Bit rate.
Burst: To send a predefined number of frames at every

period. You must specify the Packets per Burst.
For the Constant traffic type, specify the bit rate (expressed in
kbps).
Supported values are:
0 to < 12.5 Mbps: Steps of 0.125 Mbps
> 13 Mbps to 1 Gbps: Steps of 1 Mbps

For Burst traffic type, specify the number of frames to send per
period (Packets per Burst) as well as the period, expressed in
milliseconds, between the beginning of two successive bursts of
frames (Inter-Burst Gap).
You must select a Bit Rate that does not exceed the capacity of
the outgoing port used for that test. Failure to do so will result
in inaccurate results.

Size Type Frame sizes may be Fixed or Random:
For a Fixed frame, specify the packet Size.
For Random frame sizes only, specify the Minimum and

the Maximum values. The size of test frames will vary
randomly between the minimum and maximum values you
indicate.
Acceptable values range from 64 bytes to 10240 bytes.
Note: You may need to modify your port MTU sizes in order to
accommodate your selection.
Payload Pattern May be a Fixed-Data, Incremental or Random pattern in the
payload part of the transmitted frames:
For a Fixed payload pattern, specify the 32-bit value, e.g.
0x12345678
For a Random payload pattern, select one of the pre-

configured patterns.
For an Incremental payload pattern, select the increment

factor of Bytes for byte-by-byte increments or Words (2
bytes) for word-by-word increments.
Duration Type Duration type may be one of the following:

Continuous: Stops only when the user manually stops the
test
Seconds: Stops after a specified number of seconds
Bytes: Stops after sending a specified number of bytes.

Value must be greater than or equal to 64 bytes.
Packets: Stops after sending a specified number of packets.

Value must be greater than or equal to 8 packets.
Maximum of 4000000000 packets.
11.3.2 Starting the Traffic Generator and Viewing Test Results

To view a summary of the traffic generator results
1. Access the page SAT RFC-2544 Generator Results.
When you first enter this page, the results of the last test performed are displayed.

2. To start a new test, click Start.

You can stop the test manually at any time by clicking Stop.
3. Click details of the first or second flow to view the detailed results for this flow.
For more information on these results, refer to the following table.
RFC-2544 Generator Results (SAT RFC-2544 Generator Results)
Flow Name The name assigned to a flow
Transmit Statistics
Transmitted Packets Total packets transmitted by this flow for this test
Transmitted Bytes Total bytes transmitted by this flow for this test
L1 Rate The transmitting bit rate of Layer-1 traffic, expressed in Mbps
L2 Rate The transmitting bit rate of Layer-2 traffic, expressed in Mbps
State The flow's current state may be one of the following:
Flow State Waiting: Waiting to be started by the tester
Failed: The flow was deleted before the test was started.
Running: The flow is currently running.
Stopped: The tester stopped the flow before it completed.
Completed: The flow reached its duration limit.
Receive Statistics
Received Packets The total packets received by the generators analysis
component for this test, after being looped back by the peer
device
Received Bytes The total bytes received by this generator (analysis component)
for this test
L1 Rate The receiving bit rate of Layer-1 traffic, expressed in Mbps
L2 Rate The receiving bit rate of Layer-2 traffic, expressed in Mbps
OOO or Duplicates The out-of-order or duplicate frames received by this generator
(analysis component)
Number of Gaps The number of gaps contained in the numbered sequence. Each
frame contains a sequence number and a timestamp to identify
the gap.

Maximum Gap Maximum size, expressed in frames, of the received gaps
Two-Way Delay
Instantaneous The two-way instantaneous delay, expressed in microseconds
The delay is measured for each frame from the generator to the
loopback device and back to the generator.
Average The average two-way packet delay, expressed in microseconds.
Average Delay The delay is measured for each packet from the generator to
the loopback device and back to the generator (analysis).
Minimum The minimum two-way delay, expressed in microseconds
Maximum The maximum two-way delay, expressed in microseconds
Instantaneous The two-way instantaneous delay variation value, expressed in
microseconds
The delay variation is measured for each set of two consecutive
packets from the generator to the loopback device and back to
the generator.
Average The average two-way delay variation, expressed in
Average DV microseconds
Minimum The minimum two-way delay variation, expressed in

microseconds
Maximum The maximum two-way delay variation, expressed in
microseconds
Test Times
Test Started At The time when the test was started
Test Stopped At The time when the test was completed or halted
11.3.3 Setting Up the Traffic Analyzer

You can set up the traffic monitor to receive and analyze one or two traffic flows, which
can vary in traffic type, VLAN and patterns. The traffic monitor is used in conjunction with
the generator to perform in-service RFC-2544 non-intrusive throughput tests, while end-
user traffic continues flowing without interruption. You configure the traffic monitor from
the remote unit.
Note: In-service tests are unidirectional, as opposed to out-of-service
tests, which are bidirectional (round-trip).


generic traffic or Layer-3 testing with UDP segments, you need to program
the peer unit to have a manual loopback to match the test traffic, with a
swapping action on the MAC addresses, IP addresses and port numbers.
You can do this using the OAM menu.
To set up the RFC-2544 analyzer

1. Access the page SAT RFC-2544 Monitor Configuration.
2. Click a monitor Name to edit its settings.

Note: The page varies depending on which traffic type you select. When
using a VLAN, the VLAN settings may have been changed throughout the
network. These settings will need to reflect the current state of the RFC-
2544 traffic as it enters the unit.
RFC-2544 Monitor Configuration (SATRFC-2544 Monitor Configuration)
Name The name assigned to the monitor
Monitor Name
State The state of the monitor (Enabled or Disabled)
Enable
Monitor Description The description set up to identify the monitor and its
characteristics
Mode Terminal: The RFC-2544 test is terminated at this unit.
Monitor Mode Bypass: The RFC-2544 test measurements are performed but
the traffic follows the rules configured in the Policies for this
specific traffic type.
Port The incoming port of the monitor
Incoming Port
Packet Header Settings
Type The type of test traffic being inspected:

Accedian Ethertype


layered network
MAC Destination This is the MAC address of the terminating Monitor port (i.e. if
this monitor is set in terminal mode type, the MAC destination
will be equal to the incoming port's MAC address). For Layer-2
traffic only.
Range: 07
Y.1731.
segment
UDP segment
Header
specified VLAN ID.
S-VLAN
T-VLAN
C-VLAN

S-VLAN
T-VLAN
C-VLAN
11.3.4 Viewing Traffic Analyzer Test Results

To view a summary of the traffic analyzer test results for each flow
1. Access the page SAT RFC-2544 Monitor Results.
All test results are displayed.
2. For detailed traffic analyzer test results, click the flow details.
RFC-2544 Monitor Results (SAT RFC-2544 Monitor Results)
Name The name assigned to the monitor

State The state of the monitor (Enabled or Disabled)
Average Delay The one-way average delay, expressed in microseconds
Average DV The one-way average delay variation, expressed in
microseconds
Receive Statistics
Received Packets The total packets received by this monitor
Received Bytes The total bytes received by this monitor
L1 Rate The reception bit rate of Layer-1 traffic, expressed in Mbps
L2 Rate The reception bit rate of Layer-2 traffic, expressed in Mbps
OOO or Duplicates The Out-Of-Order or duplicate frames/packets received by this
monitor. Out-Of-Order frames/packets are frames or packets
that were received in a different order from that in which they
were sent.
Number of Gaps The number of gaps in the sequence. Each frame contains a
sequence number and a time-stamp to identify the gap.
Maximum Gap The maximum size, expressed in frames, of the gaps
Bad Packets The total packets received by the associated inspector with an
error inside the payload
Bad Bytes The total bytes of the packets that were received with an error
inside the payload
Bad Rate The data rate, expressed in Mbps. This is the number of
megabits received in the last second with an error inside the
payload.
One-Way Delay
Instantaneous The one-way instantaneous delay, expressed in microseconds
Minimum The minimum delay, expressed in microseconds
Maximum The maximum delay, expressed in microseconds
Average The average delay, expressed in microseconds
Instantaneous The one-way instantaneous delay variation, expressed in
microseconds
Minimum The minimum delay variation, expressed in microseconds

Maximum The maximum delay variation, expressed in microseconds
Average The average delay variation, expressed in microseconds
11.3.5 Setting Up a Test Suite

You can run a test suite to determine whether a network section or a specific device
conforms to a Service Level Agreement (SLA) or an Ethernet standard. You can define a
total of 16 test suites and store up to 32 test reports.
When configuring a test suite, you have the choice of enabling one or more of the
following tests:
Throughput
Frame loss
Delay
Back-to-back
You must also set information pertaining to the remote peer (Peer settings) and the test
frame contents. Various parameters are configurable, depending on the type of test
traffic.
generic traffic or Layer-3/Layer-3 generic testing with UDP segments, you
need to program the peer unit to have a manual loopback to match the
test traffic, with a swapping action on the MAC addresses, IP addresses
and port numbers, as needed. You can do this using the OAM menu.
Refer to the table at the end of this procedure for more information on the different tests
and settings.
To set up a test suite

1. Access the page SAT RFC-2544 Testsuite Configuration.
A summary of all test suites that have been set up is displayed.
2. Click the Add button to add a new test suite or click the Name of an existing test suite
to edit its settings.
3. Select the different tests to run, complete their corresponding settings and other
required fields, then click Apply.

RFC-2544 Test Suite Configuration (SAT RFC-2544 Testsuite Configuration)

Name The name of the test suite
Suite Name A maximum of 16 test suites can be created.
Description The description configured to identify the test suite and its
Suite Description characteristics
Jumbo Frame Size The size, expressed in bytes, of the user-defined jumbo frame
that will be used, if selected for the tests
Default: 2000
Maximum: 10240
Example range: 1518 to 10240
Note: The size must be less than or equal to the port's MTU.
Binary Duration The duration, expressed in seconds, of each trial completed
during the binary search for the maximum throughput
Default: 2 seconds
Range: 1 to 10 seconds
Outgoing Port The port from which to send the flow(s)
Enable Strict Failure Select this box to enable failure on Out Of Order (OOO) or
duplicate frames/packets. Out of Order frames/packets are
frames/packets that are received in a different order than they
were sent in.
When strict failure is enabled, OOO or duplicate frames/packets
will cause a test to fail, even if all frames/packets were received.
When strict failure is disabled, the unit tolerates OOO and
duplicate frames/packets. If all frames/packets were received,
the test is marked as passed.
Enable Verbose Select this box to have all tests (including any tests that failed)
Report and executed steps appear in the test report.
Test to Run
Enable Throughput Select this box to enable the throughput test.
The throughput test begins by determining the maximum rate
at which the test settings yield no lost frames.
For example, to measure the quality of a wire-speed GigE circuit,
enter a Minimum Rate of 800 Mbps, a Maximum Rate of 1000
Mbps, a Step Size of 10 Mbps and a Binary Duration of 2

seconds. The unit then performs a binary search between 800
Mbps and 1000 Mbps for 2 seconds using 10 Mbps increments
in order to determine the highest rate at which the test can be
performed without failing.
Once the maximum rate is determined, the Throughput test
starts executing the actual test, which involves sending frames
according to selected Frame Size settings for the duration
specified by the Trial Duration.
Enable Delay Select this box to enable the delay and delay variation test.
Once a wire-speed rate with no frame loss has been defined by
the throughput test, the delay and delay variation test
measures the latency and jitter at that specific rate.
Ensure that you have entered all required parameters in the
throughput settings, since some of these parameters are
required by the delay and delay variation test.
Enable Frame Loss Select this box to enable the frame loss test.
The frame loss test verifies that no frames are lost when the
current test settings are used. The unit starts at the maximum
rate defined in the throughput settings section, then steps
down by the value entered in the Step Size parameter of the
Frame Loss settings.
Two consecutive rates must have no frame loss in order to
successfully pass this test. For example, if the Device Under Test
(DUT) is able to perform full wire-speed at GigE, the test runs at
1000Mbps and 980Mbps (for a Step Size of 20Mbps). Both
tests must yield no frame loss in order to be successful,
otherwise a lower rate will be tested.
throughput settings section, since some of these parameters
also apply to the frame loss test.
Enable Back-to-Back Select this box to enable the back-to-back test.
The back-to-back test performs a burst according to the test
settings. For this test to be successful, the DUT must not lose
any frames after a burst. A two-second pause is inserted after
each burst.
throughput settings, since some of these parameters are
required by the back-to-back test.

Peer Settings
Type The type of test traffic may be one of the following:

Accedian Ethertype

swap

layered network
Layer-3 Generic: Layer-2 frames with a generic Layer-3

(UDP) payload. Only to be used with loopback devices
based on the MAC-address swap.
traffic only.
Range: 07
Y.1731.
segment
Source IP Address The source IP address used for the IP header. Applies to Layer-3
generic and IP multicast traffic only.
Note: IP multicast traffic is available for the RFC-2544 traffic
generator. It is unavailable for the RFC-2544 test suite and

Y.1564 SAT.
UDP segment
TWAMP
Layer-3 Y.1564
SAT Protocol
Header Note: If frames with more than three VLAN tags are received by
specified VLAN ID.
S-VLAN
T-VLAN
C-VLAN

Note: If frames with more than three VLAN tags are received by
S-VLAN
T-VLAN
C-VLAN
Throughput Settings
Trial Duration The period of time over which the throughput test will run
Default: 60 seconds
Maximum Rate The upper bound of the rates for which to search, expressed in
Mbps
Range: 1 to 1000 Mbps (1 Gbps). In steps of 0.125 Mbps for
rates from 0 to 12.5 Mbps, and in steps of 1 Mbps for rates
greater than or equal to 13 Mbps.
You must select a Maximum Rate that does not exceed the
capacity of the outgoing port being used for the test suite.
Failure to do so may produce inaccurate results.
Note: The actual transmission rate (TX rate) used during the
throughput test will not necessarily match the value of the
Maximum Rate parameter, since the transmission rate

depends on the results obtained from the binary search
algorithm.
This parameter also applies to the delay and delay variation
test, as well as to the frame loss test.
Minimum Rate The lower bound of rates for which to search, expressed in
Mbps
Range: 1 to 1000 Mbps (1 Gbps). In steps of 0.125 Mbps for
rates from 0 to 12.5 Mbps, and in steps of 1 Mbps for rates
greater than or equal to 13 Mbps.
You must select a Minimum Rate that does not exceed the
capacity of the outgoing port being used for the test suite.
Failure to do so may produce inaccurate results.
Step Size The granularity of the range, expressed in Mbps
Range: A value greater than zero to the maximum rate
Use Fine Stepping Select this box to enable fine stepping in the case of low
bandwidth testing (below 12Mbps). When fine stepping is
enabled, the configured Step Size is ignored. The step size used
for the range is 125 kbps.
Frame Loss The acceptable difference between measured frame losses (n x
0.1%). For example, a setting of 1 would mean a 0.1% frame loss
would be acceptable and not considered as a frame loss by the
test.
Default: 0, which means a target of no frame loss is tolerated
when defining full throughput, i.e. losing a single frame will
cause the test to fail
Frame Size Settings Select the frame sizes to include in the test. By default, the
Jumbo frame size is not selected because it is not a frame size
defined by the RFC-2544 standard.
Note:The frame size you select must be smaller than the port's
MTU. Selecting a higher frame size will prevent you from
running the test.
Delay and Delay Variation Settings
Trial Duration The period of time over which the test is run

Default: 120 seconds
The delay and delay variation test uses also the Maximum Rate,
Minimum Rate and Fine Stepping values set in the Throughput
Settings.
Frame Loss The acceptable difference between measured frame losses (n x
0.1%). For example, a value of 1 would mean a 0.1% frame loss
would be acceptable and considered as no frame loss by the
test.
Default: 0, which means a target of no frame loss is tolerated
when defining full throughput, i.e. losing a single frame will
cause the test to fail
Note: The frame size you select must be smaller than the port's
running the test.
Frame Loss Settings
Trial Duration The period of time over which the test will run
Default: 60 seconds
The frame loss test also uses the Maximum Rate, Minimum
Rate and Fine Stepping values set in the Throughput Settings
section.
Step Size The granularity of the range, expressed in Mbps
Note:The frame size you select must be smaller than the port's
running the test.
Back-to-Back Settings
Trial Duration The period of time over which the test is run
Range: 1 to 10000 milliseconds
Default: 2000 milliseconds

Repeat The number of bursts to perform for each frame/packet size. A
two-second pause is inserted after each burst.
Default: 50 bursts
Range: to 100 bursts
Note: The frame size you select must be smaller than the port's
running the test.

11.3.6 Running a Test Suite and Viewing Test Reports

Once you have set up a test suite, you can run it and view its report. Since each test is
association with one test report, you have to configure a new report each time you want
to run a new test. You can run a specific test suite many times as long as you configure a
new report.
To run a test suite

1. Access the page SAT RFC-2544 Testsuite Reports.
A summary of all test suite reports is displayed. For more information on specific
parameters, refer to the table at the end of this procedure.
2. Click the Start New Testsuite button to configure a new report.
3. Complete the required fields, then click Run.

RFC-2544 Test Suite Reports (SAT RFC-2544 Testsuite Reports)
File Name The name assigned to the report
A maximum of 32 test reports can be created.
Status The report's current status is listed for all tests that have been
created. Possible values are:
Failed: An error occurred during the test suite execution.
Running: The test suite is currently running.
Stopped: A user stopped the test suite during its execution.
Completed: The Test suite has completed.
Description A concise description used to help identify the report

Technician Name The name of the individual who executed the test suite
Testsuite Select the test suite you want to run for this report.
Configuration
Special Note Any additional report-related details that were not included in
the previous field
To view, save or delete a test suite report

1. Access the page SAT RFC-2544 Testsuite Report.

A summary of all test suite reports is displayed. For more information on specific
parameters, refer to the table "RFC-2544 Test Suite Reports (SAT RFC-2544
Testsuite Reports)" on page 348.
2. Click the Name of an existing test suite report to view its report file or to perform
other actions.
Note:You can click Stop to stop a test while it is running. You can then
click either Save to save it on the management station as a text file or
Delete to delete it.

11.4 Using Y.1564 for Service Activation Testing

This section describes how to set up Y.1564 in your Metro Ethernet network to perform
end-to-end Ethernet service activation tests.
The Accedian implementation of Y.1564 supports the following types of tests:
Layer-2 two-way testing
Layer-3 two-way testing
Layer-2 one-way testing
Layer-3 one-way testing

The steps required to set up Y.1564 are:
Set up a Y.1564 test:See "Setting Up a Y.1564 Test" on page 350.
Set up one or more Y.1564 services:See "Setting Up a Y.1564 Service" on page 353.
Before running a one-way test, you must also set up the SAT protocol so that devices
performing the one-way Y.1564 test communicate. Refer to "Setting Up the SAT Protocol"
on page 362 for more information on the SAT protocol.
Once these set up steps are complete, you can then run a test and view the results, as
described in "Running a Y.1564 Test and Viewing Test Results" on page 360.
11.4.1 Setting Up a Y.1564 Test

You can run a Y.1564 test to determine the conformance of a network section or a specific
device to a service level agreement (SLA) and/or to meet Ethernet standards. A total of 16
tests can be defined.
SAT Reporting is a system feature that enables you to have RFC-2544 or Y.1564 test
reports automatically pushed from the unit to a designated remote server (FTP, SFTP,
TFTP or SCP). Automatically pushing test reports to the server means you can view the
test results more quickly, since you do not have to manually poll the remote server to
determine whether or not the test has completed execution.
For details on how to automate report uploads to a remote server, see "Setting Up SAT
Reporting" on page 322.
Note: All reports are available in text or XML format.
When setting up the test, you also have to set the information relative to the remote peer
(Peer settings) and the test frame contents. To view the complete list of elements that
can be configured for the test, refer to the table "Y.1564 Test Configuration (SAT Y.1564
Configuration)".
Refer also to the ITU-T Y.1564 standard for the definition of parameters and tests.

Note: The contains pre-programmed RFC-2544 and Y.1564 loopbacks for

Layer-2 or Layer-2 Accedian frames. For Layer-2 generic traffic or Layer-3
testing with UDP segments, you need to program the peer unit to have a
manual loopback to match the test traffic, with a swapping action on the
MAC addresses, IP addresses and port numbers. You can do this using
the OAM menu.
To set up a Y.1564 test

1. Access the page SAT Y.1564 Configuration.
A summary of all tests that have been set up is displayed.
2. Click the Add button to add a new test or click the Name of an existing test to edit its
settings.
3. Select the different tests to run. Enter values for the corresponding settings and
other fields, then click Apply.
Y.1564 Test Configuration (SAT Y.1564 Configuration)
Name The name of the Y.1564 test
Test Name
Description A description to identify the Y.1564 test and its characteristics
Test Description
Outgoing Port The port on which to send the flow(s)
Test to Run
Configuration Step Duration, expressed in seconds, of each step during the
Duration (Seconds) configuration test
Enable Configuration Enabling the configuration test allows use of the policing test
Test and step test under each service (traffic flow) configured.
It allows you to run successive tests at rates of 25% CIR, 50%
CIR, 75% CIR, and 100% of CIR, CIR+EIR, and Policing.
For Policing:
If EIR < 20 % x CIR, Policing Rate = (125 % x CIR) + EIR
If EIR 20 % x CIR, Policing Rate = CIR + (125 % x EIR)
Enable Parallel Enable or disable the Parallel Service Configuration test.

Configuration Test
Enable: All enabled services (traffic flows) are run
simultaneously.

Disable: All enabled services (traffic flows) are run

sequentially.
Performance Test The duration of the performance test, expressed in minutes

Duration (Minutes) Range: 1 to 1440 minutes
Enable Performance Enable or disable the performance test.
Test You must configure at least one service when you enable
performance test.
Note:The performance test is run at 100% CIR.
Delay Measurement May be one-way delay or two-way delay.
Type One-way delay measurement requires the SAT protocol (SAT
Protocol Configuration) to be enabled on both devices
performing the Y.1564 test.
Device Time SYNC When this option is checked, the tests will be performed only if
Mandatory both devices performing the Y.1564 test are synchronized using
one of the supported timing mechanisms (NTP or PTP).
When this option is unchecked, the tests will be performed, but
valid results will be displayed only if both devices performing
the Y.1564 test are synchronized using one of the supported
timing mechanisms (NTP or PTP). This type of test may be useful
to test applications where delay is not important, but other
parameters, such as CIR or EIR, are important.
Note:For one-way delay measurement only.
Remote Unit Settings
Type The type of test traffic:

Accedian Ethertype

swap

layered network
Note: Layer-2 generic is for two-way measurements only.

traffic only.
Range: 07
Y.1731.
segment
UDP segment
TWAMP
Layer-3 Y.1564
SAT Protocol
11.4.2 Setting Up a Y.1564 Service

Once you have set up a Y.1564 test, you must define one to eight services (traffic flows)
for testing.
All required resources are reserved in a single operation at the beginning of a Y.1564 test,
whether the testing to be performed is parallel or sequential. The sum of the bandwidth

required for all services cannot exceed the port's total bandwidth. In addition, policing
(when used) requires an extra 20% of the port's total bandwidth. For example, if you are
setting up eight Y.1564 services to be tested sequentially with policing on a 1 Gbps link,
you cannot allocate more than 800 Mbps to these services combined, otherwise the test
will not be executed.
Refer to the ITU-T Y.1564 standard for the definition of parameters and tests.
To set up a Y.1564 service

1. Access the page SAT Y.1564 Configuration.
A summary of all tests that have been defined is displayed.
2. Click the Name of a test to edit its settings.
The screen refreshes to display the test details, as well as a list of its services.
3. Click the Name of a service from the Service List at the bottom of the page to edit its
settings.
The Y.1563 [Service_Number] Service Configuration page appears.
Y.1564 Service Configuration (SAT Y.1564 Configuration)
State Enable or disable the service for this Y.1564 test.
Enable Service
Name Name of the Y.1564 service
Service Name
Test Configuration
Policing Test Enabled Enable or disable testing above the CIR:
If EIR < 20 % x CIR, Policing Rate = (125 % x CIR) + EIR
If EIR 20 % x CIR, Policing Rate = CIR + (125 % x EIR)
Step Test Enabled Enables or disables running successive tests at a rate of 25% CIR,
50% CIR, 75% CIR, 100% CIR, and CIR+EIR
Availability Enabled Enable or disable availability measurements based on the
configured frame loss ratio.
Bandwidth Profile
CIR (in Mbps) The CIR value provided here can be interpreted as the
maximum sustained information rate that the network has

committed to transfer while meeting the performance level
guaranteed in the Service Level Agreement (SLA).
The CIR and EIR values specified in the bandwidth profile are
used by the Y.1564 tool to define the Configuration,
Performance and Policing Tests to be executed.
Range: 0 to 1000 Mbps (steps of 0.125 Mbps)
Committed Burst Size This parameter is not currently used. For future
(in kBytes) implementation.
EIR (in Mbps) The EIR value provided here can be interpreted as the maximum
sustained information rate, over and above the CIR, at which
traffic is carried though the network, if possible.
The CIR and EIR values specified in the bandwidth profile are
used by the Y.1564 tool to define the Configuration,
Performance and Policing Tests to be executed.
Range: 0 to 1000 Mbps (expressed in steps of 0.125 Mbps)
Excess Burst Size (in This parameter is not currently used. For future
kBytes) implementation.
Frame Size Type The test will be performed with this type of frame size.

Fixed frame size
EMIX
Frame Size (in bytes) The size of each frame for the test traffic
Note:Only available when the Frame Size Type is set to Fixed.
Acceptable values range from 64 bytes to 10240 bytes.
User-Defined (in The size of each user-defined packet for the test traffic
octets) Set to EMIX for the Frame Size Type only.
Range:64 to 10240 bytes
Sequence of Sizes For EMIX frame size type, the packet size values used in the test
and the specific sequence in which they are sent
Available sizes are:
a = 64 bytes
b =128 bytes
c = 256 bytes

d = 512 bytes
e = 1024 bytes
f = 1280 bytes
g = 1518 bytes
h = MTU
u = user-defined size
Default value: abceg
Service Acceptance Criteria
Frame Transfer Delay For one- or two-way delay measurements, the delay below
(in s) which the test passes. Expressed in microseconds.
Frame Delay For one- or two-way delay variation measurements, the delay
Variation (in s) variation below which the test passes. Expressed in
microseconds.
Frame Loss Ratio The ratio below which the test passes
M Factor The M factor (margin factor) is added to the Service Acceptance
Criteria in the policing test to take into account the effect of the
CBS and EBS on the total rate.
The policing test will pass if IR-T CIR + EIR + M.
Where:
IR-T: Total Information Rate
CIR: Committed Information Rate
EIR: Excess Information Rate
M: M factor
Default value: 1 Mbps
Frame Transfer Delay Make a selection from the drop-down list to indicate whether
Type the test's acceptance criteria should be based on the Frame
Transfer Delay Maximum or the Frame Transfer Delay Average
values.
Frame Delay Make a selection from the drop-down list to indicate whether
Variation Type the test's acceptance criteria should be based on the Frame
Delay Variation Maximum or the Frame Delay Variation Average

values.
MAC Settings (Layer-2 Traffic Only)
MACDestination For each service, this sets the destination MAC address and
overwrites the global MAC address of the Y.1564 test.
Overwrite Per Test Enable the overwriting of the global destination MAC address of
Destination the Y.1564 test.
MACAddress
Y.1731 MEG Level For each service, this sets the Y.1731 MEG level and overwrites
the global Y.1731 MEG level of the Y.1564 test.
Overwrite Per Test Enable the overwriting of the global Y.1731 MEG level of the
MEG Level Y.1564 test.
IPSettings (Layer-3 Traffic Only)
Destination IP For each service, this sets the destination IP address and
Address overwrites the global IPaddress of the Y.1564 test.
Overwrite Per Test Enable the overwriting of the global destination IPaddress of
Destination IP the Y.1564 test.
Address
DSCP For each service, this sets the DSCP and overwrites the global
DSCP of the Y.1564 test.
Overwrite Per Test Enable the overwriting of the global DSCP of the Y.1564 test.
DSCP
VLANSettings
Header
specified VLAN ID.
S-VLAN
T-VLAN
C-VLAN

S-VLAN
T-VLAN
C-VLAN
Far-End Verification (One-Way Testing Only)
DSCP Check Check this option if you want the peer unit to verify that the
DSCP value in the test traffic has not changed. If it has changed,
the test will fail.
DSCP Unpreserve Check this option if you expect the DSCP value to change before
it reaches the far end.
This option also instructs the peer unit to verify the value
received against the one defined for the Far-End Expected
Value. The test will fail if this criterion is not met.
Far-End Expected The value expected by the far-end when the DSCP unpreserve
Value option is checked
VLAN 1 (or VLAN 2) Header
No VLAN Check Check this option if you want to validate that the frames

received at the far-end do not have a first (or second) VLAN tag,
i.e. that far-end frames are untagged.
PCP Check Check this option if you want the peer unit to verify that the
PCP value in the test traffic has not changed. If it has changed,
the test will fail.
PCP Unpreserve Check this option if you expect the PCP value to change before
it reaches the far-end.
Far-End Expected The value expected by the far-end when the PCP unpreserve
DEI Check Check this option if you want the peer unit to verify that the DEI
value in the test traffic has not changed. If it has changed, the
test will fail.
DEI Unpreserve Check this option if you expect the DEI value to change before it
reaches the far end.
Far-End Expected The value expected by the far-end when the DEI unpreserve
VLANIDCheck Check this option if you want the peer unit to verify that the
VLANID for the test traffic has not changed. If it has changed,
the test will fail.
ID Unpreserve Check this option if you expect the VLANID to change before it
reaches the far end.
Far-End Expected The value expected by the far-end when the IDunpreserve

11.4.3 Running a Y.1564 Test and Viewing Test Results

Once you have set up a Y.1564 test, you can run it and view its report. Since each test is
associated with one test report, you have to define a new report each time you want to
run a new test. You can run a specific test many times as long as you define a new report
each time.
To run a Y.1564 test

1. Access the page SAT Y.1564 Results.
A summary of all test reports is displayed.
2. Click the Start button to define a new report.

For more information on specific parameters, refer to the second table below.
Y.1564 Service Activation (SAT Y.1564 Results)
Name The name assigned to the test report
Status The test's current status
Failed: An error occurred during the test execution.
Running: The test is currently running.
Canceled: A user stopped the test during its execution.
Completed: The test has completed.
Description The description to identify the test
Y.1564 Report Configuration (SAT Y.1564 Results)

File Name The name assigned to the test report file
Technician Name The name of the individual who executed the test
Test Configuration Select the test configuration you want to run for this test.
Special Note Any additional information relative to the test appears here.

To view, edit or export a Y.1564 test report

1. Access the page SAT Y.1564 Results.
A summary of all test reports is displayed. For more information on specific
parameters, refer to the table "Y.1564 Service Activation (SAT Y.1564 Results)"
above.
2. To view detailed results from a test, click the Name of the test report.
You will be able to perform other actions from the page that is displayed.
3. To prevent a test from running, click Stop.
4. To edit a report, click Edit.
5. To export the report to a text file and save it on the management station, click
Export.
Y.1564 Test Configuration Results (SAT Y.1564 Results)
Name The name of the Y.1564 service being tested
25% CIR The test's current status
50% CIR The available options are:
75% CIR PASS: This test passed the test criteria.
100% CIR
FAIL: This test failed the test criteria.
CIR+EIR
Policing N/A: This test is not performed as per the test
configuration.
Performance

11.5 Using the SATProtocol

Devices performing Y.1564 tests use the SAT protocol for communication and for testing
traffic.
Note: The SAT protocol must be enabled on all devices performing a one-
way Y.1564 test. It is not used for two-way tests.
11.5.1 Setting Up the SAT Protocol

To set up the SATprotocol
1. Access the page SAT Protocol Configuration.

SATProtocol Configuration (SAT Protocol Configuration)
Enable Enable or disable the server side of the SAT protocol (Enabled by
default).
Note: The SATprotocol must only be enabled on the server
(peer device) for one-way tests. Furthermore, it must be
enabled for both Layer-2 and Layer-3 traffic.
Protocol UDP Port The UDP port used by the SAT protocol
Note: This parameter must be defined on both the generator
and the server (peer device) for one-way tests, and only for
Layer-3 traffic.
One-Way Traffic UDP The destination UDP port used for one-way traffic
Port Note: This parameter must be defined on both the generator
and the server (peer device) for one-way tests, and only for
Layer-3 traffic.
TWAMP

Layer-3 Y.1564
SAT Protocol
11.5.2 Viewing SATProtocol Statistics

Viewing the statistics of the SAT protocol can be useful when troubleshooting.
To view SATprotocol statistics

1. Access the page SAT Protocol Statistics.
SAT Protocol Server Statistics (SAT Protocol Statistics)
One-Way Session The number of one-way session requests sent or received
Request
One-Way Session The number of one-way session acknowledgements sent or
Acknowledge received
Results Request The number of results requests sent or received
Results Acknowledge The number of results acknowledgements sent or received
Reset Request The number of reset requests sent or received
Reset Acknowledge The number of reset acknowledgements sent or received
Release Request The number of release requests sent or received
Release Acknowledge The number of release acknowledgements sent or received
Setup Request The number of setup requests sent or received
Setup Acknowledge The number of setup acknowledgements sent or received
Terminate The number of terminate notification sent or received
Notification
Keepalive The number of keep-alive messages sent or received
Unknown The number of unknown messages sent or received. For
example when two devices run different firmware versions and
the device running the older firmware does not recognize the
newer firmware messages sent by the other device.

11.5.3 Viewing SATProtocol Sessions

You can view the current sessions established by the unit using the SAT protocol. Viewing
these sessions can be useful for troubleshooting purposes, for example, if you believe
that a test should be running and no resources are available to open a SAT protocol
session.
To view SATprotocol sessions

1. Access the page SAT Protocol Sessions.
SAT Protocol Current Server Sessions (SAT Protocol Sessions)
Index Unique index for this SAT protocol session
Identification Information to identify this session
Host Name Remote unit host name

12 Managing Loopbacks
This chapter describes how to manage loopbacks; it contains the following sections:
12.1 Understanding Loopback Testing 366
12.2 Setting Up and Enabling Loopbacks 367

12.1 Understanding Loopback Testing

Layer14 loopbacks (MAC address, IP address & port swap) permit remote QoS testing
for Ethernet, IP/MPLS and triple-play services. Loopbacks can be established by any of
the following combination of parameters:
VLAN
Source or destination address
TCP/UDP port
Service level
Loopbacks can be performed in-band or out-of-band, so customer traffic continues to
flow while tests are performed on selected streams.
The unit allows for two types of loopback:

Local (or private) loopback: loops back all traffic matching the type of loopback in
the setup (Iometrix L1, EXFO L2, EXFO L3, Custom)
Remotely-controled loopback: Loops back traffic and is initiated upon the reception
of a predefined frame type (JDSU/Acterna, Sunrise)

12.2 Setting Up and Enabling Loopbacks

Follow the steps below to set up a local loopback:
Define filters for capturing traffic (required for custom loopbacks only), see "Defining
Filters" on page 167.
Create an OAM instance, see "Setting Up an OAM Instance" on page 232.
Create the loopback, as explained in the following procedure.
To set up a local loopback

1. Access the page OAM Loopback.
A summary of all OAMinstances that have been set up is displayed.
2. Click the instance's Name to edit its settings.
3. Enter values in the required fields (located at the top part of the page), then click
Apply.
Note: Only the fields listed in the following table are required for a local
loopback. Leave all other fields at their default settings.
OAM Loopback (OAM Loopback)
Name The OAM instance name, as defined in the OAM Configuration
page
State The current state of the loopback. An enabled loopback may
Lpbk State not necessarily loop back traffic; this depends on the location
setting. An instance enabled for a remotely-controled loopback
is not shown in this field.
Lpbk Mode When the loopback control logic is enabled, this field displays
the loopback mode that has been selected for the given port.
This parameter is always set to Private.
A value of Private indicates that either no 802.3ah loopback is
active or that a private (i.e., proprietary) loopback has been
configured.
When using the private loopback mode, you can select filters or
preset OEM loopback types, which creates an in-service
loopback that allows other traffic to flow through.

Location Indicates whether the loopback is controled locally or remotely.
Once enabled, a local loopback immediately applies the
loopback to the unit as programmed. An enabled remote
loopback instructs the unit to transmit a loopback request to its
OAM partner.
Loopback Enable Select this box to activate a locally-controled loopback, then
choose a Type from the drop-down list.
Note:Do not select this box to activate a remote loopback.
Instead, indicate the type of remote device in the Remote
Loopback Enable section below.
Type Type may be one of the following:
Iometrix L1: Iometrix cNode level 1. Loops back all frames
that have a destination address equal to 00:30:79:FF:FF:FF
Exfo L2: Loops back all frames that have a source MAC OUI
equal to 00:03:01
Exfo L3: Loops back all UDP echo service packets
AnaCise L2: Loops back all frames that have a source MAC
OUI equal to 00:18:75
AnaCise L3: Loops back all UDP echo service packets
Custom: Loops back all traffic that matches the user-

defined filter (Filter Type and related fields)
802.3ah: Indicates that a loopback has been activated on

the port as a result of receiving a 802.3ah OAM PDU. At the
same time, the Loopback State field is updated to Enabled .
Persistent Enables the loopback at start-up time

Note:This option only applies to locally-controled loopbacks
with no timeout.
Filter Type The type of filter to be applied to the loopback traffic:
L2 Filter
IPv4 Filter
L2 Filter The L2 filter to be applied to loopback traffic, if the filter type is

L2 Filter
IPv4 Filter The IPv4 filter to be applied to loopback traffic, if the filter type

is IPv4 Filter
Actions The action may be one or more of the following:
Swap MAC Addresses: Swaps the source and destination
MAC addresses
Swap IP Addresses: Swaps the source and destination IP

addresses
Swap TCP/UDP Ports: Swaps the source and destination

TCP/UDP ports
Drop Opposite Traffic Drops the traffic entering the device on the opposite port
Note: enabling this option interrupts the Ethernet service in
one direction.
Loopback Timeout Number of minutes for the loopback to remain enabled. When
the timeout expires, the loopback is automatically terminated.
Remote Loopback Enable
JDSU/Acterna Select this box to indicate that this remote loopback will be
controled by a JDSU/Acterna device.
Enable Discovery Select this box to indicate that this remote loopback will accept
Loop Commands JDSU/Acterna discovery loopback commands.
Sunrise Select this box to indicate that this remote loopback will be
controled by a Sunrise device.
The unit supports tests on Layer2 and Layer3.
VeEX Select this box to indicate that this remote loopback will be
controled by a VeEX device.
The unit supports tests on Layer2, Layer3 and Layer4.
OAM 802.3ah Select this box to indicate that this remote loopback will be
controled by a device that supports the OAM 802.3ah protocol.
Accept Tagged Select this box to indicate that this remote loopback will accept
Loopback tagged loopback commands.
Commands This option is only valid for untagged OAM instances. Tagged
OAM instances only accept loopback commands from a specific
VLAN.

13 Managing Alarms and System Messages

This chapter describes functions related to alarms and system messages; it contains the
following sections:
13.1 Managing Alarms 372
13.2 Viewing Dry-Contact Alarms 385
13.3 Managing Syslog Messages 386
13.4 Managing the SNMP Agent 388
13.5 Managing History Files 390

13.1 Managing Alarms

The unit provides alarm functions to monitor and report on the status of the unit, of the
traffic performance and of other components.
13.1.1 Setting General Alarms

To set up general alarms
1. Access the page System Alarm General.

Alarm Settings (System Alarm General)
Notification
Enable LED Reporting Enables the reporting of alarms by activating the unit LED that is
appropriate and that corresponds to the severity, e.g. minor,
major or critical
Enable Syslog Enables the reporting of alarms by creating entries in the syslog
Reporting
Enable SNMP Enables the reporting of alarms via SNMP traps from Accedians
Reporting private MIB
Enable 802.3ah Enables reporting of alarms via 802.3ah OAMPDUs using
Reporting organization-specific events
Thresholds
Threshold On The delay after an event is detected before the alarm
(Soaking time in notification occurs.
msecs)
Threshold Off The delay after an event clears before the alarm notification
(Soaking time in clears.
msecs)

13.1.2 Customizing Alarms

To customize an alarm
1. Access the page System Alarm Configuration.
The settings for all alarms are displayed. For more information on specific parameters,
refer to the table at the end of this procedure.
2. Click the Number of the alarm that you want to edit.

Alarm Configuration (System Alarm Configuration)
Number The unique number that identifies this alarm. This number is
assigned by the unit and cannot be modified.
This alarm number is composed of three fields, the module
number, the instance number and the error number. The
format is AA.BBBB.CC, where the parameters are as follows:
AA: Module number (1-99)
BBBB: Instance number (0001-9999).
CC: Error number (01-99)

A module number is assigned for each alarm in the system and
may be one of the following:
1: Port module for link down and other related alarms
2: SFP module for Rx/Tx power, temp, vcc and lbc alarms
and warnings
3: PAA module for Continuity Check, Delay, Packet Loss and

other related alarms
4: SOAM module for Continuity Check, Delay, Packet Loss

and other related alarms
5: Unassigned
6: Unassigned
7: System module such as NTP and other agents

8: Environmental module for power supplies and

temperature sensors
9: ERP module
10: Unassigned
11: TWAMP
Enable Indicates whether the alarm is enabled (true) or disabled (false).

If enabled, alarms are reported.
Severity The severity of the alarm. If LED reporting is enabled on the
Alarm General page, the Minor, Major and Critical alarms are
indicated on the unit's front panel LEDs.
Informational: No effect on service. Provides status
information.
Minor: An error condition has occurred that does not

seriously affect system functionality.
Major: A serious degradation of service or hardware

malfunction has occurred which requires immediate
attention to restore system functionality.
Critical: A service-affecting condition has occurred that

requires immediate corrective action.
Service Affecting Alarms may be displayed as service affecting or non-service

affecting.
Description Textual description of the alarm. The description is displayed in
the Show Alarm page.
Note:This description cannot be modified.
13.1.3 Viewing Alarms

To view the status of an alarm
1. Access the page Show Alarm.
The alarm status is displayed.

Alarm Status (Show Alarm)

Status The status LED is ON if the alarm is enabled and has been
triggered
Number The unique number identifying this alarm
This number is assigned by the unit and cannot be modified.
This alarm number is composed of three fields, the module
number, the instance number and the error number. The
format is AA.BBBB.CC, where the parameters are as follows:
AA: Module number (1-99)
BBBB: Instance number (0001-9999)
CC: Error number (01-99)

A module number is assigned for each alarm in the system and
may be one of the following:
1: Port module for link down and other related alarms
2: SFP module for Rx/Tx power, temp, vcc and lbc alarms
and warnings
3: PAA module for Continuity Check, Delay, Frame Loss and

other related alarms
4: SOAM module for Continuity Check, Delay, Packet Loss

and other related alarms
5: Unassigned
6: Unassigned
7: System module such as NTP and other agents
8: Environmental module for power supplies, temperature

sensors and dry contact
9: ERP module
10: Unassigned
11: TWAMP
Presence Indicates whether the alarm is currently present (true) or not

(false)

Severity The severity of the alarm. Possible values may be one of the
following:
Warning: A non-service-affecting condition has occurred
that required attention.
Minor: An error condition has occurred that does not

seriously affect system functionality.
Major: A serious degradation of service or hardware

malfunction has occurred which requires immediate
attention to restore system functionality.
Critical: A service-affecting condition has occurred that

requires immediate corrective action.
Service Affecting Alarms may be displayed as one of the following:

Service Affecting (SA)
Non-Service Affecting (NSA)
Description A textual description of the alarm

Message This is displayed only when the alarm has changed status (the
alarm was turned ON or OFF). The message explains why it was
turned on or off, e.g. temperature was above the threshold.
Last Change When the alarm changed status
Refer to the following table for a list of all alarms supported and their default description.
Supported Alarms: GT Performance Element
Number Default Description
Port module for link down and other related alarms
1.0001.01 Link down on PORT-1 port
1.0001.02 Loopback on port PORT-1
1.0001.04 Fault propagation caused link down on port PORT-1


1.0005.01 Link down on Management port
1.0006.01 Link down on LAG-1 port
1.0006.02 Loopback on port LAG-1
1.0006.03 Sub-port speed mismatch on port LAG-1
1.0006.04 Fault propagation caused link down on port LAG-1
1.0007.01 Link down on LAG-2 port
1.0007.02 Loopback on port LAG-2
1.0007.03 Alarm Sub-port speed mismatch on port LAG-2
1.0007.04 Fault propagation caused link down on port LAG-2
SFP module for Rx/Tx power, temperature, VCC and LBC alarms and warnings
In this section, yyyy = SFP module, where 0001 = SFP-1, 0002 = SFP-2, 0003 = SFP-3, 0004
= SFP-4
2.yyyy.01 <SFP module> temperature high alarm
2.yyyy.02 <SFP module> temperature low alarm
2.yyyy.03 <SFP module> temperature high warning
2.yyyy.04 <SFP module> temperature low warning
2.yyyy.05 <SFP module> supply voltage high alarm
2.yyyy.06 <SFP module> supply voltage low alarm
2.yyyy.07 <SFP module> supply voltage high warning
2.yyyy.08 <SFP module> supply voltage low warning
2.yyyy.09 <SFP module> laser bias current high alarm
2.yyyy.10 <SFP module> laser bias current low alarm
2.yyyy.11 <SFP module> laser bias current high warning


2.yyyy.12 <SFP module> laser bias current low warning
2.yyyy.13 <SFP module> transmit power high alarm
2.yyyy.14 <SFP module> transmit power low alarm
2.yyyy.15 <SFP module> transmit power high warning
2.yyyy.16 <SFP module> transmit power low warning
2.yyyy.17 <SFP module> receive power high alarm
2.yyyy.18 <SFP module> receive power low alarm
2.yyyy.19 <SFP module> receive power high warning
2.yyyy.20 <SFP module> receive power low warning
2.yyyy.21 <SFP module> not present
Performance Assurance Agent alarms
In this section, yyyy = PAA instance index.
3.yyyy.01 <PAA probe name> PAA_CC_ALERT
3.yyyy.02 <PAA probe name> PAA_PL_ALERT
3.yyyy.03 <PAA probe name> PAA_OW_DELAY_ALERT
3.yyyy.04 <PAA probe name> PAA_OW_AVG_DELAY_ALERT
3.yyyy.05 <PAA probe name> PAA_OW_DV_ALERT
3.yyyy.06 <PAA probe name> PAA_OW_AVG_DV_ALERT
3.yyyy.07 <PAA probe name> PAA_TW_DELAY_ALERT
3.yyyy.08 <PAA probe name> PAA_TW_AVG_DELAY_ALERT
3.yyyy.09 <PAA probe name> PAA_TW_DV_ALERT
3.yyyy.10 <PAA probe name> PAA_TW_AVG_DV_ALERT
3.yyyy.11 <PAA probe name> PAA_VLAN1_ID_ALERT
3.yyyy.12 <PAA probe name> PAA_VLAN2_ID_ALERT
3.yyyy.13 <PAA probe name> PAA_VLAN1_PRIO_ALERT
3.yyyy.14 <PAA probe name> PAA_VLAN2_PRIO_ALERT
3.yyyy.15 <PAA probe name> PAA_DSCP_ALERT


SOAM module for Continuity Check, Delay, Packet Loss and other related alarms
In this section, zzzz = CFM instance index.
4.zzzz.01 RDI on down MEP, MEPID <ID>, port <port name>, VID <ID>,
level <#>
4.zzzz.02 MAC status on down MEP, MEPID <ID>, port <port name>, VID
<ID>, level <#>
4.zzzz.03 Remote CCM on down MEP, MEPID <ID>, port <port name>,
VID <ID>, level <#>
4.zzzz.04 Errored CCM on down MEP, MEPID <ID>, port <port name>,
VID <ID>, level <#>
4.zzzz.05 Cross-connected CCM on down MEP, MEPID <ID>, port <port
name>, VID <ID>, level <#>
4.zzzz.06 AIS on down MEP, MEPID <ID>, port <port name>, VID <ID>,
level <#>
4.zzzz.07 One-way delay on down MEP, MEPID <ID>, port <port name>,
VID <ID>, level <#>
4.zzzz.08 One-way average delay on down MEP, MEPID <ID>, port <port
4.zzzz.09 One-way delay variation on down MEP, MEPID <ID>, port <port
4.zzzz.10 One-way average delay variation on down MEP, MEPID <ID>,
port <port name>, VID <ID>, level <#>
4.zzzz.11 Two-way delay on down MEP, MEPID <ID>, port <port name>,
VID <ID>, level <#>
4.zzzz.12 Two-way average delay on down MEP, MEPID <ID>, port <port
4.zzzz.13 Two-way delay variation on down MEP, MEPID <ID>, port <port
4.zzzz.14 Two-way average delay variation on down MEP, MEPID <ID>,
4.zzzz.15 Excessive packet loss on down MEP, MEPID <ID>, port <port
4.yyyy.16 CSF-LOS on down MEP, MEPID <ID>, port <port name>, VID
<ID>, level <#>


4.yyyy.17 CSF-FDI/AIS on down MEP, MEPID <ID>, port <port name>, VID
<ID>, level <#>
4.yyyy.18 CSF-RDI on down MEP, MEPID <ID>, port <port name>, VID
<ID>, level <#>
4.yyyy.19 Excessive SLM near-end packet loss on down MEP, MEPID <ID>,
4.yyyy.20 Excessive SLM far-end packet loss on down MEP, MEPID <ID>,
SyncE
6.0001.01 SyncE loss of primary reference clock
6.0001.02 SyncE loss of secondary reference clock
6.0001.03 SyncE Forced to Free-Running or Local Clock
6.0001.04 SyncE ESMC QL failure of Primary Reference Clock
6.0001.05 SyncE ESMC QL failure of Secondary Reference Clock
System module such as VCAgent, NTP and other agents
7.0001.01 NTP client lost server communication
7.0001.02 NTP Time-of-day synchronization - May affect one-way delay
measurements
7.0001.03 GPS communication May affect one-way delay measurements
7.0001.04 PTP client failure communication with server
7.0001.05 PTP Time-of-day synchronization - May affect one-way delay
measurements
7.0001.06 NTP client used interface without timestamp capability
7.0001.07 PTP client used interface without timestamp capability
7.0001.08 Remote NTP server used an interface without timestamp
capability
7.0004.01 VCAgent communication failure with EMS
7.0004.02 VCAgent High resolution Policy instances validation
7.0004.03 VCAgent High resolution Regulator instances validation
7.0004.04 VCAgent High resolution PAA instances validation
7.0004.05 VCAgent High resolution SOAMPL instances validation


7.0004.06 VCAgent High resolution SOAM DMM instances validation
7.0004.07 VCAgent High resolution SOAM SA instances validation
7.0004.08 VCAgent High resolution SOAM SA Metrics instances validation
7.0004.09 VCAgent High resolution SOAM SLM instances validation
7.0004.10 VCAgent Policy statistics buffer full
7.0004.11 VCAgent Regulator statistics buffer full
7.0004.12 VCAgent PAA statistics buffer full
7.0004.13 VCAgent SOAM PL statistics buffer full
7.0004.14 VCAgent SOAM DMM statistics buffer full
7.0004.15 VCAgent SOAM SA statistics buffer full
7.0004.16 VCAgent SOAM SA Metrics statistics buffer full
7.0004.17 VCAgent SOAM SLM statistics buffer full
7.0004.18 VCAgent High resolution TWAMP-GEN instances validation
7.0004.19 VCAgent TWAMP-GEN statistics buffer full
7.0004.20 VCAgent High resolution TWAMP instances validation
7.0004.21 VCAgent TWAMP statistics buffer full
7.0004.22 VCAgent high-resolution shaper instances validation
7.0004.23 VCAgent shaper statistics buffer full
7.0004.24 VCAgent high-resolution port instances validation
7.0004.25 VCAgent port statistics buffer full
Environmental module for power supplies, temperature sensors and dry contact
8.0000.01 First overheat threshold
8.0000.02 Second overheat threshold
8.0000.04 No power supply on feed A
8.0000.05 No power supply on feed B
8.0000.06 Input 1 Active
8.0000.07 Input 2 Active
8.0000.08 No power supply on DC feed A


8.0000.09 No power supply on DC feed B
8.0000.40 Fan 1 slow
8.0000.41 Fan 1 failure
8.0001.01 First overheat threshold
8.0001.02 Second overheat threshold
8.0001.40 Fan 2 slow
8.0001.41 Fan 2 failure
ERPmodule
In this section, xxxx = ERP instance index.
9.xxxx.01 ERP protocol version mismatch
9.xxxx.02 ERP force switch
9.xxxx.03 ERP manual switch
9.xxxx.04 ERP signal failed
TWAMPGenerator module
In this section, xxxx = TWAMP instance index.
11.xxxx.01 Max two-way delay
11.xxxx.02 Average two-way delay
11.xxxx.03 Max two-way delay variation
11.xxxx.04 Average two-way delay variation
11.xxxx.05 Max near-end one-way delay
11.xxxx.06 Average near-end one-way delay
11.xxxx.07 Max near-end one-way delay variation
11.xxxx.08 Average near-end one-way delay variation
11.xxxx.09 Max far-end one-way delay
11.xxxx.10 Average far-end one-way delay
11.xxxx.11 Max far-end one-way delay variation
11.xxxx.12 Average far-end one-way delay variation
11.xxxx.13 Continuity loss alert
11.xxxx.14 Excessive packet loss alert

To view the detailed status of an alarm

1. Access the page Show Alarm.
2. Click the alarm Number to view its detailed status.

For more information on specific parameters, refer to the table "Alarm Status (Show
Alarm)" on page 375.
13.1.4 Viewing Chassis Alarms

To view the status of chassis-related alarms and information, including
power supplies and temperature sensors
1. Access the page System Alarm Chassis.
The chassis alarms' status is displayed.
Power Supplies and Temperature Sensors (System Alarm Chassis)
Power Supplies and Temperature Sensors
Power Supply Status The status of the various power sources for AC or DC, Feed A
and Feed B.
For an AC Powered unit:
A green light indicates that the power source is connected
and is operating normally.
A red light indicates that the power source is not

connected or is not operating normally.
For a DC Powered unit:
The Feed B indicator is always green when power to the
unit is connected. The Feed B indicator DOES NOT indicate
that a feed is connected to the Feed B input.
The DC Feed A and DC Feed B lights indicate which DC

feeds are in use.
A green light indicates that the power source is

connected and is operating normally.
A red light indicates that the power source is not

connected or is not operating normally.

Temperature Sensors
Temperature Sensor For each sensor (Sensor 1 and Sensor 2), the current
Status temperature inside the unit, expressed in Celsius
Temperature Sensor First Threshold: For each sensor (Sensor 1 and Sensor 2), the
Thresholds temperature that will activate the first overheating alarm,
expressed in Celsius
Second Threshold: For each sensor (Sensor 1 and Sensor 2), the
temperature that will activate the second overheating alarm,
expressed in Celsius
Fan Status
Fan Speed Status Fan ID: The number (1 or 2) that uniquely identifies each fan
present on the unit
Status: For each fan, the fan status is indicated as either Good
or Failed.
Note:This status is taken once every 24 hours; it is not a real-
time value.
Speed: For each fan (identified as 1 or 2), this is the number of
rotations per minute made by the fan.
Slow Threshold: For each fan (identified as 1 or 2), this is the fan
speed at which the slow fan alarm is triggered. Expressed in
RPM.
Fail Threshold: For each fan (identified as 1 or 2), this is the fan
speed at which the failed fan alarm is triggered. Expressed in
RPM.

13.2 Viewing Dry-Contact Alarms

To view the status of dry-contact-related alarms
1. Access the page System Alarm Dry-Contact.
The dry-contact alarm status is displayed for each of the unit's inputs.
Dry-Contact Alarms (System Alarm Dry-Contact)
Operational State The current state of the dry-contact input, i.e. Enabled or
Disabled
When enabled, the alarm point for this input is created and the
input is monitored.
Normal Input State The input's normal state, i.e. Closed or Opened
An alarm is raised when the input state of the dry-contact is
different from the normal state for more than three consecutive
samples.
Input Pin State The current state of the dry-contact input

13.3 Managing Syslog Messages

The unit logs information related to system operations as Syslog Messages. You can view
the syslog messages directly in the Web management interface or send the log to a
remote location such as a workstation.
13.3.1 Defining Syslog Parameters

To configure Syslog parameters
1. Access the page System Agent Syslog.
A list of all syslog entries is displayed, with the most recent entry at the top.
Tip:You can update the log window with the most recent messages by
clicking Refresh.
Syslog Configuration (System Agent Syslog)
Device Facility The device facility to log all messages using this user-defined
facility instead of the default ones
Level Threshold Logs all messages with a level greater than or equal to the
selected one. For example, setting the priority threshold to
DEBUG (lowest priority) causes all messages to be logged.
Remote Syslog Select this box to enable sending messages to a remote syslog
Enable server
Host The IP address or domain name of the remote syslog server

13.3.2 Sending Syslog Messages to a Remote Location

You can configure the unit to send Syslog messages to a Syslog server in a remote
location.
To send Syslog messages to a remote server

1. Access the page System Agent Syslog.

For more information on specific parameters, refer to the table "Syslog Configuration
(System Agent Syslog)" above.

13.4 Managing the SNMP Agent

You can configure an SNMP agent so that it provides an interface to an SNMP-based
management system (for get and set commands). The SNMP agent also allows the unit to
send SNMP traps to a receiver. The receiver is usually used to monitor the conditions of
many units.
13.4.1 Enabling the SNMP Agent

To enable the SNMP agent
1. Access the page System Agent SNMP.

SNMP Agent (System Agent SNMP)
Enable Agent Enables the units SNMP agent
Use Host Name as Uses host's name as system-name
System Name
SNMP System Name The name to identify the unit. By convention, this is the node's
fully-qualified domain name.
Contact Information Contact information for the unit. Generally an email address.
System Location Physical location of the unit
Agent UDP Port UDP port that the SNMP agent uses for all IPv4 interfaces
Note:Changing this value restarts the SNMP agent.
Read-Only The community string to control read-only access to the unit
Community
Read-Write The community string to control read/write access to the unit
Community
Enable Enables the unit to generate a trap when authentication to the
Authentication Trap agent fails
Generation
Enable Link Trap Enables trap generation when link status changes
Generation Map to the generic traps 2 (1.3.6.1.6.3.1.1.5.3 linkDown) and 3
(1.3.6.1.6.3.1.1.5.4 linkUp).

13.4.2 Setting Up the SNMP Trap Receivers

You can configure the unit to send SNMP traps to different notification receivers. The
notification receiver is usually used to monitor conditions of many units.
The unit can be configured to send SNMP v1 traps to one or two receivers, and to send
SNMP SMTP v2c traps to up to ten receivers.
Using the Auto trap receiver, you can also configure the unit to send SNMP traps (v1 or
v2c) to other compatible notification receivers. With the Auto trap receiver, the IP
address of the compatible notification receiver is automatically updated when the
receiver connects to the unit and sends the appropriate CLI commands. Refer to the CLI
Command Manual for information on the CLI command.
To configure the SNMP trap receiver information

1. Access the page System Agent Traps.
A listing of all current SNMP Trap receiver information is displayed.
2. Click the ID of the trap receiver you want to edit.

Trap Receivers (System Agent Traps)
Type The type of SNMP Trap Receiver may be either SNMPv1 or
SNMPv2c.
ID ID number of the trap receiver
Note:The Auto trap receiver is configurable via the CLI only.
State Enable this box to have the unit send SNMPv1 or SNMPv2c
traps to a specified notification receiver.
Enable Trap Enables the unit to send SNMPv1 or SNMPv2c traps to a
specified notification receiver
Notification Receiver The IP address or host name of the device that receives SNMP
Host Name traps and/or notifications
The unit sends a Cold Start trap when starting up.
Community String The community string required to send traps to the notification
Community receiver
Host UDP Port The UDP port used by the unit to send traps to the notification
UDP Port receiver
The well-known SNMP trap port 162 is used by default.

13.5 Managing History Files

You can manage the creation and transfer of history files, which are logs that contain
statistics related to the services (e.g., PAA, Regulator, Policy, CFM DMM, CFM PL, CFM
SLM, Service Availability, Service Availability Metrics, TWAMP Generator, Shaper, Port) for
which the history feature has been enabled.
You can also configure the unit to transfer its history files to a server.
Note:The exported history CSV files may not all contain the identical
range of period numbers, depending on when the given history metrics
were collected. Enabling multiple categories of history metrics with many
instances requires more time for processing than the length of the
reporting period. Since the history files are processed sequentially, some
exported files may consequently present different period numbers
compared to others.
For example, the CFM DMM file may show periods 16-30, whereas the
CFM SLM file may show 17-31, since it was processed afterwards. The
reason for this variation is that new periods are included in the CSV file as
soon as they become available.
This is the expected behavior. There is no period number synchronization
between history categories. Note that all periods are exported in the CSV
files and no data is lost.
13.5.1 Creating History Files

To enable the creation of history files
1. Access the page System Agent History.
2. In the Local Configuration frame, select the Enable History box for each feature
whose history you want to retain.
Note : Disabling the history disables the filling; enabling the filing enables
the history.
3. In the Local Configuration frame, select the Enable Filing box for each feature for
which you want to create history files, then enter the Period after which you want
the data files to be collected for storage.
4. Click Apply.

History Files, Local Configuration (System Agent History)

Local Configuration
Enable History Select this box to allow the creation of history files, which are
stored in RAM. You can access these files via the SNMP get
command.
Enable Filing Select this box to allow the history files to be stored locally in non-
volatile memory (NVRAM). Storing these files protects against
losing history statistics in the event of a power failure or system
restart. If this box is not selected, the local history files for this
feature are removed.
Use the Scheduling and File Transfer Configuration frame on this
page to have the history files pushed to a server.
History files can be stored locally for the following features:
PAA
Regulator
Policy
CFM DMM
CFM PL
CFM SLM
Service Availability
Service Availability Metrics
TWAMP Generator
Shaper
Port
Period (mins) Indicate the frequency at which the history statistics will be
collected, expressed in minutes. Acceptable values range from 1
and 60.

13.5.2 Transferring History Files

To enable the transfer of history files
1. Access the page System Agent History.
2. Ensure that filing is enabled for the appropriate history files, then click Apply in the
Local Configuration frame. See "Creating History Files" on page 390.
3. Customize when the history files will be scheduled by completing the fields in the
Scheduling section of the Scheduling and File Transfer Configuration frame.
4. Provide the URL where the file transfer server is located and the SCPpassword in the
File Transfer section of the Scheduling and File Transfer Configuration frame.
5. Choose a Period Mode and any optional fields in the File Options section, then click
Apply in the Scheduling and File Transfer Configuration frame.
History Files, Scheduling and Files Transfers (System Agent History)
Scheduling and File Transfer Configuration
Enable Scheduler Select this box to have the unit transfer its history buckets' report
files to a server, whose details are configured below.
Note:Report files will only be generated for the services whose
Enable Filing box in the Local Configuration frame is enabled.
Scheduled Hours Indicate when to transfer the history buckets by making a
selection from the list. Press the CTRL key to select more than one
item.
Note:Finer granularity is possible using the Hourly Minutes or
Periodic Minutes field, in combination with the Schedule Offset
field.
Scheduling Mode Make a selection from the drop-down list to indicate the type of
interval to define for history bucket file transfers:
Hourly:Allows you to select file transfers on the quarter-
hours
Periodic: Allows you to choose from a wider range of interval

values for file transfers
Both interval types are described below.
Hourly Minutes Use this feature to set the scheduling to trigger every 15minutes,

either right on the hour or at the 00:15, 00:30 and 00:45 marks.
Any value combination is valid, provided at least one box is
selected and Hourly is selected in the drop-down list above the
boxes.
Periodic Minutes Make a selection from the drop-down list to set the scheduling
trigger interval value.
Example:
If a unit has 3:00 and 15:00 selected in the Scheduled Hours
list, plus 20 selected in the Periodic Minutes drop-down list,
reports are generated at 3:00, 3:20, 3:40, 15:00, 15:20 and
15:40.
Any value is valid, provided that Periodic is selected in the drop-
down list above the boxes.
Schedule Offset Use this field to offset the scheduling by the number of minutes
you specify.
Hourly:Acceptable values range from 0 to 14
Periodic: Acceptable values range from 0 to (Periodic

Minutes - 1)
This field enables you to generate reports as often as four times
per hour, at any minute thereof. When a large number of units
are set to generate report files, the offset feature can be used to
spread the load on the network and servers.
Examples:
If a unit has 3:00 and 15:00 selected in the Scheduled Hours
list, plus 00:00 and 00:30 selected in the Hourly Minutes with
a Schedule Offset of 0minutes, reports are generated at 3:00,
3:30, 15:00 and 15:30.
If a unit has all hours selected in the Scheduled Hours, plus

00:15 and 00:45 in the Hourly Minutes with a Schedule Offset
of 4minutes, reports are generated at the 19th and 49th
minute of every hour.
If a unit has 3:00 selected in the Scheduled Hours list, plus 10

selected in the Periodic Minutes with a Schedule Offset of
2minutes, reports are generated at 3:02, 3:12, 3:22, 3:32,
3:42 and 3:52.

Random Offset Enter a value in this field to generate a random offset, expressed
in seconds, ranging between 0 and the specified value. This
random offset is added to the Schedule Offset.
Adding a random offset allows multiple units set to generate
reports at the same time for the same destination to be randomly
offset from one another, thus relieving the load created by
several concurrent connections.
Note: The combined value of the schedule offset and random
offset cannot exceed 15minutes (900seconds) in hourly mode or
the value of Periodic Minutes when in periodic mode. If the sum
of the schedule offset and random offset exceeds the specified
limit, the random offset value is automatically adjusted to the
highest possible value.
File Transfer
Server URL Enter the full URL of the server to which the history bucket files
will be sent once retrieved.
Examples:
http://domain.com
ftp://username:password@domain.com
sftp://username@192.168.10.10
tftp://192.168.1.5
scp://username@192.168.10.10:/target_directory
SCP Password Enter the password required for SCP and SFTP transfers.
File Options
Period Mode Indicate which periods to include in the reports by selecting one
of the available options:
All Available Periods: All the periods that are available on
the units are used to generate the reports, up to a fixed
maximum number of periods.
New Periods Since Last File Transfer: All the periods that
have been generated since the previous report. If Include
Periods From Previous Incomplete Transfers is selected, the
periods from a previous report that could not be properly
generated or sent to the server are also included.
Fixed Number of Periods: All the periods available, up to the

maximum number of periods specified in Number of Periods

Note:Enabling "All Available Periods" mode when more than
1000 policies or 1000 bandwidth regulators have been activated
can lead to prolonged, significant CPU usage. The same
behavior may be observed when the remote server is
unreachable for an extended period of time.
Options You can exercise greater control over how the reports are
generated:
Include Periods From Previous Incomplete Transfers: When
selected, any periods contained in a report that could not be
properly generated or sent to the server are also included in
the current report. If not selected, only the periods since the
previous report are included in the current report.

GT v7 0 X Performance Element User Manual

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

GT v7 0 X Performance Element User Manual

Diunggah oleh

Hak Cipta:

Format Tersedia

GT Performance Element

March 31, 2015

Accedians products are protected by patents as indicated on Accedians website at

Accedian Networks Inc.

1 About This Manual 1

2 Introduction to the GT Performance Element 5

3 Managing the Unit 21

Document revision 1|March 2015 v

3.8.2 Defining Permissions for a Group of Users 54

4 Configuring Plug & Go 69

5 Configuring the Unit 83

Document revision 1|March 2015 vi

5.12 Rebooting the Unit 113

6 Managing Ports 117

7 Setting Up Protection 147

8 Managing Traffic 163

Document revision 1|March 2015 vii

8.5.6 Creating a Shaping Envelope 212

9 Monitoring Network Performance with Ethernet OAM 231

10 Monitoring Network Performance with Service OAM 245

Document revision 1|March 2015 viii

10.4 Using the Two-Way Active Measurement Protocol (TWAMP) 306

11 Testing Network Performance 321

12 Managing Loopbacks 365

13 Managing Alarms and System Messages 371

Document revision 1|March 2015 ix

1 About This Manual

Document revision 1|March 2015 1

"Configuring Plug & Go"

"Configuring the Unit"

"Monitoring Network Performance with Ethernet OAM"

"Monitoring Network Performance with Service OAM"

"Testing Network Performance"

"Managing Alarms and System Messages"

Document revision 1|March 2015 2

CAUTION: Describes a situation where failure to take or avoid a specified

Document revision 1|March 2015 3

IEEE 802.3ah Ethernet in the First Mile (EFM)

IEEE 802.3ax Link Aggregation

ITU-T Y.1731 OAM functions and mechanisms for Ethernet-based networks

ITU-T Y.1564 Ethernet Service Activation Test Methodology

RFC-2544 Benchmarking Methodology for Network Interconnect Devices

RFC-5357 Two-Way Active Measurement Protocol

Technical Specification MEF 17 Service OAM Requirements & Framework Phase 1

Technical Specification MEF 6.1 Ethernet Services Definitions Phase 2

Technical Specification MEF 9 Abstract Test Suite for Ethernet Services

Technical Specification MEF 10.2 Ethernet Services Attributes Phase 2

Technical Specification MEF 14 Abstract Test Suite for Traffic

Technical Specification MEF 22 Mobile Backhaul Implementation Agreement,

Technical Specification MEF 26 External Network Network Interface

Document revision 1|March 2015 4

2 Introduction to the GT Performance Element

Document revision 1|March 2015 5

Document revision 1|March 2015 6

2.1.1 Mobile Backhaul

Document revision 1|March 2015 7

2.1.2 Assured Business Services

Document revision 1|March 2015 8

2.1.3 Carrier Ethernet Exchange Services

Document revision 1|March 2015 9

2.1.4 Carrier Ethernet Global Interconnect

Document revision 1|March 2015 10

2.1.5 Enterprise WAN QoS