Ethernid™ Administrator'S Guide: For The Ethernid™ Ee Ethernid™ Ge Metronid™ Te Metronid™ Te-R Metronid™ Te-S

EtherNID™
Administrator’s Guide
for the
EtherNID™ EE
EtherNID™ GE
MetroNID™ TE
MetroNID™ TE-R
MetroNID™ TE-S
1
Release 4.6.1 (August 2009)
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-2009 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 ...............................................................................................................................9
Introducing the EtherNID.......................................................................................................................................................................9

Features and benefits............................................................................................................................................................................10
Applications .........................................................................................................................................................................................10
Application scenario ..............................................................................................................................................................................11

About this scenario: .............................................................................................................................................................................11
2 HARDWARE INSTALLATION ........................................................................................................12
Hardware overview................................................................................................................................................................................12
Front panel ...........................................................................................................................................................................................13
Ethernet ports.......................................................................................................................................................................................13
SFP ports..............................................................................................................................................................................................13
Port functionality .................................................................................................................................................................................13
Status lights..........................................................................................................................................................................................16
Rear panel ............................................................................................................................................................................................16
Port/Connectors ...................................................................................................................................................................................16
Status light ...........................................................................................................................................................................................17
Buttons.................................................................................................................................................................................................17
Mounting options ...................................................................................................................................................................................18

Wall mounting .....................................................................................................................................................................................18
Desktop installation .............................................................................................................................................................................18
Rack mounting.....................................................................................................................................................................................19
Grounding the EtherNID......................................................................................................................................................................19
EtherSHELF.........................................................................................................................................................................................20
Grounding the EtherSHELF.................................................................................................................................................................20
Dimensions ..........................................................................................................................................................................................21
Powering the EtherNID.........................................................................................................................................................................22

DC power adapter ................................................................................................................................................................................22
48V DC from the 12 unit EtherSHELF................................................................................................................................................22
24V or 48V DC from the Terminal Block Adapter .............................................................................................................................23
48V DC via discrete power cord..........................................................................................................................................................23
Restarting ...............................................................................................................................................................................................25
Resetting to factory defaults..................................................................................................................................................................25
3 MANAGEMENT & CONFIGURATION ............................................................................................26
About the management web interface..................................................................................................................................................26

Starting the management web interface ...............................................................................................................................................26
Managing web interface accounts........................................................................................................................................................26
Managing accounts ..............................................................................................................................................................................27
Changing the default administrator password......................................................................................................................................27
Lost administrator password ................................................................................................................................................................27
3
Creating additional accounts................................................................................................................................................................28
DNS settings............................................................................................................................................................................................29
Use DHCP results ................................................................................................................................................................................29
Set DNS manually ...............................................................................................................................................................................29
Configuring interfaces ...........................................................................................................................................................................30

Creating or editing an interface............................................................................................................................................................30
Interface settings ..................................................................................................................................................................................31
Beacon settings ....................................................................................................................................................................................33
Auto interface settings .........................................................................................................................................................................34
Discovery settings................................................................................................................................................................................34
Advertisement settings.........................................................................................................................................................................35
Discovery inventory.............................................................................................................................................................................36
Routes......................................................................................................................................................................................................37
Adding a route .....................................................................................................................................................................................37
Route parameters .................................................................................................................................................................................38
Syslog options .........................................................................................................................................................................................39

Syslog parameters ................................................................................................................................................................................39
Remote syslog configuration ...............................................................................................................................................................40
Setting the system date and time ..........................................................................................................................................................41

Date and time settings..........................................................................................................................................................................42
Timezone and Daylight saving ..............................................................................................................................................................43
SNMP settings ........................................................................................................................................................................................44

SNMP parameters ................................................................................................................................................................................45
SNMP trap receivers ............................................................................................................................................................................46
SNMP trap receivers parameters..........................................................................................................................................................47
SNMP trap configuration parameters...................................................................................................................................................48
History buckets ......................................................................................................................................................................................49

Local Configuration .............................................................................................................................................................................49
Remote retrieval of history buckets......................................................................................................................................................50

Scheduling and file transfer configuration...........................................................................................................................................51
Certificate management ........................................................................................................................................................................54
Ping and Traceroute ..............................................................................................................................................................................55
General system settings .........................................................................................................................................................................56

Aggregator operation modes................................................................................................................................................................57
Session management ..............................................................................................................................................................................59

Management parameters ......................................................................................................................................................................59
Current sessions ...................................................................................................................................................................................59
Firmware upgrade .................................................................................................................................................................................61

Configuration maintenance ..................................................................................................................................................................61
System control .....................................................................................................................................................................................62
4
Session configuration .............................................................................................................................................................................63
Session parameters...............................................................................................................................................................................63
Session RADIUS.....................................................................................................................................................................................65
RADIUS parameters ............................................................................................................................................................................65
Show CPU usage ....................................................................................................................................................................................67

CPU usage parameters .........................................................................................................................................................................67
Management bridge ...............................................................................................................................................................................68

Configuration procedure ......................................................................................................................................................................68
4 PORT CONFIGURATION................................................................................................................70
Port list and port status .........................................................................................................................................................................70

Port configuration and status................................................................................................................................................................74
Port options ..........................................................................................................................................................................................74
Fault propagation .................................................................................................................................................................................75
Configuring port settings ......................................................................................................................................................................76

Port parameters ....................................................................................................................................................................................78
Port statistics ..........................................................................................................................................................................................81
PHY auto-negotiation configuration ....................................................................................................................................................82

PHY parameters...................................................................................................................................................................................84
SFP information.....................................................................................................................................................................................85
SFP information...................................................................................................................................................................................85
Monitoring information .......................................................................................................................................................................86
SFP thresholds .....................................................................................................................................................................................87
Temperature .........................................................................................................................................................................................87
Vcc.......................................................................................................................................................................................................88
Laser bias current.................................................................................................................................................................................88
Tx power ..............................................................................................................................................................................................88
Rx power..............................................................................................................................................................................................89
SFP memory and monitor memory ......................................................................................................................................................90
Cable verification...................................................................................................................................................................................91
Testing a cable .....................................................................................................................................................................................91
5 MONITORING & FILTERING ..........................................................................................................93
Service mapping.....................................................................................................................................................................................93
Viewing CoS profiles...........................................................................................................................................................................93
Configuring a CoS Profile ...................................................................................................................................................................94
CoS Profile parameters ........................................................................................................................................................................95
Assigning a CoS profile to a policy .....................................................................................................................................................96
Viewing Bandwidth regulator sets .......................................................................................................................................................96
Configuring a Bandwidth regulator set ................................................................................................................................................97
Bandwidth regulator set parameters.....................................................................................................................................................97
Assigning a Bandwidth regulator set to a policy..................................................................................................................................98
5
Layer-2 Protocol Tunneling ..................................................................................................................................................................99
Adding a new L2PT Rule .................................................................................................................................................................. 101
L2PT rule settings.............................................................................................................................................................................. 101
Traffic policies and monitoring .......................................................................................................................................................... 104

Configuring a traffic policy................................................................................................................................................................ 105
Policy settings .................................................................................................................................................................................... 105
Traffic filters ........................................................................................................................................................................................ 110

Viewing L2 filters .............................................................................................................................................................................. 110
Configuring an L2 filter ..................................................................................................................................................................... 110
L2 filter parameters............................................................................................................................................................................ 111
Viewing IPv4 filters........................................................................................................................................................................... 113
Configuring an IPv4 filter.................................................................................................................................................................. 114
IPv4 filter parameters......................................................................................................................................................................... 114
Bandwidth policing .............................................................................................................................................................................. 117

Configuring a regulator...................................................................................................................................................................... 118
Regulator settings .............................................................................................................................................................................. 118
Assigning a regulator to a policy ....................................................................................................................................................... 119
6 ALARMS........................................................................................................................................120
Alarm settings ...................................................................................................................................................................................... 120
Alarm configuration ............................................................................................................................................................................ 121

Customizing an alarm ........................................................................................................................................................................ 122
Alarm status ......................................................................................................................................................................................... 125
Chassis alarms...................................................................................................................................................................................... 126
7 OPERATIONS, ADMINISTRATION & MAINTENANCE ...............................................................127
OAM configuration.............................................................................................................................................................................. 127

Configuring an OAM instance........................................................................................................................................................... 128
OAM instance parameters.................................................................................................................................................................. 128
Loopbacks............................................................................................................................................................................................. 131
Adding a loopback ............................................................................................................................................................................. 132
Loopback parameters ......................................................................................................................................................................... 132
OAM events .......................................................................................................................................................................................... 135

Transmitted and Received event notifications ................................................................................................................................... 136
OAM status........................................................................................................................................................................................... 138

Detailed status information ................................................................................................................................................................ 139
Remote ............................................................................................................................................................................................... 140
OAM statistics ...................................................................................................................................................................................... 141

OAM detailed statistics information .................................................................................................................................................. 142
8 RFC-2544 ......................................................................................................................................146
6
Viewing RFC-2544 Generator ............................................................................................................................................................ 146
Configuring RFC-2544 Generator ..................................................................................................................................................... 147
RFC-2544 monitor ............................................................................................................................................................................... 151

Viewing RFC-2544 Monitor.............................................................................................................................................................. 151
Detailed view of RFC-2544 Monitor ................................................................................................................................................. 151
RFC-2544 testsuite ............................................................................................................................................................................... 154

Viewing RFC-2544 Testsuites ........................................................................................................................................................... 154
Detailed view of RFC-2544 Testsuites .............................................................................................................................................. 155
RFC-2544 reports ................................................................................................................................................................................ 159

Starting an RFC-2544 Testsuite......................................................................................................................................................... 159
Viewing RFC-2544 Reports............................................................................................................................................................... 160
9 PERFORMANCE ASSURANCE AGENT......................................................................................162
PAA configuration ............................................................................................................................................................................... 162

Configuring a probe ........................................................................................................................................................................... 163
PAA parameters................................................................................................................................................................................. 165
IGMP .................................................................................................................................................................................................... 169
PAA status ............................................................................................................................................................................................ 171

Detailed PAA status........................................................................................................................................................................... 172
PAA results........................................................................................................................................................................................... 174

Detailed PAA results.......................................................................................................................................................................... 175
1 TRAFFIC SHAPER........................................................................................................................177
Traffic shaper configuration ............................................................................................................................................................... 177
Traffic shaper statistics ....................................................................................................................................................................... 181
1 CFM ...............................................................................................................................................182
CFM continuity fault management .................................................................................................................................................... 182
CFM configuration .............................................................................................................................................................................. 183
CFM statistics....................................................................................................................................................................................... 194
1 COMMAND LINE INTERFACE .....................................................................................................196
Command summary ............................................................................................................................................................................ 196
Command syntax ................................................................................................................................................................................. 198
1 APPENDIX A - ALARMS...............................................................................................................199
7
Alarms................................................................................................................................................................................................... 199
1 APPENDIX B - MIB SUPPORT .....................................................................................................203
Public MIBs .......................................................................................................................................................................................... 203
Private MIBs ........................................................................................................................................................................................ 205
8
1: Introduction
1 Introduction
C
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.
1: Introduction
Features and benefits

• Ethernet OAM & loop-back — Increases visibility, management and easier maintenance.
• 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.
1: Introduction
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.
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.
2: Hardware Installation
2 Hardware Installation
C
Hardware overview
Front panel - EtherNID EE
Front panel - EtherNID GE
Front panel - MetroNID TE-S
Front panel - MetroNID TE / TE-R
Rear panel - All units

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)
Model SFP RJ-45

GE / Fiber SFP 10Base-THD/TFD
TE / 100Base- 100Base-TX/TXFD
TE-R BX10D/BX10U/FX/FXFD/LX10
1000Base-T/TFD
1000Base-
BX10D/BX10U/LX/LXFD/LX10
/SX/SXFD/T/TFD
(Auto-negotiation)
Copper SFP
10Base-TFD
100Base-TX/TXFD
1000Base-T/TFD
TE-S Fiber SFP 10Base-THD/TFD

100Base- 100Base-TX/TXFD
BX10D/BX10U/FX/FXFD/LX10
1000Base-
BX10D/BX10U/LX/LXFD/LX10
/SX/SXFD/T/TFD
(Auto-negotiation)
Copper SFP
10Base-TFD
100Base-TX/TXFD
1000Base-T/TFD
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.
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.
• 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.
MetroNID TE-S
• 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.
• SFP-C: This port is configured for connection to the client network. This configuration can be changed using the
• SFP-D: This port is configured for connection to the carrier network and is set to operate as a DHCP client.
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.5A connector: For use with the EtherSHELF connectors or a discrete power cord (connector sold
separately) providing +/-40 to +/-57 V DC.
• +/-20-36V---0.5A connector: For use only with a discrete power cord (connector sold separately) providing +/-20
to +/-36 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:
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 EMGIR4 from your computer, use a terminal emulation
program with the following settings:
z Protocol: Serial
z Port: COM1 to 8
z Baud rate: 115200
z Data bits: 8
z Parity: None
z Stop bits: 1
z 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 17 for
instructions.
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:
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 installation
Attach the included rubber feet to the bottom of the unit for added stability when placing on a desktop or other flat surface.
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.
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.
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.
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.
2. 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.
3. Strip one end of a 10-AWG wire to expose approximately 0.75 in. (20 mm).
4. Crimp the two-hole grounding lug around the exposed wire.
5. 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
6. 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
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. Once installed, attach the strain
relief to the center, threaded hole located above the power input with the supplied screw and washer:
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. 24V DC
models are not supported by the EtherSHELF. Slide the EtherNID or MetroNID unit 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.
24V or 48V DC from the Terminal Block Adapter

In a 1U rack mount bracket installation, it is sometimes preferable to use 24 or 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.
48V DC via discrete power cord

It is possible to power units with a custom built 24V or 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.
All models will have an isolated Return A and Return B.

The following diagram depicts the pin-out of the white +/- 24 or +/- 48V connector on the rear panel of the EtherNID and
MetroNID:
Isolated +/- 48V Return A and B Isolated +/- 24V Return A and B
The power source (+/-40 to +/-57 V DC) must be limited by a 0.5A/48V fast acting fuse or equivalent. There should be one
fuse per power feed.
The power source (+/-20 to +/-36 V DC) must be limited by a 1.0A/24V fast acting fuse or equivalent. 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).
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.
3: Management & Configuration
3 Management &
Configuration
C
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 management web interface

To start the management interface, do the following:
1. Use an Ethernet cable to connect the LAN port on a computer to the management port on 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 interface accounts

One administrator account is created by default with username and password both set to admin. The username and
password are case-sensitive. It is recommended that you change the default password immediately after installation to
safeguard the system. The administrator account provides access to all EtherNID features.
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 27.
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.
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
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, three 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.
• Auto: This is the Auto interface which will be listening for beacons by default on all ports. Once it receives a
beacon, there will be an interface automatically configured for the port on which the beacon was received.
Creating or editing an interface

To create or edit an interface, do the following:
1. Open the System > Interface page.
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:
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.
Interface settings
NOTE: It is valid to set the IP address for an interface to 0.0.0.0 when the interface is not required to be an IP interface.
For example, when the interface is used for OAM or test set interaction.
State
Enable or disable the interface. Upon interface creation, the default is enabled.
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,0x9100] (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 unit.
Use static IP until DHCP response

NOTE: This option can only be used when using Automatic IP (DHCP) mode.
Select this to use the manually configured IP address on the interface until an address is resolved by DHCP. This is
invalid on the Auto interface.
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.
• Default gateway: Specify a default gateway address. This provides a shortcut alternative to create a default
gateway other than through the route configuration. Note that only one default gateway can be set.
Beacon settings
State
Enable or disable the transmission of beacon frames on the interface. This is disabled by default.
Beacon rate
Used to select at which time interval the beacon frames will be sent.
Domain ID
The domain ID that will be used in the discovery process. The domain ID can be matched by remote devices to select
which beacons it should process.
IP config mode
Used to select the IP configuration mode that should be used by the receiver.
• Local: Use the remote device interface settings.
• Auto: Tell the remote device to compute an IP address, given the subnet, gateway and mask.
• Auto static: Behaves like Auto, but preserves the IP address, gateway and mask if an IP is already configured
(different than 0.0.0.0)
• DHCP: Use DHCP to get an IP address for the interface.
IP subnet
The subnet to be used by the remote device when the Auto IP configuration mode is selected.
Mask
The mask to be used by the remote device when the Auto IP configuration mode is selected.
Gateway
The gateway to be used by the remote device when the Auto IP configuration mode is selected.
Authorize ID mismatch
When enabled, it tells the receiver to accept beacons even if the beacon's domain ID does not match the local domain ID.
One shot beacon

When the Send button is pressed, the system will send a single beacon frame with the information that has previously
been committed. If changes to the beacon settings have been done without pressing the Apply button, they will not be
effective in the beacon frame.
Auto interface settings

NOTE: By Default there is an Auto interface created which cannot be deleted. The Auto interface type can only be
selected for this interface and this can be the only Auto interface created. This interface can however be disabled.
Discovery settings
(only available on Auto interface)
State
Enable or disable the auto configuration of an interface on beacon frame reception. This is enabled by default.
Auto media-selection
Enable or disable the scanning of ports to find out which ports have a link up. When 1 or 2 links are detected, the
appropriate media-selection mode is automatically selected. This should be used for initial system discovery and disabled
after the system has been configured. Note that when Discovery state is disabled, auto media-selection is also disabled.
ID matching
When enabled, it tells the receiver to accept beacons only if the beacon's domain ID matches the local domain ID.
Domain ID
The domain ID that will be used in the discovery process. The domain ID can be matched with the incoming beacon
domain ID to determine if the beacon should be processed.
Discovery ports
A list of ports that will be enabled to listen for incoming beacon frames.
Forward on bridge
When enabled, beacons and advertisement frames will be forwarded using the bridge associated to this interface, if a
bridge exists. Also, when this is enabled, the forwarding ports on match are not effective.
Forwarding ports on match

A list of ports to forward beacons and advertisement frames when the domain ID of these frames matches the configured
domain ID.
Forwarding ports on mismatch

A list of ports to forward beacons and advertisement frames when the domain ID of these frames does not match the
configured domain ID.
Advertisement settings
State
Enable or disable the advertisement of information frames. This is enabled by default on the Auto interface, and disabled
by default on all other interfaces.
Advertisement format
The frame format to use when sending information frames. Only proprietary Accedian ACP format is supported for now.
Use rate from beacon

When enabled, the advertisement transmission rate will match the rate that is configured in the beacon settings.
Transmission rate
The advertisement transmission rate to use, when the beacon rate option is disabled.
Discovery inventory
Enable inventory tracking
Use this option to enable the gathering of discovery inventory. This will display a table of all units that have advertisement
enabled to send an information frame on the network. You can use the hyperlink in the Remote NID IP column to connect
to the web server of a remote unit. You can also view more information of a specific unit by using the link in the Serial
Number column.
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.
Route parameters
Name
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.
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 parameters
Facility configuration
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.
Setting the system date and time

To set the system date and time, do the following:
1. Open the System > Configuration > 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 NTP 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.
Date and time settings

NTP enable
Enable this option to set the system time automatically by polling an NTP server. Select a server from the list or add your
own.
NTP server enable

Enable this option to start the NTP server service.
High resolution sync

Enable this option to use high resolution hardware synchronization. In this mode, the NTP server is queried multiple times
and the resulting time is derived from an averaging process based on a hardware clock. If unchecked, the NTP server is
only queried every 30 minutes and the system time is set accordingly, without further processing.
TAI offset
Offset to add to UTC time to convert to Temps Atomique International (Atomic International Time).
DSCP
When using NTP, the priority can be set in the DiffServ Code Point.
VLAN priority
When using NTP, the priority of the packets can be set in the VLAN priority bits if the link is through a VLAN.
Date and Time

If not using NTP you can set the date and time manually.
Timezone and Daylight saving

For a list of time zones and daylight saving time rules, please refer to: http://www.worldtimezone.com/.
UTC offset
Offset from Coordinated Universal 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 Daylight 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:
UTC 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

UTC offset=12, DST enable=check, DST offset=1,
DST start: Month=September, Week=5, Day=Sunday, Hour=2, Min=0
DST end: Month=April, Week=1, Day=Sunday, Hour=3, Min=0
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.
SNMP parameters
Enable Agent
Select this checkbox to enable the SNMP agent.
Use host name as system name

Select this checkbox to use host's name as system-name.
SNMP system name

Specify a name to identify the unit. By convention, this is the node's fully-qualified domain name.
Contact information
Specify contact information for the unit. Generally an email address.
System location
Identify the physical location of the unit.
Agent UDP port

Specify the UDP port the SNMP agent uses for all IPv4 interfaces.
Note: Changing this value restarts the SNMP agent.
Read-Only community
Specify the community string to control read-only access to the unit.
Read-Write community
Specify the community string to control read/write access to the unit.
Enable authentication trap generation

Enable this option to have a trap generated when authentication to the agent fails.
SNMP trap receivers
To configure SNMP trap options, do the following:

1. Open the System > SNMP > Traps page.
SNMP trap receivers parameters

Type
Type of SNMP Trap receivers. SNMPv1 / SNMPv2c
ID
ID number of the trap receiver.
State
If Enabled the unit will send SNMPv1 or SNMPv2c traps to a specified notification receiver.
UDP port
The UDP port that the unit will use to send traps to the notification receiver. By default, the well-known SNMP trap port
(162) is used.
Host name
The IP address or host name of the device that will receive SNMP traps (and/or inform notifications). The unit sends a
Cold Start trap when it starts up.
Community
The community string required to send traps to the notification receiver.
2. Click on the ID to configure each trap receiver.

SNMP trap configuration parameters

Enable trap
Enable this option to have the unit send SNMPv1 or SNMPv2c traps to a specified notification receiver.
Notification receiver
Specify the IP address or host name of the device that will receive SNMP traps (and/or inform notifications). The unit
sends a Cold Start trap when it starts up.
Community string
Specify the community string required to send traps to the notification receiver.
Host UDP port

Specify the UDP port that the unit will use to send traps to the notification receiver. By default, the well-known SNMP trap
port (162) is used.
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 Configuration
Enable history
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.
Remote retrieval of history buckets

NOTE: The Remote retrieval feature is only available on the MetroNID TE/TE-R/TE-S 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 > Agents > History page on the local MetroNID TE / TE-R /TE-S and add a new remote device.
Then enable scheduling at the desired time slot(s) and provide the URL for the file transfer server.
Scheduling and file transfer configuration

NOTE: The remote retrieval is only available on the MetroNID TE / TE-R /TE-S models.
Enable remote scheduling

Enable the history buckets to be retrieved from a list of remote devices, and report files to be generated.
This feature is dependant on the filing check boxes in the Local configuration sections of the remote devices. Only the
objects that have their filing feature enabled on the remote devices will be retrieved. The remote devices will ignore
requests for history buckets retrieval if their local scheduling is enabled.
Remote scheduled hours

The history buckets will be retrieved according to the Scheduled hours selected (Hold CTRL key to select more than one
time). Only hourly retrieval is possible for remote devices.
Enable local scheduling

Enable the history buckets report files to be generated by the local device.
This feature is dependent on the filing check boxes in the Local configuration sections of the local devices. Only the
objects that have their filing feature enabled on the local device will generate a report file. The local device will ignore
requests for history buckets retrieval if its local scheduling is enabled.
Local scheduled hours

The history buckets will be generated by the local device according to the Scheduled hours selected (Hold CTRL key to
select more than one time). Finer granularity is possible using the Scheduled minutes and Schedule offset fields.
Local scheduled minutes

This allows the local scheduling to be set to trigger every 15 minutes, either on the hourly boundary or on the 00:15, 00:30
and 00:45 boundaries. Any selection is valid as long as there is at least one box selected.
Schedule offset
This allows the local scheduling to be offset by [0-14] minutes. Using this field, reports can be generated as often as 4
times per hour. When a large number of devices are set to generate report files, this can be used to spread the load on
the network and servers.
Examples:
z If a device has 3:00 and 15:00 selected in the Scheduled hours, plus 00:00 and 00:30 in the Scheduled
minutes with a Schedule offset of 0 minutes, reports will be generated at 3:00, 3:30, 15:00 and 15:30.
z If a device has all hours selected in the Scheduled hours, plus 00:15 and 00:45 in the Scheduled minutes with
a Schedule offset of 4 minutes, reports will be generated at the 19th and 49th minute of every hour.
Server URL
The full URL of the Server on which to send the history bucket files once retrieved.
Examples:
z http://mypc.com
z ftp://username:password@mypc.com
z tftp://192.168.1.5
Period mode
This controls which periods are included in the generated reports. Three modes of operation are available. Note that this
setting affects both local and remote history buckets.
z All available periods: All the periods that are available on the devices are used to generate the reports, up to a
fixed maximum number of periods.
z New periods since last file transfer: All the periods that have been generated since the previous report has
been generated. If the Include periods from previous incomplete transfers option is selected, the periods
contained in a report that couldn't be properly generated or sent to the server will also be included.
z Fixed number of periods: All the periods available up to the user-specified number of periods. Note that the
number of periods to use can be set separately for local and remote reports.
Options
This allows controlling options on how the reports are generated.
z Include disabled objects: When checked, all manage objects will be included in the reports. If unchecked, only
objects which state is enabled will be included.
z Include periods from previous incomplete transfers: When checked, the periods contained in a report that
couldn't be properly generated or sent to the server will also be included in the current report. If unchecked,
only the periods since the previous schedule event will be included.
NOTE: The status of the Remote devices can be obtained by clicking on the Remote device name in the Remote device
configuration window (Only available on MetroNID TE / TE-R /TE-S models)
Certificate management
This section allows managing imported SSL certificates.
Common name
For a certificate authority (CA) it shows the name of the organization that emitted the certificate.
For a server, it should show the Fully Qualified Domain name of the service that will be using the certificate (only the web
server at this time).
For a client (Client) it may show the name of the application it will be used for.
Valid until
Date where the certificate will expire. It may still be valid if the peer has disabled checking.
Function
Describes how the certificate can be used in the unit. Possible values are:
z CA
Used to validate peer certificates and provided as part of the certificate chain for server applications.
z Client/Server
Client or server certificate. Those are certificates that were imported with a private key. It is possible for a CA
certificate imported with a private key to be used for this function. In that case, it will not show up as a CA.
Ping and Traceroute

This section allows the use of the ping and traceroute commands.
Open the System > Maintenance > System Tools page.
IP address
Specify the IP address to PING
Timeout
Number of PING messages to send (maximum count is 10).
IP address
Specify the IP address to TRACEROUTE
Hops
Number of hops to try (maximum hops is 30).
General system settings

To change the general settings of the unit do the following:
Open the System > Configuration > Mode page.
Current operation mode

In the case where a product supports more than one operation mode, this field displays the currently active mode.
Next operation mode

You can select the next operation mode to apply to this board after the next reboot.
IGMP version
Choose the IGMP version for the unit. This will affect the IGMP configuration of all interfaces on the unit.
S-VLAN ethertype
Choose a value for the S-VLAN ethertype. This will affect all unit entities that make use of the S-VLAN ethertype. (i.e.
interfaces, filters, rfc-2544)
Bandwidth regulator adjustment

Enable or disable the bandwidth regulator rate adjustment. This is used to preserve a specific Bandwidth rate when an
Encapsulation is being pushed onto an EVC.
Aggregator operation modes

NOTE: Aggregator modes are only available on MetroNID TE and TE-S models.
From the System > Configuration > Mode page, selecting the next operation mode will result in a warning that the Next
operation mode will be active after reboot.
After rebooting (Note that the configuration will be reset to factory default), you will see one of the following configurations
in Port > Configuration page. This shows that there are now four Client ports and one Network port when in 4x1 mode or
two Client ports, one Network port and one Protection port when in 2x1 mode. Note that the Protection port in
Aggregator2x1 mode cannot be used as a monitor port, it is to be used for Link or LACP protection.
Aggregator 4x1
Aggregator 2x1
When in Aggregator4x1 mode, all four Client port’s traffic (4x100Mbps) will be forwarded out the Network port (1Gbps).
When in Aggregator2x1 mode, both Client port’s traffic (2x1Gbps) will be forwarded out the Network port (1Gbps) with
equal priority. Traffic Policies will need to be configured on the Network port in order to have the incoming traffic
forwarded out the proper Client port. The following Policies page shows the new field added for the Network Traffic, when
in aggregator mode, in order to be able to specify the outgoing port based on the traffic filter.
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 parameters
Writelock session
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.
Firmware upgrade
To upgrade the EtherNID firmware, do the following:
1. Open the System > Maintenance > Firmware page.
2. Specify the location and name of the new firmware file or click Browse and select it.
3. Click Upgrade.
4. Once the firmware has been uploaded the unit will restart.
NOTE: All configuration settings are preserved as much as possible. Some changes may occur to reflect the new
functionality of the upgraded firmware.
Configuration maintenance
Use this page to import/export or rollback configurations. The imported/exported file is an agglomeration of all
configuration elements into an ASCII file. Since each product has different configuration elements that may be
incompatible, the file contains, at the top, an identifier to prevent importing the wrong file. Although possible, editing the
file is done at your own risk!
NOTE: A reboot of the unit is required for the new configuration to be activated.
Import a configuration as follows:

1. Click Browse.
2. Select the configuration file and click Open.
3. Click Import.
Export a configuration as follows:

1. Enter a filename for the configuration file in the text box.
2. Click Export.
Export a Vision EMS PPT file as follows:

1. Enter a filename for the PPT configuration file in the text box. The PPT file will be exported as a compressed ZIP file.
2. Click Export.
Factory default
This will bring the unit configuration back to factory defaults.
Cancel changes
This will cancel a factory reset or rollback action.
Rollback
This will bring back the configuration from last boot.
System control
Use these options to reboot and other system affecting functions.
Reboot
This will reboot the unit.
Session configuration
To configure session options, do the following:
1. Open the System > Session > Configuration page.
2. Define session parameters as required by your setup and then click Apply.
Session parameters
Max CLI sessions
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.
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 parameters
Authentication method
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 number 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.
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.
2 methods are supported for providing authorizations using standard RADIUS attribute.
If the attribute is not configured then the permissions will be set to:
• If the username exists locally, the local permissions will be assigned to the user.
• If the username does not exist locally, permissions will be set to viewer only.
Callback-Id (id=20)
Provides a fine grained permissions mechanism.
The permissions are the same as those that can be configured locally on the unit. It is a space or coma separated list of
tokens. They can be a mix of either locally defined user permission groups or individual privileges.
Service-Type (id=6)
Provides for full admin privileges if attribute is set to "Administrative-User". Any other value will grant viewer only.
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.
Service-Type = "Administrative-User"
Grant full administration privileges. Same as first example.
Show CPU usage

Indicates the CPU usage average over a period of time.
Open the Show > CPU usage page.
CPU usage parameters

Current
The CPU usage over the last second.
15 seconds average
The CPU usage average integrated from the last completed period of 15 seconds.
30 seconds average
60 seconds average
5 minutes average
The CPU usage average integrated from the last completed period of 5 minutes.
CPU usage history

The CPU usage over the last 100 seconds presented as a graph.
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 procedure
1. Power on EtherNID #1 with factory default settings.
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
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.
4: Port configuration
4 Port configuration
C
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:
• You will see the following page on an EtherNID GE or MetroNID TE / TE-R / TE-S:
NOTE: On a TE-S the ports will be SFP-A, SFP-B, SFP-C, SFP-D
• You will see the following page on a MetroNID TE / TE-S when in Aggregator4x1 mode:
• You will see the following page on a MetroNID TE / TE-S when in Aggregator2x1 mode:
Port configuration and status

Status
Indicates the status of the port.
• 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 / TE-S only)
Lets you select which two media connectors will be used to carry traffic.
These four options are available on the EtherNID GE and MetroNID TE / TE-R:
• SFP-A with SFP-B
• SFP-A with RJ-45-B
• RJ-45-A with SFP-B
• RJ-45-A with RJ-45-B
These four options are available on the MetroNID TE-S:

• SFP-A with SFP-B
• SFP-A with SFP-D
• SFP-C with SFP-B
• SFP-C with SFP-D
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
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.
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:
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 Link or LACP status Protection:
3. Define port parameters as required by your setup and then click Apply.
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
(Only on MetroNID products and 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 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 mentioned 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
• SFP must be a 1000X if link-status mode is selected. 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.
Mode
Switching to standby connector can be based on Link status or LACP status. If LACP status is selected, an L2PT rule with
an Operation mode Peer and Protocol LACP needs to be created on the this port in order to terminate LACP packets.
Working connector
Selects the working connector for the specified port. The connector choice allows the user to perform a switchover
operation.
Revertive
(Link status Mode only)
If enabled, the traffic is switched back to the main connector after the Revert period has expired.
Revert period
Specifies the time, in seconds, that we must continuously 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 enabled and auto-negotiation is also enabled, the exact behavior depends on auto-negotiation results.
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.
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 /TE-S you will see a page similar to the following:
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 grayed-out based on the
capabilities of the port.
PHY parameters
Advertisement configuration
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.
SFP information
(Supported only on the EtherNID GE / MetroNID TE / TE-R / TE-S)
To view SFP information, do the following:
1. Open the Port > SFP page.
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 8585
•SFP thresholds on page 87
•SFP memory and monitor memory on page 90
SFP information
This box displays general SFP information and monitoring 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).
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.
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.
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).
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.
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.
When completed, test status will be one of the following:

z GOOD: Normal cable.
z SHORT: Indicates that the positive and the negative lines of the same cable pair are touching: Possible
causes include:
z Cable wire may be touching the wire closet patch panel.
z Cable may be worn or broken allowing the positive and negative lines to touch.
z OPEN: Indicates that one pair on the cable is not connected at the far end of the cable. Possible causes
include:
z Cable is not connected.
z Cable was cut.
z 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.
z 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.
z Impedance Mismatch: Indicates that the effective impedance is not 100 Ohms. the TDR can determine an
impedance mismatch. Possible causes include:
z Different quality cables are connected together through a cable extender.
z A low quality cable is being used.
5: Monitoring & Filtering
5 Monitoring & Filtering

C
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:
z p-bits in 802.1Q / 802.1Q .1Q tags
z IP precedence bits in IPv4 TOS byte
z DSCP bits in IPv4 DSCP byte
The class of service value (0-7) assigned to the outgoing traffic is selected based on the conformance level
(Green/Yellow) of the incoming traffic.
Viewing CoS profiles

To view a list of configured CoS profiles, open the Traffic > Mapping page. By default, commonly used profiles. Index,
CoS profile's unique identifier.
Name
CoS profile's name as defined in the configuration page. Click this name for more details.
Type
CoS profile's type. Possible values are:
z PCP
z IP precedence
z DSCP
Reference count
The reference count is the number of policies that are currently using this CoS profile.
Configuring a CoS Profile

Once a Cos profile is created, it can be applied to policies for traffic classification.
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.
CoS Profile parameters

Name
Name of the CoS profile.
Type
Indicates the type of CoS profile. Possible values are:
z PCP
z IP precedence
z 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 precedence/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.
Assigning a CoS profile to a policy

Once a CoS profile has been configured you can assign it to a policy. See Traffic policies and monitoring on page 104.
Viewing Bandwidth regulator sets

To view a list of configured Bandwidth regulator sets, open the Traffic > Mapping page.
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:
z PCP
z IP precedence
z DSCP
Reference count
The reference count is the number of policies that are currently using this Bandwidth regulator set.
Configuring a Bandwidth regulator set

Once a Bandwidth regulator set is created, it can be applied to policies for traffic classification.
To configure a Bandwidth regulator set, do the following:
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 regulator set parameters

Name
Name of the Bandwidth regulator set.
Type
Indicates the type of Bandwidth regulator set. Possible values are:
z PCP
z IP precedence
z DSCP
Reference count (only visible on existing sets)

The reference count is the number of policies that are currently using this Bandwidth regulator set.
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 precedence/DSCP value.
Enable regulator
Enable or disable traffic regulation for this PCP, IP precedence or DSCP value.
Assigning a Bandwidth regulator set to a policy

Once a Bandwidth regulator set has been configured you can assign it to a policy. See Traffic policies and monitoring on
page 104.
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 from the incoming to the outgoing port. Optionally, EVC mapping can be enabled
on forwarding rules (see below).
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.
Type
The type of the rule, normal or catchall.
EVC Mapping
This allows the forwarding rules to perform VLAN tagging on the forwarded frames. Possible values are:
None: frames matching the specific rule are forwarded unmodified.
Push: frames matching the specific rule are forwarded with an extra VLAN tag determined by the VLAN ID field and their
Ethernet type is set to the value specified by the VLAN ethertype field.
Pop: frames matching the specific rule and where the VLAN tag matches the VLAN ID field and the Ethernet type
matches the value specified by the VLAN ethertype field are forwarded, with the VLAN tag stripped. If the frame's
VLAN ID or ethertype does not match, it is dropped.
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.
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.
Adding a new L2PT Rule

To add or edit an L2PT rule, do the following:
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 settings

Enable L2PT rule
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:
z 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.
z 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 from the incoming to the outgoing port. Optionally, EVC mapping can be
enabled on forwarding rules (see below).
• 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.
EVC Mapping
This allows the forwarding rules to perform VLAN tagging on the forwarded frames. Possible values are:
None: frames matching the specific rule are forwarded unmodified.
Push: frames matching the specific rule are forwarded with an extra VLAN tag determined by the VLAN ID field and their
Ethernet type is set to the value specified by the VLAN ethertype field.
Pop: frames matching the specific rule and where the VLAN tag matches the VLAN ID field and the Ethernet type
matches the value specified by the VLAN ethertype field are forwarded, with the VLAN tag stripped. If the frame's
VLAN ID or ethertype does not match, it is dropped.
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.
VLAN ethertype
Allows selecting the ethertype of the tag inserted in the forwarded frame. This is available only when the Forwarding
VLAN1 ethertype
Allows selecting the ethertype of the first tag inserted in the tunneled frame. This is available only when the Tunneling
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 ID
This specifies which VLAN tags to insert in the forwarded frames. The VLAN ID field is available only when the
Forwarding 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.
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.
Configuring a traffic policy

To configure a traffic policy, do the following:
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 filter is defined. This enables you
to monitor all traffic on a port.
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.
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.
Type VLANinVLAN VLAN, IP precedence,

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

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

VLAN 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 119.
Bandwidth regulator
Choose a default bandwidth regulator that will be associated with the traffic matched by this policy. To define a bandwidth
regulator see the Bandwidth policing section.
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.
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 filters
To view a list of active L2 traffic filters, open the Traffic > L2 Filters page. By default, 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.
Configuring an L2 filter
To configure an L2 filter, do the following:
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 parameters
L2 filter name
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).
"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.
Viewing IPv4 filters

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

z Filter name: Unique name assigned to the filter.
z 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.
z 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.
z 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)
z TCP is used by HTTP, FTP, Telnet, SMTP,
z UDP is used by DNS, SNMP, RIP,
z ICMP is used by Ping,
z 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).
z 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 IPv4 filter

To configure an IPV4 filter, do the following:
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.
IPv4 filter parameters

IPv4 filter name
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.
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.
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.

• 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.
Configuring a regulator
To configure a traffic regulator, do the following:
1. Open the Traffic > Regulators page.
2. Click Add to define a new regulator.:
3. Configure settings and click Apply.
Regulator settings
Traffic regulator name
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.
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 regulator to a policy

Once a regulator has been configured you can assign it to a policy. See Traffic policies and monitoring on page 104.
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.
6: Alarms
Alarm configuration
The Alarm > Configuration page lists all defined alarms.
6: Alarms
For a description of each field see Customizing an alarm on page 122.
Customizing an alarm
To customize an alarm, click its Number.
6: Alarms
Alarm number
Unique number that identifies this alarm. Assigned by the EtherNID.
The alarm number is composed of 3 fields, the module number, the instance number and the error number. The alarm
number looks like this A.BBB.CC and is express in decimal.
A: 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 SOAM module for CC, Packet Loss and other related alarms.
5 Unassigned
6 Unassigned
7 System module like NTP and other agents.
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
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: An 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.
6: Alarms
• 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.
6: Alarms
Alarm status
The Alarm > Status page presents a summary of all alarms.
For a description of each field see Customizing an alarm on page 122.

To view detailed information on an alarm click its Number. For example:
6: 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.
7: Operations, Administration & Maintenance
7 Operations, Administration &

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
transmits 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.
Configuring an OAM instance

To configure an OAM instance, do the following:
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 parameters

OAM instance name
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.
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

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
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.
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.
Adding a loopback
To add a loopback, do the following:
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 parameters
Name
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.
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
110.
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.
NOTE: 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:
z JDSU/Acterna™
z Enable discovery loop commands: Accept or discard JDSU/Acterna discovery loopback commands.
z Sunrise™: The EtherNID supports tests on layers 2 and 3.
z 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.
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.

Transmitted and Received event notifications
OAM Local Error Symbol Period Event

A sequence of six integers corresponding to the respective fields in the most recently 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 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 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.
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 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.
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
OAM status
The OAM > Status page presents a summary of the status of each OAM 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.
•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 information
Local
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 correspond to the Parser Action bits in the State field. The third bit corresponds to the Multiplexer Action bit in
the State field.
NOTE: These states will change when a loopback is enabled.
Vendor OUI
The value of the OUI variable in the Vendor Identifier field of the most recently transmitted Information OAMPDU. This
value is updated 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
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 correspond to the Parser Action bits in the State field. The third bit corresponds to the Multiplexer Action bit in
the State field.
NOTE: These states will change when a loopback is enabled.
Vendor OUI
The value of the OUI variable in the Vendor Identifier field of the most recently received Information OAMPDU.
Vendor specific info

The value of the Vendor Specific Information field of the most recently received Information OAMPDU.
OAM statistics
The OAM > Statistics page, presents a summary of the statistics for each OAM 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:

OAM detailed statistics information

Name
The name of the OAM instance.
Receive
Unsupported codes
A count of OAMPDUs received that contain an OAM code that is not supported by the device. This counter is incremented
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 contains 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.
• The OAMPDU code equals the OAM Information code and is supported by the device.
Unique event
A count of the OAMPDUs received that contain the Event Notification code. This counter is incremented 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.
• 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.
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:
• The Sequence Number field is equal to the Sequence Number field of the last received Event Notification
OAMPDU.
Loopback control
A count of OAMPDUs received that contain the Loopback Control code. This counter is incremented on reception of a
valid frame, with:
• The OAMPDU code equals the Loopback Control code and is supported by the device.
Variable request
A count of OAMPDUs received that contain the Variable Request code. This counter is incremented on reception of a
valid frame, with:
• The OAMPDU code equals the Variable Request code and is supported by the device.
Variable response
A count of OAMPDUs received that contain the Variable Response code. This counter is incremented on reception of a
valid frame, with:
• The OAMPDU code equals the Variable Response code and is supported by the device.
Organization specific
A count of OAMPDUs received that contain the Organization Specific code. This counter is incremented on reception of a
valid frame, with:
• The OAMPDU code equals the Organization Specific code and is supported by the device.
Transmit
Unsupported codes
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that is 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.
Information
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contains the OAM Information code.
This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAMPDU
code indicating an Information OAMPDU.
Unique event
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contains 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 Sequence Number field is not equal to the Sequence Number field of the last transmitted Event Notification
OAMPDU.
Duplicate event
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contains the Event Notification code.
This counter is incremented when a request service primitive is generated within the OAM sublayer.
• The Sequence Number field is equal to the Sequence Number field of the last transmitted Event Notification
OAMPDU.
Loopback control
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contains 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.
Variable request
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contains 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 non-resettable counter. This counter has a maximum increment rate of slow protocol frames (No more than
Variable response
A count of OAMPDUs passed to the OAM subordinate sublayer for transmission that contains the Variable Response
code. This counter is incremented when a request service primitive is generated within the OAM sublayer with an OAM
code indicating a Variable Response OAMPDU.
Organization specific
A count of Organization Specific OAMPDUs passed to the OAM subordinate sublayer for transmission that contains 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.
8: RFC-2544
: Error! Reference source not found.
8 RFC-2544
C
RFC-2544 Generator
NOTE: The RFC-2544 feature is only available on the EtherNID GE and MetroNID TE / TE-R / TE-S models.
Viewing RFC-2544 Generator

To view the RFC-2544 generator configuration, open the RFC-2544 > Generator > Configuration page.
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.
8: RFC-2544
Configuring RFC-2544 Generator

To edit the RFC-2544 Packet header settings, select First header packet settings show details button of the flow to be
edited.
1 .
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.
8: RFC-2544
Enable VLAN 1 header

This is to encapsulate all packets with 1 VLAN header.
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.
8: RFC-2544
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.
z Constant: The constant traffic type consists of sending packets at a specific bit rate (Kbps).
z 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.
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.
8: RFC-2544
Payload pattern
Select between fixed-data, incremental or random patterns in the payload part of the transmitted 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.
8: RFC-2544
RFC-2544 monitor
NOTE: The RFC-2544 feature is only available on the EtherNID GE and MetroNID TE / TE-R / TE-S models.
Viewing RFC-2544 Monitor

To view the RFC-2544 monitors, open the RFC-2544 > Monitor page.
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)
Detailed view of RFC-2544 Monitor

To view the detailed view of RFC-2544 measurements, click on the details link for the specific monitor.
8: RFC-2544
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.
8: RFC-2544
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.
8: RFC-2544
RFC-2544 testsuite
NOTE: The RFC-2544 testsuite feature is only available on the MetroNID TE / TE-R / TE-S models.
Viewing RFC-2544 testsuites

To view the RFC-2544 testsuites, open the RFC-2544 > Testsuite page.
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.
8: RFC-2544
Detailed view of RFC-2544 Testsuites

To view the detailed view of RFC-2544 testsuites, click on the testsuite name from the testsuite configuration list.
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.
8: RFC-2544
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.
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
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
8: RFC-2544
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 losses.
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 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 losses.
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 losses. 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 losses.
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
8: RFC-2544
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.
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.
8: RFC-2544
RFC-2544 reports
NOTE: The RFC-2544 reports feature is only available on the MetroNID TE / TE-R / TE-S models.
Starting an RFC-2544 Testsuite

To start an RFC-2544 testsuite, click on the Start new testsuite button in the RFC-2544 > Reports page. Configure the
report then click the Run button to start the 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.
8: RFC-2544
Special note
Information relative to the report not included in the previous fields.
Viewing RFC-2544 Reports

To view the RFC-2544 reports, open the RFC-2544 > Reports page and click on the name of the report to view.
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.
8: RFC-2544
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.

9: Performance Assurance Agent
9 Performance
Assurance Agent
C
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.

z Index: A unique identifier assigned to the probe.
z Probe name: Unique name assigned to the probe. Click the name to configure the probe.
z Type: Indicates the type of probe. Possible values are:
z layer-2: Probes occurs at layer 2.
z UDP: Probe occurs using UDP.
z Mode: Indicates if a probe generates (source) or collects (sink) measurement packets or does both (bi-dir).
z State: Indicates the probe's current state. Possible values are:
z Enabled: Enabled by configuration.
z Disabled: Disabled by configuration.
z Associating: Enabled looking for peer.

z Associated: Enabled peer found.
z Running: Running one time measurement.
z Idle: Idle after one time measurement completed.
z Locked IS: Locked traffic in service.
z Locked OOS: Locked traffic out of service.
z Destination: For layer-2 probes this is the peer’s MAC address. For UDP probe this is the peer’s IPV4 address.
z Sampling period: Interval at which PAA issues PAA measurement packets.
Configuring a probe
1. Open the PAA > Configuration page.
2. Click Add to create a new probe or click the probe name to edit an existing probe.
3. Configure parameters and click Apply.

PAA parameters
General
Name
Name of the PAA probe.
Type
Indicates the type of probe. Possible values are Layer-2 or udp.
Operation mode
Indicates if 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) or the 4 CRC bytes. Minimum value
is 61. Layer-2 maximum value is 1500. UDP maximum value is 1472.
Sampling period
Interval at which PAA issues PAA measurement packets.
Enable PAA probe

Enable or disable the PAA probe.
Local and Peer Indexes

Local Index
Specifies the local identifier for the probe. For add command, omitting the local identifier or specifying 0 means allocate
any free local identifier.
Remote Index
Specifies the remote peer identifier. When 0 is specified, the remote peer identifier is discovered dynamically based on
the probe name by an association phase.
Layer-2 specific parameters

Destination MAC address
The peer 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
Indicates the outgoing port used by this probe.
VLAN 1 ID
First VLAN ID. When enabled, layer-2 PAA packets are encapsulated into the specified VLAN ID.
VLAN 2 ID
Second VLAN ID. When enabled, layer-2 PAA packets are encapsulated into a second VLAN. Applies only when VLAN 1
ID is enabled.
VLAN 1 Priority
First VLAN priority bits. Applies only when VLAN 1 ID is enabled.
VLAN 2 Priority
Second VLAN priority bits. Applies only when VLAN 2 ID is enabled.
UDP specific parameters

The peer IPV4 Destination address.
Source UDP port

Specifies source UDP port (default 8793).
Destination UDP port

Specifies destination UDP port (default 8793).
Diff-Serv Codepoint (DSCP)

IP type of service field.
Explicit Congestion Notification (ECN)

The Explicit Congestion Notification value. (0 - 3)
VLAN 1 Priority
First VLAN priority bits.
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.
Continuity
Packet loss reference period

Packet loss reference period. This value needs to be at least 10 times the value of the sampling 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. This value needs to be at least 10 times the value of the sampling period.
Maximum delay
Maximum one-way average delay.
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.
NOTE: One-way delay measurements require time synchronization, via NTP, on units at each probe end.
Two-way
Reference period
Two-way reference period. This value needs to be at least 10 times the value of the sampling 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.
IGMP
One-way join period
Purpose
Indicates that IGMP join and leave delay measurements shall be performed and the period during which one-way and
packet loss samples shall be collected. This value should represent how long to collect measurements before issuing
an IGMP leave for each period.
Validity
UDP sink probe configured with a multicast destination address.
Values (in milliseconds)
0 (default): Constant, no join and leave measurement
Minimum: 10 * sampling period
Maximum: One-way reference period - (5 * sampling period)
IGMP Reference Period

Purpose
Defines a reference period for IGMP measurements. This period needs to be a multiple of the One-way reference
period.
Validity
One-way Join Period must be different than 0
0 (default): No IGMP measurement
Minimum: One-way reference period * 10
Maximum: One-way reference period * 9000
Maximum join delay

Purpose
Defines the maximum join delay objective.
Validity
Minimum: 100ms
Maximum: One-way join period
Join delay threshold

Purpose
Defines the maximum consecutives join delay samples allowed greater than the maximum join delay.
Validity
Values (in samples)
Minimum: 1
Maximum: (One-way join period / Sampling period)
Join average delay threshold

Purpose
Define the maximum join average delay.
Validity
Minimum: 100ms
Maximum: One-way join period
Maximum leave delay

Purpose
Defines the maximum leave delay objective.
Validity
0 (default): No IGMP measurement
Minimum: 100ms
Maximum: (One-way reference period - One-way join period)
Leave delay threshold

Purpose
Defines the maximum consecutives leave delay samples allowed greater than the maximum leave delay.
Validity
Values (in samples)
Minimum: 1
Maximum: (One-way reference period - One-way join period) / Sampling period
Leave average delay threshold

Purpose
Define the maximum leave average delay.
Validity
Minimum: 100ms
Maximum: (One-way reference period - One-way join period)
PAA status
To view the status of all PAA probes, open the PAA > Status page.
The following information is presented for each probe.

z Index: A unique identifier assigned to the probe.
z Probe name: Unique name assigned to the probe. Click the name to view detailed status information.
z State: Indicates the probe's current state. Possible values are:
z Disabled: Disabled by configuration.
z Associating: Enabled looking for peer.
z Associated: Enabled peer found .
z Running: Running one time measurement.
z Idle: Idle after one time measurement completed.
z Locked IS: Locked traffic in service.
z Locked OOS: Locked traffic out of service.
z Status codes
z CC: Continuity Check
z EPL: Excessive Packet Loss
z OD: One-way Delay
z OAD: One-way Average Delay
z ODV: One-way Delay Variation
z OAV: One-way Average Delay Variation
z TD: Two-way Delay
z TAD: Two-way Average Delay
z TDV: Two-way Delay Variation
z TAV: Two-way Average Delay Variation
Detailed PAA status

Clicking a probe name on the PAA > Status page presents more detailed information on a probe.
This page provides the status details for a specific PAA probe.
Probe Name
Probe's name as defined in the configuration page. Click this name for more details.
Index
Probe's unique identifier.
State
Probe's current State.
Alarms and status

Each of the following alarms can be in an active or inactive state.
• Continuity lost
• Excessive Packet Loss
• One-way Delay
• One-way Average Delay
• One-way Delay Variation
• One-way Average Delay Variation
• Two-way Delay
• Two-way Average Delay

• Two-way Delay Variation
• Two-way Average Delay Variation
NOTE: One-way delay measurements require time synchronization, via NTP, on units at each probe end.
PAA results
To view the results of all PAA probes, open the PAA > Results page.
This page provides a summary of the results of PAA probes.

Index
Probe's unique identifier.
Probe Name
Probe's name as defined in the configuration page. Click this name for more details.
State
Indicates the probe's current state. Possible values are:
• Disabled : Disabled by configuration.
• Associating : Enabled looking for peer.
• Associated : Enabled peer 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.
Results Codes definition

• PL : Packet Loss ratio
• OAD : One-way Average Delay
• OADV : One-way Average Delay Variation
• TAD : Two-way Average Delay
• TADV : Two-way Average Delay Variation
Detailed PAA results

Clicking a probe name on the PAA > results page presents more detailed information.
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 Enable PAA probe
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.
Packet loss
This section provides Packet loss statistics, the amount of gaps in the sequence number and the maximum gap size.
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.
One-way delay
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.
10: Traffic Shaper
10 Traffic Shaper
C
Traffic shaper configuration

NOTE: Traffic shaper is only available on the MetroNID TE / TE-S models.
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).
10: Traffic Shaper
• 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).
• 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 statistics

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

Click on shaper-1
Enter the desired values for the shaper then enable the shaper and Apply.
10: Traffic Shaper
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.
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

Go to Traffic > L2 filter
Then we need to use this filter in a policy on the client port

10: Traffic Shaper
Here is an example of a policy:
Here is an example of a policy:

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.
Go to Traffic > shaping > Click on MAP
The PCP shaper mapping 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.
10: Traffic Shaper
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.
C:
11: CFM
11 CFM
C
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.
• Port: This object represents the Bridge Port or aggregated port on which MEPs might be configured.
• 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.
11: CFM
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).
11: CFM
z The new MA/MEG configuration window.
z 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
z Name format: The maintenance association (or MEG) name format. The valid values are:
z PrimaryVid: Primary VLAN ID.
z String: RFC2579 DisplayString.
z Int16: 2-octet integer/big endian.
z 2865VpnId: RFC 2685 VPN ID.
z ICC-Based: ITU Carrier Code format (Y.1731).
z CCM interval: Interval in milliseconds at which the CCMs are sent.
z 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:
z None : None.
z Chassis : Chassis ID and chassis subtype.
z Manage : Management Address.
z Chassis & manage : Chassis ID, subtype and Mgmt Address.
z Defer : Determined by domain configuration or system configuration.
z 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.
z 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.
z MEP ID list: Set of MEPs associated with this Maintenance association or MEG.
11: CFM
6. Open the CFM > MEP > Configuration page
z Index: Unique index assigned to each Maintenance association End Point.

z MEPID: Maintenance association End Point Identifier (MEPID). An integer, unique to each MA, identifying a
specific MEP.
z 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.
z CCI: Indicates, if set to true, that the MEP will generate CCM messages
z Port: Indicates the port used by this MEP.
z Direction: The direction in which the MEP faces on the Bridge port. This can be up or down.
z 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.
11: CFM
7. Click Add to add a new MEP (Maintenance association End Point).
z MEP index: Unique index assigned to each Maintenance association End Point.
z MD index: Unique index assigned to each Maintenance Domain.
z MD name: The domain of the maintenance association (or MEG).
z MA/MAG index: The unique index of the maintenance association (or MEG).
z MA/MAG name: The maintenance association (or MEG).
z MEPID: Maintenance association End Point Identifier (MEPID). An integer, unique to each MA, identifying a
specific MEP in CCM frames.
z Port: Indicates the port used by this MEP.
z MAC address: Indicates the MAC address of the port used by this MEP.
z Direction: The direction in which the MEP faces on the Bridge port. This can be up or down.
z 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.
z CCI enable: Indicates, if set to true, that the MEP will generate CCM messages.
11: CFM
z 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.
z Note: A peer MEP should have sequence number enabled to allow a local MEP to perform CCM based packet
loss measurements.
z 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.
z 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).
z Lowest priority defect alarm: The lowest priority defect alarm specifies the lowest priority defect that is allowed to
generate a Fault Alarm.
z Fault notification alarm time: The time that defects must be present before a Fault Alarm is issued.
z Fault notification reset time: The time that defects must be absent before resetting a Fault Alarm.
z Enable fault propagation: Use this MEP's status in fault propagation.
z 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.
11: CFM
8. Open the CFM > LTM and click on the MEPID, then click Start to start the link trace.
• MEP index: Unique index assigned to each Maintenance association End Point.
• MEPID: Maintenance association End Point Identifier.
• Target type: Allows setting the link trace target by remote MEPID or MAC address.
• Remote MEPID: Specifies the target remote MEPID. The remote MEP MAC address should be resolved into
the local MEP database.
• MAC address: Specifies the target MAC address. Only unicast MAC address are valid for link trace target
address.
• TTL: Specifies the link trace time to live. Maximum value is 255. If 0 is specified no response should be
received.
• Set FDB only flag: Specifies if the LTM should set or not the flag "UseFDBonly" (IEEE 802.1ag) or the flag
"HWonly" (Y.1731).
• LTM sequence number: Indicates the sequence number used by the latest link trace request.
• Target MAC address: Indicates the target MAC address used by the latest link trace request.
• TTL: Indicates the TTL received in link trace responses.
• F: Forwarded. Indicates the responder maintenance point did forward the LTM.
• T: Terminal MEP. Indicates the responder maintenance point is a MEP.
• Action:
• Indicates how the responder system would process frame targeted for the destination address specified by the
LTM. Possible values are:
o RlyHit : The LTM reached an maintenance point whose MAC address matches the target MAC
address.
o RlyFDB : The Egress Port was determined by consulting the Filtering Database.
o RlyMPDB : The Egress Port was determined by consulting the MIP CCM Database.
• TLV type: Indicates what kind of TLVs were included in link trace responses.
• TLV value: Indicates TLV values included in link trace responses.
11: CFM
9. Open the CFM > LBM and click on the MEPID, then click Start to start the link trace.
• MEP index: Unique index assigned to each Maintenance association End Point.
• MEPID: Maintenance association End Point Identifier.
• Target type: Allows setting the loopback target by remote MEPID or MAC address.
• Remote MEPID: Specifies the target remote MEPID. The remote MEP MAC address should be resolved into the
local MEP database.
• MAC address: Specifies the target MAC address. Only unicast MAC address are valid for loopback target
address.
• VLAN priority: Specifies how to determine the LBM VLAN priority value:
o CCM priority : Use the same priority that MEP CCMs.
o Specific : Use a specific value specified by the Priority field.

• Priority: Specifies the value for LBM VLAN priority.
• VLAN drop eligibility: Specifies the value for LBM VLAN drop eligibility bit.
• Nbr message: Specifies the number of LBM to send.
• Interval: Specifies the interval between LBM in milliseconds. Valid values are between 100 and 5000 inclusively.
• Data TLV: Indicates if LBMs should include a Data TLV.
o None : No Data TLV included.
o Incremental : A Data TLV with incremental byte values will be included.
o Pattern : A Data TLV based on a user data pattern will be included.

• Length: Specifies the amount of data bytes inside the data TLV. Valid values are between 1 and 1488 inclusively.
• Pattern: Specifies a user data pattern for the Data TLV.
• Loopback request: Indicates if a loopback request is active for that MEP.
• Target MAC address: Indicates the target MAC address used by the latest loopback request.
11: CFM
• Latest start time: Indicates the time the latest loopback request was initiated for that MEP.
• Latest end time: Indicates the time the latest loopback request has completed or was stopped for that MEP.
• Nbr LBM requested: Indicates the number of LBM requested for the latest loopback request.
• Nbr LBM sent: Indicates the number of LBM sent for the latest loopback request. When the loopback is not active,
this number should be the same as the number of LBM requested. If not, this implies the loopback request was
stopped by a management command.
• Nbr LBR received: Indicates the number of LBR received for the latest loopback request.
• LBR with bad MSDU: Indicates the number of LBR received with a content that did not match the corresponding
LBM for the latest loopback request.
• Nbr LBR duplicated: Indicates the number of LBR received with a sequence number already received for the
latest loopback request.
• Packet loss ratio: Indicates the computed packet loss ratio for the latest loopback request.
• Nbr packet lost: Indicates the number of missing LBR for the latest loopback request.
• Nbr gaps: Indicates the number of time a sequence of LBR was missing during the latest loopback request.
• Largest gap size: Indicates the size in packets of the largest gap during the latest loopback request.
• Nbr LBR out of order: Indicates the number of time a LBR was received with a sequence number that did not
match the expected one during the latest loopback request.
11: CFM
10. Open the CFM > DMM > Configuration and select add
11: CFM
11. Open the CFM > DMM > Configuration and select add
z DMM: Delay Measurement Message, used to measure delay and variation. Enter the values and thresholds as
required and apply.
11: CFM
12. Open the CFM > Packet loss > Configuration and select add.
13. Simply enable the Packet loss module and apply

11: CFM
CFM statistics
CFM MEP Statistics
z Index: Unique index assigned to each Maintenance association End Point.

z MEPID: Maintenance association End Point Identifier.
z CCM sent: Number of Connectivity Check Messages sent by this MEP.
z CCM received: Number of Connectivity Check Messages received by this MEP.
z RDI sent: Number of Connectivity Check Messages sent by this MEP with RDI bit set.
z RDI received: Number of Connectivity Check Messages received by this MEP with RDI bit set.
z CCM seq error: The total number of out-of-sequence CCMs received from all remote MEPs.
CFM DMM results
z Index: Unique index of the Delay measurement.

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

z OAD: One-way Average Delay
z OADV: One-way Average Delay Variation
z TAD: Two-way Average Delay
z TADV: Two-way Average Delay Variation
CFM packet loss results
z Index: Unique index of the Packet loss measurement.

z MEP idx: Unique index assigned to each Maintenance association End Point.
z MEPID: Local MEP's Maintenance association End Point Identifier.
z R-MEPID: Remote MEP's Maintenance association End Point Identifier.
z Priority: Priority value to be used in VLAN tags, if present, in the transmitted frame. Same as MEP's CCM priority.
z Loss %: Packet loss ratio expressed as a percentage.
z Nbr gaps: Number of gaps.
z Largest gap: Largest gap size in packets
12: Command Line Interface
12 Command Line
Interface
C
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

z cable-test: Perform time domain reflectometry diagnostics.
z fault-propagation: Manage the link fault propagation between ports.
z lacp: Manage the link aggregation group configuration.
z media-selection: Select the ports' media type.
z port: Manage the link and physical level port settings.
z sfp: Display the SFP information, including digital diagnostics.
User traffic/flow through commands

z bandwidth-regulator: Manage bandwidth regulator database.
z cos-profile: Manage class of service profiles for service mapping.
z l2pt: Manage the Layer-2 Protocol Tunneling rules.
z filter: Manage the filter database.
z forwarding: Manage user traffic encapsulation.
z policy: Manage policy entries applied on ports.
z regulator-set: Manage bandwidth regulator sets for service mapping.
z traffic-shaping: Manage Traffic shapers database
System management commands

z certificate: Manage the SSL certificates.
z console: Manage the serial (RS-232) console port.
z echoagent: Manage the Creanord’s EchoVault agent configuration.
z date: Print or set the system date and time.
z dns: Manage the DNS settings.
z interface: Manage the interfaces used to access the management plane.
z mode: Define the general system settings.
z motd: Manage the MOTD of the unit.

z mtr: Manage management traffic regulation settings.
z ntp: Manage the network time client and server functions.
z permission-group: Manage the user privilege profiles.
z radius: Manage RADIUS authentication methods.
z route: Manage the IP routes and gateways.
z session: Manage the session settings or active sessions.
z snmp: Manage the SNMP agent settings.
z syslog: Manage the remote syslog settings.
z user: Manage user account settings including privilege profile.
OAM commands
z alarm: Manage the alarm settings.
z cfm: Manage the SOAM CFM feature
z loopback: Manage the loopback settings associated with an OAM instance.
z oam: Manage the OAM instances (802.3ah).
z paa: Manage the Performance Assurance Agent instances.
Utilities
z configuration: Export, import or factory reset the device configuration.
z firmware: Install a new firmware or display current firmware version.
z ping: Send pings to a specified host.
z reboot: Restart the device, equivalent to a power up boot.
z rfc2544: Run in-service and out-of-service packet generator and RFC-2544 tests.
z statistics: Clear all statistics. (port,policies,regulators,OAM)
z tcp-connect: Tries to connect to a TCP port to verify if a service is reachable.
z traceroute: Display the hops used to reach a given host.
Miscellaneous commands
z board: Manage assembly and environmental information.
z exit: Terminate the current CLI session.
z help <command-name>: Display this help or for a specific given command.
z quit: Terminate the current CLI session.
z syntax: Display the general command syntax.
z version: Display cli version.
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
13: Appendix A - Alarms
13 Appendix A - Alarms
C
Alarms
NOTE: Once an alarm has been raised (depending on the description of the alarm), the alarm will only be cleared once
the fault has been corrected and the alarm threshold off soaking period has expired.
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
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
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
SOAM module for CC, Packet Loss and other related alarms.
Note: These alarms are dynamically created based on the MEPs configured.
xxx : MEPID number
4.xxx.01 -> RDI on down MEP

4.xxx.02 -> MAC status on down MEP
4.xxx.03 -> Remote CCM on down MEP
4.xxx.04 -> Errored CCM on down MEP
4.xxx.05 -> Cross-connected CCM on down MEP
4.xxx.06 -> AIS on down MEP
4.xxx.07 -> One-way delay on down MEP
4.xxx.08 -> One-way average delay on down MEP
4.xxx.09 -> One-way delay variation on down MEP
4.xxx.10 -> One-way average delay variation on down MEP
4.xxx.11 -> Two-way delay on down MEP
4.xxx.12 -> Two-way average delay on down MEP
4.xxx.13 -> Two-way delay variation on down MEP
4.xxx.14 -> Two-way average delay variation on down MEP
4.xxx.15 -> Excessive packet loss on down MEP
System module like NTP and other agents.

7.001.01 -> NTP client lost server communication
Environmental module for 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
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
IEEE8021-CFM
dot1agCfmStackTable
dot1agCfmMdTable
dot1agCfmMaNetTable
dot1agCfmMaCompTable
dot1agCfmMaMepListTable
dot1agCfmMepTable
dot1agCfmMepDbTable
dot1agCfmMdTableNextIndex
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-DISCOVERY-MIB.mib
This MIB contains the information in the discovery inventory .
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.
ACD-SMAP-MIB.mib
This MIB contains all the information related to the Service Mapping configuration in the NID.
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

Ethernid™ Administrator'S Guide: For The Ethernid™ Ee Ethernid™ Ge Metronid™ Te Metronid™ Te-R Metronid™ Te-S

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ethernid™ Administrator'S Guide: For The Ethernid™ Ee Ethernid™ Ge Metronid™ Te Metronid™ Te-R Metronid™ Te-S

Uploaded by

Copyright:

Available Formats

EtherNID™

Introducing the EtherNID.......................................................................................................................................................................9

Application scenario ..............................................................................................................................................................................11

2 HARDWARE INSTALLATION ........................................................................................................12

Mounting options ...................................................................................................................................................................................18

Powering the EtherNID.........................................................................................................................................................................22

Resetting to factory defaults..................................................................................................................................................................25

3 MANAGEMENT & CONFIGURATION ............................................................................................26

About the management web interface..................................................................................................................................................26

Configuring interfaces ...........................................................................................................................................................................30

Syslog options .........................................................................................................................................................................................39

Setting the system date and time ..........................................................................................................................................................41

Timezone and Daylight saving ..............................................................................................................................................................43

SNMP settings ........................................................................................................................................................................................44

History buckets ......................................................................................................................................................................................49

Remote retrieval of history buckets......................................................................................................................................................50

Certificate management ........................................................................................................................................................................54

Ping and Traceroute ..............................................................................................................................................................................55

General system settings .........................................................................................................................................................................56

Session management ..............................................................................................................................................................................59

Firmware upgrade .................................................................................................................................................................................61

Show CPU usage ....................................................................................................................................................................................67

Management bridge ...............................................................................................................................................................................68

Port list and port status .........................................................................................................................................................................70

Configuring port settings ......................................................................................................................................................................76

Port statistics ..........................................................................................................................................................................................81

PHY auto-negotiation configuration ....................................................................................................................................................82

5 MONITORING & FILTERING ..........................................................................................................93

Traffic policies and monitoring .......................................................................................................................................................... 104

Traffic filters ........................................................................................................................................................................................ 110

Bandwidth policing .............................................................................................................................................................................. 117

Alarm settings ...................................................................................................................................................................................... 120

Alarm configuration ............................................................................................................................................................................ 121

Alarm status ......................................................................................................................................................................................... 125

Chassis alarms...................................................................................................................................................................................... 126

7 OPERATIONS, ADMINISTRATION & MAINTENANCE ...............................................................127

OAM configuration.............................................................................................................................................................................. 127

OAM events .......................................................................................................................................................................................... 135

OAM status........................................................................................................................................................................................... 138

OAM statistics ...................................................................................................................................................................................... 141

RFC-2544 monitor ............................................................................................................................................................................... 151

RFC-2544 testsuite ............................................................................................................................................................................... 154

RFC-2544 reports ................................................................................................................................................................................ 159

9 PERFORMANCE ASSURANCE AGENT......................................................................................162

PAA configuration ............................................................................................................................................................................... 162

IGMP .................................................................................................................................................................................................... 169

PAA status ............................................................................................................................................................................................ 171

PAA results........................................................................................................................................................................................... 174

Traffic shaper configuration ............................................................................................................................................................... 177

Traffic shaper statistics ....................................................................................................................................................................... 181

CFM continuity fault management .................................................................................................................................................... 182

CFM configuration .............................................................................................................................................................................. 183

CFM statistics....................................................................................................................................................................................... 194

1 COMMAND LINE INTERFACE .....................................................................................................196

Command summary ............................................................................................................................................................................ 196

Command syntax ................................................................................................................................................................................. 198

1 APPENDIX B - MIB SUPPORT .....................................................................................................203

Public MIBs .......................................................................................................................................................................................... 203

Private MIBs ........................................................................................................................................................................................ 205

Introducing the EtherNID

Features and benefits

About this scenario:

Front panel - EtherNID GE