GX v7.8.3 Performance Element User Manual

User Manual
GX Performance Element
Version 7.8.3
Revision 1 — August 16, 2019

GX Performance Element Version 7.8.3 User Manual
Publication Information
Revision 1 — Publication date: August 16, 2019
Trademark Information
Copyright © 2019 Accedian Inc. All rights reserved.
Accedian, Accedian Networks, the Accedian Networks logo, R-FLO, antModule, Vision EMS, Vision Suite,
VisionMETRIX, Data Hub IQ, V-NID, MetroNODE, EtherNID, MetroNID, NanoNID, PERFORMANT,
SkyLIGHT, SkyLIGHT Director, SkyLIGHT VCX, SkyLIGHT Director License Server, EtherPRO, Vision Collect,
Vision Flow, Vision SP, airMODULE, Plug & Go, Network State+, Traffic-Meter, FlowBROKER, FlowMETER,
Experience ●Performance, and Performance Assurance Agent (PAA) are trademarks or registered
trademarks of Accedian Networks Inc.
SevOne is a trademark of SevOne, Inc. SevOne Accedian Edition is a joint trademark of Accedian Networks
Inc. and SevOne, Inc.
All other company and product names may be trademarks of their respective companies. Accedian 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 for current certifications.
Accedian products are protected by patents as indicated on the Accedian 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.
Contact
If you have comments regarding this manual or the products it describes, address them to:
Accedian Networks Inc.
2351 Alfred-Nobel Boulevard, Suite N-410
Saint-Laurent, Québec
Canada H4S 2A9
Toll free: 1-866-685-8181
[email protected]
accedian.com
Revision 1 — August 2019 2

Table of Contents
1. About This Manual 9

1.1 Organization 10
1.2 Conventions 11
1.3 References 11
2. Introduction to the GX Performance Element 13

3. Managing the Unit 14
3.1 About the Management Web Interface 15
3.2 Starting the Management Web Interface 17
3.2.1 Physically Connecting to the Unit 17
3.2.2 Logging In 17
3.2.3 Password Considerations 18
3.2.4 Character limitations in URLs and User Input Fields 19
3.2.5 Working in the Home Page 19
3.2.6 Modifying the Host Name 20
3.2.7 Managing SSL Certificates 21
3.3 Configuring Logical Interfaces 25
3.3.1 Adding or Editing a Logical Interface 28
3.3.2 Setting Up a Beacon Instance at Layer 3 34
3.3.3 Adding or Editing an IPv4 Route 35
3.3.4 Adding or Editing an IPv6 Route 36
3.4 Finding a Host (Ping and Traceroute) 37
3.5 Using the Serial Console 38
3.6 Managing the Link Layer Discovery Protocol (LLDP) 40
3.7 Managing Sessions 44
3.7.1 Terminating a User Session 45
3.7.2 Configuring Session Options 45
3.8 Managing Users and Privileges 49
3.8.1 Setting Up the Administrator Account 49
3.8.2 Defining Permissions for a Group of Users 49
3.8.3 Adding and Editing User Accounts 52
3.8.4 Administering User Account Privileges 54
3.8.5 Changing Passwords 54
3.9 Using a RADIUS Server for Authentication 55
3.9.1 RADIUS Server Configuration Examples 56
3.10 Using a TACACS+ Server for Authentication 57
3.10.1 TACACS+ Server Configuration Examples 58

3.11 Managing Access Control Lists 60

3.11.1 Setting Up an ACL 60
3.11.2 Deleting an ACL 62
3.11.3 Viewing ACL Statistics 62
3.12 Managing OS Services 63
4. Configuring Plug & Go 64

4.1 Understanding Plug & Go 65
4.1.1 Beacon and Advertisement Frames 65
4.1.2 ACP Level 66
4.2 Configuring a Unit for Beacon 67
4.2.3 Deleting a Beacon Instance at Layer 3 71
4.2.4 Modifying a Beacon Instance at Layer 3 71
4.3 Configuring the Forwarding Settings of Intermediate Units 72
4.4 Managing Network Inventory 73
4.4.1 Viewing Network Inventory 73
4.4.2 Logging In to a Remote Unit 75
4.4.3 Sending a Beacon Frame 75
5. Configuring the Unit 76

5.1 Configuring General System Settings 77
5.1.1 Setting the S-VLAN Ethertype 77
5.1.2 Regulating Management Traffic 77
5.2 Configuring IPv4 Settings 79
5.2.1 Setting the IGMP Version 79
5.2.2 Enabling IPv4 Forwarding 80
5.3 Provisioning DHCP Relay 81
5.4 CPU OAM Options 82
5.5 Setting Dry-Contact Inputs 84
5.6 Setting the System Date and Time 86
5.6.1 Setting Date and Time Manually 86
5.6.2 Setting Date and Time Using NTP 86
5.7 Setting Up SyncE 93
5.8 Viewing SyncE/ESMC Port Statistics 96
5.9 Setting Up DNS 100
5.10 Configuring Traffic 101
5.10.1 Setting the Working Rate 101
5.10.2 Selecting VLAN level settings 101
5.11 Upgrading the Firmware 103
5.12 Importing and Exporting the Unit’s Configuration 107
5.13 Tech Support 109

5.14 Viewing CPU Usage 110

5.15 Configuring System Monitor 111
5.16 Rebooting the Unit 114
5.17 Restarting the Unit 115
5.18 Restoring Factory Default Settings 116
6. Managing Ports 117

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 SFP Configuration 146
6.8 Testing a Cable 147
7. Managing Traffic 149

7.1 Understanding the Creation of Ethernet Services 150
7.2 Defining Filters 152
7.2.1 Configuring a Layer-2 Filter 152
7.2.2 Configuring an IPv4 Filter 155
7.2.3 Configuring an IPv6 Filter 160
7.3 Setting Up Ethernet Services 165
7.3.1 Setting Up VID Sets 166
7.3.2 Setting Up Bandwidth Regulators 170
7.3.3 Setting Up Bandwidth Regulator Sets 172
7.3.4 Setting Up CoS Profiles 173
7.3.5 Setting Up Port CoS-to-PCP Mapping 175
7.3.6 Setting Up Traffic Policies 176
7.3.7 Viewing Traffic Regulator Statistics 187
7.3.8 Setting Up Bandwidth Policer Envelopes 189
7.3.9 Understanding BLUE 191
7.3.10 Configuring Queues 192
7.3.11 Viewing Traffic Shaping Queue Statistics 194
7.3.12 Viewing Queuing Profile Details 197
7.3.13 Configuring a Port Shaper 197
7.4 Using Layer-2 Protocol Tunneling 199
7.4.1 Viewing Statistics for Layer-2 Tunnel Rules 200
7.4.2 Setting Up a Layer-2 Tunnel 201
7.5 Monitoring Traffic 207
8. Setting Up Protection 209

8.1 Setting Up LAG Port Protection 210

8.1.1 Switching to the Standby Port 211

8.1.2 Viewing LACP Status 211
8.1.3 Viewing LACP Statistics 213
8.2 Setting Up ERP Protection 215
8.2.1 Viewing ERP Status 217
8.2.2 Forcing a Switch to the Standby Port 219
8.2.3 Clearing a Forced Switch 219
8.2.4 Switching Manually to the Standby Port 219
8.2.5 Viewing ERP Statistics 219
8.2.6 Viewing the ERP VLAN Learning Table 221
9. Managing Virtual Connection Endpoints (VCEs) 222

9.1 About Virtual Connection Endpoints (VCEs) 223
9.1.1 Parts of a VCE 224
9.2 Setting Up Virtual Connection Endpoints (VCEs) 225
9.3 Adding Virtual Connection Endpoints (VCEs) 227
9.3.1 VCE Examples 230
10. Managing Virtual Connection Access (VCAs) 232

10.1 About Virtual Connection Access (VCAs) 233
10.1.1 CFM Using Model 233
10.2 Setting Up Virtual Connection Access (VCAs) 235
11. Monitoring Network Performance with Ethernet OAM 237

11.1 Setting Up an OAM Instance 238
11.2 Viewing OAM Events 240
11.3 Viewing OAM Status 241
11.4 Viewing OAM Statistics 244
12. Monitoring Network Performance with Service OAM 250

12.1 Using the Performance Assurance Agent 251
12.1.1 Setting Up a Probe 251
12.1.2 Deleting a Probe 259
12.1.3 Viewing Probe Status 259
12.1.4 Viewing Probe Results 260
12.2 Using Service OAM 265
12.2.1 MEP vs. MIP 265
12.2.2 Setting Up CFM 266
12.2.3 Setting Up Link Trace Messages 282
12.2.4 Viewing Link Trace Messages Information 284
12.2.5 Setting Up Loopback Messages 284
12.2.6 Viewing Loopback Message Information 286
12.2.7 Setting Up Delay Measurements 286
12.2.8 Deleting a Delay Measurement Instance 289

12.2.9 Viewing Delay Measurement Results 290

12.2.10 Setting Up Packet Loss Measurement 293
12.2.11 Deleting a Packet Loss Instance 294
12.2.12 Viewing Packet Loss Results 294
12.2.13 Setting Up Synthetic Loss Measurements 295
12.2.14 Deleting a Synthetic Loss Measurement Instance 296
12.2.15 Viewing Synthetic Loss Measurement Results 297
12.2.16 Managing CFM Interfaces 298
12.2.17 Assigning a CFM Interface 299
12.2.18 Unassigning a CFM Interface 299
12.2.19 Setting Up VSP 299
12.2.20 Viewing VSP Results 300
12.2.21 Setting Up CFM Default Values 300
12.3 Using Service Availability 303
12.3.1 Setting Up Service Availability 303
12.3.2 Deleting an SA Instance 305
12.3.3 Setting Up an SA Metric 305
12.3.4 Deleting an SA Metric 307
12.3.5 Putting an SA Instance into Service 307
12.3.6 Viewing SA Counters 307
12.4 Using the Two-Way Active Measurement Protocol (TWAMP) 311
12.4.1 Setting Up TWAMP Generator Measurements 311
12.4.2 Deleting a TWAMP Generator Instance 315
12.4.3 Viewing TWAMP Generator Session Results 315
12.4.4 Viewing the TWAMP Generator Session Status 319
12.4.5 Setting Up a TWAMP Reflector 320
12.4.6 Viewing TWAMP Reflector Statistics 321
13. Testing Network Performance 322

13.1 Setting Up SAT Reporting 323
13.2 Testing Locally-Created Services 325
13.3 Using RFC-2544 for Traffic Generation and Analysis 327
13.3.1 Setting Up the Traffic Generator 328
13.3.2 Starting the Traffic Generator and Viewing Test Results 334
13.3.3 Setting Up the Traffic Analyzer 335
13.3.4 Viewing Traffic Analyzer Test Results 339
13.3.5 Setting Up a Test Suite 340
13.3.6 Running a Test Suite and Viewing Test Reports 348
13.4 Using Y.1564 for Service Activation Testing 350
13.4.1 Setting Up a Y.1564 Test 350
13.4.2 Setting Up a Y.1564 Service 353
13.4.3 Running a Y.1564 Test and Viewing Test Results 359
13.5 Using the SAT Protocol 362
13.5.1 Setting Up the SAT Protocol 362

13.5.2 Viewing SAT Protocol Statistics 363

13.5.3 Viewing SAT Protocol Sessions 364
14. Loop Detection 365

14.1 About Loop Detection 366
14.2 Configuring a Loop Detection Instance 367
14.3 Viewing Loop Detection Instance Details 370
14.4 Viewing Loop Detection Counter Instances 372
14.5 Viewing Loop Detection Global Counters 374
14.6 Managing the Loop Detection Diagnostic Tool 375
15. Managing Loopbacks 377

15.1 Understanding Loopback Testing 378
15.2 Setting Up and Enabling Loopbacks 379
16. Managing Alarms and System Messages 382

16.1 Managing Alarms 383
16.1.1 Setting General Alarms 383
16.1.2 Customizing Alarms 383
16.1.3 Viewing Alarms 385
16.1.4 Viewing Chassis Alarms 394
16.1.5 Performing a Fan Test 396
16.2 Viewing Dry-Contact Alarms 398
16.3 Managing Syslog Messages 399
16.3.1 Defining Syslog Parameters 399
16.3.2 Sending Syslog Messages to a Remote Location 401
16.4 Managing the SNMP Agent 402
16.4.1 Enabling the SNMP Agent 402
16.4.2 Setting Up the SNMP Trap Receivers 403
16.5 Managing the Netconf Agent 405
16.6 Managing History Files 406
16.6.1 Creating History Files 406
16.6.2 Transferring History Files 408

1. About This Manual
This document provides information about the technologies and standards used in
Accedian’s 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 Accedian’s network devices such as the GX 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.

1.1 Organization
This document contains an introduction and several chapters of detailed procedures and
examples.
The Introduction chapter provides information about technologies and standards used in
Accedian’s equipment.
The following chapters contain information and procedures for configuring the equipment:
"Managing the Unit"

"Configuring Plug & Go"
"Configuring the Unit"
"Managing Ports"
"Managing Traffic"
"Setting Up Protection"
"Managing Virtual Connection Endpoints (VCEs)"
"Managing Virtual Connection Access (VCAs)"
"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 11.

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]enter a specific IP address when you reach
the the Interface page: AMD System ▶ Interface ▶ [AMD IP Address]
Alarm numbers are composed of three fields, the module number (AA), the instance number
(BBBB) and the error number (CC). The displayed format is AA.BBBB.CC.
Other conventions:
CAUTION: Describes a situation where failure to take or avoid a specified action

could result in damage to equipment.
Note: Information that emphasizes or supplements points within the main text.
Notes often provide details that only apply in certain situations.
1.3 References
The use of equipment such as the GX 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.1ax – 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) – Phase 1

2. Introduction to the GX Performance Element
The GX Performance Element is a 1 GbE platform based on Accedian‘s all-hardware Fast-

PAAs processing engine—with 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 GX Performance Element is based on the same innovative hardware as Accedian's
award-winning TE and LT 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 GX 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 Accedian‘s GbE NIDs, the GX 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 GX 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 Accedian’s website at www.accedian.com.

3. Managing the Unit
This chapter contains the following sections:
3.1 About the Management Web Interface 15
3.2 Starting the Management Web Interface 17
3.3 Configuring Logical Interfaces 25
3.4 Finding a Host (Ping and Traceroute) 37
3.5 Using the Serial Console 38
3.6 Managing the Link Layer Discovery Protocol (LLDP) 40
3.7 Managing Sessions 44
3.8 Managing Users and Privileges 49
3.9 Using a RADIUS Server for Authentication 55
3.10 Using a TACACS+ Server for Authentication 57
3.11 Managing Access Control Lists 60
3.12 Managing OS Services 63

3.1 About the Management Web Interface

The Management Web 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 v7.0 or later.
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 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 382. 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.
Logout button: Use this button to log out 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 browser’s 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 interface on the front of the unit. This allows
you to log in and configure the unit for the first time. For example, you can set the unit’s time
and date and create other logical interfaces so you can connect through a LAN or WAN (refer
to Configuring Logical Interfaces on page 25).
Using the management Web interface, you can complete configuration tasks such as setting
the unit’s time and date, and creating other logical interfaces that enable you to connect
through a WAN (ports 1-2) or LAN (ports 3-8).
Begin by physically connecting the LAN port on the management station to the management
interface (Port-8 by default) on the front of the unit and thus establishing a connection to
the GX Performance Element. Once the unit is powered up, you are ready to log in and
configure the unit for the first time.
The default management interface for the GX Performance Element is Port-8.
3.2.2 Logging In
There are various ways to log in, depending on the unit's configuration. You would typically
connect to the unit for the first time using the management interface, 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.254 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 the unit. If you are using static IP
addresses, you should then modify the unit’s 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 Logical Interfaces on page 25.
3. The login page for the unit opens. Log in 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 that you change the default admin password after
your first log in; 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 54.
▶ When logging in for the first time (if another logical interface is configured)
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 38 to enable the console port, as well as to the CLI Help or the
CLI Command Guide for information on the CLI command.
3. The login page opens. Log in using the admin username and account password.
3.2.3 Password Considerations

The Management Web Interface supports a variety of authentication methods, as well as the
order in which these methods are applied. You can indicate your preferred authentication
order in the System ▶ Session ▶ Configuration page.
The maximum permitted password length varies, depending on the authentication method
you specify:
Local Authentication: 48 characters

RADIUS Authentication: 48 characters
TACACS+ Authentication: 64 characters
If you choose to include a fallback method in your authentication order, you must ensure that
the user password you choose is valid for all authentication methods that you want to use.
For example, if you want to use TACACS+ authentication when logging in—with local
authentication as the fallback method—your TACACS+ password cannot exceed 31
characters. Any passwords that are longer than 31 characters will be truncated and unusable
by the local authentication system, even if they are supported by the TACACS+ server.
Notes:
If you plan on using a remote server for authentication, you should confirm that the
remote system is functional before removing the local authentication.
If you remove local authentication and the remote system is not working, you will lose
access to the unit. To ensure that authentication is working on the remote server, log in
then out from the unit, then access the System ▶ Agent ▶ Syslog page. You should see
a syslog message indicating a successful login attempt.

3.2.4 Character limitations in URLs and User Input Fields

Limitations are in place to prevent utilization of specific special characters in URLs and user
inputs fields throughout the Management Web interface. These limitations are:
The following special characters are not allowed in any user input fields: "&","<", ">",
"\n", "\r", "\t ", "\'' and " " ".
The following special characters are not allowed in the URL input: "<", ">", "\n", "\r" and
"\t".
3.2.5 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
Unit Identifier The host name that identifies the unit on the network
Access the page System ▶ Configuration ▶ DNS to change the
host name.
Firmware Version The version number of the firmware running on 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
Hardware Options The unit's hardware options. This field is only displayed if the unit

has a hardware option such as a GPS or SyncE installed.
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. Access the page System ▶ Configuration ▶ Time to
set the system clock.
Note: This value is reset when a power cycle is performed on the
unit.
3.2.6 Modifying the Host Name

The default host name (or unit identifier) is the serial number assigned to 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 log in to the
unit, as shown in the figure in the section About the Management Web Interface on page 15.
Note: The host name is also displayed in the CLI prompt and is added to system
log entries to help you identify the SkyLIGHT VCX Controllerunit more clearly.
▶ To modify the Host Name
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 the use of DNS settings obtained via DHCP. You can then
select the interface to use for obtaining DHCP information using the
From Interface control.
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 64
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

Possible values 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 Custom
DHCP host name Hostname.
DHCP Client ID This value corresponds to DHCP option 61. It allows you to enter a
text string for use as the unit’s unique identifier when
communicating with the DHCP host. When the text box is empty,
the MAC address is used as the unit’s 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 Server 1 The address of DNS server 1 is available only when Use DHCP
Results is not selected.
DNS Server 2 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.7 Managing SSL Certificates

The SSL protocol is used to secure communication over the Internet between the
management station and the unit. In order to provide secure communication, a valid SSL
certificate from a certificate authority must be loaded into the unit. To learn more about
certificates, refer to the certificate authority and ITU-T Recommendation X.509.
Note: You can install the SSL certificate in each browser that you want to use
when connecting 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
the Application Management section, which manages 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, you must restart the
Web GUI interface session by clicking Restart because this certificate is being
actively used by the interface. 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
(i.e., the Web server) using the certificate.
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 Possible values are:
Web Management: This is the application you are currently

using.
File Transfers: All applications that send or receive files
through a secure channel (HTTPS or FTPS) such as 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
(i.e., the Web server) using the certificate.
For a client, this may be the name of the application.
Validate CA For client applications, perform peer certificate validation. This

includes the 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
Notes: Importing a private key separately from its certificate is not

supported.
The maximum number of single certificates supported is 10 and the
maximum number of client/server certificates supported is 5.
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 Logical Interfaces

You can define one or more logical interfaces for managing the unit; the types of interfaces
available include 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.
The following types of logical interface are available:
Standard: This interface type is associated with a single port. You could use a standard
interface to manage the unit from a single untagged 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. For a bridge interface, you can enable two options: spanning tree protocol
and IP override for subinterfaces.
VLAN: Like standard interfaces, this interface type is also associated with a single port.
One use of a VLAN interface would be if you wanted 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 process (and not forward) the management traffic and allow the customer traffic
to flow through the unit. For more information on filters and policies, refer to the
chapter Managing Traffic on page 149.
Note: Setting up policies and filters in this manner 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, as well as choose the Ethertype and VLAN.
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.
By default, the following logical interfaces are defined:
Management: This interface (Interface type Standard ) enables access to the

Management Web Interface and the CLI via the management port.
Auto: This interface (Interface type Auto) listens for beacons on all ports.
You can designate which of the unit’s logical interfaces is the primary interface, which is the
main interface used to manage the unit. Only one interface can be the primary at any given
time and Auto is the default primary interface. If the primary interface has been assigned a
list of IP addresses, these addresses will be automatically included in ACP and LLDP
advertisement frames, as well as in Plug & Go advertisements.

You can configure interfaces for dual homing by specifying a second IP address (an 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 (DHCP
cannot be used).
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 73.
Note: An interface can also be used for other purposes, such as for loopbacks or
test set interaction.
▶ To view the list of logical interfaces
1. Access the page System ▶ Configuration ▶ Interface.

A listing of all logical interfaces associated with the unit is displayed. An asterisk
appears beside the name of the primary interface.

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

3.3.1 Adding or Editing a Logical Interface

When the unit is initially installed (or after a factory default reset), a logical interface named
Management is bound to a port. You can add and edit more logical interfaces to provide the
unit with multiple management options.
CAUTION: If you modify a Management interface, you or another user may lose
access to the management Web interface and/or the CLI.
▶ To add or edit a logical 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.
Notes: When changing any parameters from VLAN settings and/or VLAN in
VLAN settings (Ethertype, Priority and VLAN ID) of an interface or when
deleting an interface, the following message will be displayed "Configuration
changes are service affecting. Are you sure you want to proceed?". Click OK to
proceed with your changes or Cancel to go back to the previous screen.
The fields displayed will vary, depending on the Interface type you select.
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
Primary Select this box to identify this interface as the primary interface.
Note: The system will not prompt you for a confirmation when
changing the existing primary interface to a new interface.
Interface Name A name to identify the interface
Interface Type The type of interface to create

Available options are:
Standard: Standard IP interface associated with a single

untagged port.
Bridge: Bridged interface that connects two or more ports.
VLAN: VLAN interface associated with a single tagged port.
VLANinVLAN: VLAN-in-VLAN (.1q in .1q) interface associated
with a single double-tagged port.
Auto: You can set up only one Auto interface for each device.
This option cannot be selected on any other interfaces.
IPv4
Allow DHCP Relay Select this box to enable relaying DHCP requests on this interface to
the server or servers you specify
In order for this parameter to take effect, you must also select the
Enable DHCP Relay box in the System ▶ DHCP Relay page to
globally permit per-interface relaying of DHCP requests.
"Configuring IPv4 Settings" on page 79 for details.
Allow IP Forwarding Select this box to enable IP forwarding for ingress traffic on this
interface
In order for this parameter to take effect, you must also select the
Enable Forwarding box in the System ▶ IPv4 page to globally
permit per-interface IPv4 forwarding. "Configuring IPv4 Settings"
on page 79 for details.
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 obtain routing information from the DHCP server.
Information
Use Static IP Until Uses the manually configured IP address on the interface until an
DHCP Response address is resolved by DHCP
Note: Available only when using Automatic IP (DHCP) mode; not
available with the Auto interface.
Manual Select this option to enable manual configuration of the IP address

Configuration settings
IP Address The 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 The default gateway associated with the IP address alias, if required
Alias
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 Make a selection from the drop-down list to indicate the

implementation of DHCPv6 (only used if IPv6 is enabled)
Acceptable values are:
Stateless: Use IPv6 stateless address auto-configuration for this

interface; configuration details are provided via DHCPv6 as
necessary (see RFC-3315 and RFC-3736)
Stateful: Use a DHCPv6 server to assign an IPv6 address to this
interface from a predefined range
Disabled: Do not use DHCPv6 for IPv6 address management on
this interface
Static Address Enable or disable IPv6 static addresses (used if IPv6 is enabled)
Router Enable or disable IPv6 router advertisement auto-configuration

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 reinitialized by setting the value to :: /0
IPv6 Default IPv6 default gateway addresses (used if IPv6 and IPv6 static
Gateway addresses are enabled)
Note: Can be reinitialized 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- The Spanning Tree Protocol (STP) may be enabled or disabled.
Tree 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 The VLAN ID assigned to the interface
VLAN Priority The VLAN priority. Acceptable values range from 0 to 7.
Ethertype The Ethertype value for the first or second VLAN ID. The Ethertype
may vary, depending on the equipment to which the unit is
connected:
C-VLAN: 0x8100
S-VLAN: 0x88A8 (or 0x9100); refer to the global setting for S-
VLAN Ethertype under System ▶ Configuration ▶ Mode.
T-VLAN: 0x9100 (or 0x88A8); refer to the global setting for the
S-VLAN Ethertype under System ▶ Configuration ▶ Mode.
Note: The S-VLAN and T-VLAN Ethertype values are assigned in

the page System ► Configuration ► Mode. For details, see
"Configuring General System Settings" on page 77.
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 even if
Mismatch 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 The name assigned to the DHCP host. Possible values are:
Current hostname
Serial number
Custom hostname
DHCP Client ID The ID assigned to the DHCP client. 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 IP addresses.
A total of 100 IP addresses can be specified here, including both
address ranges and single IP addresses.
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, the
State 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.
0–7: 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 list The list of destination IP addresses to be used in Layer-3

advertisement frames.
Use Rate from When enabled, the advertisement transmission rate matches the
Beacon 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 ACL for this interface
ACL The ACL assigned to this interface
ACL Types Enable or disable the use of ACL for each management type:
CLI: SSH and Telnet

WEB
SNMP
NETCONF
ICMP
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 Layer 2 or Layer 3. Configure the unit to
send beacon frames at Layer 2 if the remote units are within the same subnet. Configure the
unit to send beacon frames at Layer 3 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 Layer 3, see Setting Up a Beacon Instance at Layer 3 on page
68.
To set up a beacon interface at Layer 2, see Configuring Logical Interfaces on page 25.

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 does not reside in the management station’s 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 station’s 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 parameter 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

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.
Note: Ping can be used to reach a logical interface bound to a remote device's
port.
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 that you want to ping.
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 Guide 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 station’s point of attachment to the
IEEE 802 LAN required by those management entities.
The unit uses LLDP to advertise connectivity and management information about itself to
adjacent stations, as well as to receive and display network management information from
adjacent stations residing on the same IEEE 802 LAN.
▶ To view and manage LLDP information
1. Access the page Show ▶ LLDP.

The total number of ports found in the system is given in the lower-left corner of the
page, as well as the index values of the ports currently displayed on-screen (for
example, [1-25] of 254). Use the page navigation links in the lower-right corner of the
page to move between the pages of results.
2. (Optional) To limit the view to only certain ports, enter a value on which to filter, then
click Search.
Note: Enter an asterisk (*) as a wildcard to replace one or several characters.
3. To view detailed LLDP information related to a specific port, click the Port Name in the
LLDP Neighbors or LLDP Configuration sections.
Details pertaining to the selected port are displayed.
4. Manage how LLDP frames are transmitted on this port using the Enable, Forward and
Rate parameters of the LLDP Configuration section.
For more information on specific parameters, refer to the table at the end of this section.

Show ▶ LLDP
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, 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 Configuration
Enable Enable or disable LLDP (Link Layer Discovery

Protocol) frame transmission on the selected port.
Forward Enable or disable the forwarding of the LLDP

frames on the opposite port.
Rate The LLDP frame transmission rate, expressed in

seconds, on the selected port
Range: 1 to 3600

3.7 Managing Sessions

The unit’s management system provides multiple configurable management sessions to allow
multiple users to control the unit.
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
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 49.
▶ To terminate a session
1. Access the page System ▶ Session ▶ Management.
2. Select the session you want to terminate by checking the Terminate check box.
3. Click the Terminate button.

The session is immediately terminated and the selected user is logged out.
3.7.2 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 of total sessions (CLI and web combined)
The maximum number of concurrent Netconf sessions that can be supported
The maximum number of seconds that a Netconf session can remain idle before it is
automatically logged out
The CLI timeout value
The file transfer timeout value, to ensure firmware updates and configuration
maintenance entities have sufficient time to load successfully
The Management 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 configuration 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 Sessions The maximum number of concurrent Management Web Interface
sessions that can be supported
Max NETCONF The maximum number of concurrent Netconf sessions that can be
Sessions supported
Note: Currently, the maximum number of concurrent Netconf
sessions is one.
Max Total Sessions The total number of CLI and Management Web Interface 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 Web

Interface session can remain idle before it is automatically logged
out
NETCONF Timeout The maximum number of seconds that a Netconf 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. Possible

values 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.
Notes: If you plan on using a remote server for authentication, you

should confirm that the remote system is functional before
removing the local authentication. If you remove local
authentication and the remote system is not working, you will lose
access to the unit.
To ensure that authentication is working on the remote server, log
in then out from the unit, then access the System ▶ Agent ▶
Syslog page. You should see a syslog message indicating a
successful login attempt.

3.8 Managing Users and Privileges

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, traffic, etc., 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 54). 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 116.
3.8.2 Defining Permissions for a Group of Users

You must first define a permission group before you can assign users to groups.
▶ To define privileges and sub-privileges in a permission group
1. Access the page System ► Session ► Permissions.
2. Click Add or click the Group Name that you want to edit.
3. Select the Privileges to assign to the permission group, then click Apply.
Notes:
A "+" sign that precedes the privilege name indicates the availability of sub-
privileges. Clicking on the "+" will show you the available sub-privileges that
can be added or revoked.
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.
CFM: Edit/Add the SOAM CFM feature.
Config: Import/Export configuration files through CLI. Sub-
privileges are available for import, export, rollback, and factory.
Filters: Edit/Add Layer-2 filters, IPv4 filters, IPv6 filters and VLAN:
filter
vid-set
Firmware: Upgrade the firmware. Sub-privileges are available for

upgrade and rollback.
History: Edit the history bucket statistics.
L2PT: Edit/Add L2 protocol tunneling rules.
Log: Edit syslog configuration and view logged entries.
Loop Detection: Edit/Add/Delete/Enable instance loop detection
Management: Edit/Add management access to the unit:
bridge
console
dns

interface
inventory
license
mode admin
motd
mtr
ntp
ptp
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
Sub-privileges is available for internal loopback.

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
TACACS+
reboot
session
Sub-privileges is available for reboot.

Shaping: Add/Edit traffic shapers database.
Traffic: Edit/Enable VLAN encapsulation settings:
forwarding
TWAMP: Edit/Enable TWAMP settings.

Users: Edit/Add and manage user accounts and permissions:
permission-group
user
Virtual Connection: Add/Delete/Enable/Edit/Show vce

configuration
Y.1564: Edit/Add/Enable Y.1564 test methodology.
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
3.8.3 Adding and Editing User Accounts

▶ To add or edit a user account
1. Access the page System ▶ Sessions ▶ Users.

A list of all user accounts that have been created 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.

Note: Passwords for locally-authenticated users are limited to 48
characters.
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.
CAUTION: Modifying or reassigning the user groups for your account may result
in you being unable to perform some tasks.
▶ 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.
Note: You cannot change permission group of the user admin.
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.

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 individually. The unit can be connected to up to three 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
configured server
Realm The string to append to the user's name, following the

username@realm method
Vendor-Specific Enable this box to include vendor-specific information as part of the

attribute in Access- RADIUS access request. Sending this information enables the
Request RADIUS server to better identify the type of equipment requesting
access.
Server-1 / Server-2 / Server-3
Host The RADIUS server host-name or IP address
Port The RADIUS server UDP port to which to connect
Secret The shared secret for this RADIUS server. The secret can be 48
characters long.
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.
Service-Type (id=6): Provides for full admin privileges if attribute is set to
"Administrative-User".
Note: 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 and sub-privileges: Callback-Id = "Config,
Config-not-rollback, 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+ Retries 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.
Note: This field is displayed only if the Show Advanced Settings
box is checked.
TACACS+ Privilege The attribute to extract from the authorization response in order to
Level Attribute determine the privilege level of the user requesting authentication
The default value is priv-lvl.
Note: This field is displayed only if the Show Advanced Settings
box is checked.
Server-1 / Server-2
Host The TACACS+ server's host-name or IP 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

Maximum length is 64 characters.
Show Secret Enable this box to display the shared secret for this TACACS+ server
in plain text
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 case-sensitive 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.
Following are configuration examples for the TACACS+ Server using these attributes.

▶ 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"
# 'shell' service referred to as 'exec'
# in the config
service = exec {
priv-lvl = 1
}
}
▶ To assign a user a customized set of privileges and sub-privileges
user = taccfm {
login = cleartext taccfm
pap = cleartext taccfm
name = "Test Tac User CFM"
service = exec {
priv-lvl = 1
accedian-priv-lvl = 7
accedian-priv-list = Config, Config-not rollback
}
service = accedian {
priv-lvl = 1
accedian-priv-list = Config, Config-not-rollback
}
}
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 40 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 would be to 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 and Netconf) to
which the ACL applies. Refer to the section Configuring Logical Interfaces on page 25.
CAUTION: If you assign a rule to an interface, you or another user may lose
access to the unit.
Notes: Assigning an ACL to a subinterface that belongs to a bridge is not supported. The
ACL must be assigned to the bridge itself.
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.


ACL Definition Summary (System ▶ ACL)

Name The name of the ACL list.
State The 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 ACL list:
ipsrc: IPv4 and 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: 2011DB8::1212)
IPv4 subnet (ex: 192.0.2.0/24)
IPv6 subnet (ex:2001:DB8::/32)
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 (1 is 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 "ACL Definition
Summary (System ▶ ACL)".
3. To clear the statistics, click the Clear button.
4. To update the statistics, click the Refresh button.

3.12 Managing OS Services

Access the System ▶ OS Service page to:
Show available OS services

Show and edit the HTTP server configuration
▶ To change the HTTP Server configuration
1. Access the page System ▶ OS Service.

The current HTTP Server configuration is displayed.
2. Complete/modify the required fields, then click Apply.
CAUTION: Changing configuration will cause the HTTP Server to be restarted.
OS Services (System ▶ OS Service)

Value Description
Enable Select this box to either enable or disable HTTP Service.

Enabling/disabling is equivalent to turning the HTTP Server on/off .
HTTP Port Read only. HTTP Port = 80
HTTPS Port The HTTPS Port number. The default port number is 443, and the
range is 1024 to 65535.
HTTPS Redirect HTTP Redirect option. Enable this option to allow redirect from
HTTP to HTTPS. When disabled, this option prevents redirection
from HTTP to HTTPS and turns off HTTP support.
HTTP Origin Select this box to either enable or disable HTTP Origin.
Use the text box to edit the list of approved origins (add or remove
URLs). The list can contain a maximum of 5 approved origins.

4. Configuring Plug & Go
4.1 Understanding Plug & Go 65
4.2 Configuring a Unit for Beacon 67
4.3 Configuring the Forwarding Settings of Intermediate Units 72
4.4 Managing Network Inventory 73

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.
CAUTION: Because Plug & Go relies on UDP port 9065 for advertisements, and
UDP ports 67 and 68 for beacons, you must ensure that these ports are not
blocked by a firewall.
Note: The use of /31 interfaces is not supported with Layer-3 beaconing when
the "IP Config Mode" parameter is set to either "Auto" or "Auto-Static". Layer-3
Plug & Go uses the subnet's broadcast address to transmit beacon and
advertisement frames. However, /31 subnets do not have a broadcast address
because they contain only two IP addresses, and are therefore reserved for
point-to-point links.

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 Layer 2 or Layer 3. Configure the unit to
send beacon frames at Layer 2 if the remote units are within the same subnet. Configure the
unit to send beacon frames at Layer 3 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"

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 73.
▶ To configure a logical interface for sending beacon frames at Layer 2
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 ▶


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 DHCP Relay to send the beacons via a DHCP relay (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 Enables or disables the use of a specific interface for sending the
Settings 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 DHCP relay (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 is enabled.
DHCP Relay The subnet of the DHCP relay interface that faces the client
Destination Subnet network
Note: Only available when Use DHCP Relay is enabled.
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
IP Subnet The IP subnet used by the units receiving the beacon frames
Note: Only applies to the Auto and Auto-Static IP config modes.
Mask The subnet mask used by the units receiving the beacon frames
Gateway The gateway used by the units receiving the beacon frames
IP Exclusion 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 IP addresses.
A total of 100 IP addresses can be specified here, including both
address ranges and single IP addresses.
DHCP Host Name The name assigned to the DHCP host. Possible values are:
Current hostname
Serial number
Custom hostname
Note: Only applies to the DHCP IP config mode.
Field to the right of Enter the DHCP hostname or serial number value here after making
the DHCP Host Name a selection in the DHCP Host Name drop-down list.
DHCP Client ID The ID assigned to the DHCP client. Possible values are:
Serial number
Custom client ID
Field to the right of Enter the DHCP client's serial number or custom client ID value here
the DHCP Client ID after making a selection in the DHCP Client 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 Layer 3

▶ 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 Layer 3

▶ 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 ▶

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 Logical
Interfaces on page 25).
▶ 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 added to
Filtering 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 Warning The inventory NIDs are limited to 4000 devices. This field allows the
Threshold user to set an inventory almost full value, which then delivers a
notification alarm when this value is approaching. Default setting is
3000. If this value is reached the almost full alarm is raised, and
then inventory full alarm is raised if the inventory NIDs reach the
4000 devices limited.
Inventory
Remote NID IP The IP address assigned to the remote unit
System Description The type of remote equipment, such as AMT-1000-GX
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 advertisement
Address 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 73.
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 73.
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 73.
You can also configure a logical interface for beacon on the Interface Settings page. Refer to
Configuring Logical Interfaces on page 25.

5. Configuring the Unit
This chapter describes how to configure, upgrade and restart the unit; it contains the
following sections:
5.1 Configuring General System Settings 77
5.2 Configuring IPv4 Settings 79
5.3 Provisioning DHCP Relay 81
5.4 CPU OAM Options 82
5.5 Setting Dry-Contact Inputs 84
5.6 Setting the System Date and Time 86
5.7 Setting Up SyncE 93
5.8 Viewing SyncE/ESMC Port Statistics 96
5.9 Setting Up DNS 100
5.10 Configuring Traffic 101
5.11 Upgrading the Firmware 103
5.12 Importing and Exporting the Unit’s Configuration 107
5.13 Tech Support 109
5.14 Viewing CPU Usage 110
5.15 Configuring System Monitor 111
5.16 Rebooting the Unit 114
5.17 Restarting the Unit 115
5.18 Restoring Factory Default Settings 116

5.1 Configuring General System Settings
5.1.1 Setting the S-VLAN Ethertype

The Ethertype value that is associated with the Service VLAN (S-VLAN) is set globally for the
unit. The S-VLAN Ethertype options are:
0x88A8: Most applications use this value

0x9100: A supported legacy value
The S-VLAN value is typically left at the default of 0x88A8.

If you change the S-VLAN Ethertype value to 0x9100, the T-VLAN Ethertype value will
automatically be switched to 0x88A8. All units in a given network that use the S-VLAN
Ethertype must have the same assigned Ethertype value.
Tip: To avoid issues related to changing the S-VLAN value, consider assigning the
appropriate value to the S-VLAN Ethertype before creating system elements that require
a defined Ethertype, such as interfaces, filters and RFC-2544.
For more information on specific parameters, refer to the table General System Settings
(System ▶ Configuration▶ Mode) on page 77.
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.

(System ▶ Configuration ▶ Mode).
(System ▶ Configuration ▶ Traffic ▶ Mode).
General System Settings (System ▶ Configuration▶ Mode)

S-VLAN Ethertype This value affects all elements that make use of the S-
VLAN Ethertype, such as interfaces and filters.
0x88A8
0x9100

Note: This value is typically left at the default of 0x88A8.
T-VLAN Ethertype This value appears here for your convenience, based on the
value selected in the S-VLAN Ethertype drop-down list
above.
Management Traffic Regulation (MTR)
State Enable/Disable the regulation of management traffic.
Rate (Kbps) The average data rate, expressed in kbps
Latency (ms) The transmit queue size, expressed in milliseconds
Burst (bytes) 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 unit’s 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 IGMP Version drop-down list, then click Apply.
IPv4 Settings (System ▶ IPv4)

IGMP Version The IGMP version for the unit. This value 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.
Enable Forwarding Select this box to enable the IPv4 forwarding feature on a per-
interface basis. You must now enable forwarding in the System ▶
Configuration ▶ Interface page for each IPv4 interface on which
you want to forward ingress traffic.
If you clear this box, IPv4 forwarding on all interfaces configured on
this unit will be automatically disabled.

5.2.2 Enabling IPv4 Forwarding

The IPv4 forwarding feature enables you to reroute ingress traffic from one interface on the
unit to another. It can be used as part of performing traffic management tasks.
You can enable IPv4 forwarding on any type of ingress interface via either the Web Interface
or CLI, but not via SNMP.
Note: To apply IP forwarding to the ingress traffic on a particular interface,

access the page Configuration ▶ Interface ▶ <Interface_Name> and select the
box Allow IP Forwarding. "Configuring Logical Interfaces" on page 25 for
details.
▶ To enable IPv4 forwarding
1. Access the page System ▶ IPv4.
2. Select the Enable Forwarding box, then click Apply.

For more information on specific parameters, refer to the table above.

5.3 Provisioning DHCP Relay

The DHCP relaying feature enables you to redirect DHCP requests ingressing on the unit to
specified servers on the dynamic circuit network (DCN). It can be used as part of performing
traffic management tasks.
Note: To enable relaying DHCP requests on a particular interface to the server or

servers you specify in this page, you must access the page Configuration ▶
Interface ▶ <Interface_Name> and select the box Allow DHCP Relay. See
"Configuring Logical Interfaces" for details.
▶ To enable DHCP relay provisioning
1. Access the page System ▶ DHCP Relay.
2. Configure DHCP relaying by setting the appropriate parameters, then click Apply.
DHCP Relay Settings (System ▶ DHCP Relay)

Enable DHCP Relay Select this box to enable the DHCP Relay feature on a per-interface
basis. You must now enable DHCP Relay in the System ▶
Configuration ▶ Interface page for each IPv4 interface on which
you want to relay DHCP requests.
If you clear this box, DHCP relaying on all interfaces configured on
this unit will be automatically disabled.
Server 1 and Server 2 Enter the IP address of one or two servers to which all
DHCP requests will be directed. The servers you indicate must
reside on the same subnet as the unit.
You must ensure that the addresses you enter here are assigned to
accessible DHCP servers. No validation of these addresses is
performed.
Note: The servers you specify here do not act as a
primary/secondary pair; either server may respond to a DHCP
request. All DHCP requests are received by both servers.

5.4 CPU OAM Options

Use this page to restrict the types of broadcast frames (and IPv6 multicast frames) that are
sent to the CPU, as part of performing traffic management tasks. You can specify a different
management mode for each port on the unit.
Note: A LAG's management mode is only applied to the physical ports it

comprises if the protection option is enabled on the LAG. Otherwise, the settings
for the ports are applied to the physical ports.
▶ To view or configure CPU OAM options
1. Access the page System ▶ CPU OAM Options.

All local ports (including LAG ports) and their current management mode are displayed.
The total number of ports found in the system is given in the lower-left corner of the
page, as well as the index values of the ports currently displayed on-screen (for
2. To update a port's settings, click its name under the Port Name heading.
The CPU OAM Options page is displayed.
3. Configure the management mode by making a selection from the drop-down list, then
click Apply.
CPU OAM Options (System ▶ CPU OAM Options)

Port Name The name of the port you selected in the previous page appears
here.
You cannot modify this value.
Management Mode Make a selection from the drop-down list to indicate how sending
broadcast and multicast frames to the CPU should be handled:
Note: Choosing a management mode other than Auto can create
situations where you lose access to the unit. For example, ensure
that your policies have been created before selecting Policy as the
management mode.
Auto: Allow the system to determine which broadcast and

multicast frames to send to the CPU, based on how the interface
is configured. This is the default value, and the least restrictive
management mode.

MAC-OUI: Only accept broadcast and multicast frames

originating from source MAC addresses that contain an
Accedian OUI value: 0015AD or 0024FD.
Policy: No broadcast or multicast frames are allowed by default.
Sending these frames to the CPU is controlled entirely via
MGMT-OAM policies you create.

5.5 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 ▶ Dry-Contact.
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.6 Setting the System Date and Time

Accurate, precise date and time values are important when managing and troubleshooting a
network. These values are used for time-stamping alarms, among other useful functions.
The system date and time can be set manually, or be automatically controlled. For an
automatic time setting you may use an NTP server, a PTP server or a GPS. The GPS option will
provide the highest accuracy. However, any unit can act as an NTP server if you select the
NTP Server Enable option.
Note: To avoid conflicts, we recommend that only one NTP server be used in a
network.
Procedures for setting the date and time manually and automatically are provided below.
5.6.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 88 .
5.6.2 Setting Date and Time Using NTP

The unit stores a list of NTP servers that can be used to set the unit date and time. You can
add up to seven servers to the list and enable one or two of them (a primary and a secondary,
if the primary is not available).
▶ To set the date and time using NTP
2. Select the NTP Enable option.
3. Verify that the NTP server you want to use appears in the NTP Server List.
4. If the preferred NTP server is not in the list, add a new server by specifying its name or
IP address in the NTP Server box then clicking Add.
5. Select a time server from the list, then click Apply.

▶ To delete an NTP server
2. Select the NTP server's entry from the NTP Server List by clicking its name or
IP address.
Tip: Do not click the check box.
3. Click Delete.
Setting Date and Time Automatically Using PTP

▶ To update the date and time automatically using a PTP server
Refer to IEEE Std. 1588-2008 for more information about the Precision Time Protocol.
Notes:
You can enter up to two PTP servers for PTP synchronization.
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.
2. Select the PTP Enable option.
3. Verify whether the PTP server you want to use appears in the PTP Server 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 parameters and then click Apply.
▶ To delete a PTP server
2. Select the PTP server's line from the PTP Server List by clicking its name or IP address.
Do not click the check box.
3. Click Delete.
Setting the System Date and Time Automatically Using a GPS

▶ To 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/or 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) 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 Time
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, 2015, 26 leap seconds were added to the difference.
Since the last second was added on December 31, 2016, TAI has
been exactly 37 seconds ahead of UTC.
It is important that the TAI offset value be consistent throughout
your network in order to ensure valid measurements and avoid
synchronization issues. This is particularly true if Accedian products
are being used with equipment from other vendors that support
leap seconds. If there is a TAI mismatch between units, the one-way
delay measurements will show an offset of one second.
In most cases, it is preferable to allow the unit to update its
TAI offset value through a firmware upgrade (during a
maintenance window, to minimize impact) instead of manually
changing the value here.
Synchronization The s tatus 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 the NTP Server Enable box is 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
this option is not enabled, the NTP server is queried only every
30 minutes and the system time is set accordingly, without further
processing.
NTP Server List One or two NTP servers can be enabled. The unit will automatically
update its date and time from one of the enabled NTP servers. If
the NTP server being used is unreachable, the unit will attempt to
contact 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 NTP server during each time interval.
DSCP When using NTP, the priority can be set in the Differentiated
Services Code Point by making a selection in the drop-down list.
VLAN Priority When using NTP, the priority of the VLAN frames can be set in the
VLAN priority bits if the link is through a VLAN.
PTP Server List When using PTP, the unit will automatically update its date and
time from the one or two PTP servers on this list.
PTP Server 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 PTP server to add
UTC Offset from When using PTP, enable the use of UTC offset from the master
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.
-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
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 to apply to the time
zone:
North America applies a negative offset.

Eastern Europe applies a positive offset.
Range: -12 to +14
Daylight Saving Time Select to use daylight saving time (DST).

Enable
Note: Services such as syslog that timestamp events with the
current time and date are affected during DST transitions. As such,
you may observe 60-minute gaps or duplicate timestamps around
the time when the clock was changed.
Daylight Saving The time adjustment to apply to the GMT offset during the daylight
Offset 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.7 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 clock signal from 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 recovered.
Source
This parameter is 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
becomes 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 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 than
extended TLV 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 applies when ESMC QL Mode is enabled.
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.
Holdover: The selected reference clocks are no longer available
and the system is in holdover 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 (with
Selector 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.
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.8 Viewing SyncE/ESMC Port Statistics

If your equipment has this optional hardware feature, 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. Ensure that the option ESMC QL Mode is selected.

Summary statistics and the port status for all ports are displayed in the SyncE/ESMC
Port Statistics Summary section at the bottom of the page.
3. To view detailed SyncE/ESMC statistics for a port, select its name from the list.
SyncE/ESMC Port Statistics (Port ▶ SyncE)

Current QL to The current QL (Quality Level) used for the clock selection process with
Clock Selection the time elapsed in seconds (with millisecond resolution) since the last
Process 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 seconds

Remaining
Minimum QL Indicates the minimum time between any two consecutively received
Received Inter- QL for ESMC PDU of type informational
Arrival Time
Maximum QL Indicates the maximum time between any two consecutively received
Arrival Time
Averaged QL Indicates the averaged time between any two consecutively received
Arrival Time
Count of ESMC Indicates the number of ESMC PDU that have been received
PDU Received
Count of ESMC Indicates the number of ESMC PDU Malformed that have been
PDU Malformed received
Received

Count of ESMC Indicates the number of ESMC PDU that have been received with the
PDU of Type type event (event flag set to 1)
Event Received
Count of ESMC Indicates the number of ESMC PDU that have been received with valid
PDU Received QL and extended TLVs
with Valid QL and
Extended TLVs
PDU Received Quality Level STU/UNK:
with QL-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.
PDU Received Quality Level PRS:
with QL-PRS
(Option 1) QL-PRS: Primary reference source traceable [ITU-T
G.811]
PDU Received Quality Level PRC:
with QL-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].
Count of ESMC Indicates the number of ESMC PDU that have been received with
PDU Received Quality Level Invalid Code 3
with QL-INV3
PDU Received Quality Level SSU-A/TNC:
with QL-SSU-
(Option 1) QL-SSU-A: This synchronization trail transports a
A/TNC
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)
with QL-INV5
Count of ESMC Indicates the number of ESMC PDU received with Quality Level Invalid
PDU Received Code 6

with QL-INV6
PDU Received Quality Level ST2 :
with QL-ST2
(Option 2) QL-ST2: Traceable to stratum 2 (ITU-T G.812], type V)
PDU Received Quality Level SSU-B:
with QL-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].
with QL-INV9
PDU Received Quality Level EEC2/ST3:
with QL-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)
PDU Received Quality Level EEC1/SEC:
with QL-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.
PDU Received Quality Level SMC:
with QL-SMC
(Option 2) QL-SMC: Traceable to SONET clock self-timed ([ITU-T
G.813] or [ITU-T G.8262], option II)
PDU Received Quality Level ST3E:
with QL-ST3E
(Option 2) QL-ST3E: Traceable to stratum 3 ([ITU-T G.812], type
IV)
PDU Received Quality Level PROV:

with QL-PROV (Option 2) QL-PROV: Provisionable by the network operator
PDU Received Quality Level DNU-DUS:
with QL-DNU-
(Option 1) QL-DNU: This signal should not be used for
DUS
synchronization.
(Option 2) QL-DUS: This signal should not be used for
synchronization.
Count of ESMC Indicates the number of ESMC PDU that have been sent
PDU Sent
Count of ESMC Indicates the number of ESMC PDU that have been sent with the type
PDU of Type event (event flag set to 1)
Event Sent
Count of ESMC Indicates the number of ESMC PDU that have been sent with
PDU Sent with extended TLV forwarded
Extended TLVs
Count of ESMC Indicates the number of times an ESMC failure was detected (no QL for
Failure Detection five-second timeout)
Count of Signal Indicates the number of times a signal failure was detected
Failure Detection

5.9 Setting Up DNS

You can use DHCP to automatically configure the IP parameters of a unit. When the unit uses
DHCP, it can be configured to obtain its DNS settings via DHCP. If the unit does not use
DHCP, you can manually specify the address for each DNS server.
Note: 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 20.
▶ 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 20.

5.10 Configuring Traffic
5.10.1 Setting the Working Rate

You must select the layer (Layer-1 or Layer-2) 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: Rate calculation is based on the Layer-1 frames sizes, including the size of the
Inter-Frame Gap (IFG), Preamble and Start-Frame Delimiter (SFD)
Layer-2: Rate calculation is based on the Layer-2 frames sizes, which does not include
the size of the Inter-Frame Gap (IFG), Preamble or 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 (Layer-1 or Layer-2) 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 level
settings on page 101.
5.10.2 Selecting VLAN level settings

The VLAN level for each Traffic Port must be configured to be used with one or two VLAN
tags in the VLAN filters.
When the VLAN level setting is configured as "Outer" (default), then the VLAN filter is
matched against the outer VLAN of incoming frames. With this option, the outer VLAN ID can
only be used once per port in the VID sets.
When the VLAN level setting is configured as "Inner", then the VLAN filter is matched
against both outer and inner VLANs of incoming frames. With this option, the inner VLAN ID
can only be used once per port in the VID sets.
In all cases, the VLAN type must match the filters.
▶ 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’s VLAN level inspection mode:

Traffic-2 Outer: to inspect the Outer VLAN only
Traffic-3 Inner: to inspect the combination of the Outer and Inner VLANs
Traffic-4 Default: Outer
Traffic-5
Traffic-6
Traffic-7
Traffic-8
Rate Settings
Generator Working The layer used by the unit to determine the working rate:
Rate
Layer-1: Rate calculation is based on the Layer-1 frames sizes,
Regulator Working
including the size of the Inter-Frame Gap (IFG), Preamble and
Rate
Start-Frame Delimiter (SFD)
Shaper Working Rate
Layer-2: Rate calculation is based on the Layer-2 frames sizes,
which does not include the size of the Inter-Frame Gap (IFG),
Preamble or Start-Frame Delimiter (SFD)

5.11 Upgrading the Firmware

New firmware versions typically provide:
Additional functionality
Enhancements to the existing feature set
Defect corrections
To verify the current firmware version, refer to the Current Version field of the Firmware
Maintenance section in the System ▶ Maintenance ▶ Firmware page.
You can upgrade the firmware by downloading the firmware file directly from your computer
or network. If you are using the Command Line Interface (CLI), you can also upgrade the
firmware via an SFTP, HTTP, FTP or SCP server for a file transfer.
There are two ways to upgrade license server 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 license server 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 license server. You cannot store both a rollback firmware
file and a pending two-step upgrade download on the license server.
▶ 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. To verify that the upgrade was successful, access the page Home and examine the
value specified in 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 116. If a
firmware downgrade fails using the two-step procedure, repeat the downgrade
as a one-step procedure.

The Firmware Maintenance window is displayed; the One-Step tab is visible by 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

3. Ensure that the version number displayed next to the Downloaded version is the
correct firmware 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.
5. To verify that the upgrade was successful, access the page Home and examine the
value specified in the Firmware version field.

▶ To delete the downloaded firmware file
Note: This feature is provided for your convenience only. Deleting a downloaded
firmware file after it has been applied is optional. Furthermore, downloading a
new firmware file will automatically overwrite the existing file (if any) stored on
the unit.


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 field is updated to None.
▶ To revert to the previous firmware version
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
unit's configuration.

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 the
Button unit.
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

2. Click the Factory Default button.
3. Click the Browse button next to the New Firmware field and select the new firmware
file from the dialog box that appears.
4. Click the Upgrade button.

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

5.12 Importing and Exporting the Unit’s Configuration

If multiple units in your network must share a common configuration, you can configure your
first unit, 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 directly from your computer or network.
Each configuration file provides an identifier to help prevent importing an incorrect file.
CAUTION: Pay special attention to the DNS settings when using the
import/export function. 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.
CAUTION: Although you can edit a configuration file, you risk corrupting its data!
The file contents are encoded in a UNIX text format and should not be opened
with a Windows text editor such as Notepad.
CAUTION: After making configuration changes,we recommend that you wait at

least 30 seconds before exporting the configuration file. This ensures that the
latest changes have been written to the file and that the file is ready to be
exported.
▶ To export a configuration file
2. Enter a configuration filename 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, then click OK.

5. Click the Import button.
6. After 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 the
filename 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 reboot. If
button needed, you can cancel an action by clicking Cancel Changes.
Rollback button Click to revert configuration of the unit to the version from the last
reboot.

5.13 Tech Support

Tech Support provides the capability of generating and exporting system health reports.
▶ To generate and export system health reports
2. Complete the required fields, then click Export.

For more information on the other parameters, refer to the following table.
Tech Support Parameters (System ▶ Maintenance ▶ Firmware)

Report Enter a file name for the report that needs to be generated.
Generate Report Click to generate a new report.

button
Issue export filename Enter a file name for the report that needs to be exported.
Export button Click to export the current report with the name indicated in "Issue
export filename". If "Issue export filename" is empty, the report will
be exported with the name indicated in "Report" parameter.

5.14 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 unit’s 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
5 Minutes Average The CPU usage average from the last completed five-minute period
CPU Usage History The CPU usage from the last 100 seconds, presented as a graph

5.15 Configuring System Monitor

System Monitor allows for the monitoring, logging and alerting of system resources (CPU,
Memory, Disk Usage) and Network statistics. This feature can be enabled or disabled and set
to operate in either Debug or Normal mode.
Three Probes can be configured when System Monitor is enabled:
System Probe, to measure and report on CPU and memory usage as well as number of
top level processes.
Disk Probe, to measure and report on disk usage.
Network Probe, to report statistics (packets sent/received, bytes sent/received) about
currently active network devices. The Network Probe can only be used in Debug mode
and does not have any threshold limits.
▶ To enable the System Monitor and configure Probes
1. Access the page Debug ▶ System Monitor.

The System Monitor General Settings page opens.
2. Select the Enable check box to enable System Monitor.
3. Select the Mode and Output type.

In normal mode, logs of levels greater than or equal to "NOTICE" will display the probe
parameters for which thresholds have been exceeded, at the provided interval. In
debug mode, logs of level "DEBUG" will display all probe parameters, at every interval
whether thresholds have been exceeded or not.
Note: When configuring the System Monitor to be in Debug mode, the user
needs to set the Syslog level to "DEBUG" (System ▶ Agent ▶ Syslog). If
configuring the System Monitor to be in Normal mode, the user can set the
Syslog level to either "NOTICE", "INFO" or "DEBUG". This ensures the System
Monitor is able to successfully report the logs to Syslog.
4. Choose the Probe you want to enable by selecting the corresponding check box.
You can enable the System Probe, the Disk Probe and the Network Probe (can only be
used in Debug mode).
5. Configure the Probe parameters then click Apply.

System Monitor (Debug ▶ System Monitor)

General Settings

Enable Enable or disable the System Monitor feature. Default is

Disable.
Mode Configure the working mode. Debug or Normal, default is

Debug.
Output type The only output type currently supported is syslog.
System Probe
Enable System Probe Default is Enable.
Interval (in seconds) Interval at which the probe will collect data. Range is 1–60,
default is 10.
Critical CPU threshold (%) The threshold for CPU load at which a critical alarm will be
raised in normal mode. Range is 1–99, default is 90.
Warning CPU threshold (%) The threshold for CPU load at which a warning alarm will
be raised in normal mode. Range is 1–99, default is 70.
Critical Memory threshold (%) The threshold for memory usage at which a critical alarm
will be raised in normal mode. Range is 1–99, default is 90.
Warning Memory threshol (%) The threshold in percentage for memory usage at which a
warning alarm will be raised in normal mode. Range is 1–
99, default is 70.
Number of top-processes The number of processes that are reported to the output
interface. Range is 1–10, default is 4.
Sort by The criteria to sort the processes. Mem or CPU, default is

CPU.
Disk Probe
Enable Disk Probe Default is Enable.
Interval (in seconds) Interval at which the probe will collect data. Range is 1–60,
default is 10.
Critical Usage threshold (%) The threshold for disk space usage for which a critical
alarm will be raised in normal mode. Range is 1–99, default
is 90.
Warning Usage threshold (%) The threshold for disk space usage for which a warning
alarm will be raised in normal mode. Range is 1–99, default
is 70.
Network Probe
Enable Network Probe Default is Enable.
Interval (in seconds) Interval at which the probe will collect data.
Range is 1–60, default is 10.

Output information (Syslog)

The following example shows the values that are reported in the Syslog for the all three
probes (Network, Disk and System).
Jan 2 07:07:36 G274-0469 sysmon[609]: NETWORK: frames[547,320] bytes
[434479,31084]
Jan 2 07:07:36 G274-0469 sysmon[609]: DISK: /tmp 2.9% |/etc/accedian 10.5%

|/etc/accedian/history 0.0%
Jan 2 07:07:36 G274-0469 sysmon[609]: SYSTEM: MEM[77,45,8,0] loadavg[36,27,25]

CPU[68.0,22.7] webs[52.0*,0.8] portd[3.0,1.9] sysmond[2.0,0.3] eventd[1.0,0.3]
The information reported for the Network Probe represents:

NETWORK: frames [packets sent on all interfaces in current interval, packets received on all
interfaces in current interval] bytes [sent on all interfaces in current interval, received on all
interfaces in current interval].
The information reported for the Disk Probe represents:

DISK: disk1_name used in % | disk2_name used in % | disk3_name used in %.
The information reported for the System Probe represents:

SYSTEM: MEM [usage in MB, free in MB, cache in MB, free swap in MB] loadavg [utilization in
1m, utilization in 5m, utilization in 15m] CPU [cpu usage in this interval, use usage lifetime]
process1 [% cpu*, RES memory in MB] process2 [% cpu, RES memory in MB] process3 [% cpu,
RES memory in MB].

5.16 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 and Exporting the Unit’s Configuration on page 107.
CAUTION: Rebooting a unit is disruptive. It applies changes in the unit’s

configuration and affects current operations.
▶ To reboot the unit
2. Click the Reboot button.

5.17 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 its
factory default values.

5.18 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 unit’s 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 ports, which are the 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 SFP Configuration 146
6.8 Testing a Cable 147

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 GX Performance Element is available in two models with the following physical traffic
ports:
Connector Configuration
Port Type
Port Name and Speed
GX GX-S
PORT-1 (100/1000 Mbps) Optical (SFP) Optical (SFP)
PORT-5 (100/1000 Mbps) Copper (RJ45) Optical (SFP)
The GX Performance Element supports both fiber and copper SFPs on Ports 1-4. The GX-S
Performance Element supports both fiber and copper SFPs on Ports 1-8.
The GX and GS-X Performance Elements display LAG-1, LAG-2, LAG-3 and LAG-4 in the Ports
Config page.
LAG-1 protects PORT-1 and PORT-2. Traffic is mapped to Traffic-1.

▶ To view current 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 GX or GX-S Performance Element).

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 and Status (Port ▶ Configuration)

Status The following colors in the summary page indicate the port status:
Green: The port is up and running

Blue: Indicates that a signal is detected, but the protection
mode for the parent LAG port is "Link-status" and the port is
not the working connector.
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 type of physical connector associated with the port.

SFP
RJ45
Management
Port Name The name of the port.

By default, ports are named as follows: PORT-1, PORT-2 , PORT-3,
PORT-4, PORT-5, PORT-6, PORT-7, PORT-8, LAG-1, LAG-2 ,
LAG-3 and LAG-4.
Port State The port may be either enabled or disabled.
Speed Sets the port speed and duplex type.

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.
On other devices, if Auto-Negotiation is not in use, you can
manually define the port speed:
100 Mbps
1 Gbps
On other devices, if Auto-Negotiation is not in use, you can

manually define the duplex type:
Half-Duplex: Transmission in one direction at a time.

Full-Duplex: Transmission in both directions at the same time.
Notes: Unsupported options, if any, are disabled.

In 1G mode, auto-negotiation may be selected (advertises 1000
Mbps, full-duplex only).
Auto-negotiation is mandatory for 1000 BASE-T.
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.
MAC Address The MAC address assigned to the port, for example
00:15:AD:1D:72:00.
▶ To configure current port settings

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 GX or GX-S Performance Element).
2. Click the name of the port's settings, under the Port Name heading.
The Port Configuration page is displayed.
3. Enter values in the required fields, then click Apply.
Note: When disabling a regular port or a LAG port, the following message will
be displayed "Configuration changes are service affecting. Are you sure you
want to proceed?". Click OK to proceed with your changes or Cancel to go back
to the previous screen.
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_Name> Port Configuration (Port ▶ Configuration)

Enable Select this box to enable this port.
Name Enter a name to identify this port.

By default, ports are named as follows: PORT-1, PORT-2 , PORT-3,
PORT-4, PORT-5, PORT-6, PORT-7, PORT-8, LAG-1, LAG-2 , LAG-3 and

LAG-4.
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
Notes:
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.
The MTU size supports up to 12 additional bytes over and above the
defined value to account for a VLAN stack of up to three tags.
Large Packet Packets above this threshold will be classified as Large Packets. The
Threshold Large Packets count can be viewed on the Port ▶ Statistics page.
MAC Address The MAC address assigned to the port, for example 00:15:AD:1D:72:00.
Connector The type of physical connector associated with the port.

SFP
RJ45
Management
Enable Fault Enables the propagation of link faults between the ports specified in
Propagation the field Propagate From Port.
Fault One-Way Link: Propagate faults in one direction based on the link
Propagation status of the opposite port.
Mode
One-Way EVC: Propagate faults in one direction based on the link
status of the opposite port or based on the EVC status.
Propagate From The port for fault propagation may be one of the following:
Port
PORT-1 or PORT-2: The unit propagates the fault from any port
other than itself, or from the LAG-2, LAG-3 or LAG-4 port.
PORT-3 to PORT-8: The unit propagates the fault from PORT-1,
PORT-2 or LAG-1.
LAG-1: The unit propagates the fault from PORT-3, PORT-4,
PORT-5, PORT-6, PORT-7, PORT-8, LAG-2, LAG-3 or LAG-4.
LAG-2 to LAG-4: 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 Protection box,
then click Apply. The Propagate From Port drop-down list will then be
displayed.
Media Auto MDI means that the unit automatically adapts the configuration of
Dependent the connector to the cabling plant and type of link partner.
Interface
If Auto MDI is not in use, you can manually define port settings as
follows:
(Copper ports MDI: Typical setting for an Ethernet station. Link partner must be
only)
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.
On other devices, if Auto-Negotiation is not in use, you can manually
define the port speed:
100 Mbps
1 Gbps
On other devices, if Auto-Negotiation is not in use, you can manually

define the duplex type:
Half-Duplex: Transmission in one direction at a time.

Full-Duplex: Transmission in both directions at the same time.
Notes: Unsupported options, if any, are disabled.

In 1G mode, auto-negotiation may be selected (advertises 1000 Mbps,
full-duplex only).
Auto-negotiation is mandatory for 1000 BASE-T.
Link Loss Return This option determines how the unit notifies its link partner when a
(LLR) valid receive signal is absent on the link.
If LLR is disabled, then:
Note: (SFP fiber For 1000BASE-X links, a Remote Fault Indicator (RFI) using auto-
ports only)
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 Click this box to enable or disable the internal loopback mode. Enabling
Loopback Enable the system loopback mode redirects the transmitted frames to the
receive path.
Timeout value has a range of 0-60 minutes. The default is 5 minutes.
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.
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 .
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 The working physical port for the specified LAG port. Choosing the port
Connector 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.
Notes: The timer is restarted if a signal loss is detected during this
period.
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.
Notes: In a back-to-back deployment, it is recommended to set a
different link timeout on each unit for a faster link-up time.
This parameter applies to only link status and is available only 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.
Rate The LLDP frame transmission rate on the port, expressed in seconds.
Range: 1 to 3600
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].
Current Status The current link speed and duplex type of the port.
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.

Besides, the current status can be:
Link Down: The physical link is down and no signal is detected

(when a port is disabled, Current Status will also show Link Down).
Link Dormant: The port is enabled and a signal is detected but the
port cannot forward traffic, as it is in a "stand-by" state.
Note: There will be no 'Link down on <port_name> port' alarm on

member ports when the parent LAG port is in Fault Propagation
state.

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-5 or LAG-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 "Monitoring
Network Performance with Service OAM" on page 250.
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.
▶ 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 "Port Configuration and Status
(Port ▶ Configuration)" on page 119.

6.3 Network Requirements — TCP/UDP Ports

Accedian demarcation devices, including the GX Performance Element, use various
Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) ports for different
services and applications.
The following table lists the TCP and UDP ports used by Accedian demarcation devices. This
information is useful for configuring firewalls on a network.
TCP/UDP Port Usage by Accedian Devices
Note: The indicated destination ports are the default values. You can use
different values as needed.
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
SAT reporting

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

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

Device
Firmware upgrades
TCP 22 SCP File Transfers: Device to Server; Server to

Device
Firmware upgrades
TCP 22 SFTP File Transfers: Device to Server; Server to

Device
Firmware upgrades
SAT reporting
RFC-2544 report
uploads
TCP 80 HTTP File Transfers: Device to Server
Firmware upgrades
History file transfer
UDP 862 TWAMP Two-Way Active Device to Server

Measurement Protocol
UDP 6000 TWAMP Two-Way Active Device to Server

Dest. Service
Port Name
(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 Device to Device

(see Traffic
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

6.4 Viewing Port Statistics

You can view a summary and a detailed port statistics for each port. The port’s 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.
▶ To view a summary of statistics for all ports
1. Access the page Port ▶ Statistics.
2. (Optional) Select the Broom icon to clear the 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 n 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.
Tip: Click the Clear button to reset all counters to 0.
Port Statistics (Port ▶ Statistics)

Summary Page
Port Name The port for which statistics are displayed.
Txm Packets The total number of frames/packets (both good and bad)
transmitted by the port. Bad frames include normal collisions, late
collisions and FIFO underflows.
Txm Errors Number of transmission errors.
Rcv Packets The total number of frames/packets (both good and bad) 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 total number of bytes transmitted by the port in good frames.
The number of bytes 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
64 bytes (after any padding) up to the maximum size.
Bytes Total The total number of frames/packets (both good and bad)
transmitted by the port. Bad frames include normal collisions, late
collisions and FIFO underflows.
Unicast Packets The count of the good (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 (the first bit
transmitted is a 0).
Multicast Packets The count of the good (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 (not dropped and having a valid CRC)
broadcast frames transmitted by this port.
Broadcast frames are identified by a destination address consisting
of all 1s.
Pause Frames The count of the good (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 (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 number of frames that were deferred on the first transmit

attempt due to the medium being busy. Frames with subsequent

deferrals (for example, 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 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 3036 byte times have passed
without the transmission starting.
Single Collisions The number of times a frame was successfully transmitted from this
port after experiencing a single collision.
This count does not include erroneous (dropped) frames.
Multiple Collisions The number of times a frame was successfully transmitted from this
port after experiencing multiple collisions.
This number does not include erroneous (dropped) frames or
frames dropped due to excess collisions.
Excessive Collisions The number of frames dropped by this port due to excess collisions
(number of collisions equals MaxRetry+1)
This number 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 number of frames dropped by this port due to late collisions. A
late collision is an 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 number does not include frames dropped due to FIFO
underflow. Late collisions are not retried.
Normal Collisions 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 was not
attempting to transmit are not counted.
This number does not include collisions during half-duplex back
pressure.
FIFO Errors 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 and bad) transmitted by this port
that were exactly 64 bytes in length (excluding the preamble and
SFD, but including the CRC).
Packets 65–127 The total number of frames (good or bad) transmitted by this port,
that were of the length indicated in the parameter column
Packets 128–255
This frame length value excludes the preamble and SFD, but
Packets 256–511
includes the CRC.
Packets 512– 1023
Note: Frames with a length of 1024 and above are only available on
Packets 1024–1518 certain types of units.
Packets 1519–2047
Packets 2048–4095
Packets 4096–8191
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
Notes: 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.
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 Layer-2
for the selected port, expressed in Mbps
Receive Statistics
Bytes Good The total number of bytes received by the port in good frames. This
number 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 total number of frames/packets (both good and bad) 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 number of error-free frames shorter than 64 bytes that were
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 number of frames received on this port that were shorter than
64 bytes and have an invalid CRC. Frames with PHY or FIFO errors
are not counted
Long OK The number of error-free frames received that are longer than the
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 number of frames received that are longer than the MTU
configured on the port and have an invalid CRC. Frames with PHY
or FIFO errors are not counted.
Unicast Packets The number 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
received is a 0).
Multicast Packets The number of good multicast frames received by this port. A good
multicast frame is a normally-sized frame (64 to MTU configured on
the port) that is not dropped and has a good CRC.
Multicast frames are identified by having a 1 in the least significant
received is a 1). Broadcast frames are not included in this number.
Broadcast Packets The number of good broadcast frames received by this port. A good
broadcast frame is a normal-sized frame (64 to MTU configured on
the port) that is not dropped and has a good CRC. Broadcast frames
are identified by a destination address of all 1s.
Pause Frames The number of 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 number of 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 , 88A8h or
9100h , set in the outer VLAN tag.
CRC Errors The number 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 number 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 number of received 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 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 (46–1500 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 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 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 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 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 23 nibbles) 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 20 bytes long (12 bytes of IFG and 8 bytes of
preamble/SFD). The enforcement limit is set to 10 bytes (half the
normal gap length).
Bad OpCode The number of 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 64 bytes in length (excluding preamble and SFD but
including CRC)
Packets 65–127 The total number of frames (good and bad) received by this port,
that were 65 to 127 bytes (or the other length) in length inclusive
Packets 128–255
(excluding the preamble and SFD, but including the CRC).
Packets 256–511
Note: Frames with a length of 1024 and above are only available on
Packets 512–1023 certain types of units.
Packets 1024–1518
Packets 1519–2047
Packets 2048–4095
Packets 4096–8191
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 traffic
Utilization (%) on the selected port, expressed as a percentage of the line rate
Notes: 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.

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 Layer-1
for the selected port, expressed in Mbps.
L2 Rate (Mbps) The rate at which incoming traffic is currently circulating at Layer-2
for the selected port. Expressed in Mbps.

6.5 Setting Up Port PHY Parameters

You can view both SFP and copper ports, and set up the PHY parameters for each port. The
PHY parameters are used to set the abilities that are advertised to the link partner.
▶ To view PHY parameters
1. Access the page Port ▶ PHY.

A list of PHY configuration and status for all ports is displayed.
Port Configuration (Port ▶ PHY)

Status The 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 port’s PHY parameters
1. Access the page Port ▶ PHY.

A list of PHY configuration and status values for all ports is displayed.
Note: You can only set up port PHY for the RJ45 ports.
3. Define the 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:
10 Mbps Half
100 Mbps Half
1 Gbps Half
10 Gbps Half
10 Mbps Full
100 Mbps Full
1 Gbps Full
10 Gbps Full
Pause Symmetric (able to receive and transmit pause frames)
Pause Asymmetric (able to either receive or transmit pause
frames)
Note: Unsupported options, if any, are disabled.
Link Partner Ability The abilities of the link partner

Possible options include:
10 Mbps Half
100 Mbps Half
1 Gbps Half
10 Gbps Half
10 Mbps Full
100 Mbps Full
1 Gbps Full
10 Gbps Full
Pause Symmetric (can receive and transmit pause frames)
Pause Asymmetric (can either receive or transmit pause frames)
Note: Unsupported options, if any, are disabled.
State The state field corresponds to ifMauAutoNegConfig and

ifMauAutoNegRemoteSignaling from RFC-3636.
The disabled state indicates that auto-negotiation is not supported
by the media or is disabled by the configuration. Possible values are:
Other
Configuring
Complete

Disabled
Parallel Detect Fail

6.6 Viewing SFP Information

Use this page to view both summary and detailed information about all currently-detected
SFPs.
▶ To view a configuration summary of all SFPs
1. Access the page Port ▶ SFP ▶ Configuration.

A listing all SFPs currently detected by the unit is displayed, along with their status and
speed.
▶ To view detailed configuration information for a specific SFP

A listing all SFPs currently detected by the unit is displayed, along with their status and
speed.
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 ▶ Configuration)

Present An indication of whether or not the SFP is present. Available options

are:
Green: The SFP is present

Red: The SFP is not present
Connector The physical connector the port is using.
Part Number The manufacturer’s part number or product name.
Serial Number The manufacturer’s 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.
▶ To view a status summary of all SFPs
1. Access the page Port ▶ SFP ▶ Status.

Summary information for all SFPs currently detected by the unit is displayed.

▶ To view detailed status information for a specific SFP
1. Access the page Port ▶ SFP ▶ Status.

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. The level of detail provided
may vary, depending on the SFP's state.
SFP Status Information (Port ▶ SFP ▶ Status ▶ [connector])

SFP or Fiber 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 manufacturer’s 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 . Two values are
displayed:
Actual: The speed at which this SFP is currently operating

Detected: The speed, as obtained by SFP detection
Monitoring Information
Temperature Transceiver temperature, measured internally.

Temperature accuracy is manufacturer-specific, but must be better
than 3 degrees 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 3 dB 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 3 dB 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
manufacturer’s specified wavelength, accuracy should be better
than 3 dB 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 ▶ Status ▶ [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, expressed in
microamperes
Low Alarm: Low-laser bias current alarm for the TX, expressed in
microamperes
High Warning: High-laser bias current warning for the TX,
expressed in microamperes
Low Warning: Low-laser bias current warning for the TX,
expressed in microamperes
Tx Power High Alarm: High-output power alarm for the TX

(~ -40 dBm to +8.2 dBm)
Low Alarm: Low-output power alarm for the TX
(~ -40 dBm to +8.2 dBm)
High Warning: High-output power warning for the TX
(~ -40 dBm to +8.2 dBm)
Low Warning: Low-output power warning for the TX
(~ -40 dBm to +8.2 dBm)
Rx Power High Alarm: High-input power alarm for the RX

(~ -40 dBm to +8.2 dBm)
Low Alarm: Low-input power alarm for the RX
(~ -40 dBm to +8.2 dBm)
High Warning: High-input power warning for the RX
(~ -40 dBm to +8.2 dBm)
Low Warning: Low-input power warning for the RX
(~ -40 dBm to +8.2 dBm)

SFP Memory Information (Port ▶ SFP ▶ Status ▶ [connector])

SFP Memory (Location: A0h)
The SFP memory field provides a hexadecimal dump of the digital diagnostic memory
map at address A0h. Refer to SFF-8472 for detailed descriptions of the individual data
fields.
Monitor Memory (Location: A2h)
The Monitor memory field provides a hexadecimal dump of the digital diagnostic
memory map at address A2h. Refer to SFF-8472 for detailed descriptions of the
individual data fields.
Copper PHY Config Memory (Location: ACh or A2h)
The Copper PHY config memory field provides a hexadecimal dump of the PHY memory
map at address ACh. Refer to the copper SFP vendor's specification for detailed
descriptions of the individual data fields.

6.7 SFP Configuration

▶ To change speed manually
2. Select the desired connector to obtain the detailed dialog: SFP-X Configuration.
3. Clear the Automatic check box if selected. (This option is selected by default.)
The three speed options appear.
4. Select the appropriate option.
5. Click Apply.
Port ▶ SFP ▶ Configuration

Present An indication of whether or not the SFP is present. Available options

are:
Green: The SFP is present

Red: The SFP is not present
Connector The physical connector used by the port
Speed The speed supported by the SFP
Automatic: Allows the SFP port to operate at the best speed

determined via auto-detection. Clear this box to manually select
a speed for this SFP.
100 Mbps/1 Gbps/10 Gbps: Forces the SFP port to operate at

the selected speed.
Note: Speed overriding can only be used for optical SFP

transceivers. The available override speeds are dependent on the
model.
For the GX Performance Element:
SFP optical: 100Mbits/s is not supported at all.

SFP copper: supported on all SFP ports; however, 10 Mbits/s
speed is not supported.

6.8 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)

Connector The physical connector the port is using
Channel A The results for each pair in a four-pair cable are presented in these
four columns.
Channel B
Channel C
Channel D
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/100 Mbps. 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
125 ms, it reports the test result as FAIL.
Impedance Mismatch Status: Whenever the effective
impedance is not 100 Ohms. The possible causes are:
Different quality cables are connecting through a cable
extender.
A cable with the wrong quality is being used.
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.

7. Managing Traffic
This chapter describes how to create and manage Ethernet services; it contains the following
sections:
7.1 Understanding the Creation of Ethernet Services 150
7.2 Defining Filters 152
7.3 Setting Up Ethernet Services 165
7.4 Using Layer-2 Protocol Tunneling 199
7.5 Monitoring Traffic 207

7.1 Understanding the Creation of Ethernet Services

This section presents the creation of E-Line, E-LAN and E-Tree services as described in
MEF 6.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 237

Monitoring Network Performance with Service OAM on page 250
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-VLAN, S-VLAN 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 MEF 10.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.

7.2 Defining Filters

You can set up a specific filter (Layer-2, IPv4 or IPv6) for use with loopbacks or traffic policies.
By using such a filter, 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 or IPv6 Header settings, ICMP settings and VLAN settings. You can also use
the preconfigured Layer-2, IPv4 or IPv6 filters.
Note: The maximum number of traffic policies using a specific filter (Layer-2,
IPv4 or IPv6) is limited by the type of unit you use. Refer to your unit’s datasheet
for the maximum number of specific filters possible for traffic policies.
7.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.
The total number of filters found in the system is given in the lower-left corner of the
page, as well as the index values of the items currently displayed on-screen (for
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 379). 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.
Notes: When making changes to any parameter of an in-use filter (filter

associated to an active policy or an active OAM loopback), the following
message will be displayed "Configuration changes are service affecting. Are
you sure you want to proceed?". Click OK to proceed with your changes or
Cancel to go back to the previous screen.
For all fields, check the box to enable the field. If the check box is not selected,

the value will be ignored.
You can specify several VLAN fields for the first VLAN (VLAN 1) as well as for
the second level VLAN (VLAN in VLAN).
Layer-2 Filters (Traffic ▶ Filters ▶ L2 Filters)

L2 Filter Name / A unique name to identify the filter

Filter Name
Ethernet Header Settings
MAC Destination / The destination MAC address and mask. Only the bits specified by
Mask 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)
SNMP (0x814C)
WCP (0x80FF)
IPv6 (0x86DD)
MAC Control (0x8808)
MAC Protocol (0x22E2)
PPP (0x880B)
MPLS (0x8847)
MPLS Multicast (0x8848)
PPPOE Discovery (0x8863)
PPPOE Session (0x8864)
VLAN (0x8100)
VLAN (0x88A8)
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 the inner tag).

S-VLAN: Service VLAN (typically the outer tag).
T-VLAN: Tunnel VLAN (either the inner or outer tag).
Any: Choose this option so filters will allow frames with C-VLAN,
S-VLAN or T-VLAN tags through.
Note: Access the page System ► Configuration ► Mode to set the

value for the S-VLAN Ethertype.
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. The valid operator types are:
Greater than
Less than
Equal to
Note: For this parameter to function as expected, you must also

enable the Ethertype parameter and set its value to "IPv4 (0x800)
or IPv6 (0x86dd)".
7.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 on
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 379). For traffic policies, the
changes you make are applied immediately when you click Add.
click Add.

You can specify several VLAN fields for the first VLAN (VLAN 1), as well as for
the second-level VLAN (VLAN in VLAN).
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 mask
are used; the other bits are ignored.
IP Source
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 the
Mask 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 that you 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 5–15.
Protocol Either select a protocol from the drop-down list or enter a port
number (decimal value) manually.
Common protocols:
TCP (6): Used by HTTP, FTP, Telnet and SMTP.

UDP (17): Used by DNS, SNMP and RIP.
ICMP (1): Used by Ping.
Available protocols [protocol name (port number)]:
ICMP (1)
IGMP (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)
Custom
UDP/TCP Port Settings
Source Port Enable this box to specify the UDP or TCP port number (or range of
port numbers) to be used by the IPv4 source port field.
Make a selection from the drop-down list, depending on how many

source ports you want to specify:
Equal to: Enter a single port number in the adjacent field

Range: Enter the start and end values for the range of
consecutive port numbers in the adjacent fields
This setting is valid only when the Protocol is set to TCP (6) or UDP
(17).
Destination Port Enable this box to specify the UDP or TCP port number (or range of
port numbers) to be used by the IPv4 destination port field.
Make a selection from the drop-down list, depending on how many
destination ports you want to specify:
Equal to: Enter a single port number in the adjacent field

Range: Enter the start and end values for the range of
consecutive port numbers in the adjacent 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 the ICMP code
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.


Any: Choose this option so filters will allow frames with C-VLAN,
S-VLAN or T-VLAN tags through.
Note: Access the page System ► Configuration ► Mode to set the

value for the S-VLAN Ethertype.
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

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. The valid operator types are:
Greater than
Less than
Equal to
7.2.3 Configuring an IPv6 Filter

▶ To set up an IPv6 filter
1. Access the page Traffic ▶ Filters ▶ IPv6 Filters.

A summary of all IPv6 filters that have been set up is displayed. For more information on
2. Click the Add button to add a new filter, or click the Filter Name of an existing IPv6
filter to edit its settings.
Note: When you edit an existing IPv6 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 IPv6 filter, you need to disable the loopback and re-enable it
(See Setting Up and Enabling Loopbacks on page 379). For traffic policies, the
changes you make are applied immediately when you click Add.
click Add.

You can specify several VLAN fields for the first VLAN (VLAN 1), as well as for
the second-level VLAN (VLAN in VLAN).

IPv6 Filters (Traffic ▶ Filters ▶ IPv6 Filters)

IPv6 Filter Name A unique name used to identify the filter

Filter Name
IPv6 Header Settings
IPv6 Source / Prefix The source address and prefix. Only the bits specified
by the prefix are used; the other bits are ignored.
IPv6 Source
Note: Filtering source or destination IP addresses that
are assigned by Dynamic Host Control Protocol version 6
(DHCPv6) 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.
IPv6 Destination / Prefix The destination address and prefix. Only the bits
specified by the prefix are used; the other bits are
IPv6 Destination
ignored.
Note: Filtering source or destination IP addresses that
are assigned by Dynamic Host Control Protocol version 6
(DHCPv6) 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.
Hop Limit The current value of the hop limit

Valid values range from 0 to 255.
Note: This field is the IPv6 equivalent of the IPv4 field
"Time to Live" (TTL)".
Next Header Select this box to filter on packets that contain a Next
Headerfield that references the protocol indicated in the
drop-down list to the right (this field is the IPv6
equivalent of the IPv4 field "Protocol").
Notes: The decimal value indicated to the right of the
dropdown list is refreshed automatically after you make
your selection. As an alternative, you can enter the value
associated with the protocol instead of selecting it from
the list.
Because the frame headers fields extraction depth is
limited to the first 96 bytes of a frame, any fields of an
IPv6 frame that are beyond the first 96 bytes will not be
extracted. Therefore, they will not be found in the
classification key used against an IPv6 filter."
Also, the following IPv6 Next Headers identifying

Extension Headers will be skipped. Therefore, they will

not be found in the classification key used against an
IPv6 filter:
Fragment header (44)
Destination options (60)
Routing header (43)
Fragment header (44)
Authentication header (51)
Mobility Header (135)
UDP/TCP Port Settings
Source Port Enable this box to specify the UDP or TCP port number
(or range of port numbers) to be used by the IPv6
destination port field.
Make a selection from the drop-down list, depending on
how many destination ports you want to specify:
Equal to: Enter a single port number in the adjacent

field
Range: Enter the start and end values for the range
of consecutive port numbers in the adjacent fields
This setting is valid only when the Next Header is set to

TCP (6) or UDP (17).
Destination Port Enable this box to specify the UDP or TCP port number
(or range of port numbers) to be used by the IPv6
destination port field.
Make a selection from the drop-down list, depending on
how many destination ports you want to specify:
Equal to: Enter a single port number in the adjacent

field
Range: Enter the start and end values for the range
of consecutive port numbers in the adjacent fields
This setting is valid only when the Next Header is set to

TCP (6) or UDP (17).
ICMPv Settings
ICMPv6 Type Enables the use of ICMPv6 type. You must specify the
ICMPv6 message type to be matched by this filter.
Note: These settings are only valid when the "Next

Header" parameter is set to ICMPv6 (58).

Some well-known ICMPv6 types are:
Echo Request (128)

Echo Reply (129)
Destination Unreachable (1)
Redirect (137)
Neighbor Solicitation (135)
Neighbor Advertisement (136)
Other ICMPv6 Codes: See www.iana.org/
ICMPv6 Code Enables the use of the ICMPv6 code
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.

T-VLAN: Tunnel VLAN (either the inner or outer
tag).
Any: Choose this option so filters will allow frames
with C-VLAN, S-VLAN or T-VLAN tags through.
Note: Access the page System ► Configuration ►

Mode to set the value for the S-VLAN Ethertype.
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 Enable this box to specify the 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

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
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).
Traffic Class
DSCP/IP Precedence The DSCP/IP precedence operator. The valid operator

types are:
Greater than
Less than
Equal to

7.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 152.
VID Sets. See Setting Up VID Sets on page 166.
2. Define Service Attributes:
Define bandwidth profiles. See Setting Up Bandwidth Regulators on page 170.
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 173.
Define bandwidth regulator sets. See Setting Up Bandwidth Regulator Sets on page
172.
3. Create the Service (See Setting Up Traffic Policies on page 176):
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
To view a summary of the policy configurations, access the page Traffic ▶ Policies.

7.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, Traffic-4, Traffic-5, Traffic-6, Traffic-7
and Traffic-8) to classify the incoming traffic before sending it to the service creation
function.
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 165).
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 102.
Viewing VID Sets

▶ To view all current VID sets
1. Access the page Traffic ▶ VLAN ▶ VID Sets.

The VID sets 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 VID sets in the bottom half of the
page.
3. To filter the VID sets for a given policy list results on the name, type, state, policy or size,
use the VLAN Type 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 VID Set page appears.

3. Complete or update the required fields, then click Apply.
Note: When changing VIDs from an in-use VID set (VID set associated to an
active policy), the following message will be displayed "Configuration changes
are service affecting. Are you sure you want to proceed?". Click OK to proceed
with your changes or Cancel to go back to the previous screen.
Adding or Editing VID Sets (Traffic ▶ VLAN ▶ VID Sets)

Name The name to assign to the policy list
Policy List Assigned when the VID set is created, the policy list indicates the traffic
policy to which the VID set applies. The value here is the policy list on
which the VID set will be active.
VLAN Level 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 VID set.
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 VID set.
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 0–4095. For
untagged frames, assign VID 0.
Outer VLAN
VLAN Type The VLAN Ethertype for the outer VLAN (when dual VLAN is used)
This field is only applicable if the VLAN Level for this traffic policy is
set to Inner in the Traffic ▶ Configuration page.
VID Specify a VID for the outer VLAN.

This field is only applicable if the VLAN Level 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 VLAN IDs 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, the VID set's name appears
here
7.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 165).
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.
Range: 0 to maximum port speed (steps of 125 kbps)
Maximum Committed The maximum CIR, expressed in kbps, that the regulator can
Information Rate achieve by using the shared tokens from its envelope
CIR Max Range: CIR to maximum port speed (steps of 125 kbps)
Committed Burst Size The maximum number of kibibytes available for a burst of frames
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 KiB to 2015 KiB (steps of 1 KiB) (1024 bytes)
Minimum: 1 KiB (steps of 1 KiB) (1024 bytes)
Note: 1 KiB of CBS is required for each 500 Mbps of CIR Max. For
example, if the CIR Max is set to 1 Gbps, the minimum CBS value is 2
KiB.
Maximum: 2015 KiB (steps of 1 KiB) (1024 bytes)
Excess Information The average rate up to which excess service frames are delivered
Rate by the bandwidth regulator.
EIR EIR-conformant frames are colored yellow.
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)
Maximum Excess The maximum EIR, expressed in kbps, that the regulator can
Information Rate achieve by using the shared tokens from its envelope
EIR Max Range: EIR to maximum port speed (steps of 125 kbps)
Excess Burst Size The maximum number of kibibytes available for a burst of frames
sent at the port's speed that remain EIR-conformant.
EBS
Note: Burst size must be greater than the port's MTU.
Range: 1 KiB to 2015 kB (steps of 1 KiB) (1024 bytes)
Minimum: 1 KiB (steps of 1 KiB) (1024 bytes)
Note: 1 KiB of EBS is required for each 500 Mbps of EIR Max. For

example, if the EIR Max is set to 1 Gbps, the minimum EBS value is 2
KiB.
Maximum: 2015 KiB (steps of 1 KiB)
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 drop-down list to indicate how regulator
processes yellow traffic via coupling flag:
False: Yellow data is limited according to the EIR.

True: Yellow data is limited according to a combination of the
CIR and the EIR.
7.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 or in the IPv6 Traffic Class byte.
DSCP: DSCP bits in the IPv4 ToS byte or in the IPv6 Traffic Class 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
165).
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 on

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.
7.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.

IP Precedence: IP precedence bits in the IPv4 ToS byte or in the IPv6 Traffic Class byte.
DSCP: DSCP bits in the IPv4 ToS byte or in the IPv6 Traffic Class 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 165.
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.
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 enabled 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:

yellow.
The pre-marking color is yellow, and no bandwidth regulator is
The frame has passed through a color-aware bandwidth policer
and has been marked as yellow (due to the depletion of its CIR
bucket).
7.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 unit’s 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 port’s CoS-to-PCP mapping details are displayed.
3. Use the information in the table below to configure the port’s 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 enabled 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:

green.
The pre-marking color is green and no bandwidth regulator is
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:

yellow.
The pre-marking color is yellow and no bandwidth regulator is
The frame has passed through a color-aware bandwidth policer
and has been marked as yellow due to the depletion of its CIR
bucket.
7.3.6 Setting Up Traffic Policies

Once you have set up the filters, bandwidth regulators, CoS profiles, queues, envelopes and
bandwidth regulator sets, you are ready to assign them to a traffic policy so they can become
a service.

▶ To set up a traffic policy
1. Access the page Traffic ▶ Policies ▶ Configuration.

The Policy Lists page opens. The configuration for the selected traffic flow are
displayed.
Note: Users can click on the arrow buttons (Next and Previous), located on
either side of the Apply or Rest buttons, to sort through policies.
2. Select the appropriate traffic flow from the Policy Lists frame by clicking its name.
The configuration information is refreshed onscreen. The details for Traffic-1 pertain to
Port-1; the details for Traffic- n pertain to Port- n .
3. Apply filter to search through the list.
4. Click a policy index number from the Policy Configuration – Traffic-n frame.
The Traffic-n [n-x] Policy Configuration page opens.
5. Use the information in the table Policy Configuration (Traffic ▶ Policies ▶ Configuration)
on page 179 and the steps below to configure the traffic policy, then click Apply.
Notes: The fields available for configuration vary, depending on the Encapsulation and
the PCP action you select.
When making changes to any parameter of an active policy, the following message will
be displayed "Configuration changes are service affecting. Are you sure you want to
proceed?". Click OK to proceed with your changes or Cancel to go back to the previous
screen.

Traffic ▶ Policies ▶ Configuration
a. 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.
b. Select the Filter type and 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, IPv4 or IPv6) or a
specific VID set is limited by the type of unit you use. Refer to your unit’s
datasheet for the maximum number of specific filters possible for traffic
policies.
c. Select the EVC mapping encapsulation option and the required EVC mapping
parameters. Refer to EVC Encapsulation Options on page 183.
d. Select the PCP action for CoS mapping to perform if required. Refer to PCP Action
Options on page 184.

e. 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.
f. If you selected the PCP action Direct, complete the Direct mapping parameters.
g. Enable the Monitoring port, if required, then choose the port to which traffic is
forwarded for monitoring from the drop-down list.
Note: Users are limited by 2000 enabled policies for shared traffic-5 and traffic-
6.
Policy Configuration (Traffic ▶ Policies ▶ Configuration)

Enable Policy Select this box to activate the policy.
Outgoing Port The egress port assigned to this policy.
Queuing Profile A drop-down list with options for the queuing profile associated
with this outgoing port. By default, default queuing-profile is
selected.
Filter Type The filter type (Layer-2 filter, IPv4 filter, IPv6 filter or VID set ) used
to classify traffic.
Filter The name of the filter. You must select a filter name from the drop-
down list.
Note: The catch-all filter 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.
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 VLAN tags (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 (or 0x9100)
T-VLAN: 0x9100 (or 0x88A8)
Note: The values assigned to the S-VLAN and T-VLAN Ethertypes

can vary, depending on the S-VLAN Ethertype value selected in the
page System ► Configuration ► Mode. For details, see
"Configuring General System Settings" on page 77.
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.
IP Precedence: IP precedence bits in the IPv4 ToS byte or in the
IPv6 Traffic Class byte.
DSCP: DSCP bits in the IPv4 ToS byte or in the IPv6 Traffic Class
byte.
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 Map
Regulation 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 not
match the first and second traffic mapping choices.
PCP

Outgoing Port Options

The GX Performance Element offers flexibility with regards to how port combinations are
configured in its traffic policies; however, not all port combinations are possible.
You can configure the unit to forward traffic between NNI ports.
You can configure the unit to forward traffic from a UNI port to an NNI port.
You can configure the unit to forward traffic from an NNI port to a UNI port.
You cannot configure the unit to forward traffic between UNI ports.
For more information regarding the specifications of each port, refer to the GX Performance
Element Hardware Installation Guide.
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 want 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 184.

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 184.
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.
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

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 Optional Optional
Viewing a Summary of the Policy Configurations

Use this page to view how the unit's traffic policies have been configured.
Filters based on VID sets use direct access to identify the corresponding policy for an
incoming frame. Each frame’s VLAN ID is analyzed and the value of the VLAN ID is used to
directly access the appropriate policy to apply.

▶ To view a summary of the policy configurations
1. Access the page Traffic ▶ Policies ▶ Configuration.

A listing of all policies associated with the unit is displayed.
The total number of traffic policies found in the system is given in the lower-left corner
of the page, as well as the index values of the items currently displayed on-screen (for
2. (Optional) Click the name in the Policy Lists to view the summary of the policy
configurations of a particular port.
3. (Optional) Select a filter, using the drop- down menu, and enter a corresponding
keyword in the text field to search through policy list.
Policy (Traffic ▶ Policies ▶ Configuration)

Policy List
Name Name of the traffic policy.
Incoming Port Name of the port of the traffic policies.
Number of Policies Number of policies.
Policy Configuration
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.
Type The filter type (L2, IPv4, IPv6 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.
Outgoing Port The name of the outgoing port to which each policy is mapped.
▶ To view a summary of the policy statistics
1. Access the page Traffic ▶ Policies ▶ Statistics.

A listing of all policy statistics associated with the unit is displayed.
The total number of traffic policies found in the system is given in the lower-left corner
of the page, as well as the index values of the items currently displayed on-screen (for

2. (Optional) Click the name in the Policy Lists to view the summary of the policy
statistics of a particular port.
3. (Optional) Select a filter, using the drop- down menu, and enter a corresponding
keyword in the text field to search through policy list
Policy (Traffic ▶ Policies ▶ Statistics)

Policy List
Name Name of the traffic policy.
Incoming Port Name of the port of the traffic policies.
Number of Policies Number of policies.
Policy Statistics
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.
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 invalid 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.
7.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 The 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
regulator, then dropped.
Yellow Packets The total number of yellow frames handled by this regulator since
its creation
regulator, then dropped.
Yellow L1 Rate The rate of yellow Layer-1 data, expressed in Mbps

(Mbps)
Yellow L2 Rate The rate of yellow Layer-2 data, expressed in Mbps

(Mbps)
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
7.3.8 Setting Up Bandwidth Policer Envelopes

Use the Traffic ▶ Regulators ▶ Envelope page to set up a bandwidth regulator envelope,
which enables you to share bandwidth between multiple services.
Note: You must create and properly configure the bandwidth regulators before
adding them to an envelope. This includes associating each of them with a traffic
policy in the Traffic ▶ Policies page.

▶ To configure a bandwidth regulator envelope
1. Access the page Traffic ▶ Regulators ▶ Envelope.

The Regulator Envelope Configuration summary page opens. The details related to all
envelopes that have been created are displayed.
Note: No envelopes are defined by default.
2. Click Add to create a new envelope or click the name of a bandwidth regulator envelope
to edit its details.
The screen refreshes as the Regulator Envelope Configuration details page opens. All
available regulators are listed on the left side of the page.
Note: Editing an existing envelope may be traffic affecting.
3. Use the information in the table below to configure the bandwidth regulator envelope,
then click Apply.
Bandwidth Regulator Statistics (Traffic ▶ Regulators ▶ Envelope)

Name The name assigned to the regulator envelope. Acceptable values

are between 1 and 31 characters in length.
Note: It is recommended to provide an envelope name that can be
used to identify the service.
Coupling Flag Use this box to indicate how the regulators in this envelope process
yellow traffic:
Checked: Yellow data is limited according to a combination of

the Committed Information Rate and the Excess Information
Rate.
Unchecked: Yellow data is limited according to the Excess
Information Rate. This is the default value.
All the regulators you add to the envelope must share the same
value for the coupling flag (i.e., all must either use it or not use it), as
defined by the following rules:
If the envelope's coupling flag is enabled, the coupling flag of all

regulators in the envelope are automatically disabled.
If the envelope's coupling flag is disabled, the coupling flag of
all regulators in the envelope are automatically set to the same
value as the envelope's highest-ranking regulator.
Available Regulators Select a regulator from the list, then click the button to add it

to the envelope's ranking list on the right side of the page.
To remove a regulator from the ranking list, click the button.

Notes: A bandwidth regulator cannot be used in more than one
envelope. All regulators appear in the list of available regulators,
even those that have already been assigned to another envelope.
You must add at least two regulators to the ranking list before
saving the envelope. The maximum number of regulators you can
assign to an envelope is eight.
Ranking List The bandwidth regulators you have added to this envelope appear
here.
Use the and buttons to rearrange the regulators in the

ranking list once they have been added.
▶ To delete a bandwidth regulator envelope

1. Access the page Traffic ▶ Regulators ▶ Envelope.
The Regulator Envelope Configuration summary page opens. The details related to all
envelopes that have been created are displayed.
2. Click the name of the bandwidth regulator envelope you want to delete.
The screen refreshes as the Regulator Envelope Configuration details page opens.
3. Click Delete.
The envelope is removed from the system immediately and you return to the Regulator
Envelope Configuration summary page. You are not prompted to confirm your actions.
7.3.9 Understanding BLUE

The BLUE algorithm is used by the shapers for queue management.
BLUE is an enhancement to the RED congestion avoidance algorithm; it offers the same
benefits as RED and provides similar queue monitoring. The main difference between BLUE
and RED is that BLUE also uses the queue packet loss and utilization history. Its use of a drop
probability is more friendly with TCP global synchronization and reduces the number of TCP
retransmissions.
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 expressed 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.
7.3.10 Configuring Queues

The GX Performance Element has eight dedicated queues per port, as listed in the table
below. When in LAG mode, the queues dedicated to the LAG’s ports are unavailable because
the LAG’s own queues are used instead. The LAG-1-PORT-1-RPTQ-X is available on Ports 1
and 2. Both these have eight dedicated queues.
Note:
1 Gbps Ports Eight dedicated queues per port:
Port-1-1, Port-1-2, ... Port-1-8

LAG-1-PORT-1-RPTQ-1, LAG-1-PORT-1-RPTQ-2, … LAG-1-
PORT-1-RPTQ-8
Port-2-1, Port-2-2, ... Port-2-8

LAG-1-PORT-2-RPTQ-1, LAG-1-PORT-2-RPTQ-2, … LAG-1-
PORT-2-RPTQ-8
Port-3-1, Port-3-2, ... Port-3-8

Port-4-1, Port-4-2, ... Port-4-8
Port-5-1, Port-5-2, ... Port-5-8
Port-6-1, Port-6-2, ... Port-6-8
Port-7-1, Port-7-2, ... Port-7-8
Port-8-1, Port-8-2, ... Port-8-8

Each queue has a defined port and size. There are no user-assignable queues. When in LAG
mode, the queues dedicated to the LAG’s ports are unavailable because the LAG’s own
queues are used instead.
▶ To configure queues
1. Access the page Traffic ▶ Shaping ▶ Queue ▶ Configuration.

The Traffic Shaping Queue Configuration page opens. All the unit’s queues are listed
in a grid.
2. Select a queue from the list to configure by clicking it.

The queue’s details are displayed.
3. Use the information in the table below to configure the queue, then click Apply.
Queue Settings (Traffic ▶ Shaping ▶ Queue ▶ Configuration)

Outgoing Port Traffic from this queue will egress on the port specified here.
Name The name assigned to this shaper
Queue Scheduling
Priority (0 to 7) The strict scheduling priority assigned to this queue: 7 is the

highest and 0 the lowest priority.
Note: This value is provided for your convenience; however, it
cannot be modified. When several queues have the same priority,
scheduling is carried out in a round-robin fashion.
Queue Management Parameters
Maximum Queue Size The buffer's size, expressed in KiB (1024 bytes)
Acceptable values range from 16 KiB to 2044 KiB.
The Maximum Queue Size must be greater than the Yellow
Threshold value.
Yellow Threshold When the queue length reaches this threshold, tail-dropping is
performed on new packets with yellow marking.
Acceptable values range from 16 KiB to the Maximum Queue Size
value indicated above.
BLUE State Select to enable the BLUE queue management algorithm.

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.
BLUE Queue Full Once the queue fills to the specified percentage, the marking

Threshold probability will be increased. The current range is from 5 to 98. The
Blue Queue Full Threshold must be equal or greater than the Blue
Queue Empty Threshold.
BLUE Queue Empty Once the queue empties to the specified percentage, the marking
Threshold probability will be decreased. The current range is from 5 to 98. The
Blue Queue Empty Threshold must be less than the Blue Queue Full
Threshold.
BLUE Marking This value determines the minimum interval time, expressed in
Probability Freeze microseconds (in increments of 10, between two successive updates
Time of marking probability.
Maximum of 655350 µs
BLUE Marking The marking probability is incremented by this value (expressed as

Probability Increment a step percentage) in the event of a buffer overflow.
Notes: If this parameter is set to 0, the BLUE algorithm is disabled.
The percentage value you enter here is only an approximation; the

actual configured value appears to the right of this field.
Maximum of approximately 25%
BLUE Marking The marking probability is decremented by this value (expressed as

Probability 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 approximately 25%
7.3.11 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 unit’s 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.
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 unit’s queues are listed in a
grid.

2. Select the queue from the list whose statistics you wish to view by clicking it.
The queue’s details are displayed. For more information on specific parameters, refer to
the following table.
Tip: To clear the statistics in the Traffic Shaping Queue Statistics page, click the Clear
button located above the queue details.
To obtain the latest statistics from the unit, click the Refresh button located beside the
Clear button.
Select the Poll Every n 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
shaper using the CIR bucket
EIR Compliant The total number of frames that have been forwarded by this
shaper using the EIR bucket

7.3.12 Viewing Queuing Profile Details

Use this page to view the details related to the eight queuing profiles created for this unit.
Note: Queuing profiles are read-only; you cannot modify them.
▶ To view a summary of queuing profiles
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.
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.
7.3.13 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 unit’s 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 Shaper Configuration (Traffic ▶ Shaping ▶ Port ▶ Shaper)

Port The name assigned to this outgoing port
State The current state of this outgoing port: enabled or disabled
CIR (kbps) The shaping rate of outgoing frames, expressed as a multiple of 125
kbps
Range: 0 to port speed
CBS (KiB) (1024 bytes) The shaping burst of outgoing frames, expressed in kibibytes
Range: 1 KiB to 2047 KiB, when the CIR value is <= 500,000 kbps
Range: 2 KiB to 2047 KiB, when the CIR value is > 500,000 kbps
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 unit’s 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 port’s 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 outgoing frames, expressed as a multiple of 125

Information Rate kbps
(kbps)
Range: 0 to port speed
Committed Burst Size The shaping burst of outgoing frames, expressed in kilobytes with 1
(KiB) (1024 bytes) kibibyte granularity
Range: 1 KiB to 2047 KiB, when the CIR value is <= 500,000 kbps
Range: 2 KiB to 2047 KiB, when the CIR value is > 500,000 kbps
CPU Traffic Debited CPU traffic is never shaped. However, you can select this box to
from CIR have the system debit CPU traffic from the outgoing port’s CIR
bucket.
Note: If you select this box, the bucket value could become
negative.

7.4 Using Layer-2 Protocol Tunneling

You can use the Layer-2 Protocol Tunneling function to allow the client’s 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 Accedian’s 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 202.

Traffic ▶ L2PT ▶ Configuration
7.4.1 Viewing Statistics for Layer-2 Tunnel Rules

▶ To view statistics for all L2PT rules
1. Access the page Traffic ▶ L2PT ▶ Statistics.

Statistics for all rules in the system are displayed in a grid.
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 creation.
This counter is incremented under the following 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 creation.
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 creation.
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.
7.4.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 rule’s 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 L2PT rule 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 "Setting Up a Layer-2
Tunnel" 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 rule’s 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 MAC address 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 MAC addresses 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 end points 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 VLAN Ethertype 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
0–7: 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 selection in the drop-down list.
0–1: 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 5–6
and 22–88, you would specify: 3, 5:6, 22:88.
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.
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.
CoS Mapping
Mode Note: Only applies to the "Tunnel" operation mode, or to

the "Forward" operation mode when the EVC mapping
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 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: 0–7.
Note: Only applies to the "Tunnel" operation mode, or to
CFI 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.
Note: Only applies to the "Tunnel" operation mode, or to

7.5 Monitoring Traffic

This section describes how to set up the GX 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 GX Performance
Element can use up to two monitor ports. Any of the 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.8 µs at 1000 Mbps).
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
1000 Mbps 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., the 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, Traffic ▶
Filters ▶ IPv6 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 152 for more information on how to setup L2,
IPv4 IPv6, or VID Set 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 the policy
Select the appropriate Filter Type
Select the Filter you defined in the previous steps from the drop-down list
Set the Action to Permit Traffic
Enable monitoring
Set the monitor port to Monitor-1 or Monitor-2

Then, click Apply. Refer to the table Setting Up Traffic Policies on page 176 for more
information on how to set up the policy.

8. Setting Up Protection
This chapter describes how to set up protection on the unit; it contains the following sections:
8.1 Setting Up LAG Port Protection 210
8.2 Setting Up ERP Protection 215

8.1 Setting Up LAG Port 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 its assigned physical ports.
The port protection mechanism is shown below.
z
▶ To set up port protection
3. Define port protection parameters as required by your setup, then click Apply.
For more information on specific parameters, refer to the table Port Configuration and Status
(Port ▶ Configuration) on page 119.
LACP Configuration (Protection ▶ LACP ▶ Configuration)

Aggregator Name The name of the LAG group
Mode The mode of the LACP protection. 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 LACP participant sends LACPDUs to maintain the

LAG.
Timeout The time to wait before sending LACPDU

Long: The 802.1ax Long Timeout

Short: The 802.1ax 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
8.1.1 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.
8.1.2 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.
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.
8.1.3 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

LACPDU Sent
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
LACPDU Received
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 transmitted
Sent
Marker Response The number of marker response packets that were received
Received
Bad Marker Received The number of invalid marker packets that were received

8.2 Setting Up ERP Protection

Ethernet Ring Protection (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 LAG Port Protection on page
210 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 ERP instance once it has been
created. You cannot modify this value.
Note: The system supports up to eight ERP instances.
Name The name of the ERP instance
Version The version number assigned to the ERP instance once it has been
created. You cannot modify this value.
Port Configuration
LAG Port The LAG port used by this ERP instance. You must first set this LAG
port to ERP status protection mode in the page Port ▶

Configuration.
Port 0 The name of the physical port 0 (PORT-1, 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, 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 ERP instance.
Owner: This unit is the RPL Owner for this ERP instance. Only
one unit can be set to Owner for an ERP ring.
Neighbor: This unit is the RPL Neighbor for this ERP instance.
Only one unit can be set to Neighbor for an ERP ring.
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 ERP messages
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-ring’s 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 VLAN must be reserved solely for the APS protocol,
otherwise an error will be raised. Furthermore, the VLAN must not
be used for any type of customer traffic.
VID Set The list of VLAN IDs protected by this ERP instance. Only these
VLANs can be sent on this ring.
VID-List
8.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 the detailed status of a specific ERP instance
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 ERP instance. You cannot
modify this value.
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.

8.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.
8.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.
8.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.
8.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 ERP instance. You cannot
modify this value.
Node ID The MAC address of this unit
Port X (The results for each port)
Local Clear The number of the local clears performed
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.
8.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 n Seconds box and enter a value.
ERP VLAN Forwarding Table (Protection ▶ ERP ▶ VLAN fdb)

Index The unique identifier assigned to the ERP instance
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

9. Managing Virtual Connection Endpoints (VCEs)
This chapter explains how to create and manage Virtual Connection Endpoints (VCEs). VCEs
are used to define the traffic mapping on a Performance Element.
9.1 About Virtual Connection Endpoints (VCEs) 223
9.2 Setting Up Virtual Connection Endpoints (VCEs) 225
9.3 Adding Virtual Connection Endpoints (VCEs) 227

9.1 About Virtual Connection Endpoints (VCEs)

VCE is a constituent element of VCA and an abstraction of an 802.1Q VLAN bridge
component. A VCA (Virtual Connection Access) is used to connect one or more virtual
connection endpoints (VCE) together to complete the description of the end-to-end
connectivity between two ports on an Accedian Edge Element. For more information, see
section "About Virtual Connection Access (VCAs)" on page 233 in section 10.1. The VCE
manipulates only one VLAN and consists of two termination points, labelled TP-A and TP-Z.
TP-A defines the incoming port and TP-Z defines the outgoing port. Relay action and frame
type complete the definition, as shown in figure below. For more information, see Application
Note 200: Configuring SOAM with Virtual Connections.
The VCA/VCE defines traffic forwarding within an Accedian product. The connectivity is
defined from the direction of the TP-A to TP-Z endpoints on one or more VCE elements. The
end-to-end connectivity from TP-Z to TP-A is automatically inferred and symmetric with
end-to-end definition of TP-A to TP-Z, as shown below. The TP A (Termination Point) defines
the incoming port and TP Z defines the outgoing port. The Relay action and Frame Types
define the action to transform the incoming frames TP A toward the TP Z. The traffic is not
restricted to being forwarded from "TP-A" to "TP-Z", The TP A and TP Z are there only to
define the direction for the configuration.

9.1.1 Parts of a VCE

Frame types: Defines the incoming frames as: {vlan-tagged, untagged, any, and all-to-
one}.
Relay actions: Defines the action that be perform such as:
Tag (add a VLAN tag). the VLAN tag is added from TP A toward TP Z.
In the reverse direction the VLAN tag is removed for traffic coming from TP Z
toward TP A.
Untag (remove a VLAN tag), the VLAN tag is removed from TP A towards TP Z. In
the reverse direction the VLAN tag is added for traffic coming from TP Z toward TP
A.
Translate (change VLAN ID), the TP A VID is translated to TP Z VID for traffic going
from TP A toward TP Z. In the reverse direction, the TP Z VID is translated to TP A
VID for traffic going from TP Z towards TP A.
Preserve (preserve the VLAN tag), the VLAN is the same on both TP A and TP Z.

9.2 Setting Up Virtual Connection Endpoints (VCEs)

▶ To view a summary of existing VCEs
1. Access the page VCE ▶ Configuration.

A list of all existing VCEs and their current status is displayed.
Note: A type Tunnel VCE will create an implicit VCA which can be included
within another VCA. Also, a VCE with both TP A and TP Z ports configured as
external will generate an implicit VCA.
VCE Configuration and Status (VCE ▶ Configuration)

VCE Name A name that uniquely identifies the VCE on the GX

Performance Element.
TPID The TPID (Tag Protocol Identifier). Specifies the type of VLAN-
tagging used in the frames that will be handled by this VCE.
Available tag protocol options are:
0x8100: C-VLAN
0x88a8: S-VLAN
0x9100: T-VLAN
TP A The TP A is the Terminal Point interface. Can be:
Internal: Used to identify the TP as being connected to

another VCE.
External: Used to identify the TP as being connected to an
external port.
TP A VID Used to indicate the VLANIDs expected for this VCE

configuration. When Frame Type is 'all-to-one', this value is
irrelevant, and '---' is displayed.
TP Z The TP Z is the Terminal Point interface. Can be:

another VCE.
external port.
TP Z VID TP Z VID is applicable when 'vid-relay-action' is set to

'translate' or 'tag'. Only a single value for the VID may be
specified.

Component ID The ID of the Component into which the VCE will be attached.
Specifying 0 indicates that the system shall automatically
assign a component ID.
▶ To add a new VCE or edit an existing VCE
CAUTION: Before you can add a VCE to a Performance Module, you must add a
standard logical interface to it. For details, see "Configuring Logical Interfaces" on
page 25.

2. Click Add to create a new VCE or click the Name of an existing VCE to edit its settings.
See "Adding Virtual Connection Endpoints (VCEs)" on the next page.

9.3 Adding Virtual Connection Endpoints (VCEs)

Depending on the use case, a VCE element has a “component type” attribute: Customer (C-
VLAN), Operator (S-VLAN) or Tunnel (S-VLAN):
A Tunnel VCE is used for trunking use cases (Access Provider).

An Operator VCE is used to tag the data frames in the operator's network.
A Customer VCE is used to handle customer (tagged or untagged) traffic (usually at UNI
and at VUNI)
▶ To add a new VCE or edit an existing VCE

2. Click Add to create a new VCE or click the Name of an existing VCE to edit its settings.
Note: A type Tunnel VCE will create an implicit VCA which can be included
within another VCA. Also, a VCE with both TP A and TP Z ports configured as
external will generate an implicit VCA.
VCE Configuration and Status (VCE ▶ Configuration)

VCE Name A name that uniquely identifies the VCE on the GX

Performance Element.
Type Type indicates which type of VCE is being created. The default
is Customer. The available options are:
Customer
Operator
Tunnel
TPID The TPID (Tag Protocol Identifier). Specifies the type of VLAN-
tagging used in the frames that will be handled by this VCE.
Available tag protocol options are:
0x8100: C-VLAN
0x88a8: S-VLAN
0x9100:T-VLAN
Component ID The ID of the Component into which the VCE will be attached.
Specifying 0 indicates that the system shall automatically
assign a component ID.

Frame Type Specifies the type of frames that will be selected for handling
by this VCE.
all-to-one: Multiple frames that are associated with a

single VLAN. Used for port-based service interface
definition.
untagged: Frames that are not associated with a VLAN.
vlan-tagged: Frames that are associated with a VLAN.
any: Frames that are associated with any VLAN.
Relay Action Select the action to be performed on incoming frames.
tag: Add a VLAN tag to untagged frames.

untag: Remove a VLAN tag from tagged frames.
preserve: Keep the VLAN tag of tagged frames.
translate: Change the VLAN ID of tagged frames.
A VCE can only perform one action. If you need to perform a

series of actions, you must define multiple VCEs.
TP A Use this parameter to configure the incoming Terminal Point

(TP). The TP A is a virtual UNI (User Network Interface) port. It
can be either:
External: is used to identify the TP as being connected to

an external port.
Internal: is used to identify the TP as being connected to
another VCE.
TP Z Use this parameter to configure the outgoing Terminal Point

(TP). The TP Z is always a virtual NNI (Network Network
Interface) port. It can be either:
External: is used to identify the TP as being connected to

an external port.
Internal: is used to identify the TP as being connected to
another VCE.
TP A Port The TP A Port defines the Ingress port of VCE.
TP Z Port The TP Z Port defines the Egress port of VCE.
TP A VID The TP A VID is used to assign a VID to frames. When Frame

Type is configured as 'untagged' the option is unavailable. A
single VLAN-ID chosen from the range 1..4094 is assigned to
this parameter. If the Frame Type is Customer, multiple

VLANIDs may be specified in the following format: [-],[-] ...(e.g.

1,2,100-200 will include VIDs 1,2,100,101,102,103...200).
TP Z VID The TP Z VID is applicable when 'vid-relay-action' is set to

'translate' or 'tag'. Only a single value for the VID may be
specified.
CoS Mapping:
TP A PCP Mapping The TP A PCP Mapping is the ingress CoS profile name with
the type PCP.
TP Z PCP Mapping The TP Z PCP Mapping is the egress CoS profile name with
the type PCP.

9.3.1 VCE Examples

This section provides examples of how to set up the VCEs required for two different types of
sessions on the unit:
VCE Settings Example #1: C-VLAN Bridge

VCE Name C_VID_1000
Type Customer
TPID 0x8100
Frame type Vlan-tagged
VID Relay Action Preserve
TP A PORT-1
TP A VID 1000
TP A PCP Mapping
TP Z PORT-2
TP Z VID 1000
TP Z PCP Mapping
Component ID 1

VCE Settings Example #2: Tagged Service Interface

VCE Name C_VID_1000
Type Customer
TPID 0x8100
Frame Type vlan-tagged
VID Relay Action Preserve
TP A PORT-1
TP A VID 1000
TP A PCP Mapping
TP Z Internal
TP Z VID
TP Z PCP Mapping
ComponentID 1
VCE Name S_VID_5
Type Operator
TPID 0x88A8
Frame Type all-to-one
VID Relay Action Tag
TP A Internal
TP A VID
TP A PCP Mapping
TP Z PORT-2
TP Z VID 5
TP Z PCP Mapping
Component ID 2

10. Managing Virtual Connection Access (VCAs)
This chapter explains how to create and manage Virtual Connection Access (VCAs).
10.1 About Virtual Connection Access (VCAs) 233
10.2 Setting Up Virtual Connection Access (VCAs) 235

10.1 About Virtual Connection Access (VCAs)

VCA is used to connect one or more virtual connection endpoints (VCE) together to complete
the description of the end-to-end connectivity between two ports on an Accedian Edge
Element, and describes a customer's traffic flow access to the service provider's network
through the performance element.
A VCA element is formed by an ordered list of one or more individual Virtual Connection
Endpoints (VCE) elements in order to form an external port-to-external port definition for the
Virtual Connection Access. The Virtual Connection defines the traffic path to be used by UP
MEP, DOWN MEP and MIP.
The connectivity is defined from the direction of the TP-A to TP-Z endpoints on one or more
VCE elements. The end-to-end connectivity from TP-Z to TP-A is automatically inferred and
symmetric with end-to-end definition of TP-A to TP-Z, as shown below.
10.1.1 CFM Using Model

Depending on the use case, a VCE element has a type attribute: Customer (C-VLAN),
Operator (S-VLAN) or Tunnel (T-VLAN):
A Customer VCE is used to handle customer (tagged or untagged) traffic (usually at UNI
and at VUNI).
An Operator VCE is used to tag the data frames in the operator's network.
A Tunnel VCE is used for trunking use cases (Access Provider).

The VCE type is used to determine how to construct the bridge component and component
ID required for CFM.
A Termination Point (TP) is a logical point of attachment to either a Physical (or LAG) port,
referred to as an external TP, or to another VCE, referred to as an internal TP.
A VCA

10.2 Setting Up Virtual Connection Access (VCAs)

▶ To view a summary of existing VCAs
1. Access the page VCA ▶ Configuration.

A list of all existing VCAs and their current status is displayed.
VCA Configuration and Summary (VCA ▶ Configuration)

VCA Name A name that uniquely identifies the VCA on the unit.
This name is propagated to the unit along with all the
connectivity information for VCA.
TP A Port The TP A is the Terminal Point interface.

It can be either:

another VC.
external port.
TP Z Port The TP Z is the Terminal Point interface.

It can be either:

another VCE, in the case of an implicit VCA with VCE type
tunnel.
External: Used to identify the TP as being connected to
another VC.
VC list The VC list is a comma separated list of VCEs (type Operator

or Customer) or an implicit VCA containing a VCE tunnel
instance referenced by name.
▶ To add a new VCA
1. Access the page VCA ▶ Configuration.

A list of all existing VCAs and their current status is displayed.
2. Click Add to create a new VCA or click the Name of an existing VCA to edit its settings.
3. If adding a new VCA, type the new VCA name in the VCA Name field.

4. Add VCs from the list of available VCs.
5. Press Apply.
VCA Configuration and Summary (VCA ▶ Configuration)

VCA Name A name that uniquely identifies the VCA on the unit.
Available VC Allows you to select VCs from a list of available VCs that
you want to add to the VC list.
VC list The VC list is a comma separated list of VCEs (type

Operator or Customer) or an implicit VCA containing a VCE
tunnel instance referenced by name.
▶ To add VCs to or from the VC list
1. To add VCs, select the desired VCs from the Available VC list and use the double arrow
to move them to the right into the VC list.
Those selected will move to the VC list.
▶ To remove VCs from the VC list
1. To remove VCs, select the desired VCs from the VC list and use the double arrow to
move them to the left.
Those selected will be removed from the VC list.
▶ To reorder VCs in the VC list

1. Select the desired VC and use the + or - buttons to move up or down respectively.
The selected VC will be reordered in the list.
Note: The order of the VCs shall be aligned such that TP-A of the first VC is
mapped to an external port and TP-Z of the last VC is also mapped to an
external port.

11. 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:
11.1 Setting Up an OAM Instance 238
11.2 Viewing OAM Events 240
11.3 Viewing OAM Status 241
11.4 Viewing OAM Statistics 244

11.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 OAM
instance. An active instance immediately starts sending information
Enable OAM Protocol
OAMPDUs associated with the discovery process.
Note: This field does not indicate that an OAM peer has been
successfully discovered.
OAM Mode Select the mode in which OAM will be used:

Active Mode / Passive Passive: Listens for OAMPDUs and replies once it starts receiving
Mode them
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 the
Loopback 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 that
(EFE) must be detected in a given period to trigger the transmission of an
event
Threshold and
Window The window setting defines the time of the period. Expressed in
seconds.
A frame error is an error detected at Layer 2 or at the MAC level. It
can be caused by various types of errors such as CRC errors, short
frames and long frames.
Errored Frame Period The threshold setting that defines the number of frame errors that
Event (EFPE) must be detected in a given period to trigger the transmission of an
event
Threshold and
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.
Errored Frame The threshold setting that defines the number of frame errors that
Seconds Summary must be detected in a given period to trigger the transmission of an
Event (EFSSE) event
Threshold and An errored frame second is a one-second period in which at least
Window 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.

11.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

11.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 most
recently transmitted OAMPDU
Flags
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 the
most recently transmitted information OAMPDU
Info TLV Revision
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 most
State 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 most
recently received OAMPDU
Flags
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 the
most recently received information OAMPDU. This value is updated
Info TLV Revision
upon reception of a valid frame.
Parser State / Mux A string of three bits corresponding to the State field of the most
State 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

11.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:

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:

for slow protocols

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 of a
valid frame with the following:

for slow protocols
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 of a
valid frame with the following:

for slow protocols
protocols
OAM
last received Event Notification OAMPDU.

Loopback Control A count of OAMPDUs received that contain the Loopback Control
with the following:

for slow protocols
protocols
OAM
The OAMPDU code equals the Loopback Control code and is

Variable Request A count of OAMPDUs received that contain the Variable Request
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

Variable Response A count of OAMPDUs received that contain the Variable Response
with the following:

for slow protocols
protocols


OAM
The OAMPDU code equals the Variable Response code and is

Organization Specific A count of OAMPDUs received that contain the Organization

Specific code. This counter is incremented upon reception of a valid
frame, with:

for slow protocols
protocols
OAM
The OAMPDU code equals the Organization Specific code and is

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.

last transmitted Event Notification OAMPDU.

increment rate for slow protocol frames: no more than 10 frames
shall be transmitted in any one-second period.
Loopback Control A count of transmitted OAMPDUs containing the Loopback Control

is generated within the OAM sublayer with an OAM code indicating
a Loopback Control OAMPDU.
Variable Request A count of transmitted OAMPDUs containing the Variable Request

is generated within the OAM sublayer with an 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 service
primitive is generated within the OAM sublayer with an 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 service

primitive is generated within the OAM sublayer with an OAM code
indicating an Organization Specific OAMPDU.

12. 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:
12.1 Using the Performance Assurance Agent 251
12.2 Using Service OAM 265
12.3 Using Service Availability 303
12.4 Using the Two-Way Active Measurement Protocol (TWAMP) 311

12.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.
12.1.1 Setting Up a Probe

▶ To configure a PAA probe
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 Layer 2.

UDP: 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, collects
PAA samples (Sink) or does both operations (Bi-Dir).
Mode
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: 1500
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.

Peer Index 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 mode
Destination 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 Encapsulates Layer-2 PAA frames into a VLAN-in-VLAN. VLAN2

encapsulation represents the inner VLAN.
Note: Only applies when VLAN 1 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.
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.

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 ID value 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
Rx VLAN 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 ID that 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
Rx VLAN 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.
Rx VLAN 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 UDP port 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
value with the value that was received.
Couple Tx/Rx DSCP
If you expect the transmit and receives values to be equal, enable
Expected RX DSCP
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 Validate Tx/Rx VLAN 1 Priority enables validating the

Couple Tx/Rx If you expect the transmit and receives values to be equal, enable
VLAN 1 Priority Couple Tx/Rx VLAN 1 Priority.
Rx VLAN 1 Priority field.
Range: 0-7
Continuity
Packet Loss The reference period, expressed in milliseconds, for the continuity
Reference Period 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 any
Threshold 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 the
Threshold reference period. For example, for a reference period of 10 seconds,
the average is calculated from samples taken during the last
10 seconds.
Exceeding the threshold triggers the alarm PAA_OW_AVG_
DELAY_ALERT.
Maximum Delay The maximum one-way delay variation threshold to monitor during
Variation 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 samples
Variation Threshold 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 Threshold The number of consecutive samples exceeding the Maximum 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 the
Threshold reference period.
Exceeding the threshold triggers the alarm PAA_TW_AVG_
DELAY_ALERT.
Maximum Delay The maximum two-way delay variation threshold to monitor during
Variation a test period.
Threshold to trigger the alarm PAA_TW_DV_ALERT.

Threshold Delay Variation that are allowed before triggering the two-way
delay variation alarm for this Reference Period.
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 be
(msec) 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: 100 milliseconds

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

Maximum: One-way join period
Maximum Leave The maximum leave delay objective.

Delay
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

Maximum: (One-way reference period) - (One-way join period)

12.1.2 Deleting a Probe

CAUTION: Deleting a PAA probe instance will also delete all SA metrics that use
this PAA probe instance as the metric source.
▶ To delete a PAA probe
1. Access the page SOAM ▶ PAA ▶ Configuration.
2. Click the name of the probe you want to delete.
3. Click Delete.
12.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:

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
12.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:

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,
expressed in microseconds
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 of
Exceeded 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
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 variation of the samples with the highest delay
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 the
Exceeded 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 of
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 delay
Maximum DV The two-way delay variation of the samples with the highest delay
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 the
Exceeded 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 value of
Exceeded 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 value
Exceeded 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 ID mismatch, the VLAN 1 ID that was expected
ID Received In the event of an ID mismatch, 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 ID mismatch, the VLAN 2 ID that was expected
ID Received In the event of an ID mismatch, 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

12.2 Using Service OAM

Service OAM (SOAM) is a layer-2 protocol used for Connectivity Fault Management (CFM) and
Performance Monitoring (PM) in a Carrier Ethernet Network (CEN) and encompasses the
fault management and performance management capabilities of the GX Performance
Element. For more information, see Application Note 200: Configuring SOAM with Virtual
Connections.
The following sections describe IEEE 802.1ag Service OAM and show how to set up your
Metro Ethernet Network to perform end-to-end monitoring.
An overview of Service OAM is given below.
Overview of Service OAM
The diagram below shows a typical setup scenario for Service OAM.
Typical Setup Scenario for Service OAM
12.2.1 MEP vs. MIP

A Maintenance End Point (MEP) is a provisioned OAM reference point that can initiate and
terminate proactive OAM frames and can initiate and react to diagnostic OAM frames. A MEP
is represented by a “triangle” symbol, as shown in the OAM diagram below. A Point-to-Point
EVC has two MEPs, one at each end-point of the ME (i.e., each UNI-N)
Each MEP has a direction, down or up:

A Down MEP receives PDUs from the local interface and sends PDUs towards the local
interface.
An Up MEP receives PDUs from the relay entity and sends PDUs towards the relay
entity.
A Maintenance Intermediate Point (MIP) is a provisioned OAM reference point that is capable
of reacting to diagnostic OAM frames initiated by MEPs and does not initiate proactive or
diagnostic OAM frames. A MIP is represented by a “circle” symbol, as shown in the Overview
of Service OAM, in Using Service OAM. The number of MIPs in a Point-to-Point EVC or
Multipoint EVC depends on the specific deployment.
MIPs are used for Fault Management.
For more information, see Application Note 200: Configuring SOAM with Virtual Connections.
12.2.2 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 association End Points (MEP).
Once these are set up, you can use Service OAM for performing the following fault
management functions:
Link Trace Messages.

Loopback Messages.
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 or MIPs have been configured
VID The VLAN ID to which the Maintenance Point is attached, or 0, if

there is no VLAN ID
Level The MD level (or MEG level) of the Maintenance Point

Possible values: 0-7
Dir The direction in which the MEP or MIPs faces on the port

MD idx The index of the Maintenance Domain with which the MEP or MIP
is associated
MA idx The index of MA (or MEG) with which the MEP or MIP is associated
MEPID The MEPID of the MEP or MIP (MEPID of MIP is 0)
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 0–31 (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 end points.
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 lower active MD level on the
component port.
Explicit: Create MHFs only if there is an MEP at the next lower
active MD level on the component port.
Sender ID Permission The information (if any) to be included in the Sender ID TLV
transmitted in CCMs, LBMs, LTMs and LTRs.
The available values are:
None: The Sender ID TLV is not to be sent.

Chassis: The Chassis ID Length, Chassis ID subtype, and Chassis
ID fields of the Sender ID TLV are to be sent.
Manage: The Management Address Length and Management
Address of the Sender ID TLV are to be sent.
Chassis and Manage: The Chassis ID Length, Chassis ID
Subtype, Chassis ID, Management Address Length, and
Management Address fields are all to be sent.
Deleting a Maintenance Domain (MD)

CAUTION: Deleting an MD will also delete all instances (e.g. MA/MEG) that use
this 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.
Setting Up Maintenance Associations (Maintenance Entity Groups)

Before setting up a Maintenance Association or 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 are
discussed in IEEE 802.1ag. Maintenance Entity Groups are discussed in ITU-T Y.1731.
The remote MEP auto-discovery feature is intended to make it easier to configure MA/MEGs
because it eliminates the process of manually building the comma-separated list of up to 255
associated MEPs (i.e., the MEPID list). With the remote MEP auto-discovery, Connectivity
Check Messages (CCM) are processed as they are received by the MEP and the associated

remote MEP is automatically added to the MEPID list. An R-CCM alarm is raised in the SOAM
▶ CFM ▶ MEP ▶ Status page when CCMs are no longer being received by a MEP; this MEP
will be monitored until its MEPID is manually removed from the MEP IP list.
Note: For remote MEP auto-discovery to function as expected, all MEPs to be

discovered must belong to the same MA. Furthermore, you must manually create
at least one MEP per MA in order to receive the CCMs from the remote MEPs
being discovered.
▶ 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 Maintenance Entity Group
Index
MD Index Unique index value assigned to the Maintenance Domain

for this Maintenance Association or Maintenance Entity
Group
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
MAID string format mode Indicates the string format mode of the Maintenance
Association Identifier (MAID).
Note: This field will be visible only if the Maintenance
Domain (MD) is set to Y.1731 and the Name Format is set to
String.
Normal: The MEG ID length will have a value equal to

the MA/MEG name string length.

Legacy: The MEG ID length will have a default minimum
length field of 13 character.
Name The name of this Maintenance Association or Maintenance

Entity Group
MA/MEG Name
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

Maintenance Entity Group
CCM Interval The 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.

Default: Create MHFs if there is no lower active MD
level, or if there is a MEP at the next lower active MD
level on the port.
Explicit: Create MHFs only if there is a MEP at the next
lower active MD level on the port.
Defer: Use the Maintenance Domain parameter to
determine MHF creation.
Sender ID Permission Determines what, if anything, is to be included in the

Sender ID TLV transmitted in CCMs, LBMs, LTMs and LTRs.
None: The Sender ID TLV is not to be sent.

Chassis: The Chassis ID Length, Chassis ID subtype, and
Chassis ID fields of the Sender ID TLV are to be sent.
Manage: The Management Address Length and
Management Address of the Sender ID TLV are to be
sent.
Chassis & Manage: The Chassis ID Length, Chassis ID

subtype, Chassis ID, Management Address Length, and

Management Address fields are all to be sent.
Defer: Determined by the domain configuration or
system configuration.
Use VCE Select this box to enable VCE for use. When enabled,
another field is shown: VCE Name allowing you to select the
VCE to use.
VCE Name Type the name of the VCE you wish to use.
ComponentID An unsigned integer identifying the VLAN bridge

component in the system.
VLAN Type The VLAN type associated with this Maintenance

Association or Maintenance Entity Group.
None: The association is not attached to a VLAN and the

contents of the VLAN ID list is ignored.
Note: The values assigned to the S-VLAN and T-VLAN

Ethertypes can vary, depending on the S-VLAN Ethertype
value selected in the page System ► Configuration ►
Mode.
VLAN ID List A list 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.
Remote MEP Auto-Discovery Select this box to enable the Remote MEP Auto-Discovery
feature for this Maintenance Association or Maintenance
Entity Group. When enabled, remote MEPs are
automatically added to the MA/MEG as soon as the remote
MEP's CCM message is received.
Note: You must manually refresh the page to view any
remote MEPs that have been discovered since the page
was initially loaded. Access the page SOAM ▶ CFM ▶ MEP
▶ Statistics and examine the values in the "CCM Sent" and
"CCM Received" columns if you believe a MEP has failed to
be discovered.

MEPID List A comma-separated list of all the MEPs that are associated
with this Maintenance Association or Maintenance Entity
Group.
Typically, when two MEP are added to a MA/MEG, it is
usually because you are creating an E-Line type of service,
based on a point-to-point EVC. In contrast, adding multiple
MEP is for when you are creating an E-LAN type of service,
based on a rooted-multipoint EVC.
If this Maintenance Association or Maintenance Entity
Group has a MEP with CSF enabled (see SOAM ▶ CFM ▶
MEP ▶ Configuration), a maximum of only two MEPID are
permitted in the list, since ETH-CSF is point-to-point.
Consequently, the MA/MEG MEPID list can only be edited if
ETH-CSF is disabled.
If the Remote MEP Auto-Discovery feature for this
Maintenance Association or Maintenance Entity Group is
enabled, the list of MEPIDs will be presented in numerical
order, not the order in which the MEPs are discovered.
▶ To delete a Maintenance Association (Maintenance Entity Group)
CAUTION: Deleting a MA/MEG will also delete all instances (e.g. MEP) that use
this MA/MEG.
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.
Setting Up Maintenance Association End Points

Before setting up a MEP, you must first set up its MA/MEG. Maintenance association End
Points (MEP) are discussed in IEEE 802.1ag.
▶ To set up a Maintenance association End Point
1. Access the page SOAM ▶ CFM ▶ MEP ▶ Configuration.

A listing of all existing Maintenance association End Points 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 end point for valid
results to be displayed.

Maintenance association End Point (SOAM ▶ CFM ▶ MEP ▶ Configuration)

Index The index value assigned to the Maintenance association End Point
MA/MEG Name The name of the maintenance association (or MEG) to associate
with the MEP
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.
VCE port A check box to enable use of a VCE port. Once selected, other
options appear in the dialog.
VCE Name The name of the VCE that you wish to use. Appears only if VCE port
check box has been selected.
TP A pull-down menu with a limited selection: tp-a or tp-z. Select the

desired terminal point. Appears only if VCE port check box has been
selected.
Direction A pull-down menu with a limited selection: Up or Down. Select the

desired direction.
Port The port or CFM interface used by this MEP. Appears only if VCE
port check box has not been selected.
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 receives them from, the direction of the Bridge
Relay Entity. Up MEP points toward the Bridge Relay Entity.
Down: The MEP resides in a Bridge that receives CFM PDUs
from, and transmits them toward, the direction of the LAN.
Down MEP points away the Bridge Relay Entity.
MEP Name 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
IDs assigned to the MEP's MA/MEG. The value 0 indicates that
VLAN
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.

TLV Enable
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 end points 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.

Notes: This parameter is ignored if the port you select has not been
set up to perform EVC fault propagation.
For a MEP on a VCE, the client interface is automatically chosen

from the VCE configuration. During an add, the client interface will
be hidden; during an edit, it will be shown, but will not be editable.
▶ To delete a Maintenance association End Point
CAUTION: Deleting a MEP will also delete all instances (e.g. LTM, LBM) that use
this MEP.
1. Access the page SOAM ▶ CFM ▶ MEP.
2. Click the MEPID of the MEP to be deleted.
3. Click Delete.
Viewing MEP Status

▶ To view maintenance association end point (MEP) status
1. Access the page SOAM ▶ CFM ▶ MEP ▶ Status.

A listing of all MEPs is displayed, along with their status codes and details.
The total number of MEPs found in the system is given in the lower-left corner of the
2. (Optional) To limit the view to only certain MEPs, enter a value on which to filter, then
click Search. You can filter by the index value, MEPID, database, or by any of the
provided status codes.
Note: Enter an asterisk (*) as a wildcard to replace one or several characters.
3. 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
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
Defects (Alarm Conditions)
RDI The latest CCM received by this MEP from a remote MEP containing
the Remote Defect Indication (RDI) bit
CCM RDI
Possible values are Active (A) or Inactive (I).
MAC The last CCM received by this MEP from a remote MEP indicates
that the transmitting MEP's associated MAC is reporting an error
MAC Status
status via the Port Status TLV or Interface Status TLV.
R-CCM Indicates whether the MEP is not receiving CCMs from a MEP in its
configured list.
Remote CCM
E-CCM Indicates whether the MEP is receiving invalid CCM messages

Errored CCM Possible values are Active (A) or Inactive (I).
X-CCM Indicates whether the MEP is receiving CCM messages that could
be coming from another MA
Cross-Connect CCM

AIS Indicates whether Y.1731 Alarm Indication Signal (AIS) PDUs are
being received
Received AIS
EPL Indicates whether some packet loss measurement defect is Active

(A) or Inactive (I) for that MEP
Excessive Packet Loss
EDM Indicates whether some delay measurement defect is Active (A) or

Inactive (I) for that MEP
Excessive Delay
C-LOS Indicates whether Y.1731 Client Signal Fail (CSF) Loss of Signal (LOS)
PDUs are being received
Received C-LOS
C-FDI Indicates whether Y.1731 Client Signal Fail (CSF) Forward Defect
Indication (FDI) PDUs are being received
Received C-FDI
Possible vales are Active (A) or Inactive (I).
C-RDI Indicates whether Y.1731 Client Signal Fail (CSF) Reverse Defect
Indication (RDI) PDUs are being received
Received C-RDI
N-SLM The Near-End Synthetic Loss Measurement indicates whether

near-end synthetic loss messages are Active (A) or Inactive (I) for
that MEP
F-SLM The Far-End Synthetic Loss Measurement indicates whether far-

end synthetic loss messages are 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 are 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 MEP database 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 MEP

whose information from the MEP Database is to be returned
Remote MEPID
State The operational state of the remote MEP IFF state machines
Remote MEP State Possible values are:
Idle: MEP monitoring is disabled because the MA/MEG ID list

contains only one MEP ID
Start: MEP monitoring has started, but no MEPs have been
received
Failed: MEP messages were not received, or received late
OK: Valid MEP messages have been received
RDI The state of the RDI bit in the last received CCM. Possible values
are:
Latest CCM RDI
True: The RDI bit was set
False: The RDI bit was not set, no CCM message was received
Mac Address The MAC address of the remote MEP

Latest Failed-OK The time at which the IFF Remote MEP state machine last entered
Time 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 this
MEP
CCM
CCM Received Indicates the number of connectivity check messages received by

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

this MEP with the RDI bit set
CCM with RDI
CCM Seq Error Indicates the total number of out-of-sequence CCMs received from
all remote MEPs
CCM Received
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 received
by this MEP per VLAN priority
SLR Indicates the number of synthetic loss responses sent and received
by this MEP per VLAN priority
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 dropped
MAC because of an invalid MAC address
12.2.3 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 End Points 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 resolved
into the local MEP database.
R-MEPID
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: 0–255
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

12.2.4 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.
12.2.5 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 End Points 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: 100–5000
Data TLV Indicates whether LBMs should include a Data Type Length Value
(TLV). Possible values are:
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: 1–1488 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
loopback request
LBM Received
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
12.2.6 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.
12.2.7 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 timestamps:
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 timestamps, 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 DMM
frames. Expressed in milliseconds.
Interval
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 for
this Reference Period.
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, to

Value monitor in the Reference Period.
Instantaneous Number of consecutive measurements exceeding the Maximum

Threshold 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
alarm for this Reference Period.
microsecond granularity. Consequently, values such as 1.001 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 in

Value the Reference Period.
Instantaneous Number of consecutive measurements exceeding the Maximum

Threshold Allowed Value that triggers a two-way delay alarm for this
Reference Period.
Average Threshold Two-way average delay threshold, expressed in milliseconds, that

triggers the average two-way delay alarm for this Reference
Period.
microsecond granularity. Consequently, values such as 1.001 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, to

Value monitor in the Reference Period.
Instantaneous Specify the number of consecutive measurements exceeding the

Threshold Maximum Allowed Value that triggers a two-way delay variation
Average Threshold Specify the two-way average delay variation threshold, expressed
in milliseconds, that triggers the average two-way delay variation

microsecond granularity. Consequently, values such as
1.001 ms are acceptable.
12.2.8 Deleting a Delay Measurement Instance

CAUTION: Deleting a DMM instance will also delete all SA metrics that use this
DMM instance as the metric source.
▶ 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.

12.2.9 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 286.
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
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 DV The one-way instantaneous delay variation, expressed in

microseconds
Minimum DV The minimum delay variation over one period, expressed in

microseconds
Maximum DV The maximum delay variation over one period, expressed in

microseconds
Average DV The average delay variation over one period, expressed in

microseconds
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 over one period, expressed in microseconds
Nbr Threshold Number of times the two-way delay exceeded the value of the
Exceeded Maximum Delay parameter
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 DV The two-way instantaneous delay variation, expressed in

microseconds
Minimum DV The minimum delay variation over one period, expressed in

microseconds
Maximum DV The maximum delay variation over one period, expressed in

microseconds
Average DV The average delay variation over one period, expressed in

microseconds
Nbr Threshold Number of times the two-way delay variation exceeded the value of
Exceeded the Maximum DV parameter

12.2.10 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.

12.2.11 Deleting a Packet Loss Instance

CAUTION: Deleting a PL instance will also delete all SA metrics that use this PL
instance as the metric source.
▶ 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.
12.2.12 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

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.
detected during the period
Largest Gap
This counter is reset to zero at the beginning of each period.
12.2.13 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 SLM instance
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.

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.
Enable The state of the SLM instance. When enabled, SLM frames are sent
at the specified interval. Disabled by default.
State
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.
12.2.14 Deleting a Synthetic Loss Measurement Instance

CAUTION: Deleting an SLM instance will also delete all SA metrics that use this
SLM instance as the metric source.
▶ 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.

12.2.15 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

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
sequence of packets that were received during the interval
Nbr Gaps
Note: This counter is reset to zero at the beginning of each period.
detected during the period. Expressed in packets
Largest Gap
Note: This counter is reset to zero at the beginning of each period.
12.2.16 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 CFM Interfaces page opens. All available CFM interfaces 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 CFM Interface-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
12.2.17 Assigning a CFM Interface

▶ 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.
12.2.18 Unassigning a CFM Interface

CAUTION: Interfaces currently in use by a MEP instance cannot be unassigned.
▶ To unassign a CFM interface

assigned port name.
2. Select the interface from which you wish to unassign a CFM interface from the
Interface Name column.
The CFM Interface-n Configuration page is displayed.
3. Click Unassign to unassign the selected interface from CFM.

The system returns to the CFM Interfaces page. The name of the interface you
unassigned is now listed in the Interface Name drop-down list beside the Assign
button.
12.2.19 Setting Up VSP

The VSP function is used to reflect VSP (vendor-specific) 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.
12.2.20 Viewing VSP Results

▶ To view VSP Results
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)
VLAN ID The VLAN ID of the VSP frames received
MEG Level The MEG level of the VSP frames received
RX Count The number of VSP frames received
TX Count The number of VSP frames reflected
12.2.21 Setting Up CFM Default Values

The MIP Half-Function (MHF) default parameters control the MHF creation for VIDs that are
not attached to a Maintenance Association within a VLAN component. For each component

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 that
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 an MA, the MA 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 default parameters is displayed.
2. Click on a numerical ID number of component ID to edit existing component defaults.
3. The Detailed SOAM CFM Defaults page appears.

CFM Defaults (SOAM ▶ CFM ▶ Defaults)

Component Id An unsigned integer identifying the VLAN bridge component in the

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

Default: Create MHFs if there is no lower active MD level, or if
there is a MEP at the next lower active MD level on the
component port.
Explicit: Create MHFs only if there is a MEP at the next lower
active MD level on the component port.
Defer: Use the Maintenance Domain parameter to determine
whether MHFs can be created.
(Default) MHF Sender Indicates what, if anything, is to be included in the Sender ID TLV
ID Permission transmitted in CCMs, LBMs, LTMs and LTRs
None: The Sender ID TLV is not to be sent

Chassis: The Chassis ID Length, Chassis ID subtype, and Chassis
ID fields of the Sender ID TLV are to be sent

Manage: The Management Address Length and Management

Address of the Sender ID TLV are to be sent
Chassis and Manage: The Chassis ID Length, Chassis ID
subtype, Chassis ID, Management Address Length, and
Management Address fields are all to be sent

12.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 SA function 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 303.
Add one or more SA metrics: See Setting Up an SA Metric on page 305.
Put a Service Availability instance into service: See Putting an SA Instance into Service
on page 307.
12.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 SA instance or click the SA instance 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 305.
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 addition
(min) 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.
Notes: 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.
When the SA Metric type is set to CFM, the Time Interval must be
set to a minimum value of 20 seconds because the CFM module
updates its statistic every 10 seconds. It is recommended not to
configure a Time Interval of 10 seconds or less for the CFM.
Client Port Cut-Off Feature

Client Port Cut-off allows the client to configure a network performance threshold below
which the client port is automatically disabled in order to advertise the link failure to a peer
network.
A user-configurable timer is available to define the time to wait before restoring the link after
the network performance has returned to normal. Default value is 120. Range is 0 to 300
seconds in increments of 1 second.
A user-configurable timer is available to define the time to wait before disabling the client
port after the network performance has fallen below the configured threshold. Default value
is 0. Range is 0 to 120 seconds in increments of 1 second.
12.3.2 Deleting an SA Instance

▶ To delete a Service Availability instance

2. Click the SA instance Name to delete.
3. Click Delete.
Note: This also deletes all SA metrics associated with this SA instance.
12.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 SA instance.
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 294, Deleting a Delay Measurement
Instance on page 289, and to Deleting a Probe on page 259.
▶ 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 SA metric or click the SA metric
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 Possible values 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 is a
PAA packet loss, the Metric source name must be the name of an
Metric Source Name

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.
12.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.
12.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 SA instance 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.
12.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.

12.4 Using the Two-Way Active Measurement Protocol

(TWAMP)
Two-Way Active Measurement Protocol (TWAMP) is a protocol used to measure round-trip
IP performance between any two TWAMP-enabled units deployed in a network. With
TWAMP, you can reliably perform in-band, round-trip performance measurements and
identify performance issues by sending test packets to a unit that reflects them back.
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 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 TWAMP when connecting to Layer-3
TWAMP session sender devices.
12.4.1 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 TWAMP generator 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 (ms) The time at which this TWAMP instance transmits packets
expressed in milliseconds
Reference Period The reference period for the TWAMP instance, expressed in
(min) 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 (IPv4) and 1452 bytes (IPv6)
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 RFC-5357. Similarly, if you observe that packets are
not being reflected, try increasing the packet size to at least 41
bytes.
UDP Parameters
Destination IP The remote peer IP address

Address
Source UDP Port The UDP source port. The default value is 10000.
Other acceptable values are in the range of 1024 to 65535.
Destination UDP Port The UDP destination port. The default value is 862 .
Other acceptable values are in the range of 1024 to 65535.
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 (sample) 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
(msec) Period
trigger the alarm TWAMP_TW_MAX_DELAY_ALERT.

(sample) 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 taken
Threshold (msec) 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 during
Variation (msec) a test period
Threshold to trigger the alarm TWAMP_MAX_DV_ALERT.

Threshold (sample) Delay Variation that are allowed before declaring the two-way
delay variation alarm for this Reference Period
Average Delay The average two-way delay variation is calculated from samples

Variation Threshold taken during the reference period.

(msec)
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
(msec) Reference Period
trigger the alarm TWAMP_NE_OW_MAX_DELAY_ALERT.

(sample) 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 (msec) 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 (msec) monitor during a test period
Threshold to trigger the alarm TWAMP_NE_OW_MAX_DV_
ALERT.

Threshold (sample) 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 using
Variation Threshold the samples taken during the reference period.
(msec)
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
(msec) Reference Period
trigger the alarm TWAMP_FE_OW_MAX_DELAY_ALERT.

(sample) 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 (msec) 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 (sample) monitor during a test period
Threshold to trigger the alarm TWAMP_FE_OW_MAX_DV_
ALERT.

Threshold (smaple) 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.
(msec)
Exceeding the threshold triggers the alarm TWAMP_FE_OW_
AVG_DV_ALERT.
12.4.2 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.
12.4.3 Viewing TWAMP Generator 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 TWAMP generator results will be refreshed.
TWAMP Generator Session Results (SOAM ▶ TWAMP ▶ Generator ▶ Results)

TWAMP Generator Results
Session Name The name of the probe

Status Codes The current state (active or inactive) for all TWAMP alarms for the

OAD-NE: One-Way Average Delay, Near End
ODV-NE: One-Way Delay Variation, Near End
OADV-NE: One-Way Average Delay Variation, Near End
OAD-FE: One-Way Average Delay , Far End
ODV-FE: One-Way Delay Variation, Far End
OADV-FE: One-Way Average Delay Variation, Far End
Local Sync Indicates whether or not the local clock is in sync with its configured
reference clock (PTP, NTP or GPS)
Remote Sync Indicates whether or not the remote clock is in sync with its
configured reference clock (PTP, NTP or GPS)
Protocol The protocol used by this session's protocol is UDP
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 period,
Maximum Delay The two-way delay of the slowest sample collected over the period,
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 of
Instantaneous DV The two-way instantaneous delay variation value, expressed in

microseconds. This is the latest two-way delay variation measured
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
over the period, expressed in microseconds
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 period,
Maximum Delay The one-way delay of the slowest sample collected over the period,
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 delay
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
Maximum Delay The one-way far-end delay of the slowest sample collected over the
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 the

Exceeded 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
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
12.4.4 Viewing the TWAMP Generator 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.
frequency with which the TWAMP generator status data will be refreshed.
TWAMP Generator Session Status (SOAM ▶ TWAMP ▶ Generator ▶ Status)

Session Name The name of the probe
Local Sync Indicates whether or not the local clock is in sync with its configured
reference clock (PTP, NTP or GPS)
Remote Sync Indicates whether or not the remote clock is in sync with its
configured reference clock (PTP, NTP or GPS)
Status Codes The current state (active or inactive) for all TWAMP alarms for the

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
12.4.5 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

Default value: Disabled
UDP Port The UDP port of the reflector. The default value is 862 . Other
acceptable values are any value within the range of 1025 to 65535.

TWAMP.
Layer-3 Y.1564.
SAT Protocol.

12.4.6 Viewing TWAMP Reflector Statistics

▶ To view TWAMP reflector 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

13. 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.
This chapter describes how to perform end-to-end testing and monitoring, which enables
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:
13.1 Setting Up SAT Reporting 323
13.2 Testing Locally-Created Services 325
13.3 Using RFC-2544 for Traffic Generation and Analysis 327
13.4 Using Y.1564 for Service Activation Testing 350
13.5 Using the SAT Protocol 362

13.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 SAT reporting
1. Access the page SAT ▶ Reporting.

SAT Reporting (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 format
Transfer to the specified server.
Enable XML File Enables or disables the transfer of RFC-2544 reports in XML format
Transfer 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 to
Transfer the specified server.
Enable XML File Enables or disables the transfer of Y.1564 reports in XML format to
Transfer the specified server.
File Server Configuration
Server URL The full URL of the server to which to send test reports.
Note: The following special characters are not allowed in the URL
input: "<", ">", "\n", "\r", "\t".
Examples:
ftp://username:[email protected]
ftps://username:[email protected]
sftp://[email protected]/24

tftp://192.0.2.0/24
scp://[email protected]/24:/target_directory
scp://username@[2001:DB8::/32]:/target_directory
SCP Password Enter the password required for SCP and SFTP transfers.

13.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 unit’s 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
Notes: 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.
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.

13.3 Using RFC-2544 for Traffic Generation and Analysis

Used to pinpoint devices or network problems or to measure current throughput, frame delay
and frame-delay variation on a specific network segment, traffic generation and analysis is
specified in RFC-2544. The following sections describe how to set up your Metro Ethernet
network in order to perform end-to-end testing and monitoring.
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 GX 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

13.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 GX 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
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, FTPS, 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 323.
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.
Exclude VLAN size When excluding the VLAN size, the frame length is increased by
the size of the VLAN tag header(s) being added to the frame.
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 generic: Layer-2 frames with a generic Layer-3 (UDP)
payload. Only to be used with OAM loopback devices with no
IP address swapping. This mode will work with or without
MAC swapping.
Layer-3: UDP segments to perform a test across a multi-

layered network.
IP multicast: IP multicast packets to test multiple receiving

points. The IP multicast test is a one-way test. Receiving unit

must not loopback the packets.
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 not available for Y.1564 SAT.
Y.1731 MEG Level The Maintenance Entity Group level.

Range: 0–7
Note: Applies to Layer-2 traffic only. For details, refer to ITU-T
Y.1731.
Destination IP Address The IP address of the remote unit interface. Applies to Layer-3
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.
Notes:
Layer-3 generic traffic is available for the RFC-2544 traffic
generator and test suite. It is unavailable for Y.1564 SAT.
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 near-end UDP port number used to generate the test's PDU.
Note: Applies to Layer-3 traffic only.
Destination Port The far-end UDP port number associated with the IP address of
the unit that will receive, process and display the traffic statistics
and report.
Notes:
Applies to Layer-3 traffic only.
For reporting to work properly, you must set the port to a value in
the range of 0 to 65535 but you cannot set the destination port
value to 8793, since this is Accedian's proprietary port number.
For information on destination ports default values, refer to
"Network Requirements — TCP/UDP Ports" on page 127.
A port cannot be defined as the UDP port here if it is already
being used for any of the following features:

TWAMP.


Layer-3 Y.1564.
SAT Protocol.
TTL The Time To Live (TTL) of the packets transmitted on the flow.
Note: Applies to layer-3 type tests only.
Enable VLAN 1 Header This encapsulates all frames with one VLAN header.

When enabled, all test frames are encapsulated with the
specified VLAN ID.
VLAN 1 Ethernet Type The first VLAN Ethernet type.

VLAN (0x8100)
VLAN (0x88A8)
VLAN (0x9100)
Notes : The Ethertype associated with the value selected in the

drop-down list is displayed in a read-only text box for your
convenience.
Applies only when the VLAN 1 header is enabled.
VLAN 1 Priority The first VLAN priority bits.

Note: Applies only when the VLAN 1 header is enabled.
VLAN 1 CFI The first VLAN Canonical Format Indicator (CFI).

Enable VLAN 2 Header Encapsulates all frames with two VLAN headers (as in Q in Q ).
VLAN1 must be enabled to use two VLAN headers.
VLAN 2 ID The second VLAN ID. When enabled, all test frames are
encapsulated with the second specified VLAN ID (inner VLAN).
VLAN 2 Ethernet Type The first VLAN Ethernet type.

VLAN (0x8100)
VLAN (0x88A8)
VLAN (0x9100)
Notes:The Ethertype associated with the value selected in the


convenience.
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 Type The type of flow testing being conducted is:
Out-of-Service: Two-way loopback using the full link

bandwidth
In-Service: One-way test for sharing a bandwidth regulator
with client traffic
Note: When the flow type is In-Service, you must select a

Regulator.
Regulator The regulator to use when the flow type is in-service. For In-
service flow type, you must also enure the Regulator working
rate and the Generator working rate are set to the same layer
(Layer 1 or Layer 2) in order to have accurate tests. These settings
are available in the Traffic ▶ Configuration page.
Note: This field has no effect when the flow type is Out-of-
Service.
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

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 produce
inaccurate results.
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).
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
preconfigured 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.
Minimum value of 1. Maximum of 4,000,000,000 packets.

13.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:
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
Working Rate The flow's working rate may be one of the following:
Layer-1
Layer-2
Receive Statistics
Received Packets The total packets received by the generator’s 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.

The delay is measured for each packet from the generator to the
Average Delay
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 microseconds

Average DV
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
13.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.

Notes: In-service tests are unidirectional, as opposed to out-of-service tests, which are
bidirectional (round-trip).
Accedian's GX Performance Elements contain 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 the RFC-2544 analyzer
1. Access the page SAT ▶ RFC-2544 ▶ Monitor ▶ Configuration.

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 (SAT ▶ RFC-2544 ▶ Monitor ▶ Configuration)

State The state of the monitor (Enabled or Disabled )
Monitor Name The name assigned to the monitor
Monitor Description The description set up to identify the monitor and its characteristics
Monitor Mode Terminal: The RFC-2544 test is terminated at this unit.

Bypass: The RFC-2544 test measurements are performed but the
traffic follows the rules configured in the Policies for this specific
traffic type.
Incoming Port The incoming port of the monitor
Packet Header Settings
Type The type of test traffic being inspected:
Layer-2 Accedian: Y.1731 LBM frames marked with the Accedian

Ethertype.
Layer-3: UDP segments to perform a test across a multi-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: 0–7
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.
Destination Port The far-end UDP port number associated with the IP address of the
unit that will receive, process and display the traffic statistics and
report.
Notes:
value to 8793, since this is Accedian's proprietary port number. For
information on destination ports default values, refer to "Network
Requirements — TCP/UDP Ports" on page 127.
Enable VLAN 1 This encapsulates all frames with one VLAN header.
Header
Enable or disable VLAN 1 header.
This encapsulates all frames with one VLAN header.
If the VLAN 1 header is enabled, the packet size increases by 4
bytes. For example:
If the packet size set to 64 and the VLAN 1 header is not

enabled, the traffic generator will send packets of 64 bytes.
If the packet size is set to 64 and the VLAN 1 header is enabled,
the traffic generator will send packets of 68 bytes.

When enabled, all test frames are encapsulated with the specified
VLAN ID.
VLAN 1 Ethernet The first VLAN Ethernet type.

Type

VLAN (0x8100)
VLAN (0x88A8)
VLAN (0x9100)

convenience.


Enable VLAN 2 Enables or disables the VLAN 2 header.

Header
Encapsulates all frames with two VLAN headers (as in Q in Q ).
In order to use two VLAN headers, both VLAN 1 and VLAN 2
headers must be enabled.
If VLAN 1 and VLAN 2 headers are both enabled, the packet size
increases by 8 bytes. For example:
If the packet size set to 64 and both VLAN 1 and VLAN 2

headers are enabled, the traffic generator will send packets of
72 bytes.

Type
VLAN (0x8100)
VLAN (0x88A8)
VLAN (0x9100)
The Ethertype assocaited with the value selected in the drop-down

list is displayed in a read-only text box for your convenience.



13.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.
Note: When using In-Service Throughput Testing mode, the Generator and
Monitor need time syncing before examining "One-way delay" and "One-way
delay Variation" parameters to get the proper results.
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 timestamp to identify the gap.
Maximum Gap The maximum size, expressed in frames, of the gaps
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
13.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.
Note: Accedian's GX Performance Elements contain pre-programmed RFC-2544

and Y.1564 loopbacks for Layer-2 or Layer-2 Accedian frames. For Layer-2
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.

A maximum of 1 test suite can be created per device
Suite Name
A maximum of 16 test suites can be created.
Description The description configured to identify the test suite and its
characteristics.
Suite Description
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) and
Report executed steps appear in the test report.
Exclude VLAN size When excluding the VLAN size, the frame length is increased by
the size of the VLAN tag header(s) being added to the frame.
Note: Enabling this parameter does not affect the Frame size that
will 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 Unit Under Test (UUT)
is able to perform full wire-speed at GigE, the test runs at
1000 Mbps and 980 Mbps (for a Step Size of 20 Mbps). 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 (default is disabled).
The back-to-back test sends a minimum of 50 repetitive bursts of
frames with minimum inter-frame gap (line rate) according to the
test settings. For this test to be successful, the network being
tested 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:

Ethertype.

with loopback devices based on the MAC-address swap .

network.
Layer-3 generic: Layer-2 frames with a generic Layer-3 (UDP)

payload. Only to be used with OAM loopback devices with no IP
address swapping. This mode will work with or without MAC
swapping.
traffic only.

Range: 0–7
Y.1731.

Source IP Address The source IP address used for the IP header. Applies to Layer-3
generic and IP multicast traffic only.
Notes:
Layer-3 generic traffic is available for the RFC-2544 traffic
generator and test suite. It is unavailable for Y.1564 SAT.
IP multicast traffic is available for the RFC-2544 traffic generator. It
is unavailable for the RFC-2544 test suite and Y.1564 SAT.

report.
Notes:

TWAMP.
Layer-3 Y.1564.
SAT Protocol.
TTL The Time To Live (TTL) of the packets transmitted on the flow.
Note: Applies to layer-3 type tests only.
Header

VLAN ID.

Type
VLAN (0x8100)
VLAN (0x88A8)
VLAN (0x9100)

convenience.



Enable VLAN 2 Encapsulates all frames with two VLAN headers (as in Q in Q ).
Header
VLAN1 must be enabled to use two VLAN headers.

Type
VLAN (0x8100)
VLAN (0x88A8)
VLAN (0x9100)
The Ethertype assocaited with the value selected in the drop-down

list is displayed in a read-only text box for your convenience.


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 ( 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 12 Mbps). 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.
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.
the test.
Back-to-Back Settings
Trial Duration The period of time over which the test is run.
Range: 1 to 10000 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
the test.

13.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.
Test suite 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 349.
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.

13.4 Using Y.1564 for Service Activation Testing

Y.1564 is used to perform end-to-end Ethernet service activation tests (SAT). The following
sections describe how to set up Y.1564 in your Metro Ethernet network.
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: For details on how to set up a Y.1564 test, see Setting Up a Y.1564
Test on page 350.
Set up one or more Y.1564 services: For details on how to set up a Y.1564 service, 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 359.
13.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, FTPS, 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 323.
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 GX Performance Elements contain 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 flow(s).
Test to Run
Configuration Step The duration, expressed in seconds, of each step during the
Duration (Seconds) configuration test.
Note: This parameter is also used for the burst SLA Test
Enable Configuration Enabling the configuration test allows use of the policing test and
Test 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.
Enable burst SLA Enable or disable the burst SLA test.

Test
(Default is disabled)
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 enabled, the tests will be performed only if both
Mandatory devices performing the Y.1564 test are synchronized using one of
the supported timing mechanisms (NTP or PTP).
When this option is disabled, 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:

Ethertype.

with loopback devices based on the MAC-address swap .

network.
Note: Layer-2 generic is for two-way measurements only.

traffic only.

Range: 0–7
Y.1731.

report.
Notes:

TWAMP.
Layer-3 Y.1564.
SAT Protocol.
13.4.2 Setting Up a Y.1564 Service

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.1564 [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.
Name Name of the Y.1564 service.
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 1250 Mbps (steps of 0.125 Mbps)
Committed Burst Size The maximum number of kibibytes available for a burst of frames

(in KiB) (1024 bytes) that are sent at the port's speed and remain CIR conformant.
Range: 0 to 10000 KiB
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 1250 Mbps (expressed in steps of 0.125 Mbps)
Excess Burst Size (in This parameter is not currently used and is grayed out. This is for
KiB) (1024 bytes) future implementation only.
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 the 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 of the outgoing portThe 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.
u = user-defined size

Default value: abceg
Service Acceptance Criteria
Frame Transfer Delay For one- or two-way delay measurements, the delay below which
(in μs) 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 the
Type 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 the
Variation Type 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)
MAC Destination 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.
MAC Address
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 Y.1564
MEG Level test.
IP Settings (Layer-3 Traffic Only)
Destination IP For each service, this sets the destination IP address and overwrites
Address the global IP address of the Y.1564 test.

Overwrite Per Test Enable the overwriting of the global destination IP address of the
Destination IP 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
Header
Enable or disable VLAN 1 header.
This encapsulates all frames with one VLAN header.
If the VLAN 1 header is enabled, the packet size increases by 4
bytes. For example:
If the packet size set to 64 and the VLAN 1 header is not

enabled, the traffic generator will send packets of 64 bytes.
If the packet size is set to 64 and the VLAN 1 header is enabled,
the traffic generator will send packets of 68 bytes.

VLAN ID.


Enable VLAN 2 Enables or disables the VLAN 2 header.

Header
Encapsulates all frames with two VLAN headers (as in Q in Q ).
In order to use two VLAN headers, both VLAN 1 and VLAN 2
headers must be enabled.
If VLAN 1 and VLAN 2 headers are both enabled, the packet size
increases by 8 bytes. For example:
If the packet size set to 64 and both VLAN 1 and VLAN 2

headers are enabled, the traffic generator will send packets of
72 bytes.



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 enabled.
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
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
Value option is enabled.
DEI Check Check this option if you want the peer unit to verify that the DEI
will fail.
DEI Unpreserve Check this option if you expect the DEI value to change before it
Far-End Expected The value expected by the far-end when the DEI unpreserve option

Value is enabled.
VLAN ID Check Check this option if you want the peer unit to verify that the
VLAN ID for the test traffic has not changed. If it has changed, the
test will fail.
ID Unpreserve Check this option if you expect the VLAN ID to change before it
Far-End Expected The value expected by the far-end when the ID unpreserve option
Value is enabled.
13.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 current status of the test.

Passed: The test has been successfully executed.

Failed: An error occurred during the test execution.
Running: The test is currently running.
Cancelled: A user stopped the test during its execution.
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 current status of the test.

50% CIR Possible values are:
75% CIR PASS: This test passed the test criteria.
100% CIR FAIL: This test failed the test criteria.
CIR+EIR N/A: This test is not performed per the test configuration.
Policing
Performance
CBS
State Enabled or disabled state of a service within this Y.1564 test.

13.5 Using the SAT Protocol

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.
13.5.1 Setting Up the SAT Protocol

▶ To set up the SAT protocol
1. Access the page SAT ▶ Protocol ▶ Configuration.

SAT Protocol Configuration (SAT ▶ Protocol ▶ Configuration)

Enable Enable or disable the server side of the SAT protocol (Enabled by
default).
Note: The SAT protocol 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 The destination UDP port used for one-way traffic
UDP 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.

13.5.2 Viewing SAT Protocol Statistics

Viewing the statistics of the SAT protocol can be useful when troubleshooting.
▶ To view SAT protocol statistics
1. Access the page SAT ▶ Protocol ▶ Statistics.

Statistics for the SAT protocol server are displayed in a grid.
Tip: To reset the current statistics to zero, click the Clear button above the grid.
Note: Select the Poll Every n Seconds box, then enter a number representing
the frequency with which the statistics will be automatically refreshed. You can
also update the statistics manually by clicking the Refresh button.
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 The number of release acknowledgements sent or received

Acknowledge
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.

13.5.3 Viewing SAT Protocol 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 SAT protocol sessions
1. Access the page SAT ▶ Protocol ▶ Sessions.

Details on all current SAT protocol sessions are displayed in a grid.
The total number of sessions found in the system is given in the lower-left corner of the
page, as well as the index values of the sessions currently displayed on-screen (for
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

14. Loop Detection
This chapter describes how to configure and use the loop detection feature to detect loops at
the link and tunnel level; it contains the following sections:
14.1 About Loop Detection 366
14.2 Configuring a Loop Detection Instance 367
14.3 Viewing Loop Detection Instance Details 370
14.4 Viewing Loop Detection Counter Instances 372
14.5 Viewing Loop Detection Global Counters 374
14.6 Managing the Loop Detection Diagnostic Tool 375

14.1 About Loop Detection

The loop detection feature enables you to detect the presence of loops in an OLO network,
either at the port (link-level loop detection) or the tunnel level (tunnel-level loop detection).
Use it to determine if there are any untagged frames on a network or if a loop is present in a
specific VLAN. Loop detection on UNI, ENNI and INNI interfaces is supported.
Any loops that are detected are reported through SNMP traps (i.e., alarms) that can be
viewed in the Show ► Alarm page of the management Web interface. One alarm entry is
created for each loop detection instance, which can be individually configured in the System
► Alarm ► Configuration page.
You can also test for loopbacks manually and using the Loop Detection Diagnostic Tool.
The design of the loop detection feature involves certain limitations. A loop detection instance
can be created on physical and logical ports, but not on LAG ports:
If a loop detection instance is created on a physical port, the LAG port containing the
physical port cannot be activated using LACP or Link Status protection.
If a loop detection instance is created on a logical port, the protection mode must be set
to LACP or Link-Status. If a protection mode is enabled, the loop detection instance
must be disabled before the protection mode can be disabled.
If a LAG port is enabled, a loop detection instance cannot be created on a port that is
part of that LAG port.
Furthermore, ERP protection mode is not supported with loop detection:
If a loop detection instance is created on a logical port with LACP or Link Status
protection mode, and the port configuration is subsequently changed to ERP protection
mode, the loop detection instance will be disabled.
If a loop detection instance is created on a physical port with the LAG port activated
using ERP protection mode, the loop detection instance will be disabled.

14.2 Configuring a Loop Detection Instance

Loopbacks are frequently introduced in a network to assist with provisioning and
troubleshooting. However, network loops can also have serious disruptive effects on the
network including a loss of management connectivity. The loop detection feature is helpful
when you must quickly identify the presence of loops at either the port or the tunnel level of
the network.
If loop detection detects the presence of a loop on the network, the traffic flow on the
incoming port affected by the loop can be blocked (i.e., squelched). You can configure the
blocking functionality to block and/or unblock traffic automatically whenever a loop is
detected, or you can block or unblock traffic manually. If a traffic block was in effect when a
loop detection instance is disabled or deleted, the block is also cleared at the same time. In
contrast, if you recreate or enable the loop detection instance at a later time, the traffic block
is not automatically reapplied.
Use this page to manage loop detection instances, including the loop detection traffic block
capability.
▶ To set up a loop detection instance
1. Access the page Loop Detection ► Configuration ► Instances.

A summary of all loop detection instances that have been configured is displayed. The
total number of instances found in the system is given in the lower-left corner of the
2. Click Add to add a new loop detection instance, or click the Name of an existing loop
detection instance to edit its settings.
3. Complete the required fields, then click Add for a new loop detection instance or Apply
for an existing loop detection instance.
Loop Detection Configuration (Loop Detection ► Configuration ► Instances)

Index The unique identifier assigned to the loop detection instance once it
has been created. You cannot modify this value.
Note: The system supports up to 100 tunnel-level loop detection
instances, in addition to one loop detection instance per port.
Type Make a selection from the drop-down list to indicate the type of
loop to detect.
Link: Creates a loop detection instance on either a physical or a

logical port
Tunnel: Creates a loop detection instance to poll an OLO for
either untagged frames (no VLAN) or loops on a specific VLAN
Resource The name of the physical/logical port or interface polled by this loop
detection instance is provided here.
Port Make a selection from the drop-down list to select the physical port
on which to listen for loops.
The port assigned to a loop detection instance cannot be modified
after you click Apply.
A maximum of one loop detection instance can be created per port.
Notes: Applies to link-level loop detection instances only.
A loop detection instance can be created on physical and logical
ports, but not on LAG ports. See "Loop Detection" on page 365 for
other considerations related to the behavior of port-level loop
detection instances.
Interface Make a selection from the drop-down list to select the interface on
which to poll for loops.
UNI, ENNI and INNI interfaces are all supported; however, only the
interfaces whose type is VLAN will appear in the drop-down list.
Note: Applies to tunnel-level loop detection instances only.
Name Enter a name to identify the loop detection instance. A maximum of

31 alphanumeric characters is supported.
The name you enter can contain alphanumeric characters, spaces or
special characters such as underscores and asterisks.
Enable Select this box to activate this loop detection instance
Interval(s) Indicate the interval at which the loop detection instance will poll
the specified resource for the presence of loops by sending a
beacon, expressed in seconds.
Minimum value: 1 (link level) or 2 (tunnel level)
Maximum value: 30
Default value: Same as minimum value
Note: In the summary screen, this value is displayed for your
convenience; you cannot modify this value here.
State Whether or not this loop detection instance is currently active is

indicated here. To modify this value, you must open the loop
detection instance directly.
Auto Block Select this box to enable the auto-block mechanism

When the auto-block mechanism is enabled, traffic is automatically

blocked within one second upon the detection of a loop on this port
or tunnel.
Revertive Select this box to enable revertive mode for the auto-block
mechanism
When revertive mode is enabled, traffic is automatically unblocked
within one second of a loop on this port or tunnel being resolved.
▶ To delete a loop detection instance
1. Access the page Loop Detection ► Configuration ► Instances.

A summary of all loop detection instances that have been configured is listed in a grid.
For more information on specific parameters, refer to the table above.
2. Select the loop detection instance to delete from the list by clicking its Name.
The Loop Detection Configuration page opens, with the loop detection instance’s
details displayed.
3. Click Delete.
The selected loop detection instance is permanently deleted; you are not prompted to
confirm your actions. The system returns to the listing of loop detection instances on
the previous page.

14.3 Viewing Loop Detection Instance Details

Use this page to view the status of the loop detection instances created on the unit, whether
enabled or disabled.
▶ To view the status of all loop detection instances
1. Access the page Loop Detection ► Status.

2. Click the Name of an existing loop detection instance to view its detailed status.
The Loop Detection Status page opens.
frequency with which the loop detection instance’s status will be automatically
refreshed. You can also update the status manually by clicking the Refresh button.
Loop Detection Status (Loop Detection ► Status)

Index The unique identifier assigned to the loop detection instance. You
cannot modify this value.
Name The name used to uniquely identify the loop detection instance
State The state of this loop detection instance. Acceptable values are
either Enabled or Disabled .
Operational State The operational state of this loop detection instance. Acceptable
values are either Enabled or Disabled .
Type The type of loop detection instance.

Link: A loop detection instance that polls either a physical or a

logical port
Tunnel: A loop detection instance that polls an OLO for either
untagged frames (no VLAN) or loops on a specific VLAN
detection instance

VLAN ID The VLAN ID on which the loop detection beacon was sent
Loop Detected Whether or not a loop has been detected by this instance.
If a loop has been detected on this resource, three consecutive
beacons must indicate that the loop has been resolved in order for
this value to revert back to No.
Latest Loop Detected The timestamp (for example, 2016-02-17 15:47:11+00:00) of the most
Time recent beacon that detected the presence of a loop on this resource.
This value will continue to update, at the specified interval, until the
loop is resolved.
Round-Trip Time The loop detection beacon’s round-trip time, expressed in

(usec) microseconds.
Auto Block Whether or not the auto-block mechanism has been enabled for
this loop detection instance
When the auto-block mechanism is enabled, traffic is automatically
blocked within one second upon the detection of a loop on this
resource.
Revertive Whether or not the auto-block mechanism's revertive mode has

been enabled for this loop detection instance
When revertive mode is enabled, traffic is automatically unblocked
within one second of a loop on this resource being resolved.
Traffic Blocked Whether or not the traffic flow associated with this loop detection
instance is currently being blocked, regardless of whether the block
was manually or automatically applied

14.4 Viewing Loop Detection Counter Instances

Use this page to view the statistical counters that provide an overview of the loop detection
instances created on the unit.
▶ To view the counters of all loop detection instances
1. Access the page Loop Detection ► Counters ► Instances.

2. (Optional) To clear the counters for all loop detection instances at the same time, click
the icon on the right side of the table header.
3. Click the Name of an existing loop detection instance to view its counters' details.
frequency with which the loop detection instance’s counters will be automatically
refreshed. You can also update the counters manually by clicking the Refresh button.
Click the Clear button to reset all counters for this loop detection instance to zero.
Loop Detection Counters (Loop Detection ► Counters ► Instances)

Index The unique identifier assigned to the loop detection instance. You
cannot modify this value.
Name The name used to uniquely identify the loop detection instance
State The state of this loop detection instance. Acceptable values are
either Enabled or Disabled .
Type The type of loop detection instance.

Link: A loop detection instance that polls either a physical or a

logical port
Tunnel: A loop detection instance that polls an OLO for either
untagged frames (no VLAN) or loops on a specific VLAN
detection instance

Sent Frames The total number of loop detection beacons that have been
transmitted by this instance, but have not returned.
This value is calculated for the period since either the loop detection
instance was created or since the counters were last cleared,
whichever is more recent.
Received Frames The total number of loop detection beacons that have been
transmitted and received by this instance.
Note: The number of received frames does not always equal the
number of loop detected frames. A frame could be received for
reasons other than a detected loop, such as a change of VLAN ID.
Loop Detected The total number of loop detection beacons transmitted by this
Frames instance that have successfully detected a loop on the specified
resource.

14.5 Viewing Loop Detection Global Counters

Use this page to view combined statistical counters that provide an overview of all loop
detection instances on the unit combined.
▶ To view a global summary of all loop detection counters
1. Access the page Loop Detection ► Counters ► Global.

The Loop Detection Global Counters page opens. The combined statistics for all
existing loop detection instances are displayed.
Notes: To reset the counters for all loop detection instance to zero, click the
Clear button above the grid.
Select the Poll Every n Seconds box, then enter a number representing the
frequency with which the loop detection instance’s counters will be
automatically refreshed. You can also update the counters manually by clicking
the Refresh button.
Loop Detection Global Counters (Loop Detection ► Counters ► Global)

Sent Frames The total number of loop detection beacons that have been
transmitted by this instance, but have not returned.
Received Frames The total number of loop detection beacons that have been
transmitted and received by this instance.
Note: The number of received frames does not always equal the
number of loop detected frames. A frame could be received for
reasons other than a detected loop, such as a change of VLAN ID.
Loop Detected The total number of loop detection beacons transmitted by this
Frames instance that have successfully detected a loop on the specified
resource.

14.6 Managing the Loop Detection Diagnostic Tool

Use this page to create a manually-controlled, customized loop detection beacon, then view
its results.
Note: The loop detection diagnostic tool does not require an interface to be
created in order to send a tunnel-level beacon.
▶ To configure a customized loop detection beacon
1. Access the page Loop Detection ► Diagnostic Tool.

The Loop Detection Diagnostic Tool page opens.
2. Use the information in the table below to configure the loop detection beacon, then
click Send.
A loop detection beacon is transmitted from the specified port; Frame is successfully
sent appears in the frame at the bottom of the page. If no loop is detected within the
period specified timeout value, it will expire.
3. To view the results of the loop detection beacon created in the previous step, click
Show.
The frame at the bottom of the page refreshes with the loop detection beacon’s results.
Results will appear similar to the following:
Beacon Type : LPDB
Status : Received
Port : PORT-4
Vlan1 Id : 100
Vlan1 Ethertype : T-VLAN
Vlan2 Id : 200
Vlan2 Ethertype : S-VLAN
Vlan3 Id : 300
Vlan3 Ethertype : C-VLAN
Timeout (s) : 3
Round trip time (usec) : 40
Loop Detection Diagnostics (Loop Detection ► Diagnostic Tool)

Port Make a selection from the drop-down list to select the physical port

on which to listen for loops.
Direction This parameter is not currently used. For future implementation.
Timeout Expressed in seconds. Acceptable values range from 3 to 30.
VLANn Enable Select this box to enable VLAN for a tunnel-level loop detection
beacon. You can select up to three VLAN .
Ethertype Make a selection from the drop-down list to select the Ethertype for
its associated VLAN ID.
C-VLAN: 0x8100
S-VLAN: 0x88A8 (or 0x9100) Refer to the global setting for S-
VLAN Ethertype under System ▶ Configuration ▶ Mode
T-VLAN: 0x9100 (or 0x88A8, depending on the value assigned
to the S-VLAN Ethertype)
VLAN ID The VLAN ID on which the loop detection beacon will be sent

15. Managing Loopbacks
This chapter describes how to manage loopbacks; it contains the following sections:
15.1 Understanding Loopback Testing 378
15.2 Setting Up and Enabling Loopbacks 379

15.1 Understanding Loopback Testing

Layer 1–4 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-controlled loopback: Loops back traffic and is initiated upon the reception
of a predefined frame type (JDSU/Acterna™, Sunrise™)

15.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 152
Create an OAM instance, see Setting Up an OAM Instance on page 238
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 OAM instances 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: When selecting Loopback Enable and/or Drop Opposite Traffic, the
following message will be displayed "Configuration changes are service
affecting. Are you sure you want to proceed?". Click OK to proceed with your
changes or Cancel to go back to the previous screen.
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
Port Make a selection from the drop-down list to indicate the port on
which the loopback will be created.
State The current state of the loopback. An enabled loopback may not
necessarily loop back traffic; this depends on the location setting.
An instance enabled for a remotely-controlled 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 controlled 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-controlled 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-controlled loopbacks with
no timeout.
Filter Type The type of filter to be applied to the loopback traffic:
L2 Filter
IPv4 Filter
IPv6 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

IPv6 Filter The IPv6 filter to be applied to loopback traffic, if the filter type is
IPv6 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
controlled 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
controlled by a Sunrise™ device.
The unit supports tests on Layer 2 and Layer 3.
VeEX™ Select this box to indicate that this remote loopback will be
controlled by a VeEX™ device.
The unit supports tests on Layer 2, Layer 3 and Layer 4.
OAM 802.3ah Select this box to indicate that this remote loopback will be
controlled by a device that supports the OAM 802.3ah protocol.
Accept Tagged Select this box to indicate that this remote loopback will accept
Loopback Commands tagged loopback commands.
This option is only valid for untagged OAM instances. Tagged OAM
instances only accept loopback commands from a specific VLAN.

16. Managing Alarms and System Messages
This chapter describes functions related to alarms and system messages; it contains the
following sections:
16.1 Managing Alarms 383
16.2 Viewing Dry-Contact Alarms 398
16.3 Managing Syslog Messages 399
16.4 Managing the SNMP Agent 402
16.5 Managing the Netconf Agent 405
16.6 Managing History Files 406

16.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.
16.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 Enables the reporting of alarms by activating the appropriate LED
Reporting on the unit 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 Accedian’s
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 notification
(Soaking time in occurs.
msecs)
Threshold Off The delay after an event clears before the alarm notification clears.
(Soaking time in
msecs)
16.1.2 Customizing Alarms

▶ To customize an alarm
1. Access the page System ▶ Alarm ▶ Configuration.

The settings for all alarms are displayed.
2. Click the Number of the alarm that you want to edit.

The Alarm Configuration page appears.
3. Complete the required fields , then click Apply.
Note: If you modify an alarm's configuration, then decide to discard those

changes, click Reset to revert to the last set of saved configuration values. Once
you click Apply, however, you must manually restore the previous configuration
values.
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, Frame Loss and
other related alarms
4: SOAM module for Continuity Check, Delay, Packet Loss and
other related alarms
5: Unassigned
6: SyncE
7: System modules, such as NTP and other agents
8: Environmental module for power supplies, temperature
sensors and dry contact
9: ERP module
10: Unassigned
11: TWAMP
12: Unassigned
13: Loop detection
14: Unassigned

15: Unassigned
16:Unassigned
17: Unassigned
18: Advertisement Inventory Alarm
Enable Indicates whether the alarm is enabled (true) or disabled (false). If

enabled, alarms are reported.
Severity The severity of the alarm.
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.
If LED reporting is enabled in the Alarm ▶ General page, the Minor,

Major and Critical alarms are indicated on the unit's front panel
LEDs.
Service Affecting Alarms may be displayed as true for service affecting or as false for
non-service affecting.
Description Textual description of the alarm. The description is displayed in the

Show ▶ Alarm page.
Note: This description cannot be modified.
16.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)
Presence Indicates whether the alarm is currently present (true) or not

(false).
Severity The severity of the alarm. Possible values:
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 Indicates whether the alarm affects the unit's ability to provide
service.
Possible values:
yes: The alarm is Service Affecting (SA)

no: The alarm is 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: GX 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

Loopback on port TRAFFIC-1-1

Loopback on port TRAFFIC-1-2
1.0007.02 Loopback on PORT-7 port

Link down on TRAFFIC-2-2 port
1.0008.02 Loopback on PORT-8 port
1.0009.01 Link down on LAG-1 port

1.0009.02 Loopback on LAG-1 port
1.0009.03 Sub-port speed mismatch on port LAG-1
1.0009.04 Fault propagation caused link down on port LAG-1
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 (GX model) and where 0001 = SFP-1, 0002 = SFP-2, 0003 = SFP-3 [...] 0007 = SFP-7,
0008 = SFP-8 (GX-S model).
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>, port
4.zzzz.15 Excessive packet loss on down MEP, MEPID <ID>, port <port name>,
VID <ID>, level <#>
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>,
port <port name>, VID <ID>, level <#>
4.yyyy.20 Excessive SLM far-end packet loss on down MEP, MEPID <ID>, port

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 modules, such as the Vision Collect Agent, 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 Vision 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 SOAM PL 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
7.0004.28 VCAgent SFP statistics buffer full
7.0004.29 VCAgent System Health statistics buffer full
NE Alarms
8.0000.80 Troubleshooting tool is running

Note: This alarm is raised when either a either a troubleshooting
tool is running or the Remote Syslog feature is enabled. The alarm is
cleared only when both (troubleshooting tool and Remote Syslog
feature) are disabled.
Environmental module for power supplies, temperature sensors and dry contact
8.0000.70 Input 1 Active
8.0000.71 Input 2 Active
8.0001.20 Power feed A not present alarm
8.0001.30 PCB temperature sensor not present alarm
8.0001.31 PCB high-temperature warning
8.0001.32 PCB high-temperature alarm
8.0001.40 Fan 1 not present alarm
8.0001.41 Fan 1 fan-stall alarm
8.0001.42 Fan 1 fan-aging warning
8.0001.43 Fan 1 fan-aging alarm
8.0002.20 Power feed B not present alarm

8.0002.30 CPU temperature sensor not present alarm
8.0002.31 CPU high-temperature warning
8.0002.32 CPU high-temperature alarm
8.0002.40 Fan 2 not present alarm
8.0002.41 Fan 2 fan-stall alarm
8.0002.42 Fan 2 fan-aging warning
8.0002.43 Fan 2 fan-aging alarm
8.0003.30 FPGA temperature sensor not present alarm
8.0003.31 FPGA high-temperature warning
8.0003.32 FPGA high-temperature alarm
ERP module
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
TWAMP Generator 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
Loop Detection feature

In this section, xxxx = Loop Detection instance index.
13.xxxx.01 Loop detected on Link/Tunnel instance x
13.xxxx.02 Traffic discarded because of loop detection on instance <Loop

detection name>
13.xxxx.03 Loop detection instance <Loop detection name> not operational

Advertisement Inventory Alarm module
18.0001.01 Inventory entries list is almost full
18.0001.02 Inventory entries list is full

Certificate Alarms
19.0000.01 One or more certificates is about to expire
19.0000.02 One or more certificates has expired
▶ 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 385.
16.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 Supply
Power Feed A and The status of the various power sources for AC or DC (AUX), Feed A
Power Feed B 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 (AUX) 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
Front/Back PCB and The following information is provided for each sensor (Front/Back
FPGA Temperature PCB and FPGA):
Sensors
Status: Either Present or Not Present
Alarm: Set to In Alarm (if an alarm has been triggered) or None
Temperature: The most recent temperature detected by the
sensor, expressed in Celsius
High-Temperature Warning: The temperature that triggers an
overheating warning, expressed in Celsius
High-Temperature Alarm: The temperature that triggers an
overheating alarm, expressed in Celsius
Low-Temperature Warning: The temperature that triggers a
low-temperature warning, expressed in Celsius
Low-Temperature Alarm: The temperature that triggers a
low-temperature alarm, expressed in Celsius
For details on any alarms or warnings, access the page Show ▶

Alarm.
Fan Monitors
Fan 1 and Fan 2 For each fan on the unit (identified as 1 or 2), the following
information is provided:
Status:

Present: The fan is connected.

Not Present: The fan is not connected.
Alarm:
In Alarm: An alarm has been triggered for this fan.

None: No alarm has been triggered for this fan.
Speed:
This the number of rotations per minute made by the fan,

expressed in RPM.
The following threshold information is provided for each fan:
Fan-Stall Alarm: This is the fan speed at which the fan stall
alarm is triggered, indicating that the fan is no longer
functioning. Expressed in RPM.
Fan-Aging Warning: This is the fan speed at which the fan
aging warning is triggered, indicating that the fan is no longer
functioning optimally. Expressed in RPM.
Fan-Aging Alarm: This is the fan speed at which the fan aging
alarm is triggered. Expressed in RPM.
For details on any alarms or warnings, access the page Show ▶

Alarm.
16.1.5 Performing a Fan Test

▶ To perform a fan test
1. Access the page System ▶ Alarm ▶ Chassis.

The chassis alarms' status is displayed.
2. Click the Start button to immediately initiate a fan test.

The latest results for both Fan 1 and Fan 2 are displayed.
Note: The fan test retry period can be modified by changing the value in the
"Retry period (hours)" field.
For more information on specific parameters, refer to the table below.
Fan Test (System ▶ Alarm ▶ Chassis)

Start button Clicking on the Start button will initiate a fan test immediately.

Retry period (hours) 1 to 24. Default is 1 hour. If a fan test fails, this value will be used to
set the retry period of the fan test.
Latest Results Shows for both fans if the test passed or failed. If the test failed, the
rpm will be shown as well.

16.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

16.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.
16.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)

Facility Configuration
Device Facility The device facility to log all messages using this user-defined
facility instead of the default ones.
Level Configuration
Level Threshold Configure the level threshold for syslog. All messages with a level
greater than or equal to the selected one will be logged. For
example, setting the priority threshold to DEBUG (lowest priority)
causes all messages to be logged.
Emergency (1)
Alert (2)
Critical (3)
Error (4)
Warning (5)
Notice (6)
Info (7)
Debug (8)
Remote Syslog Configuration

Remote Syslog Select this box to enable sending messages to a remote syslog
Enable server.
When Remote Syslog is enabled, the following alarm is raised:
Alarm ID: 8.0000.80
Severity: Major
Service Affecting: No
Description: Troubleshooting tool is running.
Note: This alarm is raised when either a either a troubleshooting
tool is running or the Remote Syslog feature is enabled. The alarm is
cleared only when both (troubleshooting tool and Remote Syslog
feature) are disabled.
Host The IP address or domain name of the remote syslog server.

Remote Level Configuration
Level Threshold Configure the level threshold for remote syslog. All messages with a
level greater than or equal to the selected one will be logged. For
example, setting the priority threshold to DEBUG (lowest priority)
causes all messages to be logged. Available levels are:
Emergency (1)
Alert (2)
Critical (3)
Error (4)
Warning (5)
Notice (6)
Info (7)
Debug (8)
The default level for the remote syslog is Notice.

16.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) on page 399.

16.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.
16.4.1 Enabling the SNMP Agent

The SNMP Agent is used to generate SNMP traps and to provide OID information. Use the
System ▶ Agent ▶ SNMP page to configure how the SNMP agent is enabled.
Some SNMP queries can require an extended period of time to execute fully, due to the large
quantity of data to provide. If your SNMP MIB browser times out while walking through the
MIB tables, consider increasing the timeout value to at least 10 seconds. Extending the
timeout value will allow the SNMP Agent to serve the request instead of timing out and
retrying until the configured number of retries is exhausted. It will reduce the amount of
SNMP traffic going through your network.
Note: Only Netconf or SNMP (not both) can be enabled at the same time.
▶ To enable the SNMP agent
1. Access the page System ▶ Agent ▶ SNMP.

SNMP Agent (System ▶ Agent ▶ SNMP)

Enable Agent Enables the unit’s 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 unit's fully-
qualified domain name.
Contact Information Contact information for the unit (typically an email address).
System Location Physical location of the unit.
Agent UDP Port UDP port that the SNMP agent uses for all 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 used to control read/write access to the unit.

Community
Enable Enables the unit to generate a trap when authentication of the

Authentication Trap agent fails.
Generation
Enable Link Trap Enables trap generation when the link status changes.
Generation
Maps to 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).
16.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 the conditions of many units.
Note: The SNMP agent must be enabled before you can configure and use the
SNMP Trap Receiver.
The unit can be configured to send SNMP v1 traps to one or two receivers, and to send SNMP
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 Guide 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 The state of this SNMP trap: Enabled or Disabled .
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 traps
and/or notifications.
Host Name
The unit sends a Cold Start trap when starting up.
Community String The community string required to send traps to the notification
receiver.
Community
Host UDP Port The UDP port used by the unit to send traps to the notification
receiver.
UDP Port
The widely used SNMP trap port 162 is the default port.

16.5 Managing the Netconf Agent

You can configure a Netconf agent so users with a Netconf client can get or edit
configuration and get notifications from the unit via the Netconf protocol.
▶ To enable the Netconf agent
1. Access the page System ▶ Agent ▶ Netconf.

Netconf Agent (System ▶ Agent ▶ Netconf)

Enable Agent Enables the unit's Netconf agent

16.6 Managing History Files

You can manage the creation and transfer of history files, which are logs that contain
statistics related to the services (for example, PAA, Regulator, Policy, CFM DMM, CFM PL, CFM
SLM, Service Availability, Service Availability Metrics, TWAMP Generator, Shaper, Port, SFP,
System Health) for which the history feature has been enabled.
You can configure the unit to transfer its history files to a server.
Notes: 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 afterward. 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.
16.6.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 (NVM). 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
SFP
System Health
Period (mins) Indicate the frequency at which the history statistics will be collected,
expressed in minutes. Acceptable values range from 1 and 60.

16.6.2 Transferring History Files

▶ To enable the transfer of history files
1. Access the page System ▶ Agent ▶ History.
2. Customize when the history files will be scheduled by completing the fields in the
Scheduling section of the Scheduling and File Transfer Configuration frame.
3. Provide the URL where the file transfer server is located and the SCP password in the
File Transfer section of the Scheduling and File Transfer Configuration frame.
4. 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 Check this box to enable automatic transfer of history buckets report
files from the unit to a server. The details of the scheduler and server
are configured in this page.
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 time.
Note: Finer granularity is possible using the Hourly Minutes or
Periodic Minutes field, in combination with the Schedule Offset
field.
Scheduling Mode Select a value from the drop-down list to set the type of interval that
will be used for history bucket file transfers:
Hourly: Allows you to select file transfers on the quarter-hours. If

you select Hourly, use the Hourly Minutes checkboxes
(described below) to determine when the file will be transferred
each hour.
Periodic: Allows you to choose from a wider range of interval
values for file transfers. If you select Periodic, use the Periodic
Minutes drop-down list (described below) to determine how
often you want to transfer the files.
Hourly Minutes Use this feature to set the scheduling to trigger every 15 minutes,
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 Select a value from the drop-down list to set the scheduling trigger
interval.
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 Enter a value in this to set the number of minutes by which to offset
file transfers.
Hourly: Acceptable values range from 0 to 14

Periodic: Acceptable values range from 0 to (Periodic Minutes - 1)
This field allows 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 0 minutes, 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
4 minutes, 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
2 minutes, 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 add a random number of seconds to the
number of minutes entered in the Schedule Offset field.
Adding a random offset allows multiple units to send reports to the
same server at slightly different times. This relieves the load that
would be created by several concurrent transfers.
The combined value of the schedule offset and random offset cannot
exceed 15 minutes (900 seconds) in Hourly mode or the value of
Periodic Minutes in Periodic mode. If the sum of the schedule offset

and the 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.
Note: The following special characters are not allowed in the URL
input: "<", ">", "\n", "\r", "\t".
Examples:
http://example.com
ftp://username:[email protected]
ftps://username:[email protected]
sftp://[email protected]/24
tftp://192.0.2.0/24
scp://[email protected]/24:/target_directory
scp://username@[2001:DB8::/32]:/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
unit 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.
Number of Periods: Specifies the number of local periods to
process in fixed mode.
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.

GX v7.8.3 Performance Element User Manual

Uploaded by

Copyright:

Available Formats

GX v7.8.3 Performance Element User Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GX v7.8.3 Performance Element User Manual

Uploaded by

Copyright:

Available Formats

User Manual

Revision 1 — August 16, 2019

Revision 1 — Publication date: August 16, 2019

Accedian products are protected by patents as indicated on the Accedian website at

Revision 1 — August 2019 2

1. About This Manual 9

2. Introduction to the GX Performance Element 13

Revision 1 — August 2019 3

3.11 Managing Access Control Lists 60

4. Configuring Plug & Go 64

5. Configuring the Unit 76

Revision 1 — August 2019 4

5.14 Viewing CPU Usage 110

6. Managing Ports 117

7. Managing Traffic 149

8. Setting Up Protection 209

Revision 1 — August 2019 5

8.1.1 Switching to the Standby Port 211

9. Managing Virtual Connection Endpoints (VCEs) 222

10. Managing Virtual Connection Access (VCAs) 232

11. Monitoring Network Performance with Ethernet OAM 237

12. Monitoring Network Performance with Service OAM 250

Revision 1 — August 2019 6

12.2.9 Viewing Delay Measurement Results 290

13. Testing Network Performance 322

Revision 1 — August 2019 7

13.5.2 Viewing SAT Protocol Statistics 363

14. Loop Detection 365

15. Managing Loopbacks 377

16. Managing Alarms and System Messages 382

Revision 1 — August 2019 8

1. About This Manual

Revision 1 — August 2019 9

"Managing the Unit"

Revision 1 — August 2019 10

CAUTION: Describes a situation where failure to take or avoid a specified action

IEEE 802.1ag – Connectivity Fault Management

Revision 1 — August 2019 11

Technical Specification MEF 10.2 – Ethernet Services Attributes – Phase 2

Revision 1 — August 2019 12

2. Introduction to the GX Performance Element

The GX Performance Element is a 1 GbE platform based on Accedian‘s all-hardware Fast-

Revision 1 — August 2019 13

3. Managing the Unit

This chapter contains the following sections:

3.1 About the Management Web Interface 15

3.2 Starting the Management Web Interface 17

3.3 Configuring Logical Interfaces 25

3.4 Finding a Host (Ping and Traceroute) 37

3.5 Using the Serial Console 38

3.6 Managing the Link Layer Discovery Protocol (LLDP) 40

3.7 Managing Sessions 44

3.8 Managing Users and Privileges 49

3.9 Using a RADIUS Server for Authentication 55

3.10 Using a TACACS+ Server for Authentication 57

3.11 Managing Access Control Lists 60

3.12 Managing OS Services 63

Revision 1 — August 2019 14

3.1 About the Management Web Interface

Revision 1 — August 2019 15