EtherNID™

Administrator’s Guide
for the

EtherNID™ EE
EtherNID™ GE
MetroNID™ TE
MetroNID™ TE-R

1
Release 4.1.1 (September 2008)

Accedian Networks, EtherNID, EtherSHELF, MetroNID and Performance Assurance Agent (PAA) are trademarks of Accedian Networks
Inc.
All other brand and product names are trademarks or registered trademarks of their respective corporations.
The mention of any product does not constitute an endorsement by Accedian Networks Inc.
The content of this manual is furnished 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 prior written consent of Accedian
Networks Inc.
Changes are periodically made to the information herein; these changes will be incorporated into new editions of this publication.
Accedian Networks Inc. may make improvements and/or changes in the products and/or software programs described in this publication
at any time.
If you have comments on this manual or the products it describes, address them to:
Accedian Networks Inc.
Attention: Publications
4878, Levy street, Suite 202
Saint-Laurent, Québec
Canada
H4R 2P1
Tel: (514) 331-6181
Fax: (514) 331-2210
Toll free: 1-866-685-8181
Accedian Networks Inc. may use or distribute whatever information you supply in any way it believes appropriate without incurring any
obligations to you.
Copyright © 2005-2008 Accedian Networks Inc. All rights reserved, including those to reproduce this publication or parts thereof in any
form without permission in writing from Accedian Networks Inc.

2
Contents
1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . 6
Introducing the EtherNID . . . . . . . . . . . . . . . . . . . 6
Features and benefits . . . . . . . . . . . . . . . . . . . . . . . . 7
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Application scenario . . . . . . . . . . . . . . . . . . . . . . . 8
2 Management parameters . . . . . . . . . . . . . . . . . . . . 37
Hardware installation . . . . . . . . . . . . . . . . 9
Hardware overview . . . . . . . . . . . . . . . . . . . . . . . . 9
Front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Status lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Mounting options . . . . . . . . . . . . . . . . . . . . . . . . 14
Wall mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Desktop installation . . . . . . . . . . . . . . . . . . . . . . . . . 14
Rack mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Powering the EtherNID . . . . . . . . . . . . . . . . . . . . 18
Restarting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Resetting to factory defaults . . . . . . . . . . . . . . . . 20
3 Port configuration and status . . . . . . . . . . . . . . . . . . 47
Management and configuration . . . . . . . 21
About the management web interface . . . . . . . . 21
Starting the management web interface . . . . . . . . . 21
Managing web interface accounts . . . . . . . . . . . . . . 21
DNS settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring interfaces . . . . . . . . . . . . . . . . . . . . . 25
Creating or editing an interface . . . . . . . . . . . . . . . . 25
Interface parameters . . . . . . . . . . . . . . . . . . . . . . . . 26
Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Adding a route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Route parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Syslog options . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Syslog parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3
Setting the system date and time . . . . . . . . . . . . 30
Timezone and Daylight saving . . . . . . . . . . . . . . 31
SNMP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
SNMP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 33
History buckets . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 34
Remote retrieval of history buckets . . . . . . . . . . . 35
Scheduling and file transfer configuration . . . . . . . . 36
Session management . . . . . . . . . . . . . . . . . . . . . 37
Firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . 38
Session configuration . . . . . . . . . . . . . . . . . . . . . 39
Session parameters. . . . . . . . . . . . . . . . . . . . . . . . . 39
Session management . . . . . . . . . . . . . . . . . . . . . 40
Management parameters . . . . . . . . . . . . . . . . . . . . 40
Session RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . 41
RADIUS parameters . . . . . . . . . . . . . . . . . . . . . . . . 41
Management bridge . . . . . . . . . . . . . . . . . . . . . . 43
Configuration procedure . . . . . . . . . . . . . . . . . . . . . 43
4
Port configuration . . . . . . . . . . . . . . . . . .45
Port list and port status . . . . . . . . . . . . . . . . . . . . 45
Port options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Configuring port settings . . . . . . . . . . . . . . . . . . . 49
Port parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Port statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
PHY auto-negotiation configuration . . . . . . . . . . . 55
PHY parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
SFP information . . . . . . . . . . . . . . . . . . . . . . . . . . 57
SFP information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
SFP thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
SFP memory and monitor memory . . . . . . . . . . . . . 61
Cable verification . . . . . . . . . . . . . . . . . . . . . . . . . 62
Testing a cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
5 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Monitoring and filtering . . . . . . . . . . . . . 64
Service mapping . . . . . . . . . . . . . . . . . . . . . . . . . 64
Viewing CoS profiles . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a CoS Profile . . . . . . . . . . . . . . . . . . . .
CoS Profile parameters . . . . . . . . . . . . . . . . . . . . . .
Assigning a CoS profile to a policy . . . . . . . . . . . . .
Viewing Bandwidth regulator sets . . . . . . . . . . . . . .
Configuring a Bandwidth regulator set . . . . . . . . . . .
Bandwidth regulator set parameters . . . . . . . . . . . .
Assigning a Bandwidth regulator set to a policy . . .
Layer-2 Protocol Tunneling . . . . . . . . . . . . . . . . . 70
Adding a new L2PT Rule . . . . . . . . . . . . . . . . . . . . . 72
L2PT rule settings . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Traffic policies and monitoring . . . . . . . . . . . . . . 74
Configuring a traffic policy . . . . . . . . . . . . . . . . . . . . 75
Policy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Traffic filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Viewing L2 filters . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring an L2 filter . . . . . . . . . . . . . . . . . . . . . . .
L2 filter parameters . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing IPv4 filters. . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring an IPv4 filter . . . . . . . . . . . . . . . . . . . . .
IPv4 filter parameters . . . . . . . . . . . . . . . . . . . . . . . .
Bandwidth policing . . . . . . . . . . . . . . . . . . . . . . . 86
Configuring a regulator . . . . . . . . . . . . . . . . . . . . . . 87
Regulator settings . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Assigning a regulator to a policy . . . . . . . . . . . . . . . 88
6
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Alarm settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Alarm configuration . . . . . . . . . . . . . . . . . . . . . . . 90
Customizing an alarm . . . . . . . . . . . . . . . . . . . . . . . 91
Alarm status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Chassis alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7
Operations, Administration and
Maintenance. . . . . . . . . . . . . . . . . . . . . . . 95
OAM configuration . . . . . . . . . . . . . . . . . . . . . . . 95
Configuring an OAM instance . . . . . . . . . . . . . . . . . 96
OAM instance parameters . . . . . . . . . . . . . . . . . . . . 96
Adding a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Loopback parameters . . . . . . . . . . . . . . . . . . . . . . . 99
OAM events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
64 Transmitted and Received event notifications . . . . 102
65
66 OAM status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
67 Detailed status information . . . . . . . . . . . . . . . . . . 105
67 OAM statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 107
68 OAM detailed statistics information . . . . . . . . . . . . 108
68
69
8
RFC-2544. . . . . . . . . . . . . . . . . . . . . . . . .113
RFC-2544 Generator . . . . . . . . . . . . . . . . . . . . . 113
Viewing RFC-2544 Generator . . . . . . . . . . . . . . . . 113
Configuring RFC-2544 Generator . . . . . . . . . . . . . 114
RFC-2544 monitor . . . . . . . . . . . . . . . . . . . . . . . 118
Viewing RFC-2544 Monitor . . . . . . . . . . . . . . . . . . 118
79 Detailed view of RFC-2544 Monitor. . . . . . . . . . . . 119
80 RFC-2544 testsuite . . . . . . . . . . . . . . . . . . . . . . 121
80
Viewing RFC-2544 Testsuites . . . . . . . . . . . . . . . . 121
82
Detailed view of RFC-2544 Testsuites . . . . . . . . . 122
83
84 RFC-2544 reports . . . . . . . . . . . . . . . . . . . . . . . 126
Starting an RFC-2544 Testsuite . . . . . . . . . . . . . . 126
Viewing RFC-2544 Reports . . . . . . . . . . . . . . . . . . 127
9
Performance Assurance Agent. . . . . . .129
PAA configuration . . . . . . . . . . . . . . . . . . . . . . . 129
Configuring a probe . . . . . . . . . . . . . . . . . . . . . . . . 131
PAA parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 132
PAA status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Detailed PAA status. . . . . . . . . . . . . . . . . . . . . . . . 136
PAA results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Detailed PAA results . . . . . . . . . . . . . . . . . . . . . . . 138
4
10
Traffic shaper. . . . . . . . . . . . . . . . . . . . . 140
Traffic shaper configuration . . . . . . . . . . . . . . . 140
Traffic shaper statistics . . . . . . . . . . . . . . . . . . . 144

11
CFM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
CFM continuity fault management . . . . . . . . . . 146
CFM configuration . . . . . . . . . . . . . . . . . . . . . . 147
CFM statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 154

12
Command Line Interface. . . . . . . . . . . . 156
Command summary . . . . . . . . . . . . . . . . . . . . . 156
Command syntax . . . . . . . . . . . . . . . . . . . . . . . 158

13
Appendix A - Alarms . . . . . . . . . . . . . . . 159
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

14
Appendix B - MIB support . . . . . . . . . . 163
Public MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Private MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

5
1: Introduction Introducing the EtherNID

Chapter 1: Introduction

1 Introduction

Introducing the EtherNID

The growing demand for Ethernet Services is exploding everywhere. Carriers contending in
this competitive market space are faced with several challenges:
• Setting a clear Demarcation Point between the Customers' and the Carriers' Ethernet
Network.
• Implementing Operations, Administration and Maintenance (OAM), to reduce operational
expenses and minimize truck-roll.
• Offering Carrier-Grade Reliability.
All of this while optimizing end-to-end Network Performance and keeping capital expenses at
a minimum.
Accedian's EtherNID Demarcation Point offers a solution to address these challenges by
implementing standards-based Ethernet OAM and loop-back capabilities as part of the
industry's first Line-Powered Ethernet NID (patent pending).
Installed in-line on the Ethernet media, the EtherNID implements a transparent fail-safe
bypass, meeting the reliability objectives that carriers have come to expect from telecom
demarcation units.
Furthermore, Accedian's EtherNID’s unique Fast-Thru™ architecture minimizes packet-jitter
and latency, two parameters critical in real-time applications such as Voice and Video over IP,
especially when adding cascaded network devices.
The EtherNID comes equipped with two Monitor Ports where external test equipment can be
connected to perform non-intrusive troubleshooting, thus offering independent Monitoring
Access to each direction independently, a function that carriers are used-to with traditional
demarcation devices but lacking from current Ethernet service delivery methods. Additionally,
the EtherNID allows combining both signal directions on a single Monitor Access port by using
a Port Mirroring function.
The Performance Assurance Agent™ (PAA™) allows measuring and tracking End-to-End
SLA parameters such as Latency, Jitter, Packet Loss and Availability in a continuous manner,
while the service is running.
The EtherNID interacts seamlessly with Ethernet OAM compliant devices, comes with an
embedded Web Server User Interface and can be optionally managed directly via SNMP.
Designed cost effectively for volume deployment, the EtherNID allows for systematic
installation on every customer Ethernet line and therefore obtaining a consistent look & feel
across the network.

6
1: Introduction Introducing the EtherNID

Features and • Ethernet OAM & loop-back — Increases visibility, management and easier maintenance.
benefits • Fail-safe Bypass — No impact on the MTBF of the E-Line
• Fast-Thru ™ Architecture — Minimizes Packet Jitter and Latency, (important for Video &
VoIP)
• Dual Tap/Mirror ports — Allows non-intrusive Monitor Access
• Creates a clear demarcation point between the Carrier's and Customer's Network.
• Extends the Network's OAM capabilities all the way to the customer's IT closet.
• Allows offering full NID power responsibility and reliability as a value-added SLA.
• Increases service reliability and availability.
• Reduces Carrier's operational expenses by reducing truck-roll.
• Eliminates finger pointing.
• Increases end-customer satisfaction.

Applications • Acts as an Ethernet OAM extension for Metro Access Platforms.

• Adds Ethernet OAM capability to legacy media-converters and Access Platforms.
• Sectionalizes Multi-Carrier E-lines.
The EtherNID’s ultra-compact form factor also allows for high-density rackmount installation.
Its fail-safe bypass architecture allows it to be used as a Modular Intelligent Ethernet Patch
Panel, providing non-intrusive Monitor Access to each direction or combined access to both
directions using port mirroring.

7
1: Introduction Application scenario

Application scenario
The following scenario illustrates how the EtherNID can be used to provide a remotely
manageable customer premises demarcation point for the delivery of Ethernet services.

Carrier Site Customer Site

Remote Site
Remote Site

Local
Customer Management
Remote traffic Station Management port
Management
Station

Hub Node Transport Media Access Node EtherNIDTM Customer Device

Network Client
Test port port
Equipment

Demarcation
point

Test traffic Legend

Test traffic

Test traffic looped back Customer traffic

Ethernet connection

About this scenario:

• Remote Management station is a computer that is used to remotely manage the
EtherNID and to setup loopbacks. Access to the EtherNID management web interface
occurs through a secure shell (SSL) via a web browser session and requires a
JavaScript-enabled Web browser such as Firefox 1.0 or higher, or Microsoft Internet
Explorer 6.0 or higher.
• Test equipment provides the test suite that is used to validate the link to the customer
premises.
• Hub node provides network connectivity for the carrier site.
• Transport media provides connectivity between the carrier site and the customer
premises.
• Access node provides network connectivity for one or more customer devices at a
remote location.
• Local management station is the computer that is used to define initial configuration
settings on the EtherNID when it is installed. This station can be eliminated if a DHCP
server is available on the network. In this case the DHCP server can be configured to
provide a specific IP address to the EtherNID based on its MAC address.
• Customer device is the customer-owned switch or router residing on the customer’s
network.

8
2: Hardware installation Hardware overview

Chapter 2: Hardware installation

2 Hardware installation

Hardware overview
Front panel - EtherNID EE

Front panel - EtherNID GE, and MetroNID TE / TE-R

Rear panel - All units

9
2: Hardware installation Hardware overview

Front panel The front panel features different ports and status lights depending on the model.

Ethernet ports
All Ethernet ports are 10/100/1000BaseT or 10/100BaseT Ethernet, depending on the model,
supporting auto-negotiation, auto-MDIX and have RJ-45 connectors.
Each port has two indicator lights as follows:

Light Solid Flashing

Link/RX Port is connected at the link layer. Port is receiving data.

TX N/A Port is transmitting data

SFP ports
All SFP ports are compliant with INF-8074 and must be connected to SFP modules that are
class 1 lasers and are compliant with IEC825-1.

Port functionality
The following table lists the capabilities of each port.

Model SFP RJ-45

EE N/A 10Base-THD/TFD
100Base-TX/TXHD/TXFD
(Auto-negotiation/Auto MDIX)

GE / TE Fiber SFP 10Base-THD/TFD

/ TE-R
100Base-BX10D/BX10U/FX/F 100Base-TX/TXFD
XFD/LX10 1000Base-T/TFD
1000Base-BX10D/BX10U/LX/L (Auto-negotiation/Auto MDIX)
XFD/LX10/SX/SXFD/T/TFD
(Auto-negotiation)

Copper SFP
10Base-TFD
100Base-TX/TXFD
1000Base-T/TFD
(Auto-negotiation/Auto MDIX)

The following describes the factory default configuration settings for all ports. Use the
management web interface to change these settings as required by your installation.

10
2: Hardware installation Hardware overview

EtherNID EE
• Management: For connection of a local management station. By default, this port is set to
the static IP address 192.168.1.254/24 and connection is made by using an SSL or SSH
Client.
• Monitor 1: Configured for traffic monitoring.
• Monitor 2: Configured for traffic monitoring.
• RJ-45-A: This port is configured for connection to the client network.
• RJ-45-B: This port is configured for connection to the carrier network and is set to operate
as a DHCP client.

EtherNID GE / MetroNID TE / TE-R

• SFP-A: By default, this port is configured for connection to the client network.
Configuration can be changed using the management web interface.
• SFP-B: By default this port is configured for traffic monitoring.
• Management: For connection of a local management station. By default, this port is set to
the static IP address 192.168.1.254/24 and connection is made by using an SSL or SSH
Client.
• RJ-45-A: This port is configured for connection to the client network. This configuration
can be changed using the management web interface.
• RJ-45-B: This port is configured for connection to the carrier network and is set to operate
as a DHCP client.

11
2: Hardware installation Hardware overview

Status lights • PWR (green): On when power is applied.

• LPBK (yellow): On when the loopback function is enabled. Flashes when traffic is being
looped-back.
• MIN (yellow): On when a minor alarm condition is present.
• MAJ (red): On when a major alarm condition is present.
• CRIT (red): On when a critical alarm condition is present.
• SFP (green):
• TX: Flashes when the port transmits data.
• Link/RX: Solid when the link level is present. Flashes when the port receives data.

Rear panel The rear panels on all units are identical.

Port/Connectors
• +/-40-57V---0.25A connector: For use with the EtherSHELF connectors or a discrete
power cord (connector sold separately) providing +/-40 to +/-57 V DC.
• 5V---2A connector: For use with the DC power adapter.
• Console: RJ-45 serial connection for access to the console interface. Pin-outs for both
ends of the console cable are as follows:

Console
RJ-45
Cable

8 1

DB-9 Female
1
TERMINAL

9
5

12
2: Hardware installation Hardware overview

RJ-45 Connector DB-9 Connector

Pins # Signals Pins # Signals

1 Not connected

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

8 Not connected

To establish a connection with the CLI interface on the EtherNID from your computer, use
a terminal emulation program with the following settings:
• Protocol: Serial
• Port: COM1 to 8
• Baud rate: 115200
• Data bits: 8
• Parity: None
• Stop bits: 1
• Flow Control: None

Status light
• 5V: On when power is applied via the power adapter.

Buttons
The Bypass and Loopback buttons are used to reset the EtherNID. See "Resetting to factory
defaults" on page 20 for instructions.

13
2: Hardware installation Mounting options

Mounting options
Several different mounting options are available as described in this section.

Wall mounting Optional brackets and screws are available for mounting the EtherNID on a wall. Attach the
brackets as follows:

Screw Screw

Mounting
bracket

When mounting the EtherNID on a wall, ensure that:

• the surface you attach the EtherNID to and the fasteners you use are able to support at
least 2 kg (4.4 pounds)
• cable pull (accidental or otherwise) does not make the unit exceed the 2 kg (4.4 pound)
limit

Desktop Attach the included rubber feet to the bottom of the unit for added stability when placing on a
installation desktop or other flat surface.

14
2: Hardware installation Mounting options

Rack mounting To install the EtherNID in a standard 19” rack, attach the optional 1U rack mount bracket as
shown.

An optional 1U bracket is available that can hold two units.

Grounding the EtherNID

Connect the EtherNID to a ground point on the rack as follows:
1. Turn OFF power to the unit. However, to channel ESD voltages to ground, do not unplug
the power cable. Remove all network interface cables.
Warning: Before proceeding to the next step, ensure that power is removed from the DC
circuit. To ensure that all power is OFF, locate the circuit breaker on the panel board that
services the DC circuit, switch the circuit breaker to the OFF position, and then tape the
switch handle of the circuit breaker in the OFF position.
2. Strip one end of a 10-AWG wire to expose approximately 0.75 in. (20 mm).
3. Crimp the ground lug around the exposed wire.
4. Use a Phillips #2 screwdriver to fasten the ground lug to the bottom hole on the left side of
the unit (towards the rear) using a 4-40, 3/16 stainless steel screw with an oversized
washer.
5. Connect the other end of the wire to a grounding point on the rack.

15
2: Hardware installation Mounting options

EtherSHELF
The EtherSHELF, an optional 12 unit, 4U shelf is available for large-scale installations.

To mount an EtherNID in the EtherSHELF, L-shaped brackets must be attached to the left and
right side of the unit.

Attach brackets before mounting in the drawer.

Grounding the EtherSHELF

Connect the EtherSHELF to a ground point on the rack as follows:
1. Turn OFF power to the shelf. However, to channel ESD voltages to ground, do not unplug
the power cable. Remove all network interface cables.
Warning: Before proceeding to the next step, ensure that power is removed from the DC
circuit. To ensure that all power is OFF, locate the circuit breaker on the panel board that
services the DC circuit, switch the circuit breaker to the OFF position, and then tape the
switch handle of the circuit breaker in the OFF position.
2. Strip one end of a 10-AWG wire to expose approximately 0.75 in. (20 mm).
3. Crimp the two-hole grounding lug around the exposed wire.

16
2: Hardware installation Mounting options

4. Use a small wrench to tighten the bolts around the two grounding screws to secure the
two-hole grounding lug to the back of the EtherSHELF
5. Connect the other end of the wire to a grounding point on the rack.

Dimensions
The EtherSHELF is a 4U chassis for 19 inch racks with available side extenders for 23 inch
racks. It holds 12 EtherNIDs all individually fused that are powered by 2 x 48V power feeds.
• Height = 7 inches
• Width = 19 inches
• Depth = 7 inches

17
2: Hardware installation Powering the EtherNID

Powering the EtherNID

The EtherNID can be powered using one of the following options:

DC power adapter
Connect the supplied power adapter to the 5V/2A DC connector on the rear of the unit.

48V DC from the 12 unit EtherSHELF

You can power EtherNIDs mounted in the EtherSHELF using the shelf’s built-in 48 V DC
power connector. Slide the EtherNID into the shelf to engage the power connector on the rear
of the unit.
The EtherSHELF’s power feed must be limited with a 5A/48V fuse. Voltage must be in the
range +/-40 to +/-57 V DC using AWG 14 gauge or larger cable.

48V DC from the Terminal Block Adapter

In a 1U rack mount bracket installation, it is sometimes preferable to use 48V DC power
through directly secured wires as opposed to the DC power adapter.The Terminal Block
Adapter fastens to the back of the EtherNID to provide such an installation.
To ground the Terminal Block Adapter, use a small wrench to tighten the bolt around the
grounding screw, located at the bottom right on the back of the Terminal Block Adapter, to
secure the grounding lug.

18
2: Hardware installation Powering the EtherNID

48V DC via discrete power cord

It is possible to power units with a custom built 48V DC power cable. When powered in this
manner, the unit must be installed horizontally to meet all applicable safety
regulations. Therefore, supported mounting options are desktop mounting or 1 or 2 unit rack
mounting. Wall mounting is not allowed.
On older models of the EtherNID™, the +/- 48V Return is common to both Feed A and Feed
B, whereas other models will have an isolated Return A and Return B.

To locate your serial number, please refer to the sticker on the Rear Panel of the unit. If the
serial number starts with:
• I006-… or less then the unit has a common +/- 48V Return
• P004-… or less then the unit has a common +/- 48V Return
• I007-… or more then the unit has an isolated +/- 48V Return A and Return B
• P005-… or more then the unit has an isolated +/- 48V Return A and Return B

The following diagram depicts the pin-out of the white +/- 48V connector on the
rear panel of the EtherNID™:
Common +/- 48V Return Isolated +/- 48V Return A and B

If an EtherNID™ with a Common +/- 48V Return is being used with the Terminal Block Adapter, then the
two +/- 48V Return screws corresponding to the “RTN FEED A” and “RTN FEED B” on the Terminal
Block Adapter must be tied together:

Terminal Block Adapter with Return Feeds tied

The power source (+/-40 to +/-57 V DC) must be limited by a 0.5A/48V fast acting fuse or
equivalent (Littelfuse 0217.500 0.50A). There should be one fuse per power feed.
Warning: Disconnect all power sources (feed A and feed B) when servicing. Removing fuses
can be used as a disconnect method.
Warning: Fuses must be installed on the live wire(s) and not on the grounded wire(s).

19
2: Hardware installation Restarting

Restarting
To restart the EtherNID:
1. Press and hold the Bypass button.
2. Press and release the Loopback button. The unit will restart.
3. Release the Bypass button.
If required, the EtherNID can also be restarted using the command line interface. See
Chapter 12 for details.

Resetting to factory defaults

To reset the EtherNID to factory default settings:
1. Press and hold the Bypass button.
2. Press and release the Loopback button.
3. Continue to press the Bypass button until the following lights all flash at the same time:
• Minor
• Major
• Critical
• Power
4. Release the Bypass button.

20
3: Management and configuration About the management web interface

Chapter 3: Management and configuration

3 Management and configuration

About the management web interface

The web-based management web interface provides secure access, via an SSL client, to all
EtherNID control, management, and monitoring functions.
The management station is the computer that you use to connect to the management web
interface. To act as a management station, a computer must:
• have a JavaScript-enabled Web browser installed (Firefox 1.0 or higher, or Internet
Explorer 6.0 or higher).
• be able to establish an IP connection with the EtherNID

Starting the To start the management interface, do the following:

management 1. Use an Ethernet cable to connect the LAN port on a computer to the management port on
web interface the front of the EtherNID.
2. Configure the computer with the static IP address 192.168.1.2.
3. Start your Web browser and specify the following in the address box:
https://192.168.1.254 and press Enter.
4. The EtherNID login page opens. Login as admin with the Password admin.

Managing web One administrator account is created by default with username and password both set to
interface admin. The username and password are case-sensitive. It is recommended that you change
the default password immediately after installation to safeguard the system. The administrator
accounts account provides access to all EtherNID features.

21
3: Management and configuration About the management web interface

Managing accounts
Administrator accounts are managed on the Session > Users page.

Changing the default administrator password

1. Open the Session > Users page and click admin in the list.
2. Specify the new password, confirm it.

3. Click Apply.

Lost administrator password

If you forget the username or password the only way to gain access to the management web
interface is to perform a factory reset as described in "Resetting to factory defaults" on page
20.

22
3: Management and configuration About the management web interface

Creating additional accounts

1. Open the Session > Users page and click Add.
2. In the new user setting box, specify the new user name and other details.

3. Click Apply.

23
3: Management and configuration DNS settings

DNS settings
To define DNS options, open the System > DNS page. You can either choose to use the DNS
settings obtained via DHCP on a specific port, or manually set DNS settings.

Use DHCP results

Set DNS manually

In either case, you can define the host name for the EtherNID.
Note: The default host name is the serial number of the NID and will be displayed in the
banner at the top of the management web interface.

24
3: Management and configuration Configuring interfaces

Configuring interfaces
The EtherNID lets you define multiple logical interfaces for management purposes that can be
active on different ports. This includes defining bridges and VLANs.
To see a list of all logical interfaces. Open the System > Interface page.

By default, two interfaces are defined:

• Management: This is the default interface that enables access to the management web
interface via the management port. If you modify this interface you may lose access to the
management web interface.
• Network: This is the default interface active on the network port.

Creating or To create or edit an interface, do the following:

editing an 1. Open the System > Interface page.
interface 2. Click the Add button to add a new interface, or click the name of an existing interface to
edit its settings. For example, if you click the Management interface you will see:

Note: Different fields will appear depending on the selections you make for
Interface type.
3. Define interface parameters as required by your setup and then click Apply.

25
3: Management and configuration Configuring interfaces

Interface Note: It is valid to set the IP address for an interface to 0.0.0.0 when the interface is not
parameters required to be an IP interface. For example, when the interface is used for OAM or test set
interaction.

Interface name
Specify a name to identify the interface.

Interface type
Sets the interface type to use. Select one of the following options:
• Standard: Standard IP interface associated with a single port.
• Bridge: Bridged interface than connects two or more ports.
• VLAN: VLAN interface associated with a single port.
• VLANinVLAN: VLAN in VLAN (.1q in .1q) interface associated with a single port.

On port(s)
Select the port the interface will be active on. In the case of a bridge, select multiple ports by
holding down the control key when you click on port names in the list.

VLAN ID
(Only available when Interface type is set to VLAN or VLANinVLAN.)
Specify the VLAN ID (Management VLAN) to assign to the interface.

Ethertype
(Only available when Interface type is set to VLANinVLAN.)
Specify the Ethertypes for the first and second VLAN IDs. Valid Ethertypes are: 0x8100
(C-VLAN) and/or 0x88A8 (S-VLAN).

Automatic IP (DHCP)
Select this option to have the interface act as a DHCP client and automatically obtain its IP
address, DNS server, and gateway settings from a DHCP server.

Use DHCP route information

If the DHCP server has routing information, it will be applied to the EtherNID.

Manual configuration
Select this option to manually configure IP addressing settings.
• IP address: Specify an IP address to assign to the interface.
• Network mask: Specify the network mask associated with the IP address.
• Gateway address: Specify a default gateway address. This provides a shortcut
alternative, to route configuration, to create a default gateway.

26
3: Management and configuration Routes

Routes
Select System > Interface to open the routes pages, which shows all active routes on the
EtherNID. Initially, no routes are defined.

Adding a route To add a system route, do the following:

1. Open the System > Routes page.
2. Click the Add button in the Routes box.
3. Define route parameters as required by your setup and then click Apply.

27
3: Management and configuration Routes

Route Name
parameters Specify the name to assign to the route.

Type
Select a route type:
• Network
• Host

Interface
Select the interface to which the route is associated. Note: This field is optional if a matching
active route is already associated to the interface.

Destination
Network or host address of the route. Use 0.0.0.0 for default.

Network mask
Specify the mask to assign to the route. Only used for routes of type Network.

Gateway
Specify the gateway associated with this route.

28
3: Management and configuration Syslog options

Syslog options
To define syslog options, open the System > Syslog page. The syslog page displays all
syslog entries with the most recent entry at the top.

Syslog information can be sent to a remote server by setting the options in the Remote
Syslog Configuration box. Configure these options as required and then click Apply.

Syslog Facility configuration

parameters Device facility
All messages are logged using this user defined facility instead of the default ones.

Level configuration
Level threshold
Log all messages with level equal to or above the selected one in the drop down list. For
example, If CRITICAL level is selected, then all messages with level CRITICAL, ALERT or
EMERGENCY will be logged.

Remote syslog configuration

Remote syslog enable
Enables the sending of messages to a remote syslog server.

Host
Specify the IP address or domain name of the remote syslog server.

29
3: Management and configuration Setting the system date and time

Setting the system date and time

To set the system date and time, do the following:
1. Open the System > Time page.

2. Specify the current date and time and click Apply or to automatically update the system
date and time using the Network Time protocol, select the NTP enable option. The
following options will be displayed:

3. Select a time server from the list. To add a new server, specify its name or IP address in
the Added Server box and then click add. Then select the new server in the list and click
Apply.
4. The EtherNID can also act as an NTP server by selecting the NTP server enable option.

30
3: Management and configuration Timezone and Daylight saving

Timezone and Daylight saving

For a list of time zones and daylight saving time rules, please refer to:
http://www.worldtimezone.com/.

GMT offset
Offset from Greenwich Mean Time. North America would have negative values while Eastern
Europe would have positive values.

Daylight saving enable

For regions of the world implementing Daylight saving time, this can be enabled.
Beware that syslog and other services that timestamp events using the current date and time
will be affected during transitions of DST periods. There will possibly be an hour gap or
duplicate time stamps because the clock was set back.

Daylight saving offset

Time correction to apply to GMT offset during the Dailight saving period. Most of the time it will
be one hour.

DST start and DST end

Period where daylight saving time is in effect.
The events are described as:
"the change will take place on the n'th (week) of (month) on a (day) at (hour) (min)"
To describe the last day of the month, use week=5

Examples:
Montreal, Quebec, Canada time:
GMT offset=-5, DST enable=check, DST offset=1
DST start: Month=March, Week=2, Day=Sunday, Hour=2, Min=0
DST end: Month=November, Week=1, Day=Sunday, Hour=2, Min=0

Wellington, New Zealand

GMT 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

31
3: Management and configuration SNMP settings

SNMP settings
To configure SNMP options, do the following:
1. Open the System > SNMP page.

2. Define SNMP parameters as required by your setup and then click Apply.

32
3: Management and configuration SNMP settings

SNMP Enable agent

parameters Select this checkbox to enable the SNMP agent.

SNMP system name

Specify a name to identify the EtherNID. By convention, this is the node's fully-qualified
domain name.

Contact information
Specify contact information for the EtherNID. Generally an email address.

System location
Identify the physical location of the EtherNID.

Agent UDP port

Specify the UDP port the SNMP agent uses for all IPv4 interfaces.

Read-only community
Specify the community string to control read-only access to the EtherNID.

Read-write community
Specify the community string to control read/write access to the EtherNID.

Enable trap host

Enable these options to have the unit send SNMPv1 or SNMPv2c traps to the specified
management host(s).

Community string
Specify the community string required to send traps to the management host(s).

Management host
Specify the IP address or host name of the device that will receive SNMP traps (and/or inform
notifications). The EtherNID sends a Cold Start trap when it starts up.

UDP port
Specify the UDP port that the EtherNID will use to send traps to the management host(s). By
default, the well-known SNMP trap port (162) is used.

Note: For a list of Public and Private supported MIBs, see Appendix B.

33
3: Management and configuration History buckets

History buckets
To configure local history bucketing, do the following:
1. Open the System > History page.

2. Define the history parameters as required and then click Apply.

Local Enable history

Configuration This will start the creation of history files being stored in RAM. These will then be accessible
through SNMP.

Enable filing
This will enable the history files to be stored locally instead of storing this information in the
RAM. This will enable the remote retrieval of these files as well as protect against losing these
statistics history in the event of a power failure or reboot. Unchecking this box will result in the
existing history files for this feature to be removed locally.

Period
The frequency, in minutes, of storing the statistics history into files.

34
3: Management and configuration Remote retrieval of history buckets

Remote retrieval of history buckets

NOTE: The Remote retrieval feature is only available on the MetroNID TE/TE-R models.
To configure remote retrieval of history buckets, do the following:
1. Open the System > History page on the remote NIDs.

2. Ensure filing is enabled for the desired history buckets and then click Apply.
3. Open the System > History page on the local MetroNID TE / TE-R and add a new
remote device. Then enable scheduling at the desired time slot(s) and provide the URL
for the file transfer server.

35
3: Management and configuration Remote retrieval of history buckets

Scheduling and Enable scheduling

file transfer Enable the history buckets to be retrieved from the local device and/or the list of remote
devices. The history buckets will be retrieved according to the Scheduled hours selected.
configuration (Hold CTRL key to select more than one hour)
This feature is dependant on the Enable filing check boxes in the Local configuration sections
of the local and remote devices.
Example: If Enable scheduling is checked but the local device has not checked Enable filing,
then only the remote history buckets will be retrieved.
Example: If Enable scheduling is checked and the local device, as well as the remote
device(s), have checked Enable filing, then both the local and remote history buckets will be
retrieved.

Server URL
The full URL of the Server on which to send the history bucket files once retrieved.
Examples:
http://mypc.com
ftp://username:password@mypc.com
tftp://192.168.1.5

NOTE: The status of the Remote devices can be obtained by clicking on the Remote
device name in the Remote device configuration window.

36
3: Management and configuration Session management

Session management
To configure session management options, do the following:
1. Open the Session > Management page.

2. Define session management parameters as required by your setup and then click Apply.

Management Writelock session

parameters The management web interface supports multiple concurrent users, therefore to maintain the
integrity of the configuration settings, only one user at a time has the ability to make changes.
• Writelock: Click this button to lock the configuration so you can make changes.
• Writeunlock: Click this button to unlock the configuration so someone else can make
changes.

Current sessions
Lists all sessions currently logged into the EtherNID.

Session ID
Unique number that identifies a session. Automatically generated by the EtherNID.

Type
Indicates which interface the session is using.

Username
Identifies the user account that is logged in. An asterisk (*) next to the username indicates the
username of the session that is viewing this web page.

Uptime
Indicates how long the session has been active.

Writelock
Indicates which session has the ability to make configuration changes.

Terminate
Select one or more sessions and then click the Terminate button to force a log out.

37
3: Management and configuration Firmware upgrade

Firmware upgrade
To upgrade the EtherNID firmware, do the following:
1. Open the System > Firmware page.

2. Specify the location and name of the new firmware file or click Browse and select it.
3. Click Upload.
4. Once the firmware has been uploaded the unit will restart.

38
3: Management and configuration Session configuration

Session configuration
To configure session options, do the following:
1. Open the Session > Configuration page.

2. Define session parameters as required by your setup and then click Apply.

Session Max CLI sessions

parameters Specify the maximum number of CLI sessions that are supported at the same time.

Max WEB sessions

Specify the maximum number of management tool sessions that are supported at the same
time.

Max total sessions

Specify the total number of CLI and WEB sessions that are supported at the same time.

CLI timeout
Specify the maximum number of seconds that a CLI session can remain idle before it is
automatically logged out.

WEB timeout
Specify the maximum number of seconds that a management tool session can remain idle
before it is automatically logged out.

Authentication
Order
Authentication method to use in order of availability. Refer to RADIUS configuration page for
server configuration instructions. This parameter is described in the RADIUS section below on
page 35.

39
3: Management and configuration Session management

Session management
To configure session management options, do the following:
1. Open the Session > Management page.

2. Define session management parameters as required by your setup and then click Apply.

Management Writelock session

parameters The management web interface supports multiple concurrent users, therefore to maintain the
integrity of the configuration settings, only one user at a time has the ability to make changes.
• Writelock: Click this button to lock the configuration so you can make changes.
• Writeunlock: Click this button to unlock the configuration so someone else can make
changes.

Current sessions
Lists all sessions currently logged into the EtherNID.

Session ID
Unique number that identifies a session. Automatically generated by the EtherNID.

Type
Indicates which interface the session is using.

Username
Identifies the user account that is logged in. An asterisk (*) next to the username indicates the
username of the session that is viewing this web page.

Uptime
Indicates how long the session has been active.

Writelock
Indicates which session has the ability to make configuration changes.

Terminate
Select one or more sessions and then click the Terminate button to force a log out.

40
3: Management and configuration Session RADIUS

Session RADIUS
To configure RADIUS authentication, do the following:
1. Open the Session > RADIUS page.

2. Define RADIUS parameters as required by your setup and then click Apply.

RADIUS Authentication method

parameters Authentication method to use. This can be one of the following methods:
• PAP : Password Authentication Protocol

RADIUS timeout
Time to wait for the RADIUS server to respond before retrying the connection. After the num-
ber of retries has been exhausted, a connection to the next configured server will be
attempted, in which the same timeout and retry scheme will apply.

RADIUS retry
Number of times to retry the server before trying the next server configured.

Realm
A string to append to the user's name using the "username@realm" method.

41
3: Management and configuration Session RADIUS

Server-1 / Server-2
Host
RADIUS server host-name or IPV4 address.

Port
RADIUS server UDP port to connect to.

Secret
Shared secret for this RADIUS server.

Radius server configuration

When RADIUS authentication is enabled, the unit supports Authentication and Authorization
as configured on the RADIUS server. The RADIUS Callback-Id (id=20) attribute is used to
provide the Authorization (permissions) info to the unit. If the attribute is not configured then
the permissions will be set to viewer only.

The permissions are the same as those that can be configured locally on the unit. It is a space
or coma separated list of tokens. They can be a mix of either locally defined user permission
groups or individial privileges.

Notes:
- RADIUS assigned permissions cannot be viewed with the CLI or web based interface.
- The permissions tokens are case sensitive.

Configuration examples

Callback-Id = "Admin"
A userid member of the built-in Admin group.

Callback-Id = "Config Firmware Log Management, Users"

A list of individual privileges.

42
3: Management and configuration Management bridge

Management bridge
This section describes how to set up a bridged management port using the command line
interface.
A minimum of two EtherNIDs are required for this setup. An out-of-band EtherNID
management port will be used to manage the other EtherNIDs, in-band through a bridged
interface. This is useful when the core transport devices do not need to be connected to the
internal private management network. Instead, the first EtherNID is connected to the private
network and manages the other EtherNIDs in-band through its out-of-band Management port.
The following diagram describes the typical setup scenario for a bridged interface:

Configuration 1. Power on EtherNID #1 with factory default settings.

procedure 2. Connect your computer to serial port on the back of the EtherNID.
3. Open a terminal emulation session with the following configuration:
• Bits per second: 115200
• Data bits: 8
• Parity: None Stop bits: 1
• Flow Control: None
4. Login to the CLI with username admin and password admin.
5. If an EtherNID GE is being used, and the setup requires the Client and Network ports to
be set as copper medium, type the following command:
media-selection select RJ45-A_RJ45-B

43
3: Management and configuration Management bridge

6. Delete any existing interfaces with the following commands:

interface delete Management
interface delete Network
7. The Network port of EtherNID #1 will be used for the in-band management. Configure the
Network port with the following command:
interface add net1-10 type vlan vlan1-id 10 port Network address
192.168.1.253 netmask 255.255.255.0
8. Repeat configuration steps 1. to 7. on EtherNID #3 using the following settings when
defining the new interface:
interface add net3-10 type vlan vlan1-id 10 port Network address
192.168.1.252 netmask 255.255.255.0
9. Repeat configuration steps 1. to 6. on EtherNID #2.
10. Execute the following commands to add three interfaces on EtherNID #2:
interface add mgmt type standard port Management
interface add cli10 type vlan vlan1-id 10 port Client
interface add net10 type vlan vlan1-id 10 port Network
The interface 'mgmt' will be used to connect to the management bridge. The other two
interfaces will be used to access the other two EtherNIDs remotely.
11. Next, create the bridge interface. Execute the following command to bridge all three
interfaces together for access using the Management port.
interface add Bridge type bridge sub-intf mgmt,cli10,net10 address
192.168.1.254 netmask 255.255.255.0
12. Connect the Management port of EtherNID #2 to the private network.
13. Open a web browser on a computer connected to the private network and enter the
address 192.168.1.254 to reach the management web interface on EtherNID #2.
14. Connect the Client port of EtherNID #2 to the Network port of EtherNID #3.
15. Connect the Network port of EtherNID #2 to the Network port of EtherNID #1.
16. Open a web browser and enter the address 192.168.1.254 to reach the management web
interface on EtherNID #2.
17. Open a second web browser and enter the address 192.168.1.253 to reach the
management web interface on EtherNID #1.
18. Open a third web browser and enter the address 192.168.1.252 to reach the
management web interface on EtherNID #3.

44
4: Port configuration Port list and port status

Chapter 4: Port configuration

4 Port configuration

Port list and port status

To view a list of all ports and their status, open the Port > Configuration page.
• You will see the following page on an EtherNID EE:

45
4: Port configuration Port list and port status

• You will see the following page on an EtherNID GE or MetroNID TE / TE-R:

46
4: Port configuration Port list and port status

Port Status
configuration Indicates the status of the port.

and 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.
• Grey: The port is disabled.

Connector
Identifies the physical connector the port is using.

Port name
Identifies the logical name assigned to the port.

Port state
Indicates if the port is enabled (ready to connect) or disabled.

Speed
Indicates the current port speed and duplex type. If set to Auto-nego the EtherNID
automatically negotiates port speed and duplex type with the device it is connected to. For this
to work the device must also be configured to support auto-negotiation.

MAC address
Indicates the MAC address of the port.

Port options Media-selection

(Supported on the EtherNID GE and MetroNID TE / TE-R only)
Lets you select which two media connectors will be used to carry traffic. Four options are
available:
• SFP-A with SFP-B
• SFP-A with RJ-45-B
• RJ-45-A with SFP-B
• RJ-45-A with RJ-45-B
If you change the setting and then click Apply, all the associations between connectors and
ports will be reflected in the Port configuration and status table.
The two other connectors on the device will be monitor ports. When used as monitor ports,
connectors RJ45-A and SFP-A are mapped to port Monitor-1, and RJ45-B and SFP-B are
mapped to port Monitor-2.
For example: By default, SFP-A with RJ-45-B is selected. This denotes Traffic-A is connected
to the SFP-A connector and Traffic-B is connected to the RJ-45-B connector

47
4: Port configuration Port list and port status

Fault propagation
Enable fault propagation
Select this check box to enable fault propagation. When this feature is enabled the EtherNID
will propagate link faults between the Client and Network ports.

Fault propagation mode

Select fault propagation operation mode:
• One-way link: Propagate fault in one direction based on opposite port link status.
• One-way EVC: Propagate fault in one direction based on opposite port link status and
EVC status.
• Two-way link: Propagate fault in both direction based on opposite port link status.
Fault propagation could be based on link status only or link status and EVC status.
For link status only operation mode, a link down on the opposite port is propagated to the
specified port.
For EVC status operation mode, the status of PAA probe(s) and/or CFM MEP(s) are
propagated to the specified port. At least one PAA probe or CFM MEP should be free of
connectivity errors to enable the specified port. If there is no PAA probe and no CFM MEP
configured in EVC fault propagation mode for the specified port, that port will stay down.

Propagate fault on port

Select the port that the EtherNID will use for fault propagation. Select one of the following
options:
• Client: If the EtherNID detects a link down condition on the Network port it will also bring
down the Client port.
• Network: If the EtherNID detects a link down condition on the Client port it will also bring
down the Network port.

48
4: Port configuration Configuring port settings

Configuring port settings

To configure port settings, do the following:
1. Open the Port > Configuration page.
2. Click the name of the port that you want to configure. The port configuration page will
open.
• If you are configuring a copper port it will be similar to the following page:

49
4: Port configuration Configuring port settings

• If you are configuring an SFP fiber port it will be similar to the following page:

• The Network port will give you the option of setting up Dual Link Protection:

3. Define port parameters as required by your setup and then click Apply.

50
4: Port configuration Configuring port settings

Port parameters Enable

Select this check box to enable the port.

Name
Specify a name to identify the port. By default, ports are named as follows: Management,
Client, Network, Monitor-1 and Monitor-2.

Alias
This is an 'alias' name for the port as specified by a network manager.

Port MTU
Specify the maximum transmission unit. By default, this is set to 1522. Example range: 1518
to 10240.

Large packet threshold

Specify the threshold such that all packets above this value will be classified as Large Packets
on the Port > Statistics page.

MAC address
Identifies the MAC address of the port.

Connector
Identifies the physical connector associated with the port.

Protection
(Network port only)
The port protection is a mechanism used to switch the traffic to a standby connector if a link
down is detected on the main connector. The main and the standby connectors are
determined by the Media-selection field in the Port / Configuration page. For example, if the
we choose RJ45-A with SFP-B, the main connector is SFP-B and standby connector is
SFP-A. If we refer to the default ports names, the protected port is always the Network port
and the protect port is always the Monitor-1 port. It should be mentionned that when a
switchover or a failover operation is performed, the two ports are swapped.
In order to use the port protection feature, the following conditions must be met:
• Platform is a MetroNID
• Media-selection is SFP-A with RJ45-B or RJ45-A with SFP-B
• Main and standby connectors must have the same media type (Copper/Fiber) and must
be 1000X in fiber mode. if this condition is not met, the port is disabled.

Enable
Enable the protection for this port. The protecting port is reserved by the protection
mechanism and can not be used for monitoring purposes as long as the protection is enabled.

Working connector
Selects the working connector for the specified port. The connector choice allows the user to
perform a switchover operation.

Revertive
If enabled, the traffic is swtiched back to the main connector after the Revert period has
expired.

51
4: Port configuration Configuring port settings

Revert period
Specifies the time, in seconds, that we must continously detect a signal on the main
connector. The timer is restarted if a signal loss is detected during this period.

Link time out

Specifies the time, in seconds, to wait for the link to come up after switching to the standby
connector. If the timer expires and the link stays down, we switch back to the protected
connector.

Media dependent interface

(Copper ports only)
Select Auto MDI Enable to have the unit automatically adapt the configuration of the
connector to the cabling plant and link partner type.
If you do not select Auto MDI Enable, you can manually define port settings as follows:
• MDI: Typical setting for an Ethernet station. Link partner must be set to MDIX or a
cross-over cable must be used.
• MDIX: Typical setting for an Ethernet switch. Link partner must be set to MDI or a
cross-over cable must be used.

Link speed
Sets port speed and duplex type.
Select Auto-negotiation enable to have the unit automatically negotiate port speed and duplex
type with the device it is connected to. For this to work the device must also be configured to
support auto-negotiation.
If you do not select Auto-negotiation enable, you can manually define port speed and duplex
type using the available options.
Note: Auto-negotiation is mandatory for 1000BASE-T.

Link Loss Return (LLR)

(SFP fiber ports only)
This option determines how the unit notifies its link partner when a valid receive signal is
absent on the link.
If this option is disabled, then:
• For 1000BASE-X links, a Remote Fault Indicator using auto-negotiation advertisement is
sent to the link partner.
• For 100BASE-FX links, the FEFI idle pattern is sent to the link partner.
If this option is enabled, then the unit turns off its transmitter for the amount of time defined by
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 in order to re-establish the link. So for this reason, 0 should not be configured on
both sides or the link will never re-establish.

Flow control
Specify if pause frames are processed locally, transparently passed through or disabled.
When enable and auto-negotiation is also enable, the exact behavior depend on
auto-negotiation result.

52
4: Port configuration Configuring port settings

Current status
Reports the following for Ethernet ports:
• Current link speed and duplex type when Auto-negotiation enable is selected.
• Current connector configuration: If the link partner is also using Auto MDI, the resulting
connector configuration is correct but random. A cross-over cable present on the cabling
plant will result in both partners using the same connector configuration.

53
4: Port configuration Port statistics

Port statistics
To view port statistics, do the following:
1. Open the Port > Statistics page.

2. Click the name of a port to view detailed statistics. For example, if you click the Client port
name on an EtherNID GE or MetroNID TE / TE-R you will see a page similar to the
following:

54
4: Port configuration PHY auto-negotiation configuration

PHY auto-negotiation configuration

To configure PHY auto-negotiation settings, do the following:
1. Open the Port > PHY page.

2. Click the name of a port that you want to configure. For example, if you click the Client
port name you will see the following page.

3. Define PHY parameters as required by your setup and then click Apply.
Note: Advertised parameters are checked and parameters that are not configurable are
greyed-out based on the capabilities of the port.

55
4: Port configuration PHY auto-negotiation configuration

PHY Advertisement configuration

parameters Sets the abilities that are advertised to the link partner. Supported options include:
• 10Mbps Half
• 100Mbps Half
• 1Gbps Half
• 10Mbps Full
• 100Mbps Full
• 1Gbps Full
• Pause Symmetric
• Pause Asymmetric

Link Partner Ability

Lists the abilities of the link partner.
• 10Mbps Half
• 100Mbps Half
• 1Gbps Half
• 10Mbps Full
• 100Mbps Full
• 1Gbps Full
• Pause Symmetric
• Pause Asymmetric

State
The state field corresponds to ifMauAutoNegConfig and ifMauAutoNegRemoteSignaling
from RFC3636.
The state disabled indicates that auto-negotiation is not supported by the media or disabled
by configuration.

56
4: Port configuration SFP information

SFP information
(Supported only on the To view SFP information, do the following:
EtherNID GE / MetroNID
1. Open the Port > SFP page.
TE / TE-R)

2. Click the name of the port for which you want to view detailed statistics. Refer to the
following sections for more information.
• "SFP information" on page 57
• "SFP thresholds" on page 59
• "SFP memory and monitor memory" on page 61

SFP This box displays general SFP information and monitoring information.
information

SFP information
Connector Type
Indicates the external optical or electrical cable connector provided as the media interface.

Vendor
Indicates the vendor name. This is a 16 character field that contains ASCII characters padded
on the right with ASCII spaces (20h).

57
4: Port configuration SFP information

Wave Length
Indicates the nominal transmitter output wavelength at room temperature in nm.

Part number
Indicates the vendor 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
Indicates the vendor serial number for the transceiver. This is a 16 character field that
contains ASCII characters padded on the right with ASCII spaces (20h).

Revision
Indicates the vendor’s product revision. This is a 16 character field that contains ASCII
characters padded on the right with ASCII spaces (20h).

SFP present
Indicates the presence of a recognized SFP.

Diagnostics
If bit 6 is set, address 92 is set indicating that digital diagnostic monitoring has been
implemented, received power monitoring, transmitted power monitoring, bias current
monitoring, supply voltage monitoring and temperature monitoring will all be displayed.

Calibration
The values in this field are interpreted differently depending upon the option bits set at
address 92.
• Internal: If bit 5 is set, the values are calibrated to absolute measurements, which should
be interpreted according to the convention “Internal Calibration”.
• External: If bit 4 is set, the values are A/D counts, which are converted into real units per
the convention “External Calibration”.

Thresholds
Additionally, alarm and warning thresholds must be written as specified in this document at
locations 00 – 55 on 2 wire serial address 1010001X (A2h).

Monitoring information
Temperature
Internally measured transceiver temperature. Temperature accuracy is vendor specific but
must be better than 3 degrees Celsius over specified operating temperature and voltage.

Laser bias current

Measured coupled TX output power. Accuracy is vendor specific but must be better than 3dB
over 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
Measured coupled TX output power. Accuracy is vendor specific but must be better than 3dB
over 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.

58
4: Port configuration SFP information

Receive power
Measured received optical power. Absolute accuracy is dependent upon the exact optical
wavelength. For the vendor specified wavelength, accuracy should be better than 3dB over
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. Absolute
accuracy beyond this minimum required received input optical power range is vendor specific.

Supply voltage
Internally measured transceiver supply voltage. Note that in some transceivers, transmitter
supply voltage and receiver supply voltage are isolated. In that case, only one supply is
monitored. Refer to the device specification for more detail.

SFP thresholds

Temperature
High alarm
High Alarm transceiver temperature.

Low alarm
Low Alarm transceiver temperature.

High warning
High Warning transceiver temperature.

Low warning
Low Warning transceiver temperature.

59
4: Port configuration SFP information

Vcc
High alarm
High Alarm transceiver supply voltage.

Low alarm
Low Alarm transceiver supply voltage.

High warning
High Warning transceiver supply voltage.

Low warning
Low Warning transceiver supply voltage.

Laser bias current

High alarm
High Alarm TX bias current in micro-Amps.

Low alarm
Low Alarm TX bias current in micro-Amps.

High warning
High Warning TX bias current in micro-Amps.

Low warning
Low Warning TX bias current in micro-Amps.

Tx power
High alarm
High Alarm TX output power in dBm (~ -40 to +8.2 dBm).

Low alarm
Low Alarm TX output power in dBm (~ -40 to +8.2 dBm).

High warning
High Warning TX output power in dBm (~ -40 to +8.2 dBm).

Low warning
Low Warning TX output power in dBm (~ -40 to +8.2 dBm).

Rx power
High alarm
High Alarm Rx input power in dBm (~ -40 to +8.2 dBm).

Low alarm
Low Alarm Rx input power in dBm (~ -40 to +8.2 dBm).

60
4: Port configuration SFP information

High warning
High Warning Rx input power in dBm (~ -40 to +8.2 dBm).

Low warning
Low Warning Rx input power in dBm (~ -40 to +8.2 dBm).

SFP memory
and monitor
memory

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

61
4: Port configuration Cable verification

Cable verification
The EtherNID uses Time Domain Reflectometry (TDR) to determine the quality of cables,
connectors, and terminations. Some of the possible problems that the EtherNID can diagnose
are: opens, shorts, cable impedance mismatch, bad connectors, and termination mismatch.

Testing a cable To perform a cable test, do the following:

1. Open the Port > Cable page.

2. Click the name the connector you want to test. For example, if you click RJ45-B you will
see the following page.

3. Click Perform Test.

4. The status of each channel is updated as the tests are run.

62
4: Port configuration Cable verification

When completed, test status will be one of the following:

• GOOD: Normal cable.
• SHORT: Indicates that the positive and the negative lines of the same cable pair are
touching: Possible causes include:
• Cable wire may be touching the wire closet patch panel.
• Cable may be worn or broken allowing the positive and negative lines to touch.
• OPEN: Indicates that one pair on the cable is not connected at the far end of the
cable. Possible causes include:
• Cable is not connected.
• Cable was cut.
• FORCED: Indicates a persistent noise on the cable. This can be caused by a link
partner running forced at 10/100 Mbps. Cable length is not available when the test
results indicate FORCED.
• FAIL: If the remote partner sends traffic at the same time as the test is being
conducted, then these packets may interfere with the TDR resulting in a FAIL status.
• Impedance Mismatch: Indicates that the effective impedance is not 100 Ohms. the
TDR can determine an impedance mismatch. Possible causes include:
• Different quality cables are connected together through a cable extender.
• A low quality cable is being used.

63
5: Monitoring and filtering Service mapping

Chapter 5: Monitoring and filtering

5 Monitoring and filtering

Service mapping
The EtherNID can perform EVC mapping (which is essentially a VLAN push), CoS mapping
and Bandwidth Policing mapping. These options can be used together or separately.
Prior to creating CoS profiles and/or Bandwidth regulator sets, appropriate filters and
bandwidth regulators will need to be created. See section Traffic Filters and Bandwidth
Policing below for details about creating filters and regulators.

A CoS profile is used to map an input packet to an L2 class of service. This traffic mapping
(classification) is accomplished using the following fields in the incoming packet:
• p-bits in 802.1Q / 802.1Q .1Q tags
• IP precedence bits in IPv4 TOS byte
• DSCP bits in IPv4 DSCP byte
The class of service value (0-7) assigned to the outgoing traffic is selected based on the con-
formance level (Green/Yellow) of the incoming traffic.

Viewing CoS To view a list of configured CoS profiles, open the Traffic > Mapping page. By default,
commonly used profiles.
profiles

Index
CoS profile's unique identifier.

Name
CoS profile's name as defined in the configuration page. Click this name for more details.

64
5: Monitoring and filtering Service mapping

Type
CoS profile's type. Possible values are:
• PCP
• IP precedence
• DSCP

Reference count
The reference count is the number of policies that are currently using this CoS profile.

Configuring a Once a Cos profile is created, it can be applied to policies for traffic classification.
CoS Profile To configure a CoS profile, do the following:
1. Open the Traffic > Mapping page.
2. Click Add in the CoS profiles section, or click a profile name to edit and existing one.
3. Configure CoS profile parameters and click Apply.

65
5: Monitoring and filtering Service mapping

CoS Profile Name

parameters Name of the CoS profile.

Type
Indicates the type of CoS profile. Possible values are:
• PCP
• IP precedence
• DSCP

Decode DEI
This field is only valid for PCP CoS profiles. If this field is set, the pre-marking color is
decoded from the DEI bit (Drop Eligible Indication). Otherwise, the user defined pre-color is
used.

Encode using DEI

This field controls the DEI bit in an S-VLAN tag. If this field is set and the outgoing packet is
marked yellow then the DEI bit is set to 1. Otherwise, the DEI is set to 0.

Reference count (only visible on existing profiles)

The reference count is the number of policies that are currently using this CoS profile.

Mapping table
The mapping table maps the input traffic to a specific class of service. This table has four
columns and 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. Otherwise, the CoS profile is a DSCP profile and N=64.
Each row in this table represents a mapping entry and each entry has the following
parameters:

PCP/IP precedence/DSCP [IN]

PCP/IP precedence/DSCP input value.

Pre-marking color
The pre-marking color that will be assigned to the input packet that has this PCP/IP
precendence/DSCP value.

Green [OUT]
The class of service value that will be used in the outgoing green packets. This value is
selected if the result of the bandwidth regulator assigned to this entry is green or if the
pre-marking color is green and no bandwidth regulator is assigned to this entry.

Yellow [OUT]
The class of service value that will be used in the outgoing yellow packets. This value is
selected if the result of the bandwidth regulator assigned to this entry is yellow or if the
pre-marking color is yellow and no bandwidth regulator is assigned to this entry.

66
5: Monitoring and filtering Service mapping

Assigning a CoS Once a CoS profile has been configured you can assign it to a policy. See "Traffic policies and
profile to a monitoring" on page 74.

policy

Viewing To view a list of configured Bandwidth regulator sets, open the Traffic > Mapping page.
Bandwidth
regulator sets

Index
Bandwidth regulator set's unique identifier.

Name
Bandwidth regulator set's name as defined in the configuration page. Click this name for more
details.

Type
Bandwidth regulator set's type. Possible values are:
• PCP
• IP precedence
• DSCP

Reference count
The reference count is the number of policies that are currently using this Bandwidth regulator
set.

67
5: Monitoring and filtering Service mapping

Configuring a Once a Bandwidth regulator set is created, it can be applied to policies for traffic classification.
Bandwidth To configure a Bandwidth regulator set, do the following:

regulator set 1. Open the Traffic > Mapping page.

2. Click Add in the Bandwidth regulator sets section, or click a regulator set name to edit
and existing one.
3. Configure Bandwidth regulator set parameters and click Apply.

Bandwidth Name
regulator set Name of the Bandwidth regulator set.

parameters Type
Indicates the type of Bandwidth regulator set. Possible values are:
• PCP
• IP precedence
• DSCP

Reference count (only visible on existing sets)

The reference count is the number of policies that are currently using this Bandwidth regulator
set.

68
5: Monitoring and filtering Service mapping

Regulator set
This table has three columns and N rows, where N depends on the type of the regulator set. If
the type is PCP or IP precedence then N=8. Otherwise, the regulator set type is DSCP and
N=64. Each row in this table allows assigning a traffic regulator to a specific PCP/IP
precedence/DSCP > value.

PCP/IP precedence/DSCP [IN]

PCP/IP precedence/DSCP input value.

Bandwidth regulator
The bandwidth regulator that will be used to regulate the traffic flow that has this PCP/IP
precendence/DSCP value.

Enable regulator
Enable or disable traffic regulation for this PCP, IP precedence or DSCP value.

Assigning a Once a Bandwidth regulator set has been configured you can assign it to a policy. See "Traffic
Bandwidth policies and monitoring" on page 74.

regulator set to
a policy

69
5: Monitoring and filtering Layer-2 Protocol Tunneling

Layer-2 Protocol Tunneling

The Layer-2 Protocol Tunneling feature allows the customer's layer-2 control protocol (L2CP)
frames to be transparently transported across an EVC without interfering with the
carrier/operator network and equipment. 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 reinserting the original destination MAC when the
traffic reaches the destination equipment. A total of 64 L2PT rules can be defined.

Name
Unique name assigned to the rule.

State
The state of the rule, enabled or disabled.

Protocol
The Layer-2 Control Protocol to be processed by the rule.

Mode
The current mode of operation of the rule. Four modes of operation are available:
• Drop: frames matching the specific rule are dropped.
• Forwarding: frames are sent unaltered to and from the specified ports (both ways).
• Tunneling: frames matching the specific rule get their destination MAC address replaced
by the MAC specified in the rule's parameters when ingressing the specified client port.
Frames matching the specific rule get their original destination MAC address put back
when ingressing the specified network port.
• Peering: the frames are sent to software layers for further processing.

Incoming port
The incoming port that is used by the rule. The incoming port is considered to be the port
where the layer-2 control protocols will ingress.

Outgoing port
The outgoing port that is used by the rule. The outgoing port is considered to be the port
where the tunneled frames, containing a replacement destination MAC, will egress.

70
5: Monitoring and filtering Layer-2 Protocol Tunneling

Unique ID
The unique identifier used by the rule when performing tunneling. This value is used when
building the replacement destination MAC address. Note that the same value has to be used
on both sides when creating a tunnel-detunnel set of rules between a pair of units.

VLAN1 type
The ethertype of the first tag inserted in the tunneled frame. This is available only when the
Tunneling operation mode is selected.

VLAN2 type
The ethertype of the second tag inserted in the tunneled frame (for Q-in-Q). This is available
only when the Tunneling operation mode is selected.

71
5: Monitoring and filtering Layer-2 Protocol Tunneling

Adding a new To add or edit an L2PT rule, do the following:

L2PT Rule 1. Open the Traffic > L2PT page.
2. Click the Add button to add a new rule or click on the rule name to edit an existing rule.

L2PT rule Enable L2PT rule

settings Allows a rule to be enabled or disabled without being deleted.

L2PT rule name

Unique name assigned to the rule.

Protocol
Layer-2 Control Protocol to be processed by a specific rule.

Replacement MAC
The multicast MAC address to use as a replacement when protocol tunneling is performed.
The following replacement MAC can be used:
• The Cisco replacement: 01:00:0C:CD:CD:D0 MAC is used. Because it can't be altered, it
can be used only once amongst all rules.
• The Accedian replacement: 01:15:AD:CC:xx:yy MAC is used. Because this replacement
MAC has variable elements, it can be used on multiple rules as the variable elements
allow a match to a specific rule when a tunneled frame ingresses the network port. These
variable elements are set as such:
• xx: the unique ID specified in the configuration (see below). When creating a tunnel
between two units, this is used to match the replacement frames going both ways on
the network port. As such, it is important that the matching rules on both endpoints
have the same unique ID.

72
5: Monitoring and filtering Layer-2 Protocol Tunneling

• yy: the protocol ID. This is automatically generated according to which Layer-2 control
protocol the rule handles.

Operation mode
This controls how the rule will handle the traffic associated with the specified protocol. Four
modes of operation are available:
• Drop: frames matching the specific rule are dropped.
• Forwarding: frames are sent unaltered to and from the specified ports (both ways).
• Tunneling: frames matching the specific rule get their destination MAC address replaced
by the MAC specified in the rule's parameters when ingressing the specified client port.
Frames matching the specific rule get their original destination MAC address put back
when ingressing the specified network port.
• Peering: the frames are sent to software layers for further processing.

Incoming port
This allows the incoming port used by the rule to be selected. The incoming port is considered
to be the port where the layer-2 control protocols will ingress.

Outgoing port
This allows the outgoing port used by the rule to be selected. The outgoing port is considered
to be the port where the tunneled frames, containing a replacement destination MAC, will
egress.

Unique ID
This is used to uniquely identify a rule when performing tunneling. As described in the
Replacement MAC section above, this value is used when building the replacement
destination MAC address. Note that the same value has to be used on both sides when
creating a tunnel-detunnel set of rules between a pair of units.

VLAN1 ethertype
Allows selecting the ethertype of the first tag inserted in the tunneled frame. This is available
only when the Tunneling operation mode is selected.

VLAN2 ethertype
Allows selecting the ethertype of the second tag inserted in the tunneled frame (for Q-in-Q).
This is available only when the Tunneling operation mode is selected.

VLAN list
This specifies which VLAN tags to insert in the tunneled frames. The format is a list of
comma-separated groups formatted as vlan1:vlan2. The second tag (Q-in-Q) entry is optional.
For example, if we wanted to single-tag tunneled frames with VLAN ID 3, and double-tag
frames with VLAN IDs 5-6 and 22-88, we would specify: 3, 5:6, 22:88.
Note that the frames are duplicated for each entry in the VLAN list. In the example above, 3
frames would egress the network port for each ingressing frame, matching the rule, on the
client port.
Also note that there should be at least one entry in the list, as tunneling untagged frames is
currently not supported.
The VLAN list is available only when the Tunneling operation mode is selected.

73
5: Monitoring and filtering Traffic policies and monitoring

Traffic policies and monitoring

To view a list of all traffic policies and their settings, open the Traffic > Policies page.
This page shows the access policy rules that are enabled for a specific port. For example, if
the Network port is selected then this is the list of policy rules that are enabled or disabled for
the Network port.
Access policy rules are ordered by their priority. When rules are applied they are processed
from the top down and the first suitable rule that is found is applied.
Note: The *default filter is a factory default rule that forwards all traffic. A rule, such as this is
required to have traffic forwarded.

Note:
The following information is presented for each policy:
• Entry: Indicates the position of the rule in the access list.
• State: Indicates if the policy is enabled or disabled. Disabled policies are skipped when
the rules are applied to incoming data.
• Action: Indicates the action that the policy applies to data that it matches.
• Filter name: Indicates the name of the filter assigned to the policy.
• Packets good: The number of good packets that matched the policy. A good packet is an
error-free frame that has a length between 64 bytes and the maximum frame length.
• Bytes good: This is the total number of bytes in good packets that matched the policy.
• Packets bad: The number of bad packets that matched the policy. A bad packet is a
packet that has a valid framing but contains an error within the packet, has a bad CRC or
either shorter than 64 bytes or longer than the maximum frame length.

74
5: Monitoring and filtering Traffic policies and monitoring

Configuring a To configure a traffic policy, do the following:

traffic policy 1. Open the Traffic > Policies page.
2. Click the policy entry that you want to configure.
3. Configure policy settings and click Apply.

Policy settings Enable policy

Select this check box to activate the policy.

Filter type
Select the filter type that will be used to capture traffic. The filter type is either a Layer 2 or
IPv4 filter.

L2 filter / IPv4 filter

The list shows all available filters.
To define a new filter, open the Port > L2 Filters/IPv4 Filters page. By default, a catchAll fil-
ter is defined. This enables you to monitor all traffic on a port.

75
5: Monitoring and filtering Traffic policies and monitoring

Action
Select the action that will be applied to traffic that matches the filter.

Enable monitoring
Select this check box to activate monitoring.

Monitor port
Indicates the port to which traffic will be forwarded for monitoring.

Encapsulation Push
Add a new VLAN.

Ethertype
The ethertype of the VLAN to be added. Possible values are: C-VLAN=0x8100 or
S-VLAN=0x88a8

VLAN ID
A value between 0 and 4095.

PCP action
This section selects the PCP (Priority Code Points) action to perform. Possible values are:
• Preserve: Keep the PCP bits if the packet is already tagged
• Direct: Add the default PCP value
• Map: Use a CoS profile for PCP selection

For each PCP action there is one or two traffic mapping choices and the default PCP bits to
use if the packet does not match the first and the second choices. The following tables show
the valid selection of the first and second choice for each of the PCP actions

PCP Preservation
If this option is selected, PCP bits are copied from the first VLAN(if any). If the packet is not
tagged, the user may select the PCP bits from an IP precedence / DSCP CoS profile. It is also
possible to select a bandwidth regulator set for traffic regulation.

Parameter First choice Second choice

Type IP Precedence / DSCP N/A

CoS profile CoS profile N/A

BWR set Optional N/A

PCP Direct
If this option is selected, the first and second choices are ignored. The PCP bits are forced to
the default green or yellow values based on the result of the bandwidth regulator or the
pre-marking color. It should be noted that the pre-marking color red is ignored if the default
bandwidth regulator is not enabled.

76
5: Monitoring and filtering Traffic policies and monitoring

Parameter First choice Second choice

Type N/A N/A

CoS profile N/A N/A

BWR set N/A N/A

PCP mapping
If this option is selected, the first and second choices can be used to map and regulate traffic
based on PCP / IP precedence /DSCP values. The table below shows the valid configurations
of the first and second choices.

Parameter First choice Second choice

Type VLANinVLAN VLAN, IP precedence, DSCP

VLAN IP precedence, DSCP
IP precedence, DSCP VLAN, VLANinVLAN
CoS profile CoS profile CoS profile

BWR set Optional Optional

Encapsulation None
This option can be used to perform traffic regulation based on PCP / IP precedence /DSCP
values. The selected CoS profile in the first and second choices are ignored. The table below
shows the valid configurations of the first and second choices.

Parameter First choice Second choice

Type VLANinVLAN VLAN, IP precedence, DSCP

VLAN IP precedence, DSCP
IP precedence, DSCP VLAN, VLANinVLAN
CoS profile Ignored Ignored

BWR set BWR set BWR set

Encapsulation Pop
This option can be used to perform traffic regulation based on PCP / IP precedence /DSCP
values before removing the VLAN tag. The selected CoS profile in the first and second
choices are ignored.

77
5: Monitoring and filtering Traffic policies and monitoring

Parameter First choice Second choice

Type VLANinVLAN VLAN, IP precedence, DSCP

VLAN IP precedence, DSCP
IP precedence, DSCP VLAN, VLANinVLAN
CoS profile Ignored Ignored

BWR set BWR set BWR set

Default/Direct Bandwidth regulator

Enable bandwidth regulation
Check this box to activate a default bandwidth regulator.

Pre-marking color
Pre-mark, with a specific color, the traffic that does not match the first and second choices.
This option has no effect if the enabled bandwidth regulator is color-blind. In addition, if no
bandwidth regulator is enabled, this option selects the default green/yellow CFI & PCP values
to be used in the outgoing packets.
Green traffic will use buffers from CIR until depleted at which time it will be tagged as Yellow
data.
Yellow traffic will use buffers from either CIR + EIR or just EIR depending on the coupling flag
set in the regulator. Once CIR + EIR buffers are depleted, this data will be tagged as Red
data.
Red traffic will be dropped. Please note, that it's not possible to pre-mark data as red if there
bandwidth regulator is disabled.
Traffic color will affect how the regulator handles the traffic. For details see "Color mode" on
page 88.

Bandwidth regulator
Choose a default bandwidth regulator that will be associated with the traffic matched by this
policy. To define a bandwidth regulator see "Bandwidth policing" on page 86.

CFI/PCP
The default CFI and PCP values to be applied if the Encapsulation is Push. This would only be
applied if the traffic does not match the first and second choices.

78
5: Monitoring and filtering Traffic filters

Traffic filters
To develop specific access policies and to make traffic monitoring more efficient and effective,
custom (layer 2 or IPv4) filters can be applied to the traffic before it is presented on the
monitor ports. This reduces overhead and enables access policies and monitoring to be
targeted at specific types of traffic only.
By default, commonly used filters are defined for both layer 2 and IPv4.

Viewing L2 To view a list of active L2 traffic filters, open the Traffic > L2 Filters page. By default,
filters commonly used filters are defined.

The following information is presented for each filter:

• Filter name: Unique name assign to the filter.
• MAC destination: Indicates the destination MAC address assigned to the filter. The filter
will only process frames being sent to this address. The address is specified as six pairs
of hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx).
• MAC source: Indicates the source MAC address assigned to the filter. The filter will only
process frames received from this address. The address is specified as six pairs of
hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx).
• Ethertype: Identifies the Ethernet frame type that this filter will process. Other frame
types are ignored.
• VLAN1: Indicates the VLAN ID assigned to the filter. The filter will only process frames
tagged with this VLAN ID.
• VLAN 2: Indicates the second VLAN ID assigned to the filter. Used to process VLAN in
VLAN traffic.

79
5: Monitoring and filtering Traffic filters

Configuring an To configure an L2 filter, do the following:

L2 filter 1. Open the Traffic > L2 Filters page.
2. Click Add to create a new file, or click the filter name to edit and existing one.
3. Configure filter parameters and click Apply.

L2 filter L2 filter name

parameters Specify a name to uniquely identify the filter.

Ethernet header settings

The following characteristics can be defined.

MAC destination / mask

Specify the destination MAC address and mask. Specify the address as six pairs of
hexadecimal digits separated by colons (xx:xx:xx:xx:xx:xx). Only the bits specified by the
mask are used. The other bits are ignored.

MAC source / mask

Specify the source MAC address and mask. Specify the address as six pairs of hexadecimal
digits separated by colons (xx:xx:xx:xx:xx:xx). Only the bits specified by the mask are used.
The other bits are ignored.

Ethertype
Select a well-known protocol from the list or specify a value manually (hexadecimal).

80
5: Monitoring and filtering Traffic filters

"VLAN" and "VLAN in VLAN" settings

You can specify several VLAN fields for the first VLAN (VLAN 1) as well as the second level
VLAN (VLAN 2).
Note: If a check box is not checked, then the value is ignored.

Ethertype
Specify the VLAN Ethernet Type. The Ethernet type identifies if the following VLAN is a
C-VLAN an S-VLAN or if we accept both types.

CFI/DEI
Specify the Canonical Format Indicator or the Drop Eligibility Indicator. This should always be
set to zero for connection to Ethernet switches. CFI is used for compatibility reasons between
Ethernet type networks and Token Ring type networks. If a frame received at an Ethernet port
has a CFI set to 1, then that frame should not be forwarded "as is" to an untagged port.

Priority
Specify the VLAN priority. Allows you to provide CoS prioritization by using the standard
based 802.1Q priority tag. Possible values are 0 to 7. Interpretation is based on the carrier's
equipment and administrative policies.

Priority operator
VLAN priority operator. Valid operator types are: Greater than, Less than, Equal to or Range
(inclusive range).

VLAN ID
Specify the VLAN ID that will be used to filter traffic.

VLAN ID operator
VLAN ID operator. Valid operator types are: Greater than, Less than, Equal to or Range
(inclusive range).

DSCP/IP precedence
Specify the DSCP/IP precedence that will be used to filter traffic.
DSCP/IP precedence operator
DSCP/IP precedence operator. Valid operator types are: Greater than, Less than, Equal to or
Range (inclusive range).

Note:
A limitation exists for the operators. Only one of the VLAN operators can be set to a range, the
other needs to be set to Equal to. For instance if you select a Range for the second VLAN ID
operator you need to select Equal to for the first VLAN ID operator.

81
5: Monitoring and filtering Traffic filters

Viewing IPv4 To view a list of active IPV4 traffic filters, open the Traffic > IPV4 Filters page. By default,
filters commonly used filters are defined.

The following information is presented for each filter:

• Filter name: Unique name assigned to the filter.
• IP source: Indicates the source address assigned to the filter. The filter will only process
packets received from this address. The address is specified in dotted decimal notation.
Note: Filtering source or destination IP address assigned by Dynamic Host Control
Protocol (DHCP) can cause problems. You should ensure that all IP addresses specified
in a filter are static or reserved. Otherwise you must have to manually update your filter
every time the addresses change.
• IP destination: Indicates the destination address assigned to the filter. The filter will only
process packet being sent to this address. The address is specified in dotted decimal
notation.
Note: Filtering source or destination IP address assigned by Dynamic Host Control
Protocol (DHCP) can cause problems. You should ensure that all IP addresses specified
in a filter are static or reserved. Otherwise you must have to manually update your filter
every time the addresses change.

82
5: Monitoring and filtering Traffic filters

• Protocol: Identifies the protocol type that this filter will process. Other protocol types are
ignored. Common protocol are TCP (6),UDP (17) and ICMP (1)
• TCP is used by HTTP, FTP, Telnet, SMTP,
• UDP is used by DNS, SNMP, RIP,
• ICMP is used by Ping,
• Src port: Identifies the source port that will be used to match this rule. This setting is only
valid when the protocol field is set to TCP (6) or UDP (17).
• Dst port: Identifies the destination port that will be used to match this rule. This setting is
only valid when the protocol field is set to TCP (6) or UDP (17).

Configuring an To configure an IPV4 filter, do the following:

IPv4 filter 1. Open the Traffic > IPV4 Filters page. By default, commonly used filters are defined.
2. Click Add to create a new file, or click the filter name to edit and existing one.
3. Configure filter parameters and click Apply.

83
5: Monitoring and filtering Traffic filters

IPv4 filter IPv4 filter name

parameters Specify a name to uniquely identify the filter.

IPv4 header settings

The following characteristics can be defined:

IPv4 source / mask

Specify the source address and mask. Only the bits specified by the mask are used. The other
bits are ignored.

IPv4 destination / mask

Specify the destination address and mask. Only the bits specified by the mask are used. The
other bits are ignored.

TTL
Specify the time-to-live value to match.

DSCP
The DiffServ Code Points (DSCP) value may be selected from a list of predefined values or a
decimal value between 0 and 63 may be defined.

Protocol
Select a well-known protocol from the list or specify a port number manually (decimal).

ECN
Explicit Congestion Notification. Specify either 0 or 3.

Header length
Specify the header length in 32-bit units. Specify a value in the range of 5 - 15.

UDP/TCP port settings

Specify the UDP or TCP port number used by the IPv4 source and IPv4 destination port fields.
These settings are only valid when the Protocol field is set to TCP (6) or UDP (17).

ICMP settings
Specify the ICMP message type that this filter will match. These settings are only valid when
the Protocol field is set to ICMP (1).
Some well-known ICMP types are:
Echo Reply (0)
Destination Unreachable (3)
Redirect (5)
Echo (8)
Time Exceeded (11)
ICMP Code: See www.iana.org for current values

"VLAN" and "VLAN in VLAN" settings

You can specify several VLAN fields for the first VLAN (VLAN 1) as well as the second level
VLAN (VLAN 2).
Note: If a check box is not checked, then the value is ignored.

84
5: Monitoring and filtering Traffic filters

Ethertype
Specify the VLAN Ethernet Type. The Ethernet type identifies if the following VLAN is a
C-VLAN an S-VLAN or if we accept both types.

CFI/DEI
Specify the Canonical Format Indicator or the Drop Eligibility Indicator. This should always be
set to zero for connection to Ethernet switches. CFI is used for compatibility reasons between
Ethernet type networks and Token Ring type networks. If a frame received at an Ethernet port
has a CFI set to 1, then that frame should not be forwarded "as is" to an untagged port.

Priority
Specify the VLAN priority. Allows you to provide CoS prioritization by using the standard
based 802.1Q priority tag. Possible values are 0 to 7. Interpretation is based on the carrier's
equipment and administrative policies.

Priority operator
VLAN priority operator. Valid operator types are: Greater than, Less than, Equal to or Range
(inclusive range).

VLAN ID
Specify the VLAN ID that will be used to filter traffic.

VLAN ID operator
VLAN ID operator. Valid operator types are: Greater than, Less than, Equal to or Range
(inclusive range).

DSCP/IP precedence
Specify the DSCP/IP precedence that will be used to filter traffic.
DSCP/IP precedence operator
DSCP/IP precedence operator. Valid operator types are: Greater than, Less than, Equal to or
Range (inclusive range).

Note:
A limitation exists for the operators. Only one of the VLAN operators can be set to a range, the
other needs to be set to Equal to. For instance if you select a Range for the second VLAN ID
operator you need to select Equal to for the first VLAN ID operator.

85
5: Monitoring and filtering Bandwidth policing

Bandwidth policing
Traffic regulators enable you to limit the flow of traffic for a specific policy. A total of 15 traffic
regulators can be defined.
To view a list of all defined regulators, open the Traffic > Regulators page. Initially this page
is empty as no regulators are defined by default.

The following information is presented for each filter:

• Name: Unique name assigned to the regulator.
• CIR: Committed Information Rate.
• CBS: Committed Burst Size.
• EIR: Excess Information Rate. Range.
• EBS: Excess Burst Size. Range: < 2 to 62 >
• Color mode: Indicates if the regulator reacts to data color.
• Coupling Flag: Modifies the way in which the regulator processes yellow traffic.

86
5: Monitoring and filtering Bandwidth policing

Configuring a To configure a traffic regulator, do the following:

regulator 1. Open the Traffic > Regulators page.
2. Click Add to define a new regulator.:
3. Configure settings and click Apply.

Regulator Traffic regulator name

settings Specify a name to uniquely identify the regulator.

Committed Information Rate (CIR)

Specify the maximum average bandwidth for traffic declared green by the regulator. Green
traffic in excess of this maximum will be declared yellow by the regulator and will be submitted
to EIR regulation.
Range: 0 to maximum port speed (in kbps)

Committed Burst Size

Specify the maximum burst size for traffic declared green by the traffic regulator.
Range: 2 to 62 kBytes
Note: Burst size must be greater than the port MTU.

Excess Information Rate (EIR)

Specify the maximum average bandwidth for traffic declared yellow by the regulator. Yellow
traffic in excess of this maximum will be declared red by the regulator and will be dropped.
Range: 0 to maximum port speed (in kbps)

Excess Burst Size

Specify the maximum burst size for traffic declared yellow by the traffic regulator.
Range: 2 to 62 kBytes
Note: Burst size must be greater than the port MTU.

87
5: Monitoring and filtering Bandwidth policing

Color mode
Specifies how the initial color of traffic should be attributed.
• color-aware: Traffic enters the traffic regulator with the color set by a policy.
• color-blind: All incoming traffic enters the traffic regulator initially green.

Coupling Flag
Modifies the way in which the regulator processes yellow traffic.
• False: Yellow data is limited by the setting of the Excess Information Rate.
• True: Yellow data is limited by the setting of the Committed Information Rate plus the
Excess Information Rate.

Assigning a Once a regulator has been configured you can assign it to a policy. See "Traffic policies and
regulator to a monitoring" on page 74.

policy

88
6: Alarms Alarm settings

Chapter 6: Alarms

6 Alarms

Alarm settings
General alarm settings are defined on the Alarm > General page.
Note: For a list of all supported alarms, see Appendix A.

Notification
There are four mechanisms for alarm reporting: LED, syslog, SNMP, and 802.3AH.
• Enable LED reporting: Reports alarms by activating the appropriate EtherNID LED
corresponding to the severity of the alarm.
• Enable syslog reporting: Reports alarms by creating syslog entries.
• Enable SNMP reporting: Reports alarms via SNMP traps from Accedian’s private MIB.
• Enable 802.3AH reporting: Reports alarms via 802.3AH organization specific
OAMPDUs.

Thresholds
• Threshold on (soaking time in msecs): Delay after an event is detected before the
alarm notification occurs.
• Threshold off (soaking time in msecs): Delay after an event clears before the alarm
clear notification occurs.

89
6: Alarms Alarm configuration

Alarm configuration
The Alarm > Configuration page lists all defined alarms.

For a description of each field see "Customizing an alarm" on page 91.

90
6: Alarms Alarm configuration

Customizing an To customize an alarm, click its Identifier.

alarm

Identifier
Unique number that identifies this alarm. Assigned by the EtherNID.
The alarm identifier is compose of 3 fields, the module number, the instance number and the
error number. The alarm number look like this AAA.BBB.CC and is express in decimal.
AAA: Module number (1-999).
BBB: Instance number (1-999).
CC: Error number (1-99).
A module number is assigned for each source of alarm in the system. For instance the port
module is set to 1, the SFP module is set to 2, the PAA is set to 3 and the environmental is set
to 8.

ID Description
1 Port module for link down and others related alarms.

2 SFP module for Rx/Tx power, temp, vcc and lbc alarms and warnings.

3 PAA module for CC, Packet Loss and others related alarms.

4 Unassigned

5 Unassigned

6 Unassigned

7 Unassigned

8 Environmental module for fans, power supplies and temperature

sensors.

9 Unassigned

10 Unassigned

Enable
Indicates if the alarm is enabled (true) or disabled (false). If enabled, the alarm will be
reported

91
6: Alarms Alarm configuration

Severity
Indicates the severity level for the alarm. If LED reporting is enabled on the Alarm > General
page, the Minor, Major, and Critical alarms will be indicated on the EtherNID front panel LEDs.
• Informational: No effect on service. Provides status information.
• Minor: A error condition has occurred that does not seriously affect system functionality.
• Major: A serious disruption 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
Specify if the alarm will be displayed as service affecting or non-service affecting.

Description
Textual description of the alarm.

92
6: Alarms Alarm status

Alarm status
The Alarm > Status page presents a summary of all alarms.

For a description of each field see "Customizing an alarm" on page 91.

To view detailed information on an alarm click its Identifier. For example:

93
6: Alarms Chassis alarms

Chassis alarms
The Alarm > Chassis page presents chassis-related status, alarms, and alarm settings.

Power supply status

Indicates the status of the various power sources.
• 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 sensor status

Indicates the current temperature inside the unit.

Temperature sensor thresholds

• First threshold: Indicates the temperature that will activate a first overheat temperature
alarm.
• Second threshold: Indicates the temperature that will activate a second overheat
temperature alarm.

94
7: Operations, Administration and Maintenance OAM configuration

Chapter 7: Operations, Administration and Maintenance

7 Operations, Administration and

Maintenance

OAM configuration
To view a list of all OAM instances and their settings, open the OAM > Configuration page.

The following information is presented for each instance:

• Name: The instance name as defined in the configuration page. Click this name to
configure the instance.
• OAM state: Indicates if an instance is enabled or disabled. This field does not indicate a
successful discovery of an OAM peer. See the status page for details.
• OAM mode: The OAM instance may be active or passive. When passive, the instance
will only listen and reply to received information type length and value (TLV) frames during
the discovery phase. An active instance actively transmit unsolicited information TLV
frames.
• Port: Indicates the port used by this OAM instance.
• Encapsulation: Indicates if OAM packets are tagged with a VLAN or not.

95
7: Operations, Administration and Maintenance OAM configuration

Configuring an To configure an OAM instance, do the following:

OAM instance 1. Open the OAM > Configuration page.
2. Click Add to add a new OAM instance.
3. Configure OAM instance settings and click Apply.

OAM instance OAM instance name

parameters Specify a name to identify the OAM instance.

Port name
Indicates the port used by this OAM instance.

Encapsulation
Indicates if OAM packets are tagged with a VLAN or not.

Enable OAM protocol

Enable the passive or active OAM 802.3AH protocol for this OAM instance. An active instance
will immediately start to send information OAMPDUs associated with the discovery process.

96
7: Operations, Administration and Maintenance OAM configuration

Active Mode / Passive Mode

Select the mode of operation for the OAM instance.
• Passive: Listens for OAMPDUs and replies once it starts receiving them.
• Active: Immediately searches for an OAM peer by sending OAMPDUs.

Max OAM PDU size

Specify the maximum frame size the OAM instance will use. This enables you to limit the
impact of the extra OAM traffic on a link that is already heavily loaded.

This unit supports loopback

Enable this option to react to loopback requests from the OAM peer.

This unit supports events

Enable this option to issue event OAMPDUs when needed.

This unit supports variable responses

Enable this option to respond to OAMPDUs requests.

Number of Events re-transmitted

Specify the number of times an event is re-transmitted to ensure its reception by the peer.
This setting is only valid if This unit supports events is enabled.

Errored Frame Event (EFE) Threshold and window

Specify the threshold setting that defines the number of frame errors that must be detected in
a given period to trigger the transmission of an event.
The window setting defines the time, in seconds, of the period.
A frame error is an error detected at the layer 2, or MAC level. This can be caused by various
types of errors including, but not limited to, CRC errors, short frames, long frames, etc.

Errored Frame Period Event (EFPE) Threshold and window

Specify the threshold setting that defines the number of frame errors that must be detected in
a given period to trigger the transmission of an event.
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.
A frame error is an error detected at the layer 2, or MAC, level. This can be caused by various
types of errors including, but not limited to: CRC errors, short frames, long frames, etc.

Errored Frame Seconds Summary Event (EFSSE)

Threshold and window
Specify the threshold setting that defines the number of frame errors that must be detected in
a given period to trigger the transmission of an event.
An errored frame second is a one second period in which at least one frame was bad. In other
words, this event is generated when the number of seconds with any number of bad frames is
greater than or equal to the threshold during a period defined by the window.
The window setting defines the time, in seconds, of the period.
A frame error is an error detected at the layer 2, or MAC, level. This can be caused by various
types of errors including, but not limited to: CRC errors, short frames, long frames, etc.

97
7: Operations, Administration and Maintenance Loopbacks

Loopbacks
The EtherNID supports in-service loopbacks on either the client or network ports. To view a
list of all loopbacks and their settings, open the OAM > Loopback page.

The following information is presented for each loopback:

• Name: This field reports the loopback instance name, as configured in the loopback
configuration page. Click on an instance name to configure it.
• Lpbk state: Reports the enable/disable state of the loopback. An enabled loopback may
not necessarily loopback traffic; this depends on the location setting. An instance enabled
to react on external loopback commands is not shown in this field.
• Lpbk mode: The loopback control logic, once enabled, may be using the standard IEEE
802.3ah mode or may be using a private or proprietary mode. When using the private
mode, the user can select filters and can allow other traffic to flow through, effectively
doing an in-service loopback.
• Location: A loopback instance may be local or remote. Once enabled, a local loopback
immediately applies the loopback to the unit as programmed. An enabled remote
loopback will instruct the unit to transmit a loopback request to its OAM partner.
• Filter type: For private loopback mode, a filter must be selected. See the loopback
configuration page for details.

98
7: Operations, Administration and Maintenance Loopbacks

Adding a To add a loopback, do the following:

loopback 1. Only one loopback is supported per OAM instance. Therefore, before you can add a new
loopback, you must first add an OAM instance on the OAM > Configuration page.
2. Open the OAM > Loopback page.
3. Configure loopback parameters and click Apply.

Loopback Name
parameters The OAM instance name as defined in the OAM configuration page.

State
The current state of the loopback.

Loopback enable
Enables the loopback function.

Type
• Iometrix L1: Iometrix cNode level 1. Loopback all packets that have a destination address
equal to 00:30:79:FF:FF:FF
• Exfo L2: Loopback all packets that have a source MAC OUI equal to 00:03:01
• Exfo L3: Loopback all UDP echo service packets.
• Custom: Loopback all traffic that matches the user defined filter.

99
7: Operations, Administration and Maintenance Loopbacks

Persistent
Enable or disable loopback at startup time. This option can only be set for Manual loopbacks
with no timeout.

Filter type
Select the filter type that will be applied to the loopback traffic. For more information on filters,
see "Traffic filters" on page 79.

L2 filter
If Filter type is set to L2 filter, select the L2 filter that will be applied to loopback traffic.

IPV4 filter
If Filter type is set to IPv4 filter, select the IPv4 filter that will be applied to loopback traffic.

Actions
• 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 traffic originating from Client port when looping back to the Network port and vice
versa.
Warning: Enabling this option will interrupt the Ethernet service in one direction.

Loopback timeout
Specify the number of minutes that the loopback will remain enabled. When the timeout expires
the loopback is automatically removed.

Remote loopback enable

These options allow loopbacks to be activated remotely using the following devices/protocols:
• JDSU/ActernaTM
• Enable discovery loop commands: Accept or discard JDSU/Acterna discovery
loopback commands.
• SunriseTM: The EtherNID supports tests on layers 2 and 3.
• OAM 802.3AH
Note: This option is not affected by the setting of Loopback enable.

Accept VLAN loop commands:

When enabled, VLAN loopback commands will be accepted. This option is only valid for
untagged OAM instances. Tagged OAM instances only accept loopback commands from a
specific VLAN.
Note: This option is not affected by the setting of Loopback enable.

100
7: Operations, Administration and Maintenance OAM events

OAM events
The OAM > Event page, lists a summary of all the events exchanged on an OAM connection.

The following information is presented for each event:

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

For complete details on transmitted and received events, click a Name.

101
7: Operations, Administration and Maintenance OAM events

Transmitted OAM Local Error Symbol Period Event

and Received A sequence of six integers corresponding to the respective fields in the most recently
event transmitted Errored Symbol Period Event TLV in an Event Notification OAMPDU. This
sequence is updated when a request service primitive is generated within the OAM sublayer
notifications with an OAMPDU Code field value equal to the Event Notification code and Event TLV Type
field equal to the Errored Symbol Period Event value.
• The first INTEGER represents the Event Time Stamp field.
• The second INTEGER represents the Errored Symbol Window field.
• The third INTEGER represents the Errored Symbol Threshold field.
• The fourth INTEGER represents the Errored Symbols field.
• The fifth INTEGER represents the Error Running Total field.
• The sixth INTEGER represents the Event Running Total field.

OAM Local Error Frame Event

A sequence of six integers corresponding to the respective fields in the most recently
transmitted Errored Frame Event TLV in an Event Notification OAMPDU. This sequence is
updated when a request service primitive is generated within the OAM sublayer with an
OAMPDU Code field value equal to the Event Notification code and Event TLV Type field
equal to the Errored Frame Event value.
• The first INTEGER represents the Event Time Stamp field.
• The second INTEGER represents the Errored Frame Window field.
• The third INTEGER represents the Errored Frame Threshold field.
• The fourth INTEGER represents the Errored Frames field.
• The fifth INTEGER represents the Error Running Total field.
• The sixth INTEGER represents the Event Running Total field.

OAM Local Error Frame Period Event

A sequence of six integers corresponding to the respective fields in the most recently
transmitted Errored Frame Period Event TLV in an Event Notification OAMPDU. This
sequence is updated when a CTL:OAMI:request service primitive is generated within the
OAM sublayer with an OAMPDU Code field value equal to the Event Notification code and
Event TLV Type field equal to the Errored Frame Period Event value.
• The first INTEGER represents the Event Time Stamp field.
• The second INTEGER represents the Errored Frame Period Threshold field.
• The third INTEGER represents the Errored Frame Period Threshold field.
• The fourth INTEGER represents the Errored Frame Period Threshold field.
• The fifth INTEGER represents the Error Running Total field.
• The sixth INTEGER represents the Event Running Total field.

102
7: Operations, Administration and Maintenance OAM events

OAM Local Error Frame Seconds Summary Event

A sequence of six integers corresponding to the respective fields in the most recently
transmitted Errored Frame Seconds Summary Event TLV in an Event Notification OAMPDU.
This sequence is updated when a request service primitive is generated within the OAM
sublayer with an OAMPDU Code field value equal to the Event Notification code and Event
TLV Type field equal to the Errored Frame Seconds Summary Event value.
• The first INTEGER represents the Event Time Stamp field
• The second INTEGER represents the Errored Frame Seconds Summary Window field
• The third INTEGER represents the Errored Frame Seconds Summary Threshold field
• The fourth INTEGER represents the Errored Frame Seconds Summary field
• The fifth INTEGER represents the Error Running Total field
• The sixth INTEGER represents the Event Running Total field

103
7: Operations, Administration and Maintenance OAM status

OAM status
The OAM > Status page presents a summary of the status of each OAM instance.

The following information is presented for each instance:

• Name: OAM instance name.
• Discovery: Identifies the current state of the OAM Discovery function. The enumerations
match the states 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 flags: A string of seven bits corresponding to the Flags field in the most recently
transmitted OAMPDU.
• 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 flags: A string of seven bits corresponding to the Flags field in the most recently
received OAMPDU.
• 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.

104
7: Operations, Administration and Maintenance OAM status

• 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.
• Note: The revision number indicates the number of times that the configuration for the
local OAM instance has been modified.
• Remote revision: The value of the Revision field in the Local Information TLV of the most
recently received Information OAMPDU. This value is updated on reception of a valid
frame.

For detailed status information, click a Name. For example:

Detailed status Local

information Info TLV revision
The value of the Revision field in the Local Information TLV of the most recently transmitted
Information OAMPDU.

Parser state / Mux state

A string of three bits corresponding to the State field of the most recently transmitted
Information OAMPDU. The first and second bits corresponds 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 on 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 on reception of a valid frame, with:
• DestinationField equal to the reserved multicast address for slow protocols
• LengthOrType 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

105
7: Operations, Administration and Maintenance OAM status

Remote
Info TLV revision
The value of the Revision field in the Remote Information TLV of the most recently received
Information OAMPDU.

Parser state / Mux state

A string of three bits corresponding to the State field of the most recently received Information
OAMPDU. The first and second bits corresponds 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.

106
7: Operations, Administration and Maintenance OAM statistics

OAM statistics
The OAM > Statistics page, presents a summary of the statistics for each OAM instance.

The following information is presented for each instance:

• Name: OAM instance name.
• Rcv OAMPDU: Number of OAMPDUs received by this instance. Include all types: info,
var request, var response, loopback etc.
• Txm OAMPDU: Number of OAMPDUs transmitted by this instance. Include all types:
info, var request, var response, loopback etc.
• Rcv Info OAMPDUs: Number of Info OAMPDUs received by this instance.
• Txm Info OAMPDUs: Number of Info OAMPDUs transmitted by this instance.

For complete detailed statistics, click a Name. For example:

107
7: Operations, Administration and Maintenance OAM statistics

OAM detailed Name

statistics The name of the OAM instance.

information
Receive
Unsupported codes
A count of OAMPDUs received that contain an OAM code that are not supported by the
device. This counter is incremented on reception of a valid frame with:
• Destination Field 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.
• An OAMPDU code for a function that is not supported by the device.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Information
A count of OAMPDUs received that contain the OAM Information code. This counter is
incremented on reception of a valid frame, with:
• Destination Field 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 equals the OAM Information code and is supported by the device.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Unique event
A count of the OAMPDUs received that contain the Event Notification code. This counter is
incremented on reception of a valid frame, with:
• DestinationField equal to the reserved multicast address for slow protocols.
• LengthOrType 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 equals the Event Notification code.
• The Sequence Number field is not equal to the Sequence Number field of the last
received Event Notification OAMPDU and is supported by the device.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

108
7: Operations, Administration and Maintenance OAM statistics

Duplicate event
A count of the OAMPDUs received that contain the Event Notification code. This counter is
incremented on reception of a valid frame, with:
• DestinationField equal to the reserved multicast address for slow protocols.
• LengthOrType 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 equals the Event Notification code.
• The Sequence Number field is equal to the Sequence Number field of the last received
Event Notification OAMPDU.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Loopback control
A count of OAMPDUs received that contain the Loopback Control code. This counter is
incremented on reception of a valid frame, with:
• DestinationField equal to the reserved multicast address for slow protocols.
• LengthOrType 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 equals the Loopback Control code and is supported by the device.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Variable request
A count of OAMPDUs received that contain the Variable Request code. This counter is
incremented on reception of a valid frame, with:
• DestinationField equal to the reserved multicast address for slow protocols.
• LengthOrType 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 equals the Variable Request code and is supported by the device.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Variable response
A count of OAMPDUs received that contain the Variable Response code. This counter is
incremented on reception of a valid frame, with:
• DestinationField equal to the reserved multicast address for slow protocols.
• LengthOrType 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 equals the Variable Response code and is supported by the device.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

109
7: Operations, Administration and Maintenance OAM statistics

Organization specific
A count of OAMPDUs received that contain the Organization Specific code. This counter is
incremented on reception of a valid frame, with:
• DestinationField equal to the reserved multicast address for slow protocols.
• LengthOrType 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 equals the Organization Specific code and is supported by the
device.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Transmit
Unsupported codes
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that are not
supported by the device. 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.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Information
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain
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.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Unique event
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain
the Event Notification code. This counter is incremented when a request service primitive is
generated within the OAM sublayer.
• A Slow_Protocols subtype value equal to the subtype reserved for OAM.
• The OAMPDU code equals the Event Notification code.
• The Sequence Number field is not equal to the Sequence Number field of the last
transmitted Event Notification OAMPDU.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

110
7: Operations, Administration and Maintenance OAM statistics

Duplicate event
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain
the Event Notification code. This counter is incremented when a request service primitive is
generated within the OAM sublayer.
• The OAMPDU code equals the Event Notification code.
• The Sequence Number field is equal to the Sequence Number field of the last transmitted
Event Notification OAMPDU.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Loopback control
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain
the Loopback Control code. This counter is incremented when a request service primitive is
generated within the OAM sublayer with an OAM code indicating a Loopback Control
OAMPDU.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Variable request
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain
the Variable Request code. This counter is incremented when a request service primitive is
generated within the OAM sublayer with an OAM code indicating a Variable Request
OAMPDU.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Variable response
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contain
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.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

Organization specific
A count of Organization Specific OAMPDUs passed to the OAM subordinate sublayer for
transmission that contain 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.
Generalized nonresettable counter. This counter has a maximum increment rate of slow
protocol frames (No more than 10 frames shall be transmitted in any one-second period).

111
7: Operations, Administration and Maintenance OAM statistics

112
8: RFC-2544 RFC-2544 Generator

Chapter 8: RFC-2544

8 RFC-2544

RFC-2544 Generator
NOTE: The RFC-2544 feature is only available on the EtherNID GE and MetroNID TE /
TE-R models.

Viewing To view the RFC-2544 generator configuration, open the RFC-2544 > Generator >
RFC-2544 Configuration page.

Generator

To edit any existing settings, click the flow profile setting.

Test Description
Description configured to identify the test and its characteristics.

Outgoing port
Name configured for the port out which to send the flow(s).

Enable flows
Checkboxes to specify the flow(s) included in the test.

113
8: RFC-2544 RFC-2544 Generator

Configuring 1. To edit the RFC-2544 Packet header settings, select First header packet settings show
RFC-2544 details button of the flow to be edited.

Generator

Type
Layer-2 or Layer-3.

Layer-2 settings
Port name
Name configured for the port on which to send the flow(s).

MAC destination
This is the peer MAC address.

Y.1731 MEG level

The maintenance Entity Group level.

Layer-3 settings
Destination IP address
The IP address of the remote side.

DSCP
The DiffServ Code Point to set in the generated packets.

UDP port settings (Source & Destination)

Specify the UDP port numbers used to generate the UDP packet.

Enable VLAN 1 header

This is to encapsulate all packets with 1 VLAN header.

114
8: RFC-2544 RFC-2544 Generator

VLAN 1 ID
First VLAN ID. When enabled, all test packets are encapsulated into the specified VLAN ID.

VLAN 1 Ethernet type

First VLAN Ethernet type. Applies only when VLAN 1 header is enabled.

VLAN 1 Priority
First VLAN priority bits. Applies only when VLAN 1 header is enabled.

VLAN 1 CFI
First VLAN canonical format indicator (CFI). Applies only when VLAN 1 header is enabled.

Enable VLAN 2 header

This is to encapsulate all packets with 2 VLAN headers. (.1Q in .1Q)

VLAN 2 ID
Second VLAN ID. When enabled, all test packets are encapsulated into the second specified
VLAN ID. Applies only when VLAN 1 header is enabled.

VLAN 2 Ethernet type

Second VLAN Ethernet type. Applies only when VLAN 2 header is enabled.

VLAN 2 Priority
Second VLAN priority bits. Applies only when VLAN 2 header is enabled.

VLAN 2 CFI
Second VLAN canonical format indicator (CFI). Applies only when VLAN 2 header is enabled.

115
8: RFC-2544 RFC-2544 Generator

2. To edit the RFC-2544 Flows , select flow settings show details button of the flow to be
edited.

Flow type
The type of flow testing being done. Either In-service (sharing a traffic regulator with client
traffic) or Out-of-service (using the full link bandwidth).

Regulator
Regulator to use when In-service flow type is selected. When Out-of-service flow type is
selected, this field has no effect.

Flow name
Unique name assigned to the flow.

Flow description
Description to identify the flow and its characteristics.

Traffic type
Select between burst or constant rate traffic.
• Constant: The constant traffic type consist of sending packets at a specific bit rate
(Kbps).
• Burst: The burst traffic type consist of sending a configured number of packets at every
period. The period is a number of milli-seconds between each burst of packets.

116
8: RFC-2544 RFC-2544 Generator

Size type
Select between fixed or random size. The fixed configuration requires a packet Size to be
specified. The random configuration requires a Minimum size value and a Maximum size
value to be specified.

Payload pattern
Select between fixed-data, incremental or random patterns in the payload part of the transmit-
ted frames. For the random configuration you need to select one of the supported patterns.

Duration type
Choose between the following duration types:
• Continuous : Stops only when user manually stops the test.
• Seconds : Stops after a specified amount of seconds.
• Bytes : Stops after sending a specified amount of bytes.
• Packets : Stops after sending a specified amount of packets.

117
8: RFC-2544 RFC-2544 monitor

RFC-2544 monitor
NOTE: The RFC-2544 feature is only available on the EtherNID GE and MetroNID TE /
TE-R models.

Viewing To view the RFC-2544 monitors, open the RFC-2544 > Monitor page.
RFC-2544
Monitor

Name
Unique name assign to the monitor.

State
State of the monitor. (Enabled or Disabled)

Mode
Mode of the monitor. (Terminal or Bypass)
• Terminal : The RFC-2544 test will terminate at this NID.
• Bypass : The RFC_2544 test measurements will be taken but the traffic will follow the
rules configured in the Policies for this specific traffic type.

Port
Incoming port of the monitor.

Type
Type of packets being inspected. (Layer-2 or Layer-3)

118
8: RFC-2544 RFC-2544 monitor

Detailed view of To view the deatiled view of RFC-2544 measurements, click on the details link for the specific
RFC-2544 monitor.

Monitor

Monitor results
Name
Unique name assign to the monitor.

State
State of the monitor. (Enabled or Disabled)

Receive statistics
Received packets
Total packets received by the associated inspector.

Received bytes
Total bytes received by the associated inspector.

Rate
Data rate in Mbps. This is the amount of Mbits received in the last second. (step of 1 Mbps)

OOO or duplicates
Out of order or duplicate packets received by this inspector.

Number of gaps
Number of gaps in the sequence number.

Maximum gap
Maximum size of the received gaps.

119
8: RFC-2544 RFC-2544 monitor

One-way delay
Instantaneous
One-way instantaneous delay value in microseconds.

Minimum
Minimum delay in microseconds.

Maximum
Maximum delay in microseconds.

Average
Average delay in microseconds

One-way delay variation

Instantaneous
One-way instantaneous delay variation value in microseconds.

Minimum
Minimum delay variation in microseconds.

Maximum
Maximum delay variation in microseconds.

Average
Average delay variation in microseconds.

120
8: RFC-2544 RFC-2544 testsuite

RFC-2544 testsuite
NOTE: The RFC-2544 testsuite feature is only available on the MetroNID TE / TE-R
models.

Viewing To view the RFC-2544 testsuites, open the RFC-2544 > Testsuite page.
RFC-2544
Testsuites

Once defined, the Testsuite can be run to determine the conformance of a network section or
a specific device.
To add a new testsuite, click the Add button.
To edit any existing testsuite, click the testsuite name in the list.

Name
Unique name assigned to the testsuite.

Description
Description configured to identify the testsuite and its characteristics.

121
8: RFC-2544 RFC-2544 testsuite

Detailed view of To view the deatiled view of RFC-2544 testsuites, click on the testsuite name from the
RFC-2544 testsuite configuration list.

Testsuites

Suite configuration
Suite name
Unique name assigned to the testsuite.

Suite description
Description configured to identify the testsuite and its characteristics.

Jumbo frame size

This defines what size is considered jumbo frames.

Outgoing port
Name configured for the port out which to send the flow(s).

Test to run
Select all conformance tests you want to run in this testsuite.

Peer settings
Information relative to the remote peer and the test packet contents. VLAN protocol IDs are
set to 0x8100 for 802.1Q network when VLAN is chosen. Test packets are Y.1731 LBM and
the MEG (ME Group) level is configurable.

122
8: RFC-2544 RFC-2544 testsuite

Type
Layer-2 or Layer-3.

Layer-2 settings
Port name
Name configured for the port on which to send the flow(s).

MAC destination
This is the peer MAC address.

Layer-3 settings
Destination IP address
The IP address of the remote side.

DSCP
The DiffServ Code Point to set in the generated packets.

UDP port settings (Source & Destination)

Specify the UDP port numbers used to generate the UDP packet.

Y.1731 MEG level

The Maintenance Entity Group level.

VLAN ID
VLAN identifier, possible values are 0 to 4095. Applies only when the specific VLAN is
enabled.

VLAN priority
VLAN priority bits, possible values are 0 to 7. Applies only when the specific VLAN is enabled.

VLAN CFI
Specify the Canonical Format Indicator. This should always be set to zero for connections to
Ethernet switches. Applies only when the specific VLAN is enabled.

Throughput settings
These settings are used to define the Throughput test, which searches for the maximum rate
for which there is no frame loss. The Trial duration parameter defines the length during which
throughput will be analyzed and during which no frame loss shall occur. The Maximum rate
and Minimum rate define the range of rates to search for while the Step size defines the
granularity of the range. For example, if the user wishes to measure the quality of a wirespeed
GigE circuit, he would enter a range of 800 Mbps and 1000 Mbps with a step size of 10 Mbps.
The NID would then test at full GigE speed, 1000 Mbps and perform a dichotomist algorithm
between 800 and 1000 (and a granularity of 10) to find the highest rate for which there is no
frame loss. The frame loss setting defines the acceptable difference between measured frame
loss. For example, a setting of 1 would mean a 0.1% frame loss would be acceptable and
considered as no frame loss by the test. The default value is 0, which means absolutely no
frame loss is the target for defining full throughput. The Frame Size parameters let the user
choose which frame sizes are to be tested. By default, the 10000 byte frame size (Jumbo
frame) is unselected as it was not a frame size defined by the RFC-2544 standard, but which
Accedian supports nevertheless.

123
8: RFC-2544 RFC-2544 testsuite

Trial duration
The Trial duration parameter defines the length during which throughput will be analyzed and
during which no frame loss shall occur.

Maximum rate
The Maximum rate defines the upper bound of rates to search for while the Step size defines
the granularity of the range.

Minimum rate
The Minimum rate defines the lower bound of rates to search for while the Step size defines
the granularity of the range.

Step size
The Step size defines the granularity of the range.

Frame loss
The frame loss setting defines the acceptable difference between measured frame loss.

Delay and delay variation settings

Once a wirespeed rate with no frame loss has been defined by the throughput test, the delay
and delay variation test will measure the latency and jitter at that specific rate. If the
throughput test has not been run prior to the delay test, the NID will perform a short
throughput test first (based on the throughput settings). The frame loss setting defines the
acceptable difference between measured frame loss. For example, a setting of 1 would mean
a 0.1% frame loss would be acceptable and considered as no frame loss by the test. The
default value is 0, which means absolutely no frame loss is the target for defining full
throughput. The Frame Size parameters let the user choose which frame sizes are to be
tested. By default, the 10000 byte frame size (Jumbo frame) is unselected as it was not a
frame size defined by the RFC-2544 standard, but which Accedian supports nevertheless.

Trial duration
The Trial duration is the duration for which the test will be run.

Frame loss
The frame loss setting defines the acceptable difference between measured frame loss.

Frame loss settings

The Frame loss test will verify that no frames are being lost for a duration of time, at two
consecutive rates. The test will run for each Frame size selected, for a duration defined by
Trial duration. The Step size indicates the step between each rate being tested. The NID will
start at the Maximum rate defined in the throughput settings and step down by the value set in
the Step size parameter of the Frame loss settings. Two consecutive rates must be frame loss
less in order to successfully pass this test. For example, if the DUT is able to perform full
wirespeed at GigE, the test will run at 1000 Mbps and 980 Mbps (for a Step size of 20 Mbps).
Both tests must yield no frame loss to be successful, or a lower rate will then be tested.

Trial duration
The Trial duration is the duration for which the test will be run.

Step size
The Step size defines the granularity of the range.

124
8: RFC-2544 RFC-2544 testsuite

Back to back settings

The Back-to-back test performs a burst for a duration of time. The NID will again perform a
Back-to-back test for each one of the Frame sizes selected. To be successful, the DUT must
not create any frame loss for each burst. A burst will have a duration specified by the Total
duration parameter, and the NID will perform a number of bursts as defined by the Repeat
parameter. A pause of 2 seconds will be done after each burst.

Trial duration
The Trial duration is the duration for which the test will be run in milli-secs.

Repeat
Indicates the number of bursts perform for each packet size.

125
8: RFC-2544 RFC-2544 reports

RFC-2544 reports
NOTE: The RFC-2544 reports feature is only available on the MetroNID TE models.

Starting an To start an RFC-2544 testsuite, click on the Start new testsuite button in the RFC-2544 >
RFC-2544 Reports page. Configure the report then click the Run button to start the testsuite.

Testsuite

RFC-2544 report configuration

File name
Unique name assigned to the report.

Description
Provide a description to identify the report and its characteristics.

Technician name
Who executed the testsuite.

Testsuite configuration
Select the testsuite you want to run in this report.

Special note
Information relative to the report not included in the previous fields.

126
8: RFC-2544 RFC-2544 reports

Viewing To view the RFC-2544 reports, open the RFC-2544 > Reports page and click on the name of
RFC-2544 the report to view.

Reports

Testsuite Report
Name
Unique name assigned to the report.

Status
Indicates the report's current status. Possible values are:
• Failed : An error occurred during the testsuite execution.
• Running : The testsuite is currently running.
• Stopped : A user stopped the testsuite during its execution.
• Completed : The Testsuite has completed.

Description
Provide a description to identify the report.

127
8: RFC-2544 RFC-2544 reports

Report contents
Once a test suite has finished running, the bottom of the report will look similar to the below
screen shot.

The entire report is displayed below.

128
9: Performance Assurance Agent PAA configuration

Chapter 9: Performance Assurance Agent

9 Performance Assurance Agent

PAA configuration
The EtherNID Performance Assurance Agent™ can be used measure the jitter, latency and
packet loss of a given network. Two EtherNIDs with matching settings will communicate with
each other to collect data.
The PAA can be configured in a point-to-point or point-to-multi-point fashion, either allowing a
single PAA instance to exchange data with another PAA instance or enabling it to
communicate with several PAA instances simultaneously.
To view a summary of all PAA probes, open the PAA > Configuration page.

The following information is presented for each probe.

• Index: A unique identifier assigned to the probe.
• Probe name: Unique name assigned to the probe. Click the name to configure the probe.
• Type: Indicates the type of probe. Possible values are:
• layer-2: Probes occurs at layer 2.
• UDP: Probe occurs using UDP.
• State: Indicates the probe's current state. Possible values are:
• Enabled : Enabled by configuration.
• Disabled : Disabled by configuration.
• Associating : Enabled looking for peer.
• Associated : Enabled peer found.
• Running : Running one time measurement.

129
9: Performance Assurance Agent PAA configuration

• Idle : Idle after one time measurment completed.

• Locked IS : Locked traffic in service.
• Locked OOS : Locked traffic out of service.
• Mode: Indicates if a probe generates (source) or collects (sink) measurement packets or
does both (bi-dir).

130
9: Performance Assurance Agent PAA configuration

Configuring a 1. Open the PAA > Configuration page.

probe 2. Click Add to create a new probe or click the probe name to edit an existing probe.
3. Configure parameters and click Apply.

131
9: Performance Assurance Agent PAA configuration

PAA General
parameters Name
Specify a unique name to identify this probe.

Type
Select the type of probe.
• layer-2: Probes occurs at layer 2.
• UDP: Probe occurs using UDP.

Operation Mode
.Indicatesif a probe generates (Source) or collects (Sink) measurement packets or
does both (Bi-Dir).

Packet size
Size of PAA sample packets. Does not include protocol headers (UDP, IP,Ethernet) nor the 4
CRC bytes. Minimum value is 61. Layer-2 maximum value is 1500. UDP maximum value is
1472.

Sampling Period
Set the interval (in milliseconds) at which the probe issues measurement packets.

PAA state
Select this checkbox to enable the probe.

Layer-2 Parameters
Destination MAC address
Specify the peer’s MAC address. When set to FF:FF:FF:FF:FF:FF, Layer-2 peer address
discovery will be done to automatically find the peer MAC address.

Port name
Select the outgoing port.

VLAN 1 Encapsulation
Select this checkbox to enable encapsulation on VLAN 1.

VLAN 2 Encapsulation
Select this checkbox to enable encapsulation on VLAN 1.

VLAN 1 ID
Set the ID to use for VLAN 1.

VLAN 2 ID
Set the ID to use for VLAN 2.

VLAN 1 Priority
First VLAN priority bits. This applies only if the outgoing interface is encapsulated over a
VLAN.

132
9: Performance Assurance Agent PAA configuration

VLAN 2 Priority
Second VLAN priority bits. This applies only if the outgoing interface is encapsulated over two
VLANs.

EVC fault propagation

Enable fault propagation
Use this PAA probe's status in fault propagation.
Propagate on port
Specify the EVC client port to which the PAA probe status should be propagated. That port
should be also configured to perform EVC fault propagation for this parameter to take effect.

UDP parameters
Destination IP address
The peers IPv4 destination address.

Diff-Serv Codepoint (DSCP)

The Diff-Serv CodePoint value.

Explicit Congestion Notification (ECN)

The Explicit Congestion Notification value.

VLAN 1 Priority
First VLAN priority bits. This applies only if the outgoing interface is encapsulated over a
VLAN.

Continuity
Packet loss reference period
Packet loss reference period.

Packet loss threshold

Packet loss threshold in %.

Continuity check threshold

Continuity check threshold. Number of consecutive sampling periods without receiving peer
packets before declaring loss of continuity.

One-way
Reference period
One-way reference period.

Maximum delay
Maximum one-way average delay.

133
9: Performance Assurance Agent PAA configuration

Delay threshold
Maximum one-way delay allowed in samples.

Average delay threshold

One-way average delay threshold.

Maximum delay variation

Maximum one-way delay variation allowed.

Delay variation threshold

One-way delay variation threshold in samples.

Average delay variation threshold

One-way average delay variation threshold.

Two-way
Reference period
Two-way reference period.

Maximum delay
Maximum two-way average delay.

Delay threshold
Maximum two-way delay allowed in samples.

Average delay threshold

Two-way average delay threshold.

Maximum delay variation

Maximum two-way delay variation allowed.

Delay variation threshold

Two-way delay variation threshold in samples.

Average delay variation threshold

Two-way average delay variation threshold.

134
9: Performance Assurance Agent PAA status

PAA status
To view the status of all PAA probes, open the PAA > Status page.

The following information is presented for each probe.

• Index: A unique identifier assigned to the probe.
• Probe name: Unique name assigned to the probe. Click the name to view detailed status
information.
• State: Indicates the probe's current state. Possible values are:
• Disabled: This probe is disabled. To enable it, click the probe name and then select
the PAA state checkbox.
• Associating: Probe is looking for peer.
• Associated: Peer was found.
• Running: Running one time measurement.
• Idle: Idle after one time measurement completed.
• Locked IS: Locked traffic in service.
• Locked OOS: Locked traffic out of service.
• Status codes
• CC: Continuity Check
• EPL: Excessive Packet Loss
• 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

135
9: Performance Assurance Agent PAA status

Detailed PAA Clicking a probe name on the PAA > Status page presents more detailed information on a
status probe.

The following information is presented for the probe.

• Probe name: Unique name assigned to the probe. Click the name to view detailed status
information.
• Index: A unique identifier assigned to the probe.
• State: Indicates the probe's current state. Possible values are:
• Disabled: This probe is disabled. To enable it, click the probe name and then select
the PAA state checkbox.
• Associating: Probe is looking for peer.
• Associated: Peer was found.
• Running: Running one time measurement.
• Idle: Idle after one time measurement completed.
• Locked IS: Locked traffic in service.
• Locked OOS: Locked traffic out of service.

Alarms and status

Indicates the state of each probe’s alarm.

136
9: Performance Assurance Agent PAA results

PAA results
To view the results of all PAA probes, open the PAA > Results page.

The following information is presented for each probe.

• Index: A unique identifier assigned to the probe.
• Probe name: Unique name assigned to the probe. Click the name to view detailed results
information.
• State: Indicates the probe's current state. Possible values are:
• Disabled: This probe is disabled. To enable it, click the probe name and then select
the PAA state checkbox.
• Associating: Probe is looking for peer.
• Associated: Peer was found.
• Running: Running one time measurement.
• Idle: Idle after one time measurement completed.
• Locked IS: Locked traffic in service.
• Locked OOS: Locked traffic out of service.
• PLNE: Packet Loss ratio Near-End.
• PLFE: Packet Loss ratio Far-End.
• OADV: One-way Average Delay Variation.
• TAD: Two-way Average Delay.
• TADV: Two-way Average Delay Variation.

137
9: Performance Assurance Agent PAA results

Detailed PAA Clicking a probe name on the PAA > results page presents more detailed information.
results

• Current results for probe: Unique name assigned to the probe.

• Index: A unique identifier assigned to the probe.
• State: Indicates the probe's current state. Possible values are:
• Disabled: This probe is disabled. To enable it, click the probe name and then select
the PAA state checkbox.
• Associating: Probe is looking for peer.
• Associated: Peer was found.
• Running: Running one time measurement.
• Idle: Idle after one time measurement completed.
• Locked IS: Locked traffic in service.
• Period: Interval at which measurement packets were issued.

138
9: Performance Assurance Agent PAA results

Packet loss
This section provides Packet loss statistics for the near-end probe and the far-end probe.
• Near End: Represents the statistics of a specific probe.
• Far End: Represents the statistics as seen by the peer probe.

One-way delay variation

Two-way delay variation
• Instantaneous DV: Instantaneous delay variation value in microseconds.
• Minimum DV: Minimum delay variation in microseconds over one period.
• Maximum DV: Maximum delay variation in microseconds over one period.
• Average DV: Average delay variation in microseconds over one period.
• Nbr threshold exceeded: Number of times the threshold was exceeded.

Two-way delay
• Instantaneous delay: Instantaneous delay value in microseconds.
• Minimum delay: Minimum delay microseconds over one period.
• Maximum delay: Maximum delay microseconds over one period.
• Average delay: Average delay in microseconds over one period.
• Nbr threshold exceeded: Number of times the threshold was exceeded.

139
10: Traffic shaper Traffic shaper configuration

Chapter 10: Traffic shaper

10 Traffic shaper

Traffic shaper configuration

NOTE: Traffic shaper is only available on the MetroNID TE model.
This is the main tab used for traffic shaping, configuration and monitoring functions.

Traffic shaper menu

• Port: This option allows the user to configure the global traffic shaping parameters for the
outgoing port .
• Map: This option allows the user to edit the PCP to shaper map. It should be noted that
the PCPs are output by the Service Mapping module.
• Statistics: This option shows the CPU, loopback and Traffic generator traffic statistics.
• BLUE statistics: This option provides statistics on queue management.

Traffic shaper configuration

• Name: Unique name assigned to this shaper.
• State: State of the Shaper (Enabled/Disabled).
• Q-length: Size in KBytes of the shaper's queue.
• CIR: The shaping rate of green packets in Kbps (average output rate of the shaper).
• CBS: The shaping burst of green packets in Bytes (maximum output burst of the shaper).

140
10: Traffic shaper Traffic shaper configuration

• EIR: The shaping rate of yellow packets in Kbps (average output rate of the shaper).
• EBS: The shaping burst of yellow packets in Bytes (maximum output burst of the shaper).

Traffic shaper statistcs

• Name: Unique name assigned to this shaper.
• CIR: Instantaneous rate of green packets in Mbps.
• EIR: Instantaneous rate of yellow packets in Mbps.
• Drop green: Rate of dropped green packets in Mbps.
• Drop yellow: Rate of dropped yellow packets in Mbps.

To configure a traffic shaper, do the following:

1. Click on shaper-1

Enter the desired values for the shaper then enable the shaper and Apply.

BLUE performs queue management based on link utilization. It maintains a marking

probability pm to either mark or drop the packets. If the queue is continually dropping the
packets , pm is incremented by a factor /1.
If the queue is empty or link is idle, pm is decremented by a factor /2. The value of /1 should
be set significantly larger than /2. This is because link is underutilized when the congestion
management is either too aggressive or too conservative, but packet loss occurs only when
the congestion mechanism is too conservative.
BLUE uses one more parameter 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.

141
10: Traffic shaper Traffic shaper configuration

Before we move to the next step, traffic shaper statistics, we need to get some traffic flowing
through the shapers. The basic flow of information is:
• Traffic is received on the client port.
• There is a policy or policies on the port to set the PCP on the incoming traffic, This PCP
value will then be used to map the traffic to a specific shaper or the real-time queue.

For this example we will take VLAN 100 being received on the client port and send it to
shaper-1.

Create an L2 filter for VLAN100 and apply

2. Go to Traffic > L2 filter

Then we need to use this filter in a policy on the client port

Here is an example of a policy:

Here is an example of a policy:

142
10: Traffic shaper Traffic shaper configuration

By enabling this policy we are taking traffic being received on the client port with VLAN 100 and
directing it to shaper-1 before it is sent out the Network port.
On the screen capture below notice the Map information, PCP 1 will be directed to shaper-1.
3. Go to Traffic > shaping > Click on MAP

The PCP shaper mappping allows user to map the traffic to a shaper's queue based on the
PCP and CFI/DEI fields in the packets.

It is important to note that the PCP and CFI/DEI fields are values added to the ingress
packet by the Service Mapping module.

• Use DEI as precolor: When checked, the DEI/CFI is used to determine the precolor.
Otherwise, the user can manually specify the PCP precolor.
• Precolor: PCP precolor to be used by the shaper.
• Shaper: This is the shaper to which the PCP will be mapped.

143
10: Traffic shaper Traffic shaper statistics

Traffic shaper statistics

• PCP-Precolor: This is the list of all PCPs and their precolor that are currently mapped to
this shaper instance.
• Forward no delay: Total number of packets/bytes and rate forwarded by this shaper
without any delay.
• Forward with delay: Total number of delayed (enqueued) packets/bytes and rate
forwarded by this shaper instance.
• Drop queue overflow: Total number of packets/bytes and rate dropped due to the
shaper's queue overflow.
• Drop queue management (BLUE): Total number of packets/bytes and rate dropped by
the queue management algorithm (BLUE).
• Total yellow: This is the total number of yellow packets/bytes and rate forwarded by this
shaper.
• Total green: This is the total number of green packets/bytes and rate forwarded by this
shaper.
• CIR: Total number of packets/bytes and rate forwarded by this shaper using the CIR
bucket. Note that the Cfg value is the CIR configured by the user expressed in Mbps. For
the real-time shaper, this value is only shown when the port's global CIR is enabled.
• EIR: (Not available in the real-time shaper) Total number of packets/bytes and rate
forwarded by this shaper using the EIR bucket. Note that the Cfg value is the EIR
configured by the user expressed in Mbps.

144
10: Traffic shaper Traffic shaper statistics

145
11: CFM CFM continuity fault management

Chapter 11: CFM

11 CFM

CFM continuity fault management

To view a list of all CFM instances and their settings, open the CFM > Stack tab.

CFM stack:
• Stack: Central location to view all the CFM information.
• VID: VLAN ID to which the Maintenance Point is attached, or 0, if none.
• Level: MD level (or MEG level) of the Maintenance Point.
• Dir: Direction in which the Maintenance Point faces on the port.
• MID idx: The index of the Maintenance Domain to which the MP is associated, or 0 for
MEGs.
• MA idx: The index of the Maintenance Domain to which the MP is associated, or 0 for
MEGs.
• MEPID: The MEPID of the MEP.
• MAC address: MAC address of the Maintenance Point.

146
11: CFM CFM configuration

CFM configuration
To configure CFM, do the following:
1. Open the CFM > MD page.

2. Click Add to add a new MD configuration if required or you may use one of the
preconfigured defaults.
3. Configure CFM instance name and settings and click Apply.
4. Open the CFM > MA/MEG page

5. Click Add to add a new MA/MAG (Maintenance Association or Maintenance Entity

Group).

147
11: CFM CFM configuration

• The new MA/MEG configuration window.

• MD: There are eight pseudo MDs defined by default, one for each level, that are named
"Y.1731 level 0" to "Y.1731 level 7". These MDs exist only to simplify the integration of
Y.1731's MEGs with the CFM MIB which requires MDs. Y.1731 uses MEG-IDs which are
MAIDs without MD name. User interfaces show pseudo MD's name, but this name is not
included in Y.1731 CCM's MEG-ID. It is not possible to delete pseudo MDs
• Name format: The maintenance association (or MEG) name format. The valid values
are:
• PrimaryVid: Primary VLAN ID.
• String: RFC2579 DisplayString.
• Int16: 2-octet integer/big endian.
• 2865VpnId: RFC 2685 VPN ID.
• ICC-Based: ITU Carier Code format (Y.1731).
• CCM interval: Interval in milliseconds at which the CCMs are sent.
• Sender ID permission: Indicates what, if anything, is to be included in the Sender ID TLV
transmitted in CCMs, LBMs, LTMs, and LTRs. The valid values are:
• None : None.
• Chassis : Chassis ID and chassis subtype.
• Manage : Management Address.
• Chassis & manage : Chassis ID, subtype and Mgmt Address.
• Defer : Determined by domain configuration or system configuration.
• VLAN type: Specify the VLAN type associated with this Maintenance association or MEG.
If the value, None, is specified, the association is not attached to a VLAN and the content
of the VLAN ID list is ignored.
• VLAN ID list: Set of VLANs associated with this Maintenance association or MEG. If the
VLAN ID list is left empty, the association is not attached to a VLAN and the VLAN type is
set to None implicitly.
• MEP ID list: Set of MEPs associated with this Maintenance association or MEG.

148
11: CFM CFM configuration

6. Open the CFM > MEP > Configuration page

• Index: Unique index assigned to each Maintenance association End Point.

• MEPID: Maintenance association End Point Identifier (MEPID). An integer, unique to
each MA, identifying a specific MEP.
• Active: Indicates the administrative state of the MEP. True indicates that the MEP is to
function normally, and false indicates that it is to cease functioning.
• CCI: Indicates, if set to true, that the MEP will generate CCM messages
• Port: Indicates the port used by this MEP.
• Direction: The direction in which the MEP faces on the Bridge port. This can be up or
down.
• VLAN: The Primary VLAN ID of the MEP. This is always one of the VLAN IDs assigned to
the MEP's MA. The value 0 indicates that either the Primary VLAN ID is that of the MEP's
MA, or that the MEP's MA is associated with no VLAN ID.

149
11: CFM CFM configuration

7. Click Add to add a new MEP (Maintenance association End Point)

• MEP index: Unique index assigned to each Maintenance association End Point.
• MD index: Unique index assigned to each Maintenance Domain.
• MD name: The domain of the maintenance association (or MEG).
• MA/MAG index: The unique index of the maintenance association (or MEG).
• MA/MAG name: The maintenance association (or MEG).
• MEPID: Maintenance association End Point Identifier (MEPID). An integer, unique to
each MA, identifying a specific MEP in CCM frames.
• Port: Indicates the port used by this MEP.
• MAC address: Indicates the MAC address of the port used by this MEP.
• Direction: The direction in which the MEP faces on the Bridge port. This can be up or
down.
• Active: Indicates the administrative state of the MEP. Checked indicates that the MEP is
to function normally, and Unchecked indicates that it is to cease functioning.
• CCI enable: Indicates, if set to true, that the MEP will generate CCM messages.

150
11: CFM CFM configuration

• CCM sequence number: Enable or disable CCM sequence number. When enabled, a
MEP transmits CCMs with a sequence 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 sequence number enabled to allow a local MEP to
perform CCM based packet 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. The value 0 indicates that either the Primary VLAN ID is that
of the MEP's MA, or that the MEP's MA is associated with no VLAN ID.
• CCM and LTM priority: The priority parameter for CCMs and LTMs transmitted by the
MEP (default value: the highest priority, i.e. the highest numerical value allowed to pass
through the Bridge Port for any of this MEP's VLAN IDs).
• Lowest priority defect alarm: The lowest priority defect alarm specifies the lowest
priority defect that is allowed to generate a Fault Alarm.
• Fault notification alarm time: The time that defects must be present before a Fault
Alarm is issued.
• Fault notification reset time: The time that defects must be absent before resetting a
Fault Alarm.
• Enable fault propagation: Use this MEP's status in fault propagation.
• Propagate on port: Specify the EVC client port to which the MEP status should be
propagated. That port should be also configured to perform EVC fault propagation for this
parameter to take effect.

151
11: CFM CFM configuration

• Open the CFM > DMM > Configuration and select add

• DMM: Delay Measurement Message, used to measure delay and variation. Enter the
values and thresholds as required and apply.

152
11: CFM CFM configuration

8. Open the CFM > Packet loss > Configuration and select addf

9. Simply enable the Packet loss module and apply

153
11: CFM CFM statistics

CFM statistics
CFM MEP Statistics

• Index: Unique index assigned to each Maintenance association End Point.

• MEPID: Maintenance association End Point Identifier.
• CCM sent: Number of Connectivity Check Messages sent by this MEP.
• CCM received: Number of Connectivity Check Messages received by this MEP.
• RDI sent: Number of Connectivity Check Messages sent by this MEP with RDI bit set.
• RDI received: Number of Connectivity Check Messages received by this MEP with RDI
bit set.
• CCM seq error: The total number of out-of-sequence CCMs received from all remote
MEPs.

CFM DMM results

• Index: Unique index of the Delay measurement.

• MEP idx: Unique index assigned to each Maintenance association End Point.
• MEPID: Local MEP's Maintenance association End Point Identifier.
• R-MEPID: Remote MEP's Maintenance association End Point Identifier.
• Priority: Priority value to be used in VLAN tags, if present, in the transmitted frame.

154
11: CFM CFM statistics

Results Code definitions:

• OAD: One-way Average Delay
• OADV: One-way Average Delay Variation
• TAD: Two-way Average Delay
• TADV: Two-way Average Delay Variation

CFM packet loss results

• Index: Unique index of the Packet loss measurement.

• MEP idx: Unique index assigned to each Maintenance association End Point.
• MEPID: Local MEP's Maintenance association End Point Identifier.
• R-MEPID: Remote MEP's Maintenance association End Point Identifier.
• Priority: Priority value to be used in VLAN tags, if present, in the transmitted frame. Same
as MEP's CCM priority.
• Loss %: Packet loss ratio expressed as a percentage.
• Nbr gaps: Number of gaps.
• Largest gap: Largest gap size in packets

155
12: Command Line Interface Command summary

Chapter 12: Command Line Interface

12 Command Line Interface

Command summary
Note: For a list of all CLI command descriptions, use the help command in the CLI.
The CLI provides the following commands.

Ethernet port commands

• cable-test: Perform time domain reflectometry diagnostics.
• fault-propagation: Manage the link fault propagation between ports.
• media-selection: Select the ports' media type.
• port: Manage the link and physical level port settings.
• sfp: Display the SFP information, including digital diagnostics.

User traffic/flow through commands

• bandwidth-regulator: Manage bandwidth regulator database.
• cos-profile: Manage class of service profiles for service mapping.
• filter: Manage the filter database.
• forwarding: Manage user traffic encapsulation.
• policy: Manage policy entries applied on ports.
• regulator-set: Manage bandwidth regulator sets for service mapping.
• traffic-shaping: Manage Traffic shapers database

System management commands

• console: Manage the serial (RS-232) console port.
• date: Print or set the system date and time.
• dns: Manage the DNS settings.
• interface: Manage the interfaces used to access the management plane.
• mode: Define the ethertype for S-VLAN (0x88A8 or 0x9100).
• motd: Manage the MOTD of the unit.
• mtr: Manage management traffic regulation settings.
• ntp: Manage the network time client and server functions.
• permission-group: Manage the user privilege profiles.
• radius: Manage RADIUS authentication methods.
• route: Manage the IP routes and gateways.

156
12: Command Line Interface Command summary

• session: Manage the session settings or active sessions.

• snmp: Manage the SNMP agent settings.
• syslog: Manage the remote syslog settings.
• user: Manage user account settings including privilege profile.

OAM commands
• alarm: Manage the alarm settings.
• cfm: Manage the SOAM CFM feature
• loopback: Manage the loopback settings associated with an OAM instance.
• oam: Manage the OAM instances (802.3ah).
• paa: Manage the Performance Assurance Agent instances.

Utilities
• configuration: Export, import or factory reset the device configuration.
• firmware: Install a new firmware or display current firmware version.
• ping: Send pings to a specified host.
• reboot: Restart the device, equivalent to a power up boot.
• rfc2544: Run in-service and out-of-service packet generator and RFC-2544 tests.
• statistics: Clear all statistics. (port,policies,regulators,OAM)
• traceroute: Display the hops used to reach a given host.

Miscellaneous commands
• board: Manage assembly and environmental information.
• exit: Terminate the current CLI session.
• help <command-name>: Display this help or for a specific given command.
• quit: Terminate the current CLI session.
• syntax: Display the general command syntax.
• version: Display cli version.

157
12: Command Line Interface Command syntax

Command syntax
To see the syntax conventions used for all help commands, type
syntax
to display the following information:
Description:
Display CLI syntax explanations.
Syntax:
syntax

Syntax metacharacters
{} - Matches one in the set
[] - Optionally matches one in the set
* - Repeat 0 or more times
+ - Repeat 1 or more times
- - Matches one in the range
| - Separates options in a set
\ - Escape a metacharacter
_ - Single space character
<> - Syntax variable
<command> - <command-name> <command-modifier>* [[<target>]
<attribute-specifier>*]
<attribute-specifier> - <attribute-name> <attribute-value-list>
<attribute-value_list> - <attribute-value> [, <attribute-value-list>]
<command-name> - <key-word>
<attribute-name> - <key-word>
<attribute-value> - {<key-word> | <number> | <string>}
<key-word> - {a-z} [{a-z} | {0-9} | {\-}]*
<string> - {<characters> | <quoted-string>}
<quoted-string> - {"} <characters> [[ _ | <characters>]* <characters>] {"}
<characters> - {a-z | A-Z} [{a-z | A-Z |0-9 | : | ! | $ | % | ^ | & | \-}]*
<number> - <decimal> | <hexadecimal>
<decimal> - {0-9}+
<hexadecimal> - 0{x | X}{0-9 | a-f | A-F } [0-9 | a-f | A-F]*
<ip-addr> - <0-255>.<0-255>.<0-255>.<0-255>
<mac-addr> - <0-FF>:<0-FF>:<0-FF>:<0-FF>:<0-FF>:<0-FF>
<url> - <ip-addr>/[<path>]<file-name>
<path> - {<string>/}+
<file-name> - <string>
<dns-name> - <string>[.<string>]+
<port-name> - <string>
<connector-name> - <string>

Getting help
To get help on any CLI command type
help command_name

158
13: Appendix A - Alarms Alarms

Chapter 13: Appendix A - Alarms

13 Appendix A - Alarms

Alarms
The following alarms are supported:

Port module for link down and others related alarms.

• 1.001.01 -> link down on Management port
• 1.002.01 -> link down on Monitor-1 port
• 1.003.01 -> link down on Monitor-2 port
• 1.004.01 -> link down on Client port
• 1.005.01 -> link down on Network port
• 1.004.02 -> loopback on port Client
• 1.005.02 -> loopback on port Network

SFP module for Rx/Tx power, temp, vcc and lbc alarms and warnings.
• 2.001.01 -> SFP-A temperature high alarm
• 2.001.02 -> SFP-A temperature low alarm
• 2.001.03 -> SFP-A temperature high warning
• 2.001.04 -> SFP-A temperature low warning
• 2.001.05 -> SFP-A supply voltage high alarm
• 2.001.06 -> SFP-A supply voltage low alarm
• 2.001.07 -> SFP-A supply voltage high warning
• 2.001.08 -> SFP-A supply voltage low warning
• 2.001.09 -> SFP-A laser bias current high alarm
• 2.001.10 -> SFP-A laser bias current low alarm
• 2.001.11 -> SFP-A laser bias current high warning
• 2.001.12 -> SFP-A laser bias current low warning
• 2.001.13 -> SFP-A transmit power high alarm
• 2.001.14 -> SFP-A transmit power low alarm
• 2.001.15 -> SFP-A transmit power high warning
• 2.001.16 -> SFP-A transmit power low warning
• 2.001.17 -> SFP-A receive power high alarm
• 2.001.18 -> SFP-A receive power low alarm

159
13: Appendix A - Alarms Alarms

• 2.001.19 -> SFP-A receive power high warning

• 2.001.20 -> SFP-A receive power low warning
• 2.001.21 -> SFP-A not present
• 2.002.01 -> SFP-B temperature high alarm
• 2.002.02 -> SFP-B temperature low alarm
• 2.002.03 -> SFP-B temperature high warning
• 2.002.04 -> SFP-B temperature low warning
• 2.002.05 -> SFP-B supply voltage high alarm
• 2.002.06 -> SFP-B supply voltage low alarm
• 2.002.07 -> SFP-B supply voltage high warning
• 2.002.08 -> SFP-B supply voltage low warning
• 2.002.09 -> SFP-B laser bias current high alarm
• 2.002.10 -> SFP-B laser bias current low alarm
• 2.002.11 -> SFP-B laser bias current high warning
• 2.002.12 -> SFP-B laser bias current low warning
• 2.002.13 -> SFP-B transmit power high alarm
• 2.002.14 -> SFP-B transmit power low alarm
• 2.002.15 -> SFP-B transmit power high warning
• 2.002.16 -> SFP-B transmit power low warning
• 2.002.17 -> SFP-B receive power high alarm
• 2.002.18 -> SFP-B receive power low alarm
• 2.002.19 -> SFP-B receive power high warning
• 2.002.20 -> SFP-B receive power low warning
• 2.002.21 -> SFP-B not present

160
13: Appendix A - Alarms Alarms

EtherNID Performance Assurance Agent ™ alarms.

Note: These alarms are dynamically created based on the PAA probes configured.

xxx : PAA instance number

<probe-name> : PAA probe name

• 3.xxx.01 -> <probe-name> PAA_CC_ALERT

• 3.xxx.02 -> <probe-name> PAA_PL_ALERT
• 3.xxx.05 -> <probe-name> PAA_OW_DV_ALERT
• 3.xxx.06 -> <probe-name> PAA_OW_AVG_DV_ALERT
• 3.xxx.07 -> <probe-name> PAA_TW_DELAY_ALERT
• 3.xxx.08 -> <probe-name> PAA_TW_AVG_DELAY_ALERT
• 3.xxx.09 -> <probe-name> PAA_TW_DV_ALERT
• 3.xxx.10 -> <probe-name> PAA_TW_AVG_DV_ALERT

Example: With only 1 PAA probe created, called “paa_probe_1”, these alarms will be created:
3.001.01 -> paa_probe_1 PAA_CC_ALERT
3.001.02 -> paa_probe_1 PAA_PL_ALERT
3.001.05 -> paa_probe_1 PAA_OW_DV_ALERT
3.001.06 -> paa_probe_1 PAA_OW_AVG_DV_ALERT
3.001.07 -> paa_probe_1 PAA_TW_DELAY_ALERT
3.001.08 -> paa_probe_1 PAA_TW_AVG_DELAY_ALERT
3.001.09 -> paa_probe_1 PAA_TW_DV_ALERT
3.001.10 -> paa_probe_1 PAA_TW_AVG_DV_ALERT

Environmental module for fans, power supplies and temperature sensors.

• 8.000.01 -> First overheat threshold
• 8.000.02 -> Second overheat threshold
• 8.000.03 -> Power supply +5V DC
• 8.000.04 -> Power supply on -48V feed A
• 8.000.05 -> Power supply on -48V feed B

161
13: Appendix A - Alarms Alarms

162
14: Appendix B - MIB support Public MIBs

Chapter 14: Appendix B - MIB support

14 Appendix B - MIB support

Public MIBs
The following public MIBs are supported:

RFC-1213-MIB
• system group
• interface group
• snmp group
Note: Some groups have been removed for security reasons of the standard MIB-II.

IF-MIB
• ifXTable

EtherLike-MIB
• dot3StatsTable
• dot3PauseTable
• dot3HCStatsTable

RMON-MIB
• etherStatsTable
• etherHistoryHighCapacityTable
• historyControlTable
• etherHistoryTable

MAU-MIB
• ifJackTable
• ifMauAutoNegTable

163
14: Appendix B - MIB support Public MIBs

IEEE8021-CFM
• dot1agCfmStackTable
• dot1agCfmMdTable
• dot1agCfmMaNetTable
• dot1agCfmMaCompTable
• dot1agCfmMaMepListTable
• dot1agCfmMepTable
• dot1agCfmMepDbTable
• dot1agCfmMdTableNextIndex

164
14: Appendix B - MIB support Private MIBs

Private MIBs
The following private Accedian MIBs expose EtherNID configuration and status information.

ACCEDIAN-SMI.mib
This MIB contains all the information related to Accedian private tree and principal branches.

ACD-ALARM-MIB.mib
This MIB contains the general setting of the alarm manager and the tables for alarm
configuration and status.

ACD-CFM-MIB.mib
This MIB contains the information about CFM results for Delay Measurement Messages
(DMM) and Packet Loss (PL).

ACD-DESC-MIB.mib
This MIB contains the NID description, information and environmental values and status.

ACD-FILTER-MIB.mib
This MIB contains the Layer 2 and IPV4 filter tables.

ACD-PAA-MIB.mib
This MIB contains all the information about PAA configurations and measurement results.

ACD-POLICY-MIB.mib
This MIB contains the policies configuration table and the counters table for policy entries.

ACD-PORT-MIB.mib
This MIB contains the port configuration, status and statistics information.

ACD-REGULATOR-MIB.mib
This MIB contains all the information about the bandwidth regulator configurations and
statistics.

ACD-SFP-MIB.mib
This MIB contains all the information related to the SFP present in the NID.

165
14: Appendix B - MIB support Private MIBs

Alarms format
The alarm format is defined in the ACD-ALARM-MIB.mib file. The alarms are in SNMPv2
format and include the following fields.
• acdAlarmCfgID
• acdAlarmCfgSeverity
• acdAlarmCfgDesc
• acdAlarmStatusLastChange
• acdAlarmCfgServiceAffecting

166